KR100809641B1 - Method for exchanging contents between heterogeneous system and contents management system for performing the method - Google Patents

Abstract

The present invention discloses a method for exchanging content between heterogeneous systems and a content management system for performing the method. According to an embodiment of the present invention, there is provided a method for exchanging content between heterogeneous systems, the method comprising: receiving a content request including transmission scheme identification information from a content requesting device; And transmitting the metadata to a separate wrapper separate from the content so as to correspond to the transmission method identification information to the content requesting device, or generating and transmitting the metadata as a single integrated wrapper. A content exchange method is provided. Accordingly, the present invention can provide a metadata scheme that can be provided both as an integrated wrapper integrated with the content and a separate wrapper separate from the content so that the metadata can be transmitted in a manner corresponding to the system that requested the content during the content exchange. There is.

Metadata, content, MXF, wrapper, XML

Description

Method for exchanging contents between heterogeneous system and contents management system for performing the method}

1 is a schematic diagram showing an overall system for content exchange between heterogeneous systems according to an embodiment of the present invention.

2 illustrates content exchange using an integrated wrapper in accordance with a preferred embodiment of the present invention.

3 illustrates content exchange using a separate wrapper in accordance with a preferred embodiment of the present invention.

4 is a diagram illustrating a configuration of a content management system for exchanging content according to an exemplary embodiment of the present invention.

5-10 illustrate metadata in accordance with a preferred embodiment of the present invention.

11 is a view showing a wrapper generation example according to a metadata scheme according to an embodiment of the present invention.

12 illustrates a method of wrapping metadata in an integrated wrapper in accordance with one preferred embodiment of the present invention.

13-16 illustrate an example of XML used as a separate wrapper in accordance with a preferred embodiment of the present invention.

17 is a diagram illustrating a process of requesting and providing a download of content between systems according to an exemplary embodiment of the present invention.

18 is a diagram illustrating a process of requesting and approving uploading of content between systems according to an exemplary embodiment of the present invention.

19 illustrates an exchange request information structure according to an embodiment of the present invention.

20 illustrates an exchange result information structure according to an embodiment of the present invention.

21 is a diagram illustrating an exchange request approval information structure according to an embodiment of the present invention.

The present invention relates to content exchange, and more particularly, to a content exchange method between heterogeneous systems and a content management system performing the method.

Recently, various contents such as texts, images, and videos are provided. Recently, the importance of effective contents exchange and access has been emphasized as the network has been widely distributed and the use of various contents such as texts, images, and videos is increasing. To this end, when a content management system (CMS) stores content, metadata for the content is stored in a database. The use of such metadata is not only an advantage of facilitating the retrieval of specific content desired by the user, but also helps in the systematic management of vast and diverse contents and utilization of the contents. However, since content is created and managed by geographically separated departments or organizations on a content management system based on its own database scheme, the exchange of content is dependent on the management environment of the specific content management system and the mutual information exchange. Difficult to operate As a result, a standard of metadata called SMPTE (Society of Motion Pictures and Television Engineers) has been established, but in reality, local content metadata schemes are used, which are similar but vary slightly to suit the system.

An example of a representative content management system using content metadata is a broadcasting system, which manages broadcasting-related contents, and stores contents and metadata stored in-house or received from another system, and is managed by general users or other contents. When specific information is requested from the system, it retrieves and provides information that matches the condition from its database.

However, since most current content management systems use different metadata schemes and data transmission methods, a uniform metadata scheme and transmission method must be established in order to exchange content between two heterogeneous systems. If there are a plurality of content management systems using different exchange methods, and in order to exchange content between them, each content management system must be able to accommodate an exchange method according to another content management system. This not only causes the complexity of the system, but also makes it difficult to effectively exchange contents, and it is difficult to effectively utilize contents due to different metadata schemes.

