TWI666931B - Data transmitting apparatus, data receiving apparatus and data transceiving system - Google Patents

Abstract

A data transmission device is provided. The data transmission device includes: a packet generator for generating a packet including a first sub-packet and a second sub-packet; and a transmitter for transmitting the generated packet to a data receiving device, and the first One sub-packet and the second sub-packet include different audio data related to the first content.

Description

Data transmitting device, data receiving device and data transmitting system [Cross Reference to Related Applications]

This application claims U.S. Provisional Application No. 61 / 789,803 filed with the U.S. Patent and Trademark Office on March 15, 2013, and U.S. Provisional Application No. 61 / 802,807 filed with the U.S. Patent and Trademark Office on March 18, 2013 And Korean Patent Application No. 10-2014-0025653 filed with the Korean Intellectual Property Office on March 4, 2014, the entire disclosure of which is incorporated herein by reference.

The device, system, and method according to the exemplary embodiments are related to a method and device for transmitting data, and more particularly, a data transmitting device for transmitting and receiving (receiving) multiple audio data about the same content, Data receiving device, data transmission system, method for transmitting data, and method for receiving data.

Recently, with the establishment of a multimedia environment, high-speed cable interface standards for transmitting various data have been proposed. For example, a high-definition multimedia interface (High Definition Multimedia Interface (HDMI) and Mobile High-Definition Link (MHL) provide standards for transmitting image data, audio signals, and control signals in various formats.

However, the prior art audio signal transmission standard does not include an interface surface for transmitting audio data for a visually impaired person or for transmitting multilingual audio data.

Therefore, there is a need for an interface standard for transmitting multiple audio data related to the same content between a source device and a collection tank device.

One or more exemplary embodiments provide an interface standard for transmitting multiple audio data related to the same content between a source device and a collection tank device.

According to an aspect of the exemplary embodiment, there is provided a data transmission device including: a packet generator for generating a packet including a first sub-packet and a second sub-packet; and a transmitter for converting the generated packet Send to data receiving device. The first sub-packet and the second sub-packet include different audio data related to the first content.

The first sub-packet may include audio data for non-disabled persons, and the second sub-packet may include audio data for visually impaired persons.

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

The first sub-packet may include a corresponding packet corresponding to the second sub-packet. Audio description audio information.

The packet may further include a third sub-packet, and the third sub-packet includes audio data about a second content different from the first content.

The audio data included in the first sub-packet may be audio data provided for the first content, and the audio data included in the third sub-packet may be audio provided for the second content. Data, and the audio data included in the second sub-packet may be audio data commonly used for the first content and the second content.

The packet may further include a fourth sub-packet, the fourth sub-packet includes audio data related to the second content, and the third sub-packet and the fourth sub-packet may include different audio data.

According to an aspect of another exemplary embodiment, a data receiving device is provided, including: a receiver for receiving a packet including a first sub-packet and a second sub-packet from the data transmitting device; and a parser for analyzing the data The first sub-packet received and the second sub-packet received are described. The first sub-packet and the second sub-packet include different audio data related to the first content.

The first sub-packet may include audio data for non-disabled persons, and the second sub-packet may include audio data for visually impaired persons.

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

The first sub-packet may include a corresponding packet corresponding to the second sub-packet. Audio description audio information.

The packet may further include a third sub-packet, and the third sub-packet includes audio data related to a second content different from the first content.

The audio data included in the first sub-packet may be audio data provided for the first content, and the audio data included in the third sub-packet may be audio provided for the second content. Data, and the audio data included in the second sub-packet may be audio data commonly used for the first content and the second content.

The packet may further include a fourth sub-packet, the fourth sub-packet includes audio data related to the second content, and the third sub-packet and the fourth sub-packet may include different audio data.

According to an aspect of another exemplary embodiment, a data transmission system is provided, including: a data transmission device for generating a packet including a first sub-packet and a second sub-packet and transmitting the generated packet to data A receiving device; and a data receiving device for receiving the packet from the data transmitting device, and the first sub-packet and the second sub-packet may include different audio data related to the first content.

According to an aspect of another exemplary embodiment, a data transmission device is provided, including: a packet generator for generating an audio metadata packet; and a transmitter for transmitting the generated audio metadata packet To the data receiving device, and the header of the generated audio metadata packet may include an instruction whether to transmit 3D audio field to send 3D audio sample packets.

The header of the generated audio metadata packet may further include a number of audio stream fields containing information about the number of audio streams transmitted.

The header of the generated audio metadata packet may further include a number of view fields containing information about the number of different content transmitted.

The payload of the generated audio metadata packet may include an audio metadata descriptor field containing metadata about a sub-packet of a multi-stream audio sample packet or a multi-stream one-voice sample packet.

The audio metadata descriptor field may include at least one of the following: indicating whether there is an emergency channel field for emergency broadcasting; indicating whether the audio data corresponding to the left-eye image or the right-eye image is included in a multi-view Multi-view field in; language field valid field indicating whether the language of audio data is recognized; supplementary audio field indicating whether there is supplementary audio data; pre-mix indicating whether the main audio data and the supplemental audio data are pre-mixed A supplementary audio field; a supplementary audio type field indicating a type of the supplemental audio data; and a language code field indicating a language code of the audio data.

According to an aspect of another exemplary embodiment, a data receiving device is provided, including: a receiver for receiving an audio relay data packet from a data transmitting device; and a parser for analyzing the received audio relay Data packet. The header of the received audio metadata packet may include a 3D audio field indicating whether to transmit a 3D audio sample packet.

The header of the generated audio metadata packet may further include a number of audio stream fields containing information about the number of audio streams transmitted.

The header of the generated audio metadata packet may further include a number of view fields containing information about the number of different content transmitted.

The payload of the generated audio metadata packet may include an audio metadata descriptor field containing metadata about a sub-packet of a multi-stream audio sample packet or a multi-stream one-voice sample packet.

The audio metadata descriptor field may include at least one of the following: indicating whether there is an emergency channel field for emergency broadcasting; indicating whether to include audio data corresponding to a left-eye image or a right-eye image in more than one Multi-view field in the view; language code valid field indicating whether to identify the language of the audio data; indicating whether there is a supplementary audio valid field supplementing the audio data; indicating the main audio data and whether the supplemental audio data is pre-mixed A mixed supplemental audio field; a supplemental audio type field indicating a type of the supplemental audio data; and a language code field indicating a language code of the audio data.

According to an aspect of another exemplary embodiment, a data transmission system is provided, including: a data transmission device for generating an audio metadata packet and transmitting the generated audio metadata packet to a data receiving device; And a data receiving device for receiving the audio metadata packet from the data transmitting device, a header of the audio metadata packet may include a 3D audio field indicating whether to transmit a 3D audio sample packet.

According to an aspect of another exemplary embodiment, there is provided a data transmission system including: a generator for generating display identification information including information about the nature of audio data supported by a collecting tank device; and a transmitter For transmitting the display identification information to the data receiving device, and the display identification information includes a main / supplementary audio property field containing information about the nature of the main audio and supplementary audio supported by the collection tank device.

The main / supplementary audio nature field may include at least one of the following: an audio mixing field indicating whether the collection tank device supports a combination of main audio and supplemental audio; indicating whether the collection tank device supports supplementary Supplementary audio support field for audio; language support field indicating whether the collection slot device supports audio data in multiple languages; multi-view audio support indicating whether the collection slot device supports multi-stream audio data for multi-view content A field; a maximum stream count field containing the maximum number of audio streams handled by the collection tank device; and an audio descriptor number field containing the number of 3D audio descriptors.

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

According to an aspect of another exemplary embodiment, there is provided a data receiving device including a receiver for receiving a display identification including information about a property supported by a collecting tank device and related to the nature of audio data received from the data transmitting device. Information; and an analyzer for analyzing the received display identification information. The display identification information may include information about the main audio supported by the collection tank device. And supplementary audio information fields.

The main / supplementary audio nature field may include at least one of the following: an audio mixing field indicating whether the collection tank device supports a combination of main audio and supplemental audio; indicating whether the collection tank device supports supplementary Supplementary audio support field for audio; language support field indicating whether the collection slot device supports audio data in multiple languages; multi-view audio support indicating whether the collection slot device supports multi-stream audio data for multi-view content A field; a maximum stream count field indicating the maximum number of audio streams handled by the collection tank device; and an audio descriptor number field containing the number of 3D audio descriptors.

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

According to an aspect of another exemplary embodiment, a data transmission system is provided, including: a data transmission device for generating display identification information including information about the nature of the audio data supported by the collection tank device, and converting the information The generated display identification information is transmitted to the data receiving device. The data receiving device may be used to receive the display identification information from the data transmission device, and the display identification information may include a primary / secondary information including information about the nature of the main audio and supplementary audio supported by the collection tank device. Added audio nature field.

A data transmission method according to another aspect of the exemplary embodiment may include generating a packet including a first sub-packet and a second sub-packet; and transmitting the generated packet to a data receiving device. The first sub-packet and the second sub-packet The package may include different audio materials related to the first content.

According to another aspect of the exemplary embodiment, the data receiving method may include: receiving a packet including a first sub-packet and a second sub-packet from a data transmission device; and analyzing the received first sub-packet and the data packet. Received second sub-packet. The first sub-packet and the second sub-packet may include audio data associated with an independent audio channel and related to the first content.

The data transmission method according to another aspect of the exemplary embodiment may include: generating an audio metadata packet; and transmitting the generated audio metadata packet to a data receiving device. The header of the generated audio metadata packet may include a 3D audio field indicating whether to transmit a 3D audio sample packet.

Yet another aspect of the data receiving method according to the exemplary embodiment may include: receiving an audio metadata packet from a data transmitting device; and analyzing the received audio metadata packet. The header of the received audio metadata packet may include a 3D audio field indicating whether to transmit a 3D audio sample packet.

According to an aspect of another exemplary embodiment, there is provided a data transmission method including: generating display identification information including information about the nature of audio data supported by a collecting tank device; and transmitting the display identification information to Data receiving device. The display identification information may include a main / supplementary audio property field containing information about the nature of the main audio and supplementary audio supported by the collection tank device.

The data receiving method according to another aspect of the exemplary embodiment may include: Receiving display identification information including information about the nature of the audio data supported by the collection tank device from the data transmission device; and analyzing the received display identification information. The display identification information may include a main / supplementary audio property field containing information about the nature of the main audio and supplementary audio supported by the collection tank device.

According to another aspect of an exemplary embodiment, a data transmission device includes: a packet generator for generating a packet including a first sub-packet and a second sub-packet; and a transmitter for transmitting the generated packet . The first sub-packet and the second sub-packet may include audio data associated with an independent audio channel and related to the first content.

The first sub-packet may include a first independent audio channel for transmitting audio data for non-disabled persons, and the second sub-packet may include a second independent audio channel for transmitting audio data for visually impaired persons aisle.

The first sub-packet may also include a first independent audio channel for transmitting audio data in a first language, and the second sub-packet may include a second independent audio channel for transmitting audio data in a second language.

The first sub-packet may include audio data corresponding to an audio description related to the second sub-packet. In addition, the packet may further include a third sub-packet, and the third sub-packet includes audio data related to a second content different from the first content.

The audio data may be included in the audio data provided specifically for the first content. The audio data included in the first sub-packet included in the third sub-packet may include audio data provided specifically for the second content. The audio data included in the second sub-packet may include audio data commonly used for the first content and the second content. The packet may further include a fourth sub-packet, the fourth sub-packet includes audio data related to the second content, and the third sub-packet and the fourth sub-packet may include associated audio information Audio data for the channel.

According to various aspects of the exemplary embodiments, an interface standard is provided for transmitting multiple audio data related to the same content between a source device and a collection tank device.

100-1, 100-2, 100-3‧‧‧‧ data transmission device

110‧‧‧ packet generator

120‧‧‧ transmitter

130‧‧‧ generator

200-1, 200-2, 200-3‧‧‧ data receiving device

210‧‧‧ Receiver

220‧‧‧Parser

230‧‧‧ Analyzer

310‧‧‧source device

320‧‧‧ collection tank device

1000-1, 1000-2, 1000-3‧‧‧‧ Data Transmission System

S1710 ~ S1720‧‧‧step

S1810 ~ S1820‧‧‧step

S1910 ~ S1920‧‧‧ steps

S2010 ~ S2020‧‧‧step

S2110 ~ S2120‧‧‧step

S2210 ~ S2220‧‧‧step

The above and / or other aspects of the inventive concept will be more apparent from the following description of the exemplary embodiments in conjunction with the accompanying drawings.

FIG. 1A illustrates a single audio stream.

FIG. 1B illustrates a multi-audio stream.

FIG. 2A is a block diagram illustrating a multi-window or multi-screen source device that transmits multiple audio data to a collection tank device.

FIG. 2B is a block diagram illustrating the transmission of a plurality of audio data related to a quick preview or picture-in-picture (PIP) view to a quick playback source device of a collection tank device.

FIG. 2C is a block diagram illustrating a split-screen multi-player game source device that transmits multiple audio data to a collection tank device.

FIG. 3 is a block diagram for explaining data transfer between a collecting tank device and a source device for displaying split screen support information.

FIG. 4 is a block diagram illustrating the payload of four transmitted multi-audio sample packets.

5A, 5B, and 5C illustrate types of split screens associated with audio streams according to an exemplary embodiment.

6 and 7 illustrate transmission timings of 3D audio signals.

FIG. 8 illustrates a multi-stream audio sample packet scenario according to an exemplary embodiment.

FIG. 9 is a block diagram illustrating a data transmission system according to an exemplary embodiment.

FIG. 10 is a block diagram illustrating a data transfer device according to another exemplary embodiment.

FIG. 11 is a block diagram illustrating a data receiving apparatus according to an exemplary embodiment.

FIG. 12 is a block diagram illustrating a data transmission system according to another exemplary embodiment.

FIG. 13 is a block diagram illustrating a data transfer device according to another exemplary embodiment.

FIG. 14 is a block diagram illustrating a data receiving apparatus according to another exemplary embodiment.

FIG. 15 is a block diagram illustrating a data transmission system according to another exemplary embodiment.

FIG. 16 is a block diagram illustrating a data transfer device according to another exemplary embodiment.

FIG. 17 is a block diagram illustrating a data receiving apparatus according to another exemplary embodiment.

18A, 18B, and 18C illustrate various data transmission formats for transmitting four-view video content in a 3D interleaved format.

FIG. 19 is a flowchart of a data transmission method according to an exemplary embodiment.

FIG. 20 is a flowchart of a data receiving method according to an exemplary embodiment.

FIG. 21 is a flowchart of a data transfer method according to another exemplary embodiment.

FIG. 22 is a flowchart of a data receiving method according to another exemplary embodiment.

FIG. 23 is a flowchart of a data transfer method according to another exemplary embodiment.

FIG. 24 is a flowchart of a data receiving method according to another exemplary embodiment.

In the following description, the same drawing reference numerals are used for the same parts, even in different drawings. The matters defined in the present specification, such as detailed construction and components, are provided to assist in a comprehensive understanding of the exemplary embodiments. The method steps and system components are illustrated in the figures by using conventional symbols to show only specific relevant details in order to facilitate understanding of the exemplary embodiments. Well-known functions or constructions are not described in detail because they would obscure the exemplary embodiments with unnecessary details. Relational terms such as first and second and the like are used to distinguish one component from another. These terms do not necessarily imply any actual relationship between these components Or order.

The exemplary embodiments are applicable to, but not limited to, various cable interface transmission standards, such as HDMI, MHL, and similar cable interface standards.

In describing the exemplary embodiments, the following documents will be referenced and incorporated herein in their entirety.

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

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

IEC, IEC 62574 version 1.0, "Audio, video and multimedia systems-General channel assignment of multichannel audio", April 7, 2001.

In Table 1, terms used to describe the exemplary embodiments are defined.

1A and 1B illustrate a single audio stream and a multi-audio stream.

FIG. 1A shows a single audio stream for transmitting a plurality of audio data related to at least one video data. The plurality of audio data is transmitted by a single stream. In a single stream shown in FIG. 1A, all stream data is packetized to share the same packet stream ID.

FIG. 1B shows a multi-audio stream transmitting multiple single AV streams. Multi-audio streaming transmits multiple single AV streams in packets. A unique packet stream ID is assigned to each single AV stream. Video data from multiple single AV streams are interdependent.

Each audio stream of a multi-audio stream transmits audio data for two audio channels. Each audio in single-view mode can be connected to a preset video stream, and audio in dual-view mode can be connected to left or right video (or both). In addition, one or more supplemental audio options can be transmitted. Complementary audio options can include split screen tagging, language instructions, and audio instructions for people with visual / hearing impairments.

Split screen source device provides different audio data Viewing options that are labeled and identified and assigned to one or more windows displayed on the display screen of the collection tank device. Split screen source devices are used in PIP viewing, quick preview viewing, split screen multi-player games, and more. The window is a unique display image displayed in the area of the display screen of the collection tank device.

A split screen (or multi-window) can be an optional element used in conjunction with multiple audio data. The split screen mode is a configuration in which the screen is split and a collection slot device label is provided. The audio stream is mapped to a specific window displayed on the display screen of the collection tank device.

2A, 2B, and 2C are block diagrams of a source device that transmits a plurality of audio data to a collection tank device.

FIG. 2A is a block diagram illustrating a multi-window or multi-screen source device transmitting a plurality of audio data to a collection tank device according to an exemplary embodiment. 2B is a block diagram illustrating a fast play source device that transmits a plurality of audio data related to a quick preview or a PIP view to a collection tank device according to an exemplary embodiment. FIG. 2C is a block diagram illustrating a split screen multi-player game source device that transmits a plurality of audio data to a collection tank device according to an exemplary embodiment. The user of the collection tank device can select and listen to the desired audio.

FIG. 3 is a block diagram for explaining data transfer between a collecting tank device and a source device for displaying split screen support information.

The source device 310 transmits the manufacturer-specific information frame, the multi-audio sample packet, and the multi-audio metadata packet to the collection slot device.

A multi-audio sample packet includes multiple audio streams. Multi-audio metadata packets include settings for each audio stream related to the video stream. Multi-audio metadata packets can also include supplemental audio information. The vendor-specific information frame includes a multi-view mode indication (ie, type) of the content being transmitted.

The collecting tank device 320 transmits the expansion component capability register to the source device to provide information about the multi-audio mode supported by the collecting tank device.

Supplementary multi-audio supports the transmission of auxiliary audio tracks (for example, multilingual audio tracks, audio descriptions for visually impaired persons, or audio for hearing impaired persons). Can send up to 16 stereo audio streams simultaneously.

TMDS sending and encoding

Data Platform Packet

3D Audio Sample Packet

3D audio is defined as audio in which a speaker can be placed at a predetermined position in a 3D space for each 3D audio standard (for example, 10.2ch, 22.2ch, 30.2ch, etc.). A 3D audio sample packet consists of one audio sample containing 9 to 32 audio channels.

The 3D audio stream includes up to 32 audio channels (or more) and is transmitted via consecutive packets in the data aggregation chapter. Each packet includes up to 8 audio channels. The configuration of the sub-packet is determined by the sequence number in the header and the sample existence bit.

The sequence number field (sequence_number) indicates the order of the current packet. Since multiple 3D audio sample packets include a single 3D audio sample packet, this field is required to correctly identify the packet order.

The other header fields and sub-packet structure are the same as the audio sample packet structure shown in the MHL 2.0 specification.

Table 3-3D Audio Sample Packet

Multi-Audio Sample Packet

A multi-audio sample packet consists of four audio samples, and each audio sample is associated with a separate audio stream. When the MHL source element transmits more than four independent audio streams at the same time, these continuous audio streams are transmitted in a series of consecutive multi-audio sample packets. The sequence number defined in the packet header identifies each of the multi-audio sample packets and indicates the order of the current packets within the packet array. The configuration of the sub-packet is determined by the serial number in the header and the bit existence of the sample, as described in detail below about the multi-audio data packetization.

For each sub-packet (or audio stream), a descriptor field is provided in the multi-audio metadata packet, and the descriptor field describes the view mode (ie, single view or multi-view). In addition, provide optional information (e.g., split screen tagging, language codes, audio for visually impaired people, etc.).

The sequence number field (sequence_number) stores the serial number of the current multi-audio sample packet when more than four audio streams are transmitted from the source to the MHL collection slot. If this field is set to 0, the packet can include the first four audio streams in the corresponding sub-packet. If this field is set to 1, the packet can include a second set of four audio streams in the corresponding sub-packet. In a similar manner, when this field is set to 2 or 3, the packet may include the third or fourth group of four audio streams. When the sequence_number is set to 0, the audio stream carried in the sub-packet 0 may be represented as a preset audio stream.

The stream presence field (stream_present.spX) indicates whether the sub-packet X contains audio samples of the stream X.

The stream flat field (stream_flat.spX) indicates whether the sub-packet X represents Sample "flatline" of stream X, the stream flat field is only valid if "stream_present.spX" is also set.

The other header fields and sub-packet structures are the same as the audio sample packets described in the MHL 2.0 specification.

FIG. 4 is a block diagram illustrating the payload of four transmitted multi-audio sample packets.

As shown in FIG. 4, when transmitting four multi-audio sample packets, 16 audio streams can be transmitted. Because the serial number consists of 2 bits, it can pass 16 audio strings flow.

3D Audio Metadata Packet

Use 3D audio metadata packets to send auxiliary data describing the role of 3D audio data. When the MHL source sends 3D audio sample packets, the MHL source sends 3D audio metadata packets at least once every two video fields.

The following table shows 3D audio metadata packets.

Table 9-3D_CA (3D audio channel / speaker assignment) field (3D_CAST = 0x02 (up to 22.2ch))

Table 10-3D_CA (3D audio channel / speaker assignment) field (3D_CAST = 0x03 (up to 30.2ch))

Multi-audio metadata packets

Use multi-audio metadata packets to send auxiliary data describing the effect of multi-audio streaming. Multi-audio packets are used to describe the type of view and auxiliary audio options for each audio stream transmitted in a multi-audio sample packet.

When an MHL source sends a multi-audio sample packet, the MHL source sends a multi-stream audio metadata packet at least once every two video fields.

The following table shows multi-audio metadata packets.

The view type field (MA_View_Type) indicates the associated view mode of the multi-audio stream, such as single-view mode or multi-view mode, as shown in Table 11.

The sequence number field (Sequence_Number) indicates the packet number or serial number of the current multi-audio metadata packet. This field is used to identify up to four unique multi-audio metadata packets. This sequence number field uniquely links each multi-audio metadata packet to a multi-audio sample packet with the same Sequence_Number.

The audio stream number field (Num_Audio_Streams) indicates the total number of audio streams transmitted by multiple audio sample packets.

When the split screen valid field (SC_Valid) is set to 1, split screen labeling is supported, and the split screen type field (Split_Screen_Config) is defined in the next 7 bits. If the split screen valid field (SC_Valid) is set to 0, the split screen tagging is not supported or specified, and the following 7 bits are reserved for other purposes.

The split screen type field (Split_Screen_Config) indicates the split screen type associated with the audio stream defined by the current descriptor. The selectable split screen types are listed in Table 13. The split screen type field is valid only when SC_Valid is set to 1.

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

The following table shows the multi-audio descriptor definitions.

5A, 5B, and 5C illustrate types of split screens associated with audio streams according to an exemplary embodiment.

Split screen tag field (Split_Screen_Tag) setting The specific window (as defined by Split_Screen_Config) associated with the audio stream indicated by the audio descriptor. Details are shown in Table 15. The split screen label field is only valid when SC_Valid is set to 1, otherwise, the MHL collection slot ignores this field.

An associated view identification field (Associated_View_ID) indicates a specific view associated with the audio stream indicated by the current multi-audio descriptor. The meaning of this field depends on the value of MA_View_Type. Details are shown in Table 14.

When the valid language code field (LC_present) is set to 1, the current descriptor includes a valid Language_Code field in subsequent bytes.

When the mixed audio field (Mixed_Audio) is set to 1, the corresponding audio stream contains a pre-mixed stream of general audio and supplementary audio as indicated by Suppl_Audio_Type.

When the SAT presence field (SAT_present) is set to 1, the current descriptor includes a valid Suppl_Audio_Type field in the next 4 bits.

The supplemental audio feature field (Suppl_Audio_Type) indicates the type of supplemental audio corresponding to the audio stream. Details of the supplemental audio feature fields are shown in Table 16. The supplemental audio feature field is valid only when SAT_present is set to 1, otherwise, the MHL collection slot ignores this field.

The Language Code field (Language_Code) indicates the ISO 639-defined language code corresponding to the audio stream. This field is only valid when the LC_present field is set to 1, otherwise, the MHL collection slot will ignore this field.

Multi-audio action indicator

The source component uses a vendor-specific information frame (VSIF) to indicate the view mode to the collection slot component. The format of the VSIF is shown in Table 17.

Table 17-Vendor Specific Information Frame Packet

The MHL_MULTI_VIEW field indicates the multi-view mode. Details of the MHL_MULTI_VIEW field are shown in Table 18.

Video

3D video descriptors supported by 3D

Table 19-3D Video Descriptor Data Format

Each supported 3D video mode is defined by a 3D video descriptor.

When MV_SUPP is set to 1, the component supports 3D video format for multi-view video streaming.

Audio

Channel / speaker assignment

When the MHL collection tank is capable of receiving 3D audio data, the 3D channel speaker allocation descriptors described in Tables 38 to 40 are used to indicate the configuration of the attached speakers. The current speaker assignment for the 3D audio data transmitted from the MHL source is indicated in the 3D_CA field of the 3D audio metadata packet, as shown in Tables 8 to 10.

3D audio data packetization

Each sub-packet of the 3D audio sample packet does not contain a frame in the IEC 60958 format or a frame in the IEC 60958 format. If the MHL source needs to downmix the 3D audio stream and the downmixed audio stream is also a 3D audio stream, the 3D audio sample packet is used to transmit the 3D audio stream. If the MHL collection slot does not support 3D audio features, the MHL source does not send 3D audio sample packets except for 3D audio metadata packets.

Depending on the number of channels, many different sub-packet layouts are available. Table 20 To Table 22 show the 3D audio packet layout when using 12, 24, or 32 channels, respectively.

Table 22-3D audio sample packet layout for 32 channels

There are four sample_present bits in the 3D audio sample packet header, one for each of the sub-packets. Each sample_present bit indicates whether the sub-packet contains 3D audio samples. In addition, there are four sample_flat.spX bits, which are set if the MHL source cannot obtain useful audio data during the time period represented by the sample. This can occur during sample rate changes or temporary streaming interruptions.

The continuous 3D audio sample packet can be used to carry a 3D audio sample of 9 to 32 channels (ie, 5 to 16 IEC 60958 frames) containing L-PCM audio.

The first packet of a 3D audio sample is completely filled with 8 audio channels and has Set the number field to 0. The serial number is incremented by one for each additional packet within the same 3D audio sample. The final packet depends on the total number of channels of the 3D audio sample and contains 8 or less audio channels.

For a 3D audio sample packet, there are only five valid configurations of the sample_present bit.

6 and 7 illustrate transmission timings of 3D audio signals.

In particular, Figures 6 and 7 illustrate the transmission of three 8-channel 2D audio signal samples at horizontal blanking intervals. With 24 channels of 3D audio signals, one sample is transmitted during the same time period.

Multi-audio data packetization

MHL allows MHL sources to simultaneously transmit many audio streams for a single AV stream. The multiple audio streams are associated with a single-view or multi-view video stream (eg, a multi-view game with different audio data in each view). Auxiliary audio modes are also available, such as split screen tagging (i.e. different parts of the screen are tagged Tag and associated with its own audio stream), language code, or audio for the visually / hearing impaired. Each audio stream is associated with only one view mode and contains 2 audio channels.

Each sub-packet of a multi-stream audio sample packet does not contain a frame defined by IEC 60958 or a block defined by IEC 61937, or a frame defined by IEC 60958 or a block defined by IEC 61937.

When more than four audio streams are transmitted, two or more consecutive multi-audio sample packets are used to transmit the multiple audio streams. The Sequence_Number field is used to identify the order of each packet in the packet array. MHL sources can transmit up to 16 independent audio streams simultaneously in a single AV stream.

Tables 25 and 26 show examples of multi-audio sample packets and multi-audio metadata packet layouts when the MHL source transmits four audio streams in a single-view video stream. Multi-audio metadata packets describe the characteristics (supplementary 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 transmits eight audio streams in a dual-view video stream. Multi-audio metadata packets describe the characteristics (associated views, supplementary information, language) of each audio stream.

Tables 29 and 30 show examples of multi-audio sample packets and multi-audio metadata packet layouts when the MHL source transmits six audio streams (where the split-screen tagging option is enabled for single-view video streaming).

Audio for HI Audio streaming for the hearing impaired

Audio for VI: Audio streaming for the visually impaired

Table 27-Example of Multi-Audio Metadata Packet Layout (Related Packets in Figure 26)

Audio for HI: Audio streaming for the hearing impaired

Audio for VI: Audio streaming for the visually impaired

Table 29-Examples of Multi-Audio Metadata Packet Layout (Related Packets in Figure 28)

Audio for HI: Audio streaming for the hearing impaired

Audio for VI: Audio streaming for the visually impaired

3D audio metadata packetization

When a 3D audio stream is transmitted, a 3D audio metadata packet is transmitted at least once every two video fields.

When the transmission of a new 3D audio stream begins or after any changes to the 3D audio stream indicated by the 3D audio metadata packet and the audio information frame, no later than after the first affected non-silent audio sample A video frame to send a modified 3D audio metadata packet. This happens just before transmitting the first affected audio sample.

3D audio metadata packet transmission can occur at any time during the data idle period, including any horizontal or vertical blanking period.

When 3D audio data is being streamed, the MHL collection slot ignores the CC and CA fields in the audio information frame, and instead references the 3D_CC and 3D_CA fields in the 3D audio metadata packet.

Multi-audio metadata packetization

When sending multiple audio streams, send multiple audio metadata packets at least once every two video fields.

When the transmission of a new multi-audio stream begins or after any change in the multi-audio stream indicated by the multi-audio metadata packet and the audio information frame, no later than after the first affected non-silent audio sample A video frame to send a modified multi-audio metadata packet. This happens just before transmitting the first affected audio sample.

Multi-audio metadata packet transmission can occur at any time during the data idle period, including any horizontal or vertical blanking period.

WRITE_BURST use for 3D / multi audio support

Support for 3D audio mode is indicated and formatted using the sequence transferred by WRITE_BURST, as shown in Table 31 and Table 37.

Table 33-3D Audio Descriptors Set to Audio Format Codes 9 to 13

Table 35-3D Audio Descriptor (Extended) for Audio Format Code Set to 15

Table 37-3D Channel Speaker Assignment Descriptors for 10.2 Channels

Bold bits are designated speakers associated with 10.2 channels.

Bold bits are designated speakers associated with 22.2 channels.

Table 39-3D Channel Speaker Assignment Descriptors for 30.2 Channels

Bold bits are designated speakers associated with 30.2 channels.

Link control bus

Component register change interrupt

Table 41-Register Change Interrupt Register Details

3D_AUD_REQ is used by the MHL source component to request 3D audio support information from the MHL collection slot.

BURST_ID code

3D_AD and 3D_CSAD are used by the MHL collection slot to indicate support for audio expansion.

Control and configuration

Expansion component capacity register

The collection tank device can provide an expansion component capability register to the source device. In other words, the source device can read the expansion component capability register of the collection tank device.

As shown in Table 43, the address of the MHL-specific expansion component capability register 0x85 can be used to indicate the multi-audio mode supported by the collection tank device.

Multi-audio mode

Each MHL collection slot element indicates a specific multi-audio mode supported by the collection slot element in a MULTI_AUD_MODE register.

The MULTI_AUD_MODE register includes a split screen audio field indicating whether the collection slot device supports the reception and processing of multi-audio data related to the split screen.

If the component cannot support multi-view video streaming, the MULTI_AUD_MODE register field is set to 0.

Multi-stream audio

An exemplary embodiment of multi-stream audio transmission will now be described. Multi-stream audio transmission specifications can be applied to various wired / wireless transmission interfaces including HDMI and MHL.

The source device according to an exemplary embodiment can transmit 4 audio streams simultaneously. All audio streams share a single info frame about multi-stream audio sample packets.

The wired interface according to the exemplary embodiment can support single-view video streaming (e.g., multi-lingual support, audio for visually / hearing impaired, etc.), and this support can be achieved by modifying audio metadata packets Or modify the HDMI audio data block to execute.

For example, as shown in Table 45, multi-stream audio can support multiple languages, and audio can support 2 channels.

Situation

FIG. 8 illustrates a multi-stream audio sample packet scenario according to an exemplary embodiment.

When a multi-stream audio sample packet includes four sub-packets, the following scenarios are supported:

First, when a single television program is transmitted with a single-view audio description, stream 0 may include a normal audio signal, and stream 1 may include an audio description signal for a visually impaired person.

Second, when a single view supports two languages, the two audio signal streams of the supported languages are transmitted along with the corresponding audio description. For example, if English and Korean are supported, stream 0 may include a normal Korean audio signal, stream 1 may include a Korean audio description signal for the visually impaired, and stream 2 may include a normal English audio signal. And Stream 3 may include an English audio description signal for a visually impaired person.

Third, in a single view, one audio signal stream in one language and two description signals for visually impaired persons in two different languages can be transmitted. For example, Stream 0 may include Korean or English normal audio signals, Stream 1 may include Korean audio description signals for visually impaired persons, and Stream 2 may include English audio description signals for visually impaired persons.

Fourth, the source device can transmit multi-view audio signals. If multiple views are supported, the audio signal can be transmitted in one transmission stream for each view. Multiple views include first and second independent views, and each view provides independent content.

Fifth, for each view, two languages can be supported. An audio signal stream in a first language about a first view, an audio signal stream in a second language about a first view, an audio signal stream in a first language about a second view, and a first Audio streaming in two languages. If English and Korean are supported languages, stream 0 may include a Korean audio signal on the first view, stream 1 may include an English audio signal on the first view, and stream 2 may include Korean on the second view. An audio signal, and stream 3 may include an English audio signal regarding the second view.

Sixth, when dual views are supported, one view can further transmit audio description signals for visually impaired persons. An audio signal stream about the first view, a normal audio signal stream about the second view, and an audio description signal stream for the visually impaired person about the second view may be transmitted. Stream 0 may include an audio signal about the first view, stream 1 may include an audio signal about the second view, and stream 3 may include an audio description signal about the second view.

Fourth, a stream can be used to transmit a common audio signal. A common audio signal stream for the first and second views, an audio stream dedicated to the first view, and an audio stream dedicated to the second view may be transmitted. In this case, the receiving end is multiplexed and outputs a common audio stream and a dedicated audio stream. This situation can be applied to travel play. For example, stream 0 may include common audio signals (e.g., background sound, process guidance voice, etc.) regarding the first and second views, stream 1 may include audio signals dedicated to the first view, and stream 2 may include an audio signal dedicated to the second view.

FIG. 9 is a block diagram illustrating a data transmission system 1000-1 according to an exemplary embodiment.

Referring to FIG. 9, a data transmission system 1000-1 according to an exemplary embodiment includes a data transmission device 100-1 and a data reception device 200-1.

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

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

The first sub-packet and the second sub-packet include different audio data related to the first content.

The data transmitting device 100-1 and the data receiving device 200-1 will now be described in more detail.

FIG. 10 is a block diagram illustrating a data transfer device 100-1 according to an exemplary embodiment.

Referring to FIG. 10, a data transmission device 100-1 according to an exemplary embodiment includes a packet generator 110 and a transmitter 120.

The packet generator 110 generates a packet including a first sub-packet and a second sub-packet. Packet. The first sub-packet and the second sub-packet include different audio data related to the first content.

The transmitter 120 transmits the generated packet to the receiving device 200-1. The first sub-packet may include audio data for non-disabled persons, and the second sub-packet may include audio data for visually impaired persons.

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

The first sub-packet may include audio data corresponding to an audio description about the second sub-packet.

The packet may further include a third sub-packet, and the third sub-packet includes audio data about a second content different from the first content.

The audio data included in the first sub-packet may be audio data provided for the first content, and the audio data included in the third sub-packet may be audio provided for the second content. Data, and the audio data included in the second sub-packet may be common audio data about the first content and the second content.

In addition, the packet may further include a fourth sub-packet, the fourth sub-packet includes audio data about the second content, and the third sub-packet and the fourth sub-packet may include different audio data.

FIG. 11 is a block diagram illustrating a data receiving apparatus 200-1 according to an exemplary embodiment.

11, a data receiving device 200-1 according to an exemplary embodiment includes a receiver 210 and a parser 220.

The receiver 210 receives a packet including a first sub-packet and a second sub-packet from the data transmission device 100-1. The first sub-packet and the second sub-packet may include different audio data related to the first content.

The parser 220 is a component for parsing the received first sub-packet and the received second sub-packet.

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

The first sub-packet may include audio data corresponding to an audio description about the second sub-packet.

The packet may further include a third sub-packet, and the third sub-packet includes audio data about a second content different from the first content.

The audio data included in the first sub-packet may be audio data provided for the first content, and the audio data included in the third sub-packet may be audio provided for the second content. Data, and the audio data included in the second sub-packet may be common audio data related to the first content and the second content.

In addition, the packet may further include a fourth sub-packet, the fourth sub-packet includes audio data about the second content, and the third sub-packet and the fourth sub-packet may include different audio data.

Audio metadata packet

The source device sends an audio metadata packet to the collection slot device according to the audio specifications. The header of the audio metadata packet may have the following structure.

The description of each field is as follows.

If the 3D audio field (3D_AUDIO) [1 bit] is set to 1, the audio metadata packet includes a 3D audio channel count field (3D_CC), channel / speaker allocation information field, and audio channel allocation standard type (ACAST) Field. The ACAST field can be set to 1 when the source sends 3D audio packets.

The number of views field (NUM_VIEWS) [2 bits] indicates the number of views. If NUM_VIEWS is set to 0, single-view video streaming is supported. If NUM_VIEWS is set to 1, multi-view video streaming is supported. This mode is permitted only when 3D_DualView is set to 1 in VSIF. Keep the remaining NUM_VIEWS values for future use.

Audio stream number field (NUM_AUDIO_STR) [2 bits] indicates the number of audio streams. If NUM_AUDIO_STR is set to 1, 10, or 11, the audio metadata packet includes up to four audio metadata descriptions corresponding to the audio stream Scribe symbol.

Table 47 indicates the payload of audio metadata packets for 3D audio. If 3D_Audio is set to 1, the metadata packet payload has the following structure.

The 3D_CC field indicating the 3D audio channel count information and the ACAST field indicating the type of audio channel allocation standard are provided by the source.

Table 49 shows the audio channel according to the 3D_CC value, and Table 50 indicates the audio channel allocation standard type according to the ACAST field value.

Table 51 shows the payload of audio metadata packets for multi-stream audio. If 3D_Audio is set to 0, the metadata packet payload has the following structure.

As illustrated in Table 51, the payload of the audio metadata packet includes 5 bytes for the audio metadata descriptor. Audio metadata descriptor (4 fields, 5 bytes each) indicates the audio metadata about sub-packet X in the multi-stream audio sample packet or the one-voice audio sample packet about the multi-stream Audio metadata for subpacket X in. The structure of the audio metadata descriptor will be described later.

The description of each field is as follows.

When the Emergency Channel field (1 bit) is set to 1, the emergency warning audio data is transmitted corresponding to the audio stream. The receiving device can be commanded A script or the like notifies the existence of an emergency broadcast, and an emergency warning audio signal received through selection of audio can be output to a user.

When the Multiview_Left [1 bit] is set to 1, the left stereo image mapping corresponding to the audio stream and the 3D video format is mapped. If Multiview_Left is set to 0, the field is valid only when NUM_VIEWS is set to 1.

When Multiview_Right is set to 1, the corresponding audio stream is mapped to the right stereo image of the 3D video format. When Multiview_Right is set to 0, the fields are valid only when NUM_VIEWS is set to 1.

When the language code valid field (LC_Valid) [1 bit] is set to 1, the language code is valid and the language corresponding to the audio stream is recognized. Otherwise, the language corresponding to the audio stream is considered unspecified.

When the supplemental audio valid field (Suppl_A_Valid) [1 bit] is set to 1, the corresponding audio stream includes a supplemental audio track indicated by Suppl_A_Type.

When the pre-mixed supplementary audio field (Suppl_A_Mixed) [1 bit] is set to 1, the corresponding audio stream may include a pre-mixed supplementary audio track indicated by the main audio component and Suppl_A_Type. The bit is valid only when Suppl_A_Valid is set to 1.

The supplemental audio type field (Suppl_A_Type) [3 bits] indicates the supplementary audio type defined in Table 53. The field is valid only when Suppl_A_Valid is set to 1. Table 53 indicates the description of the supplemental audio type field value.

Language (Code) [3 bytes] identifies the language of the corresponding audio stream. The language code is defined by ISO639. In addition, three character codes are provided, and the last character code is the same as the last byte of the audio metadata descriptor X (Audio_Metadata_Descriptor_X). This field is valid only when LC_Valid is set to 1.

FIG. 12 is a block diagram illustrating a data transmission system 1000-2 according to another exemplary embodiment.

Referring to FIG. 12, a data transmission system 1000-2 according to an exemplary embodiment includes a data transmission device 100-2 and a data reception device 200-2.

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

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

The header of the audio metadata packet includes a 3D audio field indicating whether to transmit a 3D audio sample packet.

The configuration of the data transmitting device 100-2 and the data receiving device 200-2 and the configuration of the audio metadata packet will be described in more detail.

As shown in FIG. 13, the data transmission device 100-2 according to another exemplary embodiment includes a packet generator 110 and a transmitter 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 transmitter 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 an audio stream number field (an audio stream number field) containing information about the number of audio streams.

The header of the generated audio metadata packet may further include a view number field (number of views field) containing information about the number of different contents transmitted.

The payload of the generated audio metadata packet may include an audio metadata descriptor field containing metadata about a multi-stream audio sample packet or a sub-packet of a multi-stream one-voice audio sample packet.

The audio metadata descriptor field includes at least one of the following: indicating whether there is an emergency channel field for emergency broadcasting; indicating whether the audio data corresponding to the left-eye image or the right-eye image is included in the multi-view Multi-view field of; a language code valid field indicating whether the language of the audio data is identified; a supplementary audio valid field indicating whether there is a supplementary audio data; a premixed supplement indicating whether the main audio data and the supplemental audio data are premixed An audio field; a supplemental audio type field indicating the type of the supplemental audio data; and a language indicating the audio data The language code field for the code.

FIG. 14 is a block diagram illustrating a data receiving apparatus 200-2 according to another exemplary embodiment.

Referring to FIG. 14, a data receiving device 200-2 according to an exemplary embodiment includes a receiver 210 and a parser 220.

The receiver 210 is used for receiving audio metadata packets from the data transmission device 100-2. The header of the audio metadata packet includes a 3D audio field indicating whether to transmit a 3D audio sample packet.

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

In addition, the header of the audio metadata packet may further include an audio stream number field (number of audio streams field) containing information on the number of received audio streams.

The header of the audio metadata packet may further include a view number field (number of views field) containing information about the number of different content received.

The payload of the audio metadata packet may include an audio metadata descriptor field indicating metadata about a multi-stream audio sample packet or a sub-packet of a multi-stream one-voice audio sample packet.

The audio metadata descriptor field may include at least one of the following: indicating whether there is an emergency channel field for emergency broadcasting; indicating whether the audio data corresponding to the left-eye image or the right-eye image is included in a multi-view Multi-view field in; language field valid field indicating whether to recognize the language of audio data; indicating whether it exists Supplementary audio effective field for supplementary audio data; a premixed supplementary audio field indicating whether the main audio data and the supplemental audio data are pre-mixed; a supplemental audio type field indicating the type of the supplemental audio data; and an indication of audio data The language code field for your language code.

Audio data block

Table 54 describes the audio data blocks of the extended display identification data (EDID). As shown in Table 54, the portions regarding bytes 3 to 4 in Table 54 are redefined.

Delete the short audio descriptor (SAD) for multi-stream audio and use the normal SAD defined in EDID instead. Depending on the added features, up to two channels can be transferred.

Table 55 shows the configuration of the blocks replacing bytes 3 to 4 of the above-mentioned audio data block.

The description of each field is as follows.

When the emergency channel field (Supports_MS_Emergency) [1 bit] is set to 1, the collecting tank device supports receiving and processing emergency warning audio channels. When Supports_MS_Emergency is set to 0, the collection tank device does not support the above operations.

When the Audio Mixing Field (Supports_MS_Mix) [1 bit] is set to 1, the collection tank device supports the combination of main audio and supplemental audio. When Supports_MS_Mix is set to 0, the collection tank device does not support the combination and only Supports reproduction of mixed audio.

When the Supplemental Audio Support field (Supports_MS_Supple) [1 bit] is set to 1, the collection slot device supports multi-stream audio with supplemental audio tracks for visually / hearing impaired persons. When Supports_MS_Supple is set to 0, the collection tank device does not support supplementary audio tracks for visually / hearing impaired persons.

When the language support field (Supports_MS_Lang) [1 bit] is set to 1, the collection slot device supports multi-stream audio with audio streams in various languages. When Supports_MS_Lang is set to 0, the collection slot device does not support audio streaming in various languages.

When the multi-view audio support field (Supports_MS_MultiView) [1 bit] is set to 1, the collection slot device supports multi-stream audio for multi-view video streaming. When Supports_MS_MultiView is set to 0, the collection slot device does not support multi-stream audio for multi-view video streaming.

The maximum stream count field (Max_Stream_Count-1) [2 bits] indicates the maximum number of audio streams handled by the collection tank device. The field Max_Stream_Count-1 is described in Table 56.

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

FIG. 15 is a block diagram illustrating a data transmission system 1000-3 according to another exemplary embodiment.

Referring to FIG. 15, a data transmission system 1000-3 according to an exemplary embodiment includes a data transmission device 100-3 and a data reception device 200-3.

The data transmitting device 100-3 generates display identification information including information about the nature of the audio data supported by the collecting tank device, and transmits the generated information to the data receiving device 200-3.

The data receiving device 200-3 receives display identification information from the data transmitting device 100-3 and analyzes the information. The display identification information includes a main / supplementary audio property field indicating information about the nature of the main audio and supplementary audio supported by the collection tank device.

The data transmitting device 100-3 and the data receiving device 200-3 will now be described in more detail.

FIG. 16 is a block diagram illustrating a data transfer device 100-3 according to another exemplary embodiment.

Referring to FIG. 16, the data transmission device 100-3 according to an exemplary embodiment includes a generator 130 and a transmitter 120.

The generator 130 generates display identification information including information about the nature of the audio data supported by the collection tank device.

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

The display identification information includes a main / supplementary audio property field indicating information about the nature of the main audio and supplementary audio supported by the collection tank device.

The main / audio nature field includes at least one of the following: an audio mixing field indicating whether the collection tank device supports a combination of main audio and supplemental audio; an indication of whether the collection tank device supports supplemental audio Supplementary audio support field; language support field indicating whether the collection tank device supports audio data in multiple languages; multi-view audio support field indicating whether the collection tank device supports multi-stream audio data of multi-view content A maximum stream count field indicating the maximum number of audio streams handled by the collection tank device; and an audio descriptor number field indicating the number of 3D audio descriptors.

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

FIG. 17 is a block diagram illustrating a data receiving device 200-3 according to another exemplary embodiment.

Referring to FIG. 17, the data transfer device 100-3 according to an exemplary embodiment includes a receiver 210 and an analyzer 230.

The receiver 210 receives display identification information including information about the nature of the audio data supported by the collection tank device from the data transmission device 100-3.

The analyzer 230 analyzes the received display identification information.

The display identification information includes a primary / supplementary audio property field that provides information on the nature of the primary audio and supplementary audio supported by the collection tank device.

The main / audio nature field includes at least one of the following: an audio mixing field indicating whether the collection tank device supports a combination of main audio and supplemental audio; an indication of whether the collection tank device supports supplemental audio Supplementary audio support field; language support field indicating whether the collection tank device supports audio data in multiple languages; multi-view audio support field indicating whether the collection tank device supports multi-stream audio data of multi-view content A maximum stream count field indicating the maximum number of audio streams handled by the collection tank device; and an audio descriptor number field indicating the number of 3D audio descriptors.

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

The wired interface according to various exemplary embodiments may support transmission of four-view content. The 3D video format standard of the HDMI cable interface standard can be used for four-view transmission.

18A, 18B, and 18C illustrate various data transmission formats for transmitting four-view video content in a 3D interleaved format.

Vendor-specific information frames and vendor-specific data blocks can be modified by extending the conventional fields used to define 3D multi-views to the reserved area.

Table 59-VSDB

A data transmission method according to various exemplary embodiments will now be described.

FIG. 19 is a flowchart of a data transmission method according to an exemplary embodiment.

Referring to FIG. 19, a data transmission method according to an exemplary embodiment 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 (S1720). The first sub-packet and the second sub-packet include different audio data related to the first content.

The first sub-packet may include audio data for non-disabled persons, and the second sub-packet may include audio data for visually impaired persons.

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

The first sub-packet may include audio data corresponding to an audio description about the second sub-packet.

The packet may further include a third sub-packet, and the third sub-packet includes a gateway. Audio data of a second content different from the first content.

The audio data included in the first sub-packet may be audio data provided for the first content, and the audio data included in the third sub-packet may be audio provided for the second content. Data, and the audio data included in the second sub-packet may be common audio data about the first content and the second content.

In addition, the packet may further include a fourth sub-packet, the fourth sub-packet includes audio data about the second content, and the third sub-packet and the fourth sub-packet may include different audio data.

FIG. 20 is a flowchart of a data receiving method according to an exemplary embodiment.

20, a data receiving method according to an exemplary embodiment includes: receiving a packet including a first sub-packet and a second sub-packet from a data transmission device (S1810); and analyzing the received first sub-packet and the The received second sub-packet is described (S1820). The first sub-packet and the second sub-packet include different audio data related to the first content.

The first sub-packet may include audio data for non-disabled persons, and the second sub-packet may include audio data for visually impaired persons.

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

The first sub-packet may include audio data corresponding to an audio description about the second sub-packet.

The packet may further include a third sub-packet, and the third sub-packet includes audio data about a second content different from the first content.

The audio data included in the first sub-packet may be audio data provided for the first content, and the audio data included in the third sub-packet may be audio provided for the second content. Data, and the audio data included in the second sub-packet may be common audio data about the first content and the second content.

In addition, the packet may further include a fourth sub-packet, the fourth sub-packet includes audio data about the second content, and the third sub-packet and the fourth sub-packet may include different audio data.

FIG. 21 is a flowchart of a data transfer method according to another exemplary embodiment.

21, a data transmission method according to an exemplary embodiment includes: generating an audio metadata packet (S1910); and transmitting a header of the generated audio metadata packet to a data receiving device (S1920). The header of the generated audio metadata packet may include a 3D audio field indicating whether to transmit a 3D audio sample packet.

In addition, the header of the generated audio metadata packet may further include an audio stream number field (number of audio streams field) that provides information about the number of audio streams transmitted.

The header of the generated audio metadata packet may further include providing a relevant The number of views field (the number of views field) for information on the number of different transmitted contents.

The payload of the generated audio metadata packet may include an audio metadata descriptor field containing metadata about a sub-packet of a multi-stream audio sample packet or a multi-stream one-voice sample packet.

The audio metadata descriptor field includes at least one of the following: indicating whether there is an emergency channel field for emergency broadcasting; indicating whether the audio data corresponding to the left-eye image or the right-eye image is included in the multi-view Multi-view field of; a language code valid field indicating whether the language of the audio data is identified; a supplementary audio valid field indicating whether there is a supplementary audio data; a premixed supplement indicating whether the main audio data and the supplemental audio data are premixed An audio field; a supplementary audio type field indicating a type of the supplemental audio data; and a language code field indicating a language code of the audio data.

FIG. 22 is a flowchart of a data receiving method according to another exemplary embodiment.

Referring to FIG. 22, a data receiving method according to an exemplary embodiment includes: receiving an audio relay data packet from a data transmission device (S2010); and analyzing the received audio relay data packet (S2020). The header of the generated audio metadata packet includes a 3D audio field indicating whether to transmit a 3D audio sample packet.

The header of the generated audio metadata packet may further include an audio stream number field (audio stream) that provides information about the number of audio streams transmitted. Number of streams field).

The header of the generated audio metadata packet may further include a view number field (number of views field) that provides information about the number of different transmitted content.

The payload of the generated audio metadata packet may include an audio metadata descriptor field containing metadata about a sub-packet of a multi-stream audio sample packet or a multi-stream one-voice sample packet.

The audio metadata descriptor field includes at least one of the following: indicating whether there is an emergency channel field for emergency broadcasting; indicating whether the audio data corresponding to the left-eye image or the right-eye image is included in the multi-view Multi-view field of; a language code valid field indicating whether the language of the audio data is identified; a supplementary audio valid field indicating whether there is a supplementary audio data; a pre-mixed supplement indicating whether the main audio data and the supplemental audio data are pre-mixed An audio field; a supplementary audio type field indicating a type of the supplemental audio data; and a language code field indicating a language code of the audio data.

FIG. 23 is a flowchart of a data transfer method according to another exemplary embodiment.

Referring to FIG. 23, a data transmission method according to an exemplary embodiment includes: generating display identification information including information on the nature of audio data supported by a collecting tank device (S2110); and transmitting the display identification information to data reception Device (S2120). The display identification information includes providing information about Set the primary / supplementary audio fields for information about the nature of the supported primary audio and supplementary audio.

The main / audio nature field includes at least one of the following: an audio mixing field indicating whether the collection tank device supports a combination of main audio and supplemental audio; an indication of whether the collection tank device supports supplemental audio Supplementary audio support field; language support field indicating whether the collection tank device supports audio data in multiple languages; multi-view audio support field indicating whether the collection tank device supports multi-stream audio data of multi-view content A maximum stream count field indicating the maximum number of audio streams handled by the collection tank device; and an audio descriptor number field indicating the number of 3D audio descriptors.

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

FIG. 24 is a flowchart of a data receiving method according to another exemplary embodiment.

Referring to FIG. 24, a data receiving method according to an exemplary embodiment includes: receiving display identification information including information on the nature of audio data supported by a collecting tank device (S2210); and analyzing the received display identification information ( S2220). The display identification information includes a main / supplementary audio property field indicating information about the nature of the main audio and supplementary audio supported by the collection tank device.

The main / audio nature field includes at least one of: An audio mixing field indicating whether the collecting tank device supports a combination of main audio and supplementary audio; a supplementary audio support field indicating whether the collecting tank device supports supplementary audio; indicating whether the collecting tank device supports multiple languages Language support field for audio data; multi-view audio support field indicating whether the collection slot device supports multi-stream audio data with multi-view content; maximum number of maximum audio streams handled by the collection slot device A stream count field; and an audio descriptor number field indicating the number of 3D audio descriptors.

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

Although some exemplary embodiments have been shown and described, the exemplary embodiments are not limited thereto. Those skilled in the art should understand that changes can be made to these exemplary embodiments without departing from the principles and scope of this disclosure, and the scope of this disclosure is defined in the scope of patent applications and their equivalents.

Claims (8)

A data transmission device includes a packet generator for generating a packet including a plurality of sub-packets, wherein the sub-packet includes a first sub-packet and a second sub-packet; and a transmitter for converting the generated packet Sending to a data receiving device, wherein the first sub-packet and the second sub-packet include different audio data related to the first content, and wherein the generated packet includes an audio type information field in a packet payload The audio type information field includes a supplementary audio type existence field and a supplemental audio type field, and the supplemental audio type existence field indicates whether there is supplementary audio of the audio data, and when the supplemental audio type exists field The bit is set to a first predetermined value, the audio type information field includes the supplementary audio type field, and the supplementary audio type field indicates a supplementary audio type of the audio data included in each of the sub-packets, wherein When the supplemental audio type presence field is set to a second predetermined value, the supplemental audio type field is ignored, where all The audio type information field further includes a one-bit mixed audio field and a one-bit valid language code field. The one-bit mixed audio field indicates whether the main audio data and the supplemental audio data are pre-mixed. The one-bit valid language code field indicates whether a valid language of the audio data exists, and when the one-bit mixed audio field is set to a first preset value, the audio data includes the main audio and the The pre-mixed stream of supplementary audio, and when the effective language code field of the bit is set to a second preset value, the audio data includes a language code field. The device according to item 1 of the patent application scope, wherein the first sub-packet includes audio data for non-disabled persons, and the second sub-packet includes audio data for visually impaired persons. The device according to item 1 of the scope of patent application, wherein the first sub-packet and the second sub-packet include audio data in different languages. The device of claim 1, wherein the first sub-packet includes audio data corresponding to an audio description related to the second sub-packet. The device of claim 1, wherein the packet further includes a third sub-packet, and the third sub-packet includes audio data related to a second content different from the first content. The device according to item 5 of the scope of patent application, wherein the audio data included in the first sub-packet includes audio data provided specifically for the first content, including all the data included in the third sub-packet. The audio data includes audio data provided specifically for the second content, and the audio data included in the second sub-packet includes audio data commonly used for the first content and the second content . The device according to item 5 of the scope of patent application, wherein the packet further includes a fourth sub-packet, the fourth sub-packet includes audio data related to the second content, and the third sub-packet and all The fourth sub-packet includes different audio data. A data receiving device includes a receiver for receiving a packet including a plurality of sub-packets from the data transmitting device, the sub-packet including a first sub-packet and a second sub-packet; and a parser for parsing the received packet. The first sub-packet and the received second sub-packet, wherein the first sub-packet and the second sub-packet include different audio data related to the first content, wherein the generated packet is in a packet The payload includes an audio type information field, the audio type information field includes a supplemental audio type presence field and a supplemental audio type field, and the supplemental audio type presence field indicates whether there is a supplementary audio of the audio data Wherein when the supplementary audio type presence field is set to a first predetermined value, the audio type information field includes the supplemental audio type field, and the supplementary audio type field indication is included in each of the sub-packets The supplementary audio type of the audio data, wherein when the supplemental audio type presence field is set to a second predetermined value, the supplemental audio type Type fields are ignored, where the audio type information field further includes a one-bit mixed audio field and a one-bit valid language code field, the one-bit mixed audio field indicates the main audio data and Whether the supplementary audio data is pre-mixed, and the one-bit effective language code field indicates whether a valid language of the audio data exists, and when the one-bit mixed audio field is set to a first preset value, all The audio data includes a pre-mixed stream of the main audio and the supplementary audio, and when the effective language code field of the bit is set to a second default value, the audio data includes a language code field.