KR102250642B1 - Decentralized and distributed contents management system for efeective contents ditribution and computing device for executing the same - Google Patents

Abstract

Disclosed are a decentralized content distribution management system and a computing device for performing the same. A content distribution management system according to an embodiment disclosed is a decentralized content distribution management system, which constitutes a distributed management node of a content distribution management system, creates a complex content by tree-structured content, and creates a complex content. And a first node terminal to register and a second node terminal to store metadata-related information on the composite content.

Description

DECENTRALIZED AND DISTRIBUTED CONTENTS MANAGEMENT SYSTEM FOR EFEECTIVE CONTENTS DITRIBUTION AND COMPUTING DEVICE FOR EXECUTING THE SAME}

The disclosed embodiment relates to a decentralized content distribution management system technology.

In general, the content distribution platform distributes content through the content creation stage → content registration and storage stage → content management and update distribution stage → content transmission and consumption stage.

However, in the existing content distribution platform, all other stages except the content authoring stage are managed by a service provider operating the distribution platform. That is, the existing content distribution platform is managed through a centralized system in which all processes such as content registration, distribution, and settlement are performed by content service providers.

In this case, 1) After content registration, the content author has a structure in which the settlement according to the consumption of the content is settled afterwards, and the contents of the settlement according to the consumption of the content have no choice but to rely on the data presented by the service provider. 2) In the content registration and storage stage, it is common for the service provider to manage the metadata for the content, which will lead to a qualitative difference in the management of popular content (and its authors) and non-popular content (and its authors). There will be no choice but to. In other words, between popular and unpopular content management and update stages and content transmission and consumption stages, there is a qualitative difference in management by service providers. 3) In addition, the amount of consumption of content is more likely to be influenced by the service provider (for example, by exposing specific content to more consumers). Therefore, according to the existing content distribution platform, content creators and content consumers have a structure in which content creators and content consumers are ultimately dominated by a service method of a service provider.

In addition, in the current content distribution system, each distribution service provider separately establishes and uses its own distribution system, which creates a high barrier to entry from the viewpoint of the supply and demand of the corresponding content to the service provider who intends to enter the service field. As a result, a business operator wishing to provide services for the same type of content must separately supply and manage content, which leads to poor management and efficiency in terms of distribution system and content.

To solve this problem, the Distributed File System is being used, but the existing distributed file system simply functions to distribute content using the system, and there is no content management subject, and there is no content deletion, access control, and Content management is impossible because there is no function such as content version inquiry.

Therefore, it is not a simple distributed file system as in the past, but manages the content life cycle such as content creation, update, deletion, etc., self-description-based access control, personal information protection, and content distribution A content distribution management system capable of management is required.

In addition, the existing content distribution platform is location based addressing (HTTP method), which uses a method of requesting content by looking for an IP address known to have content. However, in this case, the content previously existed, but may not exist at the present time, and such content can be known only by looking for the IP address and requesting the content.

As described above, since the existing content distribution platform uses location-based addressing (HTTP method) as the content storage management method, when operations such as system update due to server error and file path change are not performed efficiently, the corresponding content There is a problem in that it is not possible to approach itself.

In addition, since the existing content distribution platform recognizes related contents (derived contents) for the reference contents as separate contents, duplicate data (for example, meta data, etc.) are stored separately for each contents despite the same contents. There is a problem that needs to be managed and managed.

Korean Patent Application Publication No. 10-2013-0123106 (2013.11.12)

The disclosed embodiment is to provide a decentralized content management technique capable of securing transparency and reliability, and efficiently distributing and managing content.

The content distribution management system according to the disclosed embodiment is a decentralized content distribution management system, which constitutes a distributed management node of the content distribution management system, creates a complex content by tree-structured the content, and creates a complex content A first node terminal that registers; And a second node terminal storing metadata-related information on the composite content.

The first node terminal includes a content structuring module that tree-structures the content to generate complex content, and the content structuring module includes a basic metadata folder and an extended metadata folder in a lower folder of the complex content folder, which is an upper folder. , A content folder, and a derived content folder can be created to tree-structure the content.

The content structuring module generates a complex content ID that can be uniquely identified for the complex content, and calculates a hash value of the basic metadata folder, the extended metadata folder, the content folder, and the derived content folder, respectively. It is extracted, and version information of the composite content may be generated based on the extracted hash values.

When a change occurs among the content, the basic metadata of the content, and the expanded metadata of the content, the content structuring module makes the complex content ID of the complex content for the content the same, and the change occurs. The hash value of the created folder is extracted, and the version information of the composite content may be updated by adding the hash value extracted from the folder in which the change has occurred to the version information of the composite content.

The first node terminal further includes a self-signed module that generates a structure description file including description information on the structure of the complex content, and the content structuring module stores the structure description file in the complex content folder. I can.

