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

Abstract

An object of the present invention is to provide an interface standard capable of transmitting and receiving a plurality of audio data related to the same content between a source device and a sink device. A data transmission device according to an embodiment of the present invention includes a packet generation unit that generates a packet including a first subpacket and a second subpacket, and a transmission unit that transmits the generated packet to a data reception device. The first subpacket and the second subpacket include different audio data for the first content.

Description

  The present invention relates to a data transmission / reception method and apparatus, and more particularly to a data transmission apparatus, a data reception apparatus, a data transmission / reception system, a data transmission method, and a data reception method for transmitting / receiving a plurality of audio data related to the same content.

  Recently, high-speed wired interface standards for various data transmissions have been proposed while the multimedia environment is being destroyed. For example, HDMI (registered trademark) and MHL define transmission standards for video data, audio signals, and control signals in various formats.

  However, conventional audio signal transmission standards cannot present interface standards such as transmitting audio data for visually impaired persons or audio data composed of multiple languages for content.

  Therefore, there is a need for an interface standard capable of transmitting and receiving a plurality of audio data related to the same content between the source device and the sink device.

US2014 / 0118616

  The present invention has been devised by the above-described need, and an object of the present invention is to provide an interface standard capable of transmitting and receiving a plurality of audio data related to the same content between a source device and a sink device. There is.

  In order to achieve the above object, a data transmitting apparatus according to an embodiment of the present invention includes a packet generation unit that generates a packet including a first subpacket and a second subpacket, and the generated packet as data. A transmission unit configured to transmit to the reception device, wherein the first subpacket and the second subpacket include different audio data for the first content.

  At this time, the first subpacket may include audio data for a non-disabled person, and the second subpacket may include audio data for a visually impaired person.

  The first subpacket and the second subpacket may include audio data in different 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 the second content different from the first content.

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

  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.

  In order to achieve the above object, a data receiving apparatus according to an embodiment of the present invention includes a receiving unit that receives a packet including a first subpacket and a second subpacket from the data transmitting apparatus; A parsing unit for parsing the first subpacket and the second subpacket, wherein the first subpacket and the second subpacket include different audio data for the first content.

  The first subpacket may include audio data for a non-disabled person, and the second subpacket may include audio data for a visually impaired person.

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

  In this case, 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 the second content different from the first content.

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

  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.

  In order to achieve the above object, a data transmission / reception system according to an embodiment of the present invention includes a data transmission device that generates a packet including a first subpacket and a second subpacket and transmits the packet to a data reception device; A data receiving device for receiving the packet from the data transmitting device, wherein the first subpacket and the second subpacket include different audio data for the first content.

In order to achieve the above object, a data transmission device according to another embodiment of the present invention includes a packet generation unit that generates an audio metadata packet;
A transmission unit that transmits the generated audio metadata packet to a data reception device, and a header of the generated audio metadata packet includes a 3D audio field (3D) indicating whether or not a 3D audio sample packet is transmitted. Audio Field).

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

  In addition, the header of the generated audio metadata packet may further include a view number field (Number Of Views Field) indicating the number information of different contents to be transmitted.

  Also, the payload of the generated audio metadata packet is a sub-stream of a multi-stream audio sample packet (Multi-stream Audio Sample Packet) or a multi-stream one-bit audio sample packet (Multi-stream One Bit Audio Sample Packet). An audio metadata descriptor field representing metadata for the packet can be included.

  The audio metadata descriptor field includes an emergency channel field indicating whether there is an emergency situation broadcast, and a multi-view indicating whether audio data corresponding to a left-eye or right-eye image is included in the multi-view. A field (Multiview Field), a language code valid field (Language Code Valid Field) indicating whether or not language is identified for audio data, an auxiliary audio valid field (Supplemental Audio Valid Field) indicating the presence or absence of auxiliary audio data, main audio data and the auxiliary audio Premix auxiliary audio field (pre-) indicating presence / absence of premix with data It includes at least one of an “Implemented Supplemental Audio Field”, an auxiliary audio type field indicating the type of the auxiliary audio data (Supplemental Audio Type Field), and a language code field indicating the language code for the audio data (Language Code Field). Can do.

  In order to achieve the above object, a data receiving apparatus according to another embodiment of the present invention includes a receiving unit that receives an audio metadata packet from a data transmitting apparatus, and parses the received audio metadata packet. And a header of the received audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted.

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

  In addition, the header of the audio metadata packet may further include a view number field (Number Of Views Field) indicating the number information of different received contents.

  In addition, the payload of the audio metadata packet is a meta for a sub-packet of a multi-stream audio sample packet (Multi-stream Audio Sample Packet) or a multi-stream one-bit audio sample packet (Multi-stream One Bit Audio Sample Packet). An audio metadata descriptor field representing the data can be included.

  The audio metadata descriptor field includes an emergency channel field indicating whether there is an emergency situation broadcast, and a multi-view indicating whether audio data corresponding to a left-eye or right-eye image is included in the multi-view. A field (Multiview Field), a language code valid field (Language Code Valid Field) indicating whether or not language is identified for audio data, an auxiliary audio valid field (Supplemental Audio Valid Field) indicating the presence or absence of auxiliary audio data, main audio data and the auxiliary audio Premix auxiliary audio field (pre-) indicating presence / absence of premix with data It includes at least one of an “Implemented Supplemental Audio Field”, an auxiliary audio type field indicating the type of the auxiliary audio data (Supplemental Audio Type Field), and a language code field indicating the language code for the audio data (Language Code Field). Can do.

  In order to achieve the above object, a data transmission / reception system according to another embodiment of the present invention includes a data transmission device that generates an audio metadata packet and transmits the packet to a data reception device; And a data receiving device that receives an audio metadata packet, and a header of the audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted.

  In order to achieve the above object, a data transmission device according to still another embodiment of the present invention includes a generation unit that generates display identification information including feature information supported by a sink device for audio data, and data A transmission unit that transmits the display identification information to a receiving device, and the display identification information includes a main / auxiliary audio characteristic field that represents information on characteristics of main audio and auxiliary audio supported by the sink device.

  The main / auxiliary audio characteristic field includes an audio mix field (Audio Mix Field) indicating whether the sink device supports synthesis of main audio and auxiliary audio, and whether the sink device supports auxiliary audio. An auxiliary audio support field (Language Audio Support Field) indicating whether or not the sink device supports audio data in a plurality of languages, and the sink device is used for multi-view content. Multi-view audio support field indicating whether to support multi-stream audio data (Multiview Audio Support) Field), a maximum stream count field (Maximum Stream Count Field) indicating the number of maximum audio streams that can be handled by the sink device, and an audio descriptor number field (Number Of Audio Descriptor Field) indicating the number of 3D audio descriptors. One can be included.

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

  In order to achieve the above object, a data receiving apparatus according to still another embodiment of the present invention receives display identification information including feature information supported by a sink apparatus regarding audio data from the data transmitting apparatus. A reception unit; and an analysis unit for analyzing the received display identification information, wherein the display identification information includes a main / auxiliary audio characteristic field representing information on characteristics of main audio and auxiliary audio supported by the sink device. Including.

  The main / auxiliary audio characteristic field includes an audio mix field (Audio Mix Field) indicating whether the sink device supports synthesis of main audio and auxiliary audio, and whether the sink device supports auxiliary audio. An auxiliary audio support field (Language Audio Support Field) indicating whether or not the sink device supports audio data in a plurality of languages, and the sink device is used for multi-view content. Multi-view audio support field indicating whether to support multi-stream audio data (Multiview Audio Support) Field), a maximum stream count field (Maximum Stream Count Field) indicating the number of maximum audio streams that can be handled by the sink device, and an audio descriptor number field (Number Of Audio Descriptor Field) indicating the number of 3D audio descriptors. One can be included.

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

  In order to achieve the above object, a data transmission / reception system according to still another embodiment of the present invention generates display identification information including feature information supported by a sink device with respect to audio data. And a data receiving device for receiving and analyzing the display identification information from the data transmitting device, the display identification information corresponding to characteristics of main audio and auxiliary audio supported by the sink device Contains main / auxiliary audio characteristic fields representing information.

  In order to achieve the above object, a data transmission method according to still another embodiment of the present invention includes a step of generating a packet including a first subpacket and a second subpacket, and the generated packet. Transmitting to a data receiving device, wherein the first subpacket and the second subpacket include different audio data for the first content.

  In order to achieve the above object, a data receiving method according to still another embodiment of the present invention includes a step of receiving a packet including a first subpacket and a second subpacket from a data transmitting apparatus, and the reception Parsing the first subpacket and the second subpacket, wherein the first subpacket and the second subpacket include different audio data for the first content.

  In order to achieve the above object, a data transmission method according to still another embodiment of the present invention includes a step of generating an audio metadata packet, and transmitting the generated audio metadata packet to a data receiving device. And a header of the generated audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted.

  In order to achieve the above object, a data receiving method according to still another embodiment of the present invention includes a step of receiving an audio metadata packet from a data transmitting device, and parsing the received audio metadata packet. The header of the received audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted.

  In order to achieve the above object, a data transmission method according to still another embodiment of the present invention includes generating display identification information including feature information supported by a sink device for audio data, and receiving data Transmitting the display identification information to a device, wherein the display identification information includes a main / auxiliary audio characteristics field representing information on characteristics of main audio and auxiliary audio supported by the sink device.

  In order to achieve the above object, a data receiving method according to an embodiment of the present invention includes receiving display identification information including feature information supported by a sink device with respect to audio data from a data transmitting device; Analyzing the received display identification information, wherein the display identification information includes a main / auxiliary audio characteristics field representing information on characteristics of main audio and auxiliary audio supported by the sink device.

  According to various embodiments of the present invention as described above, the present invention provides an interface standard capable of transmitting and receiving a plurality of audio data related to the same content between a source device and a sink device.

