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

Abstract

A data transmission device is disclosed. A data transmission apparatus according to an embodiment of the present invention includes a packet generation unit that generates a packet including a first subpacket and a second subpacket, and a transmission unit that transmits the generated packet to a data reception device, and the The first sub-packet and the second sub-packet contain different audio data for the first content.

Description

Data transmission device, data reception device, data transmission/reception system, data transmission method and data reception method {DATA TRANSMITTING APPRATUS, DATA RECEIVING APPARATUS, DATA TRANCEIVING SYSTEM, METHOD FOR TRANSMITTING DATA AND METHOD FOR RECEIVING DATA}

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

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

However, the conventional audio signal transmission standard has not proposed an interface standard such as transmitting audio data for the visually impaired or audio data in multiple languages for content.

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

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

According to an embodiment of the present invention for achieving the above object, a data transmission device includes a packet generator for generating a packet including a first subpacket and a second subpacket, and a data receiving device for the generated packet. And a transmission unit that transmits to, wherein the first sub-packet and the second sub-packet include different audio data for the first content.

In this case, the first sub-packet may include audio data for a non-disabled person, and the second sub-packet may include audio data for a visually impaired person.

In addition, the first sub-packet and the second sub-packet may include audio data in different languages.

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

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

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

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

According to an embodiment of the present invention for achieving the above object, a data receiving device includes a receiving unit for receiving a packet including a first sub-packet and a second sub-packet from a data transmission device, and the received first sub-packet. And a parsing unit that parses the packet and the second sub-packet, and the first sub-packet and the second sub-packet include different audio data for first content.

In addition, the first sub-packet may include audio data for a non-disabled person, and the second sub-packet may include audio data for a visually impaired person.

In addition, the first sub-packet and the second sub-packet may include audio data in different languages.

In this case, the first sub-packet may include audio data corresponding to an audio description of the second sub-packet.

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

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

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

According to an embodiment of the present invention for achieving the above object, a data transmission/reception system includes a data transmission device for generating a packet including a first sub-packet and a second sub-packet and transmitting the packet to a data receiving device; and And a data receiving device for receiving the packet from a data transmission device, wherein the first sub-packet and the second sub-packet contain different audio data for first content.

According to another embodiment of the present invention for achieving the above object, a data transmission device includes a packet generation unit for generating an audio metadata packet, and a transmission unit for transmitting the generated audio metadata packet to a data receiving device. And the header of the generated audio metadata packet includes a 3D audio field indicating whether or not the 3D audio sample packet is transmitted.

In addition, the header of the generated audio metadata packet may further include a Number Of Audio Stream Field indicating information on the number of transmitted audio streams.

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

In addition, the payload of the generated audio meta data packet is a sub of a multi-stream audio sample packet or a multi-stream one bit audio sample packet. It may include an audio metadata descriptor field indicating metadata about a 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 a left-eye or right-eye image is included in a multi-view, A language code valid field indicating the presence or absence of a language for audio data, a supplemental audio valid field indicating the presence or absence of auxiliary audio data, whether the main audio data and the auxiliary audio data are premixed A pre-mixed supplemental audio field indicating a pre-mixed supplemental audio field, a supplemental audio type field indicating a type of the auxiliary audio data, and a language code field indicating a language code for audio data. ) May include at least one of.

According to another embodiment of the present invention for achieving the above object, a data receiving device includes a receiving unit for receiving an audio meta data packet from a data transmission device, and a parsing unit for parsing the received audio meta data packet, , The header of the received audio metadata packet includes a 3D audio field indicating whether or not the 3D audio sample packet is transmitted.

In addition, the header of the audio metadata packet may further include a Number Of Audio Stream Field indicating information on the number of received audio streams.

In addition, the header of the audio metadata packet may further include a Number Of Views Field indicating information on the number of different contents to be received.

In addition, the payload of the audio meta data packet is a subpacket of a multi-stream audio sample packet or a multi-stream one bit audio sample packet. It may include an audio meta data descriptor field indicating meta data for the data.

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 a left-eye or right-eye image is included in a multi-view, A language code valid field indicating the presence or absence of a language for audio data, a supplemental audio valid field indicating the presence or absence of auxiliary audio data, whether the main audio data and the auxiliary audio data are premixed A pre-mixed supplemental audio field indicating a pre-mixed supplemental audio field, a supplemental audio type field indicating a type of the auxiliary audio data, and a language code field indicating a language code for audio data. ) May include at least one of.

According to another embodiment of the present invention for achieving the above object, a data transmission/reception system includes a data transmission device that generates an audio metadata packet and transmits it to a data reception device, and the audio metadata packet from the data transmission device. And a data receiving device for receiving, wherein a header of the audio metadata packet includes a 3D audio field indicating whether to transmit a 3D audio sample packet.

According to another embodiment of the present invention for achieving the above object, a data transmission device includes a generator for generating display identification information including feature information supported by a sink device for audio data, and data reception. And a transmission unit for transmitting the display identification information to a device, and the display identification information includes a main/secondary audio characteristic field indicating information on characteristics of main audio and auxiliary audio supported by the sink device.

In addition, the main/auxiliary audio characteristic field includes an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, and 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 indicating whether the sink device supports multi-stream audio data for multi-view content A multiview audio support field, a maximum stream count field indicating the number of maximum audio streams that the sink device can handle, and an audio descriptor number field indicating the number of 3D audio descriptors (Number Of Audio Descriptor Field).

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