The content structuring module generates a composite content ID that can uniquely identify the composite content, and the first node terminal determines the composite content ID when an event for the composite content occurs in the first node terminal. It may further include an event transmission module for transmitting the included event-related information to the second node terminal.

The second node terminal includes an event receiving module for receiving the event related information from the first node terminal; And extracting the composite content ID from the event-related information, accessing a first node terminal storing the composite content corresponding to the composite content ID in the content distribution management system, and connecting the connected first node terminal to the composite content ID. A metadata management module for extracting and storing basic metadata and extended metadata, respectively, from the basic metadata folder and the extended metadata folder of the content may be included.

When the first node terminal in the content distribution management system transmits a content search inquiry, the second node terminal checks whether a composite content ID corresponding to the content search inquiry is stored in the second node terminal, When the composite content ID is stored, a search module for transmitting the composite content ID to a first node terminal that has made the content search inquiry may be further included.

The first node terminal may further include a history management module for generating transmission history information when a transmission history for the composite content is generated, and linking the transmission history information to the composite content.

The second node terminal may include a transmission history collection module for collecting transmission history information for each complex content from the first node terminal.

The first node terminal generates a basic metadata folder, an extended metadata folder, a content folder, and a derived content folder in a subfolder of a compound content folder that is a parent folder, and tree-structures the content to create a complex content And a content structuring module for generating a complex content ID that can be uniquely identified for the complex content; A self-signed module for generating a structure description file including description information on the structure of the complex content; And an event transmission module for transmitting event-related information including the composite content ID to the second node terminal when an event for the composite content occurs in the first node terminal, wherein the second node terminal An event receiving module for receiving the event-related information from a node terminal; And extracting the composite content ID from the event-related information, accessing a first node terminal storing the composite content corresponding to the composite content ID in the content distribution management system, and connecting the connected first node terminal to the composite content ID. A metadata management module for extracting and storing basic metadata and extended metadata, respectively, from the basic metadata folder and the extended metadata folder of the content may be included.

The computing device according to the disclosed embodiment includes one or more processors, and a memory that stores one or more programs executed by the one or more processors, and constitutes a first node terminal of the content distribution management system. An apparatus comprising: a content structuring module configured to tree-structure content to generate complex content, generate a complex content ID that can uniquely identify the complex content, and register the generated complex content; And an event transmission module for transmitting event-related information including the composite content ID to a second node terminal of the content distribution management system when an event for the composite content occurs in the computing device.

A computing device according to another disclosed embodiment includes one or more processors, and a memory that stores one or more programs executed by the one or more processors, and constitutes a second node terminal of a content distribution management system. An apparatus, comprising: an event receiving module for receiving event-related information including a composite content ID of a composite content having a tree structured content from a first node terminal of the content distribution management system; And extracting the complex content ID from the event-related information, accessing a first node terminal storing the complex content corresponding to the complex content ID in the content distribution management system, and connecting the connected first node terminal to the complex content ID. It includes a metadata management module that extracts and stores basic metadata and extended metadata, respectively, from the basic metadata folder and the extended metadata folder of the content.

According to the disclosed embodiment, contents are tree-structured at each first node terminal constituting a distributed management node of a decentralized content distribution management system to create and register complex contents, so that content authors register contents as well as contents authoring steps. And it is possible for consumers to directly manage information necessary for purchase, such as metadata required in the storage stage and in the content management and update distribution stage. In addition, it is possible to exclude the influence of the amount of content consumption by the service provider, and to influence the consumption by the content itself, and the more content is consumed, the more stable and rapid distribution is possible.

In addition, by managing the distribution history of content through a reliable settlement system (i.e., blockchain), content authors can check settlement details in real time, and provide a content distribution environment that ensures transparency and reliability. You will be able to.

In addition, as contents are stored and managed using contents-based addressing, accessibility to the contents itself is improved, and redundant storage of contents can be prevented.

In addition, by adding a structure description file to the tree structure of the complex content, the structure of the complex content can be easily grasped, access control based on self-description, and personal information protection are possible. In this case, since complex content can be managed by each distributed management node, a decentralized content distribution management system can be implemented.

In addition, by providing a second node terminal with a special function to store metadata-related information of the complex content in the content distribution management system, the first node terminals in the content distribution management system search for the complex content through the second node terminal. It is possible to share information about complex content.

