Patent Description:
Recording mediums for recording and playing back high quality image and audio data, such as DVDs and Blu-ray discs, are widely used. Further, various display apparatuses which can display high quality image and audio data are widely distributed.

Accordingly, the use of digital TV in conjunction with various DVD and Blu-ray players that record or play content from respective recording mediums, has increased. Further the high-speed multimedia interface (HDMI) may be used as a digital interface to transmit data between such devices.

Devices that support HDMI may provide high resolution image and audio, and may support high-bandwidth digital content protection (HDCP) to prevent copying of content.

Further, recent content providers have shown some movement in adopting HDCP version <NUM> by classifying high resolution content as premium content when providing high resolution content such as <NUM> content and 3D content in full HD. Accordingly, related display apparatuses which only support less than HDCP version <NUM> have an issue in that compatibility with high resolution content, to which HDCP version <NUM> is applied, cannot be obtained.

<CIT> discloses a method for generating a communication link between devices, and apparatus for same. "<NPL>describes an interface independent adaption of the HDCP system. <CIT> describes a method and system for secure and efficient wireless transmission of HDCP-encrypted HDMI/DVT signals.

Exemplary embodiments of the present inventive concept aim to overcome the above disadvantages and other disadvantages not described above. Also, the present inventive concept is not required to overcome the disadvantages described above, and an exemplary embodiment of the present inventive concept may not overcome any of the problems described above.

According to an aspect of an exemplary embodiment, there is provided a source device for transmitting content to a sink device, the source device may include an interface configured to perform high-bandwidth digital content protection (HDCP) authentication with the sink device, and a controller configured to determine an HDCP version supported by the sink device, convert the content so as to be encrypted in the HDCP version supported by the sink device in response to a determination that another HDCP version applied to the content is not supported by the sink device, encrypt the converted content in the HDCP version supported by the sink device, and control the interface to transmit the content to the sink device.

The content may be premium content required to be encrypted in a first HDCP version, and the HDCP version supported by the sink device may be a second HDCP version which is lower than the first HDCP version.

The controller may convert the content so as to be encrypted in the HDCP version supported by the sink device by reducing resolution of the content through downscaling.

The controller may determine the HDCP version supported by the sink device based on whether HDCP authentication can be performed with the sink device according to a method respectively defined in the HDCP version supported by the sink device and the HDCP version applied to the content.

The controller may request transmitting information regarding the HDCP version previously stored in the sink device, and wherein the controller may determine the HDCP version supported by the sink device based on the received information regarding the HDCP version from the sink device.

The controller may encrypt the content in the HDCP version applied to the content and transmits the content to the sink device in response to a determination that the HDCP version applied to the content is supported by the sink device.

The controller may control the sink device to output a message indicating that the content is converted in response to the converted content being transmitted to the sink device.

According to an aspect of another exemplary embodiment, there is provided a sink device for outputting content provided from a source device, the sink device may include an interface configured to perform high-bandwidth digital content protection (HDCP)authentication with the source device, and a controller configured to control the interface to transmit previously stored information regarding a HDCP version supported by the sink device to the source device in response to a request, from the source device, for information regarding the HDCP version supported by the sink device being received.

A storage may be configured to store information regarding the HDCP version supported by the sink device in an extended display identification data (EDID) format.

According to an aspect of another exemplary embodiment, there is provided a method of transmitting content from a source device to a sink device, the method may include determining a high-bandwidth digital content protection (HDCP)version supported by the sink device, converting the content so as to be encrypted in the HDCP version supported by the sink device in response to a determination that another HDCP version applied to the content is not supported by the sink device, and encrypting the converted content in the HDCP version supported by the sink device and transmitting to the sink device.

The converting may include converting the content so as to be encrypted in the HDCP version supported by the sink device by reducing resolution of the content through downscaling.

The determining may include determining the HDCP version supported by the sink device based on whether HDCP authentication can be performed with the sink device according to a method respectively defined in the HDCP version supported by the sink device and the HDCP version applied to the content.

The determining may include requesting transmission of previously stored information regarding the HDCP version stored on the sink device, and determining the HDCP version supported by the sink device based on the received information regarding the HDCP version from the sink device.

The method may further include encrypting the content in the HDCP version applied to the content and transmitting the content to the sink device in response to a determination that the HDCP version applied to the content is supported by the sink device.

The method may further include controlling the sink device to output a message indicating that the content is converted in response to the converted content being transmitted to the sink device.

