KR20140115247A - Data transmitting appratus, data receiving apparatus, data tranceiving system, method for transmitting data and method for receiving data - Google Patents

Abstract

Disclosed is a data transmitting apparatus. The data transmitting apparatus according to one embodiment of the present invention includes a packet generating unit which generates a packet which includes a first sub packet and a second sub packet and a transmitting unit which transmits the generated packet to a data receiving apparatus. The first sub packet and the second sub packet include different audio data with regard to a first content.

Description

TECHNICAL FIELD [0001] The present invention relates to a data transmission apparatus, a data reception apparatus, a data transmission / reception system, a data transmission method, and a data reception method,

BACKGROUND OF THE INVENTION 1. Field of the Invention 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 contents will be.

Recently, as a multimedia environment has been established, a high-speed wire interface standard for various data transmission has been proposed. For example, HDMI and MHL define transmission standards for video data, audio signals, and control signals in various formats.

However, the conventional audio signal transmission standard does not provide an interface standard for transmitting audio data for a visually impaired person or audio data in multiple languages for contents.

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

It is an object of the present invention to provide an interface standard capable of transmitting and receiving a plurality of audio data related to the same content between a source apparatus and a sink apparatus.

According to another aspect of the present invention, there is provided a data transmission apparatus including a packet generator for generating a packet including a first subpacket and a second subpacket, And wherein the first subpacket and the second subpacket comprise different audio data for the first content.

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

In addition, the first subpacket and the second subpacket may include audio data in a different language.

In addition, the first subpacket may include audio data corresponding to the audio description of the second subpacket.

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

At this time, the audio data included in the first subpacket 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 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.

According to another aspect of the present invention, there is provided a data receiving apparatus including a receiver for receiving a packet including a first subpacket and a second subpacket from a data transmission apparatus, Packet and a parsing unit parsing the second subpacket, wherein the first subpacket and the second subpacket comprise different audio data for the first content.

In addition, the first subpacket may include audio data for a non-disabled person, and the second subpacket may include audio data for a blind person.

In addition, the first subpacket and the second subpacket may include audio data in a different language.

Here, the first subpacket may include audio data corresponding to the audio description of the second subpacket.

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

At this time, the audio data included in the first subpacket 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 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.

According to an aspect of the present invention, there is provided a data transmission / reception system including a data transmission device for generating a packet including a first subpacket and a second subpacket and transmitting the generated packet to a data reception device, And a data receiving apparatus for receiving the packet from a data transmission apparatus, wherein the first subpacket and the second subpacket comprise different audio data for the first content.

According to another aspect of the present invention, there is provided a data transmission apparatus including a packet generator for generating an audio metadata packet, and a transmitter for transmitting the generated audio metadata packet to a data receiver, And a header of the generated audio metadata packet includes a 3D audio field indicating whether a 3D audio sample packet is transmitted or not.

In addition, the header of the generated audio metadata packet may further include a number of audio stream field indicating the number of audio streams to be transmitted.

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

In addition, the payload of the generated audio metadata packet may be divided into a multi-stream Audio Sample Packet or a Multi-stream One Bit Audio Sample Packet And an audio metadata descriptor field indicating metadata about the packet.

In addition, the audio metadata descriptor field includes an emergency channel field indicating whether there is an emergency broadcast, a multi-view field indicating whether audio data corresponding to the left or right eye image is included in the multi-view, A language code valid field indicating whether or not the language is identified with respect to the audio data, a supplemental audio valid field indicating the presence or absence of the auxiliary audio data, whether or not the main audio data and the auxiliary audio data are premixed A supplemental audio type field indicating a type of the auxiliary audio data and a language code field indicating a language code for the audio data, ) ≪ / RTI > have.

According to another aspect of the present invention, there is provided a data receiving apparatus including a receiver for receiving an audio metadata packet from a data transmission apparatus, and a parser for parsing the received audio metadata packet, The header of the received audio metadata packet includes a 3D audio field indicating whether a 3D audio sample packet is transmitted or not.

The header of the audio metadata packet may further include a number of audio stream field indicating the number of audio streams to be received.

In addition, the header of the audio metadata packet may further include a number of view field indicating the number of pieces of different contents to be received.

The payload of the audio metadata packet may be a sub-packet of a multi-stream audio sample packet or a multi-stream one-bit audio sample packet. Lt; RTI ID = 0.0 > metadata metadata descriptor field. ≪ / RTI >

In addition, the audio metadata descriptor field includes an emergency channel field indicating whether there is an emergency broadcast, a multi-view field indicating whether audio data corresponding to the left or right eye image is included in the multi-view, A language code valid field indicating whether or not the language is identified with respect to the audio data, a supplemental audio valid field indicating the presence or absence of the auxiliary audio data, whether or not the main audio data and the auxiliary audio data are premixed A supplemental audio type field indicating a type of the auxiliary audio data and a language code field indicating a language code for the audio data, ) ≪ / RTI > have.

According to another aspect of the present invention, there is provided a data transmission / reception system including a data transmission apparatus for generating an audio metadata packet and transmitting the audio data packet to a data reception apparatus, And a header of the audio metadata packet includes a 3D audio field indicating whether a 3D audio sample packet is transmitted or not.

According to another aspect of the present invention, there is provided a data transmission apparatus including a generation unit for generating display identification information including characteristic information supported by a sink device with respect to audio data, And a transmitting unit for transmitting the display identification information to the device, wherein the display identification information includes a main / auxiliary audio property field indicating information about characteristics of main audio and auxiliary audio supported by the sink device.

The main / auxiliary audio property field may include an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, an auxiliary audio support field indicating whether the sink device supports auxiliary audio, Supplemental Audio Support Field), a language support field indicating whether the sink device supports audio data in a plurality of languages, a multi-view audio field indicating whether the sink device supports multi-stream audio data for multi- A maximum stream count field indicating a maximum number of audio streams that can be handled by the sink device, and an audio descriptor number field indicating a number of 3D audio descriptors Audio Descriptor Field) It can be included.

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

According to another aspect of the present invention, there is provided a data receiving apparatus including: a receiving unit for receiving, from a data transmission apparatus, display identification information including characteristic information supported by a sink apparatus with respect to audio data; And an analysis unit for analyzing the received display identification information. The display identification information includes a main / auxiliary audio property field indicating information about characteristics of main audio and auxiliary audio supported by the sink device.

The main / auxiliary audio property field may include an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, an auxiliary audio support field indicating whether the sink device supports auxiliary audio, Supplemental Audio Support Field), a language support field indicating whether the sink device supports audio data in a plurality of languages, a multi-view audio field indicating whether the sink device supports multi-stream audio data for multi- A maximum stream count field indicating a maximum number of audio streams that can be handled by the sink device, and an audio descriptor number field indicating a number of 3D audio descriptors Audio Descriptor Field) It can be included.

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

According to another aspect of the present invention, there is provided a data transmission / reception system for generating display identification information including feature information supported by a sink device with respect to audio data and transmitting the display identification information to a data reception device And a data receiving device for receiving and analyzing the display identification information from the data transmission device, wherein the display identification information includes information indicating characteristics of main audio and auxiliary audio supported by the sink device Main / secondary audio property field.

According to another aspect of the present invention, there is provided a data transmission method including generating a packet including a first subpacket and a second subpacket, Wherein the first subpacket and the second subpacket comprise different audio data for the first content.

According to another aspect of the present invention, there is provided a data receiving method including receiving a packet including a first subpacket and a second subpacket from a data transmission apparatus, Parsing the first subpacket and the second subpacket, wherein the first subpacket and the second subpacket comprise different audio data for the first content.

According to another aspect of the present invention, there is provided a method for generating an audio metadata packet, the method comprising: generating an audio metadata packet; and transmitting the generated audio metadata packet to a data receiving apparatus, The header of the metadata packet includes a 3D audio field indicating whether the 3D audio sample packet is transmitted or not.

According to another aspect of the present invention, there is provided a data receiving method including receiving an audio metadata packet from a data transmission apparatus, and parsing the received audio metadata packet The header of the received audio metadata packet includes a 3D audio field indicating whether a 3D audio sample packet is transmitted or not.

According to another aspect of the present invention, there is provided a data transmission method including generating display identification information including feature information supported by a sink device with respect to audio data, And the display identification information includes a main / auxiliary audio property field indicating information on characteristics of main audio and auxiliary audio supported by the sink device.

According to another aspect of the present invention, there is provided a data receiving method including receiving display identification information including characteristic information supported by a sink device with respect to audio data from a data transmission device, And analyzing the received display identification information, wherein the display identification information includes a main / auxiliary audio property field indicating 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 specification capable of transmitting and receiving a plurality of audio data related to the same content between a source apparatus and a sink apparatus.