According to another embodiment of the present invention for achieving the above object, a data reception device includes, from a data transmission device, a reception unit for receiving display identification information including feature information supported by the sink device with respect to audio data. And an analysis unit for analyzing the received display identification information, wherein the display identification information includes a main/secondary audio characteristic field indicating information on characteristics of main audio and auxiliary audio supported by the sink device.

In addition, the main/auxiliary audio characteristic field includes an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, and 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 indicating whether the sink device supports multi-stream audio data for multi-view content A multiview audio support field, a maximum stream count field indicating the number of maximum audio streams that the sink device can handle, and an audio descriptor number field indicating the number of 3D audio descriptors (Number Of Audio Descriptor Field).

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

According to another embodiment of the present invention for achieving the above object, a data transmission/reception system generates display identification information including feature information supported by a sink device for audio data and transmits it to a data receiving device. A data transmission device and a data receiving device that receives and analyzes the display identification information from the data transmission device, wherein the display identification information indicates information on characteristics of main audio and auxiliary audio supported by the sink device. Includes main/secondary audio characteristic fields.

According to another embodiment of the present invention for achieving the above object, a data transmission method includes generating a packet including a first sub-packet and a second sub-packet, and transmitting the generated packet to a data receiving device. Transmitting, wherein the first sub-packet and the second sub-packet contain different audio data for the first content.

According to another embodiment of the present invention for achieving the above object, a data receiving method includes receiving a packet including a first subpacket and a second subpacket from a data transmission device, and the received first subpacket. Parsing the sub-packet and the second sub-packet, wherein the first sub-packet and the second sub-packet contain different audio data for a first content.

Generating an audio metadata packet according to another embodiment of the present invention for achieving the above object, and transmitting the generated audio metadata packet to a data receiving device, wherein the generated audio The header of the metadata packet includes a 3D audio field indicating whether or not a 3D audio sample packet is transmitted.

According to another embodiment of the present invention for achieving the above object, a data receiving method includes receiving an audio metadata packet from a data transmission device and parsing the received audio metadata packet, , The header of the received audio metadata packet includes a 3D audio field indicating whether or not the 3D audio sample packet is transmitted.

According to another embodiment of the present invention for achieving the above object, a data transmission method includes generating display identification information including feature information supported by a sink device with respect to audio data, and a data receiving device And transmitting the display identification information to, wherein the display identification information includes a main/secondary audio characteristic field indicating information on characteristics of main audio and auxiliary audio supported by the sink device.

According to another embodiment of the present invention for achieving the above object, a data receiving method includes receiving, from a data transmission device, display identification information including feature information supported by a sink device with respect to audio data. And analyzing the received display identification information, wherein the display identification information includes a main/secondary audio characteristic 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 standard capable of transmitting and receiving a plurality of audio data related to the same content between a source device and a sink device.

1 is a diagram showing a single audio stream and a multi audio stream;
FIG. 2 is a diagram illustrating that a source device transmits multiple audio for dual window and screen separation to a sink device;
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 timing of 3D audio signals;
7 is a block diagram showing the configuration of a data transmission/reception system according to an embodiment of the present invention;
8 is a block diagram showing the configuration of a data transmission device 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 showing a configuration of a data transmission/reception system according to another embodiment of the present invention;
11 is a block diagram showing a configuration of a data transmission device according to another embodiment of the present invention;
12 is a block diagram showing a 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;
14 is a block diagram showing the configuration of a data transmission device according to another embodiment of the present invention;
15 is a block diagram showing a configuration of a data receiving apparatus according to another embodiment of the present invention;
16A to 16B are diagrams illustrating various data transmission formats when quad-view video content is transmitted in a 3D interlace 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 reception 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, and,
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 describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to users, operators, or customs. Therefore, the definition should be made based on the contents throughout this specification.

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

The present specification refers to the following documents.

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

SMPTE, SMPTE 2036-2:2008, “UHDTV-Audio characteristics and audio channel mapping for program production”, 2008

IEC, IEC 62574 ed 1.0, “Audio, video and multimedia systems-General channel assignment of multichannel audio”, 7 April 2011

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

Term Definition MHL source Devices with MHL output ports. The MHL source uses a socket on each MHL output port and does not use a plug. MHL sink Devices with one or more MHL input ports. The MHL sink uses a socket at each MHL input port and does not use a plug. 3D audio A voice system where speakers are located anywhere in the 3D space. This is an audio that does not include a height component and typically places 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 as defined in these standards comprising 9 or more audio channels. For the avoidance of doubt in this specification, 3D audio refers to a limited number of distinct channels, not object-based audio. Multi audio A collection of audio streams related to one or more video streams. Multi-audio is carried as a single-AV stream. For clarity in this specification, multi-audio does not mean transmission of multiple audio streams via multi-AV-streaming. Stream A time-ordered set of digital data originating from an MHL source and ending at one MHL sink. The stream is characterized by fixed frequency bandwidth conditions within the stream data and by a synchronization point or time stamp. (Single-AV) stream A single stream that is packetized so that all stream data share the same packet stream ID.
In a single-AV stream, the stream data can process one or more video streams and one or more audio streams. Multi-AV stream A set of multiple single-AV streams in which a unique packet stream ID is assigned to each single-AV stream. Single-view View mode in which only a single video stream is displayed in the MHL sink. Multi-view A view mode in which two or more independent video streams are simultaneously displayed on the MHL sink, and the viewer can only view one video stream at any given time. For example, the multi-view video stream may be transmitted through a 3D video format in which an independent video stream is processed in left and right stereoscopic screens, respectively. window The (non-overlapping) portion of the video image displayed by the MHL sync. The video image may be composed of two or more windows that do not overlap each other. Split screen A view option where two or more windows are tagged and identified by an MHL source (e.g., PIP TV watching, TV quick preview, multiscreen game).

