WO2008044874A1

WO2008044874A1 - Method for managing and processing information of an object for presentation of multiple sources

Info

Publication number: WO2008044874A1
Application number: PCT/KR2007/004948
Authority: WO
Inventors: Chang Hyun Kim
Original assignee: Lg Electronics Inc.
Priority date: 2006-10-12
Filing date: 2007-10-10
Publication date: 2008-04-17

Abstract

When preparing meta data of an arbitrary content, a method according to the present invention creates meta data including protocol information and access location information of the arbitrary content and an identification for identifying at least one component pertaining to the arbitrary content, and incorporates into the created meta data protocol information and access location information of an auxiliary content to be presented in synchronization with the arbitrary content or link information enabling acquisition of protocol information and access location information of the auxiliary content. Afterwards, the present method creates information about presentation combinations between components pertaining to the arbitrary content and other components pertaining to the auxiliary content and incorporates the created information about presentation combinations into the meta data.

Description

D E S C R I P T I O N

METHOD FOR MANAGING AND PROCESSING INFORMATION OF AN OBJECT FOR PRESENTATION OF MULTIPLE SOURCES

1. Technical Field

5 This document relates to a method of managing information about content sources stored in an arbitrary device on a network, for example an UPnP-based network and processing information between network devices according to the information.

2. Background Art

An UPnP^1M (hereinafter, referred to as "UPnP")-based network proposed for home 10 networking basically comprises a plurality of UPnP devices, a service, and a control point (CP). In the UPnP network, a service indicates a minimum controlled unit in a network and is modeled by a state variable.

In the UPnP-based network, the control point is a control application having a function of detecting and controlling other devices and/or services and is installed in an arbitrary device, 15 for example physical devices such as a PDA that a user is easily capable of handling.

As shown in FIG. IA, an UPnP-based AV home network comprises a media server

(MS) 120 for providing media data for a home network, a media renderer 130 (MR) for playing the media data provided through the home network, and an AV control point 110 for controlling the media server 120 and the media renderer 130. The media server 120 and the media renderer

20 130 are a controlled device controlled by the control point 110.

The media server 120 (more particularly, a Content Directory Service (CDS) 121 within the media server 120) constructs object information from information about containers (corresponding to a directory) and media files loaded in itself. An 'object' is a term to cover an item having information about one or more media file and a container having information about 25 a directory, and in some cases, a term 'object' indicates only an item or only a container. One item corresponds to one or a plurality of media files. For example, a plurality of media files having an identical content of a different bit rate is managed as one item.

FIG. IB illustrates a signal flow between devices and/or services for a media play process performed in the network of FIG. IA. A displayed play process is described as follows. 30 First, the control point 110 obtains information about a protocol which the media renderer 130 can accept (SOl). In order to provide information about a directory and a media file under the corresponding directory for the control point 110, whenever an UPnP action 141, for example a browsing action is invoked according to user request (SlO), the media server (MS) 120 provides information about a current directory and item information about media files under the directory.

The CP 110 excludes, from the received information about each object, information about an item whose protocol is not matched with acceptable protocols provided from the media renderer 130, displays the information through a proper User Interface (UI) for a user (SIl-I), invokes, if a user selects one item (or one media file of a specific quality belonging to the item) through the UI (Sl 1-2), a connection preparing action (PrepareForConnectionQ) to the media server 120 and the media renderer 130 for preparing presentation of the selected media file (hereinafter, referred to as a 'component' or a 'media component'), and receives an instance ID for participating members (CM: ConnectionManager service, AVT: AVTransport service, and RCS: RenderingControl service) required for a presentation through streaming between both devices (120,130) (S12-1, S12-2). The instance ID is used to specify and control later a streaming service to be currently performed (for example, a SetVolumeQ action uses a previously received instance ID of RCS in order to adjust a current volume in a rendering of a streaming being presented (Sl 5-1)). The CP 110 sets access location information about a previously selected component, for example Universal Resource Locator (URL) information to an AVTransport service 133 (in the example of FIG. IA, the AVTransport service is installed in the media renderer 130, however may be installed in the media server 120) through an action (Sl 3), then invokes to the AVTransport service 133 a play action with an input argument carrying an instance ID of AVTransport service (S14), and thereby enabling a presentation by the RCS 131 after data of the selected component are streamed through a proper information exchange process between the media renderer 130 and the media server 120 (S15).

In order to further present one media file during the presentation (Sl 5), the above- described processes (Sl 1-2, S12-1, S12-2, S13, and S14) should be again performed after the presentation starts. Sometimes, SlO and Sll-1 may be also performed.

However, when they should be synchronously played (hereinafter, two or more mutually associated media components are referred to as a 'multiple component') because two or more media components are mutually associated each other, for example, when one media component is a movie and the other one component is a subtitle (or caption) of the movie, it is not satisfactory to apply the method of sequentially playing two or more media components. Sequential playing of two or more media components can not ensuring a synchronous presentation in the media renderer due to time delay. 3. Disclosure of the Invention

An aspect of this document is to provide information structure of an item to ensure that media components associated each other to be presented synchronously are presented all together.

Another aspect of this document is to provide a method of processing a signal between devices and/or services according to the constructed information

Another aspect of this document is to provide a method of managing individual connections for components pertaining to a multiple component as a group.

