KR20080035084A - Method for managing and processing information of an object for presentation of multiple sources - Google Patents

Abstract

A method for managing and processing information about an object for presentation of multi-source is provided to enhance user satisfaction of viewing and listening to contents by allowing media components to normally and reliably performing reproducing cooperatively. A CP(Control Point) requests receivable protocol information from a media renderer(S30). Information about each item is transferred from a CDS(Content Directory Service) to a CP(S31). The CP provides only objects(items) having protocol information that can be received by the media renderer to a user via a suitable UI(User Interface)(S32-1). The user selects an item to be presented to the media renderer from the list of the provided objects(S32-2). If meta data of the selected item includes supplementary expression information, the supplementary expression information is interpreted and a corresponding additional selection operation is performed(S32-3). An action for preparation for connection is requested from the media server and the media renderer for a main component and an auxiliary component that have acquired protocol information and URL(Universal Resource Locator) information, and then, instant IDs with respect to participating elements required for presentation by streaming between devices are received(S33-1,S33-2). The CP individually sets access position information, namely, URL information, about each components at an AVTransport service(S34), and requests a single reproduction action with respect to the components from the AVTransport service by using an argument of a defined instantID(S35). The AVTransport service checks a list of instant IDs of the input argument and allows the components with respect to a particular connection specified by all the instant IDs belonging to list to be streamed or downloaded, and the streamed or downloaded components are synchronized by a rendering module, decoded and outputted(S36).

Description

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

1A is a configuration diagram of a general UPnP AV network,

FIG. 1B illustrates a signal flow between devices in a media playback process performed in the network of FIG. 1A.

1C illustrates the syntax of a temporary ID used in a playback action.

FIG. 2 is an example of networked devices that perform structuring of item information and device-to-device signaling for content with associated supplemental content, in accordance with the present invention;

3A illustrates a signal flow between devices in a media playback process of a plurality of components in the network of FIG.

3B illustrates the syntax of a temporary ID used in a playback action according to an embodiment of the present invention.

FIG. 4 schematically illustrates the structure of item information that is constructed including information about auxiliary content presented in cooperation with the corresponding content.

5A to 5C illustrate examples of creating additional expression information of FIG. 4 according to various embodiments of the present disclosure.

FIG. 6 illustrates an example of creating item information for content that is not presented alone but is presented auxiliary in cooperation with other components.

FIG. 7A illustrates an example of outputting auxiliary content to be interlocked with a selected main component on a list for user selection.

FIG. 7B illustrates an example of outputting a plurality of auxiliary contents that are linked to and reproduced in the selected primary component as a list for selection to the user.

8 illustrates an inquiry and setting action of a value of a synchronous rendering state variable according to the present invention,

9 is a diagram illustrating a procedure of requesting a playback after grouping individual connections according to another embodiment of the present invention.

FIG. 10A illustrates an example of management information for grouping individual connections that a connection manager service provided in a device establishes. FIG.

FIG. 10B illustrates a conceptual diagram in which temporary IDs for group and individual connections are organized according to the management information constructed in FIG. 10A.

※ Explanation of code for main part of drawing

110,210: control point 120,220: media server

130,230: Media Renderer

The present invention relates to a method for managing information about content sources stored in any device on a network, for example, a UPnP-based network, and processing information between network devices according to the information.

The proposed UPnP ^TM (hereinafter abbreviated as "UPnP") based network for home networking logically consists of a number of UPnP devices, services and control points (CPs). . In a UPnP network, a service means the smallest small control unit on the network, which is modeled through a state variable.

In a UPnP-based network, control point (CP) refers to a control application with the ability to detect and control other devices and / or services, and any device, for example, a physical device such as a user-friendly PDA. It is operated by.

In the UPnP-based AV home network, as illustrated in FIG. 1A, a media server (MS) 120 providing media data to a home network and a media renderer (MR) for playing media data through a home network are provided. A media renderer (130) and an AV control point (CP) 110 for controlling the media server 120 and the media renderer 130 are configured. The media server 120 and the media renderer 130 are controlled devices controlled by the control point 110.

