WO2008044874A1 - Procédé de gestion et de traitement d'informations d'un objet servant à présenter plusieurs sources - Google Patents

Procédé de gestion et de traitement d'informations d'un objet servant à présenter plusieurs sources Download PDF

Info

Publication number
WO2008044874A1
WO2008044874A1 PCT/KR2007/004948 KR2007004948W WO2008044874A1 WO 2008044874 A1 WO2008044874 A1 WO 2008044874A1 KR 2007004948 W KR2007004948 W KR 2007004948W WO 2008044874 A1 WO2008044874 A1 WO 2008044874A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
content
component
auxiliary
primary
Prior art date
Application number
PCT/KR2007/004948
Other languages
English (en)
Inventor
Chang Hyun Kim
Original Assignee
Lg Electronics Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lg Electronics Inc. filed Critical Lg Electronics Inc.
Publication of WO2008044874A1 publication Critical patent/WO2008044874A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/764—Media network packet handling at the destination 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/762—Media network packet handling at the source 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2805—Home Audio Video Interoperability [HAVI] networks

Definitions

  • 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.
  • 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).
  • a service indicates a minimum controlled unit in a network and is modeled by a state variable.
  • 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.
  • an UPnP-based AV home network comprises a media server
  • MS 120 for providing media data for a home network
  • MR media renderer 130
  • AV control point 110 for controlling the media server 120 and the media renderer 130.
  • 20 130 are a controlled device controlled by the control point 110.
  • 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.
  • SOl protocol which the media renderer 130 can accept
  • MS media server
  • 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).
  • CM ConnectionManager service
  • AVT AVTransport service
  • RCS RenderingControl service
  • 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.
  • 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).
  • two or more mutually associated media components are referred to as a 'multiple component'
  • a 'multiple component' two or more mutually associated media components are mutually associated each other
  • one media component is a movie and the other one component is a subtitle (or caption) of the movie
  • Sequential playing of two or more media components can not ensuring a synchronous presentation in the media renderer due to time delay.
  • 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.
  • a method of preparing meta data of a stored content includes 1 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
  • 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
  • the link information is an object ID allocated to the auxiliary content or a component belonging to the auxiliary content.
  • 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
  • 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
  • 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
  • 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.
  • 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.
  • 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.
  • ConnectionManager service connection manager service
  • connection preparing action for a connection group is invoked, a connection preparing action for individual connection is invoked for each component
  • a group connection preparing action for a connection group is invoked.
  • an action of j oining 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.
  • 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
  • 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
  • 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;
  • 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;
  • 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
  • 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
  • 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
  • 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.
  • 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
  • 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 j ect of an action is a media server or a media renderer.
  • 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.
  • 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 facilitatecture of item information generated with such a way. As shown in FIG.
  • auxiliary component for example, a subtide and sound
  • 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
  • an element ⁇ userExperienceExpression> also called as 'tag' in a certain mark-up language
  • 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
  • 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.
  • a file of "Terminator sub” stores image information for a subtitle
  • 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
  • AV data for example, an AV media file of "Teimmator mpeg”
  • 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.
  • 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.
  • each internal relationship tag ( ⁇ relationship>) indicates a singlerodntable combination
  • 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 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 1 .
  • one ielationship element is selected, one or a plurality of components can be selected from each component set and presented in mutually synchronized manner.
  • 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)
  • the CDS 221 specifies auxiliary components 'm+1 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).
  • 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.
  • an order parameter of 0 is assigned to an auxiliary component of subtitle information
  • an order parameter of 1 is assigned to an auxiliary component of voice mfoimation
  • 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.
  • ⁇ type> a type element
  • TTO or TTO_VOICE a value designated in this type element
  • 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
  • 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.
  • 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 1
  • FIG 5C is a diagram illustrating a detailed example of prepared relationship mfoimation in another implementation
  • 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 1 , 'n+3', 'n+4', 'm+1', 'rn+2' (541).
  • Each presentable combination is defined as a tag ⁇ capability>.
  • FIG. 5C is a diagram illustrating a detailed example of prepared relationship mfoimation in another implementation
  • 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 1 , 'n+3
  • 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>.
  • 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 >,..
  • a name of tag for example ⁇ relationship>, ⁇ User Experience Name>, ⁇ componentSet>, ⁇ capability >,..
  • 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.
  • FIG. 5A 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.
  • protocol information "Protocollnfo"
  • 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.
  • an object ID for the corresponding auxiliary component is prepared instead of a protocol and URL information for the component (551).
  • 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.
  • the objects 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.
  • a different type 601 for example "Object.item.TTOItem" is assigned to such objects.
  • FIG. 5A in an example of FIG.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the CP 210 for analyzing meta data for the object can easily know protocol information and URL information for the auxiliary component.
  • 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.
  • 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.
  • 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.
  • a resource element i.e., the tag ⁇ res>
  • a primary component for example, an AV stream
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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)
  • 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 j ect item TTOItem" is not presented to a user. In another implementation, the item whose type is "ob j ect item TTOItem” is displayed with a color lighter than different type of items so that it can identified differently by a user.
  • UI User Interface
  • 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).
  • additional expression information information corresponding to ⁇ userExperienceEx ⁇ ression> element in FIGS. 5A, 5D, and 5E and FIGS. 7, 8A and 8B
  • 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).
  • elements in the implementation of FIG. 5B
  • a user experience element ⁇ User Experience Name>
  • 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.
  • 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.
  • 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.
  • 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.
  • the CP 210 may additionally provide explanation enabling a usei to easily recognize in addition to the illustrated display information.
  • information corresponding to the value may be displayed on the selection window along with a text or graphic information.
  • 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>.
  • 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.
  • 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.
  • an attribute of each combinable element for example, information indicating subtitle or voice may be displayed at an uppei area of each selectable set.
  • 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>.
  • the CP 210 obtains corresponding protocol information and URL information using corresponding mdnect information, i e , an object ID as index information.
  • 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.
  • auxiliary component 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.
  • a group connection preparing action PrepareGroupConnectionQ
  • PrepareForConnectionO connection preparing action for individual connection for each component to the media server 220 and the media renderer 230 respectively.
  • 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 j oin 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).
  • 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.
  • connection preparing actions are invoked respectively for individual connections (S34-1, S34-2).
  • action sequence may be performed in a reverse order.
  • a group connection preparing action and connection preparing actions for individual connections are performed regardless of the order.
  • the CM service 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.
  • 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).
  • each of ConnectionManager services 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.
  • 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
  • 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.
  • 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).
  • an action for setting an URL of each component is invoked after a group )oin action
  • 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.
  • 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 j ustment, 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.
  • 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.
  • an instance ID for an individual connection pertaining to the connection group may be used after being obtained.
  • the CP 210 or 290 releases a state in which the connection group is established.
  • 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.
  • 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.
  • 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
  • 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.
  • 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

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Lors de la préparation de métadonnées d'un contenu arbitraire, un procédé selon l'invention crée des métadonnées incluant des informations de protocole et des informations de lieu d'accès du contenu arbitraire et une identification servant à identifier au moins un élément faisant partie du contenu arbitraire et introduit dans les métadonnes crées, des informations de protocole et des informations de lieu d'accès d'un contenu arbitraire devant être présentées en même temps que le contenu arbitraire ou des informations de liaison permettant d'acquérir les informations de protocole et les informations de lieu d'accès du contenu auxiliaire. Le procédé selon l'invention crée ensuite des informations portant sur les combinaisons de présentation entre des éléments faisant partie du contenu arbitraire et d'autres éléments faisant partie du contenu auxiliaire et intègre, dans les métadonnées, les informations créées portant sur les combinaisons de présentation.
PCT/KR2007/004948 2006-10-12 2007-10-10 Procédé de gestion et de traitement d'informations d'un objet servant à présenter plusieurs sources WO2008044874A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US82926906P 2006-10-12 2006-10-12
US60/829,269 2006-10-12