In one general aspect, a method of preparing meta data of a stored content is provided, and the method includes¹ creating meta data including protocol information and access location mfoimation for an arbitrary content and identification information identifying at least one component pertaining to the arbitrary content, incorporating into the meta data protocol information and access location information of an auxiliary content to be presented in synchronization with the arbitrary content, or link information for enabling obtainment of piotocol information and access location information of the auxiliary content; and creating information on presentable combination between a component belonging to the arbitrary content and a component belonging to the auxiliary content, and incorporating the created information on presentable combination into the meta data

In another general aspect, a method of presenting a content through data transmission between both devices and/ or a service, comprises: creating connection group information, if at least one auxiliary component is associated with a selected one primary component among a pluiakty of primary components or a primary component belonging to a content, and creating connection information for each of the components; and connecting the created each connection information to the created connection group information In an implementation, the link information is an object ID allocated to the auxiliary content or a component belonging to the auxiliary content.

In the implementation, meta data is created for the auxiliary content and protocol information and access location information of the auxiliary content are then incorporated into the cieated meta data for the auxiliary content In an implementation, type information specifying that a corresponding content is to be presented in synchronization with another content is written in the created meta data of the auxiliary content

In an implementation, the identification information of a component is specified by a value of a parameter accompanied by an element (or a tag) for specifying protocol information and access location information of a corresponding component pertaining to the at least one component

In the implementation, the information on presentable combination includes' a first element for allocating identification information to at least one component pertaining to the auxiliaiy content and specifying protocol information and access location information of the at least one component, and a second element storing combination specifying information specifying presentable combinations between at least one component belonging to the arbitrary content and at least one component belonging to auxiliary content. Identification information specified by a value of the parameter is used in the combination specifying information to identify a component belonging to the arbitrary content.

In an implementation, an element related to an auxiliary content within meta data includes a structure in which components are made to a package capable of accepting a plurality of auxiliary components that can produce desirable presentation only in case that the plurality of auxiliary components are presented all together in synchronization with a component pertaining to a primary content A single identifier is assigned to each of the component packages.

In an implementation, instance IDs are received for connections respectively by invoking a connection preparing action for each component to a connection manager service (ConnectionManager service) within both devices, and for each instance ID for the connection, an action foi joining to connection group information is invoked to the connection manager service within the both devices.

In an implementation, after a group connection preparing action for a connection group is invoked, a connection preparing action for individual connection is invoked for each component

In another implementation, after a connection preparing action for individual connection is invoked for each component, a group connection preparing action for a connection group is invoked.

In an implementation, an action of _joining each instance ID to a connection group is peiformed after obtaining an instance ID for all individual connections by invoking a connection piepaimg action for individual connections for all components necessary for playing a content.

In another implementation, if an instance ID of an individual connection for any one of all components necessary is obtained, an action of joining the obtained instance ID to a connection group is invoked regardless of obtainment of an instance ID for other individual connections

4. Brief Description of the Drawings

FIG IA is a diagram illustrating a configuration of a general UPnP AV network;

FIG. IB is a flow diagram illustrating a signal flow between devices in a media play piocess performed in the network of FIG. IA; FIG 2 is a diagram illustrating an example of networked devices for constructing item information for a content having an associated auxiliary content and for performing a signal piocessmg between devices and/or services in an implementation;

FIG 3A is a flow diagram illustrating a signal flow between devices and/or services in a media play process of a plurality of components performed in the network of FIG. 2 in an implementation,

FIG 3B is a flow diagram illustrating a signal flow between devices and/or services in a media play process of a plurality of components performed in the network of FIG. 2 in another implementation;

FIG. 4 is a diagram schematically illustrating a structure of item information constructed by comprising information about an auxiliary content presented by mutually interlocking with an arbitrary content in an implementation;

5 FIGS. 5A and 5E are diagrams illustrating preparation examples of additional expression information of FIG. 4 in various implementations;

FIG. 6 is a diagram illustrating a preparation example of item information about a content accessorily presented by interlocking with other components without being individually presented;

10 FIG. 7 illustrates a structure of item information constructed to include information on an auxiliary content to be presented in synchronization with an arbitrary content in an implementation;

FIGS. 8A and 8B illustrate examples of additional expression information in accordance with the implementation of FIG. 7;

15 FIGS. 9A and 9B illustrate user selection screens for a multiple component provided in an implementation;

FIG. 9C illustrates a user selection screen for a content having a multiple component and a single component in an implementation;

FIG. 9D is a diagram illustrating an example of outputting, when an auxiliary content 20 for interlocking playing with the selected primary component exists for a plurality of attributes, the auxiliary contents to a list for providing selection to a user in an implementation;

FIG. 1OA is a diagram illustrating an example of management information for grouping individual connections constructed by a ConnectionManager service provided within a device in an implementation;

25 FIG. 1OB is a diagram illustrating an example in which instance IDs for a group and individual connection are systematically constructed according to the management information constructed in FIG. 1OA. 5. Best Mode for Carrying Out the Invention

Hereinafter, implementations of this document will be described in detail with reference 30 to the accompanying drawings.

FIG. 2 is a diagram illustrating an example of networked devices for constructing item information for a content having a related auxiliary component and for performing a signal processing between devices and/or services in an implementation.

The network of FIG. 2 is an UPnP-based AV network and comprises a control point

35 210, a media server 220, and a media renderer 230. This document describes devices and/or services of a network based on an UPnP standard, however the following description can be just applied even to other network standards by adaptively substituting a necessary element according to a difference in a standard, so that this document is not subjected to an UPnP-based network.

