JP6514648B2 - Data transmission device, data reception device, and data transmission / reception system - Google Patents

Description

  The present invention relates to a data transmission / reception apparatus and method, and more particularly, to a data transmission apparatus, data reception apparatus, data transmission / reception system, data transmission method and data reception method for transmitting and receiving information related to screen separation support.

  Recently, high-speed wired interface standards for various data transmissions have been proposed while the multimedia environment is being overwhelmed. For example, HDMI (registered trademark) and MHL define transmission standards of video data, audio data, and control data of various formats. With the advent of multi-view technology in which different viewers can view different contents from one another through a single display device, the need for a multi-audio transmission protocol corresponding to multi-view video has been raised.

  In particular, when a plurality of users divide the screen and view different contents, the audio format matched with each of the separated screens is what format the screen is separated between the source device and the sink device The signals need to share information as to what they are.

  Therefore, the need for a standard capable of transmitting and receiving screen separation support information between the source device and the sink device is presented.

  An object of one or more embodiments of the present invention is to provide an interface standard capable of transmitting and receiving support information on screen separation between a source device and a sink device.

  In order to achieve the above object, a data transmitting apparatus according to an embodiment of the present invention includes a packet generation unit configured to generate an audio metadata packet, and data generated from the generated audio metadata packet. And a transmitter configured to transmit data to the receiver. In particular, a header of the generated audio metadata packet includes a split screen information field associated with audio data represented by the audio metadata packet.

  The screen separation information field is a split screen valid field representing presence / absence of screen separation support and a split screen type field representing a split screen type associated with audio data to be transmitted. It can include at least one.

  The separation screen type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, and a second display mode for displaying a picture in picture (PIP) screen in the display screen. One of three separation modes and a fourth separation mode for separating the display screen into three or more may be included.