1 is a view showing the configuration of a content distribution management system for content distribution according to an embodiment of the present invention
2 is a diagram showing the configuration of a first node terminal according to an embodiment of the present invention
3 is a diagram schematically showing a tree structure of complex content in an embodiment of the present invention
4 is a diagram schematically illustrating a content management state according to a version of a composite content in an embodiment disclosed
5 is a block diagram showing the configuration of a second node terminal according to an embodiment of the present invention
6 is a diagram schematically showing a configuration for managing purchase history and other history of a content distribution management system according to an embodiment of the present invention
7 is a diagram showing the configuration of a content distribution management system for content distribution according to another embodiment of the present invention
8 is a diagram schematically showing the configuration of a content distribution service system using a content distribution management system according to an embodiment of the present invention
9 is a block diagram illustrating and describing a computing environment including a computing device suitable for use in example embodiments.

Hereinafter, a specific embodiment of the present invention will be described with reference to the drawings. The following detailed description is provided to aid in a comprehensive understanding of the methods, devices, and/or systems described herein. However, this is only an example and the present invention is not limited thereto.

In describing the embodiments of the present invention, when it is determined that a detailed description of a known technology related to the present invention may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of users or operators. Therefore, the definition should be made based on the contents throughout the present specification. The terms used in the detailed description are only for describing embodiments of the present invention, and should not be limiting. Unless explicitly used otherwise, expressions in the singular form include the meaning of the plural form. In this description, expressions such as "comprising" or "feature" are intended to indicate certain features, numbers, steps, actions, elements, some or combination thereof, and one or more It should not be construed to exclude the presence or possibility of other features, numbers, steps, actions, elements, any part or combination thereof.

In the following description, "transmission", "communication", "transmission", "reception" of signals or information, and other terms having a similar meaning are not only directly transmitted signals or information from one component to another component. It includes what is passed through other components. In particular, "transmitting" or "transmitting" a signal or information to a component indicates the final destination of the signal or information and does not mean a direct destination. The same is true for "reception" of signals or information. In addition, in the present specification, when two or more pieces of data or information are "related", it means that when one data (or information) is obtained, at least a part of other data (or information) can be obtained based thereon.

In addition, terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms may be used for the purpose of distinguishing one component from another component. For example, without departing from the scope of the present invention, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element.

1 is a diagram showing the configuration of a content distribution management system for decentralized content distribution according to an embodiment of the present invention.

Referring to FIG. 1, the content distribution management system 100 may include a plurality of first node terminals 102 and second node terminals 104. Here, the content distribution management system 100 may be a decentralized content distribution management system.

The plurality of first node terminals 102 are connected to each other to enable communication through the communication network 150. In addition, the plurality of first node terminals 102 are communicatively connected with the second node terminal 104 through the communication network 150.

Each first node terminal 102 may be a terminal constituting a distributed management node for content distribution within the content distribution management system 100. For example, each first node terminal 102 may be a terminal of the copyright holder of the content. In this case, the first node terminal 102 may register (upload) content to the content distribution management system 100. When the first node terminal 102 registers the content in the content distribution management system 100, the first node terminal 102 itself is a terminal constituting a distributed management node, so the content is stored in the first node terminal 102. It can mean doing.

Here, the first node terminal 102 may structure and register the content so that the life cycle of the content can be managed (that is, the content can be managed within the content distribution management system 100). When registering or updating content, the first node terminal 102 may transmit metadata-related information of the corresponding content to the second node terminal 104.

In addition, each first node terminal 102 may be a terminal of a user who wants to share content through the content distribution management system 100. In this case, the first node terminal 102 may search and download the content to be shared through the second node terminal 104 in the content distribution management system 100. In this case, in the disclosed embodiment, the content itself can be inquired with the content distribution management system 100 through a content-based addressing technique to find a node storing the corresponding content. Details on this will be described later.

2 is a diagram showing the configuration of a first node terminal according to an embodiment of the present invention. Here, when the first node terminal 102 registers content in the content distribution management system 100, the configuration of the first node terminal 102 will be described.

Referring to FIG. 2, the first node terminal 102 includes a content structuring module 111, a self-signature module 113, an event transmission module 115, a history management module 117, and an integrated interface 119. can do.

The content structuring module 111 can structure the content so that the content registered by the first node terminal 102 can be managed in the content distribution management system 100 to manage the life cycle related to content creation, update, and deletion. have. Hereinafter, structured content may be referred to as composite content.

The content structuring module 111 may structure the content to be registered in the content distribution management system 100 into a tree structure having an upper folder and a subordinate folder thereof. That is, the content structuring module 111 generates complex content by tree-structuring the content. When the generated complex content is located in an upper folder, the content structuring module 111 may include a plurality of subfolders dependent thereon.

Here, content-based addressing can be used so that the content itself serves as an address. Each content consists of several blocks, and each block has a hash value obtained by hashing the corresponding block. In this case, each content may be uniquely identified with an encryption hash including a link. In this case, each content itself serves as a link.