In an implementation, item information for a multiple component is constructed by the CDS 221 (which may be a processor for executing software) within the media server 220 and a signal processing for the multiple component is performed mainly using the control point 210 according to a process shown in FIG. 3A.

A configuration of devices and a signal processing process described in the following desciiption illustrate a pull way among two ways, i.e. a push way and a pull way for streaming the media component However, the push way and the pull way have a difference in devices having oi using an AVTransport service for play management of streaming and have a different action direction according to whether a sub_ject of an action is a media server or a media renderer. However, the both ways have the same method of performing an action, so that a scope of this document is not limited by the illustrative drawings and descriptions.

The CDS 221 within the media server 220 prepares item information about media components, i e meta data for each component or a component group in a specific language form by searching media files stored in a large volume of storage such as a hard disk. In this case, media files having a relationship for a mutually synchronous presentation are regarded as one content and thus single item information is created therefor. FIG. 4 shows an example of a stiucture of item information generated with such a way. As shown in FIG. 4, for primary component (for example, AV stream) or primary components among components regarded as a single item, in addition to item property information 401 including a resources element (<res>) as in the prior art, information about an auxiliary component (for example, a subtide and sound) oi auxiliary components among the components and additional expression information 402 indicating relationship information for specifying various user-experienceable combinations of piimary components and auxiliary components are additionally prepared. The CDS 221 examines , based on, for example a name and/or an extension of each file, interrelationships between media files to be regarded as a single content and whether a component is primary or auxiliary component, and may determine, if necessary, from an extension of a corresponding file an attribute of each file (for example, text, image and/or coding algorithm). Further, the CDS 221 may determine, if necessary, the information from header information included in the file by opening the corresponding file, and may easily deteimine the information for stored media files (or files stored in a movable recording medium) fiom a database already prepared and stored in the same medium by other application programs.

FIG 5A shows a preparation example of additional expression information 402 in an implementation In the implementation of FIG. 5A, an element <userExperienceExpression> (also called as 'tag' in a certain mark-up language) for the additional expression information 402 compiises, for example three parts. A first part 510 is a resource element (a tag <primary resouice>) for a primary component and is an element for allocating an identifier (ID) to a primary component or primary components included in a resources element within the item piopeity information 401 In an example of FIG. 5A, IDs of 1 to n are allocated to the n primary components, respectively (511).

A second part 520 is a resources element (a tag <additional resource>) for the auxiliary component and is an element for allocating an ID to the auxiliary component presented in synchronization with the primary component and for recording a protocol and location mfoimation for enabling access of the components. The example of FIG. 5A shows that IDs of 'n+r, 'n+2', 'm+r, and 'm+2' are allocated to four auxiliary component packages, respectively. (521) The reason of allocating a single ID to a package being capable of including at least one component instead of allocating an ID to auxiliary components individually is that a normal presentation is possible in the event that a plurality of components (media files) are coupled. In the example of FIG 5A, because a file of "Terminator sub" stores image information for a subtitle and a file of "Terminator.idx" stores timing information to synchronize the subtitle information stored in the "Terminator. sub" with AV data (for example, an AV media file of "Teimmator mpeg") of a primary component, components of the both files ("Terminator, sub" and "Terminator.idx") are assigned to a single component package, so that a single identifier (n+1) is allocated to that package (522).

A third part 530 is a set of relationship elements for specifying component set information from which synchronous-presentable (user-experienceable) expression combinations of the primary components and the auxiliary components are derived. FIG. 5B shows an lllustiative particular example of relationship information in an implementation. As shown in FIG 5B, the third part 530 defines a component set providing presentable combinations of components to which each identifier is allocated in the first part 510 and the second part 520. In the example of FIG 5B, each internal relationship tag (<relationship>) indicates a single piesentable combination

In an example of FIG. 5B, three relationships (531,532,533) defining a component set piovidmg a presentable combination for a current item has prepared and an element (<relationship>) 531 of designating a first relationship shows four possible combinations in which a primary component set is 1 and 2 and an auxiliary component set is 'n+1' and 'n+2', an element 532 of designating a second relationship shows that a primary component set is 'n-1' and n, an auxiliary component set is 'n+1¹ and 'n+2', and another auxiliary component set is 'm+1' and 'm+2', and an element 533 of designating a third relationship shows that a primary component set is 1 and 2 and an auxiliary component set is 'n+3' and 'n+4¹. When one ielationship element is selected, one or a plurality of components can be selected from each component set and presented in mutually synchronized manner.