1 shows a single audio stream and a multi-audio stream,
2 is a view showing a source apparatus transmitting multi-audio for dual window and screen separation to a sink apparatus,
3 is a diagram schematically showing data transmission / reception between a sink device and a source device for displaying the screen separation support information,
4 is a diagram illustrating a situation in which a payload of the multi-audio sample packet is transmitted,
5 and 6 are diagrams showing transmission timings of a 3D audio signal,
7 is a block diagram illustrating the configuration of a data transmission / reception system according to an embodiment of the present invention.
8 is a block diagram illustrating the configuration of a data transmission apparatus according to an embodiment of the present invention.
9 is a block diagram showing the configuration of a data receiving apparatus according to an embodiment of the present invention.
10 is a block diagram illustrating a configuration of a data transmission / reception system according to another embodiment of the present invention.
11 is a block diagram showing the configuration of a data transmission apparatus according to another embodiment of the present invention.
12 is a block diagram showing the configuration of a data receiving apparatus according to another embodiment of the present invention;
13 is a block diagram showing the configuration of a data transmission / reception system according to another embodiment of the present invention;
FIG. 14 is a block diagram showing the configuration of a data transmission apparatus according to another embodiment of the present invention; FIG.
15 is a block diagram showing the configuration of a data receiving apparatus according to another embodiment of the present invention;
16A-16B illustrate various data transmission formats when transmitting quad-view video content in a 3D interlaced format;
17 is a flowchart of a data transmission method according to an embodiment of the present invention;
18 is a flowchart of a data receiving method according to an embodiment of the present invention;
19 is a flowchart of a data transmission method according to another embodiment of the present invention;
20 is a flowchart of a data receiving method according to another embodiment of the present invention;
21 is a flowchart of a data transmission method according to another embodiment of the present invention,
22 is a flowchart of a data receiving method according to another embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. The following terms are defined in consideration of the functions of the present invention, and may vary depending on the user, the operator, or the convention. Therefore, the definition should be based on the contents throughout this specification.

Since the present invention can be applied to various wired interface transmission standards such as HDMI (High Definition Multimedia Interface) and MHL (Mobile High-Definition Link) standards in the scope of the technical idea of the present invention, Interface transmission specifications.

The present specification refers to the following documents.

ITU-R BS.2159-4 (05/2012), home multi-channel sound technology and broadcasting applications (Multichannel sound technology in home and broadcasting applications)

SMPTE, SMPTE 2036-2: 2008, "UHDTV - Audio Channel and Audio Channel Mapping for Program Production", 2008

IEC 62574 ed 1.0, "Voice, Video and Multimedia Systems - General Channel Assignment of Multichannel Audio (General Channel Assignment of Multichannel Audio)", April 7, 2011

The following Table 1 briefly describes the terms used in this specification.

Term Definition MHL source An apparatus having an MHL output port. The MHL source uses a socket at each MHL output port and does not use a plug. MHL sink An apparatus having one or more MHL input ports. MHL sinks use sockets on each MHL input port and do not use plugs. 3D audio An audio system where speakers are located anywhere in 3D space. This does not include the height element, and typically places the horizontal 2D flat speakers. 3D audio uses the channel layout defined in ITU-R BS.2159-4 (Type B 10.2ch), SMPTE2036-2 (22.2ch), or IEC62574 (30.2ch). 3D audio also includes a downmixed audio stream defined in these standards, including nine or more audio channels. To avoid any doubt in this specification, 3D audio refers to a limited number of distinct channels, not audio based on objects. Multi Audio A collection of audio streams associated with one or more video streams. Multi-audio is transferred as a single-AV stream. For clarity in this specification, multi-audio does not imply the transmission of multiple audio streams via multi-AV-streaming. Stream A temporal set of digital data originating from an MHL source and terminating in one MHL sink. Streams are characterized by fixed frequency bandwidth conditions in the stream data, and by synchronization timestamps or time stamps. (Single-AV) stream A single stream in which all stream data is packetized to share the same packet stream ID.
Stream data in a single-AV stream can process one or more video streams, and one or more audio streams. Multi-AV stream A set of multiple single-AV streams with a unique packet stream ID assigned to each single-AV stream. Single-view View mode in which only a single video stream is displayed in MHL Sync. Multi-view A view mode in which two or more independent video streams are simultaneously displayed in the MHL Sync, allowing viewers to view only one video stream at any given time. For example, a multi-view video stream may be transmitted via a 3D video format in which an independent video stream is processed in left and right stereoscopic screens, respectively. window (Non-overlapping) portion of the video image displayed by the MHL Sync. The video image may be composed of two or more windows in which each window does not overlap with each other. Split Screen View options where two or more windows are tagged and identified by an MHL source (eg PIP TV viewing, TV quick preview, multi-screen games).

<Table 1? Term>

1 is a diagram showing a single audio stream and a multi-audio stream.

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

As shown in FIG. 1B, a multi-audio stream is a case in which a plurality of single AV streams are transmitted. In the multi-audio stream, there is a plurality of sets of single-AV streams in which a unique packet stream ID is assigned to each single AV stream. Video data of a plurality of single AV streams are mutually independent.

Each audio stream in a multi-audio stream transmits a maximum of two audio channels. And is associated with a single audio stream. For example, in single view mode, each audio is connected to a default video stream, and in dual view mode audio can be connected to the left image or the right image (or both). In addition, one or more of the following auxiliary audio options may be transmitted: Split-screen tagging, language indication, and audio indication for visually or hearing impaired.

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

Screen separation (or multi-window can be used with the same terminology) can be an optional configuration used with multi-audio. The Screen Separation mode represents a configuration in which the screen is separated from the sink device, tagging the audio stream and mapping it to a specific window.

2 is a diagram showing a source device transmitting multi-audio for a dual window and screen separation to a sink device.

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

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

The source device 310 transmits a Vender-Specific Infoframe, 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 the settings for each audio stream. It is associated with a video stream and can carry auxiliary audio information. The vendor-specific info frame indicates the multi-view type of the content being 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 (e.g., multiple languages, audio descriptions for visual impairments, or clean audio for audible disturbances). In this case, up to 16 audio streams can be transmitted simultaneously. This will be described in detail later.

TMDS signaling and encoding

Data platform packet

Packet Type Value Packet Type Section 0x00 Null 4.x 0x01 Audio Clock Regeneration (N / CTS) 4.x 0x02 Audio Sample 4.x 0x03 Content Mute Packet 4.x 0x04 3D Audio Sample 4.x 0x05 Multi-Audio Sample 4.x 0x06 3D Audio Metadata Packet 4.x 0x07 Multi-Audio Metadata Packet 4.x 0x80 + InfoFrame Type  InfoFrame 4.x

<Table 2 - Packet Types>

3D Audio Sample Packet

3D audio is defined as audio in which the speaker can be placed at a predetermined position for 3D audio specifications (e.g., 10.2ch, 22.2ch, 30.2ch, etc.) in 3D space. The 3D audio sample packet consists of one audio sample with 9 to 32 audio channels.

The 3D audio stream contains up to 32 audio channels (or more) and is transmitted over consecutive packets in the data island interval. Each packet includes up to eight audio channels. The configuration of the subpackets is determined by the sequence number and 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 needed to accurately identify the packet order.

The different header fields and subpacket structure are consistent with the audio sample packets shown in the MHL 2.0 specification.

Byte \ Bit # 7 6 5 4 3 2 One 0 HB0 0 0 0 0 0 One 0 0 HB1 0 0 sequence_number sample present.sp3 sample present.sp2 sample present.sp1 sample present.sp0 HB2 B.3 B.2 B.1 B.0 sample flat.sp3 sample flat.sp2 sample flat.sp1 sample flat.sp0 PB0 L.11 ... ... ... ... ... ... L.4 PB1 L.19 ... ... ... ... ... ... L.12 PB2 L.27 ... ... ... ... ... ... L.20 PB3 R.11 ... ... R.4 PB4 R.19 ... ... ... ... ... ... R.12 PB5 R.27 ... ... ... ... ... ... R.20 PB6 P _R C _R V _R P _L C _L U _L V _L PB7 L.11 ... ... ... ... ... ... L.4 PB8 L.19 ... ... ... ... ... ... L.12 PB9 L.27 ... ... ... ... ... ... L.20 PB10 R.11 ... ... R.4 PB11 R.19 ... ... ... ... ... ... R.12 PB12 R.27 ... ... ... ... ... ... R.20 PB13 P _R C _R V _R P _L C _L U _L V _L PB14 L.11 ... ... ... ... ... ... L.4 PB15 L.19 ... ... ... ... ... ... L.12 PB16 L.27 ... ... ... ... ... ... L.20 PB17 R.11 ... ... R.4 PB18 R.19 ... ... ... ... ... ... R.12 PB19 R.27 ... ... ... ... ... ... R.20 PB20 P _R C _R V _R P _L C _L U _L V _L PB21 L.11 ... ... ... ... ... ... L.4 PB22 L.19 ... ... ... ... ... ... L.12 PB23 L.27 ... ... ... ... ... ... L.20 PB24 R.11 ... ... R.4 PB25 R.19 ... ... ... ... ... ... R.12 PB26 R.27 ... ... ... ... ... ... R.20 PB27 P _R C _R V _R P _L C _L U _L V _L

<Table 3 - 3D Audio Sample Packet>

Multi Audio Sample Packet

A multi-audio sample packet may include four audio samples with each audio sample independently associated with the audio stream. When the source device simultaneously transmits four or more independent audio streams, these consecutive audio streams are transmitted by a subsequent series of multi-audio sample packets. The sequence number (sequence_number) defined in the packet header identifies each multi-audio sample packet and indicates the order of the current packet within the alignment of the packets. The configuration of the subpackets is determined by the sequence number and sample present bits in the header. This is explained in detail in multi-audio data packetization.

For each sub-packet (or audio stream), the descriptor field in the Multi-Audio Metadata Packet includes a view mode (i.e., single-view or multi-view) (E.g., screen separation tagging, language code, audio for visual impairments, etc.). These are explained in detail later.

Sequence number field (sequence_number): indicates the sequence number of the current multi-audio sample packet when there are four or more audio streams to be transmitted from the source apparatus to the sink apparatus. If this field is set to 0, then the packet may contain the first four audio streams in each of these subpackets. If this field is set to 1, then the packet may contain a second set of four audio streams each in the corresponding subpackets. 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 in subpacket 0 with a sequence number of 0 is designated as a default audio stream.

