Apparatus and method for matching protocols of embedded audio/video contents

The present invention relates to a Remote User Interface (RUI) technology on a form network, and more specifically, of embedded AV content for UI data containing AV content internally between RUI devices. It relates to a protocol matching device and method for embedded AV content that enables the protocol matching process to be executed at the same time as the profile matching process between RUI devices.

Between conventional Remote User Interface (hereinafter referred to as RUI) devices, the protocol matching process for AV (Audio Video) content embedded in the UI data transfers the AV content. It is additionally required at the time of reproduction. Here, the AV content may be a video, audio, image, or the like included in the HTML page in the form of a tag.

FIG. 1 is a diagram showing the structure of the UI data 10 transmitted to the RUI client, and the UI data 10 contains various forms of objects. Embedded AV content 20 is also one of such objects, and UPnP performs AV control based on AV Contents URI (Uniform Resource Identifier) 21 and UPnP, which are position information for bringing the AV content. It can be divided into AV CP modules 22. The UI data 10 is processed by receiving input of a control command such as play and stop of the AV content by the user, and a typical example of such UI data 10 is a web on the Internet. It can be a web page displayed using a browser.

Embedded AV content 20 embedded in the UI data 10 in the form of an object tag can be included inside the UI data used in XHTML-based Remote UI-related standards such as CEA-2014. The object tag may include a "param" element, through which additional information about the AV content corresponding to the object can be provided.

On the other hand, the RUI device includes a RUI server and a RUI client. Of these, the device description (Device Description) of the RUI server describes <rui uiServerInfo>, which is information for the RUI server, in the form of a tag. , Profile Matching should be performed based on the profile included in the XML file indicated by the URL (Uniform Resource Locator) described in <rui uiListURL> included in the <rui uiServerInfo> tag. become. The <rui uiListURL> may contain information about ui_profile name, audio_profile name, video_profile name and so on.

Similarly, the device description of the RUI client contains <rui uiClientInfo>, which is information for the RUI client, in the form of a tag, and the <rui uiClientInfo> tag has one or more profile lists. Obtained, each profilelist can include profiles for ui, audio, video. In particular, the video profile can include profile name, aspect ratio, transport, and so on.

FIG. 2 is a diagram showing a profile matching process between RUI devices. The RUI CP50 performs a search (Discovery) and control (control) process on the RUI client 40 and the RUI server 60 (S11), and confirms the ui profile that the RUI client 40 can provide to the RUI server 60. Perform the UI profile matching process, which is the process of checking whether the ui profile worthy of the list of RUI server 60 is included (S12). When the profile matching process is completed, the UI data is transmitted from the RUI server 60 to the RUI client 40 (S13). With this, the RUI server 60 receives a request for event processing from the RUI client 40, processes the event according to the request, and notifies the RUI client 40 (S14). Control commands such as play and stop for the AV content contained in the UI data are performed together with the AV content protocol matching process described later.

FIG. 3 is a diagram showing a protocol matching process of AV content based on the RUI device.

After the profile matching process of FIG. 2 is completed, the RUI server 60 receives and acquires URI information that can approach the AV content from the media server 30 before generating the UI data 10 (S21). Such an acquisition method can be changed depending on the embodied method between the media server 30 and the RUI server 60. Here, http://server.com/av.mpg may be an example of the URI information. The UI data 10 generated including the AV content having the URI information is transmitted from the RUI server 60 to the RUI client 40 (S22), and the RUI client 40 shows the UI data to the user through the rendering process. The user requests the AV CP50 to control the AV content using the RUI client 40 (S23), and the AV CP50 included in the media player starts the AV content control (AV Contents Control) by the request. become. Media player and AV Although the CPs are not the same device, they can be embodied together as one device as shown in FIG. 3, or can be embodied as separate devices.

When the AV content control is started, the AV CP 50 requests the media server 30 for protocol information (S24), and the media server 30 provides the protocol information to the AV CP 50 at the request (S25). The AV CP50 extracts protocol information that can be provided by the media player (S26), and matches the extracted protocol information with the protocol information proposed by the media server 30 (S27). When the protocol matching process is completed, the AV CP50 calls the AV content from the media server 30 using the URI for the AV content contained in the UI data (S28), thereby controlling the AV content desired by the user. Will be able to execute.

However, in the above-mentioned method, profile matching between RUI devices and protocol matching for AV contents included in UI data are duplicated for UI data transmission. Therefore, if the UI data contains n AV contents, the protocol information extraction process must be performed up to n times through the network for each AV content, which slows down the control speed for the AV contents and puts it on the network. There is a problem that excessive traffic can be weighted.