Explaining a prepared example of relationship shown in FIG. 5B in more detail, in a fust ielationship element, auxiliary components for subtitle information that can be presented in synchronization with each of the primary components 1 and 2 are designated to 'n+1' and 'n+2' (53 Ia) (that is, a synchronous presentable combination may be one of (primary, auxiliary) = (1, n+1), (1, n+2), (2, n+1), and (2, n+2)). In a second relationship element, to each of the primary components 'n-1' and n, auxiliary components of 'n+1' and 'n+2' for subtitle information that can be presented in synchronization are designated, and auxiliary components 'm+1' and 'm+2' foi voice aie designated (532a) In the example of FIG. 5B, on the assumption that an audio signal is not included in the primary components 'n-1' and n, the CDS 221 specifies auxiliary components 'm+1¹ and 'm+2' comprising a voice signal (a dialogue in a movie) in a presentation combination, for the corresponding primary components (n-1, n). As in an example of the second relationship element 532, a plurality of auxiliary components having a different attribute can be connected to the primary component Therefore, in order to distinguish them, an attribute parameter named 'order' to an element (<additionalComponent>) of designating an auxiliary component and designating a specific value to the parameter is added to distinguish attributes. In the example of FIG 5B, an order parameter of 0 is assigned to an auxiliary component of subtitle information, and an order parameter of 1 is assigned to an auxiliary component of voice mfoimation In order to use the relationship information as guide information for helping a user easily recognize and select, the CDS 221 prepares information about each element (<name>, <usage>, <subtitleLang>, and <voice>) indicating a name and a usage corresponding to the coiresponding relationship element and attribute information about an auxiliary component. The piepared information in element is provided for a user through a suitable UI by the CP 210, which receives and analyzes meta data for an ob)ect, and thus a primary component and an auxiliary component for a presentation can be selected.

The CDS 221 also designates a type element (<type>) in each relationship element, and each value (for example, TTO or TTO_VOICE) designated in this type element is pre-known to the CDS 221 A preparing method of set information for revealing a component combination for each type is also pre-specified as a policy to the CDS 221. In the example of FIG. 5B, a set of a piimaiy component and an auxiliary component having subtitle information is designated to a value 'TTO' designating a type of subtitle information to be synchronized with a time, and a set of a primary component, an auxiliary component having voice information, and an auxiliary component having voice information is designated to another value 'TTO_VOICE' designating subtitle information and voice information at the same time. Besides the mentioned types, various types can be defined and used For example, a slide show may be one type, and distinctive value having adequate text for the type can be defined and user for a component providing auxiliary presentation to support a primary component Therefore, in this document, a type used m a relationship element is not limited to a 'subtitle' and to a 'subtitle and voice¹

FIG 5C is a diagram illustrating a detailed example of prepared relationship mfoimation in another implementation In an example of FIG. 5C, all candidates of a presentation combination are defined in a tag (or element) <componentList> first. The example shows that primary components presentable for a current item are 1, 2, 'n-1', and n, and auxiliary components are 'n+1', 'n+2¹, 'n+3', 'n+4', 'm+1', 'rn+2' (541). Each presentable combination is defined as a tag <capability>. Then example of FIG. 5C shows that auxiliary components presentable in synchronization with the primary component 1 are 'n+1' and 'n+2', and shows that a default auxiliary component for synchronization in case of no selection by a user is designated as 'n+r (542). A set that can be combined for presentation can be added one by one by a <caρability> element. An attribute of an auxiliary component included in a combination for the synchronous presentation, for example information on whether voice or a subtitle can be identified by a value of "VaI" which is an attribute argument of a tag <capability>.

In a prepared example of FIG. 5C, a plurality of auxiliary components are allocated to a single primary component, and in this case, the plurality of auxiliary components for a subtitle or voice using different languages are associated with single primary AV component.

A name (i.e., a name of tag, for example <relationship>, <User Experience Name>, <componentSet>, < capability >,..) of each element used in FIGS. 5B and 5C is only an example, different name that is not presented in this document may be defined and used in the same way as explained above in this document.

As shown in FIGS. 4, 5A, and 5B or 5C, prepared information of an item is transmitted from the CDS 221 to the CP 210 as a response to a browsing action or a search action and analyzed by the CP 210, and the CP 210 provides a user with proper information enabling selection of a component to play according to the analysis. This is described later.

The implementation of FIG. 5A is prepared by directly inserting protocol information ("Protocollnfo") for an auxiliary component and location information for enabling accessing the component, for example URL information into item information of a related content. However, in another implementation, instead of a protocol and URL information for the auxiliary component associated with the primary component, indirect information enabling to aware of the information may be recorded. This indirect information may be, for example, an ID of an object designated to an associated auxiliary component. FIG. 5D shows additional expression information 402 prepared in the present implementation under the same condition as that of FIG. 5A. As shown in FIG. 5D, an object ID for the corresponding auxiliary component is prepared instead of a protocol and URL information for the component (551).

In an implementation of FIG. 5D, in a process of examining the stored media files and the storage tree structure, the CDS 221 constructs objects for components (as described above, these components can be known from a file extension or another method) to be presented auxiliary for other component not to be presented by itself and prepares item information of each object in the same form as shown in FIG. 6. However, because it is necessary that the objects are managed differently from an object of a component that can be presented by itself, the objects have to be managed in different manner from an object of a component that can be presented by itself, therefore a different type 601, for example "Object.item.TTOItem" is assigned to such objects. As described in FIG. 5A, in an example of FIG. 6, item information is prepared such that a single object is allocated to a group of auxiliary components if single component in the auxiliary group cannot be normally presented (or may be presented meaninglessly) and normal presentation is possible through only information related to other component data. Item information prepared in FIG. 6 is connected by an Object ID, i.e., "objl234" 602 to indirect information 552 for an auxiliary component in additional expression information prepared in FIG. 5D. In another implementation, protocol information for an auxiliary component and URL information for the component are used in a mixed manner of a direct information shown in FIG. 5A and an indirect information shown in FIG. 5D. FIG. 5E shows a detailed example of additional expression information prepared with the above-mentioned mixed manner. As shown in FIG. 5E, protocol information and URL information for an auxiliary component are directly written or an object ID for the auxiliary component (or auxiliary component package) is written. Of course, an object should be allocated to components for recording an object ID and item information for the object should be prepared, as shown in FIG. 6. As in this implementation, because information about the auxiliary component can be recorded by mixing direct way or indirect way, information about a source expression type, i.e., "direct" or "indirect" to a resource element (<additionalComponentRes>) for the auxiliary component is additionally written (561) so that the CP 210 may be easily identified. Thus, the CP 210 for analyzing meta data for the object can easily know protocol information and URL information for the auxiliary component.