In addition, each content can check the integrity of data through a checksum, and since the hash value is changed during forgery, it is possible to quickly check whether or not forgery is forged. In addition, since the same content has the same hash value, it is possible to prevent overlapping of the content. The first node terminal 102 may store a distributed hash table to manage each hash value in the tree structure of each composite content.

3 is a diagram schematically showing a tree structure of complex content according to an embodiment of the present invention. Referring to FIG. 3, subfolders of the composite content folder 302 may include a basic meta data folder 304, an extended meta data folder 306, a content folder 308, and a derivative content folder 310. .

The content structuring module 111 includes a composite content folder 302, a basic metadata folder 304, an extended metadata folder 306, and a content folder 308 for content to be uploaded to the content distribution management system 100. And a derived content folder 310 may be created and structured. In the disclosed embodiment, "folder" may be a term for expressing a logical upper and lower concept rather than a physically existing folder. The tree structure of such complex content is only an example, and is not limited thereto. Here, it will be described as an embodiment that the content is multimedia content.

The basic metadata folder 304 may store basic metadata for content. That is, the content structuring module 111 may store basic metadata about the content in the basic metadata folder 304. The basic metadata may include identification metadata for identification of content and metadata for content. For example, the basic metadata may include the title (title) of the content, the copyright holder of the content, the creation date and time of the content, and information on the person appearing in the content.

The hash values of the basic metadata folder 304 and its subordinate data are stored in a distributed hash table, and the corresponding distributed hash table can be managed in the distributed management system area of each distributed management node.

The extended meta data folder 306 may store extended meta data for content. That is, the content structuring module 111 may store extended metadata for the content in the extended metadata folder 306. The extended meta data may include meta data of a type not defined in the basic meta data. In an exemplary embodiment, the extended metadata may include metadata related to content sales conditions, content access control, and download restrictions, in addition to basic metadata. For example, the extended metadata may include content encryption information, content digital rights management (DRM) information, content sales restriction age (eg, 19 years or older), and the like.

The hash values of the extended metadata folder 306 and its subordinate data are stored in a distributed hash table, and the corresponding distributed hash table may be managed in a distributed management system area of each distributed management node.

Corresponding content (content actually consumed by users) may be stored in the content folder 308. For example, when the content is a record, sound source files in the record may be stored in the content folder 308. A hash value of the content folder 308 and its subordinate data is stored in a distributed hash table, and the corresponding distributed hash table may be managed in a distributed management system area of each distributed management node.

In the derived content folder 310, content derived from the corresponding content (original content) (for example, content in which a part of the original content has been changed or added, or a summary of the original content or content in which the resolution of the original content has been changed, etc.) will be stored. I can. The hash values of the derived content folder 310 and its subordinate data are stored in a distributed hash table, and the corresponding distributed hash table may be managed in a distributed management system area of each distributed management node.

The content structuring module 111 may generate complex content identification information including a complex content ID (CCID) and version information for the complex content. The composite content ID can be created to uniquely identify the composite content. Version information may be generated when metadata or content in the composite content is changed.

Specifically, the content structuring module 111 converts predetermined content into a composite content folder 302, a basic metadata folder 304, an extended metadata folder 306, a content folder 308, and a derivative content folder 310. When structuring, a unique composite content ID (CCID) can be created for the composite content. For example, the content structuring module 111 may generate a unique composite content ID based on a time stamp value of the date and time when the composite content was created and user identification information (eg, a user account, etc.).

In addition, the content structuring module 111 calculates a first hash value that is a hash value of the basic meta data folder 304, the extended meta data folder 306, the content folder 308, and the derived content folder 310 of the composite content. Each extracted and combined with the extracted first hash values may generate version information of a corresponding composite content. Here, for convenience of description, it may be referred to as version 1 (Ver 1) in the sense of first version information of the composite content.

Here, when derivative content is added to the corresponding content, the content structuring module 111 may generate the composite content by updating version information while keeping the composite content ID (CCID) the same. Specifically, the added derivative content may be stored in the derived content folder 310, and a second hash value, which is a hash value of the derived content folder 310 in which the added derived content is stored, may be extracted. The content structuring module 111 may update version information by adding the second hash value to version information of version 1 (ie, version information generated by a combination of first hash values). For convenience of description, the updated version information may be referred to as version 2 in the sense of second version information of the composite content.

In this way, when a derivative content in which the content of the content has been changed occurs, the content can be efficiently managed by updating the version information while keeping the composite content ID the same (ie, using one composite content ID). In this case, in version 2 (Ver 2) of the composite content, a new hash value is generated for the derived content of the changed content, and only the relationship with the hash value representing the existing data needs to be set. It is possible to prevent the case where contents and the like are stored redundantly. That is, since basic metadata, extended metadata, and content are included in version information of version 1 (Ver) of the composite content, it is not necessary to store them redundantly.