<p> The present invention has been devised to solve the above-mentioned problems, and the problem to be solved by the present invention is a protocol for confirming whether or not AV content embedded in UI data can be controlled. By improving the conventional method of performing the matching process separately from the UI profile matching process and simultaneously performing protocol matching of the AV content at the time of UI profile matching, separate protocol information is extracted at the time of actual AV content control. It is an object of the present invention to provide a protocol matching device and method for embedded AV contents, which can improve the efficiency of protocol matching of AV contents without performing the process of performing the above.</p><p> The object of the present invention is not limited to the object mentioned above, and other purposes not mentioned above will be clearly understood by those skilled in the art from the following description.</p>

<p> The protocol matching device for embedded AV content according to the present invention for achieving the above-mentioned object includes a RUI (Remote User Interface) server that receives URI information for AV content embedded in UI data and protocol information for the AV content. A RUI client that receives the UI data generated by using the URI information and the protocol information from the RUI server, and a media that receives the protocol information and a control request command for the AV content from the RUI client. It includes an AV CP that performs a control operation on the AV content by matching the protocol information acquired from the player with the transmitted protocol information.</p><p> Further, the protocol matching method of the embedded AV content according to the present invention for achieving the above-mentioned object is as follows: (a) The RUI (Remote User Interface) server uses the URI information for the AV content embedded in the UI data and the AV content. The stage of receiving the protocol information, (b) the stage of the RUI server transmitting the received URI information and the UI data generated by using the protocol information to the RUI client, and (c) the stage of the RUI client , The step of parsing and storing the URI information and the protocol information for the AV content embedded in the transmitted UI data.</p><p> Specific matters of other embodiments are included in the detailed description and figures.</p>

<p> In the case of the above-described embodiment of the present invention, there are the following effects.</p><p> The RUI device that sends and receives UI data based on UPnP AV does not perform protocol matching duplicately at each control point for the AV content embedded in the UI data, and extracts AV protocol information in advance at the time of UI profile matching. By saving inside the RUI client, the control speed of AV content can be improved.</p><p> In addition, by extracting the protocol information each time the AV content is controlled, it is possible to reduce the generation of unnecessary network traffic and improve the overall network efficiency.</p><p> In addition, the present invention can be implemented without modifying the UPnP AV specifications by adding the definition of the element of the object tag when constructing the UI data.</p><p> The effects of the present invention are not limited to the effects mentioned above, and other effects not mentioned above will be clearly understood by those skilled in the art from the description of the scope of claim.</p>

<figref num="1">It is a figure which shows the structure of the UI data transmitted to the RUI client by the prior art.</figref><figref num="2">It is a figure which shows the profile matching process between RUI apparatus by a prior art.</figref><figref num="3">It is a figure which shows the protocol matching process of the embedded AV content based on the RUI apparatus by the prior art.</figref><figref num="4">It is a figure which shows the structure of the embedded AV content which contains the protocol information by one Embodiment of this invention.</figref><figref num="5">It is a block diagram of the protocol matching apparatus of the embedded AV content by one Embodiment of this invention.</figref><figref num="6">It is a figure which shows the structure of the cache part which stores the protocol information by one Embodiment of this invention.</figref><figref num="7">It is a conceptual diagram which shows the protocol matching process of the embedded AV content by one Embodiment of this invention.</figref><figref num="8">It is a flowchart of the protocol matching method of the embedded AV content by one Embodiment of this invention.</figref>

The advantages, features, and methods of achieving them of the present invention will become clear with reference to the embodiments described in detail below with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, and can be embodied in various forms different from each other. The present embodiment is provided solely for the purpose of fully informing a person having ordinary knowledge in the technical field to which the present invention belongs, so that the disclosure of the present invention is complete. The invention is defined only by the scope of the claims. It should be noted that throughout the specification, the same reference numerals refer to the same components.

Hereinafter, a block for explaining a protocol matching device and a method for embedded AV content defined in advance by a desirable embodiment of the present invention will also be described in more detail with reference to a flowchart.

In the embodiment of the present invention, for convenience of explanation, the description is made based on the UPnP Remote User Interface (Remote UI: hereinafter referred to as RUI) system, which can be said to be an application of UPnP (Universal Plug and Play), to realize the present invention. For the device, the name of the device specified in the UPnP RUI specifications is mainly used. However, it is obvious to those skilled in the art that the scope of rights of the present invention is not affected by the names of the form network system and the device.