The media server 120 (exactly, the CDS 121 (ContentDirectory Service) in the server 120) pre-builds the information of the media files and containers (corresponding to the directory) stored therein as object information. Put it. 'Object' is a term used to collectively refer to an item having information about one or more media files and a container having information on a directory. In some cases, an object may be an item or a container as appropriate. . One item may correspond to a plurality of media files. For example, multiple media files with the same content at different bit rates are managed as one item.

FIG. 1B illustrates a brief signal flow between devices for a media playback process performed in the network of FIG. 1A. First, the control point (CP) 110 obtains information about a protocol that can be accepted by the media renderer (MR) 130 (S01). The media server (MS) 120 informs the control point 110 of the directory and the media file under the directory, UPnP action (141), for example browsing according to the user's request Whenever there is a (browsing) action (S10), information about the current directory and item information about media files under the directory are notified.

The CP 110 excludes information on an item that does not conform to an acceptable protocol provided by the media renderer 130 from the information on each received object and displays it through a suitable UI to the user (S11-1). When the user selects one item (or one media file of a certain quality belonging to the item) through the UI (S11-2), the selected media file (hereinafter referred to as a 'component' or 'media component'). Participation elements required for presentation by streaming between the devices 120 and 130 by requesting a connection preparation action (PrepareForConnection ()) to the media server 120 and the media renderer 130 for the presentation of each. Receive a temporary ID (Instance ID) for (CM, AVT, RCS) (S12-1, S12-2). This temporary ID is used to later specify and control the current streaming service. In addition, the CP 110 transmits the access location information of the previously selected component, for example, Universal Resource Locator (URL) information, through the action of the AVTransport service 133 (in the example of FIG. 130, but may be included in the media server 120. After setting (S13), one AVTransport service temporary ID in ui4 (unsigned integer 4 bytes) format as defined in FIG. 1C is inputted. By requesting a playback action as a factor to the AVTransport service 133 (S14), data of the selected component is streamed and presented by the RCS 131 through an appropriate information exchange process between the media renderer 130 and the media server 120. Display output (S15).

If one additional media file is to be presented during the presentation (S15), the above-described steps (S11-2, S12-1, S12-2, S13, S14) are performed after the presentation starts. This must be done again. In some cases, S10 and S11-1 may also be performed.

However, the method of sequentially performing the two or more media components may be performed in a case where two or more media components are to be synchronously played back in association with each other. Component '), for example, when one media component is a movie and the other component is a subtitle of the movie, it is difficult to apply. This is because, in the case of sequential playback, synchronous presentation may be difficult or impossible in the media renderer depending on time delay.

It is an object of the present invention to provide a signal processing method between devices according to the structured information and to structure the information on the items so that the presentation of the mutually related media components to be presented in cooperation with each other.

According to an aspect of the present invention, there is provided a method of presenting content through data transmission between two devices, the method comprising: acquiring connection information by calling a connection preparation action for each component belonging to multiple components, and connection information obtained for each component; And invoking a play request action comprising the list of input arguments.

According to an embodiment of the present invention, there is provided a method of presenting content, the method comprising: receiving a play request action for multiple components, checking a value of a state variable and determining a starting point of rendering of data of the multiple components according to the value; Making a decision.

According to the present invention, a method for presenting content includes calling an action for querying a state variable indicating whether synchronous rendering of multiple components is performed, and according to a value of the state variable queried by the action. And calling an action to set the value of the state variable.

In one embodiment according to the present invention, the list of connection information is information in which temporary IDs obtained for each component belonging to multiple components are separately listed as delimiters.

In one embodiment according to the present invention, an action for setting the state variable indicating whether or not synchronous rendering is called before the play request action is called.

In one embodiment according to the present invention, the state variable indicating whether synchronous rendering is a variable managed by a RenderingControl service that controls the rendering of video and / or audio data.

According to an embodiment of the present invention, when the state variable is a value indicating synchronous rendering, the amount of data of each component belonging to a multi-request requested component is such that mutual synchronous playback can be seamlessly performed. Causes rendering to start when buffered.

According to another aspect of the present invention, there is provided another method of presenting content through data transmission between two devices, the method comprising: invoking an action for setting a state variable used to control synchronous rendering of multiple components; And a second step of invoking a play request action for.

In one embodiment according to the present invention, the play request action includes a list of connection information obtained for each component belonging to a multi-component as an input argument.

In another embodiment according to the present invention, the play request action includes connection group information in which individual connection information corresponding to each component belonging to multiple components is grouped as an input factor.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

2 is a simplified example of networked devices that perform the structure of item information and device-to-device signal processing for a component having an associated component according to the present invention. The network of FIG. 2 is a UPnP-based AV network and includes a control point 210, a media server 220, and a media renderer 230. In the description of the present invention, networked devices based on the UPnP standard will be described. However, the following description can be applied to other network standards by adaptively replacing necessary elements according to the difference of the standard. Is not dependent on UPnP-based networks.

According to the present invention, the structure of the item information for the multi-component is performed by the CDS 221 in the media server 220, the signal processing for the multi-component according to the present invention is an example, the control point 210 Based on, it is performed according to the process illustrated in FIG. 3A.

On the other hand, the configuration and signal processing of the device illustrated in Figs. 2 and 3 is shown for the pull method in two ways of streaming media components, that is, push mode and pull method. However, the difference between the push and pull method is that the device with the AVTransport service for streaming playback management or the device used is different, and accordingly, the direction of the action is different depending on whether the action is a media server or a media renderer. Since the method of performing the action described below is the same in the push and pull method, the interpretation of the claims of the present invention is not limited to the method illustrated in the drawings and the description.

The CDS 221 (which may be one processor running software) in the media server 220 may search for media files stored in a large amount of storage such as a hard disk. Item information about components, that is, meta data about each component or a group of components, is written in a specific language. In this case, one item information is generated for the media files related to the interworking presentation as one content. 4 shows the structure of the item information generated by this method. That is, as shown, the resource element (<resource>) as in the prior art for the main component (for example, AV stream) or the main components of each component considered to belong to one item is selected. In addition to the item property information 401 that is included, the additional expression information 402 that designates various combinations of user experiences and information on auxiliary components (eg, subtitles, voice, etc.) or auxiliary components of each component. Is additionally created.

The CDS 221 recognizes the correlation between each media file and whether it is a main component or an auxiliary component, for example, from the name and / or extension of each file. And / or information about what is coded may also be obtained from the extension of the file. In addition, if necessary, the corresponding file may be opened to be grasped from the header information in the file, and previously written (by another application program, etc.) for the recorded media files (or files included in a removable recording medium provided separately). The above information can be easily obtained from the db stored in the same medium for the files.

5A shows an example of creating the additional presentation information 402 according to an embodiment of the present invention. According to the illustrated embodiment of FIG. 5A, the element <userExperienceExpression> for the additional presentation information 402 is configured as, for example, three elements. The first element 510 is a <primary resource> for the main component, and assigns IDs to the main component or the main components included in the resource element in the item property information 401. It is an element for. In the example of FIG. 5A, IDs 1 to n are assigned to n primary components, respectively (511).

The second element 520 is a resource element (<additional resource>) for the auxiliary component. The second element 520 is an element for assigning IDs to the auxiliary components presented in association with the primary component and recording protocol and location information for access. . In the example of FIG. 5A, IDs from n + 1 to n + k are allocated to k auxiliary component packages (521). The reason for assigning ID to a package having at least one component without assigning one ID for each auxiliary component is that there are components that can be normally presented when a plurality of components (media files) are combined. In the example of FIG. 5A, the files of "Terminator.sub" and "Terminator.idx" include image information for captions in the former, AV data (eg, "Terminator.mpeg") and Terminator in the latter. Since the timing information for synchronizing the subtitle information in the sub is contained, the components of both files are allocated to one component package and one identifier (n + 1) is allocated (522).

The third element 530 is an experience element (<User Experience>) for a combination (i.e., user experience) combination of the primary component and the secondary component, which is the first element 510 and the second element 520. Represents a possible presentation combination of components, each assigned an identifier. In the example of FIG. 5A, the main components presentable for the current item are 1 and 3, and the auxiliary components are n + 1, n + 4, n + 5 (531), and the presentable combination is the main component. If the interoperable auxiliary component for 1 is n + 1 and n + 4 and is not specifically selected by the user, it is shown that the default interoperable component is n + 1 (532). And, the presentation combinable set may be continuously added by the <capability> element. The example of FIG. 5A illustrates the case where two sets are combinable.

In addition, a plurality of elements of <capability> may be assigned to one main component. Of course, the IDs of the main components in each <capability> element at this time are the same, but the IDs of the corresponding auxiliary components (or auxiliary component packages) are different from each other. As such, an example in which a plurality of elements of <capability> may be created for one main component may include a plurality of auxiliary components for subtitles for one main AV component, and an auxiliary component for voices having different languages. This is the case of plural numbers. As described above, when a plurality of <capability> elements are created for one main component, information about attributes of auxiliary components belonging to each <capability> element may be written as a parameter of <capability>.

Information of the created item as illustrated in FIGS. 4 and 5A is transmitted from the CDS 221 to the CP 210 in response to a browsing action or search action and interpreted, and the CP 210 according to the interpretation. Properly provide the user with information for selection. This will be described later.

The embodiment of FIG. 5A is created by inserting protocol information (“protocolInfo”) for an auxiliary component and location information for accessing the component, for example, URL information, into item information of directly related content. However, in another embodiment of the present invention, indirect information may be recorded so that the information may be identified instead of protocol and URL information about the auxiliary component related to the main component. This indirect information can be, for example, the ID of an object assigned to the associated auxiliary component. FIG. 5B shows additional expression information created according to the present embodiment under the same conditions as in FIG. 5A. As illustrated in FIG. 5B, an object ID for the corresponding auxiliary component is created instead of protocol and URL information for the component (541).

For the embodiment of FIG. 5B, the CDS 221 is a component that is not presented alone but is presented to another component in a process of identifying the stored media files and the storage tree structure thereof (which is described above. As mentioned above, it is confirmed by the extension of the file, etc.) is also configured as an object, and item information for each object is created in the form as illustrated in FIG. However, these objects need to be managed differently than objects of a component that can be presented alone, so they are designated as a separate type 601, for example "object.item.TTOItem". In the example of FIG. 6, as mentioned in the description of FIG. 5A, for a group of auxiliary components that are not capable of normal presentation alone (or become meaningless presentations) and whose normal presentation is possible only by mutual information. Item information is created by assigning to one object. The item information created in FIG. 6 is linked to the indirect information 542 of the auxiliary component on the additional representation information created in FIG. 5B by the object ID, that is, obj1234 602.

In another embodiment according to the present invention, the protocol information of the auxiliary component and the information on the URL of the component are used by mixing the direct information writing method of FIG. 5A and the indirect information writing method of FIG. 5B. Fig. 5C shows an example of the additional expression information created accordingly. As shown, the protocol information and URL information for the additional component are directly written or the object ID for the auxiliary component (or auxiliary component package) is written. Of course, the components for recording the object ID should be assigned as an object as illustrated in FIG. 6 and item information for the object should be created. As in the present embodiment, since information on the auxiliary component may be recorded by mixing each other directly or indirectly, in the resource element (<additionalComponentRes>) for the auxiliary component so that the CP 210 can easily distinguish it, By additionally writing information about the type of the source representation form, i.e., "direct" or "indirect" (551), the CP 210, which interprets the metadata for the object, can easily make protocol information and URL information for the auxiliary component. After the item information for the stored files is constructed according to the above-described method or one of the above-described methods, as shown in FIG. 3A, the information about each item is stored in the CP 210. Is transmitted from the CDS 221 to the CP 210 by a browsing action or a search action (S31). Of course, as shown in FIG. 3A before the action, the CP 210 requests and obtains protocol information acceptable to the media renderer 230 (S30).

The CP 210 provides only the objects (items) having the protocol information acceptable to the media renderer 230 to the user through the appropriate UI (User Interface) in the information of the objects received in step S31 (S32-). One). At this time, if there is an item whose type is "object.item.TTOItem" as shown in Fig. 6, the item is not presented to the user. In another embodiment according to the present invention, an item whose type is "object.item.TTOItem" may be displayed to the user in lighter color than other types of items so as to be distinguished from each other.