4 is a diagram schematically illustrating a content management state according to a version of a composite content in an embodiment disclosed.

Referring to FIG. 4, when a composite content having a composite content ID (CCID) of QmTqGE9999 is first registered ^{, version information of a 1 st} version of composite content 410 may be registered as QmTqGE00000 (411). And, there may be three history tags (431, 432, 433) for the ^{1 st version of the composite content 410.} The identification information of the first history tag 431 may be QmTqGE1000, the identification information of the second history tag 432 is QmTqGE1001, and the identification information of the third history tag 433 may be QmTqGE1002.

Here, the 1 ^st version of the composite content 410 may have an ID of QmTqGE123 for the root tree 413, and its subfolders include basic metadata 415, contents 417, and a structure description file 419 ( manifest.json) can be included. Here, the hash value of the basic metadata 415 may be QmTqGE100, the hash value of the content 417 may be QmTqGE101, and the hash value of the structure description file 419 may be QmTqGE113.

On the other hand, if the compound contents ID (CCID) is to be made to update the version of the second register for the compound contents QmTqGE9999, 2 version information for the compound contents 420 of ^nd version may be registered as mTqGE00001 (421). 2 there may be one record tag 434 with respect to the compound contents 420 of ^nd version. The identification information of the fourth history tag 434 may be QmTqGE1003.

Here, 2 ^nd Version compound contents 420 of may be in the ID of the root tree (423) QmTqGE1245, it may be included in the structure description file (425) (manifest.json) as its subfolders.

That is, the second compound contents 420 of ^nd version are the structure description file in the compound contents 410 of the 1 ^st version changes, the other base metadata 415 and the content 417 can be the same. At this time, the second in the compound contents 420 of ^nd version 1, the same base metadata 415 and the content 417, and the compound contents 410 of the ^st version to include only the link 427, the information in the routing tree 423 By doing so, it is possible to manage version information while preventing duplicate storage of basic metadata and contents.

Existing content distribution management systems can avoid redundant storage of contents by recognizing and registering all contents as new contents when partial contents change (for example, meta data change or derivative contents, etc.) However, in the disclosed embodiment, it is possible to prevent redundant storage of content and the like and efficiently manage the content through version information management of the composite content.

In addition, the structure description file 312 may be included in the composite content folder 302. The structure description file 312 may include description information on the structure of the complex content. A detailed description of this will be described later.

The self-signed module 113 may generate a structure description file 312. The content structuring module 111 may store the structure description file 312 generated by the self-signed module 113 in the composite content folder 302.

Here, the structure description file 312 may include description information on the structure of the composite content. That is, the structure description file 312 may have a tree structure of complex content in a form, and information on which files are stored in the upper folder and the subordinate folder thereof may be included. Therefore, a user who has downloaded the composite content through the content distribution management system 100 can check which files are stored in each folder of the composite content only by looking at the structure description file 312 without having to manually check the subfolders of the composite content. There will be.

In addition, the structure description file 312 may include information on access control and personal information protection for data included in the composite content. In an exemplary embodiment, the structure description file 312 includes information on whether or not content is encrypted (eg, information including encryption and decryption methods (URI, etc.) when encrypted, and a decryption module for decryption and content use. Player information (such as URI)) may be included. The structure description file 312 may include information on whether to protect personal information (eg, a description of a range of accessible data when personal information protection is applied). The structure description file 312 may include information on whether or not a third party is authenticated (eg, information on a corresponding certification authority, applicable authentication processor technology, etc.). The structure description file 312 may include additional element descriptions required for content use (eg, copyright verification processor technology for unencrypted content, etc.).

When the first node terminal 102 downloads the complex content from the content distribution management system 100, the self-signed module 113 may serve to analyze the structure description file 312 of the corresponding complex content.

When the complex content is registered, deleted, and updated in the first node terminal 102, the event transmission module 115 may transmit event-related information to the second node terminal 104.

That is, the event transmission module 115 may notify the second node terminal 104 of such an event when an event such as registration, deletion, and update of complex content occurs in the first node terminal 102. Here, the event-related information may include composite content identification information (ie, composite content ID and version information). In addition, the event-related information may include event content information (ie, content such as whether the event is registration, deletion, or update of complex content).

The history management module 117 may store a transmission history of the composite content registered in the first node terminal 102. That is, the history management module 117 may store a transmission history of when and to whom and how much data is transmitted for each complex content registered in the first node terminal 102, respectively. Transmission history information may be stored by linking with the corresponding complex content.

The transmission history information can be used to compare with the content transaction history information in the blockchain, and in this case, the reliability of the content distribution management system 100 can be improved. Through the transmission history information, it is possible to transparently check all the transmission history of each complex content. And, the transmission history information can be exchanged with each other in a reliable manner between the sender and the receiver of the corresponding composite content.