In addition, in recent years, an effective method of transmitting content and metadata using a single integrated wrapper such as the Material Exchange Format (MXF) has been provided. However, the integrated wrapper is based on different metadata schemes used in each system. Different methods can be used to generate the problem, so there is still a problem with the use of metadata. In addition, there are cases where a system cannot process content and metadata received through an integrated wrapper. Therefore, there is a case where the content and the metadata need to be transmitted as separate files (separated wrappers). In this case, the metadata structures transmitted through the integrated wrappers and the separate wrappers are different from each other. There is a problem in that metadata having different structures for content is produced.

Accordingly, the present invention has been made to solve the above-described problem, and the method and method for exchanging content between heterogeneous systems that can provide a metadata scheme that facilitates the utilization of the received content in the content exchange The purpose is to provide a content management system.

In addition, the present invention can provide a heterogeneous metadata scheme that can be provided as both an integrated wrapper integrated with the content and a separate wrapper separate from the content, so that the metadata can be transmitted in a manner corresponding to the system that requested the content when the content is exchanged. Another object is to provide a method for exchanging content between systems and a content management system for performing the method.

In addition, the present invention provides a method for exchanging content between heterogeneous systems that can generate a plurality of unit metadata of a hierarchical structure and a single integrated wrapper or a separate wrapper for efficient use of the content and the content to perform the method Another purpose is to provide a management system.

In addition, the present invention performs a method and method for exchanging content between heterogeneous systems that can provide a transmission environment that can exchange the content storage file or a portion of the file, to enable more sophisticated content exchange and utilization of the content exchange Its purpose is to provide a content management system.

Other objects of the present invention will become more apparent through the preferred embodiments described below.

According to a first aspect of the present invention for achieving the above object, a method for exchanging content between heterogeneous systems, the method comprising: receiving a content request including transmission scheme identification information from a content requesting device; And transmitting metadata to a separate wrapper separate from content, or generating and transmitting the metadata as one integrated wrapper with the content so as to correspond to the transmission method identification information to the content requesting device. Provided are a method for exchanging content between heterogeneous systems, and a content management system for performing the method.

The metadata may be configured in a program unit, a storage file unit, and a scene unit.

According to a second aspect of the present invention, there is provided a method for exchanging content between heterogeneous systems, the method comprising: receiving a request for content including transmission unit information from the content requesting device; And generating and transmitting metadata formed of a program unit, a storage file unit, and a scene unit corresponding to the content as one integrated wrapper or the separate wrapper. There is provided a method of exchanging content between heterogeneous systems and a content management system performing the method, wherein the scene-based metadata transmits some or all of the metadata corresponding to the transmission unit information.

Here, the integrated wrapper in the first and second aspects of the present invention may be a material exchange format (MXF).

In addition, when transmitted to the separate wrapper, the metadata may be XML.

In addition, the separate wrapper or integrated wrapper may be transmitted using any one of TCP / IP and FTP.

According to a third aspect of the present invention, in a method for exchanging content between heterogeneous systems, metadata corresponding to metadata, including one or more of a program unit, a storage file unit, and a scene unit corresponding to the requested content, is included. Generating with one integrated wrapper; And transmitting the integrated wrapper to the content requesting device that has requested the content, wherein the program unit and the storage file unit are stored in a static track of the header area of the integrated wrapper, and the scene unit is stored in an event track. Provided are a method for exchanging content between heterogeneous systems, and a content management system for performing the method.

Here, the program unit may be divided into any one of broadcast, radio, record, and song.

In addition, the integrated wrapper may be an MXF, the structural metadata of the MXF stores a portion corresponding to a file structure of the storage file unit and the scene unit metadata, and the program is included in a production framework of descriptive metadata. In the unit and the clip framework, metadata describing the content content of the scene unit may be stored in the storage file unit and the scene framework.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention. In describing the drawings, similar reference numerals are used for similar elements.

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

When a component is referred to as being "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in between. Should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings, and in describing the present invention with reference to the accompanying drawings, the same or corresponding components are given the same reference numerals regardless of the reference numerals. Duplicate explanations will be omitted.