Meanwhile, the user selects an item (or one component among a plurality of components having different bit rates belonging to the item) to be presented to the media renderer 230 from the provided list of objects (S32-2). However, if additional expression information (information corresponding to the <userExperienceExpression> element in FIGS. 5A to 5C) exists in the metadata of the selected item, an action for presentation on the component of the selected item is not immediately performed. The additional expression information is interpreted to perform the additional selection operation accordingly (S32-3).

The CP 210 first identifies an element of <User Experience> that describes a presentable combination in the metadata of the selected item. The ID of the component currently selected within that element (this ID can be found in the <primary resource> element of the primary component in the supplementary presentation information.) Is not specified in the <componentList> element. Immediately request the actions (PrepareForConnection (), SetAVTransportURI (), Play (), etc.) sequentially, and if it is listed, the type of the secondary component for that component, followed by the ID of the same primary component Check in the <capability> element to present the user with a list of auxiliary components. 7A is one display example thereof. FIG. 7A shows an example in which a component (or component package) of ID n + 1 and n + 4, which are auxiliary components associated with it, is selected 701 by selecting a component having ID 1 as the primary component, and the default component is an ID. Since this is a component of n + 1, it shows that the selection bar is placed on the secondary component specified by default when listing. In the example of FIG. 7A, each component is classified by ID of a component for convenience, but information displayed to an actual user may include a file name or an object title corresponding to the component (as shown in FIG. 6. Case).