Stream Present field (stream_presnt.spX): Indicates whether subpacket X contains audio sample (s) of stream X or not.

Stream Flat Field (stream_flat.spX): Indicates whether subpacket X represents a "flatline" sample of stream X or not. Valid only when stream_present.spX is set.

Other header fields and subpacket structure match the audio sample packet seen in the MHL 2.0 specification.

Byte \ Bit # 7 6 5 4 3 2 One 0 HB0 0 0 0 0 0 One 0 One HB1 0 0 sequence_number stream present.sp3 stream present.sp2 stream present.sp1 stream present.sp0 HB2 B.3 B.2 B.1 B.0 stream flat.sp3 stream flat.sp2 stream flat.sp1 stream flat.sp0 PB0 to PB6 Audio sample data for audio stream N + 0 PB7 to PB13 Audio sample data for audio stream N + 1 PB14 to PB20 Audio sample data for audio stream N + 2 PB21 to PB27 Audio sample data for audio stream N + 3

<Table 4 - Mutli Audio Sample Packet>

4 is a diagram illustrating a state in which 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 two bits, up to 16 audio streams can be carried.

3D audio metadata packet

Ancillary data describing active 3D audio data is transmitted using 3D audio metadata packets. If the source device is capable of transmitting 3D audio sample packets, then the source device always transmits the correct 3D audio metadata packet, once per at least two video fields.

The following shows the 3D audio metadata packet.

Byte \ Bit # 7 6 5 4 3 2 One 0 HB0 0 0 0 0 0 One One One HB1 0 0 0 0 0 0 0 0 HB2 0 0 0 0 0 0 0 0 PB0 0 0 0 3D_CC PB1 0 0 0 0 3D_CAST PB2 3D_CA PB3 to PB27
Reserved

<Table 5 - 3D Audio Metadata Packet>

3D_CC [4: 0] Audio Channel Count 0b00000 Refer to Stream Header 0b00001 9 channels 0b00010 10 channels ... ... 0b11000 32 channels 0b11001 ~ 0b11111 Reserved

<Table 6 - 3D Audio Channel Count (3D_CC) field>

3D_CAST [3: 0] Description 0b0000 Reserved 0b0001 Up to 10.2 channels
Based on ITU-R BS. 2159-4 (Type B, 10.2ch) 0b0010 Up to 22.2 channels
Based on SMPTE 2036-2 0b0011 Up to 30.2 channels
Based on IEC 62574 / Ed.1 0b0100 ~ 0b1111 Reserved

<Table 7 - 3D_CAST (3D Audio Channel Allocation Standard Type) field>

3D_CA
(hex) Channel Number 12 11 10 9 8 7 6 5 4 3 2 One 0x00 TpFC LFE2 TpFR TpFL BR BL RS LS FC LFE1 FR FL 0x01 Reserved ... 0xFF

<Table 8 - 3D Audio Channel / Speaker Allocation (3D_CA) field (3D_CAST = 0x01 (up to 10.2ch))>

3D_CA
(hex) Channel Number 12 11 10 9 8 7 6 5 4 3 2 One 0x00 TpFC LFE2 TpFR TpFL BR BL SiR SiL FC LFE1 FR FL 0x01 TpFC LFE2 TpFR TpFL BR BL SiR SiL FC LFE1 FR FL 0x02 Reserved ... 0xFF 3D_CA
(hex) Channel Number 24 23 22 21 20 19 18 17 16 15 14 13 0x00 - - - - - - - - - - - - 0x01 BtFC BtFR BtFL TpC TpSiR TpSiL TpBC TpBR TpBL BC FRC FLC 0x02 Reserved ... 0xFF

<Table 9 - 3D Audio Channel / Speaker Allocation (3D_CA) field (3D_CAST = 0x02 (up to 22.2ch))>

3D_CA
(hex) Channel Number 12 11 10 9 8 7 6 5 4 3 2 One 0x00 TpFC LFE2 TpFR TpFL BR BL SiR SiL FC LFE1 FR FL 0x01 TpFC LFE2 TpFR TpFL BR BL SiR SiL FC LFE1 FR FL 0x02 TpFC LFE2 TpFR TpFL BR BL SiR SiL FC LFE1 FR FL 0x03 Reserved ... 0xFF 3D_CA
(hex) Channel Number 24 23 22 21 20 19 18 17 16 15 14 13 0x00 - - - - - - - - - - - - 0x01 BtFC BtFR BtFL TpC TpSiR TpSiL TpBC TpBR TpBL BC FRC FLC 0x02 BtFC BtFR BtFL TpC TpSiR TpSiL TpBC TpBR TpBL BC FRC FLC 0x03 Reserved ... 0xFF 3D_CA
(hex) Channel Number 32 31 30 29 28 27 26 25 0x00 - - - - - - - - 0x01 - - - - - - - - 0x02 TpRS TpLS RSd LSd RS LS FRW FLW 0x03 Reserved ... 0xFF

<Table 10 - 3D Audio Channel / Speaker Allocation (3D_CA) field (3D_CAST = 0x03 (up to 30.2ch))>

Multi-Audio Metadata Packet

Supplementary data describing the active multi-audio stream is transmitted using the multi-audio metadata packet. This packet is used to describe the view type and auxiliary audio options for each audio stream being transferred from the multi-audio sample packets.

If the source device is capable of transmitting multi-audio sample packets, the source device always transmits correct multi-stream audio metadata packets, once for at least two video fields.

The following shows a multi-audio metadata packet.

Byte \ Bit # 7 6 5 4 3 2 One 0 HB0 0 0 0 0 One 0 0 0 HB1 MA_View_Type Sequence_Number Num_Audio_Streams HB2 SC_
Valid 000 0000
(or Split_Screen_Config, if SC_Valid = 1) PB0 to PB6 MA_Descriptor_0 PB7 to PB13 MA_Descriptor_1 PB14 to PB20 MA_Descriptor_2 PB21 to PB27 MA_Descriptor_3

<Table 11 - Multi-Audio Metadata Packet>

View Type Field (MA_View_Type): Represents the associated view mode of a multi-audio stream, such as single view or multi-view. See the table below.

Sequence number field (Sequence_Number): This indicates 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 links each multi-audio metadata packet with a multi-audio sample packet having the same sequence number.

Num_Audio_Streams: indicates the total number of audio streams transmitted by the multi-audio sample packets.

Screen Separation Effective Field (SC_Valid): If set to 1, screen separation tagging is supported, and the Screen Separation Configuration field is refined in the next 7 bits. If set to 0, the screen splitting tagging is unsupported or unspecified, and the next 7 bits are left for other uses.

Screen Split Type field (Split_Screen_Config): Indicates the type of screen separation related to the audio stream represented by the current descriptor. The selectable screen separation types are listed in Table 13 below. This field is valid only when SC_Enabled = 1.

Multi Audio Descriptor Field (MA_Descriptor_X): Indicates the characteristics of the audio stream transmitted by subpacket X of the corresponding multi-audio sample packet. Table 13 shows the detailed structure of the multi-audio descriptor.

MA_View_Type [1: 0] Description 0b00 Unspecified or single view mode 0b01 Multi-View mode 0b10 Reserved 0b11 Reserved

<Table 12 - Multi-Audio Type field>

Split_Screen_Config [6: 0] Description 0b000 0000 Unspecified or single view mode 0b000 0001

Split mode 1 (split by 2)

0b000 0010 Split mode 2 (split by 2)

0b000 0011 Split mode 3 (split by 2)

0b000 0100 Split mode 4 (split by 3)

0b000 0101 Split mode 5 (split by 3)

0b000 0110 Split mode 6 (split by 3)

0b000 0111 Split mode 7 (split by 3)

0b000 1000 Split mode 8 (split by 3)

0b000 1001 Split mode 9 (split by 3)

0b000 1010 Split mode 10 (split by 4)

0b000 1011 Split mode 11 (split by 4)

0b000 1100 ... (TBD) 0bxxx xxxx ~ 0b111 1111 Reserved

<Table 13 - Split_Screen_Config field>

The following table shows the multi-audio descriptors.

Byte \ Bit # 7 6 5 4 3 2 One 0 PB N + 0 Split_Screen_Tag 0 0 Associated_View_ID PB N + 1 LC_present 0 Mixed_ Audio SAT_ present Suppl_Audio_Type PB N + 2
Language_Code (3 Bytes)
PB N + 3 PB N + 4 PB N + 5 0 0 0 0 0 0 0 0 PB N + 6 0 0 0 0 0 0 0 0

<Table 14 - Multi-Audio Descriptor>

Screen Split Tag field (Split_Screen_Tag): Indicates a specific window (as defined by the split screen configuration) associated with the audio stream currently represented by the multi-audio descriptor. Details are shown in Table 16 below. This field is valid only when SC_valid = 1, otherwise the sink device ignores this field.

Associated View Identification field (Associated_View_ID): indicates 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). Details are shown in Table 15 below.

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

Mixed Audio field (Mixed_Audio): If this field is set to 1, the audio stream contains a premixed stream of general audio and auxiliary audio, as indicated by the auxiliary audio type field (Suppl_Audio_Type).

SAT Present field (SAT_present): If this field is set to 1, the current descriptor contains a valid auxiliary audio type field (Suppl_Audio_Type) in the next four bits.

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

Language Code field (Language_Code): Represents the language code defined by ISO 639 of the audio stream. This field is valid only when the effective language code field (LC_present) is set to 1; otherwise, the sink device ignores this field.