1 is a block diagram schematically showing an entire system for content exchange between heterogeneous systems according to a preferred embodiment of the present invention, Figure 2 is a view showing a content exchange using an integrated wrapper according to a preferred embodiment of the present invention 3 is a diagram illustrating content exchange using a separation wrapper according to a preferred embodiment of the present invention.

Referring to FIG. 1, in order to provide and / or receive content between two systems having different ways of managing content, a wrapper and an exchange interface for storing and transmitting content and metadata should be defined. . That is, the system receiving the content should be able to process the received wrapper to utilize the received content. According to the present invention, a wrapper transmitted and received between systems for exchanging content uses an integrated wrapper such as MXF in which content and metadata are combined, and a separate wrapper in which content and metadata are separated. In addition, when content and metadata are transmitted to the separate wrapper, the metadata is generated in an extensible markup language (XML). For example, a video file may be transmitted using an integrated wrapper, and an audio file (eg, a WAV file) may be transmitted using a separate wrapper. Of course, video files can also be sent as separate wrappers.

A case of transmitting content and metadata using the integrated wrapper is illustrated in FIG. 2, and a case of transmitting using a separate wrapper is illustrated in FIG. 3. According to an embodiment of the present invention, an integrated wrapper and a separate wrapper may be used using the same metadata scheme (a hierarchical structure of a program unit, a storage file unit, and a scene unit). In the system that receives the wrapper, if the wrapper is an integrated wrapper, the content and the metadata must be distinguished, and in the case of the separate wrapper, the metadata and the separated metadata must be recognized and used.

Referring back to FIG. 1, a switched interface uses a unified communication protocol to transmit and receive data between two systems. According to the present invention, since the content and metadata are transmitted using a defined wrapper according to the integrated wrapper and the separate wrapper using XML, a common communication protocol, which is still mainly used today, such as TCP / IP and / or FTP, is an exchange interface. Can be applied as

Hereinafter, a configuration of a content management system for exchanging content with another system will be described.

4 is a diagram illustrating a configuration of a content management system for exchanging content according to an exemplary embodiment of the present invention.

Referring to FIG. 4, the content management system 100 includes a storage 110, a wrapper generator 120, a data communicator 130, and a controller 140.

The storage unit 110 is a means for storing content and metadata, and may be implemented as a database. The metadata according to the embodiment of the present invention will be described later with reference to the related drawings (FIGS. 5 to 10).

The wrapper generation unit 120 performs a function of generating an integrated wrapper or a separate wrapper for containing and transmitting corresponding content and corresponding metadata to be transmitted to another system (hereinafter, referred to as a "content request device") that has requested the content. The wrapper generation unit 120 generates the integrated wrapper by storing the content and the metadata together in the MXF file. The separate wrapper does not generate a file separately, but transmits metadata generated in XML separately from the content, and for convenience of description, the wrapper generating unit 120 generates the separated wrapper. However, according to the present invention, the main feature of the present invention is that metadata having the same scheme can be used as an integrated wrapper and a separate wrapper. A method of generating the integrated wrapper by using the MXF by the wrapper generator 120 will be described later with reference to the related drawings (FIG. 12).

In addition, the wrapper generation unit 120 generates one file or a portion of the file and corresponding metadata as an integrated wrapper or a separate wrapper according to the transmission unit. Since the content management system 100 according to an exemplary embodiment of the present invention may provide metadata of a scene unit, not only one content file but also a part of the file may be provided together with the corresponding metadata. That is, only a part of the plurality of scene unit metadata corresponding to the requested content is provided together with the corresponding content, so that the receiving side can more efficiently use the content and the metadata.

The data communication unit 130 transmits the generated wrapper to the content requesting device. As described above, according to an embodiment of the present invention, the communication unit may transmit the wrapper using TCP / IP or FTP, and all communication protocols other than the communication protocol may be performed identically or similarly. Will become more self-evident.

