WO2016122213A1 - Procédé de transmission et de réception de données au moyen de hdmi et de dispositif s'y rapportant - Google Patents

Procédé de transmission et de réception de données au moyen de hdmi et de dispositif s'y rapportant Download PDF

Info

Publication number
WO2016122213A1
WO2016122213A1 PCT/KR2016/000892 KR2016000892W WO2016122213A1 WO 2016122213 A1 WO2016122213 A1 WO 2016122213A1 KR 2016000892 W KR2016000892 W KR 2016000892W WO 2016122213 A1 WO2016122213 A1 WO 2016122213A1
Authority
WO
WIPO (PCT)
Prior art keywords
video mute
mute function
sink device
source device
video
Prior art date
Application number
PCT/KR2016/000892
Other languages
English (en)
Korean (ko)
Inventor
김도균
양현식
이현재
박장웅
임진권
Original Assignee
엘지전자(주)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자(주) filed Critical 엘지전자(주)
Publication of WO2016122213A1 publication Critical patent/WO2016122213A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H04N21/4363—Adapting the video stream to a specific local network, e.g. a Bluetooth® network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H04N21/4367—Establishing a secure communication between the client and a peripheral device or smart card
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/44—Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream or rendering scenes according to encoded video stream scene graphs
    • H04N21/4402—Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream or rendering scenes according to encoded video stream scene graphs involving reformatting operations of video signals for household redistribution, storage or real-time display