The header of the generated audio metadata packet is
A view type field (View Type Field) indicating whether the content to be transmitted is multiview content or single view content, a sequence number field (Sequence Number Field) indicating the sequence number of the audio metadata packet, and audio to be transmitted At least one of an audio stream number field (Number Of Audio Stream Field) representing stream number information may be further included.

  The payload of the generated audio metadata packet may include a multi audio descriptor field representing metadata for a sub packet of a multi audio sample packet.

  The multi-audio descriptor field may be a split screen tag field representing split screen information corresponding to audio data represented by the generated audio metadata packet, and the generated audio metadata packet may represent the multi-audio descriptor field. Associated view identification field (Associated View ID Field) indicating a view corresponding to audio data, valid language code field (Valid Language Code Field) indicating whether the multi-audio descriptor field includes a valid language code, main audio data and the like Mixed audio field indicating presence or absence of premix with auxiliary audio data (mixed audio field And SAT Present Field, which indicates whether the multi-audio descriptor field contains information for valid auxiliary audio data types, auxiliary audio data for audio data represented by the generated audio metadata packet. At least one of a supplemental audio type field representing a type and a language code field representing a language code defined by ISO639 of audio data represented by the generated audio metadata packet Can be included.

  In order to achieve the above object, a data receiving apparatus according to another embodiment of the present invention includes a receiving unit for receiving an audio metadata packet from a data transmitting apparatus, and a parsing for parsing the received audio metadata packet. And a unit. The header of the audio metadata packet includes a split screen information field associated with audio data represented by the audio metadata packet.

  The receiver receives the audio metadata packet from the data transmitter. The screen separation information field is a split screen valid field representing presence / absence of screen separation support and a split screen type field representing a split screen type associated with audio data to be transmitted. It can include at least one.

  The separation screen type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and It may include any one of a fourth separation mode for separating the display screen into three or more.

  The header of the audio metadata packet is a view type field indicating whether the received content is multiview content or single view content, and a sequence number indicating the sequence number of the audio metadata packet At least one of a field (Sequence Number Field) and an audio stream number field (Number Of Audio Stream Field) indicating number information of received audio streams may be further included.

  The payload of the received audio metadata packet may include a multi audio descriptor field representing metadata for a sub packet of a multi audio sample packet.

  The multi-audio descriptor field is a split screen tag field representing split screen information corresponding to audio data represented by the audio metadata packet, and a view corresponding to audio data represented by the audio metadata packet Associated view identification field (Associated View ID Field), a valid language code field (ValidLanguage Code Field) indicating whether the multi-audio descriptor field contains a valid language code, a premix of the main audio data and the auxiliary audio data Mixed audio field indicating presence or absence, the multi audio A SAT Present Field, which indicates whether the Odescriptor field contains information for valid auxiliary audio data types, and an auxiliary audio type field, which indicates auxiliary audio data types for the audio data represented by the audio metadata packet. (Supplemental Audio Type Field), at least one of a language code field representing a language code defined by ISO639 of audio data represented by the audio metadata packet may be included.

  According to still another aspect of the present invention, there is provided a data transmitting and receiving system comprising: a device capability information block including feature information supported by a sink device for audio data; A data transmitting device configured to transmit to a receiving device and a data receiving device configured to receive the audio metadata packet from the data transmitting device. The header of the audio metadata packet includes a split screen information field associated with audio data represented by the audio metadata packet.

  In order to achieve the above object, a data transmission method according to another embodiment of the present invention comprises the steps of: generating an audio metadata packet; and transmitting the generated audio metadata packet to a data receiving apparatus including. At this time, a header of the generated audio metadata packet includes a split screen information field associated with the audio data represented by the audio metadata packet.

  The screen separation information field is a split screen valid field representing presence / absence of screen separation support and a split screen type field representing a split screen type associated with audio data to be transmitted. It can include at least one.

  The separation screen type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and It may include any one of a fourth separation mode for separating the display screen into three or more.

  The header of the generated audio metadata packet is a view type field (View Type Field) indicating whether the content to be transmitted is multiview content or single view content, and the sequence number of the audio metadata packet It may further include at least one of a Sequence Number Field to represent and an Audio Stream Number Field to represent information on the number of audio streams to be transmitted.

  The payload of the generated audio metadata packet may include a multi audio descriptor field representing metadata for a sub packet of a multi audio sample packet.

  The multi-audio descriptor field may be a split screen tag field representing split screen information corresponding to audio data represented by the generated audio metadata packet, and the generated audio metadata packet may represent the multi-audio descriptor field. Associated view identification field (Associated View ID Field) indicating a view corresponding to audio data, valid language code field (Valid Language Code Field) indicating whether the multi-audio descriptor field includes a valid language code, main audio data and the like Mixed audio field indicating presence or absence of premix with auxiliary audio data (mixed audio field And SAT Present Field, which indicates whether the multi-audio descriptor field contains information for valid auxiliary audio data types, auxiliary audio data for audio data represented by the generated audio metadata packet. At least one of a supplemental audio type field representing a type and a language code field representing a language code defined by ISO639 of audio data represented by the generated audio metadata packet Can be included.

  According to another aspect of the present invention, there is provided a data receiving method comprising the steps of: receiving an audio metadata packet from a data transmitting device; and parsing the received audio metadata packet. And a header of the received audio metadata packet includes a split screen information field associated with audio data represented by the audio metadata packet.

  The screen separation information field is a split screen valid field representing presence / absence of screen separation support and a split screen type field representing a split screen type associated with audio data to be transmitted. It can include at least one.

  The separation screen information field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and It may include any one of a fourth separation mode for separating the display screen into three or more.

  The header of the generated audio metadata packet is a view type field (View Type Field) indicating whether the content to be transmitted is multiview content or single view content, and the sequence number of the audio metadata packet It may further include at least one of a Sequence Number Field to represent and an Audio Stream Number Field to represent information on the number of audio streams to be transmitted.

  The payload of the generated audio metadata packet may include a multi audio descriptor field representing metadata for a sub packet of a multi audio sample packet.

  A multi audio descriptor (Multi Audio Descriptor) is a split screen tag field (Split Screen Tag Field) representing split screen information corresponding to audio data represented by the received audio metadata packet, the received audio metadata Associated View Identification Field (Associated View ID Field) that represents the view corresponding to the audio data that the packet represents, Valid Language Code Field (Valid Language Code Field) that indicates whether the multi-audio descriptor field contains a valid language code, Main Mixed audio field (presence or absence of pre-mix between audio data and auxiliary audio data) Mixed Audio Field), SAT Present Field, which indicates whether the multi-audio descriptor field contains information for valid auxiliary audio data types, ISO 639 of audio data represented by the generated audio metadata packet At least one language code field representing a defined language code may be included.

  In order to achieve the above object, according to another embodiment of the present invention, there is provided a data transmission apparatus comprising: a packet generation unit configured to generate a packet including a plurality of subpackets for a multi audio stream; And a transmitter for transmitting the received packet to the receiver. The header of the generated packet includes a sequence number field for identifying the order of the generated packet among a plurality of packets.

  In order to achieve the above object, a data receiving apparatus according to another embodiment of the present invention has a receiving unit configured to receive a packet including a plurality of subpackets for a multi audio stream, and the received packet. And a parsing unit for parsing. The header of the received packet includes a sequence number field for identifying the order of the generated packet among a plurality of packets.

  In order to achieve the above object, a data transmitting and receiving system according to another embodiment of the present invention generates a packet including a plurality of subpackets for a multi audio stream and transmits the packet to a data receiving device; And a data receiving device for receiving the packet including a plurality of subpackets from the data transmitting device. The header of the received packet includes a sequence number field for identifying the order of the generated packet among a plurality of packets.

  According to another aspect of the present invention, there is provided a data transmission method comprising: generating a packet including a plurality of subpackets for a multi audio stream; And transmitting, the header of the generated packet includes a Sequence Number Field for identifying the order of the generated packet among the entire packets.

  According to another aspect of the present invention, there is provided a data receiving method comprising: receiving a packet including a plurality of subpackets for a multi audio stream; and parsing the received packet. And the header of the received packet includes a Sequence Number Field for identifying the order of the generated packet among the entire packets.

  In order to achieve the above object, a data transmission method according to still another embodiment of the present invention generates a device capability information block including feature information supported by a sink device for audio data. A screen separation audio indicating steps of transmitting the device performance information block to a data receiving device, the device performance information block indicating whether the sink device supports multi-audio reception and processing associated with screen separation It contains a field (Split Screen Audio Field).

  In order to achieve the above object, a data receiving apparatus according to still another embodiment of the present invention receives a device capability information block including feature information supported by a sink device for audio data. A receiver configured as described above, and an analyzer that analyzes the received device performance information block. The device performance information block includes a split screen audio field indicating whether the sink device supports multi-audio reception and processing associated with the screen separation.

  In order to achieve the above object, a data transmitting and receiving system according to another embodiment of the present invention receives data of a device capability information block including feature information supported by a sink device for audio data. And a data receiving device for receiving the device performance information block from the data transmitting device. The device performance information block includes a screen separation audio field that indicates whether the sink device supports multi-audio reception and processing in association with the screen separation.

  In order to achieve the above object, a data transmission method according to still another embodiment of the present invention generates a device capability information block including feature information supported by a sink device for audio data. And transmitting the received device performance information block to a data receiving device, wherein the device performance information block represents whether the sink device supports multi-audio reception and processing associated with screen separation. Includes Split Screen Audio Field.

  To achieve the above object, a data receiving method according to another embodiment of the present invention receives a device capability information block including feature information supported by a sink device for audio data. A screen separation audio field comprising steps of analyzing the received device performance information block, the device performance information block indicating whether the sink device supports multi-audio reception and processing associated with screen separation. (Split Screen Audio Field) is included.

  In order to achieve the above object, a data receiving apparatus according to still another embodiment of the present invention receives a packet including a split screen information field associated with audio data corresponding to the packet. The receiver may include a parsing unit that parses the received packet.

  According to the embodiment of the present invention as described above, the present invention provides an interface standard capable of transmitting and receiving support information on screen separation between a source device and a sink device.

The foregoing and / or other features should be more apparent from the following description of the embodiments with reference to the accompanying drawings.
It is a figure which shows a single audio stream and a multi audio stream. It is a figure which shows a single audio stream and a multi audio stream. FIG. 7 illustrates the source device sending multi-audio for dual window and screen separation to the sink device. FIG. 7 illustrates the source device sending multi-audio for dual window and screen separation to the sink device. FIG. 7 illustrates the source device sending multi-audio for dual window and screen separation to the sink device. FIG. 5 is a diagram schematically illustrating data transmission and reception between a sink device and a source device for displaying screen separation support information according to an embodiment of the present invention. It is a figure which shows the condition where the payload of the multi audio sample packet concerning one embodiment of this invention is transmitted. FIG. 1 is a block diagram of a data transmission and reception system according to an embodiment of the present invention. It is a figure which shows the block diagram of the data transmitter concerning one embodiment of this invention. It is a figure which shows the block diagram of the data receiver concerning one embodiment of this invention. It is a block diagram of the data transmission / reception system concerning other embodiment of this invention. FIG. 5 illustrates a screen separation mode associated with an audio stream according to one embodiment of the present invention. FIG. 5 illustrates a screen separation mode associated with an audio stream according to one embodiment of the present invention. FIG. 5 illustrates a screen separation mode associated with an audio stream according to one embodiment of the present invention. It is a block diagram of the data transmission / reception system concerning other embodiment of this invention. It is a block diagram of the data transmission apparatus concerning other embodiment of this invention. FIG. 7 is a block diagram of a data receiving apparatus according to still another embodiment of the present invention. It is a figure which shows the transmission timing of a 3D audio signal. It is a figure which shows the transmission timing of a 3D audio signal. FIG. 10 is a block diagram of a data transmission and reception system according to still another embodiment of the present invention. It is a block diagram which shows the structure of the data transmission apparatus concerning the further another embodiment of this invention. It is a block diagram which shows the structure of the data receiver concerning further another embodiment of this invention. FIG. 5 illustrates a scenario of a multi-stream audio sample packet according to an embodiment of the present invention. FIG. 5 illustrates various data transmission formats when transmitting quad view video content according to one or more embodiments of the present invention in a 3D interlaced format. FIG. 5 illustrates various data transmission formats when transmitting quad view video content according to one or more embodiments of the present invention in a 3D interlaced format. FIG. 5 illustrates various data transmission formats when transmitting quad view video content according to one or more embodiments of the present invention in a 3D interlaced format. It is a flowchart of the data transmission method concerning one embodiment of this invention. It is a flowchart of the data reception method concerning one embodiment of this invention. It is a flowchart of the data transmission method concerning other embodiment of this invention. It is a flowchart of the data reception method concerning other embodiment of this invention. It is a flowchart of the data transmission method concerning further another embodiment of this invention. 7 is a flowchart of a data receiving method according to still another embodiment of the present invention.

  The method of operation and the components of the system are indicated by the basic symbols in the figures which show the relevant detailed description for the understanding of the present invention. In addition, apparent descriptions may be omitted for those skilled in the art to which the present invention belongs. As used herein, for example, the first, second, and such descriptive terms do not obscure any practical relationship or order between such elements, but distinguish one element from another. Can be used. In the following, when listing a list of elements, expressions such as "at least one" etc are understood to modify the entire list of elements and not the individual elements of the list.

  The present invention can be applied to various wired interface transmission standards such as High Definition Multimedia Interface (HDMI) and Mobile High-Definition Link (MHL) standards within the technical idea of the present invention. The scope of rights extends to a similar wired interface transmission standard.

  The present specification refers to the following documents.

ITU-R BS. 2159-4 (05/2012), Multichannel sound technology in home and broadcasting applications
SMPTE, SMPTE 2036-2: 2008, "UHDTV-Audio characteristics and audio channel mapping for program production", 2008
IEC, IEC 62574 ed 1.0, "Audio, video and multimedia systems-General channel assignment of multichannel audio", 7 April 2011

Table 1 briefly describes the terms used in the present specification.

  FIGS. 1A and 1B show a single audio stream and a multi audio stream.

  As shown in FIG. 1A, in a single audio stream, a plurality of audio data exist for at least one video data, and these audio data are transmitted in one single stream. In single stream, all stream data is packetized so as to share the same packet stream ID.

  As shown in FIG. 1B, the multi audio stream is a case where a large number of single AV streams are transmitted. In multi-audio streams, there are multiple single-AV stream sets in which only one packet stream ID is assigned to each single AV stream. Video data of multiple single AV streams are independent of each other.

  Each audio stream of the multi-audio stream transmits up to two audio channels and is associated with a single audio stream. For example, in single view mode, each audio may be connected to the default video stream, and in dual view mode audio may be connected to the left image and / or the right image. You can also send one or more auxiliary audio options, such as: That is, Split-screen tagging, Language indication, and Indication of audio for visual / hearing impaired.

  Split Screen refers to a viewing option in which different audio data are tagged and identified by the source device for two or more windows. Screen separation is used in PIP viewing method (picture-in-pucture viewing), quick preview viewing method (quick-preview), multi-screen game (multi-screen game), and the like. Here, the window means a distinguished display image displayed on an area of the screen of the sink device.

  Screen separation (or multi-window) can be a selective configuration used with multi-audio. The screen separation mode indicates a configuration in which the screen is separated by the sink device, and tags an audio stream and maps it to a specific window window.

  FIGS. 2A, 2B, and 2C illustrate that a source device according to one or more embodiments of the present invention sends multi-audio for dual window and screen separation to a sink device.

  FIG. 2A is an embodiment of transmitting audio data for each of multiple screens, and FIG. 2B is an embodiment of transmitting a plurality of audio data accompanying quick preview viewing and PIP (picture-in-picture) viewing. FIG. 2C shows an embodiment for transmitting a plurality of audio data associated with a multi-screen game. The user of the sink device can select and listen to the desired audio.

  FIG. 3 according to an embodiment of the present invention is a diagram schematically showing data transmission / reception between the sink device 320 and the source device 310 for displaying the screen separation support information.

  As shown in FIG. 3, the source device 310 sinks vendor-specific infoframes, multi-audio sample packets, and multi-audio metadata packets. Send to device 320.

  The multi audio sample packet includes a plurality of audio streams. The multi-audio metadata packet contains one or more settings for each audio stream. It is associated with the video stream and can carry auxiliary audio information. The vendor-specific info frame contains the multiview type of content to be transmitted. Specific embodiments will be described later.

  The sink device 320 sends the extended device capability register to the source device 310 to indicate multi-audio mode information supported by the sink device. Specific embodiments will be described later.

  On the other hand, Supplementary multi-audio assists in the transmission of auxiliary audio tracks (e.g., multiple languages, audio descriptions for visual impairment, or clean audio for hearing impairment). In this case, up to 16 audio streams can be transmitted simultaneously. A specific description of this will be described later.

Transition Minimized Differential Signal (TMDS) and Encoding Data Platform Packet

3D Audio Sample Packet 3D audio is defined as audio in which speakers can be arranged at predetermined positions in 3D space according to 3D audio standards (for example, 10.2 channels, 22.2 channels, 30.2 channels, etc.). The 3D audio sample packet is composed of one audio sample having 9 to 32 audio channels.

  The 3D audio stream includes up to 32 audio channels (or more), and is transmitted via continuous packets in a data sum (sum) period. Each packet contains up to 8 audio channels. The configuration of the subpacket is determined by the sequence number and the sample present bits (sample_present bits) in the header.

  Sequence number field (sequence_number): Indicates the order of the current packet. This field is necessary to correctly identify the packet order, since many 3D audio sample packets contain a single 3D audio sample.

Other header fields and subpacket structures are consistent with the audio sample packets represented in the MHL 2.0 specification.

Multi-Audio Sample Packets Multi-audio sample packets may include four audio samples, each audio sample being independently associated with an audio stream. When the MHL source device transmits four or more independent audio streams simultaneously, these continuous audio streams are transmitted by the following multi audio sample packet series. The sequence number (sequence_number) defined in the packet header identifies each multi-audio sample packet and indicates the current packet order within the packet order. The configuration of the subpacket is determined by the sequence number and sample present bits in the header. This is described in detail in Multi-Audio Data Packetization.

  For each subpacket (or audio stream), the descriptor field in the Multi-Audio Metadata Packet is a view mode (ie single-view or multi-view), and Describe selective information (eg, screen separation tagging, language code, audio for visual impairment, etc.). These will be described in detail later.

  The sequence number field (sequence_number) represents the sequence number of the current multi-audio sample packet when there are four or more audio streams to be transmitted from the source device to the sink device. If this field is set to 0, the packet may each include the first four audio streams in the corresponding subpacket. If this field is set to 1, the packet may include the second four audio stream sets in the corresponding subpacket. In a similar manner, when the field is set to 2 or 3, the packet contains the third or fourth set of four audio streams respectively. The audio stream processed by subpacket 0 whose sequence number is 0 is designated as a default audio stream.

  The stream present field (stream_presnt.spX) indicates whether subpacket X contains stream X audio samples.

  The stream flat field (stream_flat.spX) indicates whether subpacket X represents a "flatline" sample of stream X. The stream flat field is stream_present. It is valid only when spX is set.

The other header fields and subpacket structure match the audio sample packet represented in the MHL 2.0 specification.

  FIG. 4 is a view showing a state in which the payload of the multi audio sample packet is transmitted.

  As shown in FIG. 4, 16 audio streams can be carried when 4 multi-audio sample packets are transmitted. Since the sequence number consists of 2 bits, up to 16 audio streams can be carried.

  FIG. 5 is a block diagram of a data transmission / reception system 1000-1 according to an embodiment of the present invention.

  As shown in FIG. 5, a data transmission / reception system 1000-1 according to an embodiment of the present invention includes a data transmission device 100-1 and a data reception device 200-1.

  The data transmitting apparatus 100-1 generates a packet including a plurality of subpackets for the multi audio stream and transmits the packet to the data receiving apparatus 200-1.

  The header of the packet includes a sequence number field for identifying the sequence of the generated packet among the whole packets.

  FIG. 6 is a block diagram of a data transmission apparatus 100-1 according to an embodiment of the present invention.

  As shown in FIG. 6, the data transmission apparatus 100-1 according to the embodiment of the present invention includes a packet generation unit 110 and a transmission unit 120.

  The packet generator 110 generates a packet including a plurality of subpackets for the multi audio stream. As shown in the above embodiment, one packet can include four subpackets corresponding to four audio streams.

  At this time, the header of the generated packet includes a sequence number field (Sequence Number Field) for identifying the order of the generated packet among the entire packets. As in the embodiment of FIG. 4, the sequence number field indicates the order of packets to be transmitted.

  The transmitting unit 120 transmits the generated packet to the data receiving apparatus 200-1.

  FIG. 7 is a block diagram of a data receiving apparatus 200-1 according to an embodiment of the present invention.

  As shown in FIG. 7, the data receiving apparatus 200-1 according to the embodiment of the present invention includes a receiving unit 210 and a parsing unit 220.

  The receiving unit 210 is configured to receive a packet including a plurality of subpackets for the multi audio stream from the data transmitting apparatus 100-1.

  The parsing unit 220 parses the received packet. The header of the received packet includes a sequence number field for identifying the order of the generated packet among the entire packets. As in the embodiment of FIG. 4, the sequence number field indicates the order of packets to be transmitted.

3D Audio Metadata Packets Ancillary data describing active 3D audio data is transmitted using 3D audio metadata packets. If the MHL source device can send 3D audio sample packets, the source device always sends an accurate 3D audio metadata packet at least once per every 2 video fields.

The following table shows 3D audio metadata packets according to an embodiment of the present invention.

Multi-Audio Metadata Packets Ancillary data describing the active multi-audio stream is transmitted using multi-audio metadata packets. This packet is used to describe view types and ancillary audio choices for each audio stream transferred from the multi audio sample packet.

  If the MHL source device can send multi-audio sample packets, the MHL source device always sends correct multi-stream audio metadata packets at least once per every two video fields.

The following is a multi-audio metadata packet according to an embodiment of the present invention.

  The view type field (MA_View_Type) represents the associated view mode of a multi-audio stream such as single view or multi view.

  The Sequence Number field (Sequence_Number) represents the sequence number of the packet or the current multi-audio metadata packet. This field is used to identify up to four different multi-audio metadata packets. This field uniquely connects each multi-audio metadata packet to multi-audio sample packets having the same sequence number.

  The audio stream number field (Num_Audio_Streams) represents the total number of audio streams transmitted by the multi audio sample packet.

  The screen separation valid field (SC_Valid) is associated with screen separation tagging. For example, if the screen separation valid field is set to 1, the screen separation tagging is supported, and the screen separation configuration field (Split_Screen_Config) is refined with the following 7 bits. If the Screen Separation Valid field is set to 0, then screen separation tagging is not assisted or refined and the next 7 bits are left for other use.

  The screen separation type field (Split_Screen_Config) indicates the screen separation type associated with the audio stream currently represented by the descriptor. The selectable screen separation types are listed in Table 13 below. This field is valid only when SC_valid = 1.

The multi audio descriptor field (MA_Descriptor_X) indicates the characteristics of the audio stream transmitted by the subpacket X of the corresponding multi audio sample packet. Table 13 shows the detailed structure of the multi-audio descriptor.

  8A, 8B, and 8C are diagrams illustrating screen separation modes associated with an audio stream according to an embodiment of the present invention.

The following table shows the definition of a multi-audio descriptor according to an embodiment of the present invention.

  The Screen Split Tag field (Split_Screen_Tag) indicates a particular window (as defined by the split screen configuration) associated with the audio stream currently represented by the multi-audio descriptor. The detailed description of the screen separation tag field according to one embodiment of the present invention is shown in Table 15 below. This field is valid only when SC_valid = 1, or the MHL sink device ignores this field.

  The associated view identification field (Associated_View_ID) represents a particular view associated with the audio stream currently represented by the multi-audio descriptor. The meaning of this field depends on the value of the view type field (MA_View_Type). A detailed description of the associated view identification field according to one embodiment of the present invention is provided in Table 15 below.

  The valid language code field (LC_present) indicates whether the valid language code is included. For example, if this field is set to 1, then the current descriptor contains a valid language code field (Language_Code) in the next byte.

  The mixed audio field (Mixed_Audio) indicates whether the corresponding audio stream includes a pre-mixed stream of general audio and auxiliary audio. If this field is set to 1, the corresponding audio stream contains a pre-mixed stream of general audio and auxiliary audio as represented by the auxiliary audio type field (Suppl_Audio_Type).

  The SAT present field (SAT_present) indicates whether the current descriptor includes a valid auxiliary audio type field. For example, if this field is set to 1, then the current descriptor contains a valid auxiliary audio type field (Suppl_Audio_Type) in the next 4 bits.

  The SAT present field (SAT_present) indicates whether the current descriptor includes a valid auxiliary audio type field. For example, if this field is set to 1, then the current descriptor contains a valid auxiliary audio type field (Suppl_Audio_Type) in the next 4 bits.

  The auxiliary audio type field (Suppl_Audio_Type) indicates the type of auxiliary audio for the corresponding audio stream. A detailed description of the Auxiliary Audio Type field according to one embodiment of the present invention is provided in Table 16. This field is valid only when the SAT present field (SAT_present) = 1, or the sink device ignores this field.

The language code field (Language_Code) represents a language code defined by ISO639 of the corresponding audio stream. This field is valid only when the valid language code field (LC_present) is set to 1, or the sink device ignores this field.

  FIG. 9 is a block diagram of a data transmission / reception system 1000-2 according to an embodiment of the present invention.

  As shown in FIG. 9, a data transmission / reception system 1000-2 according to another embodiment of the present invention includes a data transmission device 100-2 and a data reception device 200-2.

  The data transmission device 100-2 generates an audio metadata packet and transmits it to the data reception device 200-2. Audio metadata packets are defined for the audio specification to be transmitted.

  The header of the audio metadata packet includes a split screen information field associated with audio data represented by the audio metadata packet.

  The configurations of the data transmission apparatus 100-2 and the data reception apparatus 200-2 according to the embodiment of the present invention will be described in detail below.

  FIG. 10 is a block diagram of a data transmission apparatus 100-2 according to another embodiment of the present invention.

  As shown in FIG. 10, a data transmission apparatus 100-2 according to another embodiment of the present invention includes a packet generation unit 110 and a transmission unit 120 (for example, a transmitter).

  The packet generator 110 generates an audio metadata packet. Audio metadata packets are defined for the audio specification to be transmitted.

  In particular, a header of the generated audio metadata packet includes a split screen information field associated with audio data represented by the audio metadata packet.

  The transmitting unit 120 transmits the generated audio metadata packet to the data receiving apparatus 200-2.

  At this time, the screen separation information field is a split screen valid field representing presence / absence of screen separation support and a split screen type field representing a split screen type associated with the audio data to be transmitted. Can include at least one.

  The separation screen type field includes a first separation mode for separating the display screen in the horizontal direction, a second separation mode for separating the display screen in the vertical direction, a third separation mode for displaying the PIP screen in the display screen, and The display screen may include any one of a fourth separation mode for separating the display screen into three or more.

  The header of the generated audio metadata packet is a view type field (View Type Field) indicating whether the content to be transmitted is multiview content or single view content, and the sequence number of the audio metadata packet It may further include at least one of a Sequence Number Field to represent and an Audio Stream Number Field to represent information on the number of audio streams to be transmitted.

  The payload of the generated audio metadata packet may include a multi audio descriptor field representing metadata for a sub packet of a multi audio sample packet.

  The multi-audio descriptor field may be a split screen tag field representing split screen information corresponding to audio data represented by the generated audio metadata packet, and the generated audio metadata packet may represent the multi-audio descriptor field. Associated view identification field (Associated View ID Field) indicating a view corresponding to audio data, valid language code field (Valid Language Code Field) indicating whether the multi-audio descriptor field includes a valid language code, main audio data and the like Mixed audio field indicating presence or absence of premix with auxiliary audio data (mixed audio field And SAT Present Field, which indicates whether the multi-audio descriptor field contains information for valid auxiliary audio data types, auxiliary audio data for audio data represented by the generated audio metadata packet. At least one of a supplemental audio type field representing a type, and a language code field representing a language code defined as ISO639 of audio data represented by the generated audio metadata packet Can be included.

  FIG. 11 is a block diagram of a data receiving apparatus 200-2 according to another embodiment of the present invention.

  As shown in FIG. 11, a data receiving apparatus 200-2 according to another embodiment of the present invention includes a receiving unit 210 and a parsing unit 220 (for example, a parser).

  The receiving unit 210 receives an audio metadata packet from the data transmitting apparatus 100-2. Audio metadata packets are defined for the received audio specs.

  In particular, a header of the audio metadata packet includes a split screen information field associated with audio data represented by the audio metadata packet.

  The receiving unit 210 receives the audio metadata packet from the data transmitting apparatus 100-2.

  At this time, the screen separation information field is a split screen valid field representing presence / absence of screen separation support and a split screen type field representing a split screen type associated with the audio data to be transmitted. Can include at least one.

  The separation screen type field includes a first separation mode for separating the display screen in the horizontal direction, a second separation mode for separating the display screen in the vertical direction, a third separation mode for displaying the PIP screen in the display screen, and The display screen may include any one of a fourth separation mode for separating the display screen into three or more.

  The header of the audio metadata packet is a view type field indicating whether the received content is multiview content or single view content, and a sequence number indicating the sequence number of the audio metadata packet At least one of a field (Sequence Number Field) and an audio stream number field (Number Of Audio Stream Field) indicating number information of received audio streams may be further included.

  The payload of the audio metadata packet may include a multi audio descriptor field representing metadata for a sub packet of a multi audio sample packet.

  The multi-audio descriptor field is a split screen tag field representing split screen information corresponding to audio data represented by the audio metadata packet, and a view corresponding to audio data represented by the audio metadata packet Associated view identification field (Associated View ID Field), a valid language code field (ValidLanguage Code Field) indicating whether the multi-audio descriptor field contains a valid language code, a premix of the main audio data and the auxiliary audio data Mixed audio field indicating presence or absence, the multi audio A SAT Present Field, which indicates whether the Odescriptor field contains information for valid auxiliary audio data types, and an auxiliary audio type field, which indicates auxiliary audio data types for the audio data represented by the audio metadata packet. (Supplemental Audio Type Field), at least one of a language code field representing a language code defined by ISO639 of audio data represented by the audio metadata packet may be included.

Active Multi-Audio Mode Indicator The source device can use Vendor-Specific Infoframe (VSIF) to represent the exact view mode sent to the sink device. VSIF is structured as shown in Table 17.

The MHL multiview field (MHL_MULTI_VIEW) indicates what multiview mode is sent. A detailed description of the MHL multiview field according to one embodiment of the present invention is shown in Table 18.

Video 3D video descriptor for 3D support

  Each supported 3D video mode according to an embodiment of the present invention is represented by one 3D video descriptor.

  MV_SUPP: If set to '1', the device supports using 3D video format for multiview video streaming.

Audio Channel / Speaker Assignment If the MHL sink device is capable of receiving 3D audio, the 3D channel speaker assignment descriptor described in Tables 38 to 40 is used to indicate the configuration of the attached speaker. An indication of the current speaker assignment for 3D audio sent from the source device is handled in the 3D CA field of the 3D audio metadata packet. For a detailed description of the 3D CA field, refer to Tables 27-29.

3D Audio Data Packetization
Each subpacket of the 3D audio sample packet may include zero or one IEC 60958 frame. If the source device needs to downmix the 3D audio stream, and the downmixed audio streams are also 3D audio streams, they are processed using 3D audio sample packets. If the sink device does not support the 3D audio feature, the source device can not transmit the 3D audio sample packet with the 3D audio metadata packet.

There are other subpacket layout numbers, depending on the number of channels. Tables 20-22 below illustrate the 3D audio packet layout when transmitting each of the 12, 24, or 32 channels, according to one or more embodiments of the present invention.

  There are four sample present bits (Sample_presentbit) in the 3D audio sample packet header, one for each subpacket. Each represents that one subpacket contains one 3D audio sample. In addition, if there is no useful audio data available at the source device during the time period represented by the sample, there are four sample flat (sample_flat.spX) bits set. This can occur during sample rate changes or temporary stream jamming.

  The following 3D audio sample packet can be used to process one 3D audio sample comprising between 9 and 32 channels of L-PCM audio (i.e. 5 to 16 IEC 609 58 frames).

  The first packet of 3D audio samples is tightly packed with eight audio channels and has a sequence number field set to zero. The sequence number is incremented by one for each additional packet within the same 3D audio sample. The last packet contains eight or less audio channel numbers depending on the total channel number of 3D audio samples.

There are only 5 valid sample present bits (sample_present) for 3D audio sample packets.

  10 and 11 are diagrams showing transmission timings of 3D audio signals.

  Figures 10 and 11 illustrate transmitting three 8-channel 2D audio signal samples in a horizontal blanking interval. For 24 channel 3D audio signals, one sample is transmitted during the same period.

Multi-Audio Data Packetization MHL allows MHL source devices to transmit audio streams simultaneously for single-AV streaming. Multiple audio streams are associated with one of single view or multi view video streaming (eg, dual view gaming with other audio per view). The auxiliary audio mode can represent screen separation tagging (i.e., other parts of the screen are tagged and associated with its own audio stream), language code, or audio for visually / heard persons. . Each audio stream is associated with one view mode and includes up to two audio channels.

  Each subpacket of the multi-stream audio sample packet may contain zero or one IEC 60958 or IEC 61937 "block" "frame" as defined in IEC 60958.

  When there are four or more audio streams to be transmitted, two or more consecutive multi-audio sample packets are used to transmit multiple audio streams. The order of each packet in the packet order is identified by the sequence number field. The MHL source device can transmit up to 16 independent audio streams simultaneously in a single AV stream.

  Tables 24 and 25 show multi-audio sample packets and multi-audio metadata packet layouts when the MHL source apparatus according to one or more embodiments of the present invention transmits four audio streams in single-view video streaming. An example of Multi-audio metadata packets describe the features (auxiliary information, language, etc.) of each audio stream.

  Tables 26 and 27 show examples of multi-audio sample packets and multi-audio metadata packet layouts when the MHL source device transmits eight audio streams in dual view video streaming. Multi-audio metadata packets describe the features of each audio stream (related views, side information, language, etc.).

Table 28 and Table 29 show the multi-audio sample packet and multi-audio metadata packet layout when the MHL source device transmits 6 audio streams with a screen separation tagging option that enables single-view video streaming. An example is shown.

Audio for HI: Audio Stream for Hearing Impairment Audio for VI: Audio Stream for Visual Impairment

Audio for HI: Audio Stream for Hearing Impairment Audio for VI: Audio Stream for Visual Impairment

Audio for HI: Audio Stream for Hearing Impairment Audio for VI: Audio Stream for Visual Impairment

3D Audio Metadata Packetization Each time an active 3D audio stream is sent, an accurate 3D audio metadata packet is sent at least once per two video fields.

  The modified exact 3D audio metadata packet is the first non-affected nonce when the new 3D audio stream starts or when there is a change in the 3D audio stream that can be represented by the 3D audio metadata packet and the audio info frame Sent before one video frame according to non-silent audio samples. Preferentially, this occurs just before the first affected audio sample is transmitted.

  3D audio metadata packet transmission can occur anytime within the data platform interval including horizontal vertical blanking intervals.

  When 3D audio is streamed, the MHL sink ignores the CC and CA fields in the audio info frame, and instead references 3D_CC and 3D_CA in 3D audio metadata packets.

Multi-Audio Metadata Packetization Each time an active multi-audio stream is transmitted, an accurate multi-audio metadata packet is transmitted at least once per two video fields.

  The correct modified multi-audio metadata packet is affected for the first time when a new multi-audio stream starts or when there is a change in the multi-audio stream that can be represented by the multi-audio metadata packet and the audio info frame Prior to one video frame according to the received non-silent audio samples. Preferentially, this occurs just before the first affected audio sample is transmitted.

  Multi-audio metadata packet transmission can occur anytime within the data platform interval including horizontal vertical blanking intervals.

太い文字は、１０．２チャネルと関連した指定スピーカーを表す。

太い文字は、２２．２チャネルと関連した指定スピーカーを表す。

太い文字は、３０．２チャネルと関連した指定スピーカーを表す

Use of WRITE_BURST for 3D / Multi-Audio Support The support for 3D audio mode according to one or more embodiments of the present invention uses a formatted series of WRITE_BURST movements as shown in Table 31 and Table 37. Show.

The bold letters represent the designated speakers associated with the 10.2 channel.

The bold letters represent designated speakers associated with the 22.2 channel.

Thick letters represent selected speakers associated with the 30.2 channel

Link control bus (Link Control Bus)
Device Register Change Interrupt

  The 3D_AUD_REQ is used by the MHL source device to request 3D audio assistance information from the MHL sink device.

Burst_ID Code

  3D_AD and 3D_CSAD are used by the MHL sink device in representing audio extension assistance. MHL spec 7. See XX.

Control and Configuration
Extended Device Capability Register
The sink device can provide extended device performance registers to the source device. In other words, the source device can read the extended device performance register of the sink device.

As shown in the following table, the address 0x85 of the device performance register extended by the MHL spec can be used to represent the multi-audio mode supported by the sink device.

Multi-Audio Mode
Each sink device can display in a multi audio mode (MULTI_AUD_MODE) registering a specific multi audio mode to support.

The multi audio mode register includes a Split Screen Audio Field that indicates whether the sink device supports multi audio reception and processing associated with the screen separation.

If the device is not capable of supporting multi-view video streaming, this field is set to 0. FIG. 14 is a block diagram of a data transmission / reception system 1000-3 according to another embodiment of the present invention. .

  As shown in FIG. 14, the data transmission / reception system 1000-3 according to the embodiment of the present invention includes a data transmission device 100-3 and a data reception device 200-3.

  The data transmission apparatus 100-3 transmits a device capability information block including feature information supported by the sink apparatus for audio data to the data reception apparatus 200-3.

  FIG. 15 is a block diagram showing the configuration of the data transmission apparatus 100-3 according to the embodiment of the present invention.

  As shown in FIG. 15, the data transmitting apparatus 100-3 according to the embodiment of the present invention includes a generating unit 130 and a transmitting unit 120.

  The generation unit 130 generates a device capability information block including feature information supported by the sink device for audio data.

  The device performance information block may include a split screen audio field that indicates whether the sink device supports multi-audio reception and processing associated with the screen separation.

  The transmission unit 120 transmits the device capability information block to the data reception device 200-3.

  FIG. 16 is a block diagram showing the configuration of a data receiving apparatus 200-3 according to still another embodiment of the present invention.

  As shown in FIG. 16, the data receiving apparatus 200-3 according to the embodiment of the present invention includes a receiving unit 210 and an analysis unit 230 (for example, an analyzer).

  The receiving unit 210 receives a device performance information block from the data transmitting apparatus 100-3.

  The analysis unit 230 analyzes the received device performance information block.

  The device capability information block includes feature information supported by the sink device for audio data. Specifically, the device performance information block may include a split screen audio field that indicates whether the sink device supports multi audio reception and processing associated with the screen separation.

Multi-Stream Audio Hereinafter, multi-stream audio according to various embodiments of the present invention will be described. The multi-stream audio transmission specification described below can be adopted in various wired / wireless transmission interfaces including HDMI and MHL.

  The source device according to an embodiment of the present invention can transmit four audio streams simultaneously. For multi-stream audio sample packets, all audio streams share one audio info frame (Infoframe).

  The wired interface according to various embodiments of the present invention supports single-view video streaming (eg, supports multiple languages, or adds audio for people with visual or hearing impairments, etc.) it can. This is possible by modifying an audio metadata packet (Audio Metadata Packet) or modifying an HDMI audio data block (HDMI Audio Data Block).

For example, as shown in Table 45 below, multi-stream audio can support multiple languages, and audio can be supported on two channels.

Scenarios FIG. 17 illustrates a scenario of multi-stream audio sample packets according to one embodiment of the present invention.

  For a multistream audio sample packet with four subpackets, the following scenario can exist. 1) If a single TV program is transmitted with an audio description (audio description) for single view, stream 0 contains normal audio signal and stream 1 is an audio description for the visually impaired It can contain a signal.

  2) When supporting two languages in the single view, two audio signal streams consisting of the supported languages and an audio description corresponding to each are transmitted together. For example, if English and Korean are supported, stream 0 is a Korean normal audio signal, stream 1 is a Korean audio description signal for the visually impaired, stream 2 is an English normal audio signal, stream 3 can each include an English audio description signal for the visually impaired.

  3) It is also possible to transmit one audio signal stream consisting of one language and two audio description signals for visually impaired persons supported by different languages in a single view. For example, stream 0 includes a Korean or English normal audio signal, stream 1 includes a Korean audio description signal for the visually impaired, and stream 2 includes an English audio description signal for the visually impaired. Can.

  4) The source device can also transmit an audio signal for multiview. If dual views are supported, the most basic form is to transmit the audio signal for each view in one transmit stream. In the dual view case, which includes independent first and second views, each view provides independent content.

  5) Two languages can be supported for each view. In this case, an audio signal stream consisting of the first language for the first view, an audio signal stream consisting of the second language for the first view, an audio signal stream consisting of the first language for the second view, a second language from the second language Audio signal streams can be transmitted respectively. For example, if English and Korean are supported, stream 0 is the Korean audio signal for the first view, stream 1 is the English audio signal for the first view, stream 2 is the Korean audio signal for the second view , Stream 3 can include the English audio signal for the second view.

  6) In the case of dual view, any one view can additionally transmit an audio description signal for the visually impaired. That is, an audio signal stream for the first view, a normal audio signal stream for the second view, and an audio description signal stream for the visually impaired for the second view may be respectively transmitted. For example, stream 0 may include an audio signal for a first view, stream 1 may include an audio signal for a second view, and stream 3 may include an audio description signal for a second view.

  7) One stream can also be used to transmit common audio signals. That is, a common audio signal stream for the first view and the second view, a first view-dedicated audio stream, and a second view-dedicated audio stream may be respectively transmitted. In this case, at the receiving end, the common audio stream and the dedicated audio stream are multiplexed (Muxing) and output. Such a scenario can be applied in the case of a game. For example, stream 0 is a common audio signal for the first and second views (e.g. background sound, navigation voice, etc.), stream 1 is a dedicated audio signal for the first view, stream 2 is dedicated for the second view It can contain an audio signal.

  Referring back to FIG. 5, the data transmission / reception system 1000-1 according to the embodiment of the present invention includes a data transmission device 100-1 and a data reception device 200-1.

  The data transmitting apparatus 100-1 transmits a packet including the first subpacket and the second subpacket to the data receiving apparatus 200-1.

  The data receiving apparatus 200-1 may receive packets including the first subpacket and the second subpacket from the data transmitting apparatus 100-1.

  At this time, the first subpacket and the second subpacket include different audio data with respect to the first content.

  Hereinafter, the configurations of the data transmission device 100-1 and the data reception device 200-1 according to one or more embodiments of the present invention will be described in more detail.

  Referring back to FIG. 6, the data transmitting apparatus 100-1 according to the embodiment of the present invention includes a packet generating unit 110 and a transmitting unit 120.

  The packet generator 110 may generate a packet including the first subpacket and the second subpacket. At this time, the first subpacket and the second subpacket include different audio data with respect to the first content.

  The transmitting unit 120 transmits the generated packet to the receiving device 200-1. At this time, the first subpacket may include audio data for non-disabled persons, and the second subpacket may include audio data for visually impaired persons.

  The first subpacket and the second subpacket may include audio data of other languages.

  The first subpacket may include audio data corresponding to an audio description for the second subpacket.

  The packet may further include a third subpacket including audio data for a second content different from the first content.

  At this time, the audio data included in the first subpacket may be exclusive audio data for the first content, and the audio data included in the third subpacket is the second content. The audio data included in the second subpacket may be audio data common to the first content and the second content.

  Also, the packet may further include a fourth subpacket including audio data for the second content, and the third subpacket and the fourth subpacket may include different audio data.

  Referring back to FIG. 7, the data receiving apparatus 200-1 according to the embodiment of the present invention includes a receiving unit 210 and a parsing unit 220.

  The receiver 210 may receive a packet including the first subpacket and the second subpacket from the data transmitting apparatus 100-1. At this time, the first subpacket and the second subpacket may include different audio data with respect to the first content.

  The parsing unit 220 is an element for parsing the received first subpacket and the received second subpacket.

  The first subpacket and the second subpacket may include audio data of different languages.

  Unlike what is described above, the first subpacket may include audio data corresponding to the audio description for the second subpacket.

  The packet may further include a third subpacket including audio data for a second content different from the first content.

  At this time, the audio data included in the first subpacket may be exclusive audio data for the first content, and the audio data included in the third subpacket is the second content of the second content. The audio data included in the second subpacket may be audio data common to the first and second contents.

  Also, the packet may include a fourth subpacket including audio data for the second content, and the third subpacket and the fourth subpacket may include different audio data.