It is a figure which shows a single audio stream and a multi audio stream. It is a figure which shows the multi audio | voice with respect to a dual apparatus and screen separation for a source apparatus to a sink apparatus. FIG. 6 is a diagram schematically showing data transmission / reception between a sink device and a source device for displaying the screen separation support information. FIG. 6 is a diagram illustrating a situation in which a payload of the multi-audio sample packet is transmitted. It is a figure which shows the transmission timing of 3D audio signal. It is a figure which shows the transmission timing of 3D audio signal. It is a block diagram which shows the structure of the data transmission / reception system concerning one embodiment of this invention. It is a block diagram which shows the structure of the data transmitter concerning one embodiment of this invention. It is a block diagram which shows the structure of the data receiver concerning one embodiment of this invention. It is a block diagram which shows the structure of the data transmission / reception system concerning other embodiment of this invention. It is a block diagram which shows the structure of the data transmitter concerning other embodiment of this invention. It is a block diagram which shows the structure of the data receiver concerning other embodiment of this invention. It is a block diagram which shows the structure of the data transmission / reception system concerning other embodiment of this invention. It is a block diagram which shows the structure of the data transmitter concerning 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. 6 is a diagram illustrating various data transmission formats when quad-view video content is transmitted in a 3D interlace format. FIG. 6 is a diagram illustrating various data transmission formats when quad-view video content is transmitted in a 3D interlace format. FIG. 6 is a diagram illustrating various data transmission formats when quad-view video content is transmitted in a 3D interlace 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. It is a flowchart of the data reception method concerning further another embodiment of this invention.

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In describing the present invention, if it is determined that a specific description of a related known function or configuration may obscure the gist of the present invention, a detailed description thereof will be omitted. The terms described later are terms defined in consideration of the function of the present invention, and this may vary depending on the intention of the user, the operator, or customs. Therefore, the definition must be made based on the contents throughout this specification.

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

  This specification refers to the following documents.

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

Table 1 below briefly explains the terms used in this specification.

  FIG. 1 is a diagram illustrating a single audio stream and a multi audio stream.

  As shown in FIG. 1A, a single audio stream is a case where a plurality of audio data exists for at least one video data, and these audio data are transmitted as one single stream. In a 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 a multi-audio stream, there are a number of single-AV stream sets in which a single packet stream ID is assigned to each single AV stream. The video data of a large number of single AV streams are independent of each other.

  Each audio stream of the multi-audio stream transmits a maximum of two audio channels. And associated with a single audio stream. For example, in single view mode, each audio can be connected to a default video stream, and in dual view mode, audio can be connected to the left image and / or the right image. It can also send one or more auxiliary audio options: That is, screen separation tagging (Split-screen tagging), language display (Language indication), audio display for visually impaired / hearing impaired (indication of audio for visible / hearing implied).

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

  Screen separation (or multi-window can also be used as the same term) can be a selective configuration used with multi-audio. The screen separation mode means a configuration in which the screen is separated by the sink device, and the audio stream is tagged and mapped to a specific window.

  FIG. 2 is a diagram illustrating that the source device transmits multi-audio for dual window and screen separation to the sink device.

  2A is an embodiment in which audio data for each is transmitted to a multi-screen, and FIG. 2B is an embodiment in which a plurality of audio data is transmitted by quick preview viewing or PIP viewing. FIG. 2C shows an embodiment in which a plurality of audio data according to a multi-screen game is transmitted. The user of the sink device can select and listen to the desired audio.

  FIG. 3 is a diagram schematically showing data transmission / reception between the sink device and the source device for displaying the screen separation support information.

  The source device 310 transmits a vendor-specific info frame, a multi-audio sample packet, and a multi-audio metadata packet to the sink device.

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

  The sink device 320 transmits an extended device capability register (Extended Device Capability Register) to the source device to inform the multi-audio mode information supported by the sink device. Specific embodiments will be described later.

  Multi-audio, on the other hand, supports the transmission of auxiliary audio tracks (eg, multiple languages, audio descriptions for visual impairment, or clean audio for auditory impairment). In this case, a maximum of 16 audio streams can be transmitted simultaneously. This will be described in detail later.