The integrated interface 119 may serve to communicate and connect the first node terminal 102 with an external system. In an exemplary embodiment, the external system may be a block chain for managing distribution history of content. That is, when content (complex content) is distributed or shared through the content distribution management system 100, the distribution history of the content can be managed through a block chain. In this case, it is possible to transparently operate the settlement contents according to the distribution of contents.

Referring back to FIG. 1, the second node terminal 104 may be a node in charge of storing metadata-related information of contents registered in the content distribution management system 100. The second node terminal 104 may provide a function for the first node terminals 102 to search for contents registered in the content distribution management system 100.

That is, the second node terminal 104 stores metadata-related information of each of the registered contents so that the first node terminals 102 can search and share the contents registered in the system in the content distribution management system 100. It may be a node that performs a special function to search.

5 is a block diagram showing the configuration of a second node terminal 104 according to an embodiment of the present invention. Referring to FIG. 5, the second node terminal 104 may include an event reception module 121, a metadata management module 123, a search module 125, and a transmission history collection module 127.

The event receiving module 121 may receive event-related information from each first node terminal 102 of the content distribution management system 100. That is, the event receiving module 121 may collect events related to complex content that occur in each first node terminal 102 of the content distribution management system 100.

The metadata management module 123 extracts the composite content ID from the event-related information received by the event receiving module 121, and the first node terminal 102 that holds the corresponding composite content ID in the content distribution management system 100 ) Can be accessed.

The metadata management module 123 may extract and store the structure description file 312 from the corresponding complex content of the first node terminal 102. Then, after analyzing the structure description file 312 to check the structure of the corresponding complex content, basic metadata and extended metadata are extracted from the basic metadata folder 304 and the extended metadata folder 306 of the complex content, respectively. Can be saved after

In this case, the metadata management module 123 includes metadata (including basic metadata and extended metadata) and structure description files of complex contents stored in the first node terminal 102 in the content distribution management system 100 Each will be saved. Here, the metadata-related information may include metadata and a structure description file.

The search module 125 may provide a function for the first node terminal 102 to search for content in the content distribution management system 100. When the first node terminal 102 transmits a content search inquiry, the search module 125 may check whether a content corresponding to the content search inquiry exists in the content distribution management system 100.

In other words, the search module 125 may check whether the composite content ID of the content corresponding to the content search inquiry is stored in the second node terminal 104. When a complex content ID of a content corresponding to a content search inquiry exists, the search module 125 may extract the corresponding complex content ID and transmit it to the first node terminal 102 that made the content search inquiry. Then, the first node terminal 102 may establish a P2P connection with the other first node terminal 102 storing the composite content based on the composite content ID.

In the disclosed embodiment, by collecting and storing metadata-related information of the complex content stored in each first node terminal 102 through a special node called the second node terminal 104, the first node terminals 102 It is possible to search and share information on complex contents in the distributed management system 100.

The transmission history collection module 127 may collect and store transmission history information for each complex content from the first node terminals 102. The collected transmission history information may be shared with a content settlement system (for example, a system for content distribution history and settlement management based on a block chain).

In the present specification, a module may mean a functional and structural combination of hardware for performing the technical idea of the present invention and software for driving the hardware. For example, the "module" may mean a predetermined code and a logical unit of hardware resources for executing the predetermined code, and does not necessarily mean a physically connected code or a single type of hardware.

6 is a diagram schematically showing a purchase history and other history management configuration of a content distribution management system according to an embodiment of the present invention.

Referring to FIG. 6, the storage 300 of the content distribution management system 100 may be the storage 300 of the first node terminal 102 constituting a distributed management node. Each complex content may be structured and stored in a tree structure in the storage 300. In an exemplary embodiment, each of the composite contents is a subfolder of the composite content folder 302 and includes a basic meta data folder 304, an extended meta data folder 306, a content folder 308, a derived content folder 310, and A structure description file 312 may be included.

In addition, the version information 314 and the history tag 316 may be linked to each of the composite contents through a link. The history tag 316 may indicate where the corresponding transmission history information 318 is stored. Here, it may be referred to FIG. 4 that the composite content is linked with the version information 314 and the history tag 316. Each composite content is managed by one composite content ID (CCID), and version information 314 may be added according to a change in content or the like. At this time, since the unchanged parts can be linked to those stored in the existing version, efficient content management is possible.

7 is a diagram showing the configuration of a content distribution management system for content distribution according to another embodiment of the present invention. Here, a portion that differs from the embodiment shown in FIG. 1 will be mainly described.