FIG. 4 is a diagram showing a configuration of embedded AV content including protocol information according to an embodiment of the present invention. Referring to FIG. 4, the embedded AV content 150 is included in the UI data 100, and the protocol information 160 defined in the UPnP AV specifications is added to the element of the object tag constituting the embedded AV content 150. You can see that it is doing. This makes it possible to apply the embodiment of the present invention described later without modifying the UPnP AV specifications.

FIG. 5 is a configuration diagram of a protocol matching device for embedded AV content according to an embodiment of the present invention. Referring to FIG. 5, the embedded AV content protocol matching apparatus according to the embodiment of the present invention includes a RUI client 400, a RUI server 600, a media server 300, an AV CP500, and a media player 550 connected to the cache unit 200. Is included and configured.

The RUI server 600 receives the URI information for the AV content 150 embedded in the UI data 100 and the protocol information (Protocol Info) for the AV content from another media server 300 storing the AV content. Here, the RUI server 600 can be a device that can generate UI events and save UI data like a desktop PC or a notebook PC as one of the controlled devices specified in the UPnP AV specifications. The protocol for AV content can be said to be a convention for allowing the RUI client 400 to output the UI data 100 of the RUI server 600. Examples thereof include RDP (Remote Desktop Protocol), HTTP, and XHT. It can be a protocol. On the other hand, the RUI server 600 can be embodied as one device with the media server 300, and can exist as a separate device.

The RUI client 400 receives the transmission of the UI data 100 from the RUI server 600, and the UI data 100 can be generated by using the URI information and the protocol information. Here, the RUI client 400, as another controlled device (Controlled Device) specified in the UPnP AV specifications, is located in another location remotely adjusted by a desktop PC or notebook PC that can be the RUI server 600. It can be a PC or a digital TV that can display the UI events.

After receiving the UI data 100 from the RUI server 600, the RUI client 400 parses the URI information and the protocol information for the AV content 150 embedded in the UI data 100 and stores the URI information and the protocol information in the cache unit 200. Will be. The cache unit 200 later serves to provide protocol information stored at the request of the AV CP 500. The cache unit 200 may include a separate local storage area (not shown), and the protocol information may be stored in the cache unit 200 in the form of a kind of mapping table, which will be described with reference to FIG. To do.

FIG. 6 is a diagram showing a structure of a cache unit that stores protocol information according to an embodiment of the present invention. The data stored inside the cache unit 200 includes the content URI 210 and the content protocol information 220 in the form of a mapping table, and the content protocol information 220 includes a protocol (Protocol: 221) and a network (Network: 222). , Content Format (223), and Additional Info (224) are stored separately. For example, protocol information expressed in the form of "http-get: *: application / x-dtcp1; CONTENTFORMAT = video / MP2T: *" is divided into Protocol, Network, Format, and Additional Info and stored. ..

On the other hand, referring to FIG. 5 again, the RUI client 400 can have at least one or more profile lists inside a tag indicating information about itself (for example, &lt;rui uiClientInfo&gt;). It can consist of profile information for ui, audio, and video. In particular, the profile information for the video can clearly indicate the profile name (profile name), screen ratio (aspect ratio), and transmission method (transport), but in the case of the transmission method, the space is separated and listed by space. Displayed as value. Therefore, one or more transmission methods can be selectively used, and such selection is performed by the AV CP 500 at the time of control of the AV content.

The user can input control commands such as playback and recording for the AV content included in the UI data 100 through the RUI client 400, but the RUI client receives the input of the user's control request command. The 400 will extract the protocol information corresponding to the AV content from the cache unit 200 again. The extracted protocol information is transmitted to the AV CP 500 together with the control request command.

The AV CP500 is a device for controlling AV content as a control point defined by the UPnP AV specifications, unlike the RUI CP50 shown in FIG. 2 of the prior art. That is, after receiving the transmission of the protocol information and the control request command for the AV content from the RUI client 400, the control operation for the AV content is performed by matching the protocol information acquired from the media player 550 with the transmitted protocol information. It is a device that performs. Based on the matching result, the AV CP500 transmits a control message (Control Msg.) Such as bringing the AV content from the media server 300 to the media player 550 and causing the media player 550 to play or record the AV content. The media player 550 that has received the control message can bring the AV content from the media server 300, but can also bring the URI information of the AV content from the UI data 100 and control the AV content.