If there are a plurality of combination elements (<capability>) for the selected main component, as shown in FIG. 7B, a selection window 702 is presented for each <capability> element to display the auxiliary component (or component package) in the corresponding window. Will be chosen. As shown in FIG. 7B, when presenting a plurality of combination elements to a user, attributes of each combination element, for example, information indicating whether a caption or voice may be displayed together on the top of the selection window.

According to the above-described process, when the selection of the primary component and the secondary component is finished, the CP 210 obtains protocol information and URL information about the selected component from related elements, i.e., the conventional scheme for the primary component. The auxiliary component is obtained from the <additional resource> element described above for the auxiliary component. 5B and 5C, when information on a corresponding component is designated in an indirect manner, the CP 210 acquires corresponding protocol information and URL information using the indirect information, that is, the object ID as index information. . For example, if the metadata of the corresponding object ID is received by the previous browsing operation, the CDS includes a search action written in the metadata, and if not received, information including the object ID as an input argument. By requesting 221, desired protocol information and URL information are obtained from the corresponding element (<additionalComponent> element in the example of FIG. 6) created in the received metadata.

If the protocol information of the secondary component obtained in the above process does not conform to the acceptable protocol of the media renderer 230 obtained above, the auxiliary component is ignored and presented to the media renderer 230. It does not perform the operation described below. Instead, it may output a notification message to the user, such as "The selected secondary component cannot be represented in the media renderer!".