MA_View_Type Associated_View_ID [2: 0] Description 0b00 0b00 Unspecified or default view 0b01 0b00 Left stereoscopic picture of 3D field 0b01 Right stereoscopic picture of 3D field 0b10 ~ 0b11 Reserved

<Table 15 - Associated View Identifier field>

Split_Screen_Tag [3: 0] Description 0b0000 Window 1 0b0001 Window 2 0b0010 Window 3 ... ... 0b1111 Window 16

<Table 16 - Split-Screen Tag field>

Suppl_Audio_Type [3: 0] Description 0b0000 Unspecified or general Audio 0b0001 Narrated Audio for the visually impaired 0b0010 Spoken subtitles for the visually impaired 0b0011 Clean audio for the hearing impaired 0b0100 Emergency audio channel 0b0101 ~ 0b1111 Reserved

<Table 17 - Supplementary Audio Feature field>

Active Multi-Audio Mode Indicator

The source device uses a Vendor-Specific Infoframe (VSIF) to indicate to the sink device the exact view mode to be transmitted. VSIF is structured as shown in Table 18.

Byte \ Bit # 7 6 5 4 3 2 One 0 HB0 InfoFrame_Type = 0x81 HB1 InfoFrame_version = 0x01 HB2 0 0 0 InfoFrame_length PB0 Checksum PB1 24-bit IEEE-assigned Organizationally Unique Identifier (OUI)
0x7CA61D PB2 PB3 PB4 Reserved MHL_3D_FMT_TYPE MHL_VID_FMT PB5 TBD? (for High-End Video Mode) PB6 0 0 0 0 0 MHL_MULTI_VIEW PB7 ... PB26 Reserved PB27 Reserved

<Table 18 - Vendor-Specific InfoFrame Packet>

MHL Multi-view field (MHL_MULTI_VIEW): Indicates which Multi-view mode is transmitted. A detailed description is shown in Table 19.

MHL_MULTI_VIEW [2: 0] Description 0b000 Unspecified or Single-View mode 0b001 Dual-View mode 0b010 Triple-View mode 0b011 Quad-View mode 0b100 ~ 0b111 Reserved

<Table 19 - MHL_MULTI_VIEW field>

video

3D video descriptor for 3D support

Bit 7 6 5 4 3 2 One 0 VDI_L Reserved MV_
SUPP LR_
SUPP TB_
SUPP FS_
SUPP VDI_H Reserved

<Table 20 - 3D Video Descriptor Data Structure>

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

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

audio

Channel / speaker assignment

If the sink device is capable of receiving 3D audio, the 3D channel speaker allocation descriptor described in Table 38 to Table 40 is used to indicate the configuration of the attached speakers. Indicators of the current speaker allocation for 3D audio transmitted from the source device are handled in the 3D CA field of the 3D audio metadata packet. For a detailed description of the 3D CA field, see Tables 27 to 29.

3D Audio Data Packetization

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

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

Packet # 시퀀스 번호 Num Channels Sample Subpkt 0 Subpkt 1 Subpkt 2 Subpkt 3 0 0 12 One Chnl 1,2 (Sample 0) Chnl 3,4 (Sample 0) Chnl 5,6 (Sample 0) Chnl 7,8 (Sample 0) One One Chnl 9,10 (Sample 0) Chnl 11, 12 (Sample 0) Empty Empty

<Table 21 - 3D Audio Sample Packet Layout for 12 channels>

Packet # 시퀀스 번호 Num Channels Sample Subpkt 0 Subpkt 1 Subpkt 2 Subpkt 3 0 0 24 One Chnl 1,2 (Sample 0) Chnl 3,4 (Sample 0) Chnl 5,6 (Sample 0) Chnl 7,8 (Sample 0) One One Chnl 9,10 (Sample 0) Chnl 11, 12 (Sample 0) Chnl 13,14 (Sample 0) Chnl 15,16 (Sample 0) 2 2 Chnl 17,18 (Sample 0) Chnl 19,20 (Sample 0) Chnl 21, 22 (Sample 0) Chnl 23,24 (Sample 0)

<Table 22 - 3D Audio Sample Packet Layout for 24 channels>

Packet # 시퀀스 번호 Num Channels Sample Subpkt 0 Subpkt 1 Subpkt 2 Subpkt 3 0 0 32
(Max) One Chnl 1,2 (Sample 0) Chnl 3,4 (Sample 0) Chnl 5,6 (Sample 0) Chnl 7,8 (Sample 0) One One Chnl 9,10 (Sample 0) Chnl 11, 12 (Sample 0) Chnl 13,14 (Sample 0) Chnl 15,16 (Sample 0) 2 2 Chnl 17,18 (Sample 0) Chnl 19,20 (Sample 0) Chnl 21, 22 (Sample 0) Chnl 23,24 (Sample 0) 3 3 Chnl 25,26 (Sample 0) Chnl 27,28 (Sample 0) Chnl 29,30 (Sample 0) Chnl 31,32 (Sample 0)

<Table 23 - 3D Audio Sample Packet Layout for 32 channels>

There are four sample_present bits in one, 3D audio sample packet header for each subpacket. Each indicating that one subpacket contains 3D audio samples. In addition, there are four sample flats (sample_flat.spX) bits to set if there is no useful audio data available at the source device during the time period represented by the sample. This can occur during sample rate changes or transient stream interruptions.

Subsequent 3D audio sample packets can be used to process one 3D audio sample, including 9 to 32 channels of L-PCM audio (i.e., 5 to 16 IEC60958 frames).

The first packet of the 3D audio sample is filled with eight audio channels and has a sequence number field set to zero. The sequence number increases by one for each additional packet in the same 3D audio sample. The last packet contains eight or fewer audio channels depending on the total number of channels of the 3D audio sample.

There are only 5 valid sample_present bits for a 3D audio sample packet.

SP0 SP1 SP1 SP3 Description 0 0 0 0 No Subpackets contain parts of the audio sample. One 0 0 0 Only Subpacket 0 contains one part of the audio sample. One One 0 0 Subpackets 0 and 1 contain two contiguous parts of the audio sample. One One One 0 Subpackets 0, 1 and 2 contain three contiguous parts of the audio sample. One One One One Subpackets 0, 1, 2 and 3 contain four contiguous parts of the audio sample.

<Table 24 - Valid Sample_Present Bit Configurations for 3D Audio transmission>

5 and 6 are diagrams showing transmission timings of 3D audio signals.

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

Multi-Audio Data Packetization

The MHL allows the MHL source device to transmit audio streams simultaneously for single-AV streaming. Multiple audio streams are associated with either single view or multi-view video streaming (e.g., dual view gaming with different audio per view). Auxiliary audio modes may represent screen separation tagging (i.e., other parts of the screen are tagged and associated with their own audio streams), language codes, or audio for a visually / auditory handicapped person. Each audio stream is associated with one view mode and comprises a maximum of two audio channels.

Each subpacket of a multi-stream audio sample packet may contain zero or "frames" of IEC60958 or IEC61937 "block" defined as one IEC60958.

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

Tables 25 and 26 show examples of multi-audio sample packets and multi-audio metadata packet layout when the MHL source device transmits four audio streams with 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 layout when the MHL source device transmits eight audio streams with dual-view video streaming. The multi-audio metadata packet describes the characteristics (associated view, auxiliary information, language) of each audio stream.

Tables 29 and 30 show examples of a multi-audio sample packet and a multi-audio metadata packet layout when an MHL source device transmits six audio streams with a screen-separation tagging option to enable single-view video streaming.

Packet # 시퀀스 번호 Num Streams Subpkt 0 Subpkt 1 Subpkt 2 Subpkt 3 0 0 4 Stream 1 (Channel 1,2) Stream 2 (Channel 1,2) Stream 3 (Channel 1,2) Stream 4 (Channel 1,2)

<Table 25 - Example of Multi-Audio Sample Packet Layout with 4 audio streams in single view mode>

Packet # 시퀀스 번호 Num Streams Subpkt 0 Subpkt 1 Subpkt 2 Subpkt 3 0 0 4 English
nomal Korean
normal Japanese
Audio for VI Spanish
Audio for HI

<Table 26 - Example of Multi-Audio Metadata Packet Layout (related to the packet in Table 25)>

Audio for HI: Audio stream for auditory disorders

Audio for VI: Audio stream for visual impairment

Packet # 시퀀스 번호 Num Streams Subpkt 0 Subpkt 1 Subpkt 2 Subpkt 3 0 0 8 Stream 1 (Channel 1,2) Stream 2 (Channel 1,2) Stream 3 (Channel 1,2) Stream 4 (Channel 1,2) One One Stream 5 (Channel 1,2) Stream 6 (Channel 1,2) Stream 7 (Channel 1,2) Stream 8 (Channel 1,2)

<Table 27 - Example of Multi-Audio Sample Packet Layout with 8 audio streams in dual view mode>

Packet # 시퀀스 번호 Num Streams Subpkt 0 Subpkt 1 Subpkt 2 Subpkt 3 0 0 8 Left View
English
nomal Left View
Korean
normal Left View
Spanish
normal Left View
Spanish
Audio for HI One One Left View
English
Audio for VI Right View
Koean
Audio for VI Right View
Japanese
Audio for VI Right View
Chinese
Audio for VI

<Table 28 - Example of Multi-Audio Metadata Packet Layout (related to the packet in Table 27)>

Audio for HI: Audio stream for auditory disorders

Audio for VI: Audio stream for visual impairment