The AV CP500 can be embodied as one device with the media player 550, or can be embodied as one device with the RUI client 400, and the RUI client 400, the media player 550, and the AV CP500 are all one. It can also be embodied as one device. Of course, each may exist as a separate device.

FIG. 7 is a conceptual diagram showing a protocol matching process of embedded AV content according to an embodiment of the present invention.

The protocol matching of the AV content described in one embodiment according to the present invention is a process of combining the protocol matching method specified in the conventional UPnP AV specifications and the profile matching operation between RUI devices, and the protocol matching is performed at the time of performing the UI profile matching. Perform parallel operations in advance. The operation will be described with reference to FIG. 7.

First, the media server 300 storing the AV content transmits the URI information and the protocol information of the AV content required for UI data generation to the RUI server 600 (S102). Here, the URI information is displayed in a format such as "http://server.com/av.mpg", and the protocol information is "http-get: *: application / x-dtcp1; CONTENTFORMAT = video / MP2T". It can be displayed as ": *".

The RUI server 600 generates UI data using the transmitted URI information and protocol information, and transmits the UI data to the RUI client 400 (S104). At this time, the embedded AV content is transmitted together, but the RUI client 400 parses the transmitted protocol information and stores it in the cache unit 200. Since the method of saving in the cache unit 200 is the same as the above-described explanation of FIG. 6, it is omitted here.

On the other hand, if the user inputs a control command such as execution, stop, or recording to the AV content through the RUI client 400, the RUI client 400 requests the AV CP 500 to execute the control command (S106). Now, the control operation for the AV content starts, but the RUI client 400 extracts the protocol information corresponding to the AV content from the cache unit 200 (S108) and transmits the extracted protocol information to the AV CP500 (S110). ..

Upon receiving the transmission of the protocol information, the AV CP500 confirms whether or not it has the ability to play the AV content from a media player that can be embodied as one device or exist as a separate device from itself. Therefore, the protocol information of the media player is extracted (S112). Such an extraction process can be performed internally differently depending on the realization of the AV CP500 and the media player.

The AV CP500 performs protocol matching by comparing the protocol information acquired from the media player with the protocol information transmitted from the RUI client 400 (S114). As a result of the protocol matching, the AV CP500 can confirm whether or not the media player can execute a control operation such as playing the AV content, and it is determined that the AV CP500 can execute a specific control operation. In this case, the AV CP500 receives the AV content provided by the media server 300 (S116) and transmits the AV content to the media player.

FIG. 8 is a flowchart of a protocol matching method for embedded AV content according to an embodiment of the present invention.

First, the RUI server 600 receives the URI information for the AV content and the protocol information for the AV content from the separate media server 300 (S210). The RUI server 600 transmits the received URI information and the UI data generated by using the protocol information to the RUI client 400 (S220).

Then, the RUI client 400 parses the URI information and the protocol information for the AV content from the transmitted UI data and stores them in the cache unit 200 (S230). At this time, the cache unit 200 can separate the protocol information into a protocol (Protocol), a network (Network), a format (Format), and additional information (Additional Info) and store them in the form of a mapping table.

The RUI client 400 receives an input of a user's control request command for the AV content, and after extracting the protocol information corresponding to the AV content from the cache unit 200 by the command, AV the command together with the extracted protocol information. Transmit to CP500 (S240).

The AV CP500 will perform a protocol matching operation in which protocol information for the AV content is acquired from the media player and compared with the transmitted protocol information (S250). Based on the matching result, the AV CP500 can bring the AV content from the media server 300 and play it.

On the other hand, the scope of rights of the protocol matching method for embedded AV content according to the embodiment of the present invention does not extend to a recording medium that can be read by a computer that records a program code for executing the above method on a computer. It is self-evident to those skilled in the art.

Although the embodiments of the present invention have been described with reference to the accompanying drawings, a person having ordinary knowledge in the technical field to which the present invention belongs does not change the present invention in terms of its technical idea and essential features. It can be understood that it can be implemented in other specific forms, as it can be replaced, modified and modified in various forms. Therefore, it should be understood that the above embodiments are exemplary in all respects and are not limiting. The scope of the present invention is indicated by the scope of claims, which will be described later rather than the detailed description, and the meaning, scope, and all modified or modified forms of the scope of patent claims derived from the concept of equality thereof are the present invention. Must be interpreted as being included in the scope of.

100 UI data 150 AV content 200 cache section 300 media server 400 RUI client 500 AV CP 550 media player 600 RUI server