According to an aspect of another exemplary embodiment, there is provided a method of controlling a sink device for outputting content provided from a source device, the method may include receiving a request for information regarding a high-bandwidth digital content protection (HDCP)version supported by the sink device from the source device, and transmitting previously stored information regarding the HDCP version supported by the sink device to the source device in response to the request for transmitting information regarding the HDCP version being received.

The sink device may store information regarding the HDCP version supported by the sink device in an extended display identification data (EDID) format
According to the present invention there is provided an apparatus and method as set forth in the appended claims.

For a better understanding of the invention, and to show how embodiments of the same may be carried into effect, reference will now be made, by way of example, to the accompanying diagrammatic drawings in which:.

Certain exemplary embodiments will now be described in greater detail with reference to the accompanying drawings.

In the following description, same drawing reference numerals are used for the same elements even in different drawings. The matters defined in the description, such as detailed construction and elements, are provided to assist in a comprehensive understanding of the present inventive concept. Accordingly, it is apparent that the exemplary embodiments of the present inventive concept can be carried out without those specifically defined matters. Also, well-known functions or constructions are not described in detail because they may obscure one or more exemplary embodiments with unnecessary detail.

Referring to the attached drawings, one or more exemplary embodiments will be described in detail below.

<FIG> is a view provided to explain a content providing system according to an exemplary embodiment. Referring to <FIG>, the content providing system may include a source device <NUM> and a sink device <NUM>.

Herein, the source device <NUM> may be implemented as various types of electronic devices that can provide content to the sink device <NUM>, such as set-top box, DVD player, Blu-ray disc player, PC, or game machine. The sink device <NUM> may be implemented as various types of electronic devices that can output content provided from the source device <NUM>, such as a television (TV) and personal computer (PC).

Further, the source device <NUM> and the sink device <NUM> may connect to each other through a high-speed multimedia interface (HDMI) and perform communication.

The source device <NUM> and the sink device <NUM> may perform high-bandwidth digital content protection (HDCP) authentication according to the HDCP protocols in order to prevent copying of content without a license.

Specifically, the source device <NUM> may encrypt and transmit content to the sink device <NUM> according to a previously stored key select vector of host device (AKSV), and the sink device <NUM> may decrypt and output the content according to previously stored key select vector of display device (BASV).

Each device <NUM> and <NUM> may generate pseudo-random values at a preset time, e.g., pseudo-random value generated by the source device <NUM> is Ri and pseudo-random value generated by the sink device <NUM> is Ri'. Further, the source device <NUM> may receive the pseudo-random value generated by the sink device <NUM>, from the sink device <NUM>, during a certain period, and may determine whether the received value may be uniform with pseudo-random value generated internally.

Therefore, the source device <NUM> may continuously transmit content to the sink device <NUM> when it is determined that pseudo-random values are uniform, and stop transmitting content when it is determined that pseudo-random values are not uniform.

In order to perform HDCP authentication as described above, two operations may be done as follows. The first operation that may be performed may be a first part of an authentication protocol in which it is determined whether the source device <NUM> and the sink device <NUM> are proper for protecting content with each other, which is confirmed by generating and comparing initial pseudo-random values. Next, the second operation that may be performed is a third part of authentication protocol in which pseudo-random values generated by both devices are compared continuously thereafter, e.g., every two seconds.

According to such operations, the source device <NUM> and the sink device <NUM> may perform HDCP authentication according to the HDCP protocol.

According to an exemplary embodiment, the source device <NUM> may encrypt and transmit content to the sink device <NUM> by considering the HDCP version supported by the sink device <NUM>.

The following will specifically explain detailed composition of the source device <NUM> and the sink device <NUM>.

<FIG> is a block diagram of the source device according to an exemplary embodiment. Referring to <FIG>, the source device <NUM> may include an interface <NUM> and a controller <NUM>.

The interface <NUM> may transmit content to the sink device <NUM> by performing communication with the sink device <NUM> of <FIG>.

In this case, the interface <NUM> may perform HDCP authentication with the sink device <NUM>.

The interface <NUM> may be implemented as HDMI. Specifically, the interface <NUM> may include a transition-minimized differential signaling (TMDS) channel link which R, G, B signals and clock signals are approved, DDC communication line for dual way I<NUM>C communication, and pin connected with HPD sensing line to sense an HDMI connection. Further, the interface <NUM> may include a memory storing AKSV, and an engine performing authentication according to the HDCP protocol.