When the content request device requests a content from the content request device, the control unit 140 generates the content and the corresponding metadata as a wrapper and transmits the content to the content request device to the storage unit 110, the wrapper generation unit 120, and the data communication unit ( 130). Here, the wrapper generation unit 120 does not necessarily need to be implemented in hardware, it is natural that it can be implemented in software, it may be included in the controller 140.

In addition, the controller 140 may determine whether the content request device is a device capable of processing the integrated wrapper or a device capable of processing the separate wrapper, and control the wrapper generator 120 to generate a corresponding wrapper. . That is, when the content request device requests a content, the content requesting device may provide the transmission method identification information for identifying the transmission method to the corresponding content management system 100. Accordingly, the content management system 100 may generate and transmit a wrapper of any one of an integrated wrapper and a separate wrapper through the transmission method identification information. Alternatively, the content management system 100 has a device list including information on a wrapper that can be processed by each content requesting device, so that a request for content from the content requesting device included in the device list can be performed. In this case, the corresponding wrapper method may be recognized using the device list to transmit content and metadata.

In addition, the controller 140 may determine the transmission unit of the content to be provided to the content requesting device, and control the wrapper generation unit 120 to generate the wrapper using the corresponding content and the metadata. According to an embodiment of the present invention, when a content request is made, the content requesting apparatus may transmit transmission unit information on whether one piece of content is all, part, and part. If the transmission unit is a part rather than all, the transmission unit may include a start time and a length (or end time) of the part. For example, if the entire content is an image file of one hour and includes a start time of 30 minutes and a length of 20 minutes as the transmission unit information, the content management system 100 may include a corresponding part of the corresponding content and a scene meta according to the part thereof. Metadata including only data (metadata for 30 minutes to 50 minutes) (including metadata of a program unit and a storage file unit) is provided to the content requesting device. Accordingly, the content management system 100 receiving the transmission unit information may provide the content request apparatus with all or a part of the corresponding content and metadata corresponding thereto (the scene unit metadata is only a corresponding part).

Here, the content management system 100 according to the embodiment of the present invention may further include a search means for providing a search service of the managed content, but the content search is somewhat different from the features of the present invention. Detailed description will be omitted. In addition, the content management system 100 may further include means for uploading content as well as downloading the content, and the method of downloading and uploading content is described with reference to the related drawings (FIGS. 17 and 18). It will be described later.

Hereinafter, a metadata scheme for easily utilizing content according to an embodiment of the present invention will be described.

5 to 10 illustrate metadata according to a preferred embodiment of the present invention.

 The metadata according to the embodiment of the present invention has a hierarchical structure and is composed of a program unit, a storage file unit, and a scene unit.

5 to 8 illustrate examples of metadata of a program unit. The metadata shown in FIG. 5 is an example of metadata according to a TV program. That is, when the corresponding content is a TV program, the metadata may provide various information about the corresponding TV program, including items about a title, genre, broadcast date, performer, and the like. An example of metadata according to a radio program is shown in FIG. 6. 5 and 6, only the presence or absence of a 'clean picture' item is shown in the difference between the metadata according to the radio program and the metadata according to the TV program. Naturally, different items may exist depending on the property.

FIG. 7 is a song, and FIG. 8 is an example of metadata according to a record. That is, metadata may be produced to correspond to not only TV broadcasts and radio broadcasts but also contents according to songs and recordings.

Accordingly, according to an embodiment of the present invention, metadata may be generated by distinguishing between a broadcast program and a radio program, and metadata may be generated according to a record and a song in detail, thereby providing more efficient use of content. .

An example of metadata in a storage file unit is shown in FIG. 9, and an example of metadata in a scene unit is shown in FIG. 10. The program unit illustrated in FIGS. 5 to 8 mainly has information on the content of the corresponding content, while the metadata of the storage file unit shown in FIG. 9 has information on a file such as a file name, a file length, etc. of the corresponding content. . The file wrapper format MXF shown in FIG. 9 is an example, and of course, it may be generated in XML.

