KR20240086432A - Sink device for providing edid to source device and edid providing method thereof - Google Patents

Abstract

The sync device is started. This sink device includes an HDMI interface for communication with a source device, a memory that stores one or more instructions, and one or more processors that are connected to the interface and memory to control the sink device, and the one or more processors execute one or more instructions. By doing so, when content is received from the source device through the interface, it is identified whether the content corresponds to the EDID of the sink device based on information about the content, and if the content is identified as not corresponding to the EDID of the sink device, HF-EEODB Change the EDID that includes to an EDID that does not include HF-EEODB, and transmit the changed EDID to the source device.

Description

A sink device that provides EDID to a source device and its EDID provision method { SINK DEVICE FOR PROVIDING EDID TO SOURCE DEVICE AND EDID PROVIDING METHOD THEREOF }

This disclosure relates to a sink device that provides EDID to a source device and its EDID provision method.

With recent advances in electronic technology, display devices such as TVs can reproduce high-resolution images.

Meanwhile, the display device can use EDID to provide information about video and audio specifications supportable by the display device to the source device. Additionally, the source device can process content using EDID and transmit it to the display device.

A sink device according to an embodiment of the present disclosure includes an HDMI interface for communication with a source device, a memory for storing one or more instructions, and one or more processors connected to the interface and the memory to control the sink device. When content is received from the source device through the interface by executing the one or more instructions, the one or more processors identify whether the content corresponds to the EDID of the sink device based on information about the content. When the content is identified as not corresponding to the EDID of the sink device by executing the one or more instructions, the one or more processors change the EDID including HF-EEODB to an EDID that does not include the HF-EEODB, and , the changed EDID is transmitted to the source device.

Here, EDID including the HF-EEODB may be composed of four blocks. And, EDID not including the HF-EEODB may be composed of two blocks.

Additionally, the EDID including the HF-EEODB may include a base block, a first CTA extension block, a second CTA extension block, and a DisplayID extension block. And, the HF-EEODB may be included in the first CTA extension block.

And, the EDID that does not include the HF-EEODB may include a base block and a CTA extension block.

In addition, the content includes an image, and the one or more processors determine that, if the resolution of the image received from the source device is lower than the resolution included in the extension block of the EDID of the sink device, the image received from the source device is It can be identified as not corresponding to the EDID of the sink device.

And, the content includes audio, and the one or more processors determine whether the audio received from the source device is not compressed using a compression method supported by the sink device based on metadata about the audio received from the source device. In the case of audio, it can be identified that the audio does not correspond to the EDID of the sink device.

Additionally, if the content is identified as corresponding to the EDID of the sink device, the one or more processors may output the content.

A method of providing an EDID of a sink device that performs HDMI communication with a source device according to an embodiment of the present disclosure is that when content is received from the source device, the content corresponds to the EDID of the sink device based on information about the content. If the content is identified as not corresponding to the EDID of the sink device, changing the EDID including HF-EEODB to an EDID not including HF-EEODB, and changing the changed EDID to the EDID Including transmitting to the source device.

In a non-transitory computer-readable medium that stores computer instructions that cause the source device to perform an operation when executed by one or more processors of a sink device that performs HDMI communication with a source device according to an embodiment of the present disclosure, The operation includes, when content is received from the source device, identifying whether the content corresponds to the EDID of the sink device based on information about the content, and identifying that the content does not correspond to the EDID of the sink device. If so, it includes changing the EDID including HF-EEODB to an EDID not including HF-EEODB and transmitting the changed EDID to the source device.

1 is a diagram illustrating an example of implementation of a source device and a sink device according to an embodiment of the present disclosure;
FIG. 2A is a block diagram illustrating an example of an implementation of a sink device according to an embodiment of the present disclosure;
FIG. 2B is a block diagram showing an implementation example of a display device according to an embodiment of the present disclosure;
FIG. 3 is a diagram illustrating a communication process between a source device and a sink device according to an embodiment of the present disclosure;
4 is a diagram illustrating an example of an EDID structure including HF-EEODB according to an embodiment of the present disclosure;
5 is a diagram illustrating an example of an EDID structure not including HF-EEODB according to an embodiment of the present disclosure;
FIG. 6 is a flowchart illustrating a method in which a sink device changes EDID and transmits it to a source device according to an embodiment of the present disclosure; and
Figure 7 is a flowchart explaining a method of providing EDID of a sink device according to an embodiment of the present disclosure.

Terms used in the present disclosure will be briefly described, and the present disclosure will be described in detail.

The terms used in the embodiments of the present disclosure have selected general terms that are currently widely used as much as possible while considering the functions in the present disclosure, but this may vary depending on the intention or precedent of a person working in the art, the emergence of new technology, etc. . In addition, in certain cases, there are terms arbitrarily selected by the applicant, and in this case, the meaning will be described in detail in the description part of the relevant disclosure. Therefore, the terms used in this disclosure should be defined based on the meaning of the term and the overall content of this disclosure, rather than simply the name of the term.

In the present disclosure, expressions such as “have,” “may have,” “includes,” or “may include” refer to the presence of the corresponding feature (e.g., component such as numerical value, function, operation, or part). , and does not rule out the existence of additional features.

In the present disclosure, expressions such as “A or B,” “at least one of A or/and B,” or “one or more of A or/and B” may include all possible combinations of the items listed together. . For example, “A or B,” “at least one of A and B,” or “at least one of A or B” (1) includes at least one A, (2) includes at least one B, or (3) it may refer to all cases including both at least one A and at least one B.