In the above-explained implementation, item information is prepared such that the additional expression element 402 consists of three parts and the first part (corresponding to the element <primary resource>) assigns an ID to a primary component or primary components included in the resource element <res> within the item property information 401. In another implementation, elements for the additional expression information are constructed more simply by inserting an ID of a primary component or primary components into an element within the item property information 401 as attribute information of an element. FIG. 7 shows a concrete example of item information prepared according to the simplifying implementation.

Explaining the example shown in FIG. 7 in more detail, a parameter of "linkID" is defined as an attribute of a tag <res> (resource element) and an ID is assigned to a corresponding component by a value of the parameter (711) when a resource element (i.e., the tag <res>) is prepared (701) for a primary component (for example, an AV stream) regarded to belong to a single item. Unlike the implementation of FIG. 5A, 5D or 5E, the part 702 for additional expression information in the present implementation excludes elements (the elements < primary resource> in the implementations of FIGS. 5A, 5D and 5E) for allocating IDs to piimary components, and the part 702 consists of a resource element for auxiliary components 721 and a ielationship element 722 The resource elements for auxiliary components respectively assign IDs to auxiliary components to be presented in synchronization with a primary component and store protocol and location information for ensuring access of corresponding auxiliary components, and the relationship elements define component set information that specifies presentable (i e , user-experienceable) combinations between primary components and auxiliaiy components The method of preparing the resource element 721 for auxiliary components and the relationship element 722 is same as in the above implementations explained with reference to FIGS. 4, and 5A to 5E except that a value of the parameter linkID in a resource element <res> within the item property information is used to allocate an ID to a coiiesponding primary component Thus, the preparing method of the resource element for auxiliary components and the relationship element is omitted herein.

In the implementation of FIG 7, protocol information and URL information of an auxiliary component within the part 702 of additional expression information may be also wiitten in an indirect manner (801) as illustrated in FIG. 8A or in a mixed manner (802) of mdiiect and direct one as illustrated in FIG 8B. In the event that the mixed manner is used, mfoimation on source expression type (803), e g., "direct" or "indirect" may be additionally wiitten in the resource element for an auxiliary component <additionalComponentRes> in order that the CP 210, which interprets meta data, may distinguish the two referencing manners easily. According to the above-described manner or one among the above-described manners, aftei item information for stored files is constructed, information of each item is transmitted fiom the CDS 221 to the CP 210 in response to a browsing action or a search action of the CP 210, and operations for mutually synchronous presentation of the multiple component are peiformed based on the transmitted information. Hereinafter, those operations are described in detail

FIG 3A is a flow diagram illustrating a signal flow between devices and/or services in a process of playing a media of a multiple component in an implementation. Information of an item prepared by the CDS 221 within the media server 220 through the above-described method is tiansmitted from the CDS 221 to the CP 210 in response to a browsing action or a search action of the CP 210 (S31) Of course, before such an action, as shown in FIG. 3A, the CP 210 lequests protocol information that can be acceptable to the media renderer 230 and obtains the protocol information beforehand (S30)

The CP 210 provides from information of objects received at step S31 only objects (items) having protocol information acceptable to the media renderer 230 for a user through a suitable User Interface (UI)(S32-1). At this time, as shown in FIG 6, the item whose type is "ob_ject item TTOItem" is not presented to a user. In another implementation, the item whose type is "ob_ject item TTOItem" is displayed with a color lighter than different type of items so that it can identified differently by a user.

A user selects an item (or one of a plurality of components with different bit rates belonging to the item) to be presented by the media renderer 230 from the provided list of objects (S32-2). However, if additional expression information (information corresponding to <userExperienceExρression> element in FIGS. 5A, 5D, and 5E and FIGS. 7, 8A and 8B) exists in meta data of the selected item, the CP 210 does not immediately perform actions for a presentation for a component of the selected item. Instead the CP 210 analyzes the additional expression information, and performs additional selection operations accordingly (S32-3).

The CP 210 examines elements (in the implementation of FIG. 5B) of <relationship> specifying a relationship for a presentable combination in meta data of the selected item, or a user experience element <User Experience Name> (in the implementation of FIG. 5C). In the relationship elements or the user experience element, if an ID (this ID can be identified from a resource element <primary resource> of a primary component within the additional expression information 402 in case of the implementation of FIG. 4, and it can be identified by a value of the parameter linkID of a resource element <res> of item property information in case of the implementation of FIG. 7) of the currently selected component is not described in a <primaryComponent> element, the CP 210 immediately requests actions (PrepareForConnectionO, SetAVTransportURIQ, PlayQ, etc.) sequentially for playing the selected component, and if an ID of the currently selected component is written in a <primaryComponent> element, the CP 210 additionally presents a selection list according to information specified by a corresponding relationship element or a user experience element to a user. FIG. 9A is an illustrative example for this case and is prepared for the first relationship element 531 of FIG. 5B.