For the primary component and the secondary component from which the protocol information and the URL information are obtained, first, a connection preparation action (PrepareForConnection ()) is requested to the media server 220 and the media renderer 230 separately, that is, for each component, to stream between devices. Receive temporary IDs (Instance IDs) for participating elements required for presentation by S33-1 and S33-2. These temporary IDs are used later to specifically control each component in the streaming service to be performed. The example of the signal processing flow of FIG. 3A is an example in which two auxiliary components (or one auxiliary component package) are related to one main component, and three identical actions (eg, inputs of actions) between devices are used. argument) is written for each component and therefore has different information.

Upon receiving the temporary ID for the connection of each component by the connection preparation action, the CP 210 separately sets access location information, for example, URL information, for each component previously selected in the AVTransport service 233. In step S34, a single playback action is requested to the AVTransport service 233 for the components. In this case, an argument of instanceID defined in FIG. 3B is used according to the present invention (S35). The instanceID argument defined in FIG. 3B corresponds to a comma separated variable list of ui4s in which one or more ui4 format identifiers are separated by commas. Of course, in each field separated by a comma, a temporary ID for the AVTransport service is inserted among the temporary IDs obtained by the above connection preparation action.

The AVTransport service 233 of the media renderer 230 that has received this play action checks the list contained in the instanceID of the input argument and displays components for the connection specified by all temporary IDs belonging to the list. Streaming or downloading is done through an appropriate exchange of information. The components streamed or downloaded as described above are decoded and outputted in synchronization with each other by the rendering module 231a including each corresponding decoder (or integrated function decoder) under the control of the RenderingControl service 231 (S36).