Expressions such as “first,” “second,” “first,” or “second,” used in the present disclosure can modify various components regardless of order and/or importance, and can refer to one component. It is only used to distinguish from other components and does not limit the components.

A component (e.g., a first component) is “operatively or communicatively coupled with/to” or “connected to” another component (e.g., a second component). When “connected to” is mentioned, it should be understood that a certain component can be connected directly to another component or connected through another component (e.g., a third component).

The expression “configured to” used in the present disclosure may mean, for example, “suitable for,” “having the capacity to,” depending on the situation. ," can be used interchangeably with "designed to," "adapted to," "made to," or "capable of." The term “configured (or set to)” may not necessarily mean “specifically designed to” in hardware.

In some contexts, the expression “a device configured to” may mean that the device is “capable of” working with other devices or components. For example, the phrase "processor configured (or set) to perform A, B, and C" refers to a processor dedicated to performing the operations (e.g., an embedded processor), or by executing one or more software programs stored on a memory device. , may refer to a general-purpose processor (e.g., CPU or application processor) capable of performing the corresponding operations.

Singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, terms such as “comprise” or “consist of” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are intended to indicate the presence of one or more other It should be understood that this does not exclude in advance the presence or addition of features, numbers, steps, operations, components, parts, or combinations thereof.

In an embodiment, a “module” or “unit” performs at least one function or operation, and may be implemented as hardware or software, or as a combination of hardware and software. Additionally, a plurality of “modules” or a plurality of “units” are integrated into at least one module and implemented by at least one processor (not shown), except for “modules” or “units” that need to be implemented with specific hardware. It can be.

Meanwhile, various elements and areas in the drawing are schematically drawn. Accordingly, the technical idea of the present invention is not limited by the relative sizes or spacing drawn in the attached drawings.

Hereinafter, an embodiment of the present disclosure will be described in more detail with reference to the attached drawings.

1 is a diagram illustrating an example of implementation of a source device and a sink device according to an embodiment of the present disclosure.

Referring to FIG. 1, the source device 10 may provide content to the sink device 100. Here, the content may include at least one of video and audio.

For example, the source device 10 can be implemented as various types of electronic devices that can provide video, audio, etc. to the sink device 100, such as a set-top box, DVD player, Blu-ray disc player, PC, game console, etc. there is.

The sink device 100 can output content received from the source device 10.

Specifically, the sink device 100 can display the image received from the source device 10 on the display of the sink device 100. Additionally, the sink device 100 can output the image received from the source device 10 through a speaker. Here, the speaker may be a speaker built into the sink device 100 or may include an external speaker connected to the sink device 100. For example, the sink device 100 may be implemented with various types of electronic devices that can output content, such as a TV or monitor.

The source device 10 and sink device 100 can communicate through HDMI (High Definition Multimedia Interface) to transmit and receive content.

To this end, the source device 10 and sink device 100 may each include an HDMI interface. In this case, the HDMI interface may include an HDMI port. Additionally, one end of the HDMI cable may be connected to the HDMI port of the source device 10, and the other end of the HDMI cable may be connected to the HDMI port of the sink device 100. Accordingly, the source device 10 and sink device 100 can communicate through the HDMI port.

Meanwhile, when transmitting content to the sink device 100, the source device 10 generates content in a format that matches the EDID (Extended Display Identification Data) of the sink device 100 received from the sink device 100, Content can be transmitted to the sink device 100.

EDID may include information about the sink device 100. For example, EDID may include information about the operating characteristics of the sink device 100. The source device 10 receives the EDID from the sink device 100, and sends video and audio that meet the specifications supported by the sink device 100 based on the information about the sink device 100 defined in the EDID to the sink device (100). 100).

FIG. 2A is a block diagram illustrating an example of implementation of a sink device according to an embodiment of the present disclosure.

Referring to FIG. 2A, the sink device 100 includes an HDMI interface 110, a memory 120, and one or more processors 130.

The HDMI interface 110 is configured for communication with the source device 10. The HDMI interface 110 can communicate with the source device 10 using the HDMI communication method. To this end, the interface 110 may include an HDMI port. The HDMI port can be connected to an HDMI cable.

The memory 120 may store data necessary for the sink device 100 to operate according to various embodiments of the present disclosure.

The memory 120 may be implemented as a memory embedded in the sink device 100 or as a memory detachable from the sink device 100 depending on the data storage purpose.