Publications (1)

Publication Number Publication Date
WO2008044874A1 true WO2008044874A1 (fr) 2008-04-17

Family

ID=39283032

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2007/004948 WO2008044874A1 (fr) 2006-10-12 2007-10-10 Procédé de gestion et de traitement d'informations d'un objet servant à présenter plusieurs sources

Country Status (1)

Country Link
WO (1) WO2008044874A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6735770B1 (en) * 1998-04-27 2004-05-11 Sun Microsystems, Inc. Method and apparatus for high performance access to data in a message store
US20060059168A1 (en) * 2003-01-29 2006-03-16 Masaaki Hamada Information processing device, content management method, content information management method, and computer program
US20060089981A1 (en) * 2004-10-22 2006-04-27 Lg Electronics Inc. Supporting device information of a combo device in a universal plug and play network
WO2006059696A1 (fr) * 2004-12-02 2006-06-08 Matsushita Electric Industrial Co., Ltd. Dispositif de gestion de méta données et dispositif d’utilisation de méta données

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6735770B1 (en) * 1998-04-27 2004-05-11 Sun Microsystems, Inc. Method and apparatus for high performance access to data in a message store
US20060059168A1 (en) * 2003-01-29 2006-03-16 Masaaki Hamada Information processing device, content management method, content information management method, and computer program
US20060089981A1 (en) * 2004-10-22 2006-04-27 Lg Electronics Inc. Supporting device information of a combo device in a universal plug and play network
WO2006059696A1 (fr) * 2004-12-02 2006-06-08 Matsushita Electric Industrial Co., Ltd. Dispositif de gestion de méta données et dispositif d’utilisation de méta données