However, depending on the state of the network, all the components requested to be played are not delivered from the media server 220 to the media renderer 230 at the same rate, and a specific component may be delivered with a greater amount of time than other components, or may be played. One of the requested components may be delayed in transmission compared to other components. When this happens, the playback request is made at the same time, but in the actual presentation, the content may be played without the presentation of any one component for some time after the play starts (if the transmission start of one component is delayed) ), Or after some time after the start of the interlocking playback, either component may not be presented (if the interlocking play has started while the data of some components has not been buffered for enough time for seamless playback) There is also.

Accordingly, in order to implement a fully interoperable presentation, the RenderingControl service 231 defines a state variable for controlling synchronous rendering, for example, a variable having a name of 'ActiveSynchronousHandling' and the value of this variable. Adjust the starting point of the rendering of multiple components. For example, if the value of this state variable is 'TRUE', the RenderingControl service 231 will not allow the data of each component received under the control of the AVTransport service 233 until a sufficient amount is buffered for seamless playback. After waiting, when the amount of data of each component reaches a predetermined time, for example, a presentation time of 1 minute or more, the rendering module 231a is instructed to start decoding at the same time, thereby playing the interworking multiple components. Make it stable. If the value of the state variable is 'FALSE', if one component satisfies the buffering amount condition, decoding of the received or received component is started from then on.

Accordingly, the CP 210 sets the state variable to set the synchronous rendering state variable to TRUE in the RenderingControl service 231 as illustrated in FIG. 8 before or immediately after the request S14 of the previous playback action. The action is called (S801). This action is loaded into an input argument (StateVariableValuePairs) containing a variable-value pair in which the value of the synchronous rendering state variable (ActiveSynchronousHandling) is set to 'TRUE' so that the state variable is set to TRUE in the RenderingControl service 231a You will be notified. Of course, the action requesting to set the state variable may not be requested to the RenderingControl service 231 at the time of playing the multi-component according to the setting option of the multi-component play action of the user.

Instead of calling the state variable setting action directly, the CP 210 calls an action (GetStateVariables ()) for inquiring state variables currently set in the RenderingControl service 231 as shown in FIG. 8. (S800) In step S801, the action of checking the value of the synchronous rendering state variable in the output arguments of StateVariableValuePairs received therefrom and setting the value of the synchronous rendering state variable as described above is called only when the value is FALSE. It may be.

The synchronous rendering state variable according to the present invention may be applied to other methods for synchronous reproduction of multiple components. In the above-described embodiment, the temporary IDs for each individual connection are called in the form of a play request action in the form of a list for play for synchronous playback of the multiple components. In another embodiment, individual components belonging to the multi-component are grouped together. The play request action of multiple components may be called using a temporary ID for the grouped connection group. In this method, the above-described synchronous rendering state variable may be applied and used in the same way. This will be described in more detail below.

