Device and method for sharing source capability information between source and sink

Abstract

According to various embodiments of the present disclosure, an operating method of a source device comprises the steps of: receiving a hot plug detection (HPD) signal from a sink device; sending a request for an extended display identification (EDID) or displayID (DPID) to the sink device over a display data channel (DDC); receiving first information about the EDID or DPID from the sink device; sending second information including source capability information to the sink device on the basis of the first information about the EDID or DPID; and sending compressed source data to the sink device on the basis of the source capability information.

Description

Device and method for sharing source capability information between a source and a sink

[0001] The present disclosure relates to a device and method for sharing source capability information between a source and a sink in a device using an interface and a DisplayPort or HDMI. Specifically, the present disclosure relates to a device using an interface and a DisplayPort or HDMI, and to a device and method for sharing source capability information before transmitting and receiving video / audio data between a source device and a sink device.

[0002]

[0003] The present disclosure relates to an interface and a device using DisplayPort and HDMI. Specifically, the present disclosure relates to a device and method for sharing source capability information before transmitting and receiving video / audio data between a source device and a sink device. The present disclosure is an invention for a method for facilitating the transmission of video / audio data by allowing a sink device to know the capability information of the source device. An operation is described in which a block similar to or separate from the EDID used by the sink device is included in a signal transmitted by the source device to indicate the source capability information.

[0004] Previously, the only way to obtain Sink Capability information was for a Source device directly connected to the Sink device. This risked the Sink device having to process data delivered by the Source without any information about Source Capability. Previously, functionality to display unchanging Source information and updated Source information was very limited.

[0005]

[0006] In order to solve the above-described problem, the present disclosure provides a method and device for sharing source capability information between a source and a sink in a device using an interface and DisplayPort, HDMI.

[0007] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0008]

[0009] According to various embodiments of the present disclosure, a method of operating a source device is provided, comprising: receiving a hot plug detection (HPD) signal from a sink device; transmitting a request for an EDID (Extended Display Identification) or a DPID (DisplayID) to the sink device through a DDC (Display Data Channel); receiving first information of the EDID or the DPID from the sink device; transmitting second information including source capability information to the sink device based on the first information of the EDID or the DPID; and transmitting compressed source data to the sink device based on the source capability information.

[0010] According to various embodiments of the present disclosure, a method of operating a sink device is provided, comprising: transmitting a hot plug detection (HPD) signal to a source device; receiving a request for an Extended Display Identification (EDID) or a DisplayID (DPID) from the source device through a Display Data Channel (DDC); transmitting first information of the EDID or the DPID to the source device; receiving second information including source capability information from the source device based on the first information of the EDID or the DPID; and receiving compressed source data from the source device based on the source capability information.

[0011] According to various embodiments of the present disclosure, a source device is provided, comprising: a processor; a memory; and a transceiver, wherein the memory stores instructions for performing operations based on being executed by the processor, the operations comprising: receiving a hot plug detection (HPD) signal from a sink device; transmitting a request for an Extended Display Identification (EDID) or a DisplayID (DPID) to the sink device through a Display Data Channel (DDC); receiving first information of the EDID or the DPID from the sink device; transmitting second information including source capability information to the sink device based on the first information of the EDID or the DPID; and transmitting compressed source data to the sink device based on the source capability information.

[0012]

[0013] In order to solve the above-described problem, a device and method for sharing source capability information between a source and a sink in a device using an interface and DisplayPort, HDMI can be provided.

[0014]

[0015] The accompanying drawings are intended to aid in understanding the present disclosure and, together with detailed descriptions, may provide embodiments of the present disclosure. However, the technical features of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing may be combined with each other to form new embodiments. Reference numerals in each drawing may indicate structural elements.

[0016] FIG. 1 is a block diagram illustrating a system according to various embodiments of the present disclosure.

[0017] FIG. 2 is a block diagram showing an example of the structure of a source device and a sink device according to various embodiments of the present disclosure.

[0018] FIG. 3 is a block diagram showing an example of the structure of a source device and a sink device according to various embodiments of the present disclosure.

[0019] Figure 4 shows an example of a sequence configuration between a source device and a sink device.

[0020] Figure 5 shows an example of a sequence configuration between a source device and a sink device.

[0021] Figure 6 shows an example of a sequence configuration between a source device and a sink device.

[0022] Figure 7 shows an example of a sequence configuration between a source device and a sink device.

[0023] FIG. 8 illustrates an example of a sequence configuration between a source device and a sink device according to various embodiments of the present disclosure.

[0024] FIG. 9 is a diagram illustrating an example of an operation method of a source device according to various embodiments of the present disclosure.

[0025] FIG. 10 is a diagram illustrating an example of an operating method of a sink device according to various embodiments of the present disclosure.

[0026]

[0027] In various embodiments of the present disclosure, “A or B” may mean “only A,” “only B,” or “both A and B.” In other words, in various embodiments of the present disclosure, “A or B” may be interpreted as “A and / or B.” For example, in various embodiments of the present disclosure, “A, B or C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.”

[0028] In various embodiments of the present disclosure, a slash ( / ) or a comma may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B, or C."

[0029] In various embodiments of the present disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Furthermore, in various embodiments of the present disclosure, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted as equivalent to “at least one of A and B.”

[0030] Additionally, in various embodiments of the present disclosure, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0031]

[0032] FIG. 1 is a block diagram illustrating a system according to various embodiments of the present disclosure.

[0033] Hereinafter, devices that transmit and receive video / audio / control data will be collectively referred to as an AV (audio / video) system. Examples of AV systems include HDMI and DisplayPort.

[0034] Referring to FIG. 1, an AV system may include a source device (100) and a sink device (200). In particular, a device transmitting audio / video data in the AV system may correspond to the source device (100), and a device receiving video / audio data may correspond to the sink device (200). At this time, cables and connectors may be provided as physical devices that connect the two devices to support data transmission and reception.

[0035] Cables and connectors can pair four channels, each providing a Transition Minimized Differential Signaling (TMDS) data channel and a TMDS clock channel. The TMDS data channels can be used to carry video data, audio data, and auxiliary data.

[0036] Additionally, the AV system provides the Video Electronics Standards Association (VESA) Display Data Channel (DDC). DDC is used to exchange configuration and status information between source and sink devices. The CEC protocol can provide high-level control functions between various audiovisual products in the user environment and can also be used optionally. In addition, the optional HEAC (HDMI Ethernet and Audio Return Channel) can provide ARC (Audio Return Channel) and Ethernet-compatible data networking between connected devices in the opposite direction from TMDS.

[0037] Video data, audio data, and additional data can be transmitted / received over three TMDS data channels. The TMDS clock, which typically runs the video pixel rate, is transmitted over the TMDS clock channel. The TMDS clock can be used as a frequency reference for data recovery on the three TMDS data channels at the receiver. At the source device, 8 bits of data per TMDS data channel can be converted into a 10-bit DC-balanced, transition-minimized sequence that can be serially transmitted at a rate of 10 bits per TMDS clock period.

[0038] To transmit audio data and additional data over TMDS channels, AV systems use a packet structure. To achieve high reliability for audio and control data, data can be transmitted as 10-bit words generated using BCH error correction and error reduction coding.

[0039] A source device can read the Enhanced Extended Display Identification Data (E-EDID) of a Display Data Channel (DDC) sink device to determine the sink device's configuration information and capabilities. E-EDID may also be referred to as EDID information hereinafter.

[0040] The utility line can be used for optional extensions such as HEAC.

[0041] The source device (100) can receive EDID (Extended Display Identification Data) information from the sink device (200) via a DDC channel. The source device (100) can parse the received EDID information to recognize configuration information and supported functions of the sink device (200). The EDID information can include at least one block containing various information regarding the sink device (200).