In addition, the metadata in a scene unit has more detailed information of content in units of segments. That is, as shown in the figure, the metadata of a scene unit may have a detailed description of a part (start time is specified) of the entire contents of the corresponding content. Accordingly, more efficient utilization of content may be provided through scene-level metadata.

The metadata scheme according to the embodiment of the present invention may be displayed by applying the SMPTE (Society of Motion Pictures and Television Engineers) standard. SMPTE standard metadata is divided into descriptive metadata (DM) and structural metadata (SM) according to content characteristics and has different characteristics. Descriptive metadata (DM) have information related to the content content, it is composed of a framework (Framework) that can describe the content content in a specific unit. The framework may be classified into a production framework in a program unit, a clip framework in a storage file unit, and a scene framework in a scene unit. Each framework consists of metadata sets, which are a collection of similar metadata items.

The structural metadata SM has media information and information related to the content organization (eg, clips, segments, scenes, etc. constituting the content).

As mentioned above, metadata represented according to the SMPTE standard is stored and exchanged in standard wrappers such as MXF or XML.

11 is a diagram illustrating an example of creating a wrapper according to a metadata scheme according to an exemplary embodiment of the present invention, and FIG. 12 is a method of wrapping metadata into an integrated wrapper according to an exemplary embodiment of the present invention. 13 to 16 are diagrams showing an example of XML used as a separate wrapper according to a preferred embodiment of the present invention.

Referring to FIG. 11, when metadata is generated as XML, a coding method according to each unit is illustrated. In addition, as shown in the drawing, when generating with an integrated wrapper such as MXF, the structured metadata stores the storage file unit metadata and the segment unit metadata, and the descriptive metadata is stored in the production framework. The storage file unit metadata is stored in the clip framework, and the segment (scene) unit metadata is stored in the scene framework.

Referring to FIG. 12, metadata is located in the header of the MXF file, and the DM may be represented by plugging in a static track or an event track provided by the SM. The authoring framework and the clip framework are stored in static tracks because they span the entire MXF file, and the scene framework is the starting point (specified start time, see FIG. 10) and length (see FIG. 10) of the corresponding scene of the content. Because it needs to be mapped accordingly, it can be stored in the event track. The content is stored in an essence track.

Therefore, the receiving side that has received the MXF file can obtain information about the program and the storage file of the content from the static track of the MXF file header, and can obtain scene unit information from the event track. The metadata of the unit can be used to suit the purpose.

13 through 16 illustrate examples of metadata generated by XML's separate wrappers. FIG. 13 illustrates an upper tag of an exchanged metadata scheme, FIG. 14 illustrates a metadata tag of a program unit, FIG. 15 illustrates metadata of a storage file unit, and FIG. 16 illustrates a metadata tag of a scene unit. Therefore, according to an embodiment of the present invention, the same metadata scheme, which can be wrapped with the content in an integrated wrapper such as MXF, can also be generated as a separate file separate from the content using XML and provided to another system. (That is, metadata including a program unit, a storage file unit, and a scene unit) may be provided. That is, metadata having a structure of a program unit, a storage file unit, and a scene unit can be transmitted as an integrated wrapper MXF and a separate wrapper XML, and the receiving side receives the integrated wrapper or the separate wrapper in FIGS. 5 to 10. Metadata of each unit (program unit, storage file unit, scene unit) as shown may be equally used.

17 is a diagram illustrating a process of requesting and providing a download of content between systems according to an exemplary embodiment of the present invention, and FIG. 18 is a diagram of requesting and approving uploading of content between systems according to a preferred embodiment of the present invention. 19 is a view showing a process, an exchange request information structure according to a preferred embodiment of the present invention, FIG. 20 is a view showing an exchange result information structure according to a preferred embodiment of the present invention, and FIG. 21. Is a diagram showing an exchange request approval information structure according to an embodiment of the present invention.

Referring to FIG. 17, in operation 510, the content requesting device 200 obtains content information to be downloaded. For example, the content requesting device may obtain corresponding content information through a search application provided by the content providing system 100. This is an embodiment in which the content requesting device 200 searches for arbitrary content. In addition to this, all methods of searching for arbitrary content in the content management system 100 to obtain content information may be equally applied.