9 exemplarily illustrates a procedure for reproducing a request after grouping individual connections according to another embodiment of the present invention. In the drawings, steps S30, S31, and S32-1 to S32-3 are the same steps as those described with reference to FIG. 3A, and thus descriptions thereof will be omitted. The CP 210 performs the following connection preparation operation on the primary component and the secondary component from which the protocol information and the URL information are obtained in the same manner as described above. Actions for connection preparation are called for each connection group and individual connection. That is, as illustrated in FIG. 9, after the group connection preparation action (PrepareGroupConnection ()) for the connection group is called to the CM services 222 and 232 of each device (the media server 220 and the media renderer 230). (S93-1, S93-2), request a connection preparation action (PrepareForConnection ()) for the individual connection for each component to the media server 220 and the media renderer 230 separately, that is for each component between devices Receive temporary IDs (Instance IDs) for participating services required for presentation by streaming (S94-1, S94-2).

The temporary ID of each participating service (CM, AVT, or RCS) for each connection of each component by the connection preparation action (this temporary ID is referred to as a set of IDs assigned for each service or a temporary ID for convenience). If there is no formula of the individual service in the description of, the temporary ID means a set of temporary IDs for each of the services allocated for one connection. To group the temporary IDs for the connections, add a group join action (AddtoGroup ()) to associate the temporary IDs for each individual connection with the temporary IDs for the group connections received by the group connection preparation action. As many requests are made (S95-1, S95-2). The input argument of each group join action includes a temporary ID for the connection group and a temporary ID for one individual connection to be included in the connection group.

In the embodiment of FIG. 9, after calling the group connection preparation action for a connection group (S93-1, S93-2), the connection preparation action for each connection is called for each component (S94-1, S94-2). However, the calling order of this action may be reversed. In other words, before performing the group join action, the group ready preparation action and the connection preparation action for the individual connection are performed regardless of the order, so that the temporary ID for the individual connection to be joined to the group and the temporary ID for the connection group are set. It is enough if it is provided.

Upon receiving the action for the temporary ID connection, the CM service 222 or 232 provides management information for mapping the temporary ID for the connection group included in each group subscription action and the temporary ID for the individual connection. Build. FIG. 10A illustrates an example of management information for grouping individual connections, established by the ConnectionManager service 232 in the media renderer 230 (the media renderer 230 of FIG. 2 includes an AVTransport service 233). Since the temporary ID for the AVTransport service is also provided as a response in response to the connection preparation action, the temporary ID for the connection also includes the temporary ID of the AVTransport service.), FIG. The temporary IDs illustrate the structured conceptual diagram.

By constructing the mapping information as shown in Fig. 10A, each ConnectionManager service 222, 232 sends a service request for action control to playback management or rendering control from the CP 210 by a temporary ID of a subsequent connection group. By identifying the temporary IDs of the individual connections, the corresponding resources can be specified.

Meanwhile, in the above-described embodiment, the CP 210 receives the temporary ID by one action before receiving all the temporary IDs for each connection as needed by the individual connection preparation action for the selected components. If immediately, the action (AddtoGroup ()) may be performed to join the connection to the connection group previously set by the group connection preparation action. In other words, the execution of the group join action AddtoGroup () may be performed regardless of whether the response of the connection preparation action (PrepareForConnection ()) of another connection is received.

After grouping individual connections by the above-described operation, an action (SetAVTransportURI ()) for setting the access location information, for example, URL information, for the component to the AVTransport service 233 for each component selected above is performed. Call individually (S96). The playback action is called to the AVTransport service 233. At this time, the temporary ID (Instance_GrAVTID) of the AVTransport service for the connection group received is used (S97). The temporary ID of the AVTransport service for the connection group of this action is mapped to the temporary ID of the AVTransport service for the individual connection by the ConnectionManager service 232 and transmitted to the AVTransport service 233 so that playback operation for each individual connection can be started at the same time. To be able. Accordingly, data of each selected component is streamed or downloaded through an appropriate information exchange process between the media renderer 230 and the media server 220, and is controlled by the rendering module 231a under the control of the RenderingControl service 231. The interworking is decoded and output (S98).