Packet # 시퀀스 번호 Num Streams Subpkt 0 Subpkt 1 Subpkt 2 Subpkt 3 0 0 6 Stream 1 (Channel 1,2) Stream 2 (Channel 1,2) Stream 3 (Channel 1,2) Stream 4 (Channel 1,2) One One Stream 5 (Channel 1,2) Stream 6 (Channel 1,2) - -

<Table 29 - Example of Multi-Audio Sample Packet Layout with 6 audio streams with Split-Screen tagging (in single view) mode>

Packet # 시퀀스 번호 Num Streams Subpkt 0 Subpkt 1 Subpkt 2 Subpkt 3 0 0 6 Window 1
English
normal Window 2
Korean
normal Window 3
Spanish
normal Window 4
Japanese
normal One One Window 5
English
Audio for HI Window 6
English
Audio for VI - -

<Table 30 - Example of Multi-Audio Metadata Packet Layout (related to the packet in Table 29)>

Audio for HI: Audio stream for auditory disorders

Audio for VI: Audio stream for visual impairment

Packet 3D audio metadata

Each time an active 3D audio stream is transmitted, the correct 3D audio metadata packet is transmitted at least once per video field.

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 InfoFrame, the correct, correct 3D audio metadata packet is sent to the first affected non-silent ) &Lt; / RTI &gt; audio sample. Primarily, this happens just before the first affected audio sample is sent.

The transmission of 3D audio metadata packets can occur at any time within a data platform segment including horizontal and vertical blanking intervals.

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, the correct multi-audio metadata packet is transmitted at least once per video field.

When there is a change in the multi-audio stream that can be represented by a multi-audio metadata packet and an audio info frame at the start of a new multi-audio stream, the corrected correct multi- lt; RTI ID = 0.0 &gt; non-silent &lt; / RTI &gt; audio samples. Primarily, this happens just before the first affected audio sample is sent.

Multi-audio metadata packet transmission may occur at any time within a data platform segment that includes horizontal and vertical blanking intervals.

Enable WRITE_BURST for 3D / multi-audio support

Support for 3D audio mode is indicated using a series of WRITE_BURST moves formatted as shown in Tables 30 and 31.

Offset Symbol Value Description Notes 0x00 BURST_ID_H High-order byte of Burst_ID 0x01 BURST_ID_L Low-order byte of Burst_ID 0x02 CHECK_SUM Checksum for WRITE_BURST 0x03 TOT_DESC Total Descriptors in Sequence 0x04 SEQ Sequence Index 0x05 NUM_DESC Number of Descriptors in this burst 0x06 AUD_DESC 1 Indicates the audio descriptor for 3D Audio 0x07 0x08 0x09 0x0A AUD_DESC 2 Indicates the audio descriptor for 3D Audio 0x0B 0x0C 0x0D 0x0E TBD TBD 0x0F TBD TBD

<Table 31 - MHL 3D Audio Descriptors (3D_AD) in WRITE_BURST>

Byte \ Bit # 7 6 5 4 3 2 One 0 One 0 0 0 0 Audio Format Code = 0001b 2 0 0 0 Max Number of channels - 1 3 0 192 kHz 176.4 kHz 96 kHz 88.2 kHz 48 kHz 44.1 kHz 32 kHz 4 0 0 0 0 0 24 bit 20 bits 16 bit

<Table 32 - 3D Audio Descriptor for Audio Format Code = 1 (LPCM)>

Byte \ Bit # 7 6 5 4 3 2 One 0 One 0 0 0 0 Audio Format Code 2 0 0 0 Max Number of channels - 1 3 0 192 kHz 176.4 kHz 96 kHz 88.2 kHz 48 kHz 44.1 kHz 32 kHz 4 Maximum bit rate divided by 8kHz

<Table 33 -3D Audio Descriptor for Audio Format Codes 2 to 8>

Byte \ Bit # 7 6 5 4 3 2 One 0 One 0 0 0 0 Audio Format Code 2 0 0 0 Max Number of channels - 1 3 0 192 kHz 176.4 kHz 96 kHz 88.2 kHz 48 kHz 44.1 kHz 32 kHz 4 Audio Format Code dependent value

<Table 34 - 3D Audio Descriptor for Audio Format Codes 9 to 13>

Byte \ Bit # 7 6 5 4 3 2 One 0 One 0 0 0 0 Audio Format Code = 1110b 2 0 0 0 Max Number of channels - 1 3 0 192 kHz 176.4 kHz 96 kHz 88.2 kHz 48 kHz 44.1 kHz 32 kHz 4 Reserved (0) Profile

<Table 35 - 3D Audio Descriptor for Audio Format Code 14 (WMA Pro)>

Byte \ Bit # 7 6 5 4 3 2 One 0 One 0 0 0 0 Audio Format Code = 1111b 2 0 0 0 Max Number of channels - 1 3 0 192 kHz 176.4 kHz 96 kHz 88.2 kHz 48 kHz 44.1 kHz 32 kHz 4 Audio Format Code Extension 0 0 0

<Table 36 - 3D Audio Descriptor for Audio Format Code 15 (extension)>

Offset Symbol Value Description Notes 0x00 BURST_ID_H High-order byte of Burst_ID 0x01 BURST_ID_L Low-order byte of Burst_ID 0x02 CHECK_SUM Checksum for WRITE_BURST 0x03 CSA_DESC Indicates the channel / speaker allocation descriptor for 3D Audio 0x04 0x05 0x06 0x07 TBD TBD 0x08 TBD TBD 0x09 TBD TBD 0x0A TBD TBD 0x0B TBD TBD 0x0C TBD TBD 0x0D TBD TBD 0x0E TBD TBD 0x0F TBD TBD

<Table 37 - MHL 3D Channel / Speaker Allocation Descriptor (3D_CSAD) in WRITE_BURST>

Byte \ Bit # 7 6 5 4 3 2 One 0 PB1 FLW /
FRW BLC /
BRC FLC /
FRC BC BL / BR FC LFE1 FL / FR PB2 TpSiL / TpSiR SiL / SiR TpBC LFE2 LS / RS TpFC TpC TpFL /
TpFR PB3 0 0 0 LSd /
LRd TpLS /
TpRS BtFL /
BtFR BtFC TpBL /
TpBR PB4 3D_CAST (= 0x01) 0 0 0 0

<Table 38 - 3D Channel Speaker Allocation Descriptor for 10.2channel>

Bold text indicates the assigned speakers associated with 10.2 channels.

Byte \ Bit # 7 6 5 4 3 2 One 0 PB1 FLW /
FRW BLC /
BRC FLC /
FRC BC BL / BR FC LFE1 FL / FR PB2 TpSiL / TpSiR SiL / SiR TpBC LFE2 LS / RS TpFC TpC TpFL /
TpFR PB3 0 0 0 LSd /
LRd TpLS /
TpRS BtFL /
BtFR BtFC TpBL /
TpBR PB4 3D_CAST (= 0x02) 0 0 0 0

<Table 39 - 3D Channel Speaker Allocation Descriptor for 22.2channel>

Bold text indicates a specific speaker associated with the 22.2 channel.

Byte \ Bit # 7 6 5 4 3 2 One 0 PB1 FLW /
FRW BLC /
BRC FLC /
FRC BC BL / BR FC LFE1 FL / FR PB2 TpSiL / TpSiR SiL / SiR TpBC LFE2 LS / RS TpFC TpC TpFL /
TpFR PB3 0 0 0 LSd /
LRd TpLS /
TpRS BtFL /
BtFR BtFC TpBL /
TpBR PB4 3D_CAST (= 0x03) 0 0 0 0

<Table 40 - 3D Channel Speaker Allocation Descriptor for 30.2 channel>

Bold indicates a specific speaker associated with 30.2 channels.

3D_CAST Description 0x0 Reserved 0x1 Up to 10.2 channels
Based on ITU-R BS. 2159-4 (Type B, 10.2ch) 0x2 Up to 22.2 channels
Based on SMPTE 2036-2 0x3 Up to 30.2 channels
Based on IEC 62574 / Ed.1Reserved 0x4 Reserved ... 0xF

<Table 41 - 3D_CAST (3D Audio Channel Allocation Standard Type) field>

Link Control Bus

Device register change interrupt (Device register change interrupt)

Register Name Offset 7 6 5 4 3 2 One 0 RCHANGE_INT 0x20 Bit Name Source Sink Notes 0 DCAP_CHG X X ... One One DSCR_CHG X X ... 2 2 REQ_WRT X X ... 2 3 GRT_WRT X X ... 2 4 3D_REQ X X ... 3 5 3D_AUD_REQ X X Request for 3D Audio Information 4 6-7

<Table 42 - Register Change Interrupt Register Details>

3D_AUD_REQ is used by the MHL source device to request 3D audio support information from the MHL sink device. Refer to the MHL specification 6.14.

Burst_ID Code

Symbol Value Description Notes 3D_VIC 0x0010 Indicates Video Index Codes for 3D One 3D_DTD 0x0011 Indicates Detailed Timing Descriptors for 3D One 3D_AD 0x0101 Indicates the 3D Audio Descriptors for 3D Audio 2 3D_CSAD 0x0110 Indicates the 3D Channel / Speaker Allocation Descriptor for 3D Audio 2

<Table 43 - BURST_ID Codes>

3D_AD and 3D_CSAD are used by the MHL sink device to indicate support for audio extension. See MHL Specification 7.XX.

Control and Configuration

Extended Device Capability Register (Extended Device Capability Register)

The sink device may provide an extended device capability register to the source device. In other words, the source device can read the extended device capability register of the sink device.

The address 0x85 of the device capability register extended in the MHL specification can be used to indicate the multi-audio mode supported by the sink device, as shown in the table below.