<Table 1? Term>

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

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

As shown in FIG. 1B, the multi-audio stream is a case in which a plurality of single AV streams are transmitted. In a multi-audio stream, there is a set of multiple 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 independent of each other.

Each audio stream of a multi-audio stream carries up to two audio channels. And, it relates to a single audio stream. For example, in single view mode, each audio may be connected to a default video stream, and in dual view mode, audio may be connected to a left image or a right image (or both). In addition, one or more auxiliary audio options as follows may be transmitted. That is, split-screen tagging, language indication, and indication of audio for visually/hearing impaired.

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

Split screen (or multi-window can also be used with the same term) can be an optional configuration used with multi-audio. The screen separation mode represents a configuration in which a screen is separated from a sink device, and an audio stream is tagged and mapped to a specific window.

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

FIG. 2A is an embodiment of transmitting audio data for each of a multi-screen, and FIG. 2B is an embodiment of transmitting a plurality of audio data according to a quick preview or PIP viewing, and FIG. 2 (C) 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 desired audio.

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

The source device 310 transmits a Vendor-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 indicates the settings for each audio stream. It is related to the video stream and may carry auxiliary audio information. The vendor-specific info frame indicates the multi-view type of the transmitted content. A specific embodiment will be described later.

The sink device 320 informs the multi-audio mode information supported by the sink device by transmitting an extended device capability register to the source device. A specific embodiment will be described later.

Meanwhile, the multi-audio supports transmission of auxiliary audio tracks (eg, multiple languages, audio description for visual impairment, or clean audio for hearing impairment). In this case, up to 16 audio streams can be transmitted simultaneously. A detailed description of this will be given 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 a speaker can be placed in a position determined by 3D audio standards (e.g. 10.2ch, 22.2ch, 30.2ch, etc.) in 3D space. The 3D audio sample packet is composed of one audio sample having 9 to 32 audio channels.

The 3D audio stream includes up to 32 audio channels (or more) and is transmitted through consecutive packets in the data island section. Each packet contains up to 8 audio channels. The configuration of the sub-packets is determined by the sequence number and the 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.

Other header fields and subpacket structure are consistent with the audio sample packet 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

The multi-audio sample packet may include four audio samples, each audio sample independently associated with an audio stream. When the source device transmits four or more independent audio streams simultaneously, these consecutive audio streams are transmitted by a series of consecutive 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 arrangement of packets. The configuration of the sub-packets is determined by the sequence number and sample present bits in the header. This will be described in detail in multi-audio data packetization.

For each sub-packet (or audio stream), the descriptor field in the Multi-Audio Metadata Packet is a view mode (i.e., single-view or multi-view), and optional information. (For example, screen separation tagging, language code, audio for visual impairment, etc.) These are described in detail later.

Sequence number field (sequence_number): When there are four or more audio streams for transmission from the source device to the sink device, this indicates the sequence number of the current multi-audio sample packet. If this field is set to 0, the packet may include the first four audio streams in each of the subpackets. If this field is set to 1, the packet may include a second set of four audio streams, respectively, in the subpackets. In a similar way, a packet contains 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 having a sequence number of 0 is designated as a default audio stream.

Stream present field (stream_presnt.spX): Indicates whether sub-packet X includes audio sample(s) of stream X.

Stream flat field (stream_flat.spX): Indicates whether or not subpacket X represents a “flatline” sample of stream X. It is valid only when stream_present.spX is set.

The other header fields and subpacket structure correspond to the audio sample packet 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 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~PB6 Audio sample data for audio stream N+0 PB7~PB13 Audio sample data for audio stream N+1 PB14~PB20 Audio sample data for audio stream N+2 PB21~PB27 Audio sample data for audio stream N+3

<Table 4-Mutli Audio Sample Packet>

4 is a diagram illustrating a situation 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 may be carried. Since the sequence number consists of 2 bits, up to 16 audio streams can be carried.

3D audio metadata packet

Ancillary data describing active 3D audio data is transmitted using a 3D audio metadata packet. If the source device can transmit 3D audio sample packets, the source device always transmits the correct 3D audio metadata packet, at least once per 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~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_CC (3D Audio Channel Count) 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_CA (3D Audio Channel/Speaker Allocation) 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_CA (3D Audio Channel/Speaker Allocation) 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_CA (3D Audio Channel/Speaker Allocation) field (3D_CAST = 0x03(up to 30.2ch) )>

Multi-Audio Metadata Packet

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

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

The following shows the 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~PB6 MA_Descriptor_0 PB7~PB13 MA_Descriptor_1 PB14~PB20 MA_Descriptor_2 PB21~PB27 MA_Descriptor_3

<Table 11-Multi-Audio Metadata Packet>

View type field (MA_View_Type): Represents a related view mode of a multi-audio stream such as single view or multi view. See table below.

Sequence number field (Sequence_Number): indicates the sequence number of a packet or a current multi-audio metadata packet. This field is used to identify up to four different multi-audio metadata packets. This field associates each multi-audio metadata packet with multi-audio sample packets having the same sequence number.

The number of audio streams field (Num_Audio_Streams: represents the total number of audio streams transmitted by multi-audio sample packets).

Screen Split Valid Field (SC_Valid): If set to 1, screen split tagging is supported, and the screen split configuration field is detailed in the next 7 bits. If set to 0, screen split tagging is either not supported or detailed, and the next 7 bits are reserved for other use.