As mentioned above, simultaneous playback requests for multiple components do not necessarily guarantee the start of mutually synchronized rendering of multiple components. Therefore, in the embodiment of Fig. 9, the action of setting the value of the state variable (ActiveSynchronousHandling) indicating whether the above-described synchronous rendering is set to TRUE is preferably called to the RenderingControl service 231 before the call to the playback action. do. If the state variable is set to TRUE by this call, the RenderingControl service 231 instructs the rendering module 231a to start rendering when each component of the multiple components is fully buffered. Of course, as in the description of the embodiment of Figure 3a, it is also possible to call the play action without setting the state variable to TRUE, even if you want to set the state variable to TRUE as shown in Figure 8 It is also possible to call the action to query first to check the value of the state variable and selectively call the action of setting the state variable to TRUE according to the checked value.

Meanwhile, in the description of the embodiment of FIG. 9, the action of setting the URL of each component (SetAVTransportURI ()) is called after the group join action, but the order of these actions is only one example, and the action of setting the URL is It may be called before the group join action (AddtoGroup ()). In other words, the order of both is not constrained.

Or more, preferred embodiments of the present invention described above, for the purpose of illustration, those skilled in the art, within the technical spirit and the technical scope of the present invention disclosed in the appended claims below, to further improve various other embodiments Changes, substitutions or additions will be possible.

The present invention described as a limited embodiment of the present invention, in a situation in which data is transmitted and presented between devices interconnected via a network, has one main component with a secondary component associated therewith, By being performed at the same time, the coordinated reproduction of the media component is normally and surely performed. Accordingly, the user can increase the satisfaction of viewing or listening to the content by the auxiliary component.

Claims (18)

In the method of presenting content through data transmission between both devices, Step 1 of acquiring connection information by calling a connection preparation action for each component belonging to multiple components, And invoking a play request action including a list of connection information obtained for each component in an input argument. The method of claim 1, The list of the connection information, the temporary IDs obtained for each component, are listed separately from each other as a delimiter (delimiter). The method of claim 2, Wherein the temporary ID is an ID assigned to a service managing the play of the component. In the method of presenting content through data transmission between both devices, Step 1, which calls an action that sets a state variable used to control the synchronous rendering of multiple components, And invoking a play request action for the multiple components. The method of claim 4, wherein The action of setting the state variable is invoked for a service controlling the rendering of the multiple components. The method of claim 4, wherein Prior to said step, further comprising invoking an action to query the value of a state variable used to control the synchronous rendering of said multiple components. The method of claim 4, wherein And before the step 2, calling an action for setting access location information for each component. The method of claim 4, wherein The play request action includes a list of connection information obtained for each component belonging to the multi-component as an input argument. The method of claim 4, wherein The play request action includes connection group information in which individual connection information corresponding to each component belonging to the multi-component is included as an input argument. In the method of presenting content, Receiving a play request action for multiple components; Checking a value of a state variable and determining a start point of rendering for the data of the multi-requested request according to the value. The method of claim 10, In the second step, when the value of the state variable is a value indicative of synchronous rendering, the start of rendering is performed when the amount of data of each component belonging to the multi-component is buffered so that mutual synchronous playback can be seamlessly performed. How to determine by time. The method of claim 10, The play request action includes a list of identification information corresponding to each component belonging to the multi-component as an input argument. The method of claim 10, The play request action may include connection group information in which individual connection information corresponding to each component of the multiple components is grouped as an input argument. The method of claim 10, And before the step 2, receiving an action for requesting to set the value of the state variable to a value indicating synchronous rendering. The method of claim 10, The state variable is a variable managed by a service that controls the rendering of video and / or audio data. In the method for presenting content, A first step of calling an action for querying a state variable indicating whether synchronous rendering of multiple components is performed; And invoking an action for setting a value of the state variable according to the value of the state variable queried by the action. The method of claim 16, Wherein steps 1 and 2 are performed for a service that controls the rendering of video and / or audio data. The method of claim 17, Invoking a play request action for the multiple components after invoking the lookup action or the set action.

Images