In operation 520, the content requesting device 200 requests the content management system 100 to download the corresponding content. An exchange request information structure that can be used when the content request apparatus 200 requests a download is shown in FIG. 19. The exchange request information structure includes time information to indicate a transmission unit of content to be exchanged, that is, one file or part of a file.

Here, as described above, the content request apparatus 200 may transmit the transmission method identification information about the wrapper method that the content request apparatus 200 can process to the content management system 100 when the content request is made. Therefore, the content management system 100 may transmit the corresponding content and the corresponding metadata to the content requesting device 200 using one of the integrated wrapper and the separate wrapper according to the received transmission scheme identification information.

In addition, the content requesting device 200 may transmit the transmission unit information on whether to receive the entire content file or a part of the content file to the content management system 100 when the content request is made. Shall be.

Although not shown in FIG. 19, the transmission method identification information and the transmission unit information may be included in the exchange request information structure or may be transmitted as data separate from the exchange request information structure.

The content management system 100 generates the content requested in step 530 and corresponding metadata as an integrated wrapper or a separate wrapper, and transmits the content to the content requesting device 200 in step 540. In addition, the content management system 100 may transmit the transmission result to the content requesting apparatus 200, and the transmission result may be transmitted through an exchange result information structure as illustrated in FIG. 20.

Here, the content exchange according to the drawing is one embodiment, it is natural that the content request device 200 can also provide the content held by the content management system 100, the content request device 200 is one user terminal It may be.

A process of uploading arbitrary content to the content management system 100 by the content request apparatus 200 is illustrated in FIG. 18. Referring to FIG. 18, in operation 610, the content requesting apparatus 200 transmits a content upload request including content information to be uploaded to the content management system 100. Here, the content request device 200 may use an exchange request information structure when requesting a content upload. The exchange request information structure is the same as the download, and may include information about a transmission unit of content to be exchanged, that is, one file or part of a file, and a transmission scheme identification information.

In step 620, the content management system 100 transmits the approval result of the content upload using the exchange request approval information structure as shown in FIG. If the approval result is the upload approval, the content requesting device 200 uploads the corresponding content to the content management system 100 in step 630. Although not shown in the drawing, the content management system 100 may request an upload from an unauthenticated user (or device) or may reject an upload request according to content to be uploaded. For example, the content management system 100 may not approve the upload if the file format to be uploaded is not a predetermined format (MXF, XML, WAV, MPEG), or check the metadata and do not need the content. (Eg, personal video images not related to broadcasting), the upload may not be approved. Here, the content management system need not be limited to the above-described factors that determine the approval of the requested content upload, and may determine whether to approve the upload based on various criteria. Therefore, the content request device 100 in which the upload request is rejected cannot upload the corresponding content.

In operation 640, when the content requesting device 200 completes uploading, the content management system 100 transmits the result information to the content requesting device 200 using the exchange result information structure.

Here, the exchange request information structure, the result information structure, and the exchange request approval information structure are only one embodiment and are not limited thereto.

The method of the present invention as described above may be implemented in a program and stored in a computer-readable recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.).

The present invention is not limited to the above embodiments, and many variations are possible by those skilled in the art within the spirit of the present invention.

As described above, according to the present invention, a method of exchanging content between heterogeneous systems capable of providing a metadata scheme for facilitating utilization of received content when exchanging content, and a content management system performing the method may be provided. It has an effect.

In addition, the present invention can provide a metadata scheme that can be provided as both an integrated wrapper integrated with the content and a separate wrapper separate from the content, so that the metadata can be transmitted in a manner corresponding to the system that requested the content during the content exchange. There is also.

In addition, the present invention also has the effect of generating a plurality of unit metadata of a hierarchical structure with the content and one integrated wrapper or separated wrapper for efficient use of the content.