TMDS signaling and encoding Data platform packet

3D audio sample packet 3D audio is defined as audio in which speakers can be placed in a 3D space at a fixed position according to 3D audio standards (eg 10.2 ch, 22.2 ch, 30.2 ch, etc.). The 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 the data island period. Each packet contains up to 8 audio channels. The configuration of the subpacket is determined by the sequence number and the sample present bit (sample_present bits) in the header.

  Sequence number field (sequence_number): Indicates the order of the current packet. Since multiple 3D audio sample packets contain a single 3D audio sample, this field is necessary to accurately identify the packet order.

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

Multi-Audio Sample Packet A multi-audio sample packet can include four audio samples, where each audio sample is independently associated with an audio stream. When the source device transmits four or more independent audio streams simultaneously, such a continuous audio stream is 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 alignment. 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 (Descriptor field) is the view mode (ie single-view or multi-view), and Selective information (eg, screen separation tagging, language codes, audio for visual impairment, etc.) is described. These will be described in detail later.

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

  Stream present field (stream_presnt.spX): indicates whether or not the subpacket X includes an audio sample of the stream X.

  Stream flat field (stream_flat.spX): indicates whether subpacket X represents a “flatline” sample of stream X. stream_present. Valid only when spX is set.

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

  FIG. 4 is a diagram illustrating a situation where the payload of the multi-audio sample packet is transmitted.

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

3D Audio Metadata Packet Ancillary data that describes active 3D audio data is transmitted using 3D audio metadata packets. If the source device can send 3D audio sample packets, the source device always sends the correct 3D audio metadata packet once every at least two video fields.

The following shows a 3D audio metadata packet.

Multi-audio metadata packet (Multi-Audio Metadata Packet)
Supplementary data describing the active multi-audio stream is transmitted using multi-audio metadata packets. This packet is used to describe the auxiliary audio selection for each audio stream transferred from the view type and multi-audio sample packet.

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

The following shows a multi-audio metadata packet.

  View type field (MA_View_Type): indicates the associated view mode of a multi-audio stream such as single view or multi-view. Please refer to the table below.

  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 connects each multi-audio metadata packet to a multi-audio sample packet having the same sequence number.

  Audio stream number field (Num_Audio_Streams) This field indicates the total number of audio streams transmitted by multi-audio sample packets.

  Screen separation valid field (SC_Valid): If set to 1, screen separation tagging is supported and the screen separation configuration field is detailed in the next 7 bits. If set to 0, screen separation tagging is not supported or refined, and the next 7 bits are left for other uses.

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

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.

The table below shows multi-audio descriptors.

  Screen separation tag field (Split_Screen_Tag): Represents a specific window (as defined by the separation screen configuration) associated with the audio stream currently represented by the multi-audio descriptor. A detailed description is presented in Table 16 below. This field is valid only when SC_valid = 1, or the sink device ignores this field.

  Associated view identification field (Associated_View_ID): represents a specific 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 is given in Table 15 below.

  Valid language code field (LC_present): If this field is set to 1, the current descriptor includes a valid language code field (Language_Code) in the next byte.

  Mixed audio field (Mixed_Audio): If this field is set to 1, the corresponding audio stream includes a pre-mixed stream of general audio and auxiliary audio as shown by the auxiliary audio type field (Suppl_Audio_Type).

  SAT present field (SAT_present): If this field is set to 1, the current descriptor includes an auxiliary audio type field (Suppl_Audio_Type) valid in the next 4 bits.

  Auxiliary audio type field (Suppl_Audio_Type): indicates the type of auxiliary audio for the corresponding audio stream. See Table 17 for a detailed explanation. This field is valid only when the SAT present field (SAT_present) = 1, or the sink device ignores this field.

Language code field (Language_Code): A language code defined as ISO 639 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.

Active multi-audio mode indicator
The source device uses Vendor-Specific Infoframe (VSIF) to represent the exact view mode transmitted to the sink device. The VSIF is structured as shown in Table 18.

MHL multi-view field (MHL_MULTI_VIEW): indicates what multi-view mode is transmitted. Detailed description is shown in Table 19.

Video 3D video descriptor for 3D support

  Each supported 3D video mode is represented by one 3D video descriptor.

  MV_SUPP: If set to “1”, the device supports using 3D video format for multi-view video streaming.

Audio Channel / Speaker Allocation When the sink device is capable of receiving 3D audio, the 3D channel speaker allocation descriptors described in Tables 38 through 40 are used to represent the configuration of attached speakers. An indication of the current speaker assignment for 3D audio transmitted from the source device is handled in the 3D CA field of the 3D audio metadata packet. Refer to Table 27 to Table 29 for a detailed description of the 3D CA field.

3D Audio Data Packetization
Each subpacket of the 3D audio sample packet includes zero or one IEC 60958 frame. If the source device needs to downmix the 3D audio stream and the downmixed audio stream is also a 3D audio stream, they are processed using 3D audio sample packets. If the sink device does not support 3D audio features, the source device will not send a 3D audio sample packet with the 3D audio metadata packet.

Depending on the number of channels, there are other numbers of subpacket layouts. Tables 21 through 23 below show the 3D audio packet layout when transmitting each of 12, 24, or 32 channels.

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

  Subsequent 3D audio sample packets can be used to process one 3D audio sample containing between 9 and 32 channels of L-PCM audio (ie, 5 to 16 IEC 60958 frames).

  The first packet of 3D audio samples is packed with 8 audio channels and has a sequence number field set to zero. The sequence number is incremented by 1 for each additional packet within the same 3D audio sample. The last packet contains 8 or fewer audio channels depending on the total number of channels in the 3D audio sample.

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

  5 and 6 are diagrams illustrating the transmission timing of the 3D audio signal.

  5 and 6, it is understood that three 8-channel 2D audio signal samples are transmitted in a horizontal blanking interval. In the 24-channel 3D audio signal, one sample is transmitted during the same period.