Definitions

  • the present invention relates to a data transmission and reception apparatus and method using a high definition multimedia interface (HDMI), and more particularly, to a method and apparatus for controlling a video mute function of a sink device through a source device.
  • HDMI high definition multimedia interface
  • HDMI is an interface / standard developed for AV electronics using DVI (Digital Visual Interface), a standard for personal computers and displays.
  • HDMI is a source that is transmitted from the player to the display device without compressing video / audio. There is little latency between the device and the sink device, and there is no need for a separate decoder chip or software, resulting in high format compatibility.
  • video, audio, and control signals are all transmitted in one cable, simplifying the wiring of complex AV devices, and supporting high-bandwidth digital content protection (HDCP) for password protection. It can even provide protection.
  • HDMI is an interface / standard developed for AV electronics using DVI (Digital Visual Interface), a standard for personal computers and displays.
  • HDMI is a source that is transmitted from the player to the display device without compressing video / audio. There is little latency between the device and the sink device, and there is no need for a separate decoder chip or software, resulting in high format compatibility.
  • video, audio, and control signals are all transmitted in one cable, simplifying the wiring
  • the video mute function of a sink device cannot be controlled using a source device connected through HDMI. Accordingly, there has been an inconvenience in that the user must directly manipulate the sink device to control the video mute function of the sink device.
  • a method of transmitting and receiving data of a source device using a high definition multimedia interface comprising the steps of: connecting to the sink device via the HDMI; Receiving Extended Display Identification Data (EDID) information from the sink device; Parsing the received EDID information and determining an operating parameter; Transmitting a message instructing execution of a video mute function to the sink device; And receiving video mute state information about whether the video mute function is currently being executed from the sink device at a predetermined period. It may include.
  • EDID Extended Display Identification Data
  • the data transmitting / receiving method of the source device may further include retransmitting a message instructing execution of the video mute function to the sink device when receiving the video mute state information indicating the termination of the video mute function; It may further include.
  • the transmitting of the message indicating the execution of the video mute function may include receiving a user input for instructing execution of the video mute function or executing the video mute function through a user interface related to the video mute function. This may be a step performed when a preset external input indicating is received.
  • the preset external input may be an input received from an external device controlling the source device.
  • the preset period may be set through a user interface related to the video mute function provided by the source device.
  • the message indicating the execution of the video mute function and the video mute state information may be transmitted and received as a CEC (Consumer Electronic Control) message format.
  • CEC Consumer Electronic Control
  • a method for transmitting and receiving data of a sink device using a high definition multimedia interface comprising: connecting to a source device through the HDMI; Transmitting Extended Display Identification Data (EDID) information to the source device; Receiving a message instructing execution of a video mute function from the source device; Executing the video mute function; And transmitting video mute state information on whether the current video mute function is being executed to the source device at a predetermined period. It may include.
  • EDID Extended Display Identification Data
  • the method for transmitting / receiving data of the sink device may include: ending the video mute function; And transmitting video mute state information indicating the end of the video mute function to the source device. It may further include.
  • the data transmission and reception method of the sink device comprises the steps of: receiving a message instructing the execution of the video mute function from the source device; And rerunning the video mute function; It may further include.
  • the message indicating the execution of the video mute function and the video mute state information may be transmitted and received as a CEC message format.
  • a source device for transmitting and receiving data using a High Definition Multimedia Interface HDMI source for transmitting and receiving data through the HDMI; And a microcomputer (MICOM) generating a signal for data transmission.
  • the source device is connected to the sink device via the HDMI, receives EDID (Extended Display Identification Data) information from the sink device, parses the received EDID information, and operates an operating parameter. Determine, and transmit a message instructing the execution of the video mute function to the sink device, and receives video mute state information about whether the video mute function is currently being executed from the sink device at a predetermined period.
  • EDID Extended Display Identification Data
  • the source device may retransmit a message instructing the execution of the video mute function to the sink device.
  • a sink device for transmitting and receiving data using a high definition multimedia interface HDMI device for transmitting and receiving data through the HDMI; And a microcomputer (MICOM) generating a signal for data transmission.
  • the sink device is connected to a source device through the HDMI, transmits Extended Display Identification Data (EDID) information to the source device, and instructs execution of a video mute function from the source device.
  • EDID Extended Display Identification Data
  • Receive a message execute the video mute function, and transmit video mute state information regarding whether the video mute function is currently executed to the source device at a predetermined period.
  • the sink device may terminate the video mute function and transmit video mute state information indicating the end of the video mute function to the source device.
  • the sink device may re-receive a message instructing execution of the video mute function from the source device and re-execute the video mute function.
  • the present invention has an effect that it is possible to control the video mute function of the sink device more easily and efficiently through the source device.
  • the present invention can control the video mute function of the sink device through the source device, it is advantageous to reduce the power consumption caused by unnecessary video output of the sink device using the source device.
  • the present invention ensures that the video mute function is maintained by the source device and / or the sink device periodically checking whether the video mute function is executed even if the video mute function of the sink device is automatically terminated, thereby reducing unnecessary power consumption. It can be prevented from occurring.
  • FIG. 1 is a block diagram illustrating an HDMI system according to an embodiment of the present invention.
  • FIG. 2 is a block diagram of an HDMI CEC system according to an embodiment of the present invention.
  • 3 and 4 illustrate a structure of a CEC message according to an embodiment of the present invention.
  • FIG. 5 is a flowchart illustrating a method for transmitting and receiving data between a source device and a sink device according to an embodiment of the present invention.
  • FIG. 6 is a flowchart illustrating a method of executing a video mute function according to a first embodiment of the present invention.
  • FIG. 7 is a flowchart illustrating a method of executing a video mute function according to a second embodiment of the present invention.
  • FIG. 8 is a flowchart illustrating a method of executing a video mute function according to an embodiment of the present invention.
  • FIG. 9 is a flowchart illustrating a method of ending video mute function according to a first embodiment of the present invention.
  • FIG. 10 is a flowchart illustrating a method of ending video mute function according to a first embodiment of the present invention.
  • FIG. 11 is a flowchart of a method of ending a video mute function according to a second embodiment of the present invention.
  • FIG. 12 is a flowchart of a method of ending a video mute function according to a second embodiment of the present invention.
  • FIG. 13 is a flowchart of a method of ending a video mute function according to a third embodiment of the present invention.
  • FIG. 14 is a flowchart illustrating a method of ending a video mute function according to a third embodiment of the present invention.
  • FIG. 15 is a table listing commands transmitted and received between a source device and a sink device according to an embodiment of the present invention.
  • 16 is a flowchart of a source device and a sink device for controlling a video mute function by transmitting and receiving a CEC message.
  • FIG. 17 illustrates a CEC message format according to an embodiment of the present invention.
  • 18 through 21 are flowcharts illustrating specific embodiments of executing a video mute function.
  • 22 is a flowchart illustrating a specific operation embodiment of a source device and a sink device for maintaining execution of a video mute function.
  • FIG. 1 is a block diagram illustrating an HDMI system according to an embodiment of the present invention.
  • an HDMI (High Definition Multimedia Interface) system includes an initiator (Initiator) that is a device for transmitting a Consumer Electronic Control (CEC) message and a follower (1010) that is a device for receiving and responding to a CEC message. It may include.
  • Initiator 1020 represents a device that initiates a CEC command and sends a CEC command to the follower to control the follower.
  • the follower 1010 may indicate a device that responds to the received CEC command and performs a CEC command to inform the result.
  • Both devices may include a bus interface 1030, a MICOM 1040, a buffer 1080, a bus protocol layer 1090, and an upper layer 1110, respectively. Can be. That is, both devices may include the same configurations in common. Configurations commonly included in both devices may be logical or physical units within a device performing a specific operation, and one configuration may correspond to one or more devices, or one or more devices may correspond to one device. have. Hereinafter, the components commonly included in both devices will be described in detail.
  • the bus interface 1030 represents a physical device that enables the transmission of a message or data such as a command, a request, an action, or a response between two devices.
  • the microcomputer 1040 represents a physical device that generates a signal for data transmission or manages transmission priority, retransmission for reliable transmission, and the like.
  • the microcomputer 1040 includes a mode protocol 1050 that manages efficient resources required for high speed and low speed data transmission.
  • the mode protocol 1050 represents a protocol for performing efficient resource management required for high speed / low speed data transmission.
  • High mode 1060 represents a logical device that is responsible for high speed data transfer related processing of bus structure connections.
  • Low mode 1070 represents a logical device that is responsible for the slow data transfer related processing of the bus structure connections.
  • the buffer 1080 represents a physical device that temporarily stores them to improve the reliability of transmitted messages or data.
  • the bus protocol layer 1090 represents a logical device that processes data transmitted through a bus structure transmission method and delivers necessary information to upper layers.
  • the bus protocol layer 1090 may include a Mode Decision Component 1100.
  • Upper layer 1110 represents a logical / physical device that substantially processes instructions.
  • FIG. 2 is a block diagram of an HDMI CEC system according to an embodiment of the present invention.
  • HDMI CEC HDMI Consumer Electronic Control
  • HDMI CEC HDMI Consumer Electronic Control
  • the HDMI CEC system may largely include a follower 2010 and an initiator 2020.
  • the follower 2010 may include an HDMI connector 2030, an HDMI receiver 2050, a central processing unit (CPU) 2070, and a microcomputer 2100.
  • the initiator 2020 may include an HDMI connector 2030, an HDMI transmitter (or HDMI receiver) 2060, a central processing unit (CPU) 2070, and a microcomputer 2100.
  • the HDMI connector 2030 may include five types of connectors, such as types A, B, C, D, and E.
  • type A is a 19-pin general HDMI connector
  • type B is a 29-pin connector for transmitting UHD video
  • type C is a 19-pin mini connector
  • type D is a 19-pin micro connector
  • Type E may represent a vehicle connector.
  • the HDMI transmitter 2060 and the HDMI receiver 2050 use a HDMI connector 2030 to transmit a plurality of TMDS (Transition Minimized Differential Signaling) data transmission channels for transmitting multimedia information. Communication may be performed through the 2040 and the Consumer Electronics Control (CEC) channel 2110.
  • the HDMI transmitter 2060 and the HDMI receiver 2050 may include a clock channel (not shown), a display data channel (DDC) (not shown), a utility channel (not shown), and a hot plug detect (HPD) channel ( Communication may also be performed through control channels such as (not shown).
  • the TMDS channel 2040 may consist of three data transmission channels, and transmits video and audio data.
  • the CEC channel 2110 is a control channel that delivers the CEC protocol, which is a control command that enables the control of the devices connected through HDMI using a TV remote control. This feature allows One Touch Play. That is, without the need to control each device connected via HDMI, such as a function to perform the playback of the connected playback device using the TV remote control, it is possible to control with a single remote control to increase user convenience.
  • the central processing unit (CPU) 2070 of the follower 2010 includes a graphical user interface (GUI) layer 2080, an application layer 2080, and a CEC protocol layer 2090. ) May be included.
  • the central processing unit (CPU) 2070 of the initiator 2020 may include an application layer 2080 and a CEC protocol layer 2090.
  • the GUI layer 2080 may process data to output data received through the HDMI receiver 2050 through the GUI.
  • the application layer 2080 may process data in a manner defined by a user.
  • the CEC protocol layer 2090 processes the transmitted CEC data and transmits necessary information to an upper layer.
  • the CPU 2070 may perform communication by transmitting and receiving a microcomputer 2100 and a CEC header / data block (10 bits) to be described later.
  • the microcomputer 2100 may generate a signal for data transmission or manage (or signal processing) transmission priority, retransmission for reliable transmission, and the like. For example, the microcomputer 2100 may perform frame re-transmission, line error handling, frame validation, and the like. In addition, the microcomputer 2100 may serve as an interface for performing HDMI CEC signal processing through data communication in a frame unit with a central processing unit (CPU).
  • CPU central processing unit
  • 3 and 4 illustrate a structure of a CEC message according to an embodiment of the present invention.
  • CEC makes it possible to operate a device connected via HDMI with a single remote control.
  • each device has a physical address, and devices that support CEC have an additional logical address.
  • Each device can send and receive CEC messages through the CEC line when an event occurs, and each message can have the following functions.
  • One Touch Play One-click playback starts and the device changes to the active source.
  • Routing Control Controls routing of HDMI networks when the CEC switch is in use.
  • Preset Transfer Transfers tuner channel settings to another TV set.
  • Timer Programming Set the timer on another device
  • System Information Set the device to use the same OSD and menu language as the TV.
  • Tuner Control Controls the tuner of another device
  • OSD Display Sends text from the device to display on the TV set
  • Device Menu Control Allows you to control the device menus with the TV remote control.
  • Vendor Specific Commands Manufacturer-defined commands
  • the CEC message may be transmitted through a CEC frame.
  • the CEC frame includes a start bit, a header block, and an optional data block (first and second data blocks 1 and 2). can do.
  • Each block may have a size of 10 bits, and the maximum size of the remaining blocks except for the start bit may be 16 * 10 bits.
  • the CEC header block includes the address (logical address) of the source device (or initiator) and the address (logical address) of the destination, the first data block is composed of an Opcode block, and the second data block is an operand ( operand) block.
  • the opcode may mean a name used to identify the message. Opcode blocks and operand blocks may be selectively applied. The operand block may be determined based on the opcode.
  • Each data block and header block may include an information bits field, an end of message field, and an acknowledgment field.
  • the information bits field may include data, an opcode or an address.
  • the End Of Message (EOM) field is a bit indicating whether the last block of the message. For example, if the value of the End Of Message (EOM) field is '0', then one or more additional data blocks exist (or not the last block of the message); if '1', the message is complete ( Or the last block of a message).
  • the ACK field is sent by setting the initiator to '1' and can be used to inform the follower that the message has been received by marking it as '0'.
  • FIG. 5 is a flowchart illustrating a method for transmitting and receiving data between a source device and a sink device according to an embodiment of the present invention. Each step of the flowchart described below may be selectively applied according to an embodiment, and additional steps may be added.
  • the sink device and the source device may be connected by a cable (HDMI cable) (S5010).
  • a cable HDMI cable
  • the source device may provide a high level to the power line of + 5V (S5020). More specifically, the source device can switch the + 5V power line from low level to high level and apply current. This allows the source device to operate the EEPROM and associated circuits in which Extended Display Identification Data (EDID) information of the sink device is stored.
  • EDID Extended Display Identification Data
  • the sink device may provide a high level to the Hot Plug Detect (HPD) line (S5030). More specifically, the sink device may inform the source device 1010 that the cable is normally connected by switching the HPD line from the low level to the high level, and that the EDID related circuit is activated to enable access of the EDID information.
  • HPD Hot Plug Detect
  • the source device may request to read the EDID information to the sink device through the DDC (S5040).
  • the source device checks that the HPD line is transitioned to a high level through step S5030, and requests the sink device to read EDID information through the DDC.
  • the sink device may transmit EDID information through the DDC (S5050). More specifically, the sink device may transmit EDID information stored in the EEPROM to the source device through the DDC in response to the EDID read request of the source device.
  • the source device may parse the EDID (or EDID information) and determine an operation parameter (S1060).
  • the source device may parse the received EDID information and determine an operation parameter (timing, format, etc.) of data (for example, A / V (Audio / Video) data) to be transmitted to the sink device.
  • the source device may transmit an operation parameter determined in relation to the data to be transmitted to the sink device.
  • the source device does not provide a function for controlling the video mute function of the sink device. Therefore, there is an inconvenience in that the user has to operate the sink device separately from the source device in order to set the video muting function of the sink device (for example, the user sets the sink device to a power saving mode or the display of the sink device's display). Power off).
  • the video mute function may mean a function of stopping (or deactivating) output of a video such as cutting off power of the display. Therefore, in order to solve the inconvenience described above, a control method for controlling the video mute function of the sink device through the source device will be described in detail below.
  • FIG. 6 is a flowchart illustrating a method of executing a video mute function according to a first embodiment of the present invention.
  • steps S5010 to S5060 are the same as described above with reference to FIG. 5, and thus redundant descriptions are omitted.
  • the source device may turn on the video mute function of the sink device (S5070).
  • the source device may control the sink device such that the sink device executes the video mute function.
  • the source device may transmit a command to the sink device to instruct the execution of the video mute function.
  • the sink device may execute the video mute function according to the received command.
  • the sink device may transmit the video mute state to the source device (S5080). More specifically, the sink device may transmit information on a video mute state of the current sink device (hereinafter referred to as "video mute state information") as a response to the video mute function execution command received from the source device. Therefore, in the present embodiment, the sink device may transmit video mute state information indicating that the video mute function is currently executed to the source device.
  • video mute state information a video mute state of the current sink device
  • This step (S5080) may be selectively applied according to the embodiment. Accordingly, the sink device may or may not transmit the current video mute state information to the source device according to an embodiment.
  • command and status information may be defined and transmitted as a CEC message, and in this regard, it will be described later in detail with reference to FIGS. 15 to 17.
  • FIG. 7 is a flowchart illustrating a method of executing a video mute function according to a second embodiment of the present invention.
  • steps S5010 to S5060 are the same as described above with reference to FIG. 5, and thus redundant descriptions are omitted.
  • the source device may request a video mute state from the sink device (S5090).
  • the source device may request the sink device for information about the current video mute state of the sink device.
  • the source device may request the sink device for information on whether the sink device is currently executing a video mute function.
  • the sink device may respond to the video mute state (S5100).
  • the sink device may receive a video mute state from the source device, and respond to the current video mute state of the sink device in response to the request.
  • the sink device may supply video mute state information (or video mute state information indicating that it is not currently executing the video mute function) as a response to the request of the source device. Can be sent to.
  • This step S5100 may be selectively applied according to an embodiment. Accordingly, the sink device may or may not transmit current video mute state information to the source device even when the video mute state is requested from the source device according to the embodiment.
  • the video mute status request and the video mute status response described above may be defined and transmitted as a CEC message and will be described later in detail with reference to FIGS. 15 to 17.
  • FIG. 8 is a flowchart illustrating a method of executing a video mute function according to an embodiment of the present invention.
  • the flowcharts described above with reference to FIGS. 6 and 7 may be equally applied, and redundant descriptions thereof will be omitted.
  • the source device may video mute the sink device (S8010).
  • the source device may transmit a command to the sink device to instruct the execution of the video mute function.
  • the sink device may determine whether to support the video mute function (S8020). In more detail, the sink device may determine whether to support the video mute function according to the execution command of the video mute function of the source device.
  • the sink device may execute the video mute function (S8030). More specifically, when the sink device supports the video mute function, the sink device may execute the video mute function according to the instruction to execute the video mute function of the source device.
  • the sink device may not execute the video mute function and thus may fail to execute the video mute function (S8040).
  • the sink device may transmit the video mute state to the source device (S8050).
  • the sink device may transmit the video mute state information, which is information on whether the video mute function is currently executed, to the source device. If the sink device supports the video mute function and executes the video mute function according to the command of the source device, the sink device may transmit the video mute state information indicating that the sink device is currently executing the video mute function to the source device. On the contrary, when the sink device does not support the video mute function and fails to execute the video mute function according to the command of the source device, the video mute status information indicating that the sink device is not currently executing the video mute function may be transmitted to the source device.
  • This step (S8050) may be selectively applied according to the embodiment. Therefore, the sink device may or may not transmit current video mute state information to the source device according to an embodiment.
  • FIG. 9 is a flowchart illustrating a method of ending video mute function according to a first embodiment of the present invention.
  • steps S5010 to S5060 are the same as described above with reference to FIG. 5, and thus redundant descriptions are omitted.
  • the source device may turn off the video mute function of the sink device in operation S5110. More specifically, the source device may control the sink device to terminate the video mute function that the sink device is executing. To this end, the source device may transmit a command to the sink device to instruct the termination of the video mute function. The sink device may terminate the video mute function according to the received command.
  • the sink device may transmit the video mute state to the source device (S5120). More specifically, the sink device may transmit video mute state information of the current sink device as a response to the video mute function termination command received from the source device. Therefore, in the present embodiment, the sink device may transmit the video mute state information to the source device indicating that the video mute function is terminated (or notifying that the video mute function is not being executed).
  • This step S5120 may be selectively applied according to an embodiment. Therefore, the sink device may or may not transmit current video mute state information to the source device according to an embodiment.
  • command and status information may be defined and transmitted as a CEC message, and in this regard, it will be described later in detail with reference to FIGS. 15 to 17.
  • FIG. 10 is a flowchart illustrating a method of ending video mute function according to a first embodiment of the present invention.
  • the flowchart described above with reference to FIG. 9 may be applied in the same manner, and redundant descriptions thereof will be omitted.
  • the source device may transmit a video mute end command to the sink device (S10010). More specifically, the source device may transmit a video mute end command to the sink device to terminate the video mute function of the sink device.
  • the sink device may determine whether video muting is being performed (S10020). More specifically, the sink device may determine whether it is currently executing a video mute function as it receives a video mute end command from a source device.
  • the sink device may terminate the video mute function that is being executed (S10030).
  • the sink device may transmit the video mute state to the source device (S10040).
  • the sink device may transmit the video mute state information, which is information on whether the video mute function is currently executed, to the source device.
  • the sink device may transmit video mute state information indicating that the video mute function is not currently being executed (or the video mute function is terminated) to the source device.
  • the sink device may perform the above-described step S10040. That is, the sink device may transmit video mute state information indicating that the video mute function is not currently being executed to the source device.
  • the sink device may or may not transmit current video mute state information to the source device according to an embodiment.
  • FIG. 11 is a flowchart of a method of ending a video mute function according to a second embodiment of the present invention.
  • steps S5010 to S5060 are the same as described above with reference to FIG. 5, and thus redundant descriptions are omitted.
  • the source device may transmit a CEC command to the sink device (S5130).
  • the source device may transmit a CEC command to the sink device to control the sink device.
  • the transmitted CEC command may correspond to a command other than a command for controlling the video mute function of the sink device.
  • the CEC command is not directly related to the video mute function, but may correspond to various commands for controlling the sink device (channel change, volume control, etc.).
  • the sink device receiving the CEC command may determine whether to terminate the video mute function based on the received CEC command, and may maintain or terminate the execution of the video mute function.
  • the sink device may transmit the video mute state to the source device (S5140). More specifically, the sink device may transmit the video mute state information of the current sink device as a response to the CEC command received from the source device.
  • the sink device may transmit video mute state information indicating that the video mute function is being executed to the source device.
  • the sink device notifies that the video mute function is not running (or the video mute function is terminated). Information can be sent to the source device.
  • This step (S5140) may be selectively applied according to the embodiment. Therefore, the sink device may or may not transmit current video mute state information to the source device according to an embodiment.
  • CEC command and status information may be defined and transmitted as a CEC message, and this will be described later in detail with reference to FIGS. 15 to 17.
  • FIG. 12 is a flowchart of a method of ending a video mute function according to a second embodiment of the present invention.
  • the flowchart described above with reference to FIG. 11 may be applied in the same manner, and redundant descriptions thereof will be omitted.
  • a command may be transmitted from a source device to a sink device (S12010).
  • the command is not directly related to the control of the video mute function of the sink device, but may correspond to various CEC commands for controlling the sink device.
  • the sink device may determine whether it is necessary to terminate the video mute function as a result of the execution of the received command (S12020). For example, if it is necessary to output the video to execute the received command, the sink device may determine that the video mute function needs to be terminated. On the contrary, when the video output is not necessary to execute the received command, the sink device may determine that the video mute function does not need to be terminated.
  • the sink device may end the video mute function being executed (S12030).
  • the sink device may transmit the video mute state to the source device (S12040).
  • the sink device may transmit the video mute state information, which is information on whether the video mute function is currently executed, to the source device.
  • the sink device since the sink device has terminated the video mute function, the sink device may transmit video mute state information indicating that the video mute function is not being executed (or the video mute function is terminated) to the source device.
  • the sink device may maintain execution of the video mute function being executed. Furthermore, the sink device may transmit the video mute state to the source device (S12040). In this case, the sink device may transmit video mute state information indicating that the video mute function is currently executing (or not ending the video mute function) to the source device.
  • Step S12040 may be selectively applied according to an embodiment. Accordingly, the sink device may or may not transmit the current video mute state information to the source device according to an embodiment.
  • FIG. 13 is a flowchart of a method of ending a video mute function according to a third embodiment of the present invention.
  • steps S5010 to S5060 are the same as described above with reference to FIG. 5, and thus redundant descriptions are omitted.
  • the sink device may change its state (S5150). For example, when the sink device receives an external input (for example, various user inputs to the sink device such as a remote controller input to the sink device), the sink device may change state. If the state changes, the sink device may terminate the video mute function by itself. In particular, when it is determined that the sink device needs to output video according to an external input, the sink device may terminate the video muting function that is being executed.
  • an external input for example, various user inputs to the sink device such as a remote controller input to the sink device
  • the sink device may change state. If the state changes, the sink device may terminate the video mute function by itself. In particular, when it is determined that the sink device needs to output video according to an external input, the sink device may terminate the video muting function that is being executed.
  • the sink device may transmit a video mute state to the source device (S5160).
  • the sink device may transmit video mute state information to the source device indicating that the video mute function is not being executed (or the execution of the video mute function has ended).
  • This step S5160 may be selectively applied according to an embodiment. Therefore, the sink device may or may not transmit current video mute state information to the source device according to an embodiment.
  • the video mute state information described above may be defined and transmitted as a CEC message, and this will be described later in detail with reference to FIGS. 15 to 17.
  • FIG. 14 is a flowchart illustrating a method of ending a video mute function according to a third embodiment of the present invention.
  • the flowchart described above with reference to FIG. 13 may be applied in the same manner, and redundant description thereof will be omitted.
  • a state change may occur in the sink device (S14010).
  • the sink device may change state.
  • an external input for example, various user inputs to the sink device such as a remote controller input to the sink device
  • the sink device may change state.
  • the sink device may determine whether it is necessary to terminate the video mute function according to the state change (S14020). For example, the sink device may determine whether a video output is required when performing a specific command according to an external input.
  • the video mute function may be terminated (S14030).
  • the sink device may transmit the video mute state to the source device (S14040).
  • the sink device may transmit the video mute state information, which is information on whether the video mute function is currently executed, to the source device.
  • the sink device terminates the video mute function according to the state change, and thus, the sink device may transmit the video mute state information indicating that the video mute function is not currently executed (or the video mute function is finished). have.
  • the sink device may transmit the video mute state to the source device (S14040). In this case, the sink device may transmit the video mute state information indicating that the video mute function is currently executed to the source device.
  • Step S14040 may be selectively applied according to an embodiment. Accordingly, the sink device may or may not transmit the current video mute state information to the source device according to an embodiment.
  • FIG. 15 is a table listing command formats transmitted and received between a source device and a sink device according to an embodiment of the present invention.
  • the source device may transmit and receive various commands as described below to control the video mute function of the sink device.
  • Video Mute A command to mute the sink device's video from the source device (or a command sent from the source device to the sink device to perform the video mute function of the sink device).
  • Turn off Video Mute A command to end the video mute state of the sink device at the source device (or a command sent from the source device to the sink device to end the execution of the video mute function of the sink device).
  • Video Mute Status A command that informs the sink device of the current video mute status (a command sent from the sink device to the source device to indicate whether the sink device is currently executing the video mute function).
  • Request Video Mute Status Request the video mute current status (command sent from the source device to the sink device to request the video mute status information of the current sink device).
  • Response Video Mute Status Responds to the video mute current status (command sent from the sink device to the source device to respond to the video mute status information of the current sink device, and may be sent as a response to the Request Video Mute Status).
  • the Turn on Video Mute / Video Mute status command may be applied to the embodiment described above with reference to FIGS. 6 and 8.
  • the Request Video Mute Status / Response Video Mute Status command may be applied to the above-described embodiment with reference to FIG. 7.
  • the Turn off Video Mute / Response Video Mute Status command may be applied to the embodiment described above with reference to FIGS. 9 and 10.
  • the Video Mute Status command can be applied to the embodiment described above with reference to FIGS. 13 and 14.
  • the above-described instructions may be defined in a CEC message format and may be transmitted and received by the source device and the sink device, which will be described later in detail with reference to FIGS. 16 and 17.
  • FIG. 16 is a flowchart of a source device and a sink device for controlling a video mute function by transmitting and receiving a CEC message.
  • FIG. 16 is a flowchart summarizing the embodiments of FIGS. 6 to 12. Therefore, the above descriptions with respect to FIGS. 6 to 12 may be equally applied to the present flowchart, and redundant descriptions thereof will be omitted below.
  • the description of the CEC messages described below will be described in detail later with reference to FIG. 17.
  • a source device may transmit a CEC message ( ⁇ Video Mute On>) for executing a video mute function of a sink device (S16010).
  • the sink device that receives the corresponding CEC message ( ⁇ Video Mute On>) may execute the video mute function if it supports the video mute function.
  • the sink device may transmit a CEC message ( ⁇ Video Mute Status> [“On”]) indicating that the video mute function is currently executed to the source device (S16020).
  • the source device may transmit a CEC message ( ⁇ Request Video Mute Status>) requesting the current video mute status of the sink device to the source device (S16030).
  • the sink device may transmit a CEC message ( ⁇ Video Mute Status> [“On”]) indicating that the video mute function is currently executed to the source device (S16040).
  • the source device may transmit a CEC message ( ⁇ Video Mute Off>) for terminating the video mute function of the sink device (S16050).
  • the sink device receiving the corresponding CEC message ( ⁇ Video Mute Off>) may terminate the running video mute function.
  • the sink device may send a CEC message ( ⁇ Video Mute Status> [“Off”]) to the source device indicating that the video mute function is not currently executed (or the video mute function is finished). (S16060).
  • the source device may transmit a CEC command (or CEC message) excluding the video mute function control to the source device (S16070).
  • the CEC command is not directly related to the video mute function, but may correspond to a command for controlling a sink device (channel change, volume control, etc.).
  • the sink device receiving the CEC command may determine whether to terminate the video mute function based on the received CEC command, and may maintain or terminate the execution of the video mute function.
  • FIG. 17 illustrates a CEC message format according to an embodiment of the present invention.
  • FIG. 17 is an embodiment in which the above-described command and CEC messages are defined, and the CEC message defined in the present invention is defined as a description of a corresponding operation and is not necessarily defined in the same syntax.
  • An operator may indicate a command for sending a CEC instruction
  • an opcode may indicate a name for identifying a CEC message
  • an operand may indicate data values corresponding to a CEC instruction / message.
  • the operand may correspond to data corresponding to a specific opcode.
  • ⁇ Video Mute status> Send current video mute status, can be sent with operand [TV Mute Status]. Sent from a follower (or TV (sink device)).
  • ⁇ Request Video Mute Status> Requests the current video mute status, sent from initiator.
  • the above-described opcodes may be transmitted directly in a unicast manner.
  • the length can have 1 byte.
  • the video mute function control method of the sink device has been described above. According to the above description, the present invention has an effect that it is possible to control the video mute function of the sink device more easily and efficiently through the source device. In addition, the present invention can control the video mute function of the sink device through the source device, it is possible to reduce the power consumption caused by unnecessary video output of the sink device.
  • the video mute function described above may be implemented as various embodiments.
  • the control of the video mute function may be provided to the user through a user interface (UI) provided by the source device, or the user experience (UX), and the user may control the video mute function through the provided UI.
  • UI user interface
  • UX user experience
  • control of the video mute function may be provided to the user via a control device (or an external device) (eg, a remote controller) of the source device and / or the sink device, and the user may control the control device.
  • a control device or an external device
  • FIG. 18 is a flowchart illustrating a specific embodiment of executing a video mute function.
  • the source device and the sink device may perform steps S5010 to S5060 described above with reference to FIG. 5. Detailed description of the steps S5010 to S5060 are as described above with reference to FIG. 5.
  • the source device and / or the sink device may provide a UI (or an environment setting UI) for setting the video mute function (S18010).
  • the user can set the overall function for the video mute function through the provided UI.
  • the user can enable or disable the video mute function through the UI, how to execute the video mute function (either automatically when the video mute content is executed or by user input through a control device), or execute the video mute function.
  • General functions related to the video mute function can be set, such as the time, the execution cycle of the video mute function, and the execution check interval of the video mute function.
  • audio only content may refer to content composed of only audio data (or content in which audio data is main and video data is sub) without video data.
  • the source device may transmit audio data (and / or video data) related to the audio only content to the sink device, and the sink device may play audio data (and / or video data) received from the source device.
  • content including video data and audio data may be executed in addition to the audio only content.
  • the source device may transmit audio data and video data to the sink device, and the sink device may play audio data and video data received from the source device.
  • the source device and the sink device may perform steps S16010 to S16040. Details of the steps S16010 to S16040 are as described above with reference to FIG. 16.
  • the source device before transmitting the CEC message ( ⁇ Video Mute On>) for executing the video mute function of the sink device in step S16010, the source device provides the user with a UI related to the video mute function.
  • An execution input of the video mute function can be received.
  • the source device may provide a dialog (UI) for selecting whether to execute the video mute function, and the user may select to execute the video mute function through a control device (eg, a remote controller).
  • the source device may transmit a CEC message (eg, ⁇ Video Mute On>) for executing the video mute function to the sink device to execute the video mute function.
  • the source device and / or the sink device may perform various operations for maintaining execution of the video mute function.
  • the sink device may terminate the video mute function by itself according to the change of the status of the sink device (see FIGS. 13 and 14), which may result in the sudden termination of the video mute function differently from the user's intention.
  • a problem arises in that power consumption due to reproduction of unnecessary video data increases.
  • the sink device may terminate execution of the video mute function according to a state change while playing audio only content.
  • the video muting function of the sink device is terminated to generate unnecessary power consumption.
  • the user's intention is that if the user has set the power save mode (or the power save mode) or has always set the video mute function through the UI. There is a need to maintain the execution of the video mute function on the sink device regardless of the type of content in order to be consistent with this.
  • the source device and / or the sink device may perform various operations as follows to ensure the maintenance of the video mute function execution.
  • the sink device after the source device commands the sink device to execute the video mute function (or after receiving a CEC message of the video mute state from the sink device), the sink device periodically checks whether the video mute function is currently running. You can check To this end, the source device may periodically transmit a CEC message (eg, ⁇ Request Video Mute Status>) requesting the current video mute status information to the sink device, and the video mute of the sink device as a response to the request message. Status information may be periodically received (or updated).
  • a CEC message eg, ⁇ Request Video Mute Status>
  • the source device may send a CEC message (eg, For example, ⁇ Video Mute On>) may be transmitted to the sink device to ensure that the video mute function of the sink device is maintained.
  • a CEC message eg, For example, ⁇ Video Mute On>
  • the sink device when the sink device terminates the video mute function, the sink device transmits a CEC message (for example, ⁇ Video Mute Status> [“Off”]) notifying the source device to the source device without further request of the source device. Can be.
  • the source device receives the corresponding CEC message and transmits a CEC message (for example, ⁇ Video Mute On>) to the sink device to instruct the re-execution of the video mute function after a preset time interval. It is also possible to ensure that the video mute function of the execution is maintained.
  • the sink device may re-execute the video mute function directly without the command of the source device after the preset time interval after the video mute function ends.
  • the check period, the number of times, the time interval of the video mute function, and the like, in each embodiment may be set by the user or through the UI for setting the video mute function. If not, it may be set to a preset value by the manufacturer.
  • Actions to ensure the maintenance of the video mute function of such source and / or sink devices can be turned off (always) by the video mute function through the UI, or the user can turn off the power save mode (or sleep mode), or For example, this may not be performed when the user plays other content including video data.
  • 19 is a flowchart illustrating a specific embodiment of terminating a video mute function.
  • steps S16010 and S16020 may be performed to execute a video mute function in a sink device, and description of each step is the same as described above with reference to FIG. 16.
  • the sink device may terminate the video mute function according to the state change (S19010).
  • the change of the state of the sink device indicates a case where the sink device has changed to a state in which it is necessary to display a screen.
  • the status of the sink device may be changed when there is a situation in which a visual notification is provided to the user, such as a message received by the sink device or an alarm set.
  • a visual notification such as a message received by the sink device or an alarm set.
  • an external input any input by a user
  • the sink device may terminate the video mute function.
  • the sink device may inform the source device of the end of the video mute function through steps S16030 and S16060.
  • the source device and / or the sink device may perform various operations for continuing the execution of the video mute function. As described above in connection with.
  • 20 is a flowchart illustrating a specific embodiment of terminating a video mute function.
  • steps S16010 to S16060 may be performed to execute and terminate the video mute function in the sink device.
  • a description of each step is as described above with reference to FIG. 16.
  • the source device before transmitting the CEC message ( ⁇ Video Mute Off>) for terminating the video mute function of the sink device in step S16050, the source device provides the user with a UI related to the video mute function, A termination input of the video mute function can be received.
  • the source device may provide a dialog (UI) for selecting whether to terminate the video mute function, and the user may select to terminate the video mute function through a control device (eg, a remote controller).
  • the source device may terminate the video mute function by transmitting a CEC message ( ⁇ Video Mute Off>) to terminate the video mute function to the sink device.
  • the source device and / or the sink device may perform various operations for continuing execution of the video mute function. As described above in connection with.
  • 21 is a flowchart illustrating a specific embodiment of terminating a video mute function.
  • steps S16010 to S16060 may be performed to execute and terminate a video mute function in a sink device.
  • a description of each step is as described above with reference to FIG. 16.
  • the source device may receive a user input (or an external input) for executing the video mute function of the sink device before transmitting the CEC message ( ⁇ Video Mute On>) for executing the video mute function.
  • the user input here refers to various external inputs that command the execution of the video mute function.
  • a user input may be an input that presses a particular button (or hotkey) assigned to a control device (or external device) (e.g. a remote control) of a source device and / or a sink device to perform a video mute function. Can be represented.
  • the source device receiving the user input from the control device (or an external device) performs the step S16010 to allow the sink device to execute the video mute function.
  • the source device sends a user input (or an external input) for terminating the video mute function of the sink device before transmitting a CEC message ( ⁇ Video Mute Off>) for terminating the video mute function of the sink device.
  • the user input here refers to an input for instructing the end of the video mute function, for example, assigned to the control device (or external device) of the source device and / or the sink device (eg, the remote control) for the end of the video mute function. It can represent an input of pressing a particular button (or hotkey).
  • the source device receiving the user input from the control device (or an external device) performs step S16050 to allow the sink device to terminate the video mute function.
  • Buttons for executing or ending the video mute function may be independently present in one control device, but may be integrated into one button according to an embodiment. In this case, the user can easily toggle the execution of the video mute function via the integrated button.
  • the source device and / or the sink device may perform various operations for continuing execution of the video mute function. As described above in connection with.
  • 22 is a flowchart illustrating a specific operation embodiment of a source device and a sink device for maintaining execution of a video mute function.
  • steps S5010 to S5070 may be performed, and a description of each step is the same as described above with reference to FIG. 6.
  • the source device may periodically transmit a message requesting the video mute state information to the sink device to check whether the sink device is currently executing the video mute function (S22010).
  • the sink device may periodically transmit the current video mute state information to the source device in response to the request for the source device in the previous step (S22010) (S22020).
  • step S22010 may be selectively performed.
  • the sink device may periodically transmit its video mute state information to the source device without a separate request from the source device.
  • the sink device may terminate the video mute function (S22030).
  • the detailed description of the embodiment in which the sink device terminates the video mute function is as described above with reference to FIGS. 11 to 14 and 18.
  • the sink device may transmit the video mute state information indicating the end of the video mute function to the source device (S22040).
  • the source device may retransmit a message instructing execution of the video mute function (S22050).
  • the sink device having received the message may re-execute the video mute function (S22060).
  • the sink device may re-execute the video mute function without a command of a separate source device (receiving execution message of the video mute function) after a preset time after the video mute function ends.
  • the preset time may be set by the user directly through the UI for setting the video mute function described above or may be set to a preset value by the manufacturer even if the user does not set the time directly.
  • the drawings are divided and described, but the embodiments described in each drawing may be merged to implement a new embodiment.
  • the display device is not limited to the configuration and method of the embodiments described as described above, the above embodiments are configured by selectively combining all or some of the embodiments so that various modifications can be made May be
  • the present invention is used in the field of HDMI.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

Selon un mode de réalisation de la présente invention, un procédé par lequel un dispositif source transmet et reçoit des données au moyen d'une interface multimédia à haute définition (HDMI) peut comprendre les étapes consistant : à se connecter à un dispositif récepteur via l'HDMI ; à recevoir des informations de données d'identification d'affichage étendues (EDID) depuis le dispositif récepteur ; à analyser les informations EDID reçues et à déterminer un paramètre de fonctionnement ; à transmettre, au dispositif récepteur, un message pour indiquer l'exécution d'une fonction de sourdine de vidéo ; et à recevoir, du dispositif récepteur, à des cycles préétablis, des informations de mode sourdine de vidéo se rapportant au fait de savoir si la fonction de sourdine de vidéo est actuellement en cours d'exécution.
PCT/KR2016/000892 2015-01-28 2016-01-27 Procédé de transmission et de réception de données au moyen de hdmi et de dispositif s'y rapportant WO2016122213A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562108552P 2015-01-28 2015-01-28
US62/108,552 2015-01-28

Publications (1)

Publication Number Publication Date
WO2016122213A1 true WO2016122213A1 (fr) 2016-08-04

Family

ID=56543748

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/000892 WO2016122213A1 (fr) 2015-01-28 2016-01-27 Procédé de transmission et de réception de données au moyen de hdmi et de dispositif s'y rapportant

Country Status (1)

Country Link
WO (1) WO2016122213A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090024222A (ko) * 2006-03-29 2009-03-06 가부시끼가이샤 도시바 Ａｖ 장치 및 이의 제어 방법
KR20090066582A (ko) * 2007-12-20 2009-06-24 엘지전자 주식회사 에이치디엠아이 오디오 및 비디오 신호 분기방법
KR20090075231A (ko) * 2008-01-03 2009-07-08 주식회사 대우일렉트로닉스 텔레비전의 비디오 뮤트 처리장치 및 방법
US20110228715A1 (en) * 2008-12-01 2011-09-22 Keisuke Tsuji Wireless transmission system
JP2014222873A (ja) * 2006-11-07 2014-11-27 ソニー株式会社 受信装置および通信方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090024222A (ko) * 2006-03-29 2009-03-06 가부시끼가이샤 도시바 Ａｖ 장치 및 이의 제어 방법
JP2014222873A (ja) * 2006-11-07 2014-11-27 ソニー株式会社 受信装置および通信方法
KR20090066582A (ko) * 2007-12-20 2009-06-24 엘지전자 주식회사 에이치디엠아이 오디오 및 비디오 신호 분기방법
KR20090075231A (ko) * 2008-01-03 2009-07-08 주식회사 대우일렉트로닉스 텔레비전의 비디오 뮤트 처리장치 및 방법
US20110228715A1 (en) * 2008-12-01 2011-09-22 Keisuke Tsuji Wireless transmission system

Similar Documents

Publication Publication Date Title
WO2019103431A1 (fr) Appareil et procédé de commande de niveau d'émission de contenu multimédia
WO2017105021A1 (fr) Appareil d'affichage et procédé pour la commande d'appareil d'affichage
WO2014171682A1 (fr) Appareil d'affichage, et ses procede et appareil de reglage et de commande
WO2017048076A1 (fr) Appareil d'affichage et procédé de commande de l'affichage de l'appareil d'affichage
WO2014073823A1 (fr) Appareil d'affichage, appareil d'acquisition de voix et procédé de reconnaissance vocale correspondant
WO2014014302A1 (fr) Procédé et dispositif de partage de contenu
WO2016060474A1 (fr) Procédé et appareil permettant l'emission et la réception de données a l'aide de hdmi
WO2019078617A1 (fr) Appareil électronique et procédé de reconnaissance vocale
WO2020004765A1 (fr) Dispositif électronique, dispositif de télécommande et procédé de commande associé
WO2018028128A1 (fr) Procédé pour renvoyer des informations de données de liaison montante et appareil associé
WO2015190880A1 (fr) Procédé et appareil de transmission et de réception de données via une interface hdmi
WO2018190513A1 (fr) Dispositif d'affichage, système d'affichage et procédé de commande de dispositif d'affichage
WO2017065434A1 (fr) Dispositif de communication externe, dispositif d'affichage, système d'affichage et leur procédé de commande
WO2017069434A1 (fr) Appareil d'affichage et procédé de commande d'appareil d'affichage
WO2019125007A1 (fr) Appareil d'affichage et son procédé de fonctionnement
WO2019156532A1 (fr) Appareil d'affichage permettant la fourniture d'énergie à un appareil externe, procédé correspondant et support lisible par ordinateur
WO2020017882A1 (fr) Système comprenant plusieurs dispositifs d'affichage et procédé permettant de commander ledit système
WO2016089161A1 (fr) Procédé de commande de dispositif hdmi à base ip
WO2019194457A1 (fr) Appareil électronique, procédé de commande de celui-ci, et support d'enregistrement associé
WO2016060428A1 (fr) Procédé de transmission et de réception de données grâce à l'hdmi et dispositif pour cela
WO2020231067A1 (fr) Appareil électronique et son procédé de commande
WO2016122213A1 (fr) Procédé de transmission et de réception de données au moyen de hdmi et de dispositif s'y rapportant
WO2022245182A1 (fr) Procédé de transmission/réception de données vidéo et dispositif associé
WO2018186626A1 (fr) Système d'affichage multiple configurant un dispositif d'affichage et son procédé de commande
WO2022149659A1 (fr) Dispositif d'affichage et son procédé de commande

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16743691

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16743691

Country of ref document: EP

Kind code of ref document: A1