For example, in the case of memory embedded in the sink device 100, volatile memory (e.g., dynamic RAM (DRAM), static RAM (SRAM), or synchronous dynamic RAM (SDRAM), etc.), non-volatile memory ) (e.g. one time programmable ROM (OTPROM), programmable ROM (PROM), erasable and programmable ROM (EPROM), electrically erasable and programmable ROM (EEPROM), mask ROM, flash ROM, flash memory (e.g. NAND flash or NOR flash, etc.), a hard drive, or a solid state drive (SSD).

In addition, in the case of a memory that is removable from the sink device 100, a memory card (e.g., compact flash (CF), secure digital (SD), micro secure digital (Micro-SD), mini secure digital (Mini-SD) , xD (extreme digital), MMC (multi-media card), etc.), external memory connectable to a USB port (for example, USB memory), etc.

Memory 120 may store one or more instructions. In this case, one or more processors 130 may perform the operation of the sink device 100 according to various embodiments of the present disclosure by executing at least one instruction stored in the memory 120. Additionally, the memory 120 may store programs and data for driving the sink device 100.

One or more processors 130 generally control the sink device 100. Specifically, one or more processors 130 may be connected to each component of the sink device 100 and generally control the operation of the sink device 100. For example, one or more processors 130 may be connected to the HDMI interface 110 and the memory 120 to control the sink device 100. One or more processors 130 may be comprised of one or multiple processors.

One or more processors 130 may perform operations of the sink device 100 according to various embodiments by executing at least one instruction stored in memory.

One or more processors 130 include a Central Processing Unit (CPU), Graphics Processing Unit (GPU), Accelerated Processing Unit (APU), Many Integrated Core (MIC), Digital Signal Processor (DSP), Neural Processing Unit (NPU), and hardware. It may include one or more of an accelerator or machine learning accelerator. One or more processors 130 may control one or any combination of other components of the sink device 100 and may perform operations related to communication or data processing. One or more processors 130 may execute one or more programs or instructions stored in memory. For example, one or more processors may perform a method according to an embodiment of the present disclosure by executing one or more instructions stored in memory.

When the method according to an embodiment of the present disclosure includes a plurality of operations, the plurality of operations may be performed by one processor or by a plurality of processors. For example, when the first operation, the second operation, and the third operation are performed by the method according to one embodiment, the first operation, the second operation, and the third operation may all be performed by the first processor. , the first operation and the second operation may be performed by a first processor (eg, a general-purpose processor) and the third operation may be performed by a second processor (eg, an artificial intelligence-specific processor).

The one or more processors 130 may be implemented as a single core processor including one core, or one or more multi-cores including a plurality of cores (e.g., homogeneous multi-core or heterogeneous multi-core). It may also be implemented as a processor (multicore processor). When one or more processors 130 are implemented as multi-core processors, each of the plurality of cores included in the multi-core processor may include processor internal memory such as cache memory and on-chip memory, and may include a plurality of cores. A common cache shared by cores may be included in multi-core processors. In addition, each of the plurality of cores (or some of the plurality of cores) included in the multi-core processor may independently read and perform program instructions for implementing the method according to an embodiment of the present disclosure, and all of the plurality of cores may (or part of) may be linked to read and perform program instructions for implementing the method according to an embodiment of the present disclosure.

When a method according to an embodiment of the present disclosure includes a plurality of operations, the plurality of operations may be performed by one core among a plurality of cores included in a multi-core processor, or may be performed by a plurality of cores. there is. For example, when the first operation, the second operation, and the third operation are performed by the method according to an embodiment, the first operation, the second operation, and the third operation are all included in the multi-core processor. It may be performed by a core, and the first operation and the second operation may be performed by the first core included in the multi-core processor, and the third operation may be performed by the second core included in the multi-core processor.

In embodiments of the present disclosure, a processor may mean a system-on-chip (SoC) in which one or more processors and other electronic components are integrated, a single-core processor, a multi-core processor, or a core included in a single-core processor or a multi-core processor. Here, the core may be implemented as a CPU, GPU, APU, MIC, DSP, NPU, hardware accelerator, or machine learning accelerator, but embodiments of the present disclosure are not limited thereto. Hereinafter, for convenience of explanation, one or more processors 130 will be referred to as processor 130.

FIG. 2B is a block diagram illustrating an example of implementation of a display device according to an embodiment of the present disclosure.

According to Figure 2b, the sink device 100 includes an HDMI interface 110, a memory 120, one or more processors 130, a communication interface 140, an input interface 150, a display 160, and a speaker 170. may include. However, this configuration is an example, and of course, in carrying out the present disclosure, new configurations may be added or some configurations may be omitted in addition to these configurations. Meanwhile, a detailed description of the configuration shown in FIG. 2B that overlaps the configuration shown in FIG. 2A will be omitted.

The communication interface 140 includes circuitry. The communication interface 140 is a component that communicates with an external device. The processor 130 may transmit various data to an external device and receive various data from the external device through the communication interface 140. To this end, the communication interface 140 may communicate with an external device through a wireless communication method such as Bluetooth (BT), Bluetooth Low Energy (BLE), or Wireless Fidelity (WI-FI).

The input interface 150 can receive user commands. To this end, the input interface 150 may include at least one button. Additionally, the input interface 150 may be implemented as a touch screen that can simultaneously perform the functions of the display 160. Additionally, the input interface 150 includes an IR signal receiver (not shown) and can receive an IR signal for controlling the sink device 100 from a remote controller.

The display 160 can display images. To this end, the display 160 may be implemented as various types of displays such as LCD, LED, or OLED. Additionally, the display 160 may be implemented as a flat display, a curved display, a flexible display capable of folding and/or rolling, etc. For example, the processor 130 may process an image signal received from the source device 10 and display it on the display 160.

Speaker 170 can output audio. For example, the processor 130 may convert an audio signal received from the source device 10 into an analog audio signal and output the analog audio signal through the speaker 170.

Hereinafter, a method in which the sink device 100 provides the EDID available by the source device 10 to the source device 10 will be described in more detail with reference to the attached drawings. Meanwhile, the sink device 100 according to the present disclosure can support HDMI 2.1.

When content is received from the source device 10 through the HDMI interface 110, the processor 130 identifies whether the content corresponds to the EDID of the sink device 100 (S310).

Here, that the content corresponds to the EDID of the sink device 100 means that the content provided by the source device 10 matches the EDID of the sink device 100 transmitted by the sink device 100 to the source device 10. It can mean.

For example, although the sync device 100 supports high resolution such as 4k and 8k, the sync device 100 receives low-resolution video (e.g., SD-level video such as 480p and 576p) from the source device 10, or If no video is received from the source device 10, the video received from the source device 10 can be viewed as not corresponding to the EDID of the sink device 100.

For example, when the audio specification supported by the sink device 100 is AC-3 (Dolby), but the sink device 100 receives audio processed by PCM (Pulse Code Modulation) from the source device 10. , the audio received from the source device 10 can be viewed as not corresponding to the EDID of the sink device 100.

Meanwhile, the source device 10 may obtain the EDID of the sink device 100 from the sink device 100 and transmit content to the sink device 100 using the EDID.

FIG. 3 is a diagram illustrating a communication process between a source device and a sink device according to an embodiment of the present disclosure.

Referring to FIG. 3, the HDMI interface 11 of the source device 10 and the HDMI interface 110 of the sink device 100 may be connected through an HDMI cable.

The HDMI cable may include a Transition Minimized Differential Signaling (TMDS) line 310, a Display Data Channel (DDC) line 320, a 5V power line 330, and a Hot Plug Detect (HPD) line 340.

Meanwhile, when the source device 10 is connected to the sink device 100 through an HDMI cable, it can transmit +5V voltage to the sink device 100 through the 5V power line 330. In this case, when +5V voltage is received, the sink device 100 can transmit a high level voltage to the source device 10 through the HPD line 340.

When a high-level voltage is received through the HPD line 340, the source device 10 may transmit a signal requesting transmission of EDID to the sink device 100 through the DDC line 320. The sink device 100 may transmit EDID to the source device 10 through the DDC line 320. For example, the processor 130 may record the EDID stored in the memory 120 into the EDID memory 111. Here, the EDID memory 111 may be implemented as an Electrically Erasable Programmable Read-Only Memory (EEPROM). Accordingly, the source device 10 can read the EDID stored in the EDID memory 111.

Meanwhile, when the EDID is received from the sink device 100, the source device 10 obtains information about the sink device 100 from the EDID and uses the obtained information to meet the specifications supported by the sink device 100. The format of the video and audio can be identified, and the video and audio in the identified format can be transmitted to the sink device 100. In this case, the source device 10 can transmit video signals and audio signals to the sink device 100 through the TMDS line 310.

FIG. 4 is a diagram for explaining an example of an EDID structure including HF-EEODB according to an embodiment of the present disclosure.

For the EDID structure, the data structure of EDID version 1.3 can be used. EDID 400 may include a base block 410. The base block 410 may include various information related to the sink device 100.

For example, the base block 410 includes header, vendor and product identification information, EDID version information, basic display parameters (video input type (analog or digital), display size (horizontal screen size, and vertical ( Vertical), screen size), gamma transfer characteristics), color characteristics (color gamut range supported by the display), detailed timing information, extended flags, and checksums.

Meanwhile, the base block 410 may include information about a base resolution lower than the high resolution, in that the number of bits is insufficient to include high-resolution information such as 4K, 8K, etc.

Specifically, the pixel clock included in the detailed timing descriptor block of the base block can express up to 655.35Mhz, and the horizontal addressable pixel is set to express up to 4095 pixels. Therefore, when the pixel clock of the video signal exceeds 655.35Mhz or the horizontal screen size of the display of the sink device 100 is larger than 4095 pixels, CTA (or CEA) extension is used to record such high-resolution and high-frequency information. Blocks can be used.

Meanwhile, HF-EEODB (HDMI Forum EDID Extension Override Data Block) was introduced in HDMI 2.1. HF-EEODB is located in the CTA extension block and indicates the number of extension blocks. And, with the addition of HF-EEODB in HDMI 2.1, HDMI can also support the DisplayID expansion block for high resolution. The DisplayID extension block may include a detailed timing descriptor.

Accordingly, EDID 400 may include a first CTA extension block 420, a second CTA extension block 430, and a DisplayID extension block 440. HF-EEODB 421 may be included in the first CTA extension block 420. That is, HF-EEODB may be located in the second block among all blocks.

In addition, the first CTA extension block 420 includes a video data block, an audio data block, a speaker allocation data block, a video capability data block, a colorimetry data block, and an HDMI-VSDB (Vendor Specific Data Block). , HF-VSDB (HDMI 2.1 Vendor Specific Data Block), AMD-VSDB (AMD's Vendor Specific Data Block), HDR Static Metadata Block, YCbCr 4:2:0 Function Map Data Block (or YCbCr 4:2 :0 video map data block), vendor-specific video data blocks (e.g. HDR10+), and Detailed Timing Descriptor.

The second CTA extension block 430 and the DisplayID extension block 440 may each include a detailed timing descriptor.

As such, EDID 400 including HF-EEODB is composed of four blocks, including a base block 410, a first CTA extension block 420, a second CTA extension block 430, and a DisplayID extension block 440. ) may include.

Meanwhile, the source device 10 may obtain information about the sink device 100 from the EDID 400 and transmit video signals and audio signals to the sink device 100 based on the obtained information.

At this time, if the HDMI version of the source device 10 is lower than HDMI 2.1 (for example, if the HDMI version of the source device 10 is HDMI 2.0), the source device 10 cannot process HF-EEODB, and accordingly , subsequent data cannot be parsed. That is, given that the HF-EEODB is located in the first CTA extension block 420 (e.g., Byte4 to Byte6 of the first CTA extension block 420), the source device 10 cannot process the HF-EEODB header. In this case, information on the main specifications of the sink device 100 included in the first CTA expansion block 420 (e.g., CTA-861 resolution, audio block, HDR specifications, etc.) cannot be obtained.

In this case, the source device 10 can transmit video signals and audio signals to the sink device 100 based on information obtained from the base block 410.

For example, if the source device 10 is a PC, a video signal can be transmitted to the sink device 100 using the recommended timing included in the base block 410. Additionally, if the source device 10 is an A/V device (e.g. Blu-ray disc player, set-top box, etc.), it may not be able to transmit a video signal to the sync device 100, or it may not be able to transmit an SD-level video signal to the sync device ( 100). Additionally, even if the sink device 100 supports AC-3 (Dolby), the audio codec of the source device 10 can process the audio signal to be transmitted to the sink device 100 into PCM.

Accordingly, when content is received from the source device 10, the processor 130 can identify whether the content corresponds to the EDID of the sink device 100 based on information about the content.

To this end, the sink device 100 may include a decoder (not shown) for processing content received from the source device 10. In this case, the processor 130 can obtain information about the content by decoding the content received from the source device 10 using a decoder (not shown).

Here, information about content may include detailed specifications for video (e.g., resolution, timing, etc.) and detailed specifications for audio (e.g., whether audio is compressed, compression method, etc.).

For example, content may include video. In this case, the processor 130 may identify whether the image received from the source device 10 corresponds to the EDID of the sink device 100 based on the resolution of the image received from the source device 10.

To this end, the processor 130 can determine the resolution of the image received from the source device 10 by identifying the horizontal size and vertical size of the image received from the source device 10.

Additionally, the processor 130 may compare the resolution of the image received from the source device 10 with the resolution defined in EDID. In this case, the processor 130 may compare the resolution of the image received from the source device 10 with the resolution included in the EDID extension block.

And, if the resolution of the image received from the source device 10 is the same as the resolution included in the extension block of the EDID, the processor 130 determines that the image received from the source device 10 corresponds to the EDID of the sink device 100. It can be identified as being

Additionally, if the resolution of the image received from the source device 10 is lower than the resolution included in the extension block of the EDID, the processor 130 determines that the image received from the source device 10 corresponds to the EDID of the sink device 100. It can be identified as not working. For example, the processor 130 allows the sink device 100 to support high-resolution images such as 4k and 8k, and the extension block of EDID includes information about the display specifications of the sink device 100, but the source device ( When SD-level video is received from 10) or when video is not received from the source device 10, it can be identified that the video received from the source device 10 does not correspond to the EDID of the sink device 100.

Additionally, the processor 130 may identify whether the image received from the source device 10 corresponds to the EDID of the sink device 100 based on the timing of the image received from the source device 10.

Specifically, the processor 130 may compare the timing of the image received from the source device 10 with the timing defined in EDID. In this case, the processor 130 may compare the timing of the image received from the source device 10 with the timing included in the extension block of the EDID.

And, if the timing of the image received from the source device 10 corresponds to the recommended timing included in the extension block of the EDID, the processor 130 determines that the image received from the source device 10 is stored in the EDID of the sink device 100. It can be identified as corresponding to . In addition, if the timing of the image received from the source device 10 corresponds to the recommended timing included in the base block of the EDID, the processor 130 determines that the image received from the source device 10 is stored in the EDID of the sink device 100. It can be identified as not corresponding to .

Additionally, the content may include audio. In this case, the processor 130 may identify whether the audio received from the source device 10 corresponds to the EDID of the sink device 100 based on metadata for the audio received from the source device 10.

Specifically, the processor 130 may identify the format of the audio received from the source device 10 based on metadata. Here, the format of the audio may indicate whether the audio is compressed or uncompressed.

Additionally, the processor 130 may compare the format of the audio received from the source device 10 with the audio format defined in EDID. In this case, the processor 130 may compare the format of the audio from the source device 10 with the audio format included in the extension block of EDID.

And, if the audio received from the source device 10 is the same as the audio format included in the extension block of the EDID, the processor 130 determines that the audio received from the source device 10 corresponds to the EDID of the sink device 100. It can be identified as That is, when the audio received from the source device 10 is compressed using a compression method supported by the sink device 100, the processor 130 stores the audio received from the source device 10 in the EDID of the sink device 100. They can be identified as corresponding.

Additionally, if the audio received from the source device 10 is different from the audio format included in the extension block of the EDID, the processor 130 determines that the audio received from the source device 10 does not correspond to the EDID of the sink device 100. It can be identified as not. That is, if the audio received from the source device 10 is not compressed using a compression method supported by the sink device 100, the processor 130 sets the EDID of the sink device 100 to the audio received from the source device 10. It can be identified as not corresponding to . For example, the processor 130 supports AC-3 in the sink device 100, but when audio processed in PCM is received from the source device 10, the audio received from the source device 10 is transmitted to the sink device 100. It can be identified as not corresponding to the EDID of (100).

If the content received from the source device 10 is identified as corresponding to the EDID of the sink device 100, the processor 130 may output the content. For example, the processor 130 may display an image received from the source device 10 on the display 160. Additionally, the processor 130 may output audio received from the source device 10 through the speaker 170.

Meanwhile, if the processor 130 identifies that the content received from the source device 10 does not correspond to the EDID of the sink device 100, the processor 130 changes the EDID including HF-EEODB to an EDID not including HF-EEODB. and transmits the changed EDID to the source device 10.

That is, if the source device 10 fails to process the HF-EEODB header included in the first extension block of EDID, the source device 10 processes video and/or audio based on information obtained from the base block. In this regard, the video and/or audio provided from the source device 10 may not conform to specifications supported by the sink device 100. That is, the video and/or audio provided from the source device 10 may not match the display performance and audio performance of the sink device 100.

Accordingly, the processor 130 can change the EDID to an EDID that does not include HF-EEODB. In this case, the EDID that does not include HF-EEODB may be stored in the memory 120.

FIG. 5 is a diagram for explaining an example of an EDID structure that does not include HF-EEODB according to an embodiment of the present disclosure.

Referring to FIG. 5, EDID 500 does not include HF-EEODB and can be implemented to be compatible with devices that support HDMI 2.0. And, in the case of the EDID structure, the data structure of EDID version 1.3 can be used.

EDID 500, which does not include HF-EEODB, consists of two blocks and may include a base block 510 and a CTA extension block 520.

In this case, the CTA expansion block 520 includes a video data block, an audio data block, a speaker allocation data block, a video function data block, a colorimetry data block, HDMI-VSDB, HF-VSDB (HDMI 2.0 Vendor Specific Data Block), AMD-VSDB, which may include HDR static metadata blocks, YCbCr 4:2:0 feature map data blocks (or YCbCr 4:2:0 video map data blocks), vendor-specific video data blocks (e.g. HDR10+), and detailed timing descriptors. You can.

In this case, maximum display performance information (e.g., UHD 60Hz with a pixel clock of 600Mhz or less) can be recorded in the EDID 500 within the range that satisfies the HDMI 2.0 specification.

Meanwhile, in the above-described example, the EDID 500 has been described as being implemented to be compatible with devices that support HDMI 2.0, but the example is not limited to this. In other words, EDID 500 may be implemented to be compatible with devices that support HDMI 1.4.

Even in this case, EDID that does not include HF-EEODB consists of two blocks and may include a base block and a CTA extension block.

However, the CTA extension block includes video data block, audio data block, speaker allocation data block, video function data block, HDMI-VSDB, YCbCr 4:2:0 function map data block (or YCbCr 4:2:0 video map data block) ) and a detailed timing descriptor.