Screen split type field (Split_Screen_Config): indicates the screen split type related to the audio stream indicated by the current descriptor. Selectable screen separation types are listed in Table 13 below. This field is valid only when SC_valid=1.

Multi-audio descriptor field (MA_Descriptor_X): This indicates the characteristics of the audio stream transmitted by the sub-packet X of the 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 descriptor.

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>

Split screen tag field (Split_Screen_Tag): represents a specific window (as defined by the split screen composition) related to the audio stream represented by the current multi-audio descriptor. A detailed description is shown in Table 16 below. This field is valid only when SC_valid = 1, otherwise the sink device ignores this field.

Related view identification field (Associated_View_ID): indicates a specific view related to an audio stream represented by the current multi-audio descriptor. The meaning of this field depends on the value of the view type field (MA_View_Type). A detailed description is shown in Table 15 below.

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

Mixed Audio Field (Mixed_Audio): If this field is set to 1, the corresponding audio stream includes a premixed stream of normal 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 includes an auxiliary audio type field (Suppl_Audio_Type) valid in the following 4 bits.

Auxiliary audio type field (Suppl_Audio_Type): indicates the type of auxiliary audio for a corresponding audio stream. See Table 17 for details. 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 a language code defined as ISO639 of a corresponding audio stream. This field is valid only when the valid 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 the correct view mode to be transmitted to the sink device. 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): This 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 indicated 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

When the sink device is capable of receiving 3D audio, the 3D channel speaker assignment descriptor described in Table 40 in Table 38 is used to indicate the configuration of the attached speakers. The indicator of the current speaker allocation for 3D audio transmitted from the source device is handled in the 3D CA field of the 3D audio metadata packet. For a detailed description of the 3D CA field, refer to Tables 27 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 along with the 3D audio metadata packet.

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

Packet # sequence number 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 # sequence number 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 # sequence number 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 (Sample_present bits) in one, 3D audio sample packet header for each sub packet. Each indicates that one sub-packet contains 3D audio samples. In addition, there are four sample flat (sample_flat.spX) bits that are 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 disturbances.

Subsequent 3D audio sample packets may be used to process one 3D audio sample comprising between 9 and 32 channels of L-PCM audio (ie 5 to 16 IEC60958 frames).

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

There are only 5 valid sample present (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 illustrating transmission timing of 3D audio signals.

It can be seen from FIGS. 5 and 6 that three 8-channel 2D audio signal samples are transmitted in a horizontal blanking interval. 24 channels of 3D audio signals are transmitted one sample during the same period.

Multi-Audio Data Packetization

MHL allows the MHL source device to simultaneously transmit audio streams for single-AV streaming. Multiple audio streams are associated with either single-view or multi-view video streaming (eg, dual-view gaming with different audios per view). The auxiliary audio modes may represent screen split tagging (ie, different parts of the screen are tagged and associated with their own audio stream), language codes, or audio for the visual/deaf. Each audio stream is associated with one view mode and contains up to two audio channels.

Each sub-packet of the multi-stream audio sample packet may include "frames" of IEC60958 or IEC61937 "block" defined as 0 or 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 arrangement is identified by the sequence number field. The MHL source device can simultaneously transmit up to 16 independent audio streams within a single AV stream.

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

Tables 27 and 28 show examples of multi-audio sample packets and multi-audio metadata packet layouts when the MHL source device transmits 8 audio streams through dual-view video streaming. The multi-audio metadata packet describes the characteristics (related views, auxiliary information, language) of each audio stream.

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

Packet # sequence number 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 # sequence number 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 hearing impairment

Audio for VI: Audio stream for visual impairment

Packet # sequence number 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 # sequence number 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 hearing impairment

Audio for VI: Audio stream for visual impairment

Packet # sequence number 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 # sequence number 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 hearing impairment

Audio for VI: Audio stream for visual impairment

3D audio metadata packetization

Whenever an active 3D audio stream is transmitted, an accurate 3D audio metadata packet is transmitted once per at least two video fields.

When a new 3D audio stream starts, or when there is a change in the 3D audio stream that can be represented by the 3D audio metadata packet and audio infoframe, the corrected 3D audio metadata packet is the first affected non-silent. ) Transmitted before one video frame following the audio sample. First of all, this happens just before the first affected audio sample is transmitted.

Transmission of 3D audio metadata packets can occur at any time within a data platform section including a horizontal and vertical blanking section.

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

Multi-audio metadata packetization

Whenever an active multi-audio stream is transmitted, an exact multi-audio metadata packet is transmitted once per at least two video fields.

When a new multi-audio stream starts, or when there is a change in the multi-audio stream that can be represented by the multi-audio metadata packet and audio infoframe, the corrected multi-audio metadata packet is the first affected non-silent. It is transmitted before one video frame following the (non-silent) audio sample. First of all, this happens just before the first affected audio sample is transmitted.

Multi-audio metadata packet transmission may occur at any time within a data platform section including a horizontal and vertical blanking section.

Use of WRITE_BURST for 3D/multi-audio support

Support for 3D audio mode is indicated using a series of formatted WRITE_BURST movements 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 bit 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 designated speaker associated with the 10.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 (=0x02) 0 0 0 0

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

Bold text indicates designated speakers related to 22.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 (=0x03) 0 0 0 0

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

Bold text indicates designated speakers 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

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. See 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

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

As shown in the table below, 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.

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

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

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

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 multiview video streaming, this field is set to zero.

Multi-Stream Audio

Hereinafter, multi-stream audio according to various embodiments of the present disclosure 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 device of the present invention can simultaneously transmit 4 audio streams. For a multi-stream audio sample packet, all audio streams share one audio infoframe.