[0042] In particular, EDID information according to one embodiment of the present invention may include information on the function and power supply capability of the sink device (200) in power transmission and reception. The source device (100) may recognize the power transmission / reception capability of the sink device (200) through this EDID information, and may transmit power to the sink device (200) or receive power from the sink device (200) accordingly.

[0043] The source device (100) includes at least one of a display unit (110), a user input interface unit (120), a control unit (180), a transmitter (Tx), a memory unit (140), a storage unit (150), a multimedia unit (160), a power control unit (130), and a power supply unit (170).

[0044] The sink device (200) includes at least one of an EDID EEPROM (210), a power control unit (220), a display unit (230), a user input interface unit (240), a receiver (Rx), a control unit (280), a power supply unit (250), a memory unit (260), and a multimedia unit (270). Hereinafter, descriptions of units performing the same operation will not be repeated.

[0045] The source device (100) represents a physical device that transmits or streams content stored in the storage unit (150) to the sink device (200). The source device (100) can send a request message to the sink device (200) or receive and process a request message received from the sink device (200). The source device (100) can provide a UI that processes and transmits a response message transmitted by the sink device (200) in response to the transmitted request message to the user, and when the source device (100) includes a display unit (110), this UI can be provided as a display. In addition, the source device (100) can request the sink device (200) for power to be supplied.

[0046] The sink device (200) receives content from the source device (100), and can transmit a request message to the source device (100) or process a message received from the source device (100) and transmit a response message. The sink device (200) can also provide a UI (User Interface) that processes the response message received from the source device (100) and transmits it to the user. If the sink device (200) includes a display unit, this UI can be provided as a display. In addition, the sink device (200) can supply power requested by the source device (100) to the source device (100).

[0047] The user input interface unit (120, 240) can receive a user's action or input, and as an example, the user input interface (120, 240) can correspond to a remote controller, a voice receiving / recognition device, a touch input sensing / receiving device, etc.

[0048] The control unit (180, 280) can control the overall operation of each device. In particular, the control unit (180, 280) can perform communication between units included in each device and control the operation of each unit.

[0049] The memory unit (140, 260) represents a volatile physical device in which various types of data are temporarily stored.

[0050] The storage unit (150) represents a non-volatile physical device capable of storing various types of data.

[0051] EDID EEPROM (210) represents an EEPROM that stores EDID information.

[0052] The above-described memory unit (140, 260), storage unit (150), and EDID EEPROM (210) all serve to store data, and they may all be collectively referred to as memory units.

[0053] The display unit (110, 230) can display received data or content, data stored in the memory unit, UI, etc. under the control of the control unit (180, 280).

[0054] The multimedia unit (160, 270) can play various types of multimedia. The multimedia unit (160, 270) may be implemented separately from the control unit (180, 280), or may be implemented as a single physical configuration with the control unit (180, 280).

[0055] The power supply unit (170, 250) can supply power required for the operation of the source device (100), the sink device (200) and the units included therein.

[0056] The transmitter (Tx) is a unit equipped in the source device (100) that transmits and receives data, and performs data transmission and reception including not only audio / video data but also messages such as commands, requests, actions, and responses between devices.

[0057] The receiver (Rx) is a unit equipped in the sink device (200) that transmits and receives data, and performs data transmission and reception including not only audio / video data but also messages such as commands, requests, actions, and responses between devices.

[0058] The power control unit (130, 220) can manage and control power transmission and reception between devices via a transceiver.

[0059] Among the above-described units, units other than the transmitter (Rx), receiver (Tx), and control unit (180, 280) may be optionally included in the source device (100) or the sink device (200) depending on the embodiment, and may not be essential component units.

[0060] Previously, AV systems did not support power transfer between source and sink devices. Consequently, when operating portable devices for extended periods, the inconvenience of always having to connect an external power cable for optimal operation existed. To address this issue, this specification proposes a method for ensuring optimal AV system operation without the need for external devices by enabling the wired interface to support power transfer.

[0061] For convenience of explanation, below, a device that supplies (or transmits) power will be referred to as a P-source device, and a device that supplies (or receives) power will be referred to as a P-sink device. Additionally, a device that simultaneously supports the functions of a P-source device and a P-sink device will be referred to as a dual device.

[0062]

[0063] Various embodiments of the present disclosure relate to a method of distinguishing DSC versions.

[0064] The present disclosure relates to a device using an Interface and DisplayPort, HDMI, and is an invention for checking whether DSC is supported before transmission between a Sink device and a Source device, and for exchanging information between devices, and describes a method for supporting a gesture extraction function and directly transmitting data in each Sink / Source device, a method for providing gesture information of the Sink / Source device according to the extracted information, and a method for transmitting a change in the gesture information of the Sink / Source device to the Sink / Source device, and an operation thereof.

[0065]

[0066] Previously, the only way to obtain information was from an external video / audio capture device directly connected to the source device. Typically, receiving gesture information required implementing the technology to support the capture device in the source device. Sink devices, however, were expanding their support for gesture-related devices, and these devices were not available in the source device.

[0067]

[0068] The main components of the method proposed in this disclosure are as follows:

[0069] 1. The main transmission line uses DDC lined.

[0070] 2. The source device reads the information of the sink device using EDID / DisplayID to check whether DSC is supported (HDMI / DisplayPort).

[0071] 3-1. Read the information of the Source device from the Sink device using SCDC to check whether DSC is supported (HDMI).

[0072] 3-2. Read the information of the Source device from the Sink device using the Aux Channel to check whether DSC is supported (DisplayPort).

[0073] 4-1. The source of the current bus interface checks the HDMI DSC version and transmits DSC Data & Info that can be operated in the sink (HDMI).

[0074] 4-2. The source of the current Bus Interface checks the Display DSC version and transmits DSC Data & Info that can be operated in the Sink (DisplayPort).

[0075] 5. Using the HDMI HEC of the current Bus Interface, the Source device checks the DSC version information of the Sink device.

[0076]

[0077] According to various embodiments of the present disclosure, models employing new Sinks / Sources that utilize various types of DSC Slices are expected to diversify, thereby preventing video corruption after audio / video transmission by exchanging information in advance in terms of connection compatibility. The new Sink provides convenience by distinguishing between Legacy Sources and New Sources, allowing consumers who only have either a Sink or Source device equipped with a camera to utilize a gesture-based solution.

[0078]

[0079] Background to various embodiments of the present disclosure

[0080] FIG. 2 is a block diagram showing an example of the structure of a source device and a sink device according to various embodiments of the present disclosure.

[0081] A specific description of each configuration illustrated in Fig. 2 is as follows.

[0082] (1) Source Device

[0083] A device that sends a request message that issues a command to a Sink Device or receives and processes a request message requested from a Sink Device.

[0084] A device that provides a UI that processes the response message received from the Sink Device after sending the above request message and transmits it to the user, and a device that supports a display device that displays it, and a device that supports a user input interface that receives user actions through the UI.

[0085] A device that provides a UI that receives and processes a request message requested from the above Sink Device and transmits it to the user, and a device that supports a display device that displays the UI, and a device that supports a user input interface that receives user actions through the UI.

[0086] A physical device that transmits or streams content stored in the Content Storage of the Source Device to the Sink Device.

[0087] (2) Sink Device

[0088] A device that sends a request message that issues a command to the Source Device or receives and processes a request message requested from the Source Device.

[0089] A device that provides a UI that processes the response message received from the Source Device after sending the above request message and transmits it to the user, and a device that supports a display device that displays it, and a device that supports a user input interface that receives user actions through the UI.

[0090] A device that provides a UI that receives and processes a request message requested from the above Source Device and transmits it to the user, and a device that supports a display device that displays the UI, and a device that supports a user input interface that receives user actions through the UI.

[0091] A physical device that receives content from a source device or receives streaming and provides content rendering to the user.

[0092] (3) Network interface

[0093] A physical device that enables the transmission of messages or data such as commands, requests, actions, and responses between devices.

[0094] (4) Memory unit