Address Extended Device Capability Register Name Definition 0x80 ECBUS_SPEEDS  Frequencies 0x81 TMDS_SPEEDS TMDS Frequencies 0x82 ECBUS_TDM_SUPPORTED Number of supported eCBUS TDM channels. 0x83 ECBUS_USB_ROLES Indicates USB roles supported by this device. 0x84 CABLE_REPORT Indicates the type of cable detected at Sink. 0x85 MULTI_AUD_MODE Indicates the Multi-Audio modes supported by Sink.

< Table 44 - Extended Device Capability Register Name and Definition>

Multi Audio Mode (Multi-Audio Mode)

Each sink device can be displayed in a multi-audio mode (MULTI_AUD_MODE) for registering a specific multi-audio mode supported.

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

Register Name Offset 7 6 5 4 3 2 One 0 MULTI_AUD_MODE 0x85 Reserved SUPP_
AUD_
LANG SUPP_
AUD_
SUPPL SUPP_
AUD_
SPLIT SUPP_
AUD_
MV Bit Name Notes 0 SUPP_AUD_MV Supports Multi-View Multi-Audio mode One One SUPP_AUD_SC Supports Split-Screen tagging 2 SUPP_AUD_SUPPL Supports Supplementary Audio mode (e.g., audio for visually / hearing impaired) 3 SUPP_AUD_LANG Supports Multi-language Audio 7: 4 Reserved

<Table 45 - MULTI_AUD_MODE Register Details>

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

Multi-Stream Audio

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

The source apparatus of the present invention can simultaneously transmit four audio streams. For multi-stream Audio Sample Packets, all audio streams share an Audio Infoframe.

The wired interface according to various embodiments of the present invention may add support for single-view video streaming (e.g., supporting multi-lingual or audio for the visually impaired). This can be done by modifying the Audio Metadata Packet or by modifying the HDMI Audio Data Block.

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

<Table 46 -Overview of Supports of Multi-stream Audio for single view>

scenario

The table below shows possible scenarios.

<Table 47 - Scenarios of Multi-stream Audio Sample Packet>

For a multi-stream audio sample packet with four 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 contains And may include an audio description signal for the blind.

2) In the case of supporting two languages in the single view, two audio signal streams in a supported language and an audio description corresponding thereto are transmitted together. For example, when English and Korean are supported, stream 0 is Korean normal audio signal, stream 1 is Korean audio description signal for blind, stream 2 is English normal audio signal, stream 3 is English audio description Signals, respectively.

3) Two audio description signals may be transmitted for one visually impaired person in a single view with one language audio signal stream and different languages for this. For example, stream 0 may include a Korean or English normal audio signal, stream 1 may include a Korean audio description signal for a blind person, and stream 2 may include an English audio description signal for a blind person, respectively.

4) The source device may send an audio signal for multi-view. When dual view is supported, the most basic form is to transmit the audio signal for each view in one transport stream. In the case of a dual view, it includes independent first and second views, each providing independent content.

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

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

7) One stream may be used to transmit a common audio signal. That is, the common audio signal stream for the first view and the second view, the first view only audio stream, and the second view only audio stream, respectively, can be transmitted. In this case, the receiving end muxes and outputs the common audio stream and the dedicated audio stream. These scenarios can be applied to games. For example, stream 0 is a common audio signal (e.g., background sound, progressive voice, etc.) for the first and second views, stream 1 is a dedicated audio signal for the first view, stream 2 is a second And may include a dedicated audio signal for the view.

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

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

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

The data receiving apparatus 200-1 receives the packet including the first subpacket and the second subpacket from the data transmission apparatus 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 apparatus 100-1 and the data reception apparatus 200-1 will be described in more detail.

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

Referring to FIG. 8, a data transmission apparatus 100-1 according to an embodiment of the present invention includes a packet generation unit 110 and a transmission unit 120. FIG.

The packet generation unit 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 transmitting unit 120 transmits the generated packet to the data receiving apparatus 200-1.

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

In addition, the first subpacket and the second subpacket may include audio data in a different language.

In addition, the first subpacket may include audio data corresponding to the audio description of the second subpacket.

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

At this time, the audio data included in the first subpacket 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 audio data included in the packet may be common audio data for the first content and the second content.

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

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

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

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

The parsing unit 220 parses the received first subpacket and the second subpacket.

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

Alternatively, the first subpacket may include audio data corresponding to the audio description of the second subpacket.

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

At this time, the audio data included in the first subpacket 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 audio data included in the packet may be common audio data for the first content and the second content.

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

Audio Metadata Packet

The source device sends an audio metadata packet to the sink device to indicate the audio specification to be transmitted. At this time, the header of the audio metadata packet has the following structure.

<Table 48 - Audio Metadata Packet Header>

Each field is described as follows.

If the 3D audio field (3D_AUDIO) [1 bit]: 3D_AUDIO = 1, the audio metadata packet includes 3D audio channel count (3D_CC field, see table below) and channel / : Audio Channel Allocation Standard Type) field (see table below). When the source transmits a 3D audio packet, this field will be set to one.

View Count Field (NUM_VIEWS) [2bits]: 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 if 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. If NUM_AUDIO_STR = 01, 10, or 11, the Audio Metadata Packet includes up to four audio metadata descriptors, each corresponding to an audio stream.

<Table 49 - Valid Combinations>

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

<Table 50? Audio Metadata Packet Payload (3D_AUDIO == 1)>

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

Table 51 shows the audio channel according to the 3D_CC value, and Table 52 shows the audio channel allocation standard type according to the ACAST field value.

3D_CC4 3D_CC3 3D_CC2 3D_CC1 3D_CC0 Audio Channel Count 0 0 0 0 0 Refer to Stream Header 0 0 0 0 One 2 channels 0 0 0 One 0 3 channels 0 0 0 One One 4 channels 0 0 One 0 0 5 channels 0 0 One 0 One 6 channels 0 0 One One 0 7 channels 0 0 One One One 8 channels 0 One 0 0 0 9 channels 0 One 0 0 One 10 channels 0 One 0 One 0 11 channels 0 One 0 One One 12 channels - - - - - One One One One One 32 channels

<Table 51 3D_CC field>

ACAT3 ACAT2 ACAT1 ACAT0 Description 0 0 0 0 Reserved 0 0 0 One Refer to 10 2 channels (TTA Standard) 0 0 One 0 Refer to 22 2 channels (SMPTE2036-2) 0 0 One One Refer to 30 2 channels (IEC62574 / Ed 1) 0 One 0 0 reserved One One One One

<Table 52 - Audio Channel Allocation Standard Type field>

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

<Table 53? Audio Metadata Packet Payload (3D_AUDIO == 0)>

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

<Table 54 - Audio Metadata Descriptor (for each subpacket X in multi-stream ASP)>

Each field is described below.

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

Multiview_Left [1bit]: If Multiview_Left = 1, the corresponding audio stream is mapped to the left stereoscopic image in the 3D video format. If Multiview_Left = 0, this field is valid only if NUM_VIEWS = 01.

If Multiview_Right [1 bit]: Multiview_Right = 1, the corresponding audio stream is mapped to the right stereoscopic image in the 3D video format. If Multiview_Right = 0, this field is valid only when NUM_VIEWS = 01 Do.

Language code valid field (LC_Valid) [1 bit]: If LC_Valid = 1, the language code (Language_Code) is valid and correctly identifies the language of the corresponding audio stream. Otherwise, the language of the corresponding audio stream is not specified.

If the auxiliary audio valid field (Suppl_A_Valid) [1 bit]: Suppl_A_Valid = 1, the corresponding audio stream contains a supplemental audio track indicated by Suppl_A_Type.

If the pre-mix auxiliary audio field Suppl_A_Mixed [1 bit]: Suppl_A_Mixed = 1, the corresponding audio stream may include a pre-mixed supplemental audio track indicated by the main audio component and Suppl_A_Type. Valid only when Suppl_A_Valid = 1.

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

Language code (Language_Code) [3Bytes]: Identifies the language of the corresponding audio stream. The language code is defined in ISO639. Then, the 3-character code is located, and the last character code coincides with the last byte of the audio metadata descriptor X (Audio_Metadata_Descriptor_X). This field is valid only when LC_Valid = 1.

<Table 55 - SUPPL_A_TYPE field>

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

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

The data transmission apparatus 100-2 generates an audio metadata packet and transmits it to the data reception apparatus 200-2.

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

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

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

11, the data transmission apparatus 100-2 includes a packet generation unit 110 and a transmission unit 120 according to another embodiment of the present invention.

The packet generation unit 110 generates an audio metadata packet. The header of the generated audio metadata packet may include a 3D audio field indicating whether a 3D audio sample packet is transmitted or not.

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

In addition, the header of the generated audio metadata packet may further include a number of audio stream field indicating the number of audio streams to be transmitted.

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

In addition, the payload of the generated audio metadata packet may be divided into a multi-stream Audio Sample Packet or a Multi-stream One Bit Audio Sample Packet And an audio metadata descriptor field indicating metadata about the packet.

In addition, the audio metadata descriptor field includes an emergency channel field indicating whether there is an emergency broadcast, a multi-view field indicating whether audio data corresponding to the left or right eye image is included in the multi-view, A language code valid field indicating whether or not the language is identified with respect to the audio data, a supplemental audio valid field indicating the presence or absence of the auxiliary audio data, whether or not the main audio data and the auxiliary audio data are premixed A supplemental audio type field indicating a type of the auxiliary audio data and a language code field indicating a language code for the audio data, ) &Lt; / RTI &gt; have.

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

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