Multi-Audio Data Packetization
MHL allows the MHL source device 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 different audio for each view). Auxiliary audio mode can represent screen separation tagging (ie, other parts of the screen are tagged and associated with its own audio stream), language code, or audio for visually / audibly impaired persons . Each audio stream is associated with one view mode and includes up to two audio channels.

  Each subpacket of a multi-stream audio sample packet may contain a “frame” of IEC 60958 or IEC 61937 “blocks” defined by zero or one 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 within the packet alignment is identified by a sequence number field. The MHL source device can simultaneously transmit a maximum of 16 independent audio streams within a single AV stream.

  Tables 25 and 26 show examples of multi-audio sample packets and multi-audio metadata packet layouts when the MHL source device transmits four audio streams by single-view video streaming. The multi-audio metadata packet describes the characteristics (auxiliary information, language) of each audio stream.

  Tables 27 and 28 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. The multi-audio metadata packet describes the characteristics (relevant view, auxiliary information, language) of each audio stream.

Tables 29 and 30 show the multi-audio sample packet and multi-audio metadata packet layout when the MHL source device transmits six 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 impairments Audio for VI: Audio stream for visual impairments

Audio for HI: Audio stream for hearing impairments Audio for VI: Audio stream for visual impairments

Audio for HI: Audio stream for hearing impairments Audio for VI: Audio stream for visual impairments

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

  When a 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, the modified accurate 3D audio metadata packet is not affected for the first time. Sent before one video frame following non-silent audio samples. Preferentially, this occurs just before the first affected audio sample is transmitted.

  The 3D audio metadata packet transmission can occur at any time within the data platform period including the horizontal / vertical blacking period.

  When 3D audio is streamed, the MHL sink device ignores the CC and CA fields in the audio info frame, and instead refers to 3D_CC and 3D_CA in the 3D audio metadata packet.

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

  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 infoframe, the modified accurate multi-audio metadata packet is not affected for the first time. Transmitted before a 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 transmissions can occur at any time within a data platform period including horizontal / vertical blacking periods.

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

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

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

WRITE_BURST Use for 3D / Multi-Audio Support Support for 3D audio mode is shown using a series of formatted WRITE_BURST moves, as shown in Table 30 and Table 31.

The bold text represents the designated speaker associated with the 10.2 channel.

The bold text represents the designated speaker associated with the 22.2 channel

The bold text represents the designated speaker associated with the 30.2 channel

Link control bus (Link Control Bus)
Device register change interrupt (Device Register Change Interrupt)

  The 3D_AUD_REQ is used by the MHL source device to request 3D audio support information from the MHL sink device. See MHL spec 6.14.

Burst_ID Code

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

Control and Configuration (Control and Configuration)
Extended Device Capability Register (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 table below, the device performance register address 0x85 extended with the MHL specification can be used to represent the multi-audio mode supported by the sink device.

Multi audio mode (Multi-Audio Mode)
Each sink device can display a multi-audio mode (MULTI_AUD_MODE) in which a specific multi-audio mode to be supported is registered.

The multi-audio mode register includes a split screen audio field that indicates whether the sink device supports multi-audio reception and processing related to the split screen.

  If the device is not capable of supporting multi-view video streaming, this field is set to zero.

Multi-stream audio (Multi-StreamAudio)
Hereinafter, multi-stream audio according to various embodiments of the present invention will be described. The multi-stream audio transmission specifications described below can be applied to various wired / wireless transmission interfaces including HDMI and MHL.

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

  Wired interfaces according to various embodiments of the present invention add support for single-view video streaming (eg, support multiple-lingual or audio for visually / deaf persons) it can. This can be done by modifying the audio metadata packet (Audio Metadata Packet) or by modifying the HDMI audio data block (HDMI Audio Data Block).

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

Scenarios The table below shows possible scenarios.

For multi-stream audio sample packets with 4 subpackets:
1) When a single TV program is transmitted with an audio description for a single view, stream 0 contains a normal audio signal and stream 1 is an audio description for the visually impaired A signal can be included.

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

  3) One audio signal stream composed of one language in a single view and two audio description signals for visually impaired persons supported in different languages can be transmitted. 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 do.

  4) The source device can transmit an audio signal for multiview. When dual views are supported, the most basic form is to send the audio signal for each view in one transmission stream. The dual view includes independent first and second views, each view providing independent content.

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

  6) In the case of dual view, any one view can further 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 person for the second view can be transmitted. For example, stream 0 may include an audio signal for the first view, stream 1 may include an audio signal for the second view, and stream 3 may include an audio description signal for the second view.

  7) One stream can be used to transmit a common audio signal. That is, a common audio signal stream, a first view dedicated audio stream, and a second view dedicated audio stream for the first view and the second view can be transmitted, respectively. In this case, at the receiving end, the common audio stream and the dedicated audio stream are multiplexed 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 view and the second view (for example, background sound, progress guidance voice, etc.), stream 1 is a dedicated audio signal for the first view, and stream 2 is dedicated for the second view. Audio signals can be included.

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

  As shown in FIG. 7, 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 transmission device 100-1 transmits a packet including the first subpacket and the second subpacket to the data reception device 200-1.

  The data reception device 200-1 receives the packet including the first subpacket and the second subpacket from the data transmission device 100-1.

  At this time, the first subpacket and the second subpacket include different audio data for the first content.

  Hereinafter, the configurations of the data transmission device 100-1 and the data reception device 200-1 will be described in more detail.

  FIG. 8 is a block diagram showing a configuration of the data transmitting apparatus 100-1 according to the embodiment of the present invention.

  As illustrated in FIG. 8, the data transmission device 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 the first subpacket and the second subpacket. At this time, the first subpacket and the second subpacket include different audio data for the first content.

  The transmission unit 120 transmits the generated packet to the data reception device 200-1.

  At this time, the first subpacket may include audio data for a non-disabled person, and the second subpacket may include audio data for a visually impaired person.

  The first subpacket and the second subpacket may include audio data in different 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 the second content different from the first content.

  At this time, the audio data included in the first subpacket is dedicated audio data for the first content, the audio data included in the third subpacket is dedicated audio data for the second content, and the second subpacket The audio data included in the packet can be common audio data for the first content and the second content.

  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.

  FIG. 9 is a block diagram showing the configuration of the data receiving apparatus 200-1 according to the embodiment of the present invention.

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

  The receiving unit 210 receives a packet including the first subpacket and the second subpacket from the data transmission device 100-1. At this time, the first sub-packet and the second sub-packet may include different audio data for the first content.

  The parsing unit 220 is configured to parse the received first subpacket and the second subpacket.

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

  In contrast, 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 the second content different from the first content.

  At this time, the audio data included in the first subpacket is dedicated audio data for the first content, the audio data included in the third subpacket is dedicated audio data for the second content, and the second subpacket The audio data included in the packet can be common audio data for the first content and the second content.

  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.

