Method for describing media assets for their management

[0002] This application claims the benefit of Provisional Application No. 60/117,645, filed Jan. 28, 1999.

[0003] The present invention relates to a method and process for uniformly describing media assets, such as video, images, graphics, text, and audio, such that a multiplicity of tools used for production, approval, inventory, sales, rights management and other media management processes, can easily interoperate against a uniform view of a consistent set of media repositories.

[0004] A large number of businesses have media as a critical component. Media companies such as television studios, networks, multimedia and Internet publishing have media assets as their primary product. Advertising companies use media as their service delivery vehicle. Companies that are not in the media business also need to manage media assets from training videos to promotional literature.

[0005] A plethora of tools, processes and people are involved in the production, management, search, sales, and distribution of the media assets of a company. Media assets get fragmented across different systems because different tools and different departments handle different processes. Furthermore, there is a strong interoperability problem as these tools and departments often use different description schemes for the media assets. Thus, managing media assets is an important and difficult problem.

[0006] A standard description scheme for managing media assets will benefit a large number of industries that manage media as a direct or indirect part of their business. It will benefit the tools and processes used for managing media assets by allowing them to interact based on a shared standard description scheme.

[0007] A number of different tools and processes are used during the lifecycle of a media asset. For example, for a video asset, one tool is used for editing the video, another for logging it into the Digital Library, another for searching videos in the library, another for tracking the approval workflow, and possibly another for version control. A common description scheme for the media asset and its management information would ensure that these tools could use data generated by other tools, and in turn generate data that other tools could use. This would allow interoperability across different task specific tools on the same media assets which are stored in a common media repository.

[0008] In an advertising agency scenario, for a particular promotional effort, a number of media assets may need to be created and managed. The media assets could be videos for television, audio for radio commercials, and photographs, graphics and text for print advertisements. Different departments, such as print and video, may need to look at other material so as to maintain a common theme. An account manager may need to keep track of the progress on the media assets across the different departments. This manager may have access to view media asset collections for other advertisement campaigns, but the customer may be allowed to view only the assets related to his campaign. A description scheme for managing a logical collection of media assets and access to same would be very useful in these tasks.

[0009] It is, therefore, an object of the present invention to provide a standard description scheme for media assets.

[0010] It is another object of the invention to access a Digital Library comprising a centralized repository of media assets using a standard description scheme.

[0011] Yet another object of the invention is to provide a self-describing media asset description scheme such that a variety of different tools and users can access relevant information about a media asset from the single description.

[0012] Still another object of the invention is to provide a standard media asset description scheme which can be integrated into existing media handling tools and processes in order to standardize not only the storage access but also the local descriptions of media assets.

[0013] The foregoing and other objects are realized by the present invention which comprises a two-pronged solution: (1) a Digital Library to provide a centralized repository of the media assets and (2) a standard description scheme that will allow interoperation of a variety of tools and processes required for managing media assets. In the invention, a description scheme is provided that addresses information needed for managing media assets independent of their type. In addition, the invention provides a description scheme for logical collections of media assets. The media asset management description scheme may be based on eXtensible Markup Language (XML), to ensure maximum interoperability.

[0014] The invention will now be descried in greater detail with specific reference to the appended drawings wherein:

[0015] FIG. 1 provides a representative illustration of a prior art media asset system;

[0016] FIG. 2 provides a representative description scheme for a media asset in accordance with the present invention, including a detailed representation of the management information which can be stored as part of the inventive description scheme;

[0017] FIG. 3 illustrates a more detailed description hierarchy for content as part of the inventive description scheme

[0018] FIG. 4 provides a representative illustration of a media asset management system in accordance with the present invention;

[0019] FIG. 5 provides an illustration of an alternative embodiment of a media asset management system in accordance with the present invention; and

[0020] FIG. 6 provides a representative process flow in accordance with the present invention.

[0021] This invention proposes self-describing schemes for media assets. A media asset description is composed of (1) a description of a hierarchy of multi-modal, multi-resolution versions of the media content and (2) a description of the information critical to managing and administering media assets. Furthermore, the description provides for describing collections of such media assets and the information required for managing them as logical entities. To handle specific media types, existing description schemes for those types, for example for the description of individual image/video documents, can be imported. The descriptions are preferably defined using the eXtensible Markup Language (XML) to ensure maximum interoperability and flexibility.