The receiving unit 210 receives the audio metadata packet from the data transmitting apparatus 100-2. The header of the audio metadata packet includes a 3D audio field indicating whether a 3D audio sample packet is transmitted or not.

The parser 220 parses the received audio metadata packet.

The header of the audio metadata packet may further include a number of audio stream field indicating the number of audio streams to be received.

In addition, the header of the audio metadata packet may further include a number of view field indicating the number of pieces of different contents to be received.

The payload of the audio metadata packet may be a sub-packet of a multi-stream audio sample packet or a multi-stream one-bit audio sample packet. Lt; RTI ID = 0.0 &gt; metadata metadata descriptor field. &Lt; / RTI &gt;

In this case, the audio metadata descriptor field includes an emergency channel field indicating whether there is an emergency broadcasting, a multi-view field indicating whether the audio data corresponding to the left or right eye image is included in the multi-view, A language code valid field indicating whether or not the language is identified with respect to the audio data, a supplemental audio valid field indicating the presence or absence of the auxiliary audio data, whether or not the main audio data and the auxiliary audio data are premixed A supplemental audio type field indicating a type of the auxiliary audio data and a language code field indicating a language code for the audio data, ) &Lt; / RTI &gt; have.

Audio Data Block

The table below shows audio data blocks of EDID (Extended Display Identification Data). In the table below, we redefine the 3-4 byte part with the table below.

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

<Table 56 - HDMI Audio Data Block>

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

<Table 57 - Byte 3-4 of HDMI Audio Data Block>

Each field is described as follows.

If the emergency channel field (Supports_MS_Emergency [1 bit]: Supports_MS_Emergency = 1), the sink device supports reception and processing of the emergency alert audio channel. If Supports_MS_Emergency = 0, the sink device does not support this feature.

Audio Mix Field (Supports_MS_Mix) [1bit]: If Supports_MS_Mix = 1, the sink device supports synthesis of main audio and supplementary audio. If Supports_MS_Mix = 0, the sink device does not support this synthesis, but only supports playing back the mixed audio.

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

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

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

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

<Table 58 - Max_Stream_Count-1 field>

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

Referring to FIG. 13, a data transmission / reception system 1000-3 according to another embodiment of the present invention includes a data transmission apparatus 100-3 and a data reception apparatus 200-3.

The data transmission apparatus 100-3 generates display identification information including the feature information supported by the sink apparatus with respect to the audio data and transmits it to the data reception apparatus 200-3.

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

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

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

Referring to FIG. 14, a data transmission apparatus 100-3 according to another embodiment of the present invention includes a generation unit 130 and a transmission unit 120. FIG.

The generation unit 130 is a configuration for generating display identification information including the feature information supported by the sink device with respect to the audio data.

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

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

At this time, the main / auxiliary audio property field includes an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, an auxiliary audio support field indicating whether the sink device supports auxiliary audio Supplemental Audio Support Field), a language support field indicating whether the sink device supports audio data in a plurality of languages, a multi-view audio field indicating whether the sink device supports multi-stream audio data for multi- A maximum stream count field indicating a maximum number of audio streams that can be handled by the sink device, and an audio descriptor number field indicating a number of 3D audio descriptors Audio Descriptor Field) It can be included.

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

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

Referring to FIG. 15, a data receiving apparatus 200-3 according to another embodiment of the present invention includes a receiving unit 210 and an analyzing unit 230. FIG.

The receiving unit 210 is a configuration for receiving, from the data transmission apparatus 100-3, display identification information including characteristic information supported by the sink apparatus with respect to audio data.

The analyzer 230 analyzes the received display identification information.

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

The main / auxiliary audio property field may include an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, an auxiliary audio support field indicating whether the sink device supports auxiliary audio, Supplemental Audio Support Field), a language support field indicating whether the sink device supports audio data in a plurality of languages, a multi-view audio field indicating whether the sink device supports multi-stream audio data for multi- A maximum stream count field indicating a maximum number of audio streams that can be handled by the sink device, and an audio descriptor number field indicating a number of 3D audio descriptors Audio Descriptor Field) It can be included.

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

Meanwhile, a wired interface according to various embodiments of the present invention may support quad view content transmission. You can take advantage of the 3D video format specification of the HDMI wired interface specification for quad view transmission.

16A to 16C are diagrams illustrating various data transmission formats when transmitting quad view video contents in 3D interlaced format.

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

<Table 59? VSIF (Packet Body)>

<Table 60? NUM_VIEWS (Rsvd + 3D_DualView)>

<Table 61? VSDB>

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

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

Referring to FIG. 17, a data transmission method according to an embodiment of the present invention includes generating a packet including a first subpacket and a second subpacket (S1710), transmitting the generated packet to a data receiving apparatus (S1720), wherein the first subpacket and the second subpacket comprise different audio data for the first content.

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

In addition, the first subpacket and the second subpacket may include audio data in a different language.

In addition, the first subpacket may include audio data corresponding to the audio description of the second subpacket.

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

At this time, the audio data included in the first subpacket 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 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.

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

18, a method of receiving data according to another embodiment of the present invention includes receiving (S1810) a packet including a first subpacket and a second subpacket from a data transmission apparatus, Parsing the first subpacket and the second subpacket (S1820), wherein the first subpacket and the second subpacket comprise different audio data for the first content.

In addition, the first subpacket may include audio data for a non-disabled person, and the second subpacket may include audio data for a blind person.

In addition, the first subpacket and the second subpacket may include audio data in a different language.

Here, the first subpacket may include audio data corresponding to the audio description of the second subpacket.

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

At this time, the audio data included in the first subpacket 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 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.

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

Referring to FIG. 19, an audio metadata packet is generated (S1910) and a generated audio metadata packet is transmitted to a data receiving apparatus (S1920) according to another embodiment of the present invention. The header of the generated audio metadata packet includes a 3D audio field indicating whether a 3D audio sample packet is transmitted or not.

In addition, the header of the generated audio metadata packet may further include a number of audio stream field indicating the number of audio streams to be transmitted.

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

In addition, the payload of the generated audio metadata packet may be divided into a multi-stream Audio Sample Packet or a Multi-stream One Bit Audio Sample Packet And an audio metadata descriptor field indicating metadata about the packet.

In addition, the audio metadata descriptor field includes an emergency channel field indicating whether there is an emergency broadcast, a multi-view field indicating whether audio data corresponding to the left or right eye image is included in the multi-view, A language code valid field indicating whether or not the language is identified with respect to the audio data, a supplemental audio valid field indicating the presence or absence of the auxiliary audio data, whether or not the main audio data and the auxiliary audio data are premixed A supplemental audio type field indicating a type of the auxiliary audio data and a language code field indicating a language code for the audio data, ) &Lt; / RTI &gt; have.

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

Referring to FIG. 20, a data reception method according to another embodiment of the present invention includes receiving an audio metadata packet from a data transmission apparatus (S2010), parsing the received audio metadata packet (S2020 The header of the received audio metadata packet includes a 3D audio field indicating whether a 3D audio sample packet is transmitted or not.

The header of the audio metadata packet may further include a number of audio stream field indicating the number of audio streams to be received.

In addition, the header of the audio metadata packet may further include a number of view field indicating the number of pieces of different contents to be received.

The payload of the audio metadata packet may be a sub-packet of a multi-stream audio sample packet or a multi-stream one-bit audio sample packet. Lt; RTI ID = 0.0 &gt; metadata metadata descriptor field. &Lt; / RTI &gt;

In addition, the audio metadata descriptor field includes an emergency channel field indicating whether there is an emergency broadcast, a multi-view field indicating whether audio data corresponding to the left or right eye image is included in the multi-view, A language code valid field indicating whether or not the language is identified with respect to the audio data, a supplemental audio valid field indicating the presence or absence of the auxiliary audio data, whether or not the main audio data and the auxiliary audio data are premixed A supplemental audio type field indicating a type of the auxiliary audio data and a language code field indicating a language code for the audio data, ) &Lt; / RTI &gt; have.

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

Referring to FIG. 21, a data transmission method according to another embodiment of the present invention includes generating (S2110) display identification information including feature information supported by a sink device with respect to audio data, And transmitting the display identification information to the device (S2120), wherein the display identification information includes a main / auxiliary audio property field indicating information on characteristics of main audio and auxiliary audio supported by the sink device .

The main / auxiliary audio property field may include an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, an auxiliary audio support field indicating whether the sink device supports auxiliary audio, Supplemental Audio Support Field), a language support field indicating whether the sink device supports audio data in a plurality of languages, a multi-view audio field indicating whether the sink device supports multi-stream audio data for multi- A maximum stream count field indicating a maximum number of audio streams that can be handled by the sink device, and an audio descriptor number field indicating a number of 3D audio descriptors Audio Descriptor Field) It can be included.

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

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

22, a method of receiving data according to another embodiment of the present invention includes receiving (S2210) display identification information including characteristic information supported by a sink device with respect to audio data from a data transmission device, And analyzing the received display identification information (S2220), wherein the display identification information includes a main / auxiliary audio property field indicating information about characteristics of main audio and auxiliary audio supported by the sink device .

The main / auxiliary audio property field may include an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, an auxiliary audio support field indicating whether the sink device supports auxiliary audio, Supplemental Audio Support Field), a language support field indicating whether the sink device supports audio data in a plurality of languages, a multi-view audio field indicating whether the sink device supports multi-stream audio data for multi- A maximum stream count field indicating a maximum number of audio streams that can be handled by the sink device, and an audio descriptor number field indicating a number of 3D audio descriptors Audio Descriptor Field) It can be included.

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

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is clearly understood that the same is by way of illustration and example only and is not to be construed as limiting the scope of the invention as defined by the appended claims. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention.