Meanwhile, the processor 130 may transmit the changed EDID to the source device 10. Specifically, when a high level voltage is received through the HPD line 340, the source device 10 can read the EDID stored in the EDID memory 111 of the sink device 100. Accordingly, the processor 130 can transmit a low-level voltage to the source device 10 through the HPD line 340 and change the EDID in the EDID memory 111 while the HPD line 340 is maintained at a low level. there is. That is, the processor 130 may delete the EDID including HF-EEODB from the EDID memory 111 and store the EDID not including HF-EEODB in the EDID memory 111. Thereafter, the processor 130 may transmit a high level voltage to the source device 10 through the HPD line 340. Accordingly, the source device 10 can receive the changed EDID from the sink device 100.

And, when content is received from the source device 10 based on the changed EDID, the processor 130 can output the content. For example, the processor 130 may display an image received from the source device 10 on the display 160. Additionally, the processor 130 may output audio received from the source device 10 through the speaker 170.

Meanwhile, if the processor 130 identifies that the content received from the source device 10 does not correspond to the EDID of the sink device 100, the processor 130 may change the mode of the sink device 100.

For example, when the sink device 100 supporting HDMI 2.1 is implemented as a monitor, the EDID extension block may include Variable Refresh Rate (VRR) information. However, if the source device 10 cannot parse data from the expansion block, the VRR function cannot be provided. Accordingly, if the processor 140 identifies that the content received from the source device 10 does not correspond to the EDID of the sink device 100, the processor 140 may deactivate the VRR mode of the sink device 100.