[0022] The invention comprises a Description Scheme (hereinafter “DS”) for organizing, tracking, searching, managing and administering media assets stored in Digital Libraries. The DS will be useful for media based businesses in their media processes including production, inventory, workflow, sales, rights management and access control. This DS describes both individual media items, and logical collections of media assets. The proposed description schemes for content descriptions of multimedia archives are self-describing in the sense that they combine the data and the structure of the data in the same format using XML (eXtensible Markup Language). The advantages of such descriptions include flexibility, easy validation, and efficient exchange.

[0023] As depicted in FIG. 1, a prior art media asset management system was comprised of a plurality of independent media asset processing tools, 110, 112 and 114, each of which independently accessed the media assets from repositories 111, 113 and 115 respectively, for processing thereof The video processing tool at 110 would retrieve and store the video from repository 111, with no interaction, for example, with the output of the print media processing tool 114 which was stored at 115. Similarly, any approval processing by, for example, a legal department with tools at 112 would not be coordinated with, nor be cross-referenced to, the stored video (at 111) or print (at 115) versions of the related media assets. The shortcomings of the foregoing system have been discussed in the Background section above.

[0024] What is preferable, and what is the subject of the present invention is a description scheme which allows all relevant tools to locate the asset, identify the asset, and store relevant information about the asset for use by other tools. As shown in FIG. 2, the media asset 200 description element includes not only a content, element 205 which describes the media item or collection of media assets (215), but also a management element 210 containing data required for managing the media asset. The management information 210 is shown in greater detail with specific references to a video asset. It is to be understood that the inventive Description Scheme can be applied to media assets other than a video asset; but, that the video asset is featured for ease and completeness of the description of invention.

[0025] Relevant management information consists of identification related metadata 260, workflow related information 240 and possible textual information/annotations 254. The identification metadata may consist of ID 264, titles 266, access control information 268 and rights, such as copyright information at 264. The workflow information keeps track of the parties that have worked on or with the asset (person 242), what has been done (job 244) and when (version 250 comprising time 252 and annotations 254). Some examples of management related metadata which may be incorporated are included below:

[0026] Asset Identifier

[0027] Asset Type—correspond to MIME type/subtype pairs

[0028] Descriptive name

[0029] Language of text entries

[0030] Textual Description

[0031] Version

[0032] Creation Date

[0033] Creator

[0034] Owner

[0035] Access List

[0036] List of all allowable operations on the asset

[0037] Users allowed access to asset

[0038] List of allowed operations per user

[0039] Modification History

[0040] Who

[0041] When

[0042] Why?

[0043] Thumbnail/Icon associated with asset (for graphical representation)

[0044] Intellectual Rights Information

[0045] Bought or sold

[0046] Markets covered

[0047] Languages covered

[0048] Time periods covered

[0049] Currencies covered

[0050] Exclusive/Non-exclusive license

[0051] Exceptions

[0052] Containing product type or package

[0053] Financial arrangements

[0054] Royalty calculation

[0055] Audit trail of contract revisions

[0056] Participants, such as agents, owners, and creators

[0057] Royalty considerations per participant

[0058] Gross/net, with/without profit participation, varying rates for different uses

[0059] License Status, e.g., owned and sold, owned and unsold, etc.

[0060] Workflow Information

[0061] Index State

[0062] Index Attributes, i.e., data attributes indexed

[0063] Synchronization

[0064] Lock

[0065] Lock holder

[0066] Waiting List

[0067] Content Distribution Information ?

[0068] Distribution media, e.g., satellite, wireless microwave, etc.

[0069] Target locations and location groups

[0070] As shown in FIG. 3, the Content 370 can be an individual media item 375, such as an image or video, or a composite media item 385, such as a multimedia document, MPEG-4, or InfoPyramid, or a collection of such items 380. Each media item has associated metadata 390 that describes formats, storage information, size, etc. Where existing description schemes and descriptors have been established for specific media items (e.g., as adopted by MPEG-7), those existing descriptions can be imported into the inventive description scheme.

[0071] FIG. 4 provides a representative illustration of a media asset management system in accordance with one embodiment of the present invention. As depicted therein, a media asset management system 400 uses the media asset management description scheme 450. There are a number of different software systems or tools used in the media asset production, development, management and distribution lifecycle. For example, the media processing tools could include a video editing tool 402, a video library 403 for providing searching relative to the asset, an approval process workflow system 404, and a rights manager 409 for managing the rights associated with the media component. Each of the media processing tools potentially uses a different description scheme for the media asset. One reason is that the media asset processing products are often made by different vendors. Another reason is that different tools need to address sets of media asset attributes that do not overlap (e.g., the video editing tool would store the parameters used for a special effect, while the rights management tools has no requirement for a special effects media attribute). However, the name of the editor and the dates on which edits were made, along with the ID of the video asset on which edits were made, would be useful information across the video editing tool, the video library, the approval workflow tool and the rights manager. The media properties that are described by the inventive DS 450 are preferably those which are common to more than one tool.