Therefore, when it is determined that the sink device <NUM> connects according to HPD signals, the interface <NUM> may perform HDCP authentication with the sink device <NUM>. Further, the interface <NUM> may encrypt and transmit content to the sink device <NUM> if HDCP authentication is successful, and stop transmitting content if HDCP authentication fails.

The controller <NUM> may control general operation of the source device <NUM>. The controller <NUM> may include a microcomputer (or microcomputer and central processing unit (CPU)), a random access memory (RAM) for operation of the display apparatus <NUM>, and a read only memory (ROM). In this case, such modules may be implemented as a system on chip (SoC).

The controller <NUM> may determine the HDCP version which the sink device <NUM> supports. Herein, the HDCP version may be various versions defined in the HDCP protocol such as HDCP version <NUM>. X (e.g., HDCP version <NUM>) and HDCP version <NUM>. X (e.g., HDCP version <NUM>).

Further, the controller <NUM> may determine whether HDCP authentication can be performed with the sink device <NUM> according to a method defined respectively in the HDCP version supported by the sink device <NUM> and the HDCP version applied to the content, and confirm the HDCP version supported by the sink device <NUM>. Herein, the HDCP version applied to the content may be various versions defined in the HDCP protocol such as HDCP version <NUM>. X (e.g., HDCP version <NUM>) and HDCP version <NUM>. X (e.g., HDCP version <NUM>).

For example, assuming that the HDCP version applied to the content is HDCP version <NUM> and the HDCP version supported by the sink device <NUM> is HDCP version <NUM>. In this case, the controller <NUM> may determine whether HDCP authentication can be performed according to HDCP version <NUM> by controlling the interface <NUM> to perform HDCP authentication with the sink device <NUM> according to a method defined in HDCP version <NUM>. Therefore, the controller <NUM> may determine that the sink device <NUM> supports HDCP version <NUM> if HDCP authentication can be performed with the sink device <NUM> according to HDCP version <NUM>, and may determine that the sink device <NUM> does not support HDCP version <NUM> if HDCP authentication cannot be performed according to HDCP version <NUM>.

Likewise, the controller <NUM> may determine whether HDCP authentication can be performed according to HDCP version <NUM> by controlling the interface <NUM> to perform HDCP authentication with the sink device <NUM> according to a method defined in HDCP version <NUM>. Therefore, the controller <NUM> may determine that the sink device <NUM> supports HDCP version <NUM> if HDCP authentication can be performed according to HDCP version <NUM>, and may determine that the sink device does not support HDCP version <NUM> if HDCP authentication cannot be performed according to HDCP version <NUM>.

Therefore, the controller <NUM> may assume that the sink device <NUM> supports HDCP version <NUM> or HDCP version <NUM>, determine whether HDCP authentication can be performed with the sink device <NUM> according to each HDCP version, and confirm HDCP version supported by the sink device <NUM> according to which is actually supported.

Further, the controller <NUM> may request transmitting previously stored information regarding the HDCP version in the sink device <NUM>, and determine HDCP version supported by the sink device <NUM> based on the received information of the HDCP version.

For the above operation, the sink device <NUM> may store information regarding the HDCP version of its own as extended display identification data (EDID). In this case, the controller <NUM> may determine the HDCP version supported by the sink device <NUM> by receiving EDID from the sink device <NUM> with DDC communication line.

Further, the sink device <NUM> may store information regarding the HDCP version supported in its own RAM. In this case, the controller <NUM> may determine the HDCP version supported by the sink device <NUM> by receiving information regarding the HDCP version from the sink device <NUM>.

When it is determined that the HDCP version applied to the content is not supported by the sink device <NUM>, the controller <NUM> may convert the content so as to be encrypted in an HDCP version supported by the sink device <NUM>, encrypt the converted content to HDCP version supported by the sink device <NUM>, and control the interface <NUM> to transmit to the sink device <NUM>.

Herein, content may be premium content to be encrypted in a first HDCP version. However, the HDCP version supported by the sink device <NUM> may be a second HDCP version which is lower than the first HDCP version. For example, content may be premium content to be encrypted in HDCP version <NUM>. X, and HDCP version supported by the sink device <NUM> may be HDCP version <NUM>.

For the above, the controller <NUM> may determine the HDCP version applied to the content. Specifically, the controller <NUM> may determine the HDCP version applied to content based on whether content is premium content or not.