[0095] A volatile physical device (e.g., Memory) that is implemented in various types of devices as an optional device, temporarily storing various types of data.

[0096] (5) Control unit

[0097] Overall operation control of source and sink devices

[0098] (6) Display

[0099] Data received through the network interface or data stored in Content Storage is displayed on the screen under the control of the Control Unit.

[0100] (7) Multimedia module

[0101] Devices for playing various types of multimedia

[0102] The multimedia module can be implemented within the control unit or separately from the control unit.

[0103] (8) Storage

[0104] A non-volatile physical device that can store various types of data (e.g. SD card)

[0105] (9) Power Supply

[0106] A device that supplies power required for the operation of each component by receiving external or internal power under the control of the control unit.

[0107] (10) EDID / Display block (EEPROM, memory)

[0108] EEPROM storing EDID information

[0109] (11) Video Encoder

[0110] A device that compresses video to be transmitted via HDMI / DisplayPort Tx.

[0111] (12) Video Decoder

[0112] A device that decompresses compressed video received via HDMI / DisplayPort Rx.

[0113]

[0114] FIG. 3 is a block diagram showing an example of the structure of a source device and a sink device according to various embodiments of the present disclosure.

[0115] A specific description of each configuration shown in Fig. 3 is as follows.

[0116] (1) Source Device

[0117] A device that sends a request message that issues a command to a Sink Device or receives and processes a request message requested from a Sink Device.

[0118] A device that provides a UI that processes the response message received from the Sink Device after sending the above request message and transmits it to the user, and a device that supports a display device that displays it, and a device that supports a user input interface that receives user actions through the UI.

[0119] A device that provides a UI that receives and processes a request message requested from the above Sink Device and transmits it to the user, and a device that supports a display device that displays the UI, and a device that supports a user input interface that receives user actions through the UI.

[0120] A physical device that transmits or streams content stored in the Content Storage of the Source Device to the Sink Device.

[0121] (2) Sink Device

[0122] A device that sends a request message that issues a command to the Source Device or receives and processes a request message requested from the Source Device.

[0123] A device that provides a UI that processes the response message received from the Source Device after sending the above request message and transmits it to the user, and a device that supports a display device that displays it, and a device that supports a user input interface that receives user actions through the UI.

[0124] A device that provides a UI that receives and processes a request message requested from the above Source Device and transmits it to the user, and a device that supports a display device that displays the UI, and a device that supports a user input interface that receives user actions through the UI.

[0125] A physical device that receives content from a source device or receives streaming and provides content rendering to the user.

[0126] (3) Network interface

[0127] A physical device that enables the transmission of messages or data such as commands, requests, actions, and responses between devices.

[0128] (4)Memory unit

[0129] A volatile physical device (e.g., Memory) that is implemented in various types of devices as an optional device, temporarily storing various types of data.

[0130] (5) Control unit

[0131] Overall operation control of source and sink devices

[0132] (6) Display

[0133] Data received through the network interface or data stored in Content Storage is displayed on the screen under the control of the Control Unit.

[0134] (7) Multimedia module

[0135] Devices for playing various types of multimedia

[0136] The multimedia module can be implemented within the control unit or separately from the control unit.

[0137] (8) Storage

[0138] A non-volatile physical device that can store various types of data (e.g. SD card)

[0139] (9) Power Supply

[0140] A device that supplies power required for the operation of each component by receiving external or internal power under the control of the control unit.

[0141] (10) EDID / Display block (EEPROM, memory)

[0142] EEPROM storing EDID information

[0143] (11) Video Encoder

[0144] A device that compresses video to be transmitted via HDMI / DisplayPort Tx.

[0145] (12) Video Decoder

[0146] A device that decompresses compressed video received via HDMI / DisplayPort Rx.

[0147]

[0148] 1. EDID (Extended Display Identification Data)

[0149] EDID is a data structure that contains various information about the display device defined by VESA and is transmitted to the source device.

[0150] EDID is compatible with the upper 128 bytes from version 1.0 to 1.4, and from version 1.3, it is called Enhanced EDID, and an EDID extension block is added to insert additional data after the upper 128 bytes.

[0151] EDID is deprecated up to Version 1.2, and Version 1.3 is widely used in IT display devices, CE display devices, and video interfaces (e.g., HDMI).

[0152] Table 1 below shows the configuration of EDID.

[0153] Address No. Bytes Description 00h ~ 07h 8 Header information. Fixed to 00 FF FF FF FF FF FF 00 08h ~ 11h 10 Vendor / Product Identification. Manufacturer, product code, serial number, and manufacturing date 12h ~ 13h 2 EDID Structure Version / Revision 14h ~ 18h 5 Basic Display Parameters / Features. Video Input definition (analog or digital), Max. Horizontal Image Size, Max. Vertical Image Size, Display Transfer Characteristic (Gamma), Feature Support (Standby, Suspend, Display Type, Standard Default Color space (sRGB), Preferred Timing Mode support, etc.) 19h ~ 22h 10 Color Characteristics. Information related to color and white point. Represented as xy coordinates of Red, Green, Blue, and White in color space 23h ~ 25h 3 Established Timings. Describes commonly used timing modes. 26h ~ 35h 16Standard Timings. Eight standard timing descriptors are described, and each descriptor contains information on the range of horizontal active pixels, image aspect ratio, and refresh rate (60 ~ 123Hz). Timings not included in the established timing are described according to the VESA DMT standard or timing information calculated using GTF. 36h ~ 7Dh 72Detailed Timing Descriptors.This descriptor contains detailed timing information about the resolutions supported by the display. There are four descriptors. The first descriptor is Preferred Detailed Timing. The second descriptor indicates secondary detailed timing or additional monitor information (Serial Number, Range Limits, Name). The remaining two descriptors contain additional monitor information. Monitor Range Limits and Name must be specified. 7Eh1Extension Flag. Specifies the number of EDID extension blocks to be added. 7Fh1Checksum.

[0154]

[0155] 2. CEA 861 EDID Extension Block

[0156] The timing information described in EDID is for IT display devices, and the EDID 1.3 Extension Block in CEA 861 is used to indicate the timing information of CE display devices.

[0157] Version 3 CEA Extension is defined in the CEA 861B standard and specifies four optional Data Blocks (Video, Audio, Speaker Allocation, Vendor Specific).

[0158]

[0159] Byte #0: Tag. 0x021: Revision Number. 0x03: Byte number offset d where the 218-byte Detailed Timing Descriptor (DTD) begins. 3: Indication of underscan, audio support, YCBCR 4:4:4 or YCBCR 4:2:2 support, number of native DTDs supported. 4: Start of data block collectiond-1: End of data block collectiond. Start of 18-byte DTD. Follows EDID DTD format. d+(18*n)-1: End of 18-byte DTD. n is the number of descriptors included. +(18*n): Beginning of Padding. 0x00126: End of Padding. 0x00127: Checksum

[0160] Table 3 below shows the Video Data Block.

[0161] Byte #Bits 5-7Bits 0-40Video Tag CodeShort Video Descriptor Total number of bytes (L1)1CEA Short Video Descriptor 1L1CEA Short Video Descriptor L1

[0162]

[0163] Short Video Descriptor contains the Video Identification Code defined in CEA-861.

[0164]

[0165] Table 4 below shows the Audio Data Block.

[0166] Byte #Bits 5-7Bits 0-40Audio Tag CodeShort Audio Descriptor Total number of bytes (L2)1 ~ 3CEA Short Audio Descriptor 14 ~ 3*L2CEA Short Video Descriptor L2 / 3

[0167]

[0168] Short Audio Descriptor contains the Audio Format Code defined in CEA-861.

[0169]

[0170] Table 5 below shows the Speaker Allocation Data Block.

[0171] Byte #Bits 5-7Bits 0-40Speaker allocation Tag CodeSpeaker Allocation Total number of bytes (L3=3)1 ~ 3Speaker Allocation Data Block Payload

[0172]