[0072] Under the inventive system, all media assets are stored in a central repository 480 which may include a plurality of relational databases 482, 484 and 486. The media properties that ate described by a tool, and are covered by the DS are converted, or mapped by 432, 433, 434, 435 and 439, between the native descriptions used by the tool and the DS. For those media properties which are specific to a particular media tool and of no utility to other tools, however, the properties can be sent directly to the media repository, without mapping through the DS. For example, for the video editing tool 402, the parameters for a special effect would be stored directly in the video media repository, along line 415, while the identity of the video item, the editor, the time of the edits, etc, would be mapped by the mapping software 432 to the DS 450. There are a number of known ways to map between two different data representation schemes, such as that detailed in co-pending patent application Ser. No. 09/235,793, (YO998-407) filed Jan. 22, 1999 and entitled “Data Representation Schema Translation Through Shared Examples”. As the mapping is not a part of the present invention, no further detail need be provided at this time.

[0073] FIG. 5 provides an illustration of an alternative embodiment of a media asset management system in accordance with the present invention. Since the inventive description scheme will provide innumerable benefits for the management of a media asset, it is envisioned that the media asset tools, 502-509, in the future will be modified to directly provide output to the repository 580 which identifies and describes the media asset in accordance with the description scheme. As such, the mapping component and step would no longer be necessary.

[0074] Below, a possible rendition of a video media asset using XML is detailed.

[0075] <media-asset id=“X12AZ3”> <!—media asset #X12AZ3 —>

[0076] <!—Media content—>

[0077] <content> <!—InfoPyramid—>

[0078] <IP:video-ip> <!—video InfoPyramid—>

[0079] <video fidelity=“1.0”>

[0080] <source location=“URL”>foo.com/xyz.mp2</source>

[0081] <encoding>MPEG-2</encoding>

[0082] <duration>00:12:34::12</duration>

[0083] </video>

[0084] <video fidelity=“0.5”>

[0085] <source location=“URL”>foo.com/xyz.mp1</source>

[0086] <encoding>MPEG-1</encoding>

[0087] <duration>00:12:34:12</duration>

[0088] </video>

[0089] </IP:video>

[0090] <IP:image-ip>

[0091] <COL:image type=“sequence”> <!—the key-frames described in the collection DS. [4]—>

[0092] </IP:image-ip>

[0093] . . .

[0094] </content>

[0095] <!—Meta-data for media asset management—>

[0096] <management>

[0097] <acl>

[0098] <person role=“owner”>

[0099] <name>Joe B. Editor</name>

[0100] <rights>read write</rights>

[0101] </person>

[0102] <person role=“reviewer”>

[0103] <rights>annotate</rights>

[0104] </person>

[0105] . . .

[0106] </acl>

[0107] <version-control>

[0108] <version number=“1.0”>

[0109] <name>Jane Doe</name>

[0110] <task>edit</task>

[0111] <tool>Avid</tool>

[0112] <time>01/01/99 12:30 pm</time>

[0113] <note>The initial cut</note>

[0114] </version>

[0115] . . .

[0116] </version-control>

[0117] . . .

[0118] </media-asset>

[0119] The description scheme can also deal with collections of media assets. These collections are of a variety of types, for example (1) a sequence of video assets which (together with an edit decision list) are used create a new video asset; (2) different versions of a media assets where the content represented as a sequence, or, (3) a bag or unordered collection of media assets for an advertisement campaign. In describing collections, the media asset content element is composed of a collection item. The DDL may define standard ways of defining such collections.

[0120] <media-asset>

[0121] <content>

[0122] <sequence>

[0123] <version idref=“X12AZ3”number“1.0”>

[0124] <note>The original cut</note>

[0125] </version>

[0126] . . .

[0127] <sequence>

[0128] . . .

[0129] </content>

[0130] . . .

[0131] </media-asset>

[0132] In summary, the content description element is composed of a media element, or an InfoPyramid element or a collection element.

[0133] Media asset management is an important activity for a number of businesses. The Media Asset Management DS allows multiple tools and systems to inter-operate on shared media repositories. It leverages various DS and D for description of the content of the media asset and adds information needed for its management. The invention has been described with specific reference to preferred embodiments. One having skill in the art will realize that modifications can be made without departing from the spririt and scope as set forth in the appended claims.