1000-1, 1000-2, and 1000-3: data transmission / reception system
100-1, 100-2, and 100-3: a data transmission device
200-1, 200-2, 200-3: Data receiving device
110: packet generation unit 120:
130:
210: Receiving unit 220:
230:

Claims (39)

A data transfer apparatus comprising:
A packet generator for generating a packet including a first subpacket and a second subpacket; And
And a transmitting unit for transmitting the generated packet to a data receiving apparatus,
Wherein the first subpacket and the second subpacket comprise different audio data for the first content. The method according to claim 1,
The first subpacket includes audio data for non-disabled persons,
And the second subpacket includes audio data for a blind person. The method according to claim 1,
Wherein the first subpacket and the second subpacket comprise audio data in different languages. The method according to claim 1,
Wherein the first subpacket includes audio data corresponding to an audio description of the second subpacket. The method according to claim 1,
Wherein the packet further comprises a third subpacket including audio data for a second content different from the first content. 6. The method of claim 5,
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,
Wherein the audio data included in the second subpacket is common audio data for the first content and the second content. 6. The method of claim 5,
Wherein the packet further comprises a fourth subpacket including audio data for the second content,
Wherein the third subpacket and the fourth subpacket comprise different audio data. In the data receiving apparatus,
A receiving unit for receiving a packet including a first subpacket and a second subpacket from a data transmission apparatus; And
And a parsing unit parsing the received first subpacket and the second subpacket,
Wherein the first subpacket and the second subpacket comprise different audio data for the first content. 9. The method of claim 8,
The first subpacket includes audio data for non-disabled persons,
And the second subpacket includes audio data for a blind person. 9. The method of claim 8,
Wherein the first subpacket and the second subpacket comprise audio data in different languages. 9. The method of claim 8,
Wherein the first subpacket includes audio data corresponding to an audio description of the second subpacket. 9. The method of claim 8,
Wherein the packet further comprises a third subpacket including audio data for a second content different from the first content. 13. The method of claim 12,
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,
Wherein the audio data included in the second subpacket is common audio data for the first content and the second content. 13. The method of claim 12,
Wherein the packet further comprises a fourth subpacket including audio data for the second content,
And wherein the third subpacket and the fourth subpacket comprise different audio data. In a data transmission / reception system,
A data transmission apparatus for generating a packet including a first subpacket and a second subpacket and transmitting the generated packet to a data receiving apparatus; And
And a data receiving device for receiving the packet from the data transmission device,
Wherein the first subpacket and the second subpacket comprise different audio data for the first content. A data transfer apparatus comprising:
A packet generator for generating an audio metadata packet; And
And a transmitting unit for transmitting the generated audio metadata packet to a data receiving apparatus,
Wherein a header of the generated audio metadata packet includes a 3D audio field indicating whether a 3D audio sample packet is transmitted or not. 17. The method of claim 16,
Wherein the header of the generated audio metadata packet further comprises a number of audio stream field indicating the number of audio streams to be transmitted. 17. The method of claim 16,
The header of the generated audio metadata packet may include:
Further comprising a number of view field indicating a number of pieces of different contents to be transmitted. 17. The method of claim 16,
Wherein the payload of the generated audio metadata packet includes:
And an audio metadata descriptor field indicating metadata about a subpacket of a multi-stream audio sample packet or a multi-stream one-bit audio sample packet. . 20. The method of claim 19,
Wherein the audio metadata descriptor field comprises:
An emergency channel field indicating whether there is an emergency broadcast, a multi-view field indicating whether audio data corresponding to the left eye or right eye image is included in the multi-view, A language code valid field, a supplemental audio valid field indicating whether auxiliary audio data is present, a pre-mixed audio field indicating whether the main audio data is pre-mixed with the auxiliary audio data, A Supplemental Audio Type Field indicating a type of the auxiliary audio data, and a Language Code Field indicating a language code for the audio data. Lt; / RTI &gt; In the data receiving apparatus,
A receiving unit for receiving an audio metadata packet from a data transmission apparatus; And
And a parser parsing the received audio metadata packet,
Wherein a header of the received audio metadata packet includes a 3D audio field indicating whether a 3D audio sample packet is transmitted or not. 22. The method of claim 21,
Wherein the header of the audio metadata packet further comprises a number of audio stream field indicating the number of audio streams to be received. 22. The method of claim 21,
Wherein the header of the audio metadata packet includes:
Further comprising a number of view field for indicating the number of different pieces of content to be received. 22. The method of claim 21,
Wherein the payload of the audio metadata packet comprises:
And an audio metadata descriptor field indicating metadata about a subpacket of a multi-stream audio sample packet or a multi-stream one-bit audio sample packet. . 25. The method of claim 24,
Wherein the audio metadata descriptor field comprises:
An emergency channel field indicating whether there is an emergency broadcast, a multi-view field indicating whether audio data corresponding to the left eye or right eye image is included in the multi-view, A language code valid field, a supplemental audio valid field indicating whether auxiliary audio data is present, a pre-mixed audio field indicating whether the main audio data is pre-mixed with the auxiliary audio data, A Supplemental Audio Type Field indicating a type of the auxiliary audio data, and a Language Code Field indicating a language code for the audio data. . In a data transmission / reception system,
A data transmission apparatus for generating an audio metadata packet and transmitting the audio metadata packet to a data reception apparatus; And
And a data receiving apparatus for receiving the audio metadata packet from the data transmission apparatus,
Wherein a header of the audio metadata packet includes a 3D audio field indicating whether or not a 3D audio sample packet is transmitted. A data transfer apparatus comprising:
A generating unit for generating display identification information including feature information supported by the sink device with respect to audio data; And
And a transmitting unit for transmitting the display identification information to the data receiving apparatus,
And the display identification information includes a main / auxiliary audio property field indicating information on characteristics of main audio and auxiliary audio supported by the sink device. 28. The method of claim 27,
The main / auxiliary audio property field includes:
An audio mix field indicating whether the sync apparatus supports synthesis of main audio and auxiliary audio, a supplemental audio support field indicating whether the sync apparatus supports auxiliary audio, (Multiview Audio Support Field) indicating whether the sync device supports multi-stream audio data for multi-view content, a language support field indicating whether the sync device supports multi-stream audio data for the multi- A maximum stream count field indicating a maximum number of audio streams that can be handled by the apparatus, and a number of audio descriptor field indicating the number of 3D audio descriptors. Data I feature Device. 28. The method of claim 27,
Wherein the display identification information comprises:
Further comprising an emergency channel field indicating whether the sink device supports emergency state broadcast reception and processing. In the data receiving apparatus,
A receiving unit for receiving, from the data transmission device, display identification information including characteristic information supported by the sink device with respect to audio data; And
And an analyzing unit for analyzing the received display identification information,
And the display identification information includes a main / auxiliary audio property field indicating information on characteristics of main audio and auxiliary audio supported by the sink device. 31. The method of claim 30,
The main / auxiliary audio property field includes:
An audio mix field indicating whether the sync apparatus supports synthesis of main audio and auxiliary audio, a supplemental audio support field indicating whether the sync apparatus supports auxiliary audio, (Multiview Audio Support Field) indicating whether the sync device supports multi-stream audio data for multi-view content, a language support field indicating whether the sync device supports multi-stream audio data for the multi- A maximum stream count field indicating a maximum number of audio streams that can be handled by the apparatus, and a number of audio descriptor field indicating the number of 3D audio descriptors. Number of data to be characterized Device. 31. The method of claim 30,
Wherein the display identification information comprises:
Further comprising an emergency channel field indicating whether the sink device supports reception and processing of an emergency situation broadcast. In a data transmission / reception system,
A data transmission device for generating display identification information including the feature information supported by the sink device with respect to the audio data and transmitting the display identification information to the data reception device; And
And a data receiving device for receiving and analyzing the display identification information from the data transmission device,
Wherein the display identification information comprises a main / auxiliary audio property field indicating information on characteristics of main audio and auxiliary audio supported by the sink device. In a data transmission method,
Generating a packet including a first subpacket and a second subpacket; And
And transmitting the generated packet to a data receiving apparatus,
Wherein the first subpacket and the second subpacket comprise different audio data for the first content. In the data receiving method,
Receiving a packet including a first subpacket and a second subpacket from a data transmission apparatus; And
And parsing the received first subpacket and the second subpacket,
Wherein the first subpacket and the second subpacket comprise different audio data for the first content. In a data transmission method,
Generating an audio metadata packet; And
And transmitting the generated audio metadata packet to a data receiving apparatus,
Wherein a header of the generated audio metadata packet includes a 3D audio field indicating whether a 3D audio sample packet is transmitted or not. In the data receiving method,
Receiving an audio metadata packet from a data transmission device; And
Parsing the received audio metadata packet,
Wherein a header of the received audio metadata packet includes a 3D audio field indicating whether a 3D audio sample packet is transmitted or not. In a data transmission method,
Generating display identification information including feature information supported by the sink device with respect to audio data; And
And transmitting the display identification information to the data receiving apparatus,
Wherein the display identification information comprises a main / auxiliary audio property field indicating information on characteristics of main audio and auxiliary audio supported by the sink device. In the data receiving method,
Receiving, from a data transmission device, display identification information including feature information supported by a sink device with respect to audio data; And
And analyzing the received display identification information,
Wherein the display identification information comprises a main / auxiliary audio property field indicating information on characteristics of main audio and auxiliary audio supported by the sink device.

Images