In addition, the present invention has the effect that it is possible to provide the content and the corresponding metadata in the unit of the same type of file and part of the file in the heterogeneous content management system.

Although described above with reference to a preferred embodiment of the present invention, those skilled in the art that various modifications of the present invention without departing from the spirit and scope of the invention described in the claims below And that it can be changed.

Claims (16)

In the method of exchanging content between heterogeneous systems, Receiving a content request including transmission scheme identification information from a content requesting device; And Transmitting metadata to a separate wrapper separate from content, or generating and transmitting the metadata as one integrated wrapper with the content to correspond to the transmission method identification information to the content requesting device. How to exchange content between heterogeneous systems. The method of claim 1, The metadata is a content exchange method between heterogeneous systems, characterized in that composed of a program unit, a storage file unit and a scene unit. In the method of exchanging content between heterogeneous systems, Receiving a request for a content including transmission unit information from a content requesting device; And And generating and transmitting metadata, which is configured in a program unit, a storage file unit, and a scene unit corresponding to the content, as one integrated wrapper and the separate content wrapper. The scene unit metadata may be partially or entirely transmitted to correspond to the transmission unit information. The method according to claim 1 or 3, The integrated wrapper is a content exchange method between heterogeneous systems, characterized in that the MXF (Material Exchange Format). The method according to claim 1 or 3, When transmitting to the separate wrapper, the metadata is a method of content exchange between heterogeneous systems, characterized in that the XML. The method according to claim 1 or 3, Method for exchanging content between heterogeneous systems, characterized in that for transmitting the separated wrapper or integrated wrapper using any one of TCP / IP and FTP. In the method of exchanging content between heterogeneous systems, Generating metadata including one or more of a program unit, a storage file unit, and a scene unit corresponding to the requested content into corresponding content and one integrated wrapper; And Transmitting the integrated wrapper to a content requesting device that has requested the content, The program unit and the storage file unit are stored in a static track of the header area of the integrated wrapper, and the scene unit is stored in an event track. The method of claim 7, wherein The program unit is a content exchange method between heterogeneous systems, characterized in that divided into any one of broadcast, radio, record, music. The method of claim 7, wherein The integrated wrapper is a content exchange method between heterogeneous systems, characterized in that the MXF. The method of claim 9, In the structural metadata of the MXF, a portion corresponding to a file structure of the storage file unit and the scene unit metadata is stored. Metadata describing content content of the scene unit is stored in the program unit in the production framework of the descriptive metadata, the storage file unit in the clip framework, and the scene framework. How content is exchanged. In the content management system that exchanges content with other systems, A storage unit for storing content and metadata; A data communication unit configured to receive a content request including transmission scheme identification information from the content request apparatus; And The metadata is transmitted to the content requesting device through the data communication unit as a separate wrapper separate from the content so as to correspond to the transmission method identification information, or the metadata is generated as one integrated wrapper with the content. Content management system comprising a control unit for transmitting through a communication unit. The method of claim 11, The metadata is a content management system, characterized in that composed of a program unit, a storage file unit and a scene (scene) unit. The method of claim 12, And when the transmission unit information is received from the content requesting device when the content request is received, the metadata of the scene unit is partially or entirely corresponding to the transmission unit information. In the content management system that exchanges content with other systems, A wrapper generation unit configured to generate metadata including one or more of a program unit, a storage file unit, and a scene unit corresponding to the requested content as corresponding integrated content and one integrated wrapper; And Including a data communication unit for transmitting the integrated wrapper to the content request device that requested the content, The program unit and the storage file unit are stored in the static track of the header area of the integrated wrapper, and the scene unit is stored in the event track. The method of claim 14, The integrated wrapper is MXF, The storage file unit and the scene unit are stored in the structural metadata of the MXF. The program unit is stored in a production framework of descriptive metadata, the storage file unit is stored in a clip framework, and the scene unit is stored in a scene framework. The method according to claim 11 or 14, And the data communication unit transmits or receives data using any one of TCP / IP and FTP.

Images