[0173] Speaker Allocation Data Block Descriptor contains the Data Block Payload defined in CEA-861.

[0174]

[0175] 3. Vendor-Specific Data Block

[0176] HDMI uses this Data Block to define HDMI-specific data, as a block in which vendor-specific data can be defined. The data block below is HF-VSDB.

[0177] Byte / Bits #765432100Vendor Specific Tag Code (=3)Length (=N)1IEEE OUI, Third Octet (0xD8)2IEEE OUI, Second Octet (0x5D)3IEEE OUI, First Octet (0xC4)4Version (=1)5Max_TMDS_Character_Rate6SCDC_PresentRR_CapableRsvd(0)Rsvd(0)LTE_340Mcsc_scrambleIndependent_viewDual_ view3D_OSD_Disparity7Rsvd(0)Rsvd(0)Rsvd(0)Rsvd(0)Rsvd(0)DC_48bit_420DC_36bit_420DC_30bit_420...NReserved(0)

[0178]

[0179] (1) Length: The total length of the data block. The minimum value is 7 and the maximum value is 31.

[0180] (2) IEEE OUI: The OUI assigned to the HDMI Forum as the IEEE Organizationally Unique Identifier is 0xC45DD8.

[0181] (3) Version: The version number of HF-VSDB (HDMI Forum-VSDB) is 1.

[0182] (4) Max_TMDS_Character_Rate: Indicates the maximum TMDS Character Rate supported. If the Sink device does not support 340 Mcsc or more, set it to 0. If it does, set it to 1.

[0183] (5) 3D_OSD_Disparity: If set to 1, it indicates that the Sink device supports receiving 3D_OSD_Disparity Indication.

[0184] (6) Dual_view: When set to 1, it indicates that the Sink device supports receiving Dual_view signaling.

[0185] (6) Independent_view: When set to 1, it indicates that the Sink device supports receiving 3D independent view signaling.

[0186] (7) LTE_340Mcsc_scramble: If set to 1, it indicates that the Sink device supports scrambling at TMDS character rates of 340Mcss or lower. If SCDC_Present is set to 0, this flag must also be set to 0.

[0187] (8) RR_Capable: If set to 1, it indicates that the Sink device can initiate SCDC read requests. If SCDC_Present is set to 0, this flag must also be set to 0.

[0188] (9) SCDC_Present: If set to 1, it indicates that the Sink supports the SCDC function.

[0189] (10) DC_48bit_420, DC_36bit_420, DC_30bit_420: When set to 1, it indicates that Deep Color 4:2:0 pixel encoding is supported at 10 bit / 12 bit / 16 bit per component.

[0190]

[0191] 4. Displayport supported resolutions

[0192] DisplayPort does not have a defined default mandatory resolution like HDMI.

[0193] DefinitionFormatsField RateAspect RatioSupport by standard technologyDisplayPort1.2a1.3SD (Standard Definition)All supportedED (Enhanced Definition)All supportedHD (High Definition)All supportedFull HDAll supported4K UHD (Ultra High Definition)3840x2160p23.98 / 24Hz16:9Support Support3840x2160p25Hz3840x2160p29.97 / 30Hz3840x2160p50Hz3840x2160p59.94 / 60Hz3840x2160p23.98 / 24Hz64:273840x2160p25Hz3840x2160p29.97 / 30Hz3 840x2160p50Hz3840x2160p59.94 / 60Hz4096x2160p23.98 / 24Hz256:1354096x 2160p25Hz4096x2160p29.97 / 30Hz4096x2160p50Hz4096x2160p59.94 / 60Hz8K UHD7680x4320p23.98 / 24Hz16:9Not supportedNot supported (Support planned for 1.3a)

[0194]

[0195] 5. Display ID Extension Block

[0196] (1) Display ID is a VESA standard created to replace the E-EDID standard and EDID v1.4.

[0197] (2) Display ID v1.1 was published in March 2009, and v1.3 was published in September 2013.

[0198] (3) This standard has the characteristic of having various structures including existing EDID extension formats as well as new extension formats for embedded displays and 3D displays.

[0199] (4) The Display ID format contains several blocks that describe information about the display, such as video interfaces, display device technology, timing details, and manufacturer information.

[0200] (5) Blocks are as flexible as the header length, and the length of each field is variable and the specific number of bytes is not fixed. Only a few data blocks are fixed.

[0201]

[0202] Table 8 shows the Display ID Structure.

[0203] AddressValueDescription00h12hDisplay ID Structure Version 1, Revision 201h00h -> FBhBytes in Section02h ~ 03h00h -> FFhDisplay Product Type Identifier & Extension Count04hBLOCKFirst Data block......(N-2)hBLOCKLast byte of Last valid data block(N-1)h00h -> FFhChecksum

[0204]

[0205] Table 9 shows the Data Block Format.

[0206] OffsetValueDescription00h00h -> FFhData Block Identification01h0 -> 7Block Revision and other data02h00h -> F8hNumber of Payload Bytes 0 -> 24803hDESCRIPTOR1st Data Payload Byte04h.2nd Data Payload Byte... (if present)...

[0207] (1) Data Block Identification: Displays the tag of each data block.

[0208] (2) Block revision and other data: The revision increases each time a bit is added or changed in the block.

[0209] (3) Number of Payload Bytes: This indicates the number of bytes used in the payload within one data block.

[0210] (4) 1 ~ N Data Payload Byte: From 03h, it tells what role each Data Payload Byte plays.

[0211]

[0212] 6. DDC (Display Data Channel)

[0213] (1) Protocol standard for digital information transmission between a monitor and a computer's graphic adapter defined by VESA (Video Electronics Standard Association)

[0214] (2) The monitor transmits the display mode information that can be supported to the graphics adapter, and the graphics adapter transmits the video to the monitor accordingly.

[0215] (3) Before the DDC standard was established, the VGA standard used four pins (Pin 11, 12, 4, 15) of the analog VGA connector to recognize the monitor type, and only Pin 11, 12, and 4 were used, and 7 types of monitor types could be recognized.

[0216] (4) DDC version 1 (established in 1994)

[0217] (4-1) Defines EDID (Extended Display Identification Data), a binary file format that describes monitor information.

[0218] (4-2) Pin 12 is used as a data line and 128 byte EDID block is continuously transmitted from the monitor to the computer.

[0219] (5) DDC version 2 (established in 1996)

[0220] (5-1) EDID is not defined in DDC, but is defined as an independent standard as a companion standard.

[0221] (5-2) Defined based on I2C Serial Bus, Pin 12 is used as the data line of I2C Bus, and Pin 15 is used as the clock line of I2C Bus.

[0222] (5-3) Pin 9: Used to supply 5V DC power (up to 50mA) from the computer to the monitor to read the EDID stored in the EEPROM even when the monitor is turned off.

[0223] (5-4) The monitor is assigned 7 bit I2C address 50h as a slave device of the I2C Bus.

[0224] (5-5) Allows EDID storage capacity of up to 28 bytes = 256 bytes with 8 bit data offset.

[0225] (6) E-DDC

[0226] (6-1) Version 1 was established in 1999 as a standard to replace DDC versions 1 and 2, and allows display information storage capacity of up to 32 Kbytes for use of Enhanced EDID.

[0227] (6-2) A new I2C addressing scheme using 8 bit segment index (0x00 ~ 0x7F) can be applied to access 128 segments (1 segment = 256 bytes), which allows access to up to 32K bytes.

[0228] (6-3) E-DDC version 1.1 was established in 2004 and includes support for CE devices and video interfaces other than VGA (e.g., HDMI).

[0229] (6-4) E-DDC version 1.2 was established in 2007 and includes support for DisplayPort and DisplayID.

[0230]

[0231] 7. SCDCS (Status and Control Data Channel Structure)

[0232] (1) SCDCS is a one-to-one communication protocol based on I2C serial communication that enables data exchange between HDMI Source devices and Sink devices.