Referring to FIG. 7, the content distribution management system 100 may include a plurality of first node terminals 102, second node terminals 104, and third node terminals 106. Here, since the first node terminal 102 and the second node terminal 104 are the same as or similar to those shown in FIG. 1, detailed descriptions thereof will be omitted.

The third node terminal 106 may be a type of storage node. That is, the third node terminal 106 may store complex content registered by each of the first node terminals 102. When registering the composite content, the first node terminals 102 may transmit the composite content stored in the first node terminal 102 to the third node terminal 106.

The third node terminal 106 prepares for a situation in which the power of the first node terminals 102 in which the predetermined complex content is stored is all turned off, and the corresponding complex content cannot be downloaded from the other first node terminal 102. It may be a storage node that stores each composite content to distribute the composite content.

8 is a diagram schematically showing the configuration of a content distribution service system using a content distribution management system according to an embodiment of the present invention.

Referring to FIG. 8, the content distribution service system 800 may include a content distribution management system 100, a distribution service provider system 802, and a content settlement system 804.

The content distribution management system 100 may include a first node terminal 102 and a second node terminal 104. The first node terminal 102 may structure the content to create a complex content and register it in the content distribution management system 100. The second node terminal 104 may each store metadata-related information of the composite content registered in each of the first node terminal 102.

The distribution company system 802 may refer to a system built by a business operator who wants to distribute content through the content distribution management system 100. The distribution service provider system 802 may receive complex content information registered in the content distribution management system 100 from the content distribution management system 100.

The content settlement system 804 may be a system for performing settlement according to content distribution when content is distributed through the content distribution management system 100. The content settlement system 804 may be a blockchain-based system. The content settlement system 804 may receive complex content information registered in the content distribution management system 100 from the content distribution management system 100. The content settlement system 804 may store a distribution history of complex content.

In addition, the content settlement system 804 may store sales contract information of each complex content. When the first node terminal 102 registers the composite content, sales contract information (eg, information on how much the composite content will be sold) may be transmitted to the content settlement system 804.

9 is a block diagram illustrating and describing a computing environment 10 including a computing device suitable for use in example embodiments. In the illustrated embodiment, each component may have different functions and capabilities in addition to those described below, and may include additional components in addition to those described below.

The illustrated computing environment 10 includes a computing device 12. In one embodiment, the computing device 12 may be the first node terminal 102. Also, the computing device 12 may be a second node terminal 104. Also, the computing device 12 may be a third node terminal 106.

The computing device 12 includes at least one processor 14, a computer-readable storage medium 16 and a communication bus 18. The processor 14 may cause the computing device 12 to operate in accordance with the aforementioned exemplary embodiments. For example, the processor 14 may execute one or more programs stored in the computer-readable storage medium 16. The one or more programs may include one or more computer-executable instructions, and the computer-executable instructions are configured to cause the computing device 12 to perform operations according to an exemplary embodiment when executed by the processor 14 Can be.

The computer-readable storage medium 16 is configured to store computer-executable instructions or program code, program data, and/or other suitable form of information. The program 20 stored in the computer-readable storage medium 16 includes a set of instructions executable by the processor 14. In one embodiment, the computer-readable storage medium 16 includes memory (volatile memory such as random access memory, nonvolatile memory, or a suitable combination thereof), one or more magnetic disk storage devices, optical disk storage devices, flash It may be memory devices, other types of storage media that can be accessed by the computing device 12 and store desired information, or a suitable combination thereof.

The communication bus 18 interconnects the various other components of the computing device 12, including the processor 14 and computer readable storage medium 16.

Computing device 12 may also include one or more input/output interfaces 22 and one or more network communication interfaces 26 that provide interfaces for one or more input/output devices 24. The input/output interface 22 and the network communication interface 26 are connected to the communication bus 18. The input/output device 24 may be connected to other components of the computing device 12 through the input/output interface 22. The exemplary input/output device 24 includes a pointing device (mouse or track pad, etc.), a keyboard, a touch input device (touch pad or touch screen, etc.), a voice or sound input device, various types of sensor devices, and/or photographing devices. Input devices, and/or output devices such as display devices, printers, speakers, and/or network cards. The exemplary input/output device 24 may be included in the computing device 12 as a component constituting the computing device 12, and may be connected to the computing device 12 as a separate device distinct from the computing device 12. May be.

Although the exemplary embodiments of the present invention have been described in detail above, those of ordinary skill in the art to which the present invention pertains will understand that various modifications can be made to the above-described embodiments without departing from the scope of the present invention. . Therefore, the scope of the present invention is limited to the described embodiments and should not be determined, and should not be determined by the claims to be described later, but also by those equivalents to the claims.