Herein, premium content is content requested for hard protection such as <NUM> content, 3D content in full HD, and sealed content, and the HDCP protocol defines that HDCP version <NUM>. X is applied to premium content.

Therefore, the controller <NUM> may determine whether content is premium content or not based on resolution and type of content, or determine whether content is premium content or not by extracting information indicating whether corresponding content is premium content from packet header constituting content.

Further, the controller <NUM> may determine whether content is premium content or not based on a user command. For example, when a user command indicating that content is premium content is inputted, the controller <NUM> may determine that corresponding content is premium content.

Thus, when it is determined that content is premium content, the controller <NUM> may determine that the HDCP version applied to content is HDCP version <NUM>.

When it is determined that content is premium content to which HDCP version <NUM>. X is applied while HDCP version supported by the sink device <NUM> is HDCP version <NUM>. X, the controller <NUM> may convert content so as to be encrypted in the HDCP version that the sink device <NUM> supports.

Specifically, the controller <NUM> may convert content so as to be encrypted in the HDCP version supported by the sink device <NUM> by reducing resolution of content through downscaling. For this process, the source device <NUM> may include a scaler.

The reason why HDCP protocol defines that HDCP version <NUM>. X is applied to <NUM> content is that content having high original resolution such as <NUM> content should be protected with a harder method. Therefore, when resolution of <NUM> content decreases by downscaling, HDCP version <NUM>. X should not necessarily be applied even if following the HDCP protocol.

Thus, the controller <NUM> may control reducing resolution of content by downscaling, performing HDCP authentication with the sink device <NUM> in HDCP version supported by the sink device <NUM> regarding content having the reduced resolution, and encrypting and transmitting content.

When following the HDCP protocol, premium content should be applied with HDCP version <NUM>. However, when the sink device does not support HDCP version <NUM>. X, the source device cannot perform HDCP authentication with the sink device according to HDCP version <NUM>. X applied to premium content. Therefore, users of the sink device that does not support HDCP version <NUM>. X cannot view premium content provided from the source device.

However, according to an exemplary embodiment, because the source device <NUM> reduces resolution of premium content so that HDCP version supported by the sink device <NUM> can be applied, the source device <NUM> can keep compatibility with the sink device <NUM> that does not support HDCP version <NUM>. X applied to premium content.

For example, assume that HDCP version supported by the sink device <NUM> is HDCP version <NUM>, and content is <NUM> content to which HDCP version <NUM> is applied.

In this case, the controller <NUM> may downscale <NUM> content having resolution of <NUM> x <NUM> to be resolution of <NUM> x <NUM>. Thereby, because HDCP version <NUM> should not necessarily be applied to content having the reduced resolution of <NUM> x <NUM>, the controller <NUM> may perform authentication with the sink device <NUM> according to HDCP version <NUM> supported by the sink device <NUM>, encrypt the downscaled content, and transmit to the sink device <NUM>.

The above exemplary embodiment describes <NUM> content; however, this is merely one of the possible exemplary embodiments. Thus, as well as <NUM> content, the controller <NUM> may control reducing resolution of 3D content in full HD and sealed content so that HDCP version supported by the sink device can be applied.

Further, the above exemplary embodiment describes that resolution of content is reduced; however, this is also merely one of the possible exemplary embodiments. Thus, as well as reducing resolution of content through downscaling, the controller <NUM> may reprocess content so that HDCP version supported by the sink device can be applied. For example, when both HDCP version <NUM>. X and HDCP version <NUM>. X can be applied to content, and the sink device <NUM> supports HDCP version <NUM>. X, the controller <NUM> may encrypt content according to HDCP version <NUM>. X without separate converting and transmit to the sink device <NUM>. However, this is merely one of the possible exemplary embodiments; the controller <NUM> may also reprocess content according to various methods such as modifying data format so that HDCP version supported by the sink device can be applied, encrypt the reprocessed content according to HDCP version supported by the sink device, and transmit to the sink device.

When it is determined that the HDCP version applied to content is supported by the sink device <NUM>, the controller <NUM> may encrypt content in HDCP version applied to content, and transmit to the sink device <NUM>. Thus, when it is determined that HDCP version <NUM>. X applied to premium content is supported by the sink device <NUM>, the controller <NUM> may perform authentication with the sink device <NUM> according to HDCP version <NUM>. X without separate processing, encrypt the content, and transmit to the sink device <NUM>.