Audio metadata packet (Audio Metadata Packet)
The source device transmits an audio metadata packet to the sink device to inform the audio specification to be transmitted. At this time, the header of the audio metadata packet has the following structure.

  Each field will be described as follows.

  3D audio field (3D_AUDIO) [1 bit]: When 3D_AUDIO = 1, 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 / Includes a speaker assignment information (ACAST) field (see table below). Such a field is set to 1 when the source sends a 3D audio packet.

  View number field (NUM_VIEWS) [2 bits]: Indicates the number of views. If NUM_VIEWS = 00, single view video streaming is supported. If 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. When NUM_AUDIO_STR = 01, 10, or 11, the audio metadata packet (Audio Metadata Packet) includes up to four audio metadata descriptors, each corresponding to an audio stream.

The table below represents the payload of an audio metadata packet for 3D audio. When 3D_Audio = 1, the metadata packet payload has the following structure.

  That is, it includes a 3D_CC field representing 3D audio channel count information and an ACAST field indicating the audio channel allocation standard type provided by the source.

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

The table below shows the payload of an audio metadata packet for multi-stream audio. When 3D_Audio = 0, the metadata packet payload has the following structure.

As shown in Table 53, the payload of the audio metadata packet includes a 5-byte audio metadata descriptor (Audio_Metadata_Descriptor). The audio metadata descriptor (4 fields, 5 bytes each) is an audio metadata or multi-stream one-bit audio sample packet (Multi-stream One) for the subpacket X in the multi-stream audio sample packet. The audio metadata for the subpacket X is expressed in Bit Audio Sample Packet). The structure of the audio metadata descriptor is described below.

  Each field will be described as follows.

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

  Multiview field (left side) (Multiview_Left) [1 bit]: When Multiview_Left = 1, the corresponding audio stream is mapped to the left stereoscopic video 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]: If Multiview_Right = 1, the corresponding audio stream is mapped to the right stereoscopic video in 3D video format. If Multiview_Right = 0, this field is NUM_VIEWS. Effective only for = 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 accurately identified. Or, the language of the corresponding audio stream will not be specified.

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

  Premix auxiliary audio field (Suppl_A_Mixed [1 bit]: Suppl_A_Mixed = 1, the corresponding audio stream can include a main audio component and a premix auxiliary audio track (pre-mixed audio track that appears by Suppl_A_Type). This bit is valid only when Suppl_A_Valid = 1.

  Auxiliary audio type field (Suppl_A_Type) [3 bits]: Auxiliary audio type defined in the following table. This field is valid only when Suppl_A_Valid = 1. Table 55 shows the description of the auxiliary audio type field value.

Language code (Language_Code) [3 Bytes]: The language of the corresponding audio stream is identified. The language code is defined by ISO639. Although the three character codes are located, 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.

  FIG. 10 is a block diagram showing a configuration of a data transmission / reception system 1000-2 according to another embodiment of the present invention.

  As shown in FIG. 10, 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.

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

  At this time, the header of the audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not the 3D audio sample packet is transmitted.

  Hereinafter, the configuration 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.

  FIG. 11 shows a data transmission device 100-2 according to another embodiment of the present invention, which includes a packet generation unit 110 and a transmission 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 (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted.

  The transmission unit 120 transmits the generated audio metadata packet to the data reception device 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) indicating the number information of audio streams to be transmitted.

  In addition, the header of the generated audio metadata packet may further include a view number field (Number Of Views Field) indicating the number information of different contents to be transmitted.

  In addition, the payload of the generated audio metadata packet includes a meta packet corresponding to a sub-packet of a multi-stream audio sample packet (Multi-stream Audio Sample Packet) or a multi-stream one-bit audio sample packet (Multi-stream One Bit Audio Sample Packet). An audio metadata descriptor field representing the data can be included.

  The audio metadata descriptor field includes an emergency channel field indicating whether there is an emergency situation broadcast, and a multi-view indicating whether audio data corresponding to a left-eye or right-eye image is included in the multi-view. A field (Multiview Field), a language code valid field (Language Code Valid Field) indicating whether or not language is identified for audio data, an auxiliary audio valid field (Supplemental Audio Valid Field) indicating the presence or absence of auxiliary audio data, main audio data and the auxiliary audio Premix auxiliary audio field (pre-) indicating presence / absence of premix with data It includes at least one of an “Implemented Supplemental Audio Field”, an auxiliary audio type field indicating the type of the auxiliary audio data (Supplemental Audio Type Field), and a language code field indicating the language code for the audio data (Language Code Field). Can do.

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

  As illustrated in FIG. 12, a data reception device 200-2 according to another embodiment of the present invention includes a reception unit 210 and a parsing unit 220.

  The receiving unit 210 is configured to receive an audio metadata packet from the data transmission device 100-2. The header of the audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted.

  The parsing unit 220 is configured to parse the received audio metadata packet.

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

  In addition, the header of the audio metadata packet may further include a view number field (Number Of Views Field) indicating the number information of different received contents.

  In addition, the payload of the audio metadata packet is a meta for a sub-packet of a multi-stream audio sample packet (Multi-stream Audio Sample Packet) or a multi-stream one-bit audio sample packet (Multi-stream One Bit Audio Sample Packet). An audio metadata descriptor field representing the data can be included.

  At this time, the audio metadata descriptor field includes an emergency channel field (Emergency Channel Field) indicating whether there is an emergency situation broadcast, and a multi-view indicating whether audio data corresponding to the left-eye or right-eye video is included in the multi-view. View field (Multiview Field), Language code valid field (Language Code Valid Field) indicating whether or not language is identified for audio data, Auxiliary audio valid field (Supplemental Audio Valid Field) indicating the presence or absence of auxiliary audio data, main audio data and the auxiliary A premix auxiliary audio field (pr indicating the presence or absence of premix with audio data) -It includes at least one of a mixed Supplemental Audio Field), an auxiliary audio type field indicating the type of the auxiliary audio data (Supplemental Audio Type Field), and a language code field indicating the language code for the audio data (Language Code Field). be able to.

Audio data block (Audio Data Block)
The following is a table showing audio data blocks of EDID (Extended Display Identification Data). In the table below, the 3-4 byte part is redefined in the table below.

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