[0233] (2) Extension of the existing I2C standard: A function is added where a Sink device, which is an I2C slave, requests a status check read from a Source device, which is an I2C master, and the Source device that receives the request reads the corresponding status from the Sink device.

[0234] Table 10 shows an example of a specific configuration of SCDCS.

[0235] OffsetR / WName0x01RSink Version0x02R / WSource Version0x10R / WUpdate_00x11R / WUpdate_10x12-0x1FRReserved for Update Related Uses0x20R / WTMDS_Config0x21RScrambler_Status0x30R / WConfig_00x31-0x3FRReserved for Configuration0x40RStatus_Flag_00x41RStatus_Flag_10x42-0x4FRReserved for Status Related Uses0x50RErr_Det_0_L0x51RErr_Det_0_H0x52RErr_Det_1_L0x53RErr_Det_1_H0x54RErr_Det_2_L0x55RErr_Det_2_H0x56RErr_Det_Checksum0xC0R / WTest_Config_00xC1`0xCFRReserved for test features0xD0RManufacturer IEEE OUI, Third Octet0xD1RManufacturer IEEE OUI, Second Octet0xD2RManufacturer IEEE OUI, First Octet0xD3-0xDDRDevice ID0xDE-0xFFR / WManufacturer SpecificAll Remaining OffsetsRReserved

[0236]

[0237] The following is a detailed description of each component of SCDCS.

[0238] (1) Sink Version: Displays the version information of the SCDCS compliant Sink device. Set to 1.

[0239] (2) Source Version: If the SCDCs compliant Source device reads E-EDID from the Sink device and SCDC_Present = 1 of E-EDID is set, the Source Version of SCDCS is set to 1.

[0240] (3) Update Flags (Update_0, Update_1): If there is a change in the information that the Sink device must report to the Source device (Status, Character Error Detect, etc.), the corresponding bit is set to 1.

[0241] (4) TMDS Configuration (TMDS_Config): TMDS_Bit_Clock_Ratio and Scrambling_Enable each occupy 1 bit. If the Source device wants to enable the Sink device's scrambling function, set the corresponding bit to 1. If TMDS_Bit_Clock_Ratio is 1 / 10, set it to 0, and if it is 1 / 40, set it to 1.

[0242] (5) Scrambler Status: When the Sink device detects a scrambled control code sequence, it sets this bit to 1.

[0243] (6) Configuration (Config_0): This is a field that configures information related to the Capability of the Source and Sink devices. Currently, there is only the RR_Enable field that can indicate whether the Source device supports the Read Request of the Sink device.

[0244] (7) Status Flags (Status_Flag_0, Status_Flag_1): Indicates whether the data received through Clock, channels 0, 1, and 2 was successfully decoded.

[0245]

[0246] The technical task that the invention seeks to achieve

[0247] Figure 4 shows an example of a sequence configuration between a source device and a sink device.

[0248] Referring to FIG. 4, an example of a sequence configuration between a source device and a sink device is as follows.

[0249] 0. Attach cable between source and sink device

[0250] To transmit A / V data from a source to a sink device, the user connects the two devices with a cable.

[0251] 1. Provide a high level on the +5V power line

[0252] The source device applies the +5V power line to a high level and sends current to operate the EEPROM and related circuits where the EDID information of the sink device is stored.

[0253] 2. Provide a high level on the Hot Plug Detect (HPD) line.

[0254] The EDID-related circuit of the Sink device activated through process 1 transitions the HPD line, which was maintained at a low level, to a high level to inform the Source device that the cable is normally connected and EDID information can be accessed.

[0255] 3. Request for reading EDID / DPID information over Display Data Channel (DDC)

[0256] The source device confirms that the HPD line has transitioned to a high level through process 2 and sends an EDID read request to the sink device through the DDC.

[0257] 4. Send EDID / DPID information over Display Data Channel (DDC)

[0258] In response to the EDID read request from the Source device, the Sink device transmits the EDID information stored in its EEPROM to the Source device via the DDC.

[0259] 5. Parse EDID / DPID and determine operating parameters

[0260] The Source device parses the EDID information and determines the operating parameters (timing, format, DSC compression, etc.) of the A / V data to be transmitted to the Sink device.

[0261] 6. DPCD Request

[0262] The Source device sends a DPCD request to the Sink device.

[0263] The problem with the sequence configuration between the Source device and the Sink device according to the embodiment of FIG. 4 is as follows. Since the Source only reads the Capabilities of the Sink during transmission between the Sink and the Source Device, the Sink can only know the information of the Source through the Infoframe during data transmission. In other words, the Sink can only know the information provided by the Source. If the Source operates with Function A, the Sink cannot know whether the Source can operate with Function B because the Source does not provide information about Function B to the Sink.

[0264]

[0265] Various embodiments of the present disclosure relate to devices using interfaces and DisplayPort and HDMI. Various embodiments of the present disclosure relate to checking source capability information before transmission between a sink device and a source device. Various embodiments of the present disclosure relate to a method for facilitating direct transmission of audio / video data by allowing the sink to know information about the source device. Various embodiments of the present disclosure propose a method for indicating EDID by placing a block similar to or separate from the EDID used by a conventional sink in the source.

[0266] The problems of the prior art that the various embodiments of the present disclosure seek to solve are as follows.

[0267] Previous technology only allowed a source device directly connected to a sink to obtain sink capability information. This risked the sink having to process data delivered by the source without any knowledge of the source device's capabilities. Functions for displaying unchanging source information and information that changed and required updating were very limited.

[0268] According to various embodiments of the present disclosure, the following method is proposed.

[0269] (1) The main transmission line uses DDC lined. However, additional operations are also included for other physical lines.

[0270] (2) The source device reads the information of the sink device using EDID / DisplayID to check whether the source capability information is supported (HDMI / DisplayPort).

[0271] (3) Read the information of the source device from the sink device using SCDC to check whether the source capability is supported. (HDMI)

[0272] (4) Whether Source Capability is supported is read from the Sink device using the Aux Channel. (DisplayPort)

[0273] (5) The sink of the current bus interface checks the source capability function and implements appropriate operation according to the source. (HDMI)

[0274] (6) The sink of the current bus interface checks the source capability function and implements appropriate operation according to the source. (DisplayPort)

[0275] (7) Check the capability information of the source device of the sink device using the separately defined physical channel of the current bus interface.

[0276] The technical effects according to various embodiments of the present disclosure are as follows.

[0277] In most cases, a Sink only needs to receive and process audio / video transmitted by a Source. Once the Sink knows the Source's capabilities, it can support additional functionality based on that information. While the specific information contained in the Source's capabilities is crucial, generally, the general functionality required by the Sink device is sufficient. Furthermore, in the event of connection compatibility issues, the Sink can implement source-based workarounds.

[0278] Additionally, to address the limited EDID space, the Sink can edit and display only the features required by the Source, a process known as EDID Optimization. This requires the Sink to add EDID Edit functionality, but it can precisely select the necessary features, enhancing the user experience.

[0279] If the Source learns of support for a feature that the Sink has not yet declared due to EDID space constraints, the Sink can update the EDID to include that feature. (This is an implementation-specific process called EDID Editing, which updates the EDID. After completing this operation, the Sink turns HPD off and on to force the Source to reread the EDID.)

[0280]

[0281] Composition and operation of the invention

[0282] Figure 5 shows an example of a sequence configuration between a source device and a sink device.

[0283] Referring to FIG. 5, an example of a sequence configuration between a source device and a sink device is as follows.

[0284] 0. Attach cable between source and sink device

[0285] To transmit A / V data from a source to a sink device, the user connects the two devices with a cable.

[0286] 1. Provide a high level on the +5V power line

[0287] The source device applies the +5V power line to a high level and sends current to operate the EEPROM and related circuits where the EDID information of the sink device is stored.

[0288] 2. Provide a high level on the Hot Plug Detect (HPD) line.

[0289] The EDID-related circuit of the Sink device activated through process 1 transitions the HPD line, which was maintained at a low level, to a high level to inform the Source device that the cable is normally connected and EDID information can be accessed.

[0290] 3. Request for reading EDID / DPID information over Display Data Channel (DDC)

[0291] The source device confirms that the HPD line has transitioned to a high level through process 2 and sends an EDID read request to the sink device through the DDC.

[0292] 4. Send EDID / DPID information over Display Data Channel (DDC)

[0293] In response to the EDID read request from the Source device, the Sink device transmits the EDID information stored in its EEPROM to the Source device via the DDC.

[0294] 5. SCDC Write

[0295] If the Sink has a block that can indicate Source Capability, the Source behaves as follows: When indicating to the HDMI SCDC, the Source reads the EDID and then writes the Source Capability information to the SCDC. When indicating to the DisplayPort DPCD, the Source reads the EDID and then writes the Source Capability information to the DPCD.

[0296] The Source transmits the SCDC / DPCD that performs a write operation on the Source Capability to the Sink. The Sink recognizes the Source Capability from the received SCDC / DPCD.

[0297] 6. Send Audio / Video (DSC Compressed)

[0298] The Source transmits DSC compressed audio / video data to the Sink based on the Source Capability.

[0299]

[0300] Figure 6 shows an example of a sequence configuration between a source device and a sink device.

[0301] Referring to FIG. 6, an example of a sequence configuration between a source device and a sink device is as follows.

[0302] 0. Attach cable between source and sink device

[0303] To transmit A / V data from a source to a sink device, the user connects the two devices with a cable.

[0304] 1. Provide a high level on the +5V power line

[0305] The source device applies the +5V power line to a high level and sends current to operate the EEPROM and related circuits where the EDID information of the sink device is stored.

[0306] 2. Provide a high level on the Hot Plug Detect (HPD) line.

[0307] The EDID-related circuit of the Sink device activated through process 1 transitions the HPD line, which was maintained at a low level, to a high level to inform the Source device that the cable is normally connected and EDID information can be accessed.

[0308] 3. Request for reading EDID / DPID information over Display Data Channel (DDC)

[0309] The source device confirms that the HPD line has transitioned to a high level through process 2 and sends an EDID read request to the sink device through the DDC.

[0310] 4. Send EDID / DPID information over Display Data Channel (DDC)

[0311] In response to the EDID read request from the Source device, the Sink device transmits the EDID information stored in its EEPROM to the Source device via the DDC.

[0312] 5. DPCD Write

[0313] If the Sink has a block that can indicate Source Capability, the Source behaves as follows: When indicating to the HDMI SCDC, the Source reads the EDID and then writes the Source Capability information to the SCDC. When indicating to the DisplayPort DPCD, the Source reads the EDID and then writes the Source Capability information to the DPCD.

[0314] The Source transmits the SCDC / DPCD that performs a write operation on the Source Capability to the Sink. The Sink recognizes the Source Capability from the received SCDC / DPCD.

[0315] 6. Send Audio / Video (DSC Compressed)

[0316] The Source transmits DSC compressed audio / video data to the Sink based on the Source Capability.

[0317]

[0318] Figure 7 shows an example of a sequence configuration between a source device and a sink device.

[0319] Referring to FIG. 7, an example of a sequence configuration between a source device and a sink device is as follows.

[0320] 0. Attach cable between source and sink device

[0321] To transmit A / V data from a source to a sink device, the user connects the two devices with a cable.

[0322] 1. Provide a high level on the +5V power line

[0323] The source device applies the +5V power line to a high level and sends current to operate the EEPROM and related circuits where the EDID information of the sink device is stored.

[0324] 2. Provide a high level on the Hot Plug Detect (HPD) line.

[0325] The EDID-related circuit of the Sink device activated through process 1 transitions the HPD line, which was maintained at a low level, to a high level to inform the Source device that the cable is normally connected and EDID information can be accessed.

[0326] 3. Request for reading EDID / DPID information over Display Data Channel (DDC)

[0327] The source device confirms that the HPD line has transitioned to a high level through process 2 and sends an EDID read request to the sink device through the DDC.

[0328] 4. Send EDID / DPID information over Display Data Channel (DDC)

[0329] In response to the EDID read request from the Source device, the Sink device transmits the EDID information stored in its EEPROM to the Source device via the DDC.

[0330] 5. DPCD Write

[0331] If the Source has a block that can indicate the Source Capability, the Source behaves as follows. When indicating on the SCDC / DPCD, the Source reads the EDID and then writes the Source Capability information to the SCDC / DPCD. The Source transmits the SCDC / DPCD that performed the write operation for the Source Capability to the Sink. The Sink recognizes the Source Capability from the received SCDC / DPCD.

[0332] 6. Send Audio / Video (DSC Compressed)

[0333] The Source transmits DSC compressed audio / video data to the Sink based on the Source Capability.

[0334]

[0335] The Source writes Source information to the SCDC block. The Source information written to the SCDC block by the Source is as follows (all information about the Source). Regarding the Source information written to the SCDC block, it is self-evident that additional information, in addition to the information below, can be added to the Source information for future Sink Capabilities.

[0336] (1) HDMI Version (H2.0, H2.1)

[0337] (2) Product ID, Model Name

[0338] (3) Product Type: STB, Gaming Console, Repeater, Laptop, PC, Tablet, etc.

[0339] (4) Supported HDMI Functions

[0340] (4-1) eARC, Gaming-VRR, QMS-VRR, FVA, ALLM, DSC

[0341] (5) Max_TMDS_Charter_Rate

[0342] (6) Max_FRL_Rate

[0343] (7) Source Chroma Sampling

[0344] (7-1) 4:4:4, 4:2:2, 4:2:0

[0345] (8) Source support Bit depth: 8bit, 10bit, 16bit

[0346] (9) HDR Type: Static HDR, Dynamic HDR, HDR10, HDR10+

[0347] For HDMI, this function is implemented as an extended structure of SCDC as a HW Block in Sink.

[0348] For DisplayPort, this function is implemented as an extended structure of DPCD as a HW Block in Sink.

[0349] FIG. 8 illustrates an example of a sequence configuration between a source device and a sink device according to various embodiments of the present disclosure.

[0350] Referring to FIG. 8, an example of a sequence configuration between a source device and a sink device is as follows.

[0351] 0. Attach cable between Source and Sink devices

[0352] To transmit A / V data from a source to a sink device, the user connects the two devices with a cable.

[0353] 1. Provide a high level on the +5V power line

[0354] The source device applies the +5V power line to a high level and sends current to operate the EEPROM and related circuits where the EDID information of the sink device is stored.

[0355] 2. Provide a high level on the Hot Plug Detect (HPD) line.

[0356] The EDID-related circuit of the Sink device activated through process 1 transitions the HPD line, which was maintained at a low level, to a high level to inform the Source device that the cable is normally connected and EDID information can be accessed.

[0357] 3. Request for reading EDID / DPID information over Display Data Channel (DDC)

[0358] The source device confirms that the HPD line has transitioned to a high level through process 2 and sends an EDID read request to the sink device through the DDC.

[0359] 4. Send EDID / DPID information over Display Data Channel (DDC)

[0360] In response to the source device's EDID read request, the sink device transmits the EDID information stored in its EEPROM to the source device via the DDC. Up to this point, the initial operation is the same as before.

[0361] 5. SCDC Write

[0362] In SCDC, Source writes Source Capability to Sink SCDC block.

[0363] If the Sink has a block that can indicate Source Capability, the Source behaves as follows: When indicating to the HDMI SCDC, the Source reads the EDID and then writes the Source Capability information to the SCDC. When indicating to the DisplayPort DPCD, the Source reads the EDID and then writes the Source Capability information to the DPCD.

[0364] The Source transmits the SCDC / DPCD that performed the Write operation on the Source Capability to the Dink. The Sink reads the Source Capability information written to the SCDC. The Sink recognizes the Source Capability from the received SCDC / DPCD.

[0365] 6. Conditionally send audio / video (DSC compressed)

[0366] The Source conditionally transmits DSC compressed audio / video data to the Sink based on the Source Capability.

[0367] If the highest EDID version or DPID version supported by the Source Capability corresponds to the EDID / DPID information already received, send DSC compressed audio / video data to the Sink.

[0368] However, if the highest EDID version or DPID version supported by the Source Capability is higher than the EDID / DPID information already received, the DSC compressed audio / video data is not transmitted to the Sink.

[0369] Sink performs EDID update through EDID editing in the Sink system.

[0370] The Sink either leaves the EDID information as is, or if an EDID change is required, edits the EDID and updates the editing information in the EDID. In this case, the HPD off / on causes the Source to reread the Sink EDID.

[0371] Even if the Sink doesn't update the EDID after reading the Source Capability, it can still take necessary actions based on the Source information. For example, it can disable unused features (increase available resources, reduce power consumption, etc.).

[0372] 2-2. Provide a high level on the Hot Plug Detect (HPD) line

[0373] The EDID-related circuit of the Sink device transitions the HPD line, which was maintained at a low level, to a high level to inform the Source device that the cable is connected normally and EDID information can be accessed.

[0374] 2-3. Request for reading EDID / DPID information over Display Data Channel (DDC)

[0375] The source device confirms that the HPD line has transitioned to a high level through process 2-2 and sends an EDID read request to the sink device through the DDC.

[0376] 2-4. Send EDID / DPID information over Display Data Channel (DDC)

[0377] In response to the EDID read request from the Source device, the Sink device transmits the EDID information stored in its EEPROM to the Source device via the DDC.

[0378] 2-6. Send Audio / Video (DSC Compressed)

[0379] The highest EDID or DPID version supported by the Source Capability will correspond to the newly received updated EDID / DPID information. Accordingly, the Source transmits DSC-compressed audio / video data to the Sink based on the Source Capability.

[0380]

[0381] Source writes source information to the SCDC block.

[0382] Source information is as follows:

[0383] Source Version is used as an example. The field offset and version-specific values ​​are examples and may change in actual application.

[0384] OffsetBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 00XDD

[0385] If Offset is 0x00, Source Version: H1.4b

[0386] Offset is 0x01 Source Version: H2.0

[0387] Offset is 0x02 Source Version: H2.1

[0388] Offset is 0x03 Source Version: H3.0

[0389]

[0390] Supported HDMI Functions is used as an example. The field offset and version-specific values ​​are examples and may change in actual application.

[0391] OffsetBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 00XF1ReservedReservedeARCGaming-VRRQMS-VRRFVAALLMDSC

[0392]

[0393] Bit 0: If the source supports DSC, set it to 1; otherwise, set it to 0. (Bit 0: If the source supports DSC, set it to 1; if not, set it to 0)

[0394] Bit 1: Set to 1 if the source supports ALLM, otherwise set to 0. (Bit 1: If the source supports ALLM, then set to 1, if not, set to 0)

[0395]

[0396] Information written in Source Capability can utilize information written in existing Sink Capability.

[0397] The corresponding function block can be utilized in the Sink Capability information according to Table 13 below.

[0398] Byte / Bit#76543210PB1Version (=1)PB2Max_TDMS_Character_RatePB3SCDC_PresentRR_CapableCABLE_STATUSCCBPCILTE_340Mcsc_scrambleIndependent_Vie wDual_View3D_OSD_DisparityPB4Max_FRL_RateUHD_VICDC_48Bit_420DC_36bit_420DC_30bit_420PB5FAPA_End_ExtendedQMSM Delta CinemaVRR(Deprecated)NEG_MVRRFVAALLMFAPA_start_locationPB6VRR MAX VRR MIN PB7VRR MAX PB8DSC_1p2DSC_Native_420QMS-TFR MAX QMS-TFR MINDSC_All_bppDSC_16bpc(=0)DSC_12bpcDSC_10bpcPB9DSC_Max_FRL_RateDSC_MaxSlicesPB10Rsvd(0)Rsvd(0)DSC_TotalChunkKBytesPB11..PB28Rsvd(0)

[0399]

[0400]

[0401] [Source device claim related description]

[0402] The embodiments described below are specifically described with reference to FIG. 9 in terms of terminal operation. The methods described below are distinguished for convenience of explanation, and it is understood that, unless mutually exclusive, some components of one method may be substituted for or combined with some components of another method.

[0403] FIG. 9 is a diagram illustrating an example of an operation process of a source device according to various embodiments of the present disclosure.

[0404] According to various embodiments of the present disclosure, a method is provided that is performed by a source device.

[0405] The source device includes a processor; a memory; and a transceiver. The memory stores instructions for performing operations based on those executed by the processor.

[0406] At step S901, the source device receives a hot plug detection (HPD) signal from the sink device.

[0407] In step S902, the source device transmits a request for EDID (Extended Display Identification) or DPID (DisplayID) to the sink device via DDC (Display Data Channel).

[0408] In step S903, the source device receives first information of the EDID or the DPID from the sink device.

[0409] In step S904, the source device transmits second information including source capability information to the sink device based on the first information of the EDID or the DPID.

[0410] In step S905, the source device transmits compressed source data to the sink device based on the source capability information.

[0411]

[0412] According to various embodiments of the present disclosure, the second information may be SCDC (Status and Control Data Channel) or DPCD (DisplayPort Configuration Data). The source capability information may be included by a write operation to the SCDC or DPCD.

[0413] According to various embodiments of the present disclosure, if the EDID version or DPID version of the EDID or DPID is higher than or equal to a set reference version, and the supported version of the source is higher than or equal to the reference version: the source capability information may be based on the supported version of the source.

[0414] According to various embodiments of the present disclosure, when the EDID version or DPID version of the EDID or DPID is lower than a set reference version, and the supported version of the source is higher than or equal to the reference version: the source capability information may be based on the EDID version or the DPID version.

[0415] According to various embodiments of the present disclosure, if the EDID version or DPID version of the EDID or DPID is higher than or equal to a set reference version, and the supported version of the source is lower than the reference version: the source capability information may be based on the supported version of the source.

[0416] According to various embodiments of the present disclosure, if the EDID version or DPID version of the EDID or DPID is lower than a set reference version, and the supported version of the source is lower than the reference version: the source capability information may be based on the supported version of the source.

[0417] According to various embodiments of the present disclosure, the embodiment of FIG. 9 may further include a step of receiving an updated second EDID or second DPID based on a supported version of the source from the sink device. The source data may be compressed based on the supported version of the source and then transmitted to the sink device.

[0418]

[0419] According to various embodiments of the present disclosure, a source device is provided. The source device includes a processor; a memory; and a transceiver, wherein the processor may be configured to perform a method of operating the source device according to FIG. 9.

[0420]

[0421] According to various embodiments of the present disclosure, a device for controlling a source device is provided. The device includes at least one processor and at least one memory operably connected to the at least one processor. The at least one memory may be configured to store instructions for performing an operating method of the source device according to FIG. 9 based on instructions executed by the at least one processor.

[0422]

[0423] [Sink device claim description]

[0424] The embodiments described below are specifically described with reference to FIG. 9 in terms of terminal operation. The methods described below are distinguished for convenience of explanation, and it is understood that, unless mutually exclusive, some components of one method may be substituted for or combined with some components of another method.

[0425] FIG. 10 is a diagram illustrating an example of an operation process of a sink device according to various embodiments of the present disclosure.

[0426] According to various embodiments of the present disclosure, a method performed by a sink device is provided.

[0427] A sink device includes a processor; memory; and a transceiver. The memory stores instructions for performing operations based on those executed by the processor.

[0428] At step S1001, the Sink device transmits a hot plug detection (HPD) signal to the Source device.

[0429] In step S1002, the Sink device receives a request for EDID (Extended Display Identification) or DPID (DisplayID) from the source device through DDC (Display Data Channel).

[0430] In step S1003, the Sink device transmits the first information of the EDID or the DPID to the source device.

[0431] In step S1004, the Sink device receives second information including source capability information from the source device based on the first information of the EDID or the DPID.

[0432] In step S1005, the Sink device receives compressed source data from the source device based on the source capability information.

[0433]

[0434] According to various embodiments of the present disclosure, the second information may be SCDC (Status and Control Data Channel) or DPCD (DisplayPort Configuration Data). The source capability information may be included by a write operation to the SCDC or DPCD.

[0435] According to various embodiments of the present disclosure, if the EDID version or DPID version of the EDID or DPID is higher than or equal to a set reference version, and the supported version of the source is higher than or equal to the reference version: the source capability information may be based on the supported version of the source.

[0436] According to various embodiments of the present disclosure, when the EDID version or DPID version of the EDID or DPID is lower than a set reference version, and the supported version of the source is higher than or equal to the reference version: the source capability information may be based on the EDID version or the DPID version.

[0437] According to various embodiments of the present disclosure, if the EDID version or DPID version of the EDID or DPID is higher than or equal to a set reference version, and the supported version of the source is lower than the reference version: the source capability information may be based on the supported version of the source.

[0438] According to various embodiments of the present disclosure, if the EDID version or DPID version of the EDID or DPID is lower than a set reference version, and the supported version of the source is lower than the reference version: the source capability information may be based on the supported version of the source.

[0439] According to various embodiments of the present disclosure, the embodiment of FIG. 10 may further include a step of transmitting an updated second EDID or second DPID based on a supported version of the source to the source device. The source data may be compressed based on the supported version of the source and then received from the source device.

[0440]

[0441] According to various embodiments of the present disclosure, a sink device is provided. The sink device includes a processor; a memory; and a transceiver, wherein the processor may be configured to perform a method of operating the sink device according to FIG. 10.

[0442]

[0443] According to various embodiments of the present disclosure, a device for controlling a sink device is provided. The device includes at least one processor and at least one memory operably connected to the at least one processor. The at least one memory may be configured to store instructions for performing an operating method of the sink device according to FIG. 10 based on instructions executed by the at least one processor.

[0444]

[0445] According to various embodiments of the present disclosure, one or more non-transitory computer-readable media (CRM) storing one or more commands are provided. The one or more commands, when executed by one or more processors, perform operations, and the operations may include an operating method of a source device according to FIG. 10.

[0446]

[0447] The claims described in the various embodiments of the present disclosure may be combined in various ways. For example, the technical features of the method claims of the various embodiments of the present disclosure may be combined and implemented as a device, and the technical features of the device claims of the various embodiments of the present disclosure may be combined and implemented as a method. Furthermore, the technical features of the method claims of the various embodiments of the present disclosure may be combined and implemented as a device, and the technical features of the method claims of the various embodiments of the present disclosure may be combined and implemented as a method.

Claims

1. In the method of operating the source device, A step of receiving a hot plug detection (HPD) signal from a sink device; A step of transmitting a request for EDID (Extended Display Identification) or DPID (DisplayID) to the above sink device through DDC (Display Data Channel); A step of receiving first information of the EDID or the DPID from the sink device; A step of transmitting second information including source capability information to the sink device based on the first information of the EDID or the DPID; A step of transmitting compressed source data to the sink device based on the source capability information, method.

2. In paragraph 1, The second information is SCDC (Status and Control Data Channel) or DPCD (DisplayPort Configuration Data), The above source capability information is included by a write operation to the SCDC or the DPCD. method.

3. In paragraph 1, If the EDID version or DPID version of the above EDID or DPID is higher than or equal to the set reference version, and the supported version of the source is higher than or equal to the reference version: the source capability information is based on the supported version of the source. method.

4. In paragraph 1, If the EDID version or DPID version of the above EDID or DPID is lower than the set reference version and the supported version of the source is higher than or equal to the reference version: the source capability information is based on the EDID version or the DPID version. method.

5. In paragraph 1, If the EDID version or DPID version of the above EDID or DPID is higher than or equal to the set reference version and the supported version of the source is lower than the reference version: the source capability information is based on the supported version of the source. method.

6. In paragraph 1, If the EDID version or DPID version of the above EDID or DPID is lower than the set reference version and the supported version of the source is lower than the reference version: the source capability information is based on the supported version of the source. method.

7. In paragraph 5, Further comprising the step of receiving an updated second EDID or second DPID based on the supported version of the source from the sink device, The above source data is compressed based on the supported version of the source and then transmitted to the sink device. method.

8. In the method of operating the sink device, A step of transmitting a hot plug detection (HPD) signal to a source device; A step of receiving a request for EDID (Extended Display Identification) or DPID (DisplayID) from the source device through DDC (Display Data Channel); A step of transmitting first information of the EDID or the DPID to the source device; A step of receiving second information including source capability information from the source device based on the first information of the EDID or the DPID; A step of receiving compressed source data from the source device based on the source capability information, method.

9. In paragraph 8, The second information is SCDC (Status and Control Data Channel) or DPCD (DisplayPort Configuration Data), The above source capability information is included by a write operation to the SCDC or the DPCD. method.

10. In paragraph 8, If the EDID version or DPID version of the above EDID or DPID is higher than or equal to the set reference version, and the supported version of the source is higher than or equal to the reference version: the source capability information is based on the supported version of the source. method.

11. In paragraph 8, If the EDID version or DPID version of the above EDID or DPID is lower than the set reference version and the supported version of the source is higher than or equal to the reference version: the source capability information is based on the EDID version or the DPID version. method.

12. In paragraph 8, If the EDID version or DPID version of the above EDID or DPID is higher than or equal to the set reference version and the supported version of the source is lower than the reference version: the source capability information is based on the supported version of the source. method.

13. In paragraph 8, If the EDID version or DPID version of the above EDID or DPID is lower than the set reference version and the supported version of the source is lower than the reference version: the source capability information is based on the supported version of the source. method.

14. In paragraph 12, Further comprising the step of transmitting an updated second EDID or second DPID based on the supported version of the source to the source device, The above source data is received from the source device after being compressed based on the supported version of the source. method.

15. In the source device, A processor; memory; and a transceiver, The above memory stores instructions for performing operations based on what is executed by the processor, The above actions are, A step of receiving a hot plug detection (HPD) signal from a sink device; A step of transmitting a request for EDID (Extended Display Identification) or DPID (DisplayID) to the above sink device through DDC (Display Data Channel); A step of receiving first information of the EDID or the DPID from the sink device; A step of transmitting second information including source capability information to the sink device based on the first information of the EDID or the DPID; A step of transmitting compressed source data to the sink device based on the source capability information, Source device.

16. In paragraph 15, The second information is SCDC (Status and Control Data Channel) or DPCD (DisplayPort Configuration Data), The above source capability information is included by a write operation to the SCDC or the DPCD. Source device.

17. In paragraph 15, If the EDID version or DPID version of the above EDID or DPID is higher than or equal to the set reference version, and the supported version of the source is higher than or equal to the reference version: the source capability information is based on the supported version of the source. Source device.

18. In paragraph 15, If the EDID version or DPID version of the above EDID or DPID is lower than the set reference version and the supported version of the source is higher than or equal to the reference version: the source capability information is based on the EDID version or the DPID version. Source device.

19. In paragraph 15, If the EDID version or DPID version of the above EDID or DPID is higher than or equal to the set reference version and the supported version of the source is lower than the reference version: the source capability information is based on the supported version of the source. Source device.

20. In paragraph 15, If the EDID version or DPID version of the above EDID or DPID is lower than the set reference version and the supported version of the source is lower than the reference version: the source capability information is based on the supported version of the source. Source device.

Images