The controller <NUM> may downscale premium content by using related methods. However, considering the point that resolution of content can be reduced in this case, the controller <NUM> may downscale premium content by using the method illustrated in <FIG>.

The controller <NUM> may downscale each frame constituting premium content into four frames constituted with lower frames. Specifically, the controller <NUM> generates a first frame by extracting pixels at odd series of horizontal and vertical lines in each frame of the premium content, generates a second frame by extracting pixels at even series of horizontal lines and odd series of vertical lines in each frame of the premium content, generates a third frame by extracting pixels at odd series of horizontal lines and even series of vertical lines in each frame of the premium content, and generates a fourth frame by extracting pixels at even series of horizontal and vertical lines in each frame of the premium content.

For example, the controller <NUM> may downscale each frame of <NUM> content having resolution of <NUM> x <NUM> into four frames having resolution of <NUM> x <NUM> as illustrated in <FIG>.

Further, the controller <NUM> may encrypt the downscaled content in the HDCP version supported by the sink device <NUM> and transmit to the sink device <NUM>. In this case, the sink device <NUM> may receive the downscaled content, restore original resolution that premium content has and output. Therefore, a user can view content without deteriorating in resolution.

In case converted content is transmitted to the sink device <NUM>, the controller <NUM> may control the sink device <NUM> to output a message informing that content is converted.

Thus, when the source device <NUM> reduces resolution of premium content and transmit to the sink device <NUM> by considering the HDCP version supported by the sink device <NUM>, a user may view content having deteriorated resolution compared to original resolution.

Therefore, the controller <NUM> may control the sink device <NUM> to output a message informing that content having the reduced resolution is outputted, and thus, can inform a user of outputting content having the reduced resolution. In this case, the controller <NUM> may transmit graphic data constituted with a corresponding message to the sink device <NUM>, or a controlling command to output graphic data previously stored in the sink device <NUM> to the sink device <NUM>.

As described above, when it is determined that the HDCP version applied to content is not supported by the sink device <NUM>, the controller <NUM> may convert content so as to be automatically encrypted in HDCP version supported by the sink device <NUM> without a separate user command, and transmit to the sink device <NUM>. However, when a separate user command is inputted, the controller <NUM> may convert content into the HDCP version supported by the sink device <NUM> and transmit to the sink device <NUM>.

Further, the controller <NUM> may control the sink device <NUM> to output a message informing that content cannot be outputted. Thus, when it is determined that the HDCP version applied to content is not supported by the sink device <NUM>, the controller <NUM> may transmit graphic data constituted with a message informing that content cannot be outputted to the sink device <NUM> without converting content so as to be encrypted in the HDCP version supported by the sink device <NUM>. Further, the controller <NUM> may transmit a controlling command to output graphic data previously stored in the sink device <NUM> to the sink device <NUM>.

<FIG> is a detailed block diagram of the source device according to an exemplary embodiment. Referring to <FIG>, the source device <NUM> may further include a content provider <NUM> as well as the interface <NUM> and the controller <NUM>. The content provider <NUM> may be controlled by the controller <NUM>. Among the units illustrated in <FIG>, an overlapping part with the units illustrated in <FIG> will not be described herein.

The content provider <NUM> may provide content transmitted to the sink device <NUM>, and may be implemented as various types according to exemplary embodiments.

For example, the content provider <NUM> may be implemented to include a tuner, a demodulator, and a equalizer, and may receive broadcasting content transmitted from broadcasting stations. Further, the content provider <NUM> may read content recorded on an optical disc such as DVD and Blu-ray disc. The content provider <NUM> may receive content from external recording medium such as a USB memory and a HDD.

Thereby, the controller <NUM> may control transmitting content delivered from the content provider <NUM> to the sink device <NUM> by considering the HDCP version supported by the sink device <NUM>.

As well as the units illustrated in <FIG>, the source device <NUM> may further include a storage storing various programs used for operating the source device <NUM>, an inputter to receive a user command, and a remote controller signal receiver to receive remote controller signals corresponding to a user command.

<FIG> is a block diagram of a sink device according to an exemplary embodiment. Referring to <FIG>, the sink device <NUM> may include an interface <NUM> and a controller <NUM>.

The interface <NUM> may receive content from the source device <NUM> by performing communication with the source device <NUM> of <FIG>.

In this case, the interface <NUM> may perform HDCP authentication with the source device <NUM>.