A wired interface according to various embodiments of the present disclosure may add support for single-view video streaming (eg, multi-lingual support or audio for visually or deaf people). 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 in 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>

In the case of a multi-stream audio sample packet having 4 sub-packets 1) When a single TV program is transmitted with an audio description for a single view, stream 0 includes a normal audio signal, and stream 1 is It may include an audio description signal for the visually impaired.

2) When the single view supports two languages, two audio signal streams in the supported languages and audio descriptions corresponding to each are transmitted together. For example, when English and Korean are supported, stream 0 is a Korean normal audio signal, stream 1 is a Korean audio description signal for the visually impaired, stream 2 is an English normal audio signal, and stream 3 is an English audio description for the visually impaired. Each may contain signals.

3) In a single view, one audio signal stream in one language and two audio description signals for the visually impaired supported in different languages for the same may be transmitted. For example, stream 0 may include a Korean or English normal audio signal, stream 1 may include a Korean audio description signal for the visually impaired, and stream 2 may include an English audio description signal for the visually impaired.

4) The source device may transmit an audio signal for multiview. When dual view is supported, the most basic form is to transmit an audio signal for each view in one transport stream. In the case of the dual view, an independent first view and a second view are included, and each view provides independent content.

5) Two languages can 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, and a second view. Each audio signal stream in a second language may be transmitted. For example, if English and Korean are supported, stream 0 is a Korean audio signal for a first view, stream 1 is an English audio signal for a first view, stream 2 is a Korean audio signal for a second view, and stream 3 May include an English audio signal for the second view.

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

7) One stream may be used to transmit a common audio signal. That is, a common audio signal stream for the first view and the second view, an audio stream dedicated to the first view, and an audio stream dedicated to the second view may be transmitted, respectively. In this case, the receiving end outputs a common audio stream and a dedicated audio stream by muxing. This scenario can be applied in the case of games. For example, stream 0 is a common audio signal (e.g., background sound, progress guidance voice, etc.) for a first view and a second view, stream 1 is a dedicated audio signal for the first view, and stream 2 is a second It may contain 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 device 100-1 and a data reception device 200-1.

The data transmission device 100-1 transmits a packet including a first sub packet and a second sub packet to the data receiving device 200-1.

The data receiving device 200-1 receives the packet including a first sub packet and a second sub packet from the data transmission device 100-1.

In this case, the first sub-packet and the second sub-packet include different audio data for the first content.

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

8 is a block diagram showing the 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.

The packet generator 110 generates a packet including a first sub packet and a second sub packet. In this case, the first sub-packet and the second sub-packet include different audio data for the first content.

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

In this case, the first sub-packet may include audio data for a non-disabled person, and the second sub-packet may include audio data for a visually impaired person.

In addition, the first sub-packet and the second sub-packet may include audio data in different languages.

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

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

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

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

9 is a block diagram showing the 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.

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

The parsing unit 220 is configured to parse the received first sub-packet and the second sub-packet.

The first sub-packet and the second sub-packet may include audio data in different languages.

Alternatively, the first sub-packet may include audio data corresponding to an audio description of the second sub-packet.

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

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

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

Audio Metadata Packet

The source device transmits the audio metadata packet to the sink device, and informs the transmitted audio specification. In this case, the header of the audio metadata packet has the following structure.

<Table 48-Audio Metadata Packet Header>

Each field is described as follows.

3D Audio Field (3D_AUDIO) [1bit]: If 3D_AUDIO=1, the Audio Metadata Packet is a 3D audio channel count (3D Audio Channel count: 3D_CC field, see table below) and channel/speaker assignment information (ACAST). : Audio Channel Allocation Standard Type) field (refer to the table below) is included. When the source transmits a 3D audio packet, this field will be set to 1.

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 allowed only when 3D_DualView=1 in VSIF. The remaining NUM_VIEWS values are reserved for future use.

Number of audio streams field (NUM_AUDIO_STR) [2bits]: indicates the number of audio streams -1. When NUM_AUDIO_STR=01, 10, or 11, audio metadata packets include up to four audio metadata descriptors, each corresponding to an audio stream.

<Table 49-Valid Combinations>

The table below shows the payload of the audio metadata packet for 3D audio. When 3D_Audio=1, the meta data 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 a source are included.

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

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 shows the payload of an audio metadata packet for multi-stream audio. When 3D_Audio=0, the meta data 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 the audio metadata for sub-packet X in the multi-stream audio sample packet or the multi-stream one-bit audio sample packet. Sample Packet) expresses audio metadata for subpacket X. The structure of the audio meta data descriptor is described below.

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

Each field is described below.

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

Multiview Field (Left) (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 when NUM_VIEWS=01.

Multiview field (right side) (Multiview_Right [1bit]: If 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) [1bit]: If LC_Valid=1, the language code (Language_Code) is valid, and the language of the corresponding audio stream is accurately identified. Otherwise, the language of the corresponding audio stream becomes unspecified.

Supplementary audio valid field (Suppl_A_Valid) [1bit]: When Suppl_A_Valid=1, the corresponding audio stream includes a supplemental audio track indicated by Suppl_A_Type.

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

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

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

<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 device 100-2 and a data reception device 200-2.

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

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

In this case, the header of the audio metadata packet includes a 3D audio field indicating whether to transmit a 3D audio sample packet.

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

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

The packet generator 110 generates an audio metadata packet. The header of the generated audio metadata packet may include a 3D audio field indicating whether to transmit a 3D audio sample packet.

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

In addition, the header of the generated audio metadata packet may further include a Number Of Audio Stream Field indicating information on the number of transmitted audio streams.

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

In addition, the payload of the generated audio meta data packet is a sub of a multi-stream audio sample packet or a multi-stream one bit audio sample packet. It may include an audio metadata descriptor field indicating metadata about a 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 a left-eye or right-eye image is included in a multi-view, A language code valid field indicating the presence or absence of a language for audio data, a supplemental audio valid field indicating the presence or absence of auxiliary audio data, whether the main audio data and the auxiliary audio data are premixed A pre-mixed supplemental audio field indicating a pre-mixed supplemental audio field, a supplemental audio type field indicating a type of the auxiliary audio data, and a language code field indicating a language code for audio data. ) May include at least one of.

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.

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