100: content distribution management system
102: first node terminal
104: second node terminal
106: third node terminal
111: Content structuring module
113: self-signed module
115: event transmission module
117: history management module
119: integrated interface
121: event receiving module
123: metadata management module
125: search module
127: transmission history collection module
800: Content distribution service system
802: distribution business system
804: Content settlement system

Claims (13)

As a decentralized content distribution management system,
A first node terminal configuring a distributed management node of the content distribution management system, generating a complex content by tree-structuring the content, and registering the generated complex content; And
It includes a second node terminal for storing metadata-related information on the composite content,
The first node terminal,
A content structuring module for generating complex content by tree-structuring the content,
The content structuring module,
A content distribution management system for tree-structuring the content by creating two or more of a basic metadata folder, an extended metadata folder, a content folder, and a derived content folder in a subfolder of a composite content folder that is a parent folder.
delete The method according to claim 1,
The content structuring module,
Create a composite content ID that can be uniquely identified for the composite content,
A content distribution management system for extracting hash values of the basic metadata folder, the extended metadata folder, the content folder, and the derived content folder, and generating version information of the composite content based on the extracted hash values.
The method of claim 3,
The content structuring module,
When a change occurs among the content, the basic metadata of the content, and the expanded metadata of the content, the composite content ID of the composite content for the content is the same,
A content distribution management system for extracting a hash value of the folder in which the change has occurred, and updating version information of the composite content by adding the hash value extracted from the folder in which the change has occurred to the version information of the composite content.
The method according to claim 1,
The first node terminal,
Further comprising a self-signed module for generating a structure description file including description information on the structure of the complex content,
The content structuring module,
A content distribution management system for storing the structure description file in the composite content folder.
The method according to claim 1,
The content structuring module,
Create a composite content ID that can be uniquely identified for the composite content,
The first node terminal,
The content distribution management system further comprising an event transmission module for transmitting event-related information including the composite content ID to the second node terminal when an event for the composite content occurs in the first node terminal.
The method of claim 6,
The second node terminal,
An event receiving module for receiving the event-related information from the first node terminal; And
Extracting the composite content ID from the event-related information, accessing a first node terminal storing the composite content corresponding to the composite content ID in the content distribution management system, and the composite content from the accessed first node terminal Content distribution management system, including a metadata management module that extracts and stores the basic metadata and extended metadata, respectively, from the basic metadata folder and the extended metadata folder.
The method of claim 7,
The second node terminal,
When the first node terminal in the content distribution management system transmits a content search inquiry, it is checked whether a complex content ID corresponding to the content search inquiry is stored in the second node terminal, and the complex content ID is stored. If present, the content distribution management system further comprising a search module for transmitting the complex content ID to the first node terminal that made the content search inquiry.
The method according to claim 1,
The first node terminal,
A content distribution management system further comprising a history management module for generating transmission history information when a transmission history for the composite content is generated, and linking the transmission history information to the composite content.
The method of claim 9,
The second node terminal,
A content distribution management system comprising a transmission history collection module for collecting transmission history information for each composite content from the first node terminal.
The method according to claim 1,
The content structuring module generates a composite content by tree-structuring the content, and generates a composite content ID that can uniquely identify the composite content,
The first node terminal,
A self-signed module for generating a structure description file including description information on the structure of the complex content; And
Further comprising an event transmission module for transmitting event-related information including the composite content ID to the second node terminal when an event for the composite content occurs in the first node terminal,
The second node terminal,
An event receiving module for receiving the event-related information from the first node terminal; And
Extracting the composite content ID from the event-related information, accessing a first node terminal storing the composite content corresponding to the composite content ID in the content distribution management system, and the composite content from the accessed first node terminal Content distribution management system, including a metadata management module that extracts and stores the basic metadata and extended metadata, respectively, from the basic metadata folder and the extended metadata folder.
One or more processors, and
A computing device comprising a first node terminal of a content distribution management system, comprising a memory for storing one or more programs executed by the one or more processors,
A content structuring module configured to tree-structure content to generate complex content, generate a complex content ID that can uniquely identify the complex content, and register the generated complex content; And
And an event transmission module for transmitting event-related information including the composite content ID to a second node terminal of the content distribution management system when an event for the composite content occurs in the computing device.
One or more processors, and
A computing device comprising a memory for storing one or more programs executed by the one or more processors, and constituting a second node terminal of a content distribution management system,
An event receiving module for receiving event-related information including a composite content ID of a composite content having a tree structured content from a first node terminal of the content distribution management system; And
Extracting the composite content ID from the event-related information, accessing a first node terminal storing the composite content corresponding to the composite content ID in the content distribution management system, and the composite content from the accessed first node terminal Computing device comprising a metadata management module for extracting and storing the basic metadata and extended metadata, respectively, from the basic metadata folder and the extended metadata folder.

Images