For the above, the interface <NUM> may be implemented as HDMI. Specifically, the interface <NUM> may include TMDS channel link which R, G, B signals and clock signals are approved, DDC communication line with dual way for I<NUM>C communication, and pin connected with HPD sensing line to sense an HDMI connection. Further, the interface <NUM> may include a memory to store BKSV, and a HDCP engine to perform authentication according to HDCP protocol.

Therefore, when it is determined that the source device <NUM> connects according to HPD signals, the interface <NUM> may perform HDCP authentication with the source device <NUM>. Further, the interface <NUM> may receive the encrypted content from the source device <NUM> when HDCP authentication is successful, and decrypt the received content; however, when HDCP authentication fails, content cannot be received.

The controller <NUM> controls general operation of the sink device <NUM>. The controller <NUM> may include a microcomputer (micom) (or, a micom and a CPU), RAM for operation of the display apparatus <NUM>, and ROM. In this case, such modules may be implemented as a SoC.

When a request for information regarding the HDCP version supported by the sink device <NUM> is received from the source device <NUM>, the controller <NUM> controls the interface <NUM> to transmit prestored information regarding the HDCP version supported by the sink device <NUM> to the source device <NUM>.

For the above, the sink device <NUM> may previously store EDID which includes information regarding the HDCP version that is supported. Thus, the sink device <NUM> may previously store EDID which includes information regarding the HDCP version as well as information regarding manufacturer ID indicating manufacturing company, manufacturing ID indicating model type of a product, image and audio output standards of the sink device <NUM>.

Further, the sink device <NUM> may separately store information regarding the HDCP version supported in its own on RAM.

For example, when it is determined that the source device <NUM> connects according to HPD signals, the controller <NUM> may transmit EDID including information regarding the HDCP version to the source device <NUM>, or transmit information regarding the HDCP version stored in RAM to the source device <NUM>. However, if a separate transmitting request is received from the source device <NUM>, the controller <NUM> may transmit information regarding the HDCP version to the source device <NUM>.

<FIG> is a detailed block diagram of the sink device according to an exemplary embodiment. Referring to <FIG>, the sink device <NUM> may further include an outputter <NUM>, a storage <NUM>, a receiver <NUM>, a signal processor <NUM>, a remote controller signal receiver <NUM> and an inputter <NUM> as well as the interface <NUM> and the controller <NUM>. Such operation may be controlled by the controller <NUM>. Among the units illustrated in <FIG>, an overlapping part with the units illustrated in <FIG> will not be further described.

The outputter <NUM> may output various image and audio data. For this operation, the outputter <NUM> may include a display and an audio outputter.

The display may display image content and the audio outputter may output audio content. For example, when content is received from the source device <NUM> by successfully performing HDCP authentication, the controller <NUM> may decrypt the received content, display the decrypted image content on the display, and output the audio content through the audio outputter.

The display may be implemented as liquid crystal display (LCD), organic light emitting display (OLED), or plasma display panel (PDP), and the audio outputter may be implemented as speaker or audio output port.

The display may output various messages in on screen display (OSD) format. Specifically, the controller <NUM> may generate various messages in OSD format by using graphic data which are received from the source device <NUM> or previously stored in the sink device <NUM>, and output the generated messages through the display. Herein, messages may include a message indicating that resolution of content received from the source device <NUM> changes, and a message indicating that content cannot be outputted.

The storage <NUM> may store various programs used for operation of the sink device <NUM>.

Specifically, the storage <NUM> may store information regarding the HDCP version supported by the sink device <NUM> in EDID format. For this operation, the storage <NUM> may be implemented as flash memory, and electrically erasable and programmable ROM (EEPROM).

Therefore, when a transmitting request for information regarding HDCP version is received from the source device <NUM>, the controller <NUM> may control reading EDID from the storage <NUM> and transmitting to the source device <NUM>.

The receiver <NUM> may receive broadcasting content. Broadcasting content may include image, audio, and additional data (e.g., EPG), and the receiver <NUM> may receive broadcasting content from various sources such as ground wave broadcasting, cable broadcasting, satellite broadcasting, and internet broadcasting.

For example, the receiver <NUM> may be implemented to include a tuner, a demodulate , and a equalizer in order to receive broadcasting content transmitted from broadcasting stations.