FIG. 9A shows an example in which components (or component packages) of ID 'n+1' and 'n+2', which are auxiliary components of subtitle associated with a selected primary component of ID 1 are listed 901 for user's selection. Because it is supposed that a single primary component is selected in order to describe an implementation, when combination information by a relationship element or a user experience element is displayed, in order to show that primary component (the primary component 1 in a shown example) is already selected from a primary component set included in the relationship element or the user experience element, a distinctively-identifiable displaying way 901 may be used. In addition to, a selection bar for selecting a component is positioned in an auxiliary component set. In an example of FIG. 9A, each component is identified by IDs of components for drawing convenience, however information actually displayed to a user may be a file name or an object title (in the case that auxiliary components are allocated to a separate object as shown in FIG. 6) corresponding to the corresponding component.

If the selected primary component belongs to a combinable tag <capability> within a plurality of relationship elements or user experience elements, the CP 210 provides a selection window 902 in which a name of each relationship element and additional information (information specified by a <subtitleLang> element is used in the example of FIG. 9B) written in an internal element are listed as shown in FIG. 9B so that a relationship element or a combination is selected by a user If one relationship element or one combination is selected fiom the window, the selection screen example shown in FIG. 9A is provided. If an item of 'subtitle (Korean)' is selected in a displayed example of FIG. 9B, the CP 210 outputs a selection screen such as FIG. 9A. Of course, because the CP 210 knows from the type element <type> written in each relationship element what attribute of an auxiliary component set is included in a coiresponding relationship element, the CP 210 may additionally provide explanation enabling a usei to easily recognize in addition to the illustrated display information. In an implementation of FIG 5C, after analyzing a value of an attribute parameter "VaI" of the combinable tag <capability> in order to help a selection of a user, information corresponding to the value may be displayed on the selection window along with a text or graphic information. In another implementation, if an item to be presented by the media renderer 230 is selected from a provided list of objects by a user and one primary component is selected from a pluiakty of primary components pertaining to the selected item, a selection screen such as FIG. 9A or 9B is not provided. Instead, a selection screen such as FIG. 9C is provided immediately aftei analyzing the additional expression information 402 of the corresponding meta data when an item is selected A single item listed on a multiple-component window in a selection screen illustiated in FIG 9C corresponds to a single relationship element or a single or a plurality of tags <capability>. Therefore, if a user selects one item belonging to the multiple-component window in a provided selection screen, the CP 210 provides a selection screen such as FIG. 9A based on information of a relationship element or a single or a plurality of tags <capablhty> coiresponding to the selected item so that a single primary component and at least one auxiliary component may be selected by a user If an item belonging to a single-component window is selected, necessary actions are invoked to related devices so that a component corresponding to the selected item is immediately played by the media renderer 230.

In an implementation, for the selected primary component, if there are a plurality of auxiliaiy component elements (<additionalComponent>) having a different order value (in case of the implementation of FIG 5B), or if there are a plurality of combinable elements (< capability >) (in case of the implementation of FIG 5C), the CP 210 provides selectable sets 912 foi all component elements or combinable elements as shown in FIG. 9D and receives selections of an auxiliary component (or a component package) from each selectable set. When a plurality of combinable elements is provided for a user as shown in FIG. 9D, an attribute of each combinable element, for example, information indicating subtitle or voice may be displayed at an uppei area of each selectable set. According to the above-described process, if a selection for a primary component and an auxiliaiy component is finished, the CP 210 obtains from the related elements protocol infoimation and URL information for the selected component That is, the protocol information and URL information for the primary component is obtained from an element <res> within pioperty information prepared according to a conventional method, and the protocol information and URL information for the auxiliary component is obtained from the above- descnbed element <additional resource>. In an implementation of FIG. 5D, 5E, 8A and 8B in which information about a corresponding component is specified in an indirect manner, the CP 210 obtains corresponding protocol information and URL information using corresponding mdnect information, i e , an object ID as index information. For example, protocol information and URL information is obtained from a corresponding element (the element <additionalComponent>) written within meta data that has been received for a corresponding object ID through a previous browsing operation or is received through a search action with the coriespondmg ID in an input argument thereof invoked to the CDS 221 if it has not been received through a previous browsing operation.

If the protocol information of an auxiliary component obtained through the above- described process is not matched with the previously obtained admittable protocols of the media iendeier 230, the corresponding auxiliary component is ignored and the below-explained operations to request the media renderer 230 to present does not conducted. Instead, a notification message such as "The selected auxiliary component cannot be presented by the media renderer'" may be outputted to a user.

The CP 210 conducts the following connection preparing operations for a primary component and an auxiliary component whose protocol information and URL information are obtained Actions for the connection preparing operations are invoked respectively for each of a connection group and individual connections. For example, as shown in FIG. 3A, after invoking a group connection preparing action (PrepareGroupConnectionQ) for a connection group (S33-1, S33-2) to the CM services (222,232) of each of devices (media server 220 and media renderer 230), the CP 210 invokes a connection preparing action (PrepareForConnectionO) for individual connection for each component to the media server 220 and the media renderer 230 respectively. As a result, instance IDs for participating services to be involved in presentation of streaming between the devices are received (S34-1, S34-2). connection corresponding to each component are individually received by a connection preparing action, the CP 210 invokes a group _join action (AddtoGroupQ) to connect an instance ID for an individual connection to the previously received instance ID for a group connection that is received by a group connection preparing action. The group join action is invoked as many times as the number of individual connections (S35-1, S35-2). In this case, the instance ID for a connection group and the instance ID for one individual connection to be joined to the connection group are included in an input argument of each group join action.

