DESCRIPTION
COMBINED FILE FORMAT FOR DIGITAL MULTIMEDIA BROADCASTING (DMB) CONTENT, METHOD AND APPARATUS FOR HANDLING DMB
CONTENT OF THIS FORMAT
TECHNICAL FIELD
The present invention relates to a combined file format for Digital Multimedia Broadcasting (DMB) contents, and an apparatus and method for processing DMB contents of the combined file format. More particularly, the present invention relates to a combined file format for DMB contents which allows a user to automatically filter desired contents, store the desired contents and watch the contents when the user want, and enhances applicability of contents through sharing and exchanging the contents; and an apparatus and method for processing the DMB contents of the combined file format.
This work was partly supported by IT R & D program of MIC/ HTA [2006-S-082-01, "Development of Digital Multimedia Broadcasting Technology for Personalized Broadcasting"] .
BACKGROUND ART
As Digital Multimedia Broadcasting (DMB) services launch recently, an increasing number of people watch the
DMB services through portable terminals such as mobile phones, Personal Digital Assistants (PDAs), Portable
Media Players (PMPs) and so forth. DMB is a first mobile television (TV) service based on a digital radio transmission system, and it provides high-quality video, audio and auxiliary data to mobile user equipments such as in-vehicle terminals and mobile phones so that contents can be consumed in any where at any time.
Since DMB is a broadcasting service developed in consideration of mobility, contents show time is
relatively shorter than the show time of typical broadcasting service provided to fixed equipments. Thus, DMB provides more contents. This makes it hard to remember program schedules and search DMB programs with the user equipments. Therefore, it is difficult to watch desired broadcasting contents at their scheduled show time.
Also, current DMB contents are volatile contents. They are shown on mobile user equipments in real-time once and go away. Since the mobile user equipments have limited battery power and data storage, it is hard to store DMB contents and watch them later at desired time. In addition, DMB contents currently on service basically include video and audio, and an auxiliary data service using Binary Format for Scenes (BIFS) such as securities information and whether information is under preparation to be serviced as a DMB data service.
Recently, manufactures begin equipping user equipments with high-volume memories such as a 4 GB flash memory. Furthermore, a high-volume storage on a network becomes available as they are linked to a High-Speed Downlink Packet Access (HSDPA) network or a Wireless Broadband Internet (Wibro) network. It is expected that advance in DMB video compression technology will allow coding at a bit rate much lower than the current level while maintaining DMB video quality at around the current level. Thus, it is forecasted that such auxiliary data services will be developed to utilize spared channel bandwidth and provide broadcasting program information as metadata.
Meanwhile, a Moving Picture Experts Group (MPEG) standardization group is actively working on MPEG- Applications: ISO/IEC 23000 (MPEG-A), which is a goal- oriented standardization for providing standard optimized for a specific area that is different from conventional
universal standard. It took quite a long time to establish the conventional universal standard as a complete standard, and it adopted some technology after profiling. Also, the conventional universal standard is not flexible in providing standards at proper time according to the demands of the market, and its high volume complicates and limits the development of diverse application services. The MPEG-A combines some standard specifications needed for a specific service among the conventional specifications, and specifies them into one specification, which is different from the conventional standards. A standard of a format specification is referred to as a Multimedia Application Format (MAF) . Researchers are suggesting MAF technologies applied to diverse application areas. Herein, the present invention suggests a MAF for DMB technology for supporting diverse consumption forms and its application.
DISCLOSURE TECHNICAL PROBLEM
An embodiment of the present invention is directed to providing users with DMB contents by automatically filtering desired broadcasting contents, and storing them in portable DMB user equipments or prearranging to automatically store them in a remote storage through a communication network connected to the portable user equipments, getting over an idea that broadcasting contents are of one-time consumption which are shown once on the portable user equipment and then vanish. The user can watch the DMB contents at any time they wish.
Another embodiment of the present invention is directed to enhancing applicability of broadcasting contents by sharing or exchanging contents with other user equipments. Other objects and advantages of the present
invention can be understood by the following description, and become apparent with reference to the embodiments of the present invention. Also, it is obvious to those skilled in the art of the present invention that the objects and advantages of the present invention can be realized by the means as claimed and combinations thereof,
TECHNICAL SOLUTION In accordance with an aspect of the present invention, there is provided a file format for DMB contents, capable of combining into one file: a Digital Multimedia Broadcasting (DMB) content including at least one of DMB video, DMB audio, data and a combination thereof; detailed information metadata for describing detailed information of the DMB content; and protection and governance metadata for describing information on protection and governance of the DMB content.
In accordance with another aspect of the present invention, there is provided a file format for broadcasting contents, capable of combining a broadcasting content including at least one among a video content, an audio content, and a data content, detailed information metadata describing detailed information of the broadcasting content, and protection and governance metadata describing information on protection and governance of the broadcasting content into one file.
In accordance with another aspect of the present invention, there is provided a method for generating DMB content files, which includes the steps of: generating license metadata describing license information of a specific user for a DMB content including at least one among DMB video, DMB audio and data; encrypting the DMB content based on the license information; generating encryption metadata describing information on the
encryption; and combining the DMB content, the license metadata, and the encryption metadata into one file format .
In accordance with another aspect of the present invention, there is provided a method for restoring a DMB content of a combined file format capable of combining a DMB content including at least one among DMB video, DMB audio, and data, detailed information metadata describing detailed information of the DMB content, and protection and governance metadata describing information on protection and governance of the DMB content into one file, the method including the steps of: searching for or filtering a desired DMB content based on the detailed information metadata; authenticating a user or a user equipment by parsing the DMB content of the combined file format and parsing the protection and governance metadata; extracting information needed for decrypting the DMB content based on the parsed protection and governance metadata; presenting the content of the DMB content through an interface of the user terminal by parsing the detailed information metadata; and extracting, decoding, and restoring the DMB content according to a content execution command inputted from the user.
In accordance with another aspect of the present invention, there is provided a method for remotely consuming a DMB content in connection with a DMB user equipment and a DMB content providing apparatus, which includes the steps of: receiving a DMB content from the DMB content providing apparatus according to a request of the user equipment; storing the received DMB content according to a request of the user equipment; and providing the stored DMB content to the DMB user equipment according to a request of the user equipment.
ADVANTAGEOUS EFFECTS
As described above, differently from conventional DMB contents, the present invention makes users watch DMB contents by additionally providing metadata to DMB AV contents, automatically filtering desired broadcasting contents, and storing them in portable DMB user equipments or prearranging to automatically store them in a remote storage through a communication network connected to the portable user equipments. Also, since it is possible to share or exchange the contents among user equipments, the applicability of broadcasting contents increases.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 shows the relations between MAF for DMB and other MPEG File Formats.
Fig. 2 shows components of MAF for DMB in accordance with an embodiment of the present invention.
Fig. 3 shows a schema structure of TV-Anytime metadata which is a constituent element of MAF for DMB. Fig. 4 shows the single-type file structure in accordance with an embodiment of the present invention.
Fig. 5 shows a file structure for a single-type file in accordance with an embodiment of the present invention. Fig. 6 shows a file structure for a single-type file in accordance with another embodiment of the present invention.
Fig. 7 shows a file structure for a single-type file using the meta box in accordance with an embodiment of the present invention.
Fig. 8 shows a multiple type file structure in accordance with an embodiment of the present invention.
Fig. 9 shows a single-type file structure with the IPMP metadata in accordance with an embodiment of the present invention.
Fig. 10 shows a multiple type file structure with the IPMP metadata in accordance with an embodiment of the present invention.
Fig. 11 illustrates an example of package consumption in accordance with an embodiment of the present invention.
Fig. 12 shows package restoration on TV in accordance with an embodiment of the present invention.
Fig. 13 shows an example for virtual program which is reconstructed by a user with preference for tennis.
Fig. 14 shows a usage example of coupons metadata.
Fig. 15 shows a file architecture of user-creative data using a "trak" box in accordance with an embodiment of the present invention. Fig. 16 shows an architecture of a DMB system in accordance with an embodiment of the present invention.
Fig. 17 is a flowchart describing a DMB content generating method in accordance with an embodiment of the present invention. Fig. 18 is a flowchart describing a DMB content generating method in accordance with another embodiment of the present invention.
Fig. 19 is a flowchart describing a DMB content restoring method in accordance with an embodiment of the present invention.
Fig. 20 is a flowchart describing a DMB content restoring method in accordance with another embodiment of the present invention.
Fig. 21 illustrates a structure of a DMB remote consuming apparatus and how it is connected to a network in accordance with an embodiment of the present invention.
Fig. 22 is a flowchart describing a method of remotely consuming DMB contents between a DMB user equipment and a DMB content providing apparatus .
BEST MODE FOR THE INVENTION
The advantages, features and aspects of the invention will become apparent from the following description of the embodiments with reference to the accompanying drawings, which is set forth hereinafter. When detailed description on related art may obscure a point of the present invention, the description will not be provided. Hereinafter, specific embodiments of the present invention will be described with reverence to the accompanying claims.
Fig. 1 shows the relations between MAF for DMB and other MPEG File Formats. Other MPEG File Formats are based on the ISO Base Media File Formats. MAF for DMB is derived from the MPEG-4 AVC, 3GPP Timed Text Format [27], and MPEG-4 File Format.
Table 1 describes DMB service types and Table 2 shows contents types of each service.
Table 1
Table 2
Fig. 2 shows components of MAF for DMB which consists of the MPEG Standards and non-MPEG Standards. MAF for DMB includes AV contents m a current DMB service, a data service such as Broadcast Website (BWS) , and auxiliary data shown in Fig. 3 as components.
Table 3
As described in Table 1, MAF for DMB supports the various service types such as terrestrial DMB (T-DMB) and satellite DMB (S-DMB) . The individual DMB services support their main AV contents and auxiliary data. For
the T-DMB service, the specification of the main AV contents is described in ETSI TS 102 428. The S-DMB service uses the ISO/IEC 14496-10 AVC for the video content and ISO/IEC 14496-3 MPEG-4 part 3 Audio: HE-AAC v2 for the audio content. For the auxiliary data such as BWS, the supported content types are described in ETSI TS 102 428 which is the extended version of ETSI TS 101 498- 1 and 2
Herein, a term "DMB contents" denote contents including at least one among DMB video, DMB audio, and data. A term "detailed information metadata" denotes metadata describing detailed information of DMB contents, and they are mainly represented as TV-Anytime metadata shown in Table 3. A term "protection and governance metadata" denotes metadata describing information on protection and governance of DMB contents. Among the auxiliary data shown in Tables 2 and 3, those except TV- Anytime metadata, MPEG-21 IPMP, and MPEG-21 REL are data contents. "Contents of a combined file format" denotes DMB contents having a file format that can combine DMB contents including at least one among DMB video, DMB audio and data, detailed information metadata describing detailed information of the DMB contents, and protection and governance metadata describing information on protection and governance of the DMB contents into one file.
Components of MAF for DMB
The organization of contents follows MPEG-21 DID in the present invention. MPEG-21 DID (ISO/IEC 21000-2) describes a set of abstract terms and concepts to form a useful model for defining Digital Items. In the MPEG-21 multimedia framework, the digital item (DI) is a fundamental unit with a standard representation, identification and metadata for the distribution, and
transaction. For the declaration of the digital item in the flexible and general ways, MPEG-21 DID aims to standardize the description for the definition of the digital item and provides the basic structure for content representation for the DMB storage and distribution scenario .
According to the present invention, contents are created and consumed based on TV-Anytime metadata. The metadata used to describe the content is taken as a subset of the TV-Anytime metadata specification, published by ETSI and available as ETSI TS 102 822-3. Using this metadata specification and some slight modifications, the content creation and consumption information is described in XML form. The TV-Anytime metadata are sub-divided into two categories: phase 1 metadata schemas (ETSI TS 102 822-3- 1) and phase 2 metadata schemas (ETSI TS 102 822-3-3) . The phase 1 metadata schema has the root element of TVAMainType and defines mainly about program and user descriptions. The phase 2 metadata schema has the root element of ExtendedTVAMainType and extends the phase 1 schema for including various content types and consumption conditions. The structure of the TV-Anytime schemas is briefly summarized in Fig. 3. The example usage of the TV-Anytime metadata will be described below.
Protection and governance of contents is carried out based on MPEG-21 IPMP and REL. MPEG-21 IPMP
(Intellectual Property Management and Protection) is a
DRM (Digital Right Management) architecture developed by MPEG for safe and easy distribution of contents between the different user terminals and the different content providers. The MPEG-21 IPMP Components standard provides the means to signal which IPMP Tools are required to protect specific parts of a protected Digital Item, and further information required by the Peer to manage each
IPMP Tool and by the IPMP Tool to operate on protected content. For supporting governed and protected usage of DMB contents, MAF for DMB adopts a restricted subset of MPEG-21 IPMP Components.
ISO/IEC 21000-5 defines a right expression language (REL) . In MAF for DMB, licenses governing the use of content are expressed according to the DAC profile of the MPEG-21 Rights Expression Language. The following Table 4 presents profile elements defined in the REL DAC profile .
Table 4
3GPP Timed Text format describes the normative behavior of text data for rendering. Timed text supports the characters and glyphs rendering, font support such as name, size and style, color support of text and background, text rendering position and composition, etc. By using these functionalities, various applications such as closed captioning, karaoke, dynamic highlighting and other visual annotation can be deployed in the user' s terminal .
File Structure
The file format of MAF for DMB can be represented in two kinds of structures for single movie contents and multiple movie contents. The file format structure of this specification is derived from the ISO base media file format standard. The boxes used in this specification is based on a restricted set of boxes from the ISO base media file format and the MP4 File Format. Table 5 shows the structure of the employed boxes with their description. The mandatory boxes are marked with an
10 asterisk (*) .
Table 5
Fig. 4 shows the single-type file structure containing single movie presentation. This type of file structure mainly consists of ftyp, moov and mdat boxes. 5 The moov box describes the presentation of the scene in which more than one trak box are contained. The trak box contains the description for one media. A media in each trak box can be interleaved AV, individual audio and video, BIFS, and other data service contents as shown in 0 Table 2 and Figure 3. The trak box supports time information (such as edtl, stbl box) for the synchronization with other media of other trak box. The mdat box contains the real contents which are described in the trak box or the trak box may import the content by 5 URL without deposing the content in the mdat box. In Fig. 4, λ*' marks mean the mandatory boxes in the file structure .
Fig. 5 shows the primitive file structure for a single-type file. As shown in Fig. 5, BIFS and IOD/OD 0 information is not included in the file format if only the main audio and video are stored in the file.
Fig. 6 shows another file structure for a single- type file. As shown, BIFS, IOD and OD information is included with the main AV data. 5 Fig. 7 shows a file structure for a single-type file using the meta box. This file contains the BIFS associated non-main data such as caption, images, script, timed metadata, program code and private data as shown in Tables 2 and 3. The meta box mainly consists of the iloc,
iinf, ipro, xml boxes and etc. The iloc and iinf boxes contain the item_ID, length and offset for locating to an item and information such as item ID, item protection, item_name, content_type and content_encoding. The xml box can support the untimed text or binary data such as MPEG- 21 DID, IPMP, and TV Anytime. MPEG-21 DID can support the description for items.
The iloc and iinf boxes describe the location and information of each item in the mdat box. However, the structure for items in the iloc and iinf boxes is flat and has limitation to describe the items in detail. In order to support the flexibility of the file format, MPEG-21 DID can be used to describe the location and information of the items as shown in Fig. 7. The MPEG-21 DID metadata can be contained in the xml box and can contain the metadata such as IPMP, MPEG-21, and TV anytime metadata, the script and the source code in the hierarchical structure. The example of MPEG-21 DID usages can be shown below. It is possible to collect parts of diverse contents and represent them in a combined file format through segment search for important scenes using the file structure of Fig. 7. As illustrated in Fig. 7, one or more video or audio track may exist in an MPEG-4 file format in each "mdat" box. In this case, it can have another additional file structure shown in Fig. 4 that is represented as a "moov" box. Each item information representing each "trak" box of MPEG-21 DID in the "meta" box may be mapped to "iinfo" and "iloc" information in the "meta" box.
Fig. 8 shows the multiple type file structure containing multiple movie presentations. There are two layers: outer file format which consists of the ftyp, meta and mdat boxes and inner one which consists of moov, meta and mdat boxes. The directory and information of the
items in the outer and inner file format can be described by the iloc and iinf boxes and/or MPEG-21 DID metadata in the meta box. In the multiple MAF for DMB contents, item_IDs in the outer and inner iloc box are called the global item id and local item id, respectively. The global item id shall indicate the hidden moov box and the local item id shall indicate the items in each hidden moov box. MPEG-21 DID in the outer xml box contains hierarchical item structures of all hidden moov boxes. The MPEG-21 DID metadata usages for the multiple DMB contents are described below.
Hereinafter, protected file structure will be described with reference to Figs. 9 and 10. In order to signal content protection, sample description of the trak box or IPMP DIDL of the meta box can be utilized. ISO/IEC 21000-5 defines a right expression language (REL) , which is designed to be domain-agnostic and comprehensive, and also very flexible and adaptive to the specific scope and requirements of applications within a particular domain. The language provides extension and profile mechanisms for these purposes.
Through the sample description of the trak box, DMB Player can notice that the specified resource is protected. The four-character-code of the sample description is replaced with a four-character-code indicating protection encapsulation: these codes vary only by media-type. For example, λmp4v' is replaced with 'encv' and ymp4a' is replaced with 'enca' . The entry codes for protected stream are as shown in the following Table 6:
Table 6
i»e Santole-Ente
Video encv
Signaling based on MPEG-21 IPMP information will be described hereafter. Through the IPMP information carried in meta box, the protection of the resource can be signaled. The following Table 7 shows an example of the protected DID expression which can be expressed in the xml box of meta box. Using MPEG-21 IPMP DIDL expression, a Digital Item related to a resource track can be noticed as a protected into MAF for DMB player.
Table 7
Fig. 9 shows the single-type file structure with the IPMP metadata. For signalling to protect a video item, the sample description in the trak box can be used. The IPMP information is included in the xml box using MPEG-21 IPMP information scheme. The example of MPEG-21 IPMP usage will be shown below.
Fig. 10 shows the multiple type file structure with the IPMP metadata. Based on file structure for
multiple type file structure in Fig. 8, the signalling and governance information is contained in xml box within meta box.
Usage Examples of MPEG-21 DID and TV-Anytime
Hereinafter, usage examples of the MPEG-21 DID and TV-Anytime. As described in Fig. 9, this is an example of the MPEG-21 DID description which includes the element information and the location of the resources in a MAF- for-DMB file, IPMP information and their metadata of each or whole resource.
Table 8 is a DIDL expression for a clear MAF for DMB content with a video and audio stream. The video and audio resources refer to the position of the file structure, and the content description can be inserted into Descriptor in Digital item.
Table 8
<DIDL xm. rus="urn:mpeg:mpeg21: 2006: 07-DIDL-NS" xm Ins :di-;="urn:mpeg:mpeg21: 2002 :01-DII-NS"> <Container>
<Item "id="dmb_sample"> <Descriptor>
<Statement m:merl'ypc="text/plain">
<dii: Identifier>1234</dii: Identify er> </Statement> </Descriptor> <Descriptor>
<Statement m- rno'['ypo="text/xml">
<! — . M3 vuo"*' αo >, ,. '-r —> </Statement> </Descπptor> <Component io="video01">
<Resource
rof="#mp (/byte (2048, 150000) )"/>
</Component>
<Component iri="audio01">
<Resource m]nu:Typo="audio/bsac" rof="#mp (/byte (150000, 180000) ) "/>
</Component> </Item> </Contamer> </DIDL>
Table 9 is a modified DIDL expression with protection for the Table 8 example. In this example, the video stream is protected using IPMP Tool specified by IPMPInfoDescriptor, and its usage rule can be expressed 5 in license within RightsDescriptor . It shows how to signal that a resource is governed and which IPMP Tool is required in order to access. It also shows how to express IPMP Tool information and its update information
10 Table 9
< rxml veidlon "l.C" ei±cυcU:-α "UTF-'.1"V>
<DIDL xmlns="urn:mpeg:mpeg21:2006:07-DΪDL-NS" xirdns : dil="urn:mpeg:mpeg21 : 2002 : 01-DII-NS" xmIns::_nmρd±dl="urn:mpeg:mpeg21:2004 : 01-IPMPDIDL-NS" xra" no : ' pmμ :-i>fo^"urn:mpeg:mpeg21 : 2004 : 01-1PMPINFO-NS" x_τln3 : ipmμinfo- mox="urn:mpeg:mpeg21:2006: 07-IPMPINFOMSX-NS" xr lnd : i="urn:mpeg:mpeg21 : 2003 : 01-REL-R-NS" κm" ns :rr.x="urn :mpeg:mpeg21:2003: 01-REL-MX-NS" xmlnu :dsLq="http ://www. w3.org/2000/09/xmldsig#" : schemdLocdLlo:i="urn:mpeg :mpeg21 : 2002 : 02- DIDL-NS didl.xsd"> <Container>
<item ' d-"dmb_sample"> <Descriptor>
<Statement :rimeType="text/xml">
<! — -"-I; , "-J --;.ι :- -jc-yj.- -r* <>" —> </Statement> </Descriptor^ <Component id="video01">
<Resouice mimeTγρe="application/mp21-ipmp"> <ipmpdidl : ProtectedAsset mimeTγpe="video/avc> <ipmpdidl : Identifier> urn:mpegRA:mpeg21:dii:isan:006A-15FA-002B-C95F-B </ipmpdidl : Identifier> <ipmpdidl : Info>
<ipmpinfo : IPMPInfoDescriptor> <ipmpinfo : Tool>
<ipmpinfo : ToolBaseDescription>
<ipmpinfo: IPMPToolID>urn:mpeg21 : IPMPTool : ToolID: ABCDEF9</ipmpinfo: IPMPToolID>
<ipmpinfo: Remote ref="..."/>
<ipmpinfo : ConfigurationSettings> <ipmpinfo : Update> <ipmpinfo: Location ref="..."/> <ipmpinfo:ScheduledUpdateTime per Lodic="PlD">2005-03-07T00 : 00: 00
</ipmpinfo : ScheduledUpdateTime> </ipmpinfo : Update> </ipmpinfo : ConfigurationSettings> </ipmpinfo : ToolBaseDescription>
<ipmpinfo : InitializationSettings> <ipmpinfo: InitializatioriData>... </ipmpinfo : InitializationData>
</ipmpinfo : InitializdtionSettings> </ipmpinfo : Tool> <ipmpinfo : RightsDescπptor> <ipmpinfo : License> <r:license> ... </r:license> </ipmpinfo : License> </ipmpmfo : RightsDescriptor> </ipmpinfo: IPMPInfoDescriptor> </ipmpdidl : Info>
<ipmpdidl: Contents _.e£="#mp (/byte (2048, 150000) )"/> </ipmpdidl : ProtectedAsset> </Resource> </Component> <Component id="audio01">
<Resource m; meTyρe="audio/bsac" -:ef="#mp (/byte (150000, 180000) )"/> </Component> </item> </Container> </DIDL>
Table 10 shows another DIDL expression with protection for the Table 8 example. It contains protected video and audio stream and its governance information. It
5 shows how to signal using IPMPGenerallnfoDescriptor and its referring.
Table 10
/m l .Ό T\- : oi ι = " 1 . 0 ' <:od ". " σ= " i r ; H « " ?-;
<DIDL zralna="urn:mpeg:mpeg21:2006:07-DIDL-NS" xmlns:dα :="urn:mpeg:mpeg21 : 2002 : 01-DII-NS" xm.nr, : 4 pinpdi d i="urn:mpeg :mpeg21 : 2004 : 01-IPMPDIDL-NS" XHi lT-j : :Ompi nf o="urn:mpeg:mpeg21 : 2004 : 01-IPMPINFO-NS" x:r.1 ns : ipmpi nro irif x="urn:mpeg:mpeg21:2006: 07-IPMPINFOMSX-NS" x~ln?: r="urn:mpeg:mpeg21 : 2003 : 01-REL-R-NS" xm ns :r-x="urn:mpeg:mpeg21 : 2003 : 01-REL-MX-NS" xm.nr, : dsi g="http: //www. w3. org/2000/09/xmldsig#" : f choma I .or ^t i or.="urn:mpeg:mpeg21 : 2002 : 02- DIDL-NS didl.xsd"> <Container>
<xtem :d="dmb_sample"> <Descriptor>
<Statement
<! — -'•-, ,.cr'r»rJs 'y '~r'p . ,< —> </Statement> </Descriptor> <Descriptor>
<Statement r-imo'l'ypn="text/xml"> <ipmpinfo : IPMPGenerallnfoDescriptor>
<ipmpinfo : ToolList> <ipmpinfo;ToolDescription local I ;="TPABCDEF9">
<ipmpinfo:IPMPToolID>urn:ETRI:ToolPack:ToolID:ABCDEF9</ipmpinfo:IPMPToolID>
<ipmpinfo : Remote re£="http: //www.mpeg21ToolPacks . com/ToolID: ABCDEF9"/>
<ipmpinfo : ConfigurationSettings> <ipmpinfo : Update>
<ipmpinfo: Location rei="http: //www.mpeg21ToolPacks . com/ToolPackUpdate"/>
<ipmpinfo:ScheduledUpdateTime Dexiodic="PlD">2005-03-07T00 : 00 : 00 </ipmpinfo : ScheduledUpdateTime>
</ipmpinfo : Update> </ipmpinfo : ConfigurationSettings> </ipmpinfo : ToolDesciiption> </ipmpinfo : ToolList> <ipmpinfo : LicenseCollectior^
<ipmpinfo : RightsDescriptor>
<ipmpinfo: License>... </ipmpinfo: License> </ipmpinfo : RightsDescriptor> </ipmpinfo : LicenseCollection> </ipmpinfo : IPMPGenerallnfoDescriptor> </Statement> </Descriptor>
J7/iJii!isComponent, IJiP'ifllllloΦiiJiJ
<Resource m^meTγpe="application/mp21-ipmp"> <ipmpdidl : ProtectedAsset :"imeTγpe="video/avc>
<ipmpdidl : Identifier>urn:mpegRA:mpeg21 : dii : isan: 006A-15FA-002B- C95F-B</ipmpdidl : Identifier>
<ipmpdidl : Info> <ipmpinfo : IPMPInfoDescriptor> <ipmpinfo : Tool>
<ipmpinfo:ToolRef
</ipmpinfo : Tool> <ipmpinfo : RightsDescriptor> <ipmpinfo : License>
<r: license 1 Lcenseld="license idO12345"/> </ipmpinfo: License> </ipmpinfo : RightsDescriptor> </ipmpinfo: IPMPInfoDescriptor> </ipmpdidl : Info>
<ipmpdidl: Contents rei="#mp (/byte (2048, 150000) )"/> </ipmpdidl : ProtectedAsset>
</Resource> </Component>
<Resource mimeTy»e="application/mp21-ipmp"> <ipmpdidl : ProtectedAsset mimeType="audio/bsac>
<ipmpdidl : Identifier>urn:mpegRA:mpeg21 : dii : isan: 006A-15FA-002B- C95F-B</ipmpdidl: Identifiers
<ipmpdidl : Info>
<ipmpinfo : IPMPInfoDescriptor>
<ipmpinfo : Tool> <ipmpinfo:ToolRef localJdref="TPABCDEF9"/> </ipmpinfo: Tool>
<ipmpinfo : RightsDescriptor> <ipmpinfo : License>
<r : license
</r:license>
</ipmpinfo : License> </ipmpinfo : RightsDescriptor> </ipmpinfo : IPMPInfoDescriptor> </ipmpdidl : Info>
<ipmpdidl: Contents ref="#mp (/byte (150000, 180000) )"/> </ipmpdidl : ProtectedAsset>
</Resource> </Component> </item> </Container> </DIDL>
Hereinafter, examples of TV-Anytime metadata, such as EPG metadata, package metadata, usage history metadata, segment metadata, and coupons meatadata will be described.
Major application area of MAF for DMB is for storage of mobile broadcasting contents. Mobile broadcasting contents and EPG metadata for a user to search and select them could be stored in a MAF for DMB file for a next-time usage. The kinds and definitions of
10 metadata for EPG are as shown in Table 11.
Table 11
The xml instance of Table 12 shows an example of Programlnformation and Purchaselnformation. In this example, 849th Englishcafe program is included in the genre of "edudation/language study" and can be watched free when a user watch advertisements inserted at the program.
Table 12
Fig. 11 illustrates an example of package consumption according to an embodiment of the present invention, and Fig. 12 shows package restoration on TV.
In addition to audio-visual contents, various DMB contents such as image, text, applications, slide show, web page, weather information, traffic and travel information can be acquired through IP network at DMB service. Each content can be consumed by itself or can be consumed together to provide more effective consumer experiences. TV-Anytime defines Package metadata to describe characteristics and composition of such contents collections. Some examples of packaged contents include: multi-angle service of a broadcasting content, photo album service, linguistic educational content service which may consist of main video and additional contents such as today' s expression, scripts of one' s native and foreign language, textual data for structure and vocabulary, and dictionary, etc.
Package metadata also provide a mechanism expressing options for consumption depending on usage environment (device) and user preference (user) . Then the targeting service, which is defined as automatic matching and delivering relevant content to profiled consumers, could be possible. Additionally, package metadata describes synchronization (temporal) and spatial information between content to allow content to be consumed as the service provider intended. Owing to synchronization information, multi-stream experience
(e.g., multi-camera sports, or alternate audio and video documentaries) can be provided with content packaging. The xml instance of the following Table 13 shows an example of Package metadata. In this example, a movie about the world best jazz signer, "Ray Charles" and its scripts are used as materials for English Study.
Table 13
</Item>
As user-creative DMB contents, a user can add his or her usage history for next-time usage. That is, if information describing which contents are already watched is stored with the contents, he can resume consuming the contents from the point of last consumption at any time. For this purpose, usage history metadata of TV-Anytime is used. Usage history metadata describes audio-visual content consumption history of a user as a list of actions performed over an observation period. The xml instance of the following Table 14 shows an example of usage history metadata. In this example, "Userl" consumed the content identified by the ID, "crid: //www. ebs . co . kr/englishcafe_849" for 15 minutes from the start of the contents.
Table 14
</ϋ§,ageHisi;©ry> '""
«F
As user-creative DMB contents, a user can also add his bookmark for next-time usage. That is, if bookmark information is stored with the contents, he can selectively consume the contents by just navigating his favourite bookmarked items or segments. (A segment is a continuous portion of a piece of content.) For this purpose, segmentation metadata of TV-Anytime is used. Segmentation metadata describe a segment or groups of segments. Segment metadata make it possible to repurpose programs, for example, video highlight, bookmark, and virtual program. Fig. 13 shows an example for virtual program which is reconstructed by a user with preference for tennis. The xml instance of the following Table 15 shows an example of segment metadata which describes a segment group of bookmarks type.
Table 15
Coupons metadata provides the way to signal the existence of coupon, to explain the coupon, and to signal the method to retrieve the coupon. MAF for DMB users may store the coupons with the associated contents and may
retrieve and use them at any time. Fig. 14 presents a usage example of coupons metadata.
Usage Example of User-Creative Data
In order to offer personalized DMB content consumption, MAF for DMB can wrap user-creative data such as graphics, texts, images, audio, and video in the trak box with the spatio-temporal representation of main DMB A/V contents. The representation is performed by a part of Core2D profile of BIFS. As shown in the following Table 16, the user-creative data is classified into the five types and should need the representation information by BIFS. The Table 16 shows the BIFS information of the user-creative data as a form of XMT.
Table 16
Graphic geometry, LineProperties par
Image geometry, translation, ESJD par
Video geometry, translation, ESJD par
Audio ES ID par
Text geometry, translation, ESJD par
In the Table 16 above, each type of user-creative data has spatial and temporal information. The temporal information is described via "par" node in XMT. "LineProperties" denotes color (e.g., RGB) of "Graphic" data, and "geometry" makes the shape of visual data (In this case, line, rectangle, and ellipse are used for
user-creative data.)- "translation" describes the location of visual data on the screen, in other words, it enables to display the user-creative data relative to main DMB A/V content. "ES_ID" represents the index of trak referred by the user-creative data except "Graphic" data .
The user-creative MAF for DMB content is encapsulated by two types of the file format. As shown in Fig. 22, the user-creative data is included in the trak and the mdat box which have media information and real stream of the data, respectively. However, "Graphic" can be directly expressed by only spatial and temporal information of BIFS stream. On the other hand, BIFS of remaining data types (e.g., text, image, audio, and video) should refer real streams of the embedded resources in the file format by using the trak. Consequently, the user-creative data (except "Graphic") in mdat box can be referred via trak box of MAF for DMB file format. Bifs track describes spatio-temporal information of user-creative data. As mentioned previously, "Graphic" data has no referencing resource, so that it can be described via bifs track only. As the other types of user-creative data refer the embedded resources, trak boxes wrap media information on real streams of user- creative data.
Fig. 15 shows a file architecture of user-creative data using a "trak" box in accordance with an embodiment of the present invention.
Specifying the Player' s Behavior
For the easy and convenient consumption of multiple MAF for DMB contents, the MAF for DMB content provider or author can define the player's behavior. The examples of the player' s behavior by the MAF for DMB
content provider or the author as follows:
1. The MAF for DMB content provider can include the single MAF for DMB contents for the advertisement and they want to play it periodically or mandatory. 2. When a user plays the multiple MAF for DMB contents, the player can show the single MAF for DMB content list at first or play the first MAF for DMB content automatically
3. For the better communication or understanding, the author can control the single MAF for DMB content in the multiple MAF for DMB content file.
Usage of MPEG-21 IPMP Components
The following sub-clauses specify the normative set of the required IPMP Components elements for MAF for DMB.
The IPMP tool set for MAF for DMB is a subset of MPEG-21 IPMP Components. The selection criterion on this tool set is based on the specific application domain of Digital Multimedia Broadcasting.
1. Most of the target terminals are to be the hand-held devices of Digital Multimedia Broadcasting.
2. The selected IPMP tools should be useful and applicable for MAF for DMB services on such devices.
3. For crystal-clear and easy implementation, some ambiguous tool elements, e.g. the elements with any type should be more specifically defined.
To maintain the full capability to express the protected Digital Item, the IPMP tool set for MAF for DMB shall include all the elements in the IPMP DIDL schema of
MPEG-21 IPMP Components. IPMP Information Descriptors in
MAF for DMB includes the subset of IPMP Information
Descriptor schema in MPEG-21 IPMP Components standard. The selected elements with restrictions are as shown in Table 17.
Table 17
In Table 17, The ipmpinfo : RightsDescriptor element is used for containing rights information that governs the IPMP information. The ipmpinfo : RightsDescriptor element under the ipmpinfo: Tool element is for each IPMP Tool. The common rights information about all tools in ipmpinfo : IPMPInfoDescriptor can be expressed by the ipmpinfo : RightsDescriptor under the ipmpinfo : IPMPInfoDescriptor . IPMP General Information Descriptors in MAF for DMB are composed of a subset of MPEG-21 IPMP Information Descriptor schema m MPEG-21 IPMP Components and MPEG-A Media Streaming Player application format. The selected elements with restrictions are tabulated as shown in Table 18. Table 19 presents IPMP information schema.
Table 18
Element/Child Element Restrictions on MPEG-21 IPMP ipmpinfo : IPMPGenerallnf oDescriptor | As defined in 8.3.1 of the standard
Table 19
<'xml version=" 1 . 0 " ?>
<schema xmlns="http: //www.w3. org/2001/XMLSchema" xmlns : ipmpmfo="urn:mpeg:mpeg21 : 2004 : 01-IPMPINFO-NS" xmlns : ipmpinfo- msx="urn:mpeg :mpeg21 : 2006 : 10-IPMPINFO-MSX-NS" xmlns : dn="urn :mpeg :mpeg21 :2002:01-DII-NS" xmlns : r="urn:mpeg:mpeg21 : 2003 : 01-
REL-R-NS" xmlns :dsig="http: //www. w3. org/2000/09/xmldsig#" targetNamespace="urn:mpeg:mpeg21:2004: 01-IPMPINFO-NS" elementFormDefault="qualified" attributeFormDefault="unqualified" version="0.01">
<import namespace="http: //www. w3. org/2000/09/xmldsig#"
schemaLocation="http://www. w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig- core-schema. xsd"/>
<import namespace="urn :mpeg:mpeg21 : 2003 : 01-REL-R-NS" schemaLocation="rel-r_IS.xsd"/> <import namespace="urn:mpeg:mpeg21 : 2002 : 01-DII-NS" schemaLocation="dii .xsd"/>
<element name="IPMPInfoDescriptor" tγpe="ipmpmfo: IPMPInfoDescriptorType"/>
<complexTγpe name="IPMPInfoDescriptorType"> <annotation>
<documentation>The RightsDescriptor under this element is applied to the associated asset</documentation> </annotation> <sequence> <element ref="ipmpmfo: Tool" minOccurs="0" maxOccurs="unbounded"/>
<element ref="ipmpmfo : RightsDescriptor" mmOccurs="0" maxOccurS="unbounded" />
<element ref="dsig: Signature" mmOccurs="0"/> </sequence>
</complexType>
<element name="Tool" type="ipmpinfo:ToolType"/> <complexType name="ToolType">
<complexContent> <restπction base="ipmpmfo: ToolType">
<sequence>
<element ref="ipmpinfo : ToolRef"/> <element ref="ipmpmfo: InitializationSettmgs" mmOccurs="0"/> <element ref="ipmpmfo: RightsDescriptor" minOccurs="0"/>
<element ref="dsig: Signature" mmOccurs="0"/>
</sequence> <attribute name="order"
type="positiveInteger"/>
</restriction> </complexContent> </complexType> <element name="ToolRef" type="ipmpinfo: ToolRef"/>
<complexType name="ToolRef">
<attribute name="localidref" type="IDREF" use="required"/> </complexType>
<element name="IPMPToolID" type="anyURI"/> <element name="Inline" type="ipmpinfo: InlineType"/> <complexType name="InlineType"> <sequence>
<element ref="ipmpinfo:Binary"/> <element ref="dsig: Signature" minOccurs="0"/> </sequence>
</complexType>
<element name="Binary" type="base64Binary"/> <element name="Remote" type="ipmpinfo: RemoteType"/> <complexType name="RemoteType"> <sequence>
<element ref="dsig: Signature" minOccurs="0"/> </sequence>
<attribute name="ref" type="anyURI"/> </complexType> <element name="ConfigurationSettings" type="ipinpinfo : ConfigurationSettingsType"/>
<complexType name="ConfigurationSettingsType" mixed="true"> <sequence>
<element ref="ipmpinfo: Configuration"/> <element ref="ipmpinfo: Update" minOccurs="0"/>
</sequence> </complexType>
<element name="Configuration" type="ipmpinfo: ConfigurationType"/> <complexType name="ConfigurationType" mixed="true"> <complexContent>
<restriction base="ipmpinfo : ConfigurationType"> <sequence>
<element ref="ipmpinfo-msx:ToolBody" minOccurs="0"/> </sequence> </restriction>
</complexContent> <sequence>
<any namespace="##any" processContents="lax" minOccurs="0"/> </sequence>
</complexType>
<element name="Update" type="ipmpinfo: UpdateType"/> <complexType name="UpdateType">
<sequence> <element ref="ipmpinfo: Location" maxOccurs="unbounded"/>
<element ref="ipmpinfo : ScheduledUpdateTime" minOccurs="0 "/>
<element ref="ipmpinfo: SupportedPlatform" minOccurs="0" maxOccurs="unbounded"/>
<element ref="dsig: Signature" minOccurs="0"/> </sequence> </complexType>
<element name="Location" type="ipmpinfo: RemoteType"/> <element name="ScheduledUpdateTime" type="ipmpinfo: ScheduledUpdateTimeType"/>
<complexType name="ScheduledUpdateTimeType"> <simpleContent>
<extension base="dateTime"> <attribute name="periodic" type="duration" use="optional"/>
</extension> </simpleContent> </coraplexType> <element name="SupportedPlatform"
type="ipmpinfo: SupportedPlatformType"/>
<complexType name="SupportedPlatformType"> <sequence>
<any namespace="##any" processContents="lax" minOccurs="0"/>
</sequence> </complexType>
<element name= "Rights Descriptor" type="ipmpinfo: Right sDescriptorType"/> <complexType name="RightsDescπptorType">
<sequence>
<element ref="ipmpmf o : IPMPInf oDescriptor " mmOccurs="0"/>
<choice minOccurs="0"> <element ref =" ipmpmf o : License "/>
<element ref=" ipmpmf o: LicenseReference"/> <element ref="ipmpinfo: LicenseService"/> </choice> </sequence> </complexType>
<element name="License" type="ipmpinfo: LicenseType"/> <complexType name="LicenseType" mixed="true"> <sequence>
<any namespace="##any" processContents="lax" itιmOccurs="0"/>
</sequence> </complexType>
<element name="LicenseService" type=" ipmpmf o : LicenseServiceType"/> <complexType name="LicenseServiceType" mixed="true"> <sequence>
<any namespace="##any" processContents="lax" minOccurs="0"/>
</sequence> </complexType> <element name="LicenseReference"
type="ipmpmfo: LicenseReferenceType"/>
<complexType name="LicenseReferenceType"> <simpleContent>
<extension base="anyURI"/> </simpleContent>
</complexType>
<element name="InitializationSettings" type="ipmpinf o : ImtializationSettingsType"/>
<complexType name="ImtializationSettingsType" mixed="true"> <sequence>
<element ref="ipmpinf o : IPMPInf oDescriptor" minOccurs="0"/>
<element ref="ipmpmfo: ImtializationData"/> </sequence> </complexType>
<element name="ImtializationData" type="ipmpmfo: ImtializationDataType"/>
<complexType name="InitializationDataType" mixed="true">
<sequence> <any namespace="##any" ρrocessContents="lax" minOccur s= " 0 " />
</sequence> </complexType>
<element name=" I PMPGenerallnf oDescriptor" type="ipmpinfo: IPMPGeneralInfoDescπptorType"/>
<complexType name="IPMPGeneralInfoDescriptorType"> <sequence>
<element ref="ipmpmfo:ToolList" mmOccurs="0"/> <element ref="ipmpinf o : LicenseCollection" minOccurs="0"/>
<element ref="dsig: Signature" minOccurs="0"/> </sequence> </complexType>
<element name="ToolList" type="ipmpmfo : ToolListType"/> <complexType name="ToolListType">
<complexContent>
<restπction base="ipmpinfo:ToolListType"> <sequence>
<element ref="iprapinfo : ToolDescription" maxOccurs="unbounded" />
</sequence> </restnction> </complexContent> </complexType> <element name="ToolDescπption" type="ipmpinfo:ToolDescnptionType"/>
<complexType name="ToolDescriptxonType"> <complexContent>
<restπction base="ipmpinfo: ToolDescriptionType"> <sequence>
<element ref="ipmpinfo : IPMPToolID"/> <choice minOccurs="0">
<element ref="ipmpinfo : Inline"/> <element ref ="ipmpinf o : Remote" />
</choice> <element ref="ipmpmfo: ConfigurationSet tings" minOccurs="0"/> <element ref="ipmpmfo : Rights Descriptor" mmOccurs="0"/>
<element ref="dsig: Signature" minOccurs="0"/>
</sequence> <attribute name="localID" type="ID" use="required"/>
</restπction> </complexContent> </complexType> <element name="LicenseCollection"
type="ipmpinfo : LicenseCollectionType " />
<complexTγpe name="LicenseCollectionType" mixed="true "> <sequence>
<element ref=" ipmpinf o : RightsDescriptor" maxOccurs="unbounded" />
</sequence> </complexType> </schema>
DMB contents service system, user equipment, and remote consumption device
Fig. 16 shows an architecture of DMB system in accordance with an embodiment of the present invention. As shown in the drawing, the DMB system includes a DMB content service system 100 for providing DMB contents according to a multimedia contents access authority of a user, a transmission medium such as a broadcasting network 200, a DMB user equipment 300 for requesting for and using a combined multimedia service, and a transmission medium 400 such as a communication network or the Internet for receiving stored DMB contents through remote control.
The DMB content service system 100 includes a DMB content authoring unit 101, a DMB file storing unit 102, a control unit 103, a DMB content protecting unit 104, a DMB file formatting unit 105, a combined content transmitting unit 106, a license metadata generating unit 107, a protection metadata generating unit 108, and a detailed information metadata generating unit 109. The DMB content service system 100 authors video, audio, image and/or text data into one content through the DMB content authoring unit 101, and the authored DMB content may be stored in a DMB file storing unit 102. The control unit 103 controls the detailed information metadata generating unit 109 to generate metadata
describing detailed information on the authored DMB contents. Also, the control unit 103 controls the DMB content protecting unit 104 to encrypt, or protect, the authored DMB content and controls the protection metadata generating unit 108 to generate protection metadata describing information related to the encryption while the DMB content is encrypted. Also, the control unit 103 controls the license metadata generating unit 107 to generate license metadata to be used for generation of license information allowing the DMB content to be used. The authored DMB content, detailed information metadata therefor, protection metadata, and license metadata are transmitted to the DMB file formatting unit 105 to be included in one DMB content file, and they are formatted into a form appropriate for transmission through the broadcasting network 200, such as packetization for being transmitted in the form of MPEG-2 transport stream (TS) . The DMB content formatted for transmission is delivered from the combined content transmitting unit 106 to the DMB user equipment 300 through the broadcasting network 200.
The DMB content file generated in the DMB file formatting unit 105 has a file format capable of combining the DMB content including at least one of DMB video, DMB audio, data and combinations thereof, the detailed information metadata describing detailed information on the DMB content, and the protection and governance metadata describing information on protection and governance of the DMB content. Herein, the detailed information metadata and the protection and governance metadata are selectively included according to an application .
The DMB video is coded into an MPEG-4 AVC, and the DMB audio is coded into at least one among MPEG layer II audio according to ISO/IEC 11172-3 and ISO/IEC 13818-3,
MPEG-4 ER-BSAC audio according to ISO/IEC 14496-3, MPEG-4 HE-AAC version 2 audio according to ISO/IEC 14496-3, and MPEG AAC+SBR audio according to ISO/IEC 13818-7 and ISO/IEC 14496-3 AMDl. The data content may be represented in at least one among metadata, image, video, audio, and programming code, or it may be represented in at least one among Joint Photographic Coding Experts Group (JPEG) , Portable Network Graphic (PNG), Multiple-Image Network Graphic (MNG) , Hyertext Markup Language (HTML) , Cascading Style Sheets (CSS), ECMAscript, Java midlet, and Transport Protocol Experts Group (TPEG) . The data content is transmitted through at least one protocol among Dynamic Label Segment (DLS), Multimedia Object Transfer (MOT), and Transparent Data Channel (TDC) .
The data content may transmit information needed for searching or filtering additional information on DMB video contents or DMB audio contents, DMB video contents or DMB audio contents desired by a user. Also, the data content maybe text data for the DMB video content or DMB audio content which are required to be synchronized or not according to time. Herein, timed text is represented as 3GPP TS 26.245. Also, the data content may be user data . The detailed information metadata are represented as MPEG-21 DID or TV-Anytime Part 3, and the protection and governance metadata are represented as MPEG-21 IPMP or MPEG-21 REL.
The combined file format may be represented using an ISO-based file format (ISO/IEC 14496-12), an MPEG-4 file format (ISO/IEC 14496-14), or an MPEG-21 file format (ISO/IEC 21000-9) .
The combined file format having the aforementioned structure may be one combining a plurality of files into one file, and it may be applied to broadcasting contents
other than DMB.
The DMB user equipment 300 includes a combined content receiving unit 301, a combined content decoding unit 302, a DMB content rendering unit 303, a user equipment control unit 304, and a combined content storing unit 305.
The combined content receiving unit 301 receives a DMB content transmitted through the transmission media 200 and 400. The DMB content file has a format capable of combining the DMB content including video, audio and data, detailed information metadata on the DMB content, and protection and governance metadata describing information on protection and governance of the DMB content into one file. The combined content storing unit 305 stores the content of the combined file format received in the combined content receiving unit 301. The combined content decoding unit 302 receives the content of the combined file format from the combined content receiving unit 301 or the combined content storing unit 305, and decodes the DMB content based on the protection and governance metadata. The DMB content rendering unit 303 renders the DMB content decoded in the DMB content decoding unit 302. According to the detailed information metadata, the user equipment control unit 304 controls the combined content storing unit 305 to store the content of the combined file format received through the combined content receiving unit 301, or controls the combined content decoding unit 302 to decode the content of the combined file format received through the combined content receiving unit 301.
The user of the DMB user equipment 300 may directly receive the DMB content file through the DMB content service system 100, or the user may store the DMB content file in a storage such as Personal Data Recorder (PDR) and Networked Data Recorder (NDR) via the
transmission medium 400, such as a communication network or the Internet, in a remote place. The requested DMB content file can be received through the combined content receiving unit 301, and the received DMB content file may be decoded using a user license in the combined content decoding unit 302 or stored in the combined content storing unit 305 in the DMB user equipment 300. The DMB content rendering unit 303 of the DMB user equipment 300 renders the decoded DMB content. When a DMB content the user wants to consume is stored in an external storage or when a DMB content is to be stored not in a built-in storage of the DMB user equipment 300 but in an external storage, the user equipment control unit 304 performs remote control to consume or store the DMB content in the external storage through the transmission medium 400 such as a communication network or the Internet.
Fig. 17 is a flowchart describing a DMB content generating method in accordance with an embodiment of the present invention. First, in step S1702, a DMB content including at least one among DMB video, DMB audio and data is authored. In step S1704, detailed information metadata are authored to describe detailed information of the DMB content. In step S1706, the DMB content is encrypted, and encryption information and protection and governance metadata describing license information of a specific user are generated. Herein, the encryption information includes encryption tool information, decryption key information, and encryption parameter information, whereas the license information includes the number of restoration, license purchaser or user equipment, and restoration valid time. In step S1708, the above-generated DMB content, the detailed information metadata, and the protection and governance metadata are combined into one file format. Fig. 18 is a flowchart describing a DMB content
generating method in accordance with another embodiment of the present invention. In comparison with the embodiment shown in Fig. 17, a DMB content including at least one among DMB video, DMB audio and data is authored outside and inputted from the outside and detailed information metadata describing detailed information on the DMB content are not generated in the present embodiment .
First, in step S1802, license metadata describing license information of a specific user for the DMB content are generated. In step S1804, the DMB content is encrypted according to the license information. In step S1806, encryption metadata describing encryption information are generated. In step S1808, the above- authored DMB content, the license metadata, and the encryption metadata are combined into one file format.
Fig. 19 is a flowchart describing a DMB content restoring method in accordance with an embodiment of the present invention. First, received in step S1902 is a content of a combined file format (which is a DMB content file) capable of combining a DMB content including at least one among DMB video, DMB audio and data, detailed information metadata describing detailed information of the DMB content, and protection and governance metadata describing protection and governance of the DMB content. In step S1904, the content of the combined file format which has received according to the detailed information metadata is stored. In step S1906, the DMB content is decrypted according to the protection and governance metadata, and the decrypted DMB content is rendered in step S1908.
Fig. 20 is a flowchart describing a DMB content restoring method in accordance with another embodiment of the present invention. First, in step S2002, a DMB content of a combined file format capable of combining a
DMB content including at least one among DMB video, DMB audio and data, detailed information metadata describing detailed information of the DMB content, and protection and governance metadata describing protection and governance of the DMB content is searched and filtered based on the detailed information metadata. In step S2004, the content of the combined file format is parsed, and a user or a user equipment is authenticated by parsing the protection and governance metadata. In step S2006, information needed to decrypt the DMB content is extracted using the parsed protection and governance metadata. In step S2008, the content of the DMB content is presented through an interface of the user equipment by parsing the detailed information metadata. In step S2010, a corresponding content is extracted, decoded, and restored according to a content execution command from the user.
Fig. 21 shows a structure of a DMB remote consuming apparatus and how it is connected to a network in accordance with an embodiment of the present invention. As shown in the drawing, a DMB remote consuming apparatus 500 includes a control unit 501, a combined content receiving unit 502, a combined content storing unit 503, and a combined content streaming unit 504. The combined content receiving unit 502 receives a DMB content from a DMB content service system 100 through a broadcasting network 200. The combined content storing unit 503 stores the DMB content file received in the combined content receiving unit 502. The combined content streaming unit 504 provides the DMB content file stored in the combined content storing unit 503 to a DMB user equipment 300 in the form of streaming. The control unit 501 receives a request for storing or consuming a DMB content file from the DMB user equipment 300. When it receives a request for storing a DMB content file, it
controls the combined content receiving unit 502 to receive the DMB content file from the DMB content service system 100. When it receives a request for consuming a DMB content file, it calls a DMB content file stored in the combined content storing unit 503 and provides it to the DMB user equipment 300 through the combined content streaming unit 504. The DMB user equipment can remotely access to the control unit 501 through a transmission medium 400. When the DMB user equipment 300 remotely stores or consumes a DMB content file in an external storage, the DMB remote consuming apparatus 500 can receive the request for storing or consuming the DMB content from the DMB user equipment 300 through the transmission medium 400 such as a communication network and the Internet, and it transmits the request to the control unit 501 of the DMB remote consuming apparatus 500. Upon request from the DMB user equipment 300, the control unit 501 can receive the DMB content of the combined file format in the combined content receiving unit 502, or it can call a DMB content of the combined file format stored in the combined content storing unit 503 and provides it to the DMB user equipment 300 through the combined content streaming unit 504 in the form of streaming. Fig. 22 is a flowchart describing a method of remotely consuming DMB contents between a DMB user equipment 300 and a DMB content providing apparatus, or the DMB content service system 100. First, in step S2202, a DMB content file is received from the DMB content service system 100 upon a request from a user equipment 300. In step S2204, the received DMB content file is stored upon a request from the DMB user equipment 300. In step S2206, the stored DMB content file is provided to the DMB user equipment 300 upon a request from the DMB user equipment 300.
Mode for the Invention
Meanwhile, the method of the present invention may be authored as a computer program. Codes and code segments constituting the program may be easily induced by a computer program of ordinary skill in the art to which the present invention pertains. Also, the authored program may be stored in a computer-readable recording medium, which is a data storage, and read and executed on a computer to thereby realize the method of the present invention. The recording-medium includes all kinds of recording media that can be read by a computer, including not only tangible media such as CD and DVD but also immaterial media such as sub-carrier. While the present invention has been described with respect to certain preferred embodiments, it will be apparent to those skilled in the art that various changes and modifications may be made without departing from the scope of the invention as defined in the following claims.