The parser 220 is a component that parses the received audio metadata packet.

In addition, the header of the audio metadata packet may further include a Number Of Audio Stream Field indicating information on the number of received audio streams.

In addition, the header of the audio metadata packet may further include a Number Of Views Field indicating information on the number of different contents to be received.

In addition, the payload of the audio meta data packet is a subpacket of a multi-stream audio sample packet or a multi-stream one bit audio sample packet. It may include an audio meta data descriptor field indicating meta data for the data.

In this case, the audio meta data descriptor field includes an emergency channel field indicating whether there is an emergency broadcast, a multi view field indicating whether audio data corresponding to a left-eye or right-eye image is included in a multi-view, A language code valid field indicating the presence or absence of a language for audio data, a supplemental audio valid field indicating the presence or absence of auxiliary audio data, whether the main audio data and the auxiliary audio data are premixed A pre-mixed supplemental audio field indicating a pre-mixed supplemental audio field, a supplemental audio type field indicating a type of the auxiliary audio data, and a language code field indicating a language code for audio data. ) May include at least one of.

Audio Data Block

The following is a table showing an audio data block of EDID (Extended Display Identification Data). In the table below, 3-4 bytes are redefined to the table below.

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

<Table 56-HDMI Audio Data Block>

The table below shows a block configuration 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.

Emergency Channel Field (Supports_MS_Emergency [1bit]: If Supports_MS_Emergency = 1, the sink device supports receiving and processing an 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 combining main audio and supplementary audio. If Supports_MS_Mix=0, the sink device does not support this synthesis and only supports playing mixed audio.

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

Language Support Field (Supports_MS_Lang) [1bit]: If Supports_MS_Lang=1, the sink device supports multi-stream audio having multiple language audio streams. If Supports_MS_Lang=0, nothing is indicated or it 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, nothing is indicated or it indicates that the sink device does not support multi-stream audio for multi-view video streaming.

Maximum stream count field (Max_Stream_Count-1) [2bits]: Indicates the maximum number of audio streams that the sink device can handle. The value of Max_Stream_Count-1 is shown in the table below.

Number of audio descriptors field (NUM_HDMI_3D_AD) [3bits]: indicates the number of 3D audio descriptors.

<Table 58-Max_Stream_Count-1 field>

13 is a block diagram showing the 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 device 100-3 and a data reception device 200-3.

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

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

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

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

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

The generation unit 130 is a component that generates display identification information including feature information supported by the sink device with respect to audio data.

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

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

In this case, the main/auxiliary audio characteristic field includes an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, and 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 indicating whether the sink device supports multi-stream audio data for multi-view content A multiview audio support field, a maximum stream count field indicating the number of maximum audio streams that the sink device can handle, and an audio descriptor number field indicating the number of 3D audio descriptors (Number Of Audio Descriptor Field).

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

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

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

The receiving unit 210 is configured to receive display identification information including feature information supported by the sink device with respect to audio data from the data transmission device 100-3.

The analysis unit 230 analyzes the received display identification information.

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

In addition, the main/auxiliary audio characteristic field includes an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, and 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 indicating whether the sink device supports multi-stream audio data for multi-view content A multiview audio support field, a maximum stream count field indicating the number of maximum audio streams that the sink device can handle, and an audio descriptor number field indicating the number of 3D audio descriptors (Number Of Audio Descriptor Field).

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

Meanwhile, a wired interface according to various embodiments of the present disclosure may support quad-view content transmission. For quad-view transmission, the 3D video format standard of the HDMI wired interface standard can be used.

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

Also, in this case, a vendor-specific infoframe and a vendor-specific data block may be modified. Specifically, the field defining the conventional 3D dual view is extended to the reserve area.

<Table 59? VSIF(Packet Body)>

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

<Table 61? VSDB>

Hereinafter, a method of transmitting and receiving data according to various embodiments of the present disclosure 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 sub-packet and a second sub-packet (S1710), and transmitting the generated packet to a data receiving device. A step S1720, wherein the first sub-packet and the second sub-packet include different audio data for the first content.

In this case, the first sub-packet may include audio data for a non-disabled person, and the second sub-packet may include audio data for a visually impaired person.

In addition, the first sub-packet and the second sub-packet may include audio data in different languages.

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

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

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

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

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

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

In addition, the first sub-packet may include audio data for a non-disabled person, and the second sub-packet may include audio data for a visually impaired person.

In addition, the first sub-packet and the second sub-packet may include audio data in different languages.

In this case, the first sub-packet may include audio data corresponding to an audio description of the second sub-packet.

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

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

Also, the packet may further include a fourth sub-packet including audio data for the second content, and the third sub-packet and the fourth sub-packet 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, according to another embodiment of the present invention, generating an audio metadata packet (S1910) and transmitting the generated audio metadata packet to a data receiving device (S1920), The header of the generated audio metadata packet includes a 3D audio field indicating whether or not a 3D audio sample packet is transmitted.

In addition, the header of the generated audio metadata packet may further include a Number Of Audio Stream Field indicating information on the number of transmitted audio streams.

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

In addition, the payload of the generated audio meta data packet is a sub of a multi-stream audio sample packet or a multi-stream one bit audio sample packet. It may include an audio metadata descriptor field indicating metadata about a 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 a left-eye or right-eye image is included in a multi-view, A language code valid field indicating the presence or absence of a language for audio data, a supplemental audio valid field indicating the presence or absence of auxiliary audio data, whether the main audio data and the auxiliary audio data are premixed A pre-mixed supplemental audio field indicating a pre-mixed supplemental audio field, a supplemental audio type field indicating a type of the auxiliary audio data, and a language code field indicating a language code for audio data. ) May include at least one of.

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