Meanwhile, when a preset event occurs, the processor 130 can restore the EDID back to its original state. That is, when a preset event occurs, the processor 130 may delete the EDID not including HF-EEODB from the EDID memory 111 and store the EDID including HF-EEODB in the EDID memory 111.

Here, the preset event may include events such as the sink device 100 being rebooted, the sink device 100 entering and exiting power saving mode, or the HDMI cable being removed from the HDMI port.

Figure 6 is a flowchart illustrating a method in which a sink device changes an EDID and transmits it to a source device according to an embodiment of the present disclosure.

Referring to FIG. 6, the sink device 100 can perform an HPD operation when the source device 10 is connected through an HDMI cable (S611). Specifically, the sink device 100 may transmit a high-level voltage to the source device 10 through the HPD line.

And, the sink device 100 can transmit EDID to the source device 10 (S613). Specifically, when a high-level voltage is received through the HPD line, the source device 10 may transmit a signal requesting transmission of EDID to the sink device 100 through the DDC line. Accordingly, the sink device 100 can transmit EDID to the sink device 100 through the DDC line, and the source device 10 can receive the EDID from the sink device 100 through the DDC line. In this case, the sink device 100 may record the EDID stored in the memory 120 in the EDID memory 111. Accordingly, the source device 10 can read the EDID from the sink device 100. In this case, EDID includes HF-EEODB and may be composed of 4 blocks.