Similar Documents

Publication Publication Date Title
US8065335B2 (en) Method for managing and processing information of an object for presentation of multiple sources and apparatus for conducting said method
US20100063970A1 (en) Method for managing and processing information of an object for presentation of multiple sources and apparatus for conducting said method
US9344471B2 (en) Method and apparatus for managing and processing information of an object for multi-source-streaming
US8504712B2 (en) Method and apparatus for managing multi-streaming contents and for controlling of changing players during playback of multi-streaming contents
EP1607937A1 (fr) Dispositif de traitement d'informations, procede de traitement d'informations, et programme d'ordinateur
CN102177702B (zh) 通过使用通用即插即用播放场景的方法和装置
US20140324944A1 (en) Remote management of dlna system
US8943545B2 (en) Digital living network alliance system and method for providing content therein
US8601189B2 (en) Method for processing information of an object for presentation of multiple sources
EP1686728A1 (fr) Procédé et appareil pour une connexion automatique entre des dispositifs utilisés pour reproduire un contenu et programme informatique stockant un support d'enregistrement pour mettre en oeuvre ledit procédé
EP1828916A1 (fr) Structure d'objets memorises dans un serveur multimedia ameliorant l'accessibilite a la structure
US8127030B2 (en) Method and apparatus for controlling network of shared resources
US20050132366A1 (en) Creating virtual device for universal plug and play
WO2008044874A1 (fr) Procédé de gestion et de traitement d'informations d'un objet servant à présenter plusieurs sources
WO2008039005A1 (fr) Méthode de gestion et traitement d'informations sur un objet pour la présentation de sources multiples
KR101069859B1 (ko) 다중-리소스 스트리밍을 위한 오브젝트에 대한 정보 관리 및 처리 방법 그리고 그 장치
KR20080035084A (ko) 다중 소스의 프리젠테이션을 위한 오브젝트에 대한 정보관리 및 처리 방법
US20070175975A1 (en) Method and apparatus for providing DVD content with rendering device in UPnP network
KR20080033794A (ko) 다중 소스의 프리젠테이션을 위한 오브젝트에 대한 정보와커넥션 그룹을 관리하는 방법
KR20080028578A (ko) 다중 소스의 프리젠테이션을 위한 오브젝트에 대한 정보관리 및 처리 방법
WO2009002071A2 (fr) Procédé et dispositif servant à gérer et à traiter des informations d'objet pour diffusion en flux d'un contenu multiple
KR100728034B1 (ko) ＵＰｎＰ네트워크에서 ＤＶＤ컨텐츠를 제공하는 방법 및장치
KR100833234B1 (ko) ＵＰｎＰ네트워크에서 ＤＶＤ컨텐츠를 제공하는 방법 및장치
MX2008008255A (es) Metodo y aparato que suministra contenido de disco versatil digital con dispositivo visualizdor en red de enchufe y reproduccion universal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07833259

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07833259

Country of ref document: EP

Kind code of ref document: A1