Audio Metadata Packet The source device according to an embodiment of the present invention sends an audio metadata packet to the sink device to indicate the audio spec to be sent. At this time, the header of the audio metadata packet has the following structure.

  The respective fields are as follows.

  If the 3D audio field (3D_AUDIO) [1 bit]: 3D_AUDIO = 1, then the audio metadata packet (Audio Metadata Packet) has a 3D audio channel count (3D Audio Channel count: 3D_CC field; see table below) and channel / It includes a speaker assignment information (ACAST: Audio Channel Allocation Standard Type) field (see the table below). Such field is set to 1 when the source sends 3D audio packets.

  The view number field (NUM_VIEWS) [2 bits] represents the number of views. When NUM_VIEWS = 00, single view video streaming is supported. When NUM_VIEWS = 01, dual view video streaming is supported. This mode is only allowed when 3D_DualView = 1 in VSIF. The remaining NUM_VIEWS values are reserved for future use.

Audio stream number field (NUM_AUDIO_STR) [2 bits]: Indicates the number of audio streams -1. In the case of NUM_AUDIO_STR = 01, 10, or 11, the audio metadata packet (Audio Metadata Packet) includes up to four audio metadata descriptors (audio metadata descriptors), each corresponding to an audio stream.

The following table represents the payload of audio metadata packets for 3D audio. For 3D_Audio = 1, the metadata packet payload has the following structure:

  That is, the 3D_CC field represents 3D audio channel count information, and the ACAST field represents an audio channel assignment standard type (ACAST) provided by the source.