In an implementation of FIG. 3A, after a group connection preparing action for a connection group is invoked (S33-1, S33-2), connection preparing actions are invoked respectively for individual connections (S34-1, S34-2). However such action sequence may be performed in a reverse order. In other words, before invoking a group join action that requires preparation of instance ID for a connection group and instance IDs for individual connections to join to the connection group, a group connection preparing action and connection preparing actions for individual connections are performed regardless of the order.

If the action for connecting the instance ID is received, the CM service (222 or 232) constructs management information for mapping an instance ID for a connection group and an instance ID for individual connection that are delivered by each group join action. FIG. 1OA shows an example of the management information for grouping individual connections constructed by a ConnectionManager service 232 within the media renderer 230 (Because the media renderer 230 of FIG. 2 equips with the AVTransport service 233, an AVTransport service instance ID is provided in response to the connection preparing action. Thus the instance ID of the AVTransport service is also included in the instance ID for a connection.), and FIG. 1OB is a schematic diagram illustrating an example in which instance IDs for a group connection and individual connections are systematically constructed. In addition to mapping information for the instance IDs illustrated in FIG. 1OA, information, for example, a type, information on whether an individual connection is for primary or auxiliary component, and order parameter information of an auxiliary component, etc., received via input arguments of a group connection preparing action and a group join action are also stored and managed as management information by the CM service (222 or 232).

When playing management or rendering control is requested through the instance ID of the connection group from the CP 210, each of ConnectionManager services (222,232) can identify an instance ID for an action-requested service of an individual connection with reference to the constructed mapping information such as FIG. 1OA and can identify and identify a related resource using the identified instance ID.

In the above-explained implementation, before receiving all necessary instance IDs for connections through individual connection preparing actions for the selected components, the CP 210 may immediately invoke an action (AddtoGroupQ) for joining an any individual connection to a connection group set previously by a group connection preparing action before the corresponding connection as soon as an instance ID of the any individual connection is received, as shown in FIG. 3B. FIG. 3B shows that a group join action is immediately invoked when a response to a connection preparing action is received but does not show that a connection preparing action for a next connection should be sequentially performed after one group join action. That is, in this document, as shown in the implementation of FIG. 3B, a group join action (AddtoGroupQ) for an individual connection can be performed regardless of whether a response to a connection preparing action (PrepareForConnectionQ) for another individual connection is received

After grouping individual connections into a connection group as explained above, for the selected each component, the CP 210 invokes an action (SetAVTransportURI Q) for setting access location information, for example, URL information of the each component to the AVTransport service 233 (S36). A play action is then invoked to the AVTransport service 233. At this time, the play action uses the received AVTransport service instance ID for connection gioup (Instance_GrAVTID) (S37) The AVTransport service instance ID for connection group used in the play action is mapped to the AVTransport service instance ID for an individual connection by the ConnectionManager service 232 and the AVTransport service instance ID for an individual connection is transmitted to the AVTransport service 233, whereby play operations for all individual connections can be started at the same time. Accordingly, data of the selected components are streamed or downloaded through a proper information communication between the media renderer 230 and the media server 220 and thus are synchronously decoded and outputted by the rendering module under control of the RenderingControl service 231 (S38).

In the explanation of the above-described implementation, an action (SetAVTransportURIQ) for setting an URL of each component is invoked after a group )oin action, however an order of action invocation is only an example, and an action for setting the URL may be invoked before a group join action (AddtoGroupQ). That is, an invocation order of both actions is not limited to the order described above.

While presentation is being performed according to the above processes (S38), the CP 210 invokes an action (for example, AVTStopQ, AVT:PauseQ, RCS:SetVolumeQ, RCS:SetMuteQ, etc ) matched with user's request to the media renderer 230 when a user requests control (play stop, temporary suspension, search, and speed change play (trick play), etc.) of a specific play operation or change (volume adjustment, audio output stop, brightness ad_justment, etc.) of rendering state The invoked action matched with user's request uses an instance ID for a connection group allocated to streaming of a multiple component currently in service. In the event that the instance ID for a connection group is used, a service receiving the action can translate the instance ID for a connection group to an instance ID of an individual connection corresponding to the action and identify one individual connection. Alternatively, when the action is invoked, an instance ID for an individual connection pertaining to the connection group may be used after being obtained.

When a user requests to release or it is judged that streaming of a multiple component is unnecessary, the CP 210 or 290 releases a state in which the connection group is established. In older to release the state, the CP 210 or 290 invokes an action (RemoveFromGroup Q) for lemoving an individual connection from a group to CM services 222 and 232 for each individual connection to release. At this time, the removing action includes in an input argument thereof an instance ID for the connection group and an instance ID for an individual connection to release fiom the connection group. Accordingly, the CM 222 or 232, received the removing action, deletes an instance ID from the ID mapping information constructed as shown in FIG. 1OA. The deleted instance ID is one identical to an instance ID for individual connection carried by the input argument of the received action and is linked with an instance ID for a connection group that is identical to an instance ID for a connection group carried by the input argument of the leceived action Whenever an instance ID for individual connection is deleted from the ID mapping information by every connection removing action (RemoveFromGroup Q), the CM seivice 222 or 232 examines the ID mapping information for the corresponding connection gioup and deallocates an instance ID for the connection group to be reused by another connection group if no instance ID for an individual connection associated with the coriesponding connection group is remained.