Referring to FIG. 20, according to another embodiment of the present invention, a data receiving method includes receiving an audio metadata packet from a data transmission device (S2010) and parsing the received audio metadata packet (S2020). ), and the header of the received audio metadata packet includes a 3D audio field indicating whether to transmit a 3D audio sample packet.

In addition, the header of the audio metadata packet may further include a Number Of Audio Stream Field indicating information on the number of received audio streams.

In addition, the header of the audio metadata packet may further include a Number Of Views Field indicating information on the number of different contents to be received.

In addition, the payload of the audio meta data packet is a subpacket of a multi-stream audio sample packet or a multi-stream one bit audio sample packet. It may include an audio meta data descriptor field indicating meta data for the data.

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 a left-eye or right-eye image is included in a multi-view, A language code valid field indicating the presence or absence of a language for audio data, a supplemental audio valid field indicating the presence or absence of auxiliary audio data, whether the main audio data and the auxiliary audio data are premixed A pre-mixed supplemental audio field indicating a pre-mixed supplemental audio field, a supplemental audio type field indicating a type of the auxiliary audio data, and a language code field indicating a language code for audio data. ) May include at least one of.

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

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

In addition, the main/auxiliary audio characteristic field includes an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, and 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 indicating whether the sink device supports multi-stream audio data for multi-view content A multiview audio support field, a maximum stream count field indicating the number of maximum audio streams that the sink device can handle, and an audio descriptor number field indicating the number of 3D audio descriptors (Number Of Audio Descriptor Field).

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

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

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

In addition, the main/auxiliary audio characteristic field includes an audio mix field indicating whether the sink device supports synthesis of main audio and auxiliary audio, and 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 indicating whether the sink device supports multi-stream audio data for multi-view content A multiview audio support field, a maximum stream count field indicating the number of maximum audio streams that the sink device can handle, and an audio descriptor number field indicating the number of 3D audio descriptors (Number Of Audio Descriptor Field).

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

In the above, preferred embodiments of the present invention have been illustrated and described, but the present invention is not limited to the specific embodiments described above, and is generally used in the technical field to which the present invention belongs without departing from the gist of the present invention claimed in the claims. Various modifications are possible by those skilled in the art of course, and these modifications should not be individually understood from the technical idea or perspective of the present invention.

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

Claims (39)