The source device 10 may determine the specifications of the content to be transmitted to the sink device 100 based on the information obtained from the EDID and transmit the content of the determined specifications to the sink device 100 (S615).

The sink device 100 can identify whether the content received from the source device 10 corresponds to the EDID (S617).

For example, although the sync device 100 supports high resolution such as 4k and 8k, the sync device 100 receives low-resolution video (e.g., SD-level video such as 480p and 576p) from the source device 10, or If no video is received from the source device 10, the video received from the source device 10 can be viewed as not corresponding to the EDID of the sink device 100.

For example, when the audio specification supported by the sink device 100 is AC-3 (Dolby), but the sink device 100 receives audio processed by PCM (Pulse Code Modulation) from the source device 10. , the audio received from the source device 10 can be viewed as not corresponding to the EDID of the sink device 100.

If the content received from the source device 10 corresponds to the EDID (S617-Y), the sink device 100 may output the content (S619).

Meanwhile, if the content received from the source device 10 does not correspond to the EDID (S617-N), the sink device 100 may change the EDID (S621).

Specifically, the sink device 100 can change the EDID from an EDID composed of 4 blocks to an EDID composed of 2 blocks. That is, the sink device 100 can change the EDID composed of 4 blocks stored in the EDID memory 111 to the EDID composed of 2 blocks.