The following table shows a block configuration for replacing 3-4 bytes of the audio data block.

  Each field will be described as follows.

  Emergency channel field (Supports_MS_Emergency [1bit]: Supports_MS_Emergency = 1, the sink device helps to receive and process the emergency alert audio channel. If the Supports_MS_Emergency = 0, the feature is Do not support.

  Audio mix field (Supports_MS_Mix) [1 bit]: When Supports_MS_Mix = 1, the sink device supports the synthesis of the main audio and the auxiliary audio (supplementary audio). If Supports_MS_Mix = 0, the sink device does not support such synthesis, but only supports playback of mixed audio.

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

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

  Multi-view audio support field (Supports_MS_MultiView) [1 bit]: If Supports_MS_MultiView = 1, the sink device supports multi-stream audio for multi-view video streaming. Supports_MS_MultiView = 0 indicates nothing or that 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 maximum number of audio streams that can be handled by the sink device. The Max_Stream_Count-1 value is shown in the table below.

Audio descriptor number field (NUM_HDMI — 3D_AD) [3 bits]: Indicates the number of 3D audio descriptors.

  FIG. 13: is a block diagram which shows the structure of the data transmission / reception system 1000-3 concerning further another embodiment of this invention.

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

  The data transmission device 100-3 generates display identification information including feature information supported by the sink device regarding the audio data, and transmits the display identification information to the data reception device 200-3.

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

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

  FIG. 14 is a block diagram showing a configuration of a data transmitting apparatus 100-3 according to still another embodiment of the present invention.

  As illustrated in FIG. 14, a data transmission device 100-3 according to still another embodiment of the present invention includes a generation unit 130 and a transmission unit 120.

  The generation unit 130 is configured to generate display identification information including feature information supported by the sink device regarding audio data.

  The transmission unit 120 transmits the display identification information to the data reception device 200-3.

  At this time, the display identification information includes a main / auxiliary audio characteristic field indicating information on characteristics of main audio and auxiliary audio supported by the sink device.

  At this time, the main / auxiliary audio characteristic field includes an audio mix field (Audio Mix Field) indicating whether the sink device supports synthesis of main audio and auxiliary audio, and whether the sink device supports auxiliary audio. Auxiliary audio support field indicating whether the sink device supports audio data consisting of a plurality of languages (Language Support Field), and the sink device is for multi-view content Multi-view audio support field indicating whether to support multi-stream audio data (Multiview Audio Supp) rt Field), a maximum stream count field (Maximum Stream Count Field) representing the number of maximum audio streams that can be handled by the sink device, and an audio descriptor number field (Number Of Audio Descriptor Field) representing the number of 3D audio descriptors, At least one can be included.

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

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

  As shown in FIG. 15, a data reception device 200-3 according to still another embodiment of the present invention includes a reception unit 210 and an analysis unit 230.

  The reception unit 210 is configured to receive display identification information including feature information supported by the sink device regarding 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 a main / auxiliary audio characteristic field indicating information on characteristics of main audio and auxiliary audio supported by the sink device.

  The main / auxiliary audio characteristic field includes an audio mix field (Audio Mix Field) indicating whether the sink device supports synthesis of main audio and auxiliary audio, and whether the sink device supports auxiliary audio. An auxiliary audio support field (Language Audio Support Field) indicating whether or not the sink device supports audio data in a plurality of languages, and the sink device is used for multi-view content. Multi-view audio support field indicating whether to support multi-stream audio data (Multiview Audio Support) Field), a maximum stream count field (Maximum Stream Count Field) indicating the number of maximum audio streams that can be handled by the sink device, and an audio descriptor number field (Number Of Audio Descriptor Field) indicating the number of 3D audio descriptors. One can be included.

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

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

  16A to 16C are diagrams illustrating various data transmission formats when quad-view video content is transmitted in a 3D interlace format.

In this case, the vendor-specific info frame and the vendor-specific data block can be modified. Specifically, the field defining the conventional 3D dual view is extended to the reserved area.

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

  FIG. 17 is a flowchart of a data transmission method according to an embodiment of the present invention.

  As shown in FIG. 17, the data transmission method according to an embodiment of the present invention includes a step of generating a packet including a first subpacket and a second subpacket (S1710), and receiving the generated packet as data. Transmitting to the apparatus (S1720), wherein the first subpacket and the second subpacket include different audio data for the first content.

  At this time, the first subpacket may include audio data for a non-disabled person, and the second subpacket may include audio data for a visually impaired person.

  The first subpacket and the second subpacket may include audio data in different 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 the second content different from the first content.

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

  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.

  FIG. 18 is a flowchart of a data receiving method according to an embodiment of the present invention.

  As shown in FIG. 18, the data reception method according to another embodiment of the present invention includes a step of receiving a packet including a first subpacket and a second subpacket from a data transmission device (S1810), Parsing the received first sub-packet and the second sub-packet (S1820), wherein the first sub-packet and the second sub-packet include different audio data for the first content.

  The first subpacket may include audio data for a non-disabled person, and the second subpacket may include audio data for a visually impaired person.

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

  In this case, 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 the second content different from the first content.

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

  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.

  FIG. 19 is a flowchart of a data transmission method according to another embodiment of the present invention.

  As shown in FIG. 19, the step of generating an audio metadata packet according to another embodiment of the present invention (S1910), and the step of transmitting the generated audio metadata packet to a data receiving device (S1920). The header of the generated audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted.

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

  In addition, the header of the generated audio metadata packet may further include a view number field (Number Of Views Field) indicating the number information of different contents to be transmitted.

  Also, the payload of the generated audio metadata packet is a sub-stream of a multi-stream audio sample packet (Multi-stream Audio Sample Packet) or a multi-stream one-bit audio sample packet (Multi-stream One Bit Audio Sample Packet). An audio metadata descriptor field representing metadata for the packet can be included.

  The audio metadata descriptor field includes an emergency channel field indicating whether there is an emergency situation broadcast, and a multi-view indicating whether audio data corresponding to a left-eye or right-eye image is included in the multi-view. A field (Multiview Field), a language code valid field (Language Code Valid Field) indicating whether or not language is identified for audio data, an auxiliary audio valid field (Supplemental Audio Valid Field) indicating the presence or absence of auxiliary audio data, main audio data and the auxiliary audio Premix auxiliary audio field (pre-) indicating presence / absence of premix with data It includes at least one of an “Implemented Supplemental Audio Field”, an auxiliary audio type field indicating the type of the auxiliary audio data (Supplemental Audio Type Field), and a language code field indicating the language code for the audio data (Language Code Field). Can do.

  FIG. 20 is a flowchart of a data receiving method according to another embodiment of the present invention.

  As shown in FIG. 20, a data receiving method according to another embodiment of the present invention includes a step of receiving an audio metadata packet from a data transmitting apparatus (S2010), and parsing the received audio metadata packet. And a header of the received audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted.

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

  In addition, the header of the audio metadata packet may further include a view number field (Number Of Views Field) indicating the number information of different received contents.

  In addition, the payload of the audio metadata packet is a meta for a sub-packet of a multi-stream audio sample packet (Multi-stream Audio Sample Packet) or a multi-stream one-bit audio sample packet (Multi-stream One Bit Audio Sample Packet). An audio metadata descriptor field representing the data can be included.

  The audio metadata descriptor field includes an emergency channel field indicating whether there is an emergency situation broadcast, and a multi-view indicating whether audio data corresponding to a left-eye or right-eye image is included in the multi-view. A field (Multiview Field), a language code valid field (Language Code Valid Field) indicating whether or not language is identified for audio data, an auxiliary audio valid field (Supplemental Audio Valid Field) indicating the presence or absence of auxiliary audio data, main audio data and the auxiliary audio Premix auxiliary audio field (pre-) indicating presence / absence of premix with data It includes at least one of an “Implemented Supplemental Audio Field”, an auxiliary audio type field indicating the type of the auxiliary audio data (Supplemental Audio Type Field), and a language code field indicating the language code for the audio data (Language Code Field). Can do.

  FIG. 21 is a flowchart of a data transmission method according to still another embodiment of the present invention.

  As shown in FIG. 21, a data transmission method according to still another embodiment of the present invention includes generating display identification information including feature information supported by a sink device for audio data (S2110), and data Transmitting the display identification information to a receiving device (S2120), wherein the display identification information includes a main / auxiliary audio characteristic field representing information on characteristics of main audio and auxiliary audio supported by the sink device.

  The main / auxiliary audio characteristic field includes an audio mix field (Audio Mix Field) indicating whether the sink device supports synthesis of main audio and auxiliary audio, and whether the sink device supports auxiliary audio. An auxiliary audio support field (Language Audio Support Field) indicating whether or not the sink device supports audio data in a plurality of languages, and the sink device is used for multi-view content. Multi-view audio support field indicating whether to support multi-stream audio data (Multiview Audio Support) Field), a maximum stream count field (Maximum Stream Count Field) indicating the number of maximum audio streams that can be handled by the sink device, and an audio descriptor number field (Number Of Audio Descriptor Field) indicating the number of 3D audio descriptors. One can be included.

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

  FIG. 22 is a flowchart of a data receiving method according to still another embodiment of the present invention.

  As shown in FIG. 22, the data receiving method according to another embodiment of the present invention includes receiving display identification information including feature information supported by the sink device regarding audio data from the data transmitting device (S2210). ) And analyzing the received display identification information (S2220), the display identification information being a main / auxiliary audio characteristic field representing information on characteristics of main audio and auxiliary audio supported by the sink device including.

  The main / auxiliary audio characteristic field includes an audio mix field (Audio Mix Field) indicating whether the sink device supports synthesis of main audio and auxiliary audio, and whether the sink device supports auxiliary audio. An auxiliary audio support field (Language Audio Support Field) indicating whether or not the sink device supports audio data in a plurality of languages, and the sink device is used for multi-view content. Multi-view audio support field indicating whether to support multi-stream audio data (Multiview Audio Support) Field), a maximum stream count field (Maximum Stream Count Field) indicating the number of maximum audio streams that can be handled by the sink device, and an audio descriptor number field (Number Of Audio Descriptor Field) indicating the number of 3D audio descriptors. One can be included.

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

  While the embodiments of the present invention have been illustrated and described above, the present invention is not limited to the specific embodiments described above, and does not depart from the gist of the present invention claimed in the scope of claims. Various modifications can be made by those having ordinary knowledge in the technical field to which the invention belongs, and such modifications are not individually understood from the technical idea and perspective of the present invention. Don't be.