In the data transmission device,
A packet generator for generating a packet including a first sub packet and a second sub packet for each audio stream; And
Includes; a transmission unit for transmitting the generated packet to the data receiving device,
The first sub-packet and the second sub-packet contain different audio data for first content,
The packet includes a header and a payload,
The header includes a sequence number field indicating an order of packets included in the audio stream and a present field identifying a sub packet,
The payload includes an audio type information field,
The audio type information field includes an auxiliary audio type present field, an auxiliary audio type field, a mixed audio field, and a valid language code field,
The auxiliary audio type present field indicates whether auxiliary audio of audio data exists,
The auxiliary audio type field indicates a type of auxiliary audio for audio data included in each of the plurality of subpackets,
The mixed audio field is a 1-bit field indicating whether main audio data and auxiliary audio data are premixed,
The valid language code field is a 1-bit field indicating whether there is a valid language of the audio data,
When the auxiliary audio type present field is set to a preset first value, the auxiliary audio type present field includes an auxiliary audio type field, and when the auxiliary audio type present field is set to a preset second value, the auxiliary audio type present field is set to a preset second value. The audio type field is ignored,
When the mixed audio field is set to a preset first value, the audio data includes a stream in which the main audio and the auxiliary audio are premixed,
When the valid language code field is set to a preset first value, the audio data includes a language code field. The method of claim 1,
The first sub-packet includes audio data for a non-disabled person,
And the second sub-packet includes audio data for the visually impaired. The method of claim 1,
Wherein the first sub-packet and the second sub-packet contain audio data in different languages. The method of claim 1,
Wherein the first sub-packet includes audio data corresponding to an audio description for the second sub-packet. The method of claim 1,
The packet further comprises a third sub-packet including audio data for a second content different from the first content. The method of claim 5,
The audio data included in the first sub-packet 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 second sub packet is common audio data for the first content and the second content. The method of claim 5,
The packet further includes a fourth sub-packet including audio data for the second content,
The data transmission apparatus, wherein the third sub-packet and the fourth sub-packet contain different audio data. In the data receiving device,
A receiving unit for receiving a packet including a first sub packet and a second sub packet from the data transmission device for each audio stream; And
Including; a parsing unit for parsing the received first sub-packet and the second sub-packet,
The first sub-packet and the second sub-packet contain different audio data for first content,
The packet includes a header and a payload,
The header includes a sequence number field indicating an order of packets included in the audio stream and a present field identifying a sub packet,
The payload includes an audio type information field,
The audio type information field includes an auxiliary audio type present field, an auxiliary audio type field, a mixed audio field, and a valid language code field,
The auxiliary audio type present field indicates whether auxiliary audio of audio data exists,
The auxiliary audio type field indicates a type of auxiliary audio for audio data included in each of the plurality of subpackets,
The mixed audio field is a 1-bit field indicating whether main audio data and auxiliary audio data are premixed,
The valid language code field is a 1-bit field indicating whether there is a valid language of the audio data,
When the auxiliary audio type present field is set to a preset first value, the auxiliary audio type present field includes an auxiliary audio type field, and when the auxiliary audio type present field is set to a preset second value, the auxiliary audio type present field is set to a preset second value. The audio type field is ignored,
When the mixed audio field is set to a preset first value, the audio data includes a stream in which the main audio and the auxiliary audio are premixed,
When the valid language code field is set to a preset first value, the audio data includes a language code field. The method of claim 8,
The first sub-packet includes audio data for a non-disabled person,
And the second sub-packet includes audio data for the visually impaired. The method of claim 8,
And the first sub-packet and the second sub-packet include audio data in different languages. The method of claim 8,
And the first sub-packet includes audio data corresponding to an audio description of the second sub-packet. The method of claim 8,
And the packet further includes a third sub-packet including audio data for second content different from the first content. The method of claim 12,
The audio data included in the first sub-packet 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 second sub-packet is common audio data for the first content and the second content. The method of claim 12,
The packet further includes a fourth sub-packet including audio data for the second content,
The data receiving apparatus, wherein the third sub-packet and the fourth sub-packet contain different audio data. In the data transmission and reception system,
A data transmission device that generates a packet including a first sub packet and a second sub packet for each audio stream and transmits the generated packets to the data reception device; And
Including; a data receiving device for receiving the packet from the data transmission device,
The first sub-packet and the second sub-packet contain different audio data for first content,
The packet includes a header and a payload,
The header includes a sequence number field indicating an order of packets included in the audio stream and a present field identifying a sub packet,
The payload includes an audio type information field,
The audio type information field includes an auxiliary audio type present field, an auxiliary audio type field, a mixed audio field, and a valid language code field,
The auxiliary audio type present field indicates whether auxiliary audio of audio data exists,
The auxiliary audio type field indicates a type of auxiliary audio for audio data included in each of the plurality of subpackets,
The mixed audio field is a 1-bit field indicating whether main audio data and auxiliary audio data are premixed,
The valid language code field is a 1-bit field indicating whether there is a valid language of the audio data,
When the auxiliary audio type present field is set to a preset first value, the auxiliary audio type present field includes an auxiliary audio type field, and when the auxiliary audio type present field is set to a preset second value, the auxiliary audio type present field is set to a preset second value. The audio type field is ignored,
When the mixed audio field is set to a preset first value, the audio data includes a stream in which the main audio and the auxiliary audio are premixed,
When the valid language code field is set to a preset first value, the audio data includes a language code field. delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete In the data transmission method,
Generating a packet including a first sub packet and a second sub packet for each audio stream; And
Transmitting the generated packet to a data receiving device; Including,
The first sub-packet and the second sub-packet contain different audio data for first content,
The packet includes a header and a payload,
The header includes a sequence number field indicating an order of packets included in the audio stream and a present field identifying a sub packet,
The payload includes an audio type information field,
The audio type information field includes an auxiliary audio type present field, an auxiliary audio type field, a mixed audio field, and a valid language code field,
The auxiliary audio type present field indicates whether auxiliary audio of audio data exists,
The auxiliary audio type field indicates a type of auxiliary audio for audio data included in each of the plurality of subpackets,
The mixed audio field is a 1-bit field indicating whether main audio data and auxiliary audio data are premixed,
The valid language code field is a 1-bit field indicating whether there is a valid language of the audio data,
When the auxiliary audio type present field is set to a preset first value, the auxiliary audio type present field includes an auxiliary audio type field, and when the auxiliary audio type present field is set to a preset second value, the auxiliary audio type present field is set to a preset second value. The audio type field is ignored,
When the mixed audio field is set to a preset first value, the audio data includes a stream in which the main audio and the auxiliary audio are premixed,
When the valid language code field is set to a preset first value, the audio data includes a language code field. In the data receiving method,
Receiving a packet including a first sub packet and a second sub packet from a data transmission device for each audio stream; And
Parsing the received first sub-packet and the second sub-packet; Including,
The first sub-packet and the second sub-packet contain different audio data for first content,
The packet includes a header and a payload,
The header includes a sequence number field indicating an order of packets included in the audio stream and a present field identifying a sub packet,
The payload includes an audio type information field,
The audio type information field includes an auxiliary audio type present field, an auxiliary audio type field, a mixed audio field, and a valid language code field,
The auxiliary audio type present field indicates whether auxiliary audio of audio data exists,
The auxiliary audio type field indicates a type of auxiliary audio for audio data included in each of the plurality of subpackets,
The mixed audio field is a 1-bit field indicating whether main audio data and auxiliary audio data are premixed,
The valid language code field is a 1-bit field indicating whether there is a valid language of the audio data,
When the auxiliary audio type present field is set to a preset first value, the auxiliary audio type present field includes an auxiliary audio type field, and when the auxiliary audio type present field is set to a preset second value, the auxiliary audio type present field is set to a preset second value. The audio type field is ignored,
When the mixed audio field is set to a preset first value, the audio data includes a stream in which the main audio and the auxiliary audio are premixed,
When the valid language code field is set to a preset first value, the audio data includes a language code field.

delete delete delete delete

Images