The signal processor <NUM> may perform signal-processing regarding content received through the interface <NUM> and the receiver <NUM>. Specifically, the signal processor <NUM> may perform operations such as decoding, scaling, and frame rate converting regarding image constituting content, and signal-process the content so as to be formatted such that it can be outputted on the display.

The remote control signal receiver <NUM> receives remote control controlling signals inputted through a remote control. For example, the remote control signal receiver <NUM> may receive remote control controlling signals corresponding to various user commands in order to control operation of the sink device <NUM>, and the controller <NUM> may perform operation corresponding to the received remote control controlling signals.

The inputter <NUM> may receive various user commands. The controller <NUM> may perform operation corresponding to user commands inputted by the inputter <NUM>. For this process, the inputter <NUM> may be implemented as an inputting panel. The inputting panel may be implemented with a touch pad, or a key pad provided with various function keys, number keys, special keys, and character keys, or a touch screen.

<FIG> is a view provided to explain operation of the content providing system according to an exemplary embodiment. Specific operation of the source device <NUM> and the sink device <NUM> is already described in detail with reference to <FIG>; operation of such composition will be briefly explained.

Referring to <FIG>, the source device <NUM> receives premium content (e.g., <NUM> content) from broadcasting stations, optical disc, and/or USB.

Further, the source device <NUM> determines information regarding the HDCP supported by the sink device <NUM>.

Specifically, the source device <NUM> determines whether HDCP authentication can be performed with the sink device <NUM> according to a method defined in HDCP version <NUM> (see ① of <FIG>), and determines whether HDCP authentication can be performed with the sink device <NUM> according to a method defined in HDCP version <NUM> (see ② of <FIG>).

As a determining result, when it is determined that HDCP authentication can be performed with the sink device <NUM> according to a method defined in HDCP version <NUM>, from among HDCP version <NUM> and HDCP version <NUM>, the source device <NUM> determines that the sink device <NUM> supports HDCP version <NUM>.

Therefore, the source device <NUM> downscales premium content in order to encrypt premium content in HDCP version <NUM>, and to transmit to the sink device <NUM>. For example, the source device <NUM> may downscale <NUM> content having resolution of <NUM> x <NUM> to be resolution of <NUM> x <NUM>.

Thereafter, the source device <NUM> may perform HDCP authentication according to HDCP version <NUM> with the sink device <NUM>, encrypt the downscaled content in HDCP version <NUM>, and transmit to the sink device <NUM>.

Thus, the sink device <NUM> may decrypt and output the received content from the source device <NUM>. In this case, the sink device <NUM> may output a message <NUM> indicating that content having the reduced resolution is being outputted in OSD format.

<FIG> is a flowchart provided to explain operation of the content providing system according to an exemplary embodiment.

First, when the source device <NUM> and the sink device <NUM> connect to each other according to an HDMI communication method at S810, the source device <NUM> and the sink device <NUM> perform connecting communication according to a method defined in HDCP version <NUM> at S820. Thus, the source device <NUM> and the sink device <NUM> determine whether HDCP authentication can be performed according to a method defined in HDCP version <NUM>.

At S830, the source device <NUM> determines whether communication in HDCP version <NUM> is supported and then connects.

However, when connecting communication following the HDCP version <NUM> fails, the source device <NUM> may determine that the sink device <NUM> does not support HDCP version <NUM> at S840.

When connecting communication following the HDCP version <NUM> is successful, the source device <NUM> may determine that the sink device <NUM> supports HDCP version <NUM>.

At S850 and S860, the source device <NUM> determines whether communication in HDCP version <NUM> is connected. Thus, the source device <NUM> determines whether HDCP authentication defined in HDCP version <NUM> can be performed with the sink device <NUM>.

Therefore, when connecting communication following HDCP version <NUM> fails, the source device <NUM> may determine that the sink device <NUM> does not support HDCP version <NUM>. As a result, the source device <NUM> may determine that the sink device <NUM> supports HDCP version <NUM> only at S870.

When connecting communication following HDCP version <NUM> is successful, the source device <NUM> may determine that the sink device <NUM> supports HDCP version <NUM>. As a result, the source device <NUM> may determine that the sink device <NUM> supports both HDCP version <NUM> and HDCP version <NUM> at S880.

When a command to play premium content is inputted at S890 and S910, the source device <NUM> may encrypt premium content according to a version supported by the sink device <NUM> and transmit to the sink device <NUM>.