Claims (39)

A data transmission device,
A packet generator that generates a packet including a first subpacket and a second subpacket;
A transmission unit that transmits the generated packet to a data reception device;
The data transmission device, wherein the first subpacket and the second subpacket include different audio data for the first content. The first subpacket includes audio data for a non-disabled person;
The data transmission apparatus according to claim 1, wherein the second subpacket includes audio data for a visually impaired person.   The data transmitting apparatus according to claim 1, wherein the first subpacket and the second subpacket include audio data in different languages.   The data transmission apparatus according to claim 1, wherein the first subpacket includes audio data corresponding to an audio description for the second subpacket.   The data transmission apparatus according to claim 1, wherein the packet further includes a third subpacket including audio data for the second content different from the first content. The audio data included in the first subpacket is dedicated audio data for the first content,
The audio data included in the third subpacket is dedicated audio data for the second content,
6. The data transmission apparatus according to claim 5, wherein the audio data included in the second subpacket is common audio data for the first content and the second content. The packet further includes a fourth subpacket including audio data for the second content,
The data transmission device according to claim 5, wherein the third subpacket and the fourth subpacket include different audio data. A data receiving device,
A receiving unit for receiving a packet including the first sub-packet and the second sub-packet from the data transmitting device;
A parsing unit for parsing the received first subpacket and the second subpacket,
The data receiving apparatus, wherein the first subpacket and the second subpacket include different audio data for the first content. The first subpacket includes audio data for a non-disabled person;
The data receiving apparatus according to claim 8, wherein the second subpacket includes audio data for a visually impaired person.   The data receiving apparatus according to claim 8, wherein the first subpacket and the second subpacket include audio data in different languages.   The data receiving apparatus according to claim 8, wherein the first subpacket includes audio data corresponding to an audio description for the second subpacket.   The data receiving apparatus according to claim 8, wherein the packet further includes a third subpacket including audio data for the second content different from the first content. The audio data included in the first subpacket is dedicated audio data for the first content,
The audio data included in the third subpacket is dedicated audio data for the second content,
The data receiving apparatus according to claim 12, wherein the audio data included in the second subpacket is common audio data for the first content and the second content. The packet further includes a fourth subpacket including audio data for the second content,
The data receiving apparatus according to claim 12, wherein the third subpacket and the fourth subpacket include different audio data. A data transmission / reception system,
A data transmission device that generates a packet including the first subpacket and the second subpacket and transmits the packet to the data reception device;
A data receiving device for receiving the packet from the data transmitting device;
The data transmission / reception system, wherein the first subpacket and the second subpacket include different audio data for the first content. A data transmission device,
A packet generator for generating audio metadata packets;
A transmission unit that transmits the generated audio metadata packet to a data reception device;
The header of the generated audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted.   The data transmitting apparatus of claim 16, wherein the header of the generated audio metadata packet further includes an audio stream number field (Number Of Audio Stream Field) indicating the number information of the number of audio streams to be transmitted. . The header of the generated audio metadata packet is:
The data transmission apparatus of claim 16, further comprising a view number field (Number Of Views Field) representing the number information of different contents to be transmitted. The payload of the generated audio metadata packet is:
It includes an audio metadata descriptor field representing metadata for a sub-packet of a multi-stream audio sample packet (Multi-stream Audio Sample Packet) or a multi-stream one-bit audio sample packet (Multi-stream One Bit Audio Sample Packet). The data transmission device according to claim 16. The audio metadata descriptor field is:
Emergency channel field (Emergency Channel Field) indicating whether there is an emergency status broadcast, Multi-view field (Multiview Field) indicating whether audio data corresponding to the left-eye or right-eye video is included in the multi-view, language for audio data Language code valid field indicating presence / absence of identification, auxiliary audio valid field indicating presence / absence of auxiliary audio data, premix indicating presence / absence of pre-mixing of main audio data and auxiliary audio data Auxiliary audio field (pre-mixed Supplemental Audio Field), The auxiliary audio type field (Supplemental Audio Type Field) indicating the type of auxiliary audio data and the language code field (Language Code Field) indicating the language code for the audio data are included. The data transmission device described in 1. A data receiving device,
A receiving unit for receiving an audio metadata packet from the data transmitting device;
A parsing unit for parsing the received audio metadata packet;
A header of the received audio metadata packet includes a 3D audio field indicating whether or not a 3D audio sample packet is transmitted.   The data receiving apparatus of claim 21, wherein the header of the audio metadata packet further includes an audio stream number field (Number Of Audio Stream Field) indicating the number information of the received audio streams. The header of the audio metadata packet is
The data receiving apparatus of claim 21, further comprising a view number field (Number Of Views Field) representing the number information of different contents received. The payload of the audio metadata packet is
It includes an audio metadata descriptor field representing metadata for a sub-packet of a multi-stream audio sample packet (Multi-stream Audio Sample Packet) or a multi-stream one-bit audio sample packet (Multi-stream One Bit Audio Sample Packet). The data receiving device according to claim 21. The audio metadata descriptor field is:
Emergency channel field (Emergency Channel Field) indicating whether there is an emergency status broadcast, Multi-view field (Multiview Field) indicating whether audio data corresponding to the left-eye or right-eye video is included in the multi-view, language for audio data Language code valid field indicating presence / absence of identification, auxiliary audio valid field indicating presence / absence of auxiliary audio data, premix indicating presence / absence of pre-mixing of main audio data and auxiliary audio data Auxiliary audio field (pre-mixed Supplemental Audio Field), 25. At least one of an auxiliary audio type field (Supplemental Audio Type Field) representing a type of auxiliary audio data and a language code field (Language Code Field) representing a language code for the audio data is included. The data receiving device described in 1. A data transmission / reception system,
A data transmission device that generates and transmits an audio metadata packet to a data reception device;
A data receiving device for receiving the audio metadata packet from the data transmitting device;
The header of the audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted. A data transmission device,
A generating unit for generating display identification information including feature information supported by the sink device for audio data;
A transmission unit for transmitting the display identification information to a data receiving device,
The data transmission device, wherein the display identification information includes a main / auxiliary audio characteristic field representing information on characteristics of main audio and auxiliary audio supported by the sink device. The main / auxiliary audio characteristics field is:
An audio mix field (Audio Mix Field) indicating whether the sink device supports synthesis of main audio and auxiliary audio, or an auxiliary audio support field (Supplemental Audio Support Field) indicating whether the sink device supports auxiliary audio. ), A language support field indicating whether the sink device supports audio data in a plurality of languages, and indicates whether the sink device supports multi-stream audio data for multi-view content. Multiview Audio Support Field (Multiview Audio Support Field), the maximum option that the sink device can handle It includes at least one of a maximum stream count field (Maximum Stream Count Field) representing the number of audio streams and an audio descriptor number field (Number Of Audio Descriptor Field) representing the number of 3D audio descriptors. The data transmission device according to claim 27. The display identification information is
28. The data transmission apparatus of claim 27, further comprising an emergency channel field indicating whether the sink device supports emergency situation broadcast reception and processing. A data receiving device,
A receiver for receiving display identification information including feature information supported by the sink device with respect to audio data from the data transmission device;
An analysis unit for analyzing the received display identification information,
The data receiving apparatus, wherein the display identification information includes a main / auxiliary audio characteristic field representing information on characteristics of main audio and auxiliary audio supported by the sink apparatus. The main / auxiliary audio characteristics field is:
An audio mix field (Audio Mix Field) indicating whether the sink device supports synthesis of main audio and auxiliary audio, or an auxiliary audio support field (Supplemental Audio Support Field) indicating whether the sink device supports auxiliary audio. ), A language support field indicating whether the sink device supports audio data in a plurality of languages, and indicates whether the sink device supports multi-stream audio data for multi-view content. Multiview Audio Support Field (Multiview Audio Support Field), the maximum option that the sink device can handle It includes at least one of a maximum stream count field (Maximum Stream Count Field) representing the number of audio streams and an audio descriptor number field (Number Of Audio Descriptor Field) representing the number of 3D audio descriptors. The data receiving device according to claim 30. The display identification information is
The data receiving device of claim 30, further comprising an emergency channel field indicating whether the sink device supports emergency situation broadcast reception and processing. A data transmission / reception system,
A data transmission device that generates display identification information including feature information supported by the sink device with respect to audio data and transmits the display identification information to the data reception device;
A data receiving device for receiving and analyzing the display identification information from the data transmitting device,
The data transmission / reception system, wherein the display identification information includes a main / auxiliary audio characteristic field representing information on characteristics of main audio and auxiliary audio supported by the sink device. A data transmission method,
Generating a packet including a first subpacket and a second subpacket;
Transmitting the generated packet to a data receiving device,
The data transmission method, wherein the first subpacket and the second subpacket include different audio data for the first content. A data receiving method,
Receiving a packet including a first subpacket and a second subpacket from the data transmitting device;
Parsing the received first subpacket and the second subpacket,
The data reception method, wherein the first subpacket and the second subpacket include different audio data for the first content. A data transmission method,
Generating an audio metadata packet;
Transmitting the generated audio metadata packet to a data receiving device,
A data transmission method, wherein a header of the generated audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted. A data receiving method,
Receiving an audio metadata packet from the data transmitting device;
Parsing the received audio metadata packet;
A method of receiving data, wherein a header of the received audio metadata packet includes a 3D audio field (3D Audio Field) indicating whether or not a 3D audio sample packet is transmitted. A data transmission method,
Generating display identification information including feature information supported by the sink device for audio data;
Transmitting the display identification information to a data receiving device,
The data transmission method, wherein the display identification information includes a main / auxiliary audio characteristic field representing information on characteristics of main audio and auxiliary audio supported by the sink device. A data receiving method,
Receiving display identification information including feature information supported by the sink device for audio data from the data transmitting device;
Analyzing the received display identification information;
The data reception method, wherein the display identification information includes a main / auxiliary audio characteristic field representing information on characteristics of main audio and auxiliary audio supported by the sink device.

Images