In this case, the sink device 100 may change the mode of the sink device 100. For example, if the sink device 100 identifies that content received from the source device 10 does not correspond to the EDID of the sink device 100, the sink device 100 may deactivate the VRR mode of the sink device 100.

And, the sink device 100 can perform the HPD operation (S623). Specifically, the sink device 100 may transmit a low-level voltage to the source device 10 through the HPD line. Additionally, the sink device 100 can change the EDID stored in the memory 120 to an EDID composed of two blocks. Thereafter, the processor 130 may transmit a high-level voltage to the source device 10 through the HPD line.

And, the sink device 100 can transmit EDID to the source device 10 (S625). Specifically, when a high-level voltage is received through the HPD line, the source device 10 may transmit a signal requesting transmission of EDID to the sink device 100 through the DDC line. Accordingly, the sink device 100 can transmit EDID to the sink device 100 through the DDC line, and the source device 10 can receive the EDID from the sink device 100 through the DDC line. Accordingly, the source device 10 can read the EDID from the sink device 100. In this case, EDID does not include HF-EEODB and may be composed of two blocks.

The source device 10 may determine the specifications of the content to be transmitted to the sink device 100 based on the information obtained from the EDID and transmit the content of the determined specifications to the sink device 100 (S627).

The sink device 100 can output content received from the source device 10 (S629).

As such, according to an embodiment of the present disclosure, if the EDID is not compatible between the sink device and the source device due to the HDMI version, the sink device can change the EDID and transmit it to the source device without any separate user manipulation. Accordingly, EDID compatibility is improved, and the sink device can output high-definition video with appropriate specifications.

FIG. 7 is a flowchart illustrating a method of providing an EDID of a sink device that performs HDMI communication with a source device according to an embodiment of the present disclosure.

When content is received from a source device, it is identified whether the content corresponds to the EDID of the sink device based on information about the content (S710).

Afterwards, if the content is identified as not corresponding to the EDID of the sink device, the EDID including HF-EEODB is changed to an EDID not including HF-EEODB (S720).

Then, the changed EDID is transmitted to the source device (S730).

Here, EDID including HF-EEODB may be composed of 4 blocks. Additionally, EDID that does not include HF-EEODB may be composed of two blocks.

Additionally, EDID including HF-EEODB may include a base block, a first CTA extension block, a second CTA extension block, and a DisplayID extension block. In this case, HF-EEODB may be included in the first CTA extension block.

And, EDID that does not include HF-EEODB may include a base block and a CTA extension block.

Meanwhile, content may include video. In this case, in step S720, if the resolution of the video received from the source device is lower than the resolution included in the extension block of the EDID of the sink device, it can be identified that the video received from the source device does not correspond to the EDID of the sink device. .

Additionally, the content may include audio. In this case, step S720 is based on the metadata for the audio received from the source device. If the audio received from the source device is audio that has not been compressed using the compression method supported by the sink device, the audio does not correspond to the EDID of the sink device. It can be identified as not.

Meanwhile, if the content is identified as corresponding to the EDID of the sink device, the content can be output.

Meanwhile, according to an example of the present disclosure, the various embodiments described above may be implemented as software including instructions stored in a machine-readable storage media (e.g., a computer). You can. The device is a device capable of calling instructions stored from a storage medium and operating according to the called instructions, and may include an electronic device (eg, electronic device A) according to the disclosed embodiments. When an instruction is executed by a processor, the processor may perform the function corresponding to the instruction directly or using other components under the control of the processor. Instructions may contain code generated or executed by a compiler or interpreter. A storage medium that can be read by a device may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium does not contain signals and is tangible, and does not distinguish whether the data is stored semi-permanently or temporarily in the storage medium.