Table 49 shows audio channels according to 3D_CC values, and Table 52 shows audio channel assignment standard types according to ACAST field values.

The table below shows the payload of audio metadata packets for multi-stream audio. If 3D_Audio = 0, then the metadata packet payload has the following structure:

As shown in Table 51, the payloads of audio metadata packets each include a 5-byte audio metadata descriptor (Audio_Metadata_Descriptor). The audio metadata descriptor (4 fields, 5 bytes each) is an audio metadata for a subpacket X or a multistream one bit audio sample packet (Multi-stream One) in a multi-stream audio sample packet Audio metadata for subpacket X is expressed in Bit Audio Sample Packet). The structure of the audio metadata descriptor according to an embodiment of the present invention is described below.

  It will be as follows if each field is explained.

  When the emergency channel field (Emergency_Channel) [1 bit]: Emergency_Channel = 1, the corresponding audio stream transmits emergency alert audio data. The receiving device can notify that there is an emergency broadcast via a script or the like, and the user can output the emergency alert audio signal received via the audio selection.

  Multiview field (left side) (Multiview_Left) [1 bit]: When Multiview_Left = 1, the corresponding audio stream is mapped to the left stereo image in the 3D video format. If Multiview_Left = 0, this field is valid only when NUM_VIEWS = 01.

  Multiview field (right side) (Multiview_Right [1 bit]: Multiview_Right = 1 will map the corresponding audio stream to the stereo image on the right side in 3D video format. If Multiview_Right = 0, this field is It is valid only when NUM_VIEWS = 01.

  Language Code Valid Field (LC_Valid) [1 bit]: When LC_Valid = 1, the language code (Language_Code) is valid, and the language of the corresponding audio stream is correctly identified. Or, the language of the corresponding audio stream will not be specified.

  If the auxiliary audio valid field (Suppl_A_Valid) [1 bit]: Suppl_A_Valid = 1, the corresponding audio stream includes an auxiliary audio track (supplemental audio track) that appears by Suppl_A_Type.

  If Premix Auxiliary Audio Field (Suppl_A_Mixed [1 bit]: Suppl_A_Mixed = 1), the corresponding audio stream can include the main audio component and the pre-mixed supplemental audio track that appeared by Suppl_A_Type This bit is valid only if Suppl_A_Valid = 1.

  The Auxiliary Audio Type field (Suppl_A_Type) [3 bits] represents the auxiliary audio type defined in Table 55 below. This field is valid only if Suppl_A_Valid = 1. Table 53 shows the description of the Auxiliary Audio Type field values.

The language code (Language_Code) [3 Bytes] identifies the language of the corresponding audio stream. The language code is defined by ISO639. Also, three character codes are located, and the last character code matches the last byte of the audio metadata descriptor X (Audio_Metadata_Descriptor_X). This field is valid only when LC_Valid = 1.

  Referring back to FIG. 9, the data transmission / reception system 1000-2 according to another embodiment of the present invention includes a data transmission device 100-2 and a data reception device 200-2.

  The data transmitting apparatus 100-2 generates an audio metadata packet and transmits the audio metadata packet to the data receiving apparatus 200-2.

  The data receiving apparatus 200-2 receives an audio metadata packet from the data transmitting apparatus 100-2.

  At this time, the header of the audio metadata packet includes a 3D audio field that indicates whether the 3D audio sample packet has been transmitted.

  Hereinafter, the configurations of the data transmission device 100-2 and the data reception device 200-2, and the configuration of the audio metadata packet will be described in more detail.

  Referring back to FIG. 10, the data transmitting apparatus 100-2 according to another embodiment of the present invention includes a packet generating unit 110 and a transmitting unit 120.

  The packet generator 110 generates an audio metadata packet. The header of the generated audio metadata packet may include a 3D audio field indicating presence or absence of transmission of the 3D audio sample packet.

  The transmitting unit 120 transmits the generated audio metadata packet to the data receiving apparatus 200-2.

  In addition, the header of the generated audio metadata packet may further include an audio stream number field (Number Of Audio Stream Field) representing audio stream number information (number information).

  In addition, the header of the generated audio metadata packet may further include a number of views field indicating number information of different contents to be transmitted.

  The payload of the generated audio metadata packet may include an audio metadata descriptor field that represents metadata in terms of a multi-stream audio sample packet or a multi-stream one-bit audio sample packet.

  Also, the audio metadata descriptor field is an emergency channel field that indicates whether there is an emergency broadcast, and a multiview field that indicates whether audio data corresponding to the image of the left eye or the image of the right eye in multiview is included. A language code valid field indicating whether the language of the audio data is identified, an auxiliary language valid field indicating the presence or absence of auxiliary audio data, and a premix auxiliary audio field indicating the presence or absence of premixing of the main audio data and the auxiliary audio data. At least one of an auxiliary audio type field representing a type of auxiliary audio data, and a language code field representing a language code of audio data may be included.

  Referring back to FIG. 11, the data receiving apparatus 200-2 according to another embodiment of the present invention includes a receiving unit 210 and a parsing unit 220.

  The reception unit 210 is an element for receiving an audio metadata packet from the data transmission device 9100-2. The header of the audio metadata packet includes a 3D audio field that indicates whether a 3D audio sample packet has been sent.

  The parsing unit 220 is an element for parsing an audio metadata packet received.

  Also, the header of the audio metadata packet may further include an audio stream number field indicating number information of the audio stream to be received.

  The header of the audio metadata packet may further include a number of views field representing number information of other contents to be received.

  The payload of the audio metadata packet may include an audio metadata descriptor field representing metadata relating to a multistream audio packet or a subpacket of a multistream one-bit audio sample packet.

  At this time, the audio metadata descriptor field is an emergency channel field indicating presence / absence of an emergency broadcast, a multiview field indicating whether the multiview contains audio data corresponding to an image of the left eye or an image of the right eye, audio A language code valid field that indicates whether the language of the data is identified, an auxiliary language valid field that indicates the presence or absence of auxiliary audio data, a premix auxiliary audio field that indicates whether the main audio data and the auxiliary audio data are premixed At least one of an auxiliary audio type field representing an auxiliary audio data type, and a language code field representing a language code of audio data may be included.

Audio Data Blocks Table 54 below shows audio data blocks of Extended Display Identification Data (EDID) according to an embodiment of the present invention. The parts relating to the 3-4 bytes in Table 54 are redefined in Table 57 below.

Also, a new Short Audio Descriptor (SAD) for multi-stream audio is deleted, and instead a normal SAD defined by EDID is used. According to the added content, up to two channels can be transmitted.

The following table shows the block configuration to replace 3-4 bytes of the audio data block.

  The respective fields are as follows.

  When the emergency channel field (Supports_MS_Emergency [1 bit]: Supports_MS_Emergency = 1, the sink device assists in receiving and processing the emergency alert audio channel. When Supports_MS_Emergency = 0, the sink device has such a feature Do not support

  When the audio mix field (Supports_MS_Mix) [1 bit]: Supports_MS_Mix = 1, the sink device assists in combining the main audio and the supplementary audio. When Supports_MS_Mix = 0, the sink device does not support such synthesis but only supports playing the mixed audio.

  The Auxiliary Audio Support Field (Supports_MS_Supple) [1 bit]: Supports_MS_Supple = 1, the sink device supports multi-stream audio with an auxiliary audio track for the visually / impaired person. If Supports_MS_Supple = 0, it represents nothing or indicates that the sink device does not support an auxiliary audio track for the visually impaired / heard person.

  When the language support field (Supports_MS_Lang) [1 bit]: Supports_MS_Lang = 1, the sink device supports multi-stream audio having a large number of language audio streams. Supports_MS_Lang = 0 indicates that nothing is represented or the sink device does not support multiple language audio streams.

  When the multi-view audio support field (Supports_MS_MultiView) [1 bit]: Supports_MS_MultiView = 1, the sink device supports multi-stream audio for multi-view video streaming. Supports_MS_MultiView = 0 indicates that nothing is represented or the sink device does not support multi-stream audio for multi-view video streaming.

  Maximum Stream Count Field (Max_Stream_Count-1 [2 bits]: Indicates the number of maximum audio streams that the sink device can handle. The Max_Stream_Count-1 value is shown in the following table.

Audio Descriptor Number Field (NUM_HDMI_3D_AD) [3 bits]: Indicates the number of 3D audio scripters.

  Referring back to FIG. 12, the data transmitting and receiving system 1000-3 according to another embodiment of the present invention includes a data transmitting apparatus 100-3 and a data receiving apparatus 200-3.

  The data transmission apparatus 100-3 generates display identification information including specific information supported by the sink apparatus for audio data, and transmits the display identification information to the data reception apparatus 200-3.

  The data receiving apparatus 200-3 receives and analyzes display identification information from the data transmitting apparatus 100-3. At this time, the display identification information includes a main / auxiliary audio properties field representing feature information of the main audio and auxiliary audio supported by the sink device.

  Hereinafter, the data transmission apparatus 100-3 and the data reception apparatus 200-3 will be described in more detail.

  Referring back to FIG. 13, the data transmitting apparatus 100-3 according to another embodiment of the present invention includes a generating unit 130 and a transmitting unit 120.

  The generation unit 130 is an element for generating display identification information including feature information supported by the sink device for audio data.

  The transmitting unit 120 transmits the display identification information to the data receiving apparatus 200-3.

  At this time, the display identification information includes a main / auxiliary audio properties field representing feature information of the main audio and auxiliary audio supported by the sink device.

  At this time, the main / audio property field is an audio mix field indicating whether the sink device supports the configuration of the main audio and the auxiliary audio, an auxiliary audio support field indicating the auxiliary audio support presence or absence of the sink device, the sink A language support field indicating presence / absence of audio data support consisting of multiple languages of the device, a multiview audio support field indicating whether the sink device supports multistream audio data for multiview content, and handling by the sink device Of at least one of a maximum stream count field representing the number of the maximum audio streams and an audio descriptor number field representing the number of 3D audio descriptors One, including the.

  The display identification information may further include an emergency channel field indicating whether the sink device supports reception and processing of an emergency broadcast.

  As shown in FIG. 14, a data transmitting apparatus 100-3 according to another embodiment of the present invention includes a receiving unit 210 and an analyzing unit 230.

  The receiving unit 210 is an element for receiving display identification information including feature information supported by the sink device for audio data from the data transmission device 100-3.

  The analysis unit 230 analyzes the received display identification information.

  At this time, the display identification information includes main / auxiliary audio property fields representing feature information of the main audio and the auxiliary audio supported by the sink device.

  At this time, the main / audio property field is an audio mix field indicating whether the sink device supports the configuration of the main audio and the auxiliary audio, and the auxiliary audio assistance indicating whether the sink device supports the auxiliary audio. A field, a language support field (Language Support Field) indicating whether to support audio data of multiple languages of the sink device, indicating whether the sink device supports multistream audio data for multiview content Multi-view audio support field, maximum stream count field representing the number of maximum audio streams handled by the sink device, and 3D audio descriptor At least one of the audio descriptor number field representing the number is included.

  The display identification information may further include an emergency channel field indicating whether to support emergency broadcast reception and processing of the sink device.

  Meanwhile, the wired interface according to various embodiments of the present invention can support quad view content transmission. The 3D video format standard of the HDMI wired interface standard can be utilized for quad view transmission.

  18A-18C illustrate various data transmission formats when transmitting quad view video content in a 3D interlaced format according to one or more embodiments of the present invention.

In this case, vendor-specific infoframes and vendor-specific data blocks can be modified. Specifically, the field defining the conventional 3D dual view is extended to the reserve area.

  Hereinafter, data transmission methods and reception methods according to various embodiments of the present invention will be described.

  FIG. 19 is a flowchart of a data transmission method according to an embodiment of the present invention, and FIG. 20 is a flowchart of a data reception method according to an embodiment of the present invention.

  As shown in FIG. 19, in the data transmission method according to one embodiment of the present invention, the step of generating an audio metadata packet (operation S1710), and the transmission of the generated audio metadata packet to a data receiving apparatus And (step S1720). At this time, a header of the generated audio metadata packet includes a split screen information field associated with the audio data represented by the audio metadata packet.

  The screen separation information field may be a split screen valid field representing presence / absence of screen separation support and a split screen type field representing a split screen type associated with the audio data to be transmitted. At least one can be included.

  The separation screen type field may be a first separation mode for separating the display screen in the horizontal direction, a second separation mode for separating the display screen in the vertical direction, and a third separation mode for displaying the PIP screen in the display screen. And any one of a fourth separation mode for separating the display screen into three or more.

  The header of the generated audio metadata packet is a view type field (View Type Field) indicating whether the content to be transmitted is multiview content or single view content, and the sequence number of the audio metadata packet It may include at least one of a Sequence Number Field to represent and an Audio Stream Number field to represent information on the number of audio streams to be transmitted.

  The payload of the generated audio metadata packet may include a multi audio descriptor field representing metadata for a sub packet of a multi audio sample packet.

  The multi audio descriptor may be a split screen tag field (Split Screen Tag Field) representing separated screen information corresponding to audio data represented by the generated audio metadata packet, audio represented by the generated audio metadata packet. Associated view identification field (Associated View ID Field) representing a view corresponding to data, Valid Language Code field (Valid Language Code Field) indicating whether the multi-audio descriptor field contains a valid language code, main audio data and auxiliary Mixed Audio Field, which indicates presence or absence of pre-mixing with audio data, SAT present field (SAT Present Field) indicating whether the multi-audio descriptor field contains information for valid auxiliary audio data types, indicating auxiliary audio data types for audio data represented by the generated audio metadata packet At least one of a supplemental audio type field and a language code field representing a language code defined by ISO639 of audio data represented by the generated audio metadata packet is included. Can.

  As shown in FIG. 20, the data receiving method according to an embodiment of the present invention receives the audio metadata packet from the data transmitting apparatus (operation S1810), and parses the received audio metadata packet. Step (operation S1820) is included. At this time, a header of the received audio metadata packet includes a split screen information field associated with audio data represented by the audio metadata packet.

  The screen separation information field may be a split screen valid field representing presence / absence of screen separation support and a split screen type field representing a split screen type associated with the audio data to be transmitted. At least one can be included.

  The separation screen type field includes a first separation mode for separating the display screen in the horizontal direction, a second separation mode for separating the display screen in the vertical direction, a third separation mode for displaying the PIP screen in the display screen, and The display screen may be displayed in any one of a fourth separation mode for separating into three or more.

  The header of the generated audio metadata packet is a view type field (View Type Field) indicating whether the content to be transmitted is multiview content or single view content, and the sequence number of the audio metadata packet It may further include at least one of a Sequence Number Field to represent and an Audio Stream Number Field to represent information on the number of audio streams to be transmitted.

  The payload of the generated audio metadata packet may include a multi audio descriptor field representing metadata for a sub packet of a multi audio sample packet.

  FIG. 21 is a flowchart of a data transmission method according to another embodiment of the present invention, and FIG. 22 is a flowchart of a data reception method according to another embodiment of the present invention.

  As shown in FIG. 21, according to another embodiment of the present invention, there is provided a data transmission method comprising the steps of: generating a packet including a plurality of subpackets for a multi audio stream (operation S1910); Transmitting to the receiving device (operation S 1920). At this time, the header of the generated packet includes a sequence number field (Sequence Number Field) for identifying the order of the generated packet among the entire packets.

  As shown in FIG. 22, according to another embodiment of the present invention, there is provided a data receiving method comprising the steps of: receiving a packet including a plurality of subpackets for a multi audio stream (operation S2010); And (performing operation S2020). At this time, the header of the received packet includes a sequence number field for identifying the order of the generated packet among the entire packets.

  FIG. 23 is a flowchart of a data transmission method according to still another embodiment of the present invention, and FIG. 24 is a flowchart of a data reception method according to still another embodiment of the present invention.

  As shown in FIG. 23, the data transmission method according to still another embodiment of the present invention generates a device capability information block including feature information supported by the sink device for audio data. (Operation S2110) and transmitting the device performance information block to the data receiving apparatus (Operation S2120). At this time, the device performance information block includes a split screen audio field that indicates whether the sink device supports multi-audio reception and processing associated with the screen separation.

  As shown in FIG. 24, a method of receiving data according to still another embodiment of the present invention includes the steps of receiving a device capability information block including feature information supported by a sink device for audio data. (Operation S2210) and analyzing the received device performance information block (Operation S2220). At this time, the device performance information block includes a split screen audio field that indicates whether the sink device supports multi-audio reception and processing associated with the screen separation.

  Although not limited thereto, an embodiment of the present invention can be embodied as computer readable code on a computer readable recording medium. A computer readable recording medium is any data storage device that can subsequently be read by a computer system. Examples of computer readable media include read only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage. The computer readable recording medium can also be distributed over network connected computer systems so that the computer readable code is stored and executed in a distributed manner. Also, one embodiment of the present invention may be written as a computer program transmitted over a computer readable transmission medium such as a carrier wave, and may be written for general or special purpose to execute the program. The digital computer can be recorded and embodied. Additionally, in embodiments of the present invention, one or more units or elements of the devices and systems described above may include circuitry, processors, microprocessors, etc. it can. For example, a computer program may include one or more algorithms corresponding to the methods described above.

  However, the embodiments and advantages described above are merely examples, and the concept of the present invention is not limited to the specific embodiments described above. The present teachings can be readily applied to other types of devices. Also, the description of the embodiments to the concept of the present invention is for illustration and not limiting on the scope of the claims, and many alternatives, modifications and variations are common to the technical field to which the present invention belongs. It should be clear to those who have knowledge.

Claims (12)

A data transmission device,
A packet generator for generating audio metadata packets;
A transmitter configured to transmit the generated audio metadata packet to a data receiver;
The generated audio metadata packet includes a split screen information field associated with audio data represented by the audio metadata packet,
The screen separation information field is
See contains at least one of the screen separation effective field indicating the presence or absence of a support screen separation (Split Screen Valid Field) and the screen separation type field indicating a separation screen type associated with the audio data transmitted (Split Screen Configuration Field),
The screen separation type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and A data transmission apparatus comprising any one of a fourth separation mode for separating the display screen into three or more . The header of the generated audio metadata packet is
A view type field (View Type Field) indicating whether the content to be transmitted is multiview content or single view content, a sequence number field (Sequence Number Field) indicating the sequence number of the audio metadata packet, and audio to be transmitted The data transmitting apparatus according to claim 1, further comprising at least one of an audio stream number field (Number Of Audio Stream Field) indicating stream number information. The payload of the generated audio metadata packet is
The data transmitting apparatus according to claim 1, further comprising a multi audio descriptor field representing metadata for sub-packets of a multi audio sample packet. The multi audio descriptor field is
A split screen tag field (Split Screen Tag Field) representing split screen information corresponding to audio data represented by the generated audio metadata packet, and a view corresponding to audio data represented by the generated audio metadata packet Associated View Identification Field (Associated View ID Field), Valid Language Code Field (Multiple Descriptor Field) Indicates Whether the Multi Audio Descriptor Field Contains Valid Language Code (Valid Language Code Field), Premix of Main Audio Data and Auxiliary Audio Data Mixed Audio Field indicating presence or absence, the multi-audio descriptor field is valid SAT Present Field, which indicates whether the information for auxiliary audio data type is included or not, Supplemental Audio Type field, which indicates auxiliary audio data type for audio data represented by the generated audio metadata packet (Supplemental Audio) 4. The method according to claim 3 , further comprising at least one of: Type Field) and a language code field representing a language code defined by ISO639 of audio data represented by the generated audio metadata packet. The data transmission device according to. A data receiving device,
A receiver for receiving audio metadata packets from the data transmitter;
And a parsing unit that parses the received audio metadata packet.
The received audio metadata packet includes a Split Screen Information Field associated with audio data represented by the received audio metadata packet,
The screen separation information field is
See contains at least one of the screen separation effective field indicating the presence or absence of a support screen separation (Split Screen Valid Field) and the screen separation type field indicating a separation screen type associated with the audio data transmitted (Split Screen Configuration Field),
The screen separation type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and A data receiving apparatus comprising any one of a fourth separation mode for separating the display screen into three or more . A data transmission / reception system,
A data transmitting device that generates audio metadata packets and transmits them to the data receiving device;
The data receiving device for receiving the audio metadata packet from the data transmitting device;
The audio metadata packet includes a split screen information field associated with audio data represented by the audio metadata packet,
The screen separation information field is
See contains at least one of the screen separation effective field indicating the presence or absence of a support screen separation (Split Screen Valid Field) and the screen separation type field indicating a separation screen type associated with the audio data transmitted (Split Screen Configuration Field),
The screen separation type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and A data transmitting / receiving system comprising any one of a fourth separation mode for separating the display screen into three or more . A data transmission device,
A packet generator for generating a packet including a plurality of subpackets for the multi audio stream;
And a transmitter configured to transmit the generated packet to the data receiver.
The generated packet includes a sequence number field (Sequence Number Field) for identifying the order of the generated packet among the entire packets,
The screen separation information field included in the generated packet is
See contains at least one of the screen separation effective field indicating the presence or absence of a support screen separation (Split Screen Valid Field) and the screen separation type field indicating a separation screen type associated with the audio data transmitted (Split Screen Configuration Field),
The screen separation type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and A data transmission apparatus comprising any one of a fourth separation mode for separating the display screen into three or more . A data receiving device,
A receiver for receiving a packet including a plurality of subpackets for the multi audio stream;
And a parsing unit that parses the received packet,
The received packet includes a sequence number field for identifying the order of the received packet among the entire packets,
The screen separation information field included in the received packet is
See contains at least one of the screen separation effective field indicating the presence or absence of a support screen separation (Split Screen Valid Field) and the screen separation type field indicating a separation screen type associated with the audio data transmitted (Split Screen Configuration Field),
The screen separation type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and A data receiving apparatus comprising any one of a fourth separation mode for separating the display screen into three or more . A data transmission / reception system,
A data transmitting apparatus that generates a plurality of subpackets for the multi audio stream and transmits the plurality of subpackets to the data receiving apparatus;
The data receiving apparatus for receiving the plurality of subpackets from the data transmitting apparatus;
The received packet includes a sequence number field for identifying the order of the received packet among the entire packets,
The screen separation information field included in the received packet is
See contains at least one of the screen separation effective field indicating the presence or absence of a support screen separation (Split Screen Valid Field) and the screen separation type field indicating a separation screen type associated with the audio data transmitted (Split Screen Configuration Field),
The screen separation type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and A data transmitting / receiving system comprising any one of a fourth separation mode for separating the display screen into three or more . A data transmission device,
A generator configured to generate a device capability information block including feature information supported by the sink device for audio data;
A transmitter configured to transmit the device performance information block to a data receiver;
The device performance information block includes a split screen audio field indicating whether the sink device supports multi-audio reception and processing associated with the screen separation,
The screen separation information field included in the device performance information block is
See contains at least one of the screen separation effective field indicating the presence or absence of a support screen separation (Split Screen Valid Field) and the screen separation type field indicating a separation screen type associated with the audio data transmitted (Split Screen Configuration Field),
The screen separation type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and A data transmission apparatus comprising any one of a fourth separation mode for separating the display screen into three or more . A data receiving device,
A receiving unit for receiving a Device Capability Information Block including feature information supported by the sink device for audio data;
An analysis unit that analyzes the received device performance information block;
The received device performance information block includes a split screen audio field indicating whether the sink device supports multi-audio reception and processing associated with the screen separation,
The screen separation information field included in the device performance information block is
See contains at least one of the screen separation effective field indicating the presence or absence of a support screen separation (Split Screen Valid Field) and the screen separation type field indicating a separation screen type associated with the audio data transmitted (Split Screen Configuration Field),
The screen separation type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and A data receiving apparatus comprising any one of a fourth separation mode for separating the display screen into three or more . A data transmission / reception system,
A data transmitting apparatus for transmitting a device capability information block including feature information supported by the sink apparatus for audio data to the data receiving apparatus;
A data receiving device for receiving the device performance information block transmitted from the data transmitting device;
The device performance information block includes a split screen audio field indicating whether the sink device supports multi-audio reception and processing associated with the screen separation.
The screen separation information field included in the device performance information block is
See contains at least one of the screen separation effective field indicating the presence or absence of a support screen separation (Split Screen Valid Field) and the screen separation type field indicating a separation screen type associated with the audio data transmitted (Split Screen Configuration Field),
The screen separation type field includes a first separation mode for separating a display screen in a horizontal direction, a second separation mode for separating the display screen in a vertical direction, a third separation mode for displaying a PIP screen in the display screen, and A data transmitting / receiving system comprising any one of a fourth separation mode for separating the display screen into three or more .

Images