Specifically, when it is determined that HDCP version <NUM> is supported by the sink device <NUM>, the source device <NUM> may encrypt premium content in HDCP version <NUM> at S920 and transmit to the sink device <NUM> through HDMI at S930.

When it is determined that the sink device <NUM> does not support HDCP version <NUM> but rather only HDCP version <NUM>, the source device <NUM> may downscale premium content at S940, encrypt the downscaled content in HDCP version <NUM> at S950, and transmit to the sink device <NUM> through HDMI at S960.

<FIG> is a flowchart provided to explain a content transmitting method of the source device which transmits content to the sink device according to an exemplary embodiment.

First, HDCP version supported by the sink device is determined at S1010.

Specifically, HDCP version supported by the sink device may be determined based on whether HDCP authentication can be performed with the sink device according to a method respectively defined in HDCP version supported by the sink device and HDCP version applied to content.

Further, a request for information regarding the HDCP version previously stored in the sink device, and the HDCP version supported by the sink device, may help determine the received information regarding the HDCP version from the sink device.

When it is determined that the HDCP version applied to content is not supported by the sink device, content is converted so as to be encrypted in HDCP version supported by the sink device at S1020.

Herein, content may be premium content that may need to be encrypted in the first HDCP version, and HDCP version supported by the sink device may be the second HDCP version which may be lower than the first HDCP version.

Specifically, content may be converted so as to be encrypted in the HDCP version supported by the sink device by reducing resolution of content through downscaling.

At S1030, the converted content is encrypted in the HDCP version supported by the sink device and transmitted to the sink device.

When it is determined that the HDCP version applied to content is supported by the sink device, the content may be encrypted in the HDCP version applied to content and transmitted to the sink device.

Further, when the converted content is transmitted to the sink device, the sink device may be controlled to output a message indicating that content is converted. Further, the sink device may be controlled to output a message indicating that content cannot be outputted.

<FIG> is a flowchart provided to explain a controlling method of the sink device which outputs content provided from the source device according to an exemplary embodiment.

At S1110, from the source device, may be received a request for information regarding the HDCP version supported by the sink device.

When a request for transmitting information regarding the HDCP version is received, previously stored information regarding the HDCP version supported by the sink device may be transmitted to the source device at S1120.

For this process, the sink device may store information regarding the HDCP version supported by the sink device in EDID format.

Further, there may be provided non-transitory computer readable medium storing programs which consecutively implement a menu content providing method and a controlling method according to an exemplary embodiment.

Non-transitory computer readable recording medium may indicate medium which store data semi-permanently and can be read by devices, not medium storing data temporarily such as register, cache, or memory. Specifically, the above various applications or programs may be stored and provided in non-transitory computer readable recording medium such as CD, DVD, hard disk, Blu-ray disc, USB, memory card, or ROM.

Further, although the above block diagrams describing the source device and the sink device do not illustrate a bus, communication between units in the display apparatus can be performed through the bus. Further, processors such as CPU implementing the above various operation and a microprocessor may be provided in each device.

According to the above various exemplary embodiments, even if the sink device supports different version from HDCP version applied to content, the source device may provide content in HDCP version supported by the sink device to the sink device through content converting. Therefore, compatibility with related sink devices can be obtained.

Further, the foregoing exemplary embodiments and advantages are merely exemplary and are not to be construed as limiting the exemplary embodiments. The present teaching can be readily applied to other types of apparatuses. Also, the description of the exemplary embodiments are intended to be illustrative, and not to limit the scope of the claims.

Claim 1:
An electronic device (<NUM>) for transmitting content to a display device (<NUM>), the electronic device comprising:
an HDMI interface (<NUM>); and
a controller (<NUM>) configured to:
when it is determined that the display device is connected to the electronic device via the HDMI interface (<NUM>), determine a high-bandwidth digital content protection version supported by the display device,
process a content based on the identified high-bandwidth digital content protection version supported by the display device, and
transmit the processed content to the display device via the HDMI interface,
wherein the controller is configured to process the content based on the identified high-bandwidth digital content protection version by:
based on the identified content protection version being a first high-bandwidth digital content protection version, encrypting the content based on the first high-bandwidth digital content protection version, and
based on the identified high-bandwidth digital content protection version not being the first high-bandwidth digital content protection version, downscaling the content and encrypting the downscaled content based on a second high-bandwidth digital content protection version,
wherein the second high-bandwidth digital content protection version is lower than the first high-bandwidth digital content protection version.