Additionally, according to an embodiment of the present disclosure, the method according to the various embodiments described above may be included and provided in a computer program product. Computer program products are commodities and can be traded between sellers and buyers. The computer program product may be distributed on a machine-readable storage medium (e.g. compact disc read only memory (CD-ROM)) or online through an application store (e.g. Play Store™). In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or created temporarily in a storage medium such as the memory of a manufacturer's server, an application store server, or a relay server.

In addition, according to an embodiment of the present disclosure, the various embodiments described above are stored in a recording medium that can be read by a computer or similar device using software, hardware, or a combination thereof. It can be implemented in . In some cases, embodiments described herein may be implemented with a processor itself. According to software implementation, embodiments such as procedures and functions described in this specification may be implemented as separate software. Each piece of software may perform one or more functions and operations described herein.

Meanwhile, computer instructions for performing processing operations of devices according to the various embodiments described above may be stored in a non-transitory computer-readable medium. Computer instructions stored in such a non-transitory computer-readable medium, when executed by a processor of a specific device, cause the specific device to perform processing operations in the device according to the various embodiments described above. A non-transitory computer-readable medium refers to a medium that stores data semi-permanently and can be read by a device, rather than a medium that stores data for a short period of time, such as registers, caches, and memories. Specific examples of non-transitory computer-readable media may include CD, DVD, hard disk, Blu-ray disk, USB, memory card, ROM, etc.

In addition, each component (e.g., module or program) according to the various embodiments described above may be composed of a single or multiple entities, and some of the sub-components described above may be omitted, or other sub-components may be omitted. Additional components may be included in various embodiments. Alternatively or additionally, some components (e.g., modules or programs) may be integrated into a single entity and perform the same or similar functions performed by each corresponding component prior to integration. According to various embodiments, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or at least some operations may be executed in a different order, omitted, or other operations may be added. It can be.

In the above, preferred embodiments of the present disclosure have been shown and described, but the present disclosure is not limited to the specific embodiments described above, and may be used in the technical field pertaining to the disclosure without departing from the gist of the disclosure as claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be understood individually from the technical ideas or perspectives of the present disclosure.

100: Sink device 110: HDMI interface
120: Memory 130: One or more processors

Claims (14)

In the sync device,
High Definition Multimedia Interface (HDMI) interface for communication with source devices;
A memory that stores one or more instructions; and
Includes one or more processors connected to the interface and the memory to control the sink device,
The one or more processors:
By executing one or more of the instructions above,
When content is received from the source device through the interface, identify whether the content corresponds to the EDID (Extended Display Identification Data) of the sink device based on information about the content,
If the content is identified as not corresponding to the EDID of the sink device, the EDID including HF-EEODB (HDMI Forum EDID Extension Override Data Block) is changed to an EDID not including the HF-EEODB, and the changed EDID A sink device that transmits to the source device. According to paragraph 1,
EDID including the HF-EEODB consists of 4 blocks,
The EDID that does not include the HF-EEODB is a sink device composed of two blocks. According to paragraph 2,
The EDID including the HF-EEODB includes a base block, a first CTA extension block, a second CTA extension block, and a DisplayID extension block,
The HF-EEODB is a sink device included in the first CTA extension block. According to paragraph 2,
The EDID that does not include the HF-EEODB is a sink device that includes a base block and a CTA extension block. According to paragraph 1,
The content includes video,
The one or more processors:
If the resolution of the video received from the source device is lower than the resolution included in the extension block of the EDID of the sink device, the sink device identifies that the video received from the source device does not correspond to the EDID of the sink device. According to paragraph 1,
The content includes audio,
The one or more processors:
Based on the metadata for the audio received from the source device, if the audio received from the source device is audio that has not been compressed using a compression method supported by the sink device, the audio does not correspond to the EDID of the sink device. A sync device that identifies the device as a sync device. According to paragraph 1,
The one or more processors:
A sink device that outputs the content when the content is identified as corresponding to the EDID of the sink device. In a method of providing EDID (Extended Display Identification Data) of a sink device that performs High Definition Multimedia Interface (HDMI) communication with a source device,
When content is received from the source device, identifying whether the content corresponds to the EDID of the sink device based on information about the content;
If the content is identified as not corresponding to the EDID of the sink device, changing the EDID including an HDMI Forum EDID Extension Override Data Block (HF-EEODB) to an EDID not including the HF-EEODB; and
A method of providing EDID, including: transmitting the changed EDID to the source device. According to clause 8,
EDID including the HF-EEODB consists of 4 blocks,
An EDID provision method in which the EDID not including the HF-EEODB consists of two blocks. According to clause 9,
The EDID including the HF-EEODB includes a base block, a first CTA extension block, a second CTA extension block, and a DisplayID extension block,
The HF-EEODB is included in the first CTA extension block. According to clause 9,
The EDID that does not include the HF-EEODB includes a base block and a CTA extension block. According to clause 8,
The content includes video,
The identification step is,
When the resolution of the video received from the source device is lower than the resolution included in the extension block of the EDID of the sink device, an EDID providing method identifies that the video received from the source device does not correspond to the EDID of the sink device. . According to clause 8,
The content includes audio,
The identification step is,
Based on the metadata for the audio received from the source device, if the audio received from the source device is audio that has not been compressed using a compression method supported by the sink device, the audio does not correspond to the EDID of the sink device. How to provide an EDID to identify something. According to clause 8,
If the content is identified as corresponding to the EDID of the sink device, outputting the content.

Images