In the above-explained implementations, in a situation that data is presented through tiansmission between devices connected to each other through a network, operations for play pieparation and playing of one primary component and an auxiliary component associated therewith can be conducted simultaneously, thereby enabling normal synchronous presentation of media components. In addition, connections pertaining to a connection group can be managed individually Accordingly, a user viewing and hearing a content is satisfied much more by the auxiliary component and user's convenience can be improved when changing some components during playing of a multiple component

While the invention has been disclosed with respect to a limited number of embodiments, those skilled in the art, having the benefit of this disclosure, will appreciate numerous modifications and variations therefrom. It is intended that all such modifications and variations fall within the spirit and scope of the invention.

Claims

C L A I M S

1. A method of preparing meta data of a stored content, comprising: creating meta data including protocol information and access location information for an arbitrary content and identification information identifying at least one component pertaining to the arbitrary content; incorporating into the meta data protocol information and access location information of an auxiliary content to be presented in synchronization with the arbitrary content, or link information for enabling obtainment of protocol information and access location information of the auxiliary content; and creating information on presentable combination between a component belonging to the arbitrary content and a component belonging to the auxiliary content, and incorporating the created information on presentable combination into the meta data.

2. The method of claim 1, wherein the link information is an object ID allocated to the auxiliary content or a component belonging to the auxiliary content.

3. The method of claim 2, wherein the incorporating into the meta data the protocol information and access location information or the link information further includes creating meta data for the auxiliary content and incorporating the protocol information and access location information of the auxiliary content into the meta data for the auxiliary content.

4. The method of claim 3, wherein the meta data created for the auxiliary content includes type information indicating that a corresponding content is to be presented in synchronization with another content.

5. The method of claim 1, wherein the arbitrary content and the auxiliary content respectively consist of at least one component, and the at least one component respectively corresponds to a file that stores data.

6. The method of claim 1, wherein the meta data creating includes specifying the identification information by a value of a parameter accompanied by an element for specifying protocol information and access location information of a corresponding component pertaining to the at least one component.

7. The method of claim 6, wherein the information on presentable combination includes: a first element for allocating identification information to at least one component pertaining to the auxiliary content and specifying protocol information and access location information of the at least one component; and a second element storing combination specifying information specifying presentable combinations between at least one component belonging to the arbitrary content and at least one component belonging to auxiliary content, wherein identification information specified by a value of the parameter is used in the combination specifying information to identify a component belonging to the arbitrary content.

8. The method of claim 1, wherein the information on presentable combination includes a structure capable of allocating a single piece of identification information to a component package including one or more components pertaining to the auxiliary content.

9. The method of claim 8, wherein the creating and incorporating the information on presentable combination includes incorporating a plurality of components pertaining to the auxiliary content into a single component package if desirable presentation is possible only in case that the plurality of components are presented all together in synchronization with the arbitrary content.

10. An apparatus of providing a stored content for a device through a network, comprising: a storage configured to store at least one primary content and at least one auxiliary content to be presented in synchronization with the primary content; and a processor configured to provide information on the primary content and the auxiliary content in response to an external request, wherein meta data of the primary content stored in the storage includes: at least one element, the one element specifying identification information identifying at least one component pertaining to the primary content and protocol information and access location information of the one component pertaining to the primary content; protocol information and access location information of the auxiliary content; and information on presentable combination between a component pertaining to the primary content and a component pertaining to the auxiliary content.

11. The apparatus of claim 10, wherein the identification information is specified by a value of a parameter accompanied by the one element.

12. The apparatus of claim 11, wherein the identification information specified by a value of the parameter is used in the information on presentable combination to identify a component belonging to the primary content.

13. An apparatus of providing a stored content for a device through a network, comprising: a storage configured to store at least one primary content and at least one auxiliary content to be presented in synchronization with the primary content; and a processor configured to provide information on the primary content and the auxiliary content in response to an external request, wherein meta data of the primary content includes: at least one element, the one element specifying identification information identifying at least one component pertaining to the primary content and protocol information and access location information of the one component pertaining to the primary content; link information enabling obtainment of protocol information and access location information of the auxiliary content; and information on presentable combination between a component pertaining to the primary content and a component pertaining to the auxiliary content.

14. The apparatus of claim 13, wherein the processor configured to write the protocol information and the access location information of the auxiliary content in meta data of the auxiliary content.

15. The apparatus of claim 13, wherein the link information is an object ID allocated to the auxiliary content.

16. The apparatus of claim 13. wherein the identification information is specified by a value of a parameter accompanied by the one element.

17. The apparatus of claim 16, wherein the identification information specified by a value of the parameter is used in the information on presentable combination to identify a component belonging to the primary content.

18. The apparatus of claim 10, wherein the information on presentable combination includes a structure capable of allocating a single piece of identification information to a component package including one or more components pertaining to the auxiliary content.

19. The apparatus of claim 18, wherein a plurality of components pertaining to a single component package are components that can produce desirable presentation only in case that the plurality of components are presented all together in synchronization with the arbitrary content.