Patent Description:
In the past, a technique of inserting metadata into an audio stream and transmitting the resulting audio stream was proposed (for example, see Patent Document <NUM>). Non-Patent Document <NUM> discloses an Adaptive HTTP Streaming full solution proposal as a pseudo CR. Patent Document <NUM> discloses a video framing unit manipulating left eye image data and right eye image data into a state according to the transmission mode, thereby obtaining stereoscopic image data for transmission. On the basis of the left eye image data and the right eye image data, at a predetermined position within an image, a view vector detecting unit detects a view vector that is disparity information of one of a left eye image and a right eye image with respect to the other. A view vector encoder generates an elementary stream of view vector. By a multiplexer, bit stream data into which the view vector stream is multiplexed in addition to a video stream, an audio stream, a graphics stream, and the like, is generated and transmitted. At the receiving side, as the same overlay information to be overlaid on the left eye image and the right eye image, overlay information to which disparity adjustment has been applied in accordance with the perspective of each object within the image can be used. Patent Document <NUM> discloses a process of a 3D compatible terminal to which content is distributed is made convenient. Meta information and a control signal are transmitted together with content transmitted from a content server in a predetermined transmission mode. The meta information includes information indicating whether the entirety of the content is 3D or a part thereof is 3D, information indicating whether this starts with 2D or 3D when a part thereof is 3D, and identification information of a 3D transmission method when the content is 3D.

Metadata is defined in a user data region of an audio stream, for example. However, metadata is not necessarily inserted into all audio streams.

It is an object of the present technology to enable a reception side to easily recognize that metadata is inserted into an audio stream and thus improve convenience of a process.

According to aspects of the present invention, there are provided a transmission device and a transmission method as defined in claim <NUM> and claim <NUM>, respectively.

In the present technology, a transmitting unit transmits a metafile including meta information for acquiring an audio stream into which metadata is inserted through a reception device. For example, the metadata may be access information for a connection to a predetermined network service. In this case, for example, the metadata may be a character code indicating URI information.

For example, the transmitting unit may transmit the metafile via an RF transmission path or a communication network transmission path. Further, for example, the transmitting unit may further transmit a container of a predetermined format including the audio stream into which the metadata is inserted. In this case, for example, the container may be an MP4 (ISO/IEC <NUM>-<NUM>:<NUM>).

An information inserting unit inserts identification information indicating that the metadata is inserted into the audio stream into the metafile. For example, the metafile may be a media presentation description (MPD) file. In this case, for example, the information inserting unit may insert the identification information into the metafile using a "Supplementary Descriptor.

As described above, in the present technology, the identification information indicating that the metadata is inserted into the audio stream is inserted into the metafile including the meta information for acquiring the audio stream into which the metadata is inserted in the reception device. Thus, at the reception side, it is possible to easily recognize that the metadata is inserted into the audio stream. Further, for example, it is also possible to perform the process of extracting the metadata inserted into the audio stream based on the recognition and acquire the metadata reliably without waste.

According to further aspects of the present invention, there are provided a reception device and a reception method as defined in claim <NUM> and claim <NUM>, respectively.

In the present technology, a receiving unit receives a metafile including meta information for acquiring an audio stream into which metadata is inserted. For example, the metadata may be the access information for a connection to a predetermined network service. The identification information indicating that the metadata is inserted into the audio stream is inserted into the metafile.

For example, the metadata may be access information for a connection to a predetermined network service. For example, the metafile may be an MPD file, and the identification information may be inserted into the metafile using the "Supplementary Descriptor.

A transmitting unit transmits the audio stream to an external device via a predetermined transmission path together with the identification information indicating that the metadata is inserted into the audio stream. For example, the transmitting unit may transmit the audio stream and the identification information to the external device by inserting the audio stream and the identification information into a blanking period of time of image data and transmitting the image data to the external device. For example, the predetermined transmission path may be a high definition multimedia interface (HDMI) cable.

As described above, in the present technology, the audio stream into which the metadata is inserted is transmitted to the external device together with the identification information indicating that the metadata is inserted into the audio stream. Thus, at the external device side, it is possible to easily recognize that the metadata is inserted into the audio stream. Further, for example, it is also possible to perform the process of extracting the metadata inserted into the audio stream based on the recognition and acquire the metadata reliably without waste.

According to yet further aspects of the present invention, there are provided a reception device and a reception method as defined in claim <NUM> and claim <NUM>, respectively.

In the present technology, a receiving unit receives a metafile including meta information for acquiring an audio stream into which metadata is inserted. Identification information indicating that the metadata is inserted into the audio stream is inserted into the metafile. For example, the metafile may be an MPD file, and the identification information may be inserted into the metafile using a "Supplementary Descriptor.

A metadata extracting unit decodes the audio stream based on the identification information, and extracts the metadata. A processing unit performs a process using the metadata. For example, the metadata may be access information for a connection to a predetermined network service, and the processing unit may access the predetermined server on a network based on the network access information.

As described above, in the present technology, the metadata is extracted from the audio stream based on the identification information that is inserted into the metafile and indicates that the metadata is inserted into the audio stream and used for a process. Thus, it is possible to acquire the metadata inserted into the audio stream reliably without waste and execute the process using the metadata appropriately.

In the present technology, a stream generating unit generates an audio stream into which metadata including network access information is inserted. For example, the audio stream is generated by performing encoding such as AAC, AC3, AC4, or MPEGH (3D audio) on audio data, and the metadata is embedded in a user data region of the audio stream.

A transmitting unit transmits a container of a predetermined format including the audio stream. Here, a container of a predetermined format is, for example, an MP4, an MPEG2-TS, or the like. For example, the metadata may be a character code indicating URI information.

As described above, in the present technology, the metadata including the network access information is embedded in the audio stream and transmitted. Thus, for example, it is possible to simply transmit the network access information from a broadcasting station, a delivery server, or the like using the audio stream as a container so that the network access information is used at the reception side.

Further preferred embodiments are set out in the dependent claims.

According to the present technology, a reception side can easily recognize that metadata is inserted into an audio stream. The effect described herein is merely an example and not necessarily limited and may include any effect described in the present disclosure.

Hereinafter, modes (hereinafter, referred to as "embodiments") for carrying out the invention will be described. A description will proceed in the following order.

First, an overview of an MPEG-DASH-based stream delivery system to which the present technology can be applied will be described.

<FIG> illustrates an exemplary configuration of an MPEG-DASH-based stream delivery system 30A. In this exemplary configuration, a media stream and a media presentation description (MPD) file are transmitted via a communication network transmissionpath. The stream delivery system 30A is configured such that N reception systems <NUM>-<NUM>, <NUM>-<NUM>,. , and <NUM>-N are connected to a DASH stream file server <NUM> and a DASH MPD server <NUM> via a content delivery network (CDN) <NUM>.

The DASH stream file server <NUM> generates a stream segment (hereinafter, referred to appropriately as a "DASH segment") of a DASH specification based on media data (video data, audio data, subtitle data, or the like) of predetermined content, and transmits the segment according to a HTTP request made from the reception system. The DASH stream file server <NUM> may be a server dedicated for streaming and function as a web server as well.

The DASH stream file server <NUM> transmits a segment of a predetermined stream to a receiver of a request source via the CDN <NUM> according to a request of a segment of the stream transmitted from the reception system <NUM> (<NUM>-<NUM>, <NUM>-<NUM>,. , and <NUM>-N) via the CDN <NUM>. In this case, the reception system <NUM> selects a stream of an optimal rate according to a state of a network environment in which a client is located with reference to a value of a rate described in the MPD file, and makes a request.

The DASH MPD server <NUM> is a server that generates the MPD file for acquiring the DASH segment generated in the DASH stream file server <NUM>. The MPD file is generated based on content metadata received from a content management server (not illustrated) and an address (url) of the segment generated in the DASH stream file server <NUM>. The DASH stream file server <NUM> and the DASH MPD server <NUM> may physically be the same.

In an MPD format, each attribute is described using an element such as a representation for each stream such as a video or an audio. For example, representations are divided for every a plurality of video data streams having different rates, and each rate thereof is described in the MPD file. The reception system <NUM> can select an optimal stream according to the state of the network environment in which the reception system <NUM> is located in view of the value of the rate as described above.

<FIG> illustrates an exemplary configuration of an MPEG-DASH-based stream delivery system 30B. In this exemplary configuration, the media stream and the MPD file are transmitted via an RF transmission path. The stream delivery system 30B is configured with a broadcast transmission system <NUM> connected with the DASH stream file server <NUM> and the DASH MPD server <NUM> and M reception systems <NUM>-<NUM>, <NUM>-<NUM>,. , and <NUM>-M.

In the case of the stream delivery system 30B, the broadcast transmission system <NUM> transmits a stream segment (a DASH segment) of a DASH specification generated by the DASH stream file server <NUM> and an MPD file generated by the DASH MPD server <NUM> through a broadcast wave.

<FIG> illustrate an example of a relation of structures hierarchically arranged in the MPD file. As illustrated in <FIG>, a media presentation of the entire MPD file includes a plurality of periods delimited at time intervals. For example, a first period starts from a <NUM>-th second, and a next period starts from a <NUM>-th second.

As illustrated in <FIG>, a period includes a plurality of representations. Among the plurality of representations, there is a group of representations related to media streams of the same substance having different stream attributes, for example, different rates which are grouped according to an adaptation set (AdaptationSet).

As illustrated in <FIG>, the representation includes a segment info (SegmentInfo). The segment info includes an initialization segment and a plurality of media segments in which information of segments obtained by delimiting the period finer is described as illustrated in <FIG>. The media segment includes, for example, information of an address (url) for actually acquiring segment data such as a video or an audio.

Further, stream switching can freely be performed among a plurality of representations grouped according to the adaptation set. Thus, it is possible to select a stream of an optimal rate according to a state of a network environment in which a reception system is located and perform seamless delivery.

<FIG> illustrate an exemplary configuration of a transceiving system according to an embodiment. A transceiving system <NUM> of <FIG> includes a service transmission system <NUM>, a set top box (STB) <NUM>, and a television receiver (TV) <NUM>. The set top box <NUM> is connected with the television receiver <NUM> via a high definition multimedia interface (HDMI) cable <NUM>. "HDMI" is a registered trademark.

In the transceiving system <NUM>, the service transmission system <NUM> corresponds to the DASH stream file server <NUM> and the DASH MPD server <NUM> of the stream delivery system 30A illustrated in <FIG>. In the transceiving system <NUM>, the service transmission system <NUM> corresponds to the DASH stream file server <NUM>, the DASH MPD server <NUM>, and the broadcast transmission system <NUM> of the stream delivery system 30B illustrated in <FIG>.

In the transceiving system <NUM>, the set top box (STB) <NUM> and the television receiver (TV) <NUM> correspond to the reception system <NUM> (<NUM>-<NUM>, <NUM>-<NUM>,. , and <NUM>-N) of the stream delivery system 30A illustrated in <FIG>. In the transceiving system <NUM>, the set top box (STB) <NUM> and the television receiver (TV) <NUM> correspond to the reception system <NUM> (<NUM>-<NUM>, <NUM>-<NUM>,. , and <NUM>-M) of the stream delivery system 30B illustrated in <FIG>.

A transceiving system <NUM>' of <FIG> includes a service transmission system <NUM> and a television receiver (TV) <NUM>. In the transceiving system <NUM>', the service transmission system <NUM> corresponds to the DASH stream file server <NUM> and the DASH MPD server <NUM> of the stream delivery system 30A illustrated in <FIG>. In the transceiving system <NUM>', the service transmission system <NUM> corresponds to the DASH stream file server <NUM>, the DASH MPD server <NUM>, and the broadcast transmission system <NUM> of the stream delivery system 30B illustrated in <FIG>.

In the transceiving system <NUM>', the television receiver (TV) <NUM> corresponds to the reception system <NUM> (<NUM>-<NUM>, <NUM>-<NUM>,. , and <NUM>-N) of the stream delivery system 30A illustrated in <FIG>. In the transceiving system <NUM>', the television receiver (TV) <NUM> corresponds to the reception system <NUM> (<NUM>-<NUM>, <NUM>-<NUM>,. , and <NUM>-M) of the stream delivery system 30B illustrated in <FIG>.

The service transmission system <NUM> transmits a DASH/MP4, that is, an MPD file serving as a metafile and an MP4 including a media stream (a media segment) such as a video or an audio via the RF transmission path or the communication network transmission path. The service transmission system <NUM> inserts metadata into an audio stream. For example, access information for a connection to a predetermined network service, predetermined content information, or the like is considered as the metadata. In this embodiment, the access information for a connection to a predetermined network service is inserted.

The service transmission system <NUM> inserts identification information indicating that the metadata is inserted into the audio stream into the MPD file. The service transmission system <NUM> inserts the identification information indicating that the metadata is inserted into the audio stream, for example, using a "Supplementary Descriptor.

<FIG> illustrates a description example of the MPD file. A description of "<AdaptationSet mimeType="audio/mp4" group="<NUM>">" indicates that there is an adaptation set (AdaptationSet) for an audio stream, the audio stream is supplied with an MP4 file structure, and a group <NUM> is allocated.

A description of "<SupplementaryDescriptor schemeIdUri="urn:brdcst:AudioMetaContained" value="true"/>" indicates that the metadata is inserted into the audio stream. Based on "SupplementaryDescriptor," "schemeIdUri" can be newly defined as a broadcast or any other application, separately from an existing definition in an existing standard. As illustrated in <FIG>, "schemeIdUri="urn:brdcst:AudiometaContained"" indicates that audio meta information is included, that is, that the metadata is inserted into the audio stream. For example, when a "value" is "true," it indicates that the audio meta information is included. When a "value" is "false," it indicates that the audio meta information is not included.

A description of "<SupplementaryDescriptor schemeIdUri="urn:brdcst:codecType" value= "mpegh"/>" indicates that a codec of the audio stream is MPEGH (3D audio). As illustrated in <FIG>, "schemeIdUri="urn:brdcst:codecType"" indicates a type of a codec. Examples of a "value" include "mpegh," "AAC," "AC3," and "AC4.

A description of "<SupplementaryDescriptor schemeIdUri="urn:brdcst:coordinatedControl" value="true"/>" indicates that information necessary for a network connection is emphasized among a plurality of media streams and supplied. As illustrated in <FIG>, "schemeIdUri="urn:brdcst:coordinatedControl"" indicates that the information necessary for the network connection is supplied through a coordination of a plurality of media streams. For example, when a "value" is "true," it indicates that the network connection information is supplied in coordination with a stream of another adaptation set. When a "value" is "false, " it indicates that the network connection information is supplied only through the stream of the present adaptation set.

A description of "<SupplementaryDescriptor schemeIdUri="urn:brdcst:type" value="netlink"/>" indicates that a type of a service by meta is a network connection. As illustrated in <FIG>, "schemeIdUri="urn:brdcst:type"" indicates a type of a service by meta. For example, when a "value" is "netlink," it indicates that a type of a service by meta is a network connection.

A description of "<SupplementaryDescriptor schemeIdUri="urn:brdcst:metaInsertionFrequency" value="<NUM>"/>" indicates that meta information is supplied in units of access units. As illustrated in <FIG>, "schemeIdUri="urn:brdcst:metaInsertionFrequency"" indicates a frequency in which the meta information is supplied in units of access units. For example, when a "value" is "<NUM>," it indicates that one user data entry is generated in one access unit. When a "value" is "<NUM>, " it indicates that a plurality of user data entries are generated in one access unit. When a "value" is "<NUM>, " it indicates that one or more user data entries are generated during a period of time delimited by a random access point.

<FIG> illustrates an arrangement example of video and audio access units contained in an MP4. "VAU" indicates a video access unit. "AAU" indicates an audio access unit. <FIG> illustrates that one user data entry (metadata) is inserted in each audio access unit when "frequency_type = <NUM>" is set.

<FIG> illustrates that a plurality of pieces of user data (metadata) are inserted in one audio access unit when "frequency_type = <NUM>" is set. <FIG> illustrates that at least one user data (metadata) is inserted into a first audio access unit for each group including a random access point when "frequency_type = <NUM>" is set.

Referring back to <FIG>, a description of "<Representationid="<NUM>"bandwidth="<NUM>">"indicatesthat "Representation id="<NUM>"" is set, and there is an audio stream in which the bit rate is <NUM> kbps. A description of "<baseURL>audio/jp/<NUM>. mp4</BaseURL>" indicates that a location destination of the audio stream is "audio/jp/<NUM>.

A description of "<AdaptationSet mimeType="video/mp4" group="<NUM>">" indicates that there is an adaptation set (AdaptationSet) for a video stream, the video stream is supplied with an MP4 file structure, and a group <NUM> is allocated.

A description of "<SupplementaryDescriptor schemeIdUri="urn:brdcst:VideoMetaContained" value="true"/> indicates that the metadata is inserted into the video stream. As illustrated in <FIG>, "schemeIdUri="urn:brdcst:VideoMetaContained"" indicates that video meta information is included, that is, that the metadata is inserted into the video stream. For example, when a "value" is "true," it indicates that the video meta information is included. When a "value" is "false," it indicates that the video meta information is not included.

A description of "<SupplementaryDescriptor schemeIdUri="urn:brdcst:codecType" value= "hevc"/>" indicates that a codec of the video stream is a HEVC. A description of "<SupplementaryDescriptor schemeIdUri="urn:brdcst:coordinatedControl" value="true"/>" indicates that the information necessary for the network connection is emphasized among a plurality of media streams and supplied.

A description of "<SupplementaryDescriptor schemeIdUri="urn:brdcst:type" value="netlink"/>" indicates that a type of a service by meta is a network connection. A description of "<SupplementaryDescriptor schemeIdUri="urn:brdcst:metaInsertionFrequency" value="<NUM>"/>" indicates that the meta information is supplied in units of access units.

A description of "<Representation id="<NUM>" bandwidth="<NUM>">" indicates that "Representation id="<NUM>"" is set, and there is a video stream in which the bit rate is <NUM> Mbps. A description of "<baseURL>video/jp/<NUM>. mp4</BaseURL>" indicates that a location destination of the video stream is "video/jp/<NUM>.

Here, a media file substance of a location destination indicated by "<baseURL>" will be described. In the case of a non-fragmentedMP4, there are cases in which "url1" is defined as illustrated in <FIG>, for example. In this case, a "ftyp" box describing a file type is first arranged. The "ftyp" box indicates that a file is a non-fragmented MP4 file. Subsequently, a "moov" box and a "mdat" box are arranged. The "moov" box includes all metadata, for example, header information of each track, a meta description of a content substance, time information, and the like. The "mdat" box includes a media data body.

In the case of a fragmented MP4, there are cases in which "url <NUM>" is defined as illustrated in <FIG>, for example. In this case, a "styp" box describing a segment type is first arranged. Then, a "sidx" box describing a segment index is arranged. Subsequently, a predetermined number of movie fragments are arranged. Here, the movie fragment is configured with a "moof" box including control information and a "mdat" box including a media data body. Since a fragment obtained by fragmenting a transmission media is included in the "mdat" box of one movie fragment, the control information included in the "moof" box is control information related to the fragment.

Further, a combination of "url <NUM>" and "url <NUM>" is also considered. In this case, for example, "url <NUM>" may be set as an initialization segment, and "url <NUM>" and "url <NUM>" may be set as an MP4 of one service. Alternatively, "url <NUM>" and "url <NUM>" maybe combined into one and defined as "url <NUM>" as illustrated in <FIG>.

The set top box <NUM> receives the DASH/MP4, that is, the MPD file serving as the metafile and the MP4 including the media stream (the media segment) such as a video or an audio, which is transmitted from the service transmission system <NUM> via the RF transmission path or the communication network transmission path. The access information for a connection to a predetermined network service is inserted into the audio stream included in the MP4 as the metadata. The identification information indicating that the metadata is inserted into the audio stream is inserted into the MPD file using the "Supplementary Descriptor.

The set top box <NUM> transmits the audio stream to the television receiver <NUM> via the HDMI cable <NUM> together with the identification information indicating that the metadata is inserted into the audio stream.

Here, the set top box <NUM> inserts the audio stream and the identification information into a blanking period of time of the image data obtained by decoding the video stream, transmits the image data to the television receiver <NUM>, and transmits the audio stream and the identification information to the television receiver <NUM>. The set top box <NUM> inserts the identification information into, for example, an audio InfoFrame packet.

The television receiver <NUM> receives the audio stream from the set top box <NUM> in the transceiving system <NUM> illustrated in <FIG> via the HDMI cable <NUM> together with the identification information indicating that the metadata is inserted into the audio stream. In other words, the television receiver <NUM> receives the image data in which the audio stream and the identification information are inserted into the blanking period of time from the set top box <NUM>.

Then, the television receiver <NUM> decodes the audio stream based on the identification information, extracts the metadata, and performs a process using the metadata. In this case, the television receiver <NUM> accesses a predetermined server on the network based on predetermined network service information serving as the metadata.

The television receiver <NUM> receives the DASH/MP4, that is, the MPD file serving as the metafile and the MP4 including the media stream (the media segment) such as a video or an audio, which are transmitted from the service transmission system <NUM> in the transceiving system <NUM>' illustrated in <FIG> via the RF transmission path or the communication network transmission path. The access information for a connection to a predetermined network service is inserted into the audio stream included in the MP4 as the metadata. The identification information indicating that the metadata is inserted into the audio stream is inserted into the MPD file using the "Supplementary Descriptor.

<FIG> illustrates an exemplary configuration of a DASH/MP4 generating unit <NUM> with which the service transmission system <NUM> is equipped. The DASH/MP4 generating unit <NUM> includes a control unit <NUM>, a video encoder <NUM>, an audio encoder <NUM>, and a DASH/MP4 formatter <NUM>.

The control unit <NUM> includes a CPU 111a, and controls the respective units of the DASH/MP4 generating unit <NUM>. The video encoder <NUM> performs encoding such as MPEG2, H. <NUM>/AVC, or H. <NUM>/HEVC on image data SV, and generates a video stream (a video elementary stream). Examples of the image data SV include image data reproduced from a recording medium such as a HDD and live image data obtained by a video camera.

The audio encoder <NUM> performs encoding on the audio data SA according to a compression format such as AAC, AC3, AC4, MPEGH (3D audio), and generates an audio stream (an audio elementary stream). The audio data SA is audio data corresponding to the image data SV, and examples of the audio data SA include audio data reproduced from a recording medium such as a HDD or live audio data obtained by a microphone.

The audio encoder <NUM> includes an audio encoding block unit 113a and an audio framing unit 113b. An encoded block is generated through the audio encoding block unit 113a and framed through the audio framing unit 113b. In this case, an encoded block and framing differ according to a compression format.

The audio encoder <NUM> inserts metadata MD into the audio stream under control of the control unit <NUM>. In this embodiment, the metadata MD is the access information for a connection to a predetermined network service. Here, all services such as a music network service and an audio video network service can be a predetermined network service. Here, the metadata MD is embedded in a user data region of the audio stream.

The DASH/MP4 formatter <NUM> generates an MP4 including the media stream (the media segment) such as a video or an audio serving as content based on the video stream output from the video encoder <NUM> and the audio stream output from the audio encoder <NUM>. The DASH/MP4 formatter <NUM> generates the MPD file using content metadata, segment URL information, and the like. Here, for example, the identification information indicating that the metadata is inserted into the audio stream is inserted into the MPD file (see <FIG>).

An operation of the DASH/MP4 generating unit <NUM> illustrated in <FIG> will briefly be described. The image data SV is supplied to the video encoder <NUM>. The video encoder <NUM> performs encoding such as H. <NUM>/AVC or H. <NUM>/HEVC on the image data SV, and generates the video stream including encoded video data.

The audio data SA is supplied to the audio encoder <NUM>. The audio encoder <NUM> performs encoding such as AAC, AC3, AC4, MPEGH (3D audio) on the audio data SA, and generates the audio stream.

At this time, the metadata MD and the size information for embedding the metadata MD in the user data region are supplied from the control unit <NUM> to the audio encoder <NUM>. Then, the audio encoder <NUM> embeds the metadata MD in the user data region of the audio stream.

The video stream generated by the video encoder <NUM> is supplied to the DASH/MP4 formatter <NUM>. The audio stream including the metadata MD embedded in the user data region, which is generated by the audio encoder <NUM> is supplied to the DASH/MP4 formatter <NUM>. Then, the DASH/MP4 formatter <NUM> generates the MP4 including the media stream (the media segment) such as a video or an audio serving as content. The DASH/MP4 formatter <NUM> generates the MPD file using the content metadata, the segment URL information, and the like. At this time, for example, the identification information indicating that the metadata is inserted into the audio stream is inserted into the MPD file.

First, an example in which the compression format is advanced audio coding (AAC) will be described. <FIG> illustrates a structure of the audio frame of AAC. The audio frame includes a plurality of elements. A <NUM>-bit identifier (ID) of "id_syn_ele" identifying content of an element is arranged in the head of each element.

When "id_syn_ele" is "0x4, " it indicates that an element is a data stream element (DSE) serving as an element in which user data can be arranged. When the compression format is AAC, the metadata MD is inserted into the DSE. <FIG> illustrates a configuration (syntax) of the DSE (Data Stream Element()).

A <NUM>-bit field of "element_instance_tag" indicates a data type in the DSE, and when the DSE is used as a unified user data, a value thereof may be "<NUM>. " "Data_byte_align_flag" is set to "<NUM>," and the entire DSE is byte-aligned. A value of "count" or "esc_count" indicating the number of additional bytes is appropriately decided according to the size of the user data. "metadata()" is inserted into a field of "data_stream_byte.

<FIG> illustrates a configuration (syntax) of "metadata()," and <FIG> illustrates content of main information (semantics) in the configuration. A <NUM>-bit field of "userdata_identifier" indicates audio user data by a setting of a value of an arrangement that is defined in advance. When "userdata_identifier" indicates the user data by "AAAA," an <NUM>-bit field of "metadata_type" is included. This field indicates a type of metadata. For example, "0x08" indicates that the metadata is the access information for a connection to a predetermined network service, and the access information is included in "SDO_payload()" of ATSC. When it is "0x08, " "SDO_payload()" is included. Here, "ATSC" is used, but it may be used in any other standardization organization.

<FIG> illustrates a configuration (syntax) of "SDO_payload(). " When a command ID (cmdID) is smaller than "0x05," a field of "URI_character" is included. A character code indicating URI information for a connection to a predetermined network service is inserted into this field. <FIG> illustrates a meaning of a value of the command ID (cmdID). "SDO_payload()" was standardized by Advanced Television Systems Committee standards (ATSC).

Next, an example in which the compression format is AC3 will be described. <FIG> illustrates a structure of a frame (AC3 synchronization frame) of AC3. The audio data SA is encoded so that a total size of "mantissa data" of "Audblock <NUM>," "AUX," and "CRC" does not exceed <NUM>/<NUM> of the total size. When the compression format is AC3, the metadata MD is inserted into an area of "AUX. " <FIG> illustrates a configuration (syntax) of auxiliary data of AC3.

When "auxdatae" is "<NUM>," "aux data" is enabled, and data of a size indicated by <NUM> bits (bit units) of "auxdatal" is defined in "auxbits. " At this time, a size of "auxbits" is described in "nauxbits. " In the present technology, a field of "auxbits" is defined as "metadata (). " In other words, "metadata()" illustrated in <FIG> is inserted into the field of "auxbits," and "SDO_payload()" (see <FIG>) of ATSC including the access information for a connection to a predetermined network service is arranged in the field of "data_byte" according to the syntax structure illustrated in <FIG>.

Next, an example in which the compression format is AC4 will be described. AC4 is one of next generation audio coding formats of AC3. <FIG> illustrates a structure of a simple transport layer of AC4. There are a field of a sync word (syncWord), a field of a frame length (frame Length), a field of "RawAc4Frame" serving as a field of encoded data, and a CRC field. The field of "RawAc4Frame" includes a field of a table of content (TOC) arranged in the head and a field of a predetermined number of sub streams (Substream) subsequent thereto as illustrated in <FIG>.

As illustrated in <FIG>, the sub stream (ac4_substream_data()) includes a metadata region (metadata), and a field of "umd_payloads_substream()" is arranged therein. "SDO_payload()" (see <FIG>) of ATSC including the access information for a connection to a predetermined network service is arranged in the field of "umd_payloads_substream().

Further, as illustrated in <FIG>, the TOC (ac4_toc()) includes a field of "ac4_presentation_info() " and further includes a field of "umd_info() " which indicates that the metadata is inserted into the field of "umd_payloads_substream()).

<FIG> illustrates a configuration (syntax) "umd_info (). " A field of "umd_version" indicates a version number. A field of "substream_index" indicates an index value. A combination of the version number and the index value is defined to indicate that the metadata is inserted into the field of "umd_payloads_substream()).

<FIG> illustrates a configuration (syntax) "umd_payloads_substream(). " A <NUM>-bit field of "umd_payload_id" is set to a value other than "<NUM>. " A <NUM>-bit field of "umd_userdata_identifier" indicates the audio user data by a setting of a value of an arrangement that is defined in advance. A <NUM>-bit field of "umd_payload_size" indicates the number of subsequent bytes. When "umd_userdata_identifier" indicates the user data by "AAAA," an <NUM>-bit field of "umd_metadata_type" is included. This field indicates a type of metadata. For example, "0x08" indicates that the metadata is the access information for a connection to a predetermined network service, and the access information is included in "SDO_payload()" of ATSC. When it is "0x08, " "SDO_payload()" (see <FIG>) is included.

Next, an example in which the compression format is MPEGH (3D audio) will be described. <FIG> illustrates a structure of an audio frame (<NUM> samples) in transmission data of MPEGH (3D audio). The audio frame is configured with a plurality of MPEG audio streampackets (mpeg Audio Stream Packets). Each MPEG audio stream packet is configured with a header and a payload.

The header includes information such as a packet type, a packet label, and a packet length. Information defined by the packet type of the header is arranged in the payload. The payload information includes "SYNC" corresponding to a synchronization start code, "Frame" serving an actual data of transmission data of a 3D audio, and "Config" indicating a configuration of "Frame.

Channel encoded data and object encoded data configuring the transmission data of the 3D audio are included in "Frame. " Here, the channel encoded data is configured with encoded sample data such as a single channel element (SCE), a channel pair element (CPE), and a low frequency element (LFE). The object encoded data is configured with the encoded sample data of the SCE and the metadata for mapping the encoded sample data with a speaker located at an arbitrary position and rendering the encoded sample data. The metadata is included as an extension element (Ext_element).

Here, a correspondence of the configuration information (config) of each "Frame" included in "Config" and each "Frame" is held as follows. In other words, as illustrated in <FIG>, the configuration information (config) of each "Frame" is registered in "Config" using an ID (elemIdx), and each "Frame" is transmitted in the order of the registered IDs. The values of the packet labels (PLs) are the same in "Config" and "Frames" corresponding thereto.

Referring back to <FIG>, in this embodiment, an element (Ext_userdata) including user data (userdata) is newly defined as an extension element (Ext_element). Thus, configuration information (userdataConfig) of the element (Ext_userdata) is newly defined in "Config.

<FIG> illustrates a correspondence relation between a type (ExElementType) of the extension element (Ext_element) and a value thereof. In a current state, <NUM> to <NUM> are decided. Since <NUM> and higher are extendable for use outside MPEG, for example, <NUM> is defined as a value of a type of "ID_EXT_ELE_userdata.

<FIG> illustrate a configuration (syntax) of "userdataConfig(). " A <NUM>-bit field of "userdata_identifier" indicates audio user data by a setting of a value of an arrangement that is defined in advance. A <NUM>-bit field of "userdata_frameLength" indicates the number of bytes of "audio_userdata(). " <FIG> illustrates a configuration (syntax) of "audio_userdata(). " When "userdata_identifier" of "userdataConfig()" indicates the user data by "AAAA," an <NUM>-bit field of "metadataType" is included. This field indicates a type of metadata. For example, "0x08" indicates that the metadata is the access information for a connection to a predetermined network service, and the access information is included in "SDO_payload() " of ATSC. When it is "0x08," "SDO_payload()" (see <FIG>) is included.

<FIG> illustrates an exemplary configuration of the set top box <NUM>. The set top box <NUM> includes a receiving unit <NUM>, a DASH/MP4 analyzing unit <NUM>, a video decoder <NUM>, an audio framing unit <NUM>, a HDMI transmitting unit <NUM>, and a HDMI terminal <NUM>. The set top box <NUM> further includes a CPU <NUM>, a flash ROM <NUM>, a DRAM <NUM>, an internal bus <NUM>, a remote controller receiving unit <NUM>, and a remote controller transmitter <NUM>.

The CPU <NUM> controls operations of the respective units of the set top box <NUM>. The flash ROM <NUM> stores control software and holds data. The DRAM <NUM> configures a work area of the CPU <NUM>. The CPU <NUM> activates software read from the flash ROM <NUM> or develops data onto the DRAM <NUM> and activates software, and controls the respective units of the set top box <NUM>.

The remote controller receiving unit <NUM> receives a remote control signal (a remote controller code) transmitted from the remote controller transmitter <NUM>, and supplies the remote control signal (the remote controller code) to the CPU <NUM>. The CPU <NUM> controls the respective units of the set top box <NUM> based on the remote controller code. The CPU <NUM>, the flash ROM <NUM>, and the DRAM213 are connected to the internal bus <NUM>.

The receiving unit <NUM> receives the DASH/MP4, that is, the MPD file serving as the metafile and the MP4 including the media stream (the media segment) such as a video or an audio, which are transmitted from the service transmission system <NUM> via the RF transmission path or the communication network transmission path. The access information for a connection to a predetermined network service is inserted into the audio stream included in the MP4 as the metadata. The identification information indicating that the metadata is inserted into the audio stream is inserted into the MPD file using the "Supplementary Descriptor.

The DASH/MP4 analyzing unit <NUM> analyzes the MPD file and the MP4 received by the receiving unit <NUM>. The DASH/MP4 analyzing unit <NUM> extracts the MPD information included in the MPD file, and transfers the MPD information to the CPU <NUM>. Here, the MPD information also includes, for example, the identification information indicating that the metadata is inserted into the audio stream. The CPU <NUM> controls a process of acquiring the video and audio streams based on the MPD information. The DASH/MP4 analyzing unit <NUM> extracts the metadata such as the header information of each track, a meta description of a content substance, time information, and the like from the MP4, and transmits the extracted metadata to the CPU <NUM>.

The DASH/MP4 analyzing unit <NUM> extracts the video stream from the MP4, and transfers the extracted video stream to the video decoder <NUM>. The video decoder <NUM> performs the decoding process on the video stream, and obtains the uncompressed image data. The DASH/MP4 analyzing unit <NUM> extracts the audio stream from the MP4, and transfers the extracted audio stream to the audio framing unit <NUM>. The audio framing unit <NUM> performs framing on the audio stream.

The HDMI transmitting unit <NUM> transmits the uncompressed image data obtained through the video decoder <NUM> and the audio stream framed by the audio framing unit <NUM> through the HDMI terminal <NUM> according to communication complying with the HDMI. The HDMI transmitting unit <NUM> packs the image data and the audio stream for transmission through the TMDS channel of the HDMI, and transfers the resulting data to the HDMI terminal <NUM>.

The HDMI transmitting unit <NUM> inserts the identification information indicating that the metadata is inserted into the audio stream under control of the CPU <NUM>. The HDMI transmitting unit <NUM> inserts the audio stream and the identification information into the blanking period of time of the image data. The HDMI transmitting unit <NUM> will be described in detail.

In this embodiment, the HDMI transmitting unit <NUM> inserts the identification information into the audio InfoFrame packet arranged in the blanking period of time of the image data. The audio InfoFrame packet is arranged in a data island period.

<FIG> illustrates an exemplary structure of the audio InfoFrame packet. In the HDMI, supplementary information related to a sound can be transmitted from a source device to a sink device through the audio InfoFrame packet.

"Packet Type" indicating a kind of a data packet is defined in a <NUM>-th byte, and the audio InfoFrame packet is set to "0x84. " Version information of a packet data definition is described in a 1st byte. Information indicating a packet length is described in a 2nd byte. In this embodiment, <NUM>-bit flag information of "userdata_presence_flag" is defined in a 5th bit of a 5th byte. When the flag information is "<NUM>," it indicates that the metadata is inserted into the audio stream.

When the flag information is "<NUM>," various information is defined in a 9th byte. 7th to 5th bits are used as a field of "metadata_type," a 4th bit is used as a field of "coordinated_control_flag," and 2nd to <NUM>-th bits are used as a field of "frequency_type. " Although a detailed description is omitted, the respective fields indicate the same information as the respective information added to the MPD file illustrated in <FIG>.

An operation of the set top box <NUM> will briefly be described. The receiving unit <NUM> receives the DASH/MP4, that is, the MPD file serving as the metafile and the MP4 including the media stream (the media segment) such as a video or an audio, which are transmitted from the service transmission system <NUM> via the RF transmission path or the communication network transmission path. As described above, the received MPD file and the MP4 are supplied to the DASH/MP4 analyzing unit <NUM>.

The DASH/MP4 analyzing unit <NUM> analyzes the MPD file and the MP4. The DASH/MP4 analyzing unit <NUM> extracts the MPD information included in the MPD file, and transfers the MPD information to the CPU <NUM>. Here, the MPD information also includes, for example, the identification information indicating that the metadata is inserted into the audio stream. The DASH/MP4 analyzing unit <NUM> extracts the metadata such as the header information of each track, a meta description of a content substance, time information, and the like from the MP4, and transmits the extracted metadata to the CPU <NUM>.

The DASH/MP4 analyzing unit <NUM> extracts the video stream from the MP4, and transfers the video stream to the video decoder <NUM>. The video decoder <NUM> performs the decoding process on the video stream, and obtains uncompressed image data. The image data is supplied to the HDMI transmitting unit <NUM>. The DASH/MP4 analyzing unit <NUM> extracts the audio stream from the MP4. The audio stream is framed by the audio framing unit <NUM> and then supplied to the HDMI transmitting unit <NUM>. Then, the HDMI transmitting unit <NUM> packs the image data and the audio stream, and transmits the resulting data from the HDMI terminal <NUM> to the HDMI cable <NUM>.

The HDMI transmitting unit <NUM> inserts the identification information indicating that the metadata is inserted into the audio stream into the audio InfoFrame packet arranged in the blanking period of time of the image data under control of the CPU <NUM>. Thus, the identification information indicating that the metadata is inserted into the audio stream is transmitted from the set top box <NUM> to the HDMI television receiver <NUM>.

<FIG> illustrates an exemplary configuration of the television receiver <NUM>. The television receiver <NUM> includes a receiving unit <NUM>, a DASH/MP4 analyzing unit <NUM>, a video decoder <NUM>, a video processing circuit <NUM>, a panel driving circuit <NUM>, and a display panel <NUM>.

The television receiver <NUM> includes an audio decoder <NUM>, an audio processing circuit <NUM>, an audio amplifying circuit <NUM>, a speaker <NUM>, a HDMI terminal <NUM>, a HDMI receiving unit <NUM>, and a communication interface <NUM>. The television receiver <NUM> also includes a CPU <NUM>, a flash ROM <NUM>, a DRAM <NUM>, an internal bus <NUM>, a remote controller receiving unit <NUM>, and a remote controller transmitter <NUM>.

The CPU <NUM> controls operations of the respective units of the television receiver <NUM>. The flash ROM <NUM> stores control software and holds data. The DRAM <NUM> configures a work area of the CPU <NUM>. The CPU <NUM> activates software read from the flash ROM <NUM> or develops data onto the DRAM <NUM> and activates software, and controls the respective units of the television receiver <NUM>.

The remote controller receiving unit <NUM> receives a remote control signal (a remote controller code) transmitted from the remote controller transmitter <NUM>, and supplies the remote control signal (the remote controller code) to the CPU <NUM>. The CPU <NUM> controls the respective units of the television receiver <NUM> based on the remote controller code. The CPU <NUM>, the flash ROM <NUM>, and the DRAM <NUM> are connected to the internal bus <NUM>.

The communication interface <NUM> performs communication with a server located on a network such as the Internet under control of the CPU <NUM>. The communication interface <NUM> is connected to the internal bus <NUM>.

The receiving unit <NUM> receives the DASH/MP4, that is, the MPD file serving as the metafile and the MP4 including the media stream (the media segment) such as a video or an audio, which are transmitted from the service transmission system <NUM> via the RF transmission path or the communication network transmission path. The access information for a connection to a predetermined network service is inserted into the audio stream included in the MP4 as the metadata. For example, the identification information indicating that the metadata is inserted into the audio stream is inserted into the MPD file using the "Supplementary Descriptor.

The DASH/MP4 analyzing unit <NUM> analyzes the MPD file and the MP4 received by the receiving unit <NUM>. The DASH/MP4 analyzing unit <NUM> extracts the MPD information included in the MPD file, and transfers the extracted MPD information to the CPU <NUM>. The CPU <NUM> controls a process of acquiring the video and audio streams based on the MPD information. The DASH/MP4 analyzing unit <NUM> extracts the metadata such as the header information of each track, a meta description of a content substance, time information, and the like from the MP4, and transmits the extracted metadata to the CPU <NUM>.

The DASH/MP4 analyzing unit <NUM> extracts the video stream from the MP4, and transfers the extracted video stream to the video decoder <NUM>. The video decoder <NUM> performs the decoding process on the video stream, and obtains the uncompressed image data. The DASH/MP4 analyzing unit <NUM> extracts the audio stream from the MP4, and transfers the extracted audio stream to the audio decoder <NUM>.

The HDMI receiving unit <NUM> receives the image data and the audio stream supplied to the HDMI terminal <NUM> via the HDMI cable <NUM> according to communication complying with the HDMI. The HDMI receiving unit <NUM> extracts various control information inserted into the blanking period of time of the image data, and transmits the extracted control information to the CPU <NUM>. Here, the control information also includes, for example, the identification information that indicates that the metadata is inserted into the audio stream and is inserted into the audio InfoFrame packet (see <FIG>). The HDMI receiving unit <NUM> will be described in detail later.

The video processing circuit <NUM> obtains a display image data by performing a scaling process, a synthesis process, and the like on the image data that is obtained through the video decoder <NUM> or the HDMI receiving unit <NUM> and the image data received from the server on the network through the communication interface <NUM>.

The panel driving circuit <NUM> drives the display panel <NUM> based on the display image data obtained through the video processing circuit <NUM>. The display panel <NUM> is configured with, for example, a liquid crystal display (LCD), an organic electroluminescence display (organic EL display), or the like.

The audio decoder <NUM> obtains uncompressed audio data by performing the decoding process on the audio stream that is extracted by the DASH/MP4 analyzing unit <NUM> or obtained by the HDMI receiving unit <NUM>. The audio decoder <NUM> extracts the metadata inserted into the audio stream under control of the CPU <NUM>, and transmits the extracted metadata to the CPU <NUM>. In this embodiment, the metadata is the access information for a connection to a predetermined network service (see <FIG>). The CPU <NUM> appropriately causes the respective units of the television receiver <NUM> to perform a process using the metadata.

The MPD information is supplied from the DASH/MP4 analyzing unit <NUM> to the CPU <NUM>. The CPU <NUM> can recognize that the metadata is inserted into the audio stream in advance based on the identification information included in the MPD information, and can control the audio decoder <NUM> such that the metadata is extracted.

The audio processing circuit <NUM> performs a necessary process such as D/A conversion on the audio data obtained through the audio decoder <NUM>. The audio amplifying circuit <NUM> amplifies an audio signal output from the audio processing circuit <NUM>, and supplies the amplified audio signal to the speaker <NUM>.

An operation of the television receiver <NUM> illustrated in <FIG> will briefly be described. The receiving unit <NUM> receives the DASH/MP4, that is, the MPD file serving as the metafile and the MP4 including the media stream (the media segment) such as a video or an audio, which are transmitted from the service transmission system <NUM> via the RF transmission path or the communication network transmission path. As described above, the received MPD file and the MP4 are supplied to the DASH/MP4 analyzing unit <NUM>.

The DASH/MP4 analyzing unit <NUM> analyzes the MPD file and the MP4. Then, the DASH/MP4 analyzing unit <NUM> extracts the MPD information included in the MPD file, and transfers the extracted MPD information to the CPU <NUM>. Here, the MPD information also includes the identification information indicating that the metadata is inserted into the audio stream. The DASH/MP4 analyzing unit <NUM> extracts the metadata such as the header information of each track, a meta description of a content substance, time information, and the like from the MP4, and transmits the extracted metadata to the CPU <NUM>.

The DASH/MP4 analyzing unit <NUM> extracts the video stream from the MP4, and transfers the extracted video stream to the video decoder <NUM>. The video decoder <NUM> performs the decoding process on the video stream, and obtains the uncompressed image data. The image data is supplied to the video processing circuit <NUM>. The DASH/MP4 analyzing unit <NUM> extracts the audio stream from the MP4. The audio stream is supplied to the audio decoder <NUM>.

The HDMI receiving unit <NUM> receives the image data and the audio stream supplied to the HDMI terminal <NUM> via the HDMI cable <NUM> according to communication complying with the HDMI. The image data is supplied to the video processing circuit <NUM>. The audio stream is supplied to the audio decoder <NUM>.

The HDMI receiving unit <NUM> extracts various control information inserted into the blanking period of time of the image data, and transmits the extracted control information to the CPU <NUM>. Here, the control information also includes, for example, the identification information that indicates that the metadata is inserted into the audio stream and is inserted into the audio InfoFrame packet. Thus, the CPU <NUM> controls the operation of the audio decoder <NUM> based on the identification information such that the metadata is extracted from the audio stream.

The video processing circuit <NUM> obtains a display image data by performing a scaling process, a synthesis process, and the like on the image data that is obtained through the video decoder <NUM> or the HDMI receiving unit <NUM> and the image data received from the server on the network through the communication interface <NUM>. Here, when the television broadcast signal is received and processed, the video processing circuit <NUM> deals with the image data obtained through the video decoder <NUM>. On the other hand, when the set top box <NUM> is connected through a HDMI interface, the video processing circuit <NUM> deals with the image data obtained through the HDMI receiving unit <NUM>.

The display image data obtained through the video processing circuit <NUM> is supplied to the panel driving circuit <NUM>. The panel driving circuit <NUM> drives the display panel <NUM> based on the display image data. As a result, the image corresponding to the display image data is displayed on the display panel <NUM>.

The audio decoder <NUM> obtains the uncompressed audio data by performing the decoding process on the audio stream that is obtained through the DASH/MP4 analyzing unit <NUM> or the HDMI receiving unit <NUM>. Here, when the television broadcast signal is received and processed, the audio decoder <NUM> deals with the audio stream obtained through the DASH/MP4 analyzing unit <NUM>. On the other hand, when the set top box <NUM> is connected through the HDMI interface, the audio decoder <NUM> deals with the audio stream obtained through the HDMI receiving unit <NUM>.

The audio data obtained through the audio decoder <NUM> is supplied to the audio processing circuit <NUM>. The audio processing circuit <NUM> performs a necessary process such as D/A conversion on the audio data. The audio data is amplified by the audio amplifying circuit <NUM> and supplied to the speaker <NUM>. As a result, the sound corresponding to the display image of the display panel <NUM> is output from the speaker <NUM>.

The audio decoder <NUM> extracts the metadata inserted into the audio stream. For example, the metadata extraction process is reliably performed without waste by the CPU <NUM> detecting that the metadata is inserted into the audio stream based on the identification information and controlling the operation of the audio decoder <NUM> as described above.

The metadata extracted by the audio decoder <NUM> as described above is transferred to the CPU <NUM>. The CPU <NUM> appropriately controls the respective units of the television receiver <NUM> such that the process using the metadata is performed. For example, the image data is acquired from the server on the network, and a multi-screen display is performed.

<FIG> illustrates an exemplary configuration of the HDMI transmitting unit (HDMI source) <NUM> of the set top box <NUM> illustrated in <FIG> and the HDMI receiving unit (HDMI sink) <NUM> of the television receiver <NUM> illustrated in <FIG>.

The HDMI transmitting unit <NUM> transmits a differential signal corresponding to pixel data of an image of one uncompressed screen to the HDMI receiving unit <NUM> in one direction through a plurality of channels during an effective image period (hereinafter, also referred to appropriately as an "active video period"). Here, the effective image period is a period obtained by subtracting a horizontal blanking period of time and a vertical blanking period of time from a period ranging from a certain vertical synchronous signal to a next vertical synchronous signal. The HDMI transmitting unit <NUM> transmits a differential signal corresponding to at least audio data or control data attached to an image, other auxiliary data, and the like to the HDMI receiving unit <NUM> in one direction through a plurality of channels in the horizontal blanking period of time or the vertical blanking period of time.

Transmission channels of a HDMI system configured with the HDMI transmitting unit <NUM> and the HDMI receiving unit <NUM> include the following transmission channels. In other words, there are three TMDS channels #<NUM> to #<NUM> as a transmission channel used for serially transmitting pixel data and audio data from the HDMI transmitting unit <NUM> to the HDMI receiving unit <NUM> in one direction in synchronization with a pixel clock. Further, as a transmission channel used for transmitting the pixel clock, there is a TMDS clock channel.

The HDMI transmitting unit <NUM> includes a HDMI transmitter <NUM>. For example, the transmitter <NUM> converts pixel data of an uncompressed image into a corresponding differential signal, and serially transmits the differential signal to the HDMI receiving unit <NUM> connected through the HDMI cable <NUM> in one direction through a plurality of channels, that is, the three TMDS channels #<NUM>, #<NUM>, and #<NUM>.

The transmitter <NUM> converts the audio data attached to the uncompressed image, the necessary control data, other auxiliary data, and the like into the corresponding differential signal, and serially transmits the differential signal to the HDMI receiving unit <NUM> in one direction through the three TMDS channels #<NUM>, #<NUM>, and #<NUM>.

Further, the transmitter <NUM> transmits the pixel clock synchronized with the pixel data transmitted through the three TMDS channels #<NUM>, #<NUM>, and #<NUM> to the HDMI receiving unit <NUM> connected through the HDMI cable <NUM> through the TMDS clock channel. Here, the pixel data of <NUM> bits is transmitted through one TMDS channel #i (i = <NUM>, <NUM>, and <NUM>) during one clock of the pixel clock.

The HDMI receiving unit <NUM> receives the differential signal corresponding to the pixel data transmitted from the HDMI transmitting unit <NUM> in one direction through a plurality of channels in the active video period. The HDMI receiving unit <NUM> receives the differential signal corresponding to the audio data or the control data transmitted from the HDMI transmitting unit <NUM> in one direction through a plurality of channels in the horizontal blanking period of time or the vertical blanking period of time.

In other words, the HDMI receiving unit <NUM> includes a HDMI receiver <NUM>. The HDMI receiver <NUM> receives the differential signal corresponding to the pixel data and the differential signal corresponding to the audio data or the control data which are transmitted from the HDMI transmitting unit <NUM> in one direction through the TMDS channels #<NUM>, #<NUM>, and #<NUM>. In this case, the receiving is performed in synchronization with the pixel clock transmitted from the HDMI transmitting unit <NUM> through the TMDS clock channel.

The transmission channels of the HDMI system include a display data channel (DDC) <NUM> and a transmission channels called a CEC line <NUM> in addition to the TMDS channels #<NUM> to #<NUM> and the TMDS clock channel. The DDC <NUM> is configured with two signal lines (not illustrated) included in the HDMI cable <NUM>. The DDC <NUM> is used when the HDMI transmitting unit <NUM> reads enhanced extended display identification data (E-EDID) from the HDMI receiving unit <NUM>.

The HDMI receiving unit <NUM> includes an EDID read only memory (ROM) <NUM> that stores the E-EDID serving as performance information related to its performance (configuration/capability) in addition to the HDMI receiver <NUM>. The HDMI transmitting unit <NUM> reads the E-EDID from the HDMI receiving unit <NUM> connected through the HDMI cable <NUM> through the DDC <NUM>, for example, according to a request from the CPU <NUM> (see <FIG>).

The HDMI transmitting unit <NUM> transfers the readE-EDID to the CPU <NUM>. The CPU <NUM> stores the E-EDID in the flash ROM <NUM> or the DRAM <NUM>.

The CEC line <NUM> is configured with a single signal line (not illustrated) included in the HDMI cable <NUM> and used for performing two-way communication of control data between the HDMI transmitting unit <NUM> and the HDMI receiving unit <NUM>. The CEC line <NUM> configures a control data line.

The HDMI cable <NUM> includes a line (HPD line) <NUM> connected to a pin called a hot plug detect (HPD). A source device can detect a connection of a sink device using the line <NUM>. The HPD line <NUM> is used as a HEAC-line configuring a two-way communication path as well. The HDMI cable <NUM> includes a power line <NUM> used for supplying electric power from the source device to the sink device. The HDMI cable <NUM> further includes a utility line <NUM>. The utility line <NUM> is used as a HEAC+line configuring the two-way communication path as well.

<FIG> illustrates various kinds of transmission data periods when image data of <NUM> pixels × <NUM> lines are transmitted through the TMDS channels #<NUM>, #<NUM>, and #<NUM>. There are three kinds of periods, that is, a video data period <NUM>, a data island period <NUM>, and a control period <NUM> in a video field in which transmission data is transmitted through the three TMDS channels #<NUM>, #<NUM>, and #<NUM> of the HDMI according to the kind of transmission data.

Here, the video field period is a period ranging from a rising edge (Active Edge) of a certain vertical synchronous signal to a rising edge of a next vertical synchronous signal and divided into a horizontal blanking period of time <NUM> (Horizontal Blanking), a vertical blanking period of time <NUM> (Vertical Blanking), and an effective pixel period <NUM> (Active Video) serving as a period obtained by subtracting the horizontal blanking period of time and the vertical blanking period of time from the video field period.

The video data period <NUM> is allocated to the effective pixel period <NUM>. In the video data period <NUM>, data of effective pixels (Active Pixels) of <NUM> pixels × <NUM> lines configuring image data of one uncompressed screen is transmitted. The data island period <NUM> and the control period <NUM> are allocated to the horizontal blanking period of time <NUM> and the vertical blanking period of time <NUM>. In the data island period <NUM> and the control period <NUM>, the auxiliary data is transmitted.

In other words, the data island period <NUM> is allocated to a part of the horizontal blanking period of time <NUM> and a part of the vertical blanking period of time <NUM>. In the data island period <NUM>, among the auxiliary data, a packet of data irrelevant to control, for example, a packet of the audio data is transmitted. The control period <NUM> is allocated to another part of the horizontal blanking period of time <NUM> and another part of the vertical blanking period of time <NUM>. In the control period <NUM>, among the auxiliary data, a packet of data relevant to control, for example, the vertical synchronous signal, the horizontal synchronous signal, a control packet, and the like are transmitted.

Next, a specific example of the process using the metadata in the television receiver <NUM> will be described with reference to <FIG>. The television receiver <NUM> acquires, for example, an initial server URL, network service identification information, a target file name, a session start/end command, a media recording/reproducing command, and the like as the metadata. In the above description, the metadata has been described as being the access information for a connection to a predetermined network service, but other necessary information is assumed to be included in the metadata.

The television receiver <NUM> serving as a network client accesses a primary server using the initial server URL. Then, the television receiver <NUM> acquires information such as a streaming server URL, a target file name, a MIME type indicating a type of a file, and media reproduction time information from the primary server.

Then, the television receiver <NUM> accesses a streaming server using the streaming server URL. Then, the television receiver <NUM> designates the target file name. Here, when a service is received in a multicast manner, the television receiver <NUM> specifies a service of a program based on network identification information and service identification information.

Then, the television receiver <NUM> starts or ends a session with the streaming server according to the session start/end command. Further, the television receiver <NUM> acquires media data from the streaming server using the media recording/reproducing command during the session with the streaming server.

In the example of <FIG>, the primary server and the streaming server are separately arranged. However, the servers may integrally be configured.

<FIG> illustrate a transition example of a screen display when the television receiver <NUM> accesses the network service based on the metadata. <FIG> illustrates a state in which no image is displayed on the display panel <NUM>. <FIG> illustrates a state in which broadcast reception starts, and main content related to the broadcast reception is displayed on the display panel <NUM> in a full-screen display form.

<FIG> illustrates a state in which there is access to the service based on the metadata, and a session starts between the television receiver <NUM> and the server. In this case, the display of the main content related to the broadcast reception is changed from the full-screen display to the partial-screen display.

<FIG> illustrates a state in which media reproduction from the server is performed, and network service content <NUM> is displayed on the display panel <NUM> in parallel with the display of the main content. <FIG> illustrates a state in which media reproduction from the server is performed, and network service content <NUM> is displayed on the display panel <NUM> to be superimposed on the display of the main content together with the display of the network service content <NUM> in parallel with the display of the main content.

<FIG> illustrates a state in which the reproduction of the service content from the network ends, and the session between the television receiver <NUM> and the server ends. In this case, the display panel <NUM> returns to the state in which the main content related to the broadcast reception is displayed in the full-screen display form.

The television receiver <NUM> illustrated in <FIG> includes the speaker <NUM> and has a configuration in which the audio data obtained by the audio decoder <NUM> is supplied to the speaker <NUM> via the audio processing circuit <NUM> and the audio amplifying circuit <NUM>, and thus the sound is output from the speaker <NUM> as illustrated in <FIG>.

However, as illustrated in <FIG>, the television receiver <NUM> may have a configuration in which not speaker is arranged, and the audio stream obtained by the DASH/MP4 analyzing unit <NUM> or the HDMI receiving unit <NUM> is supplied from an interface unit <NUM> to an external speaker system <NUM>. The interface unit <NUM> is a digital interface such as a HDMI, a Sony Philips digital interface (SPDIF), or a mobile high-definition link (MHL).

In this case, an audio decoder 351a arranged in the external speaker system <NUM> performs the decoding process on the audio stream, and thus the sound is output from the external speaker system <NUM>. Further, even when the television receiver <NUM> is equipped with the speaker <NUM> (see <FIG>), the audio stream may be supplied from the interface unit <NUM> to the external speaker system <NUM> (see <FIG>).

As described above, in the transceiving systems <NUM> and <NUM>' illustrated in <FIG>, the service transmission system <NUM> inserts the identification information indicating that the metadata is inserted into the audio stream into the MPD file. Thus, the reception side (the set top box <NUM> and the television receiver <NUM>) can easily recognize that the metadata is inserted into the audio stream.

Further, in the transceiving system <NUM> illustrated in <FIG>, the set top box <NUM> transmits the audio stream into which the metadata is inserted to the television receiver <NUM> together with the identification information indicating that the metadata is inserted into the audio stream according to the HDMI. Thus, the television receiver <NUM> can easily recognize that the metadata is inserted into the audio stream and acquire and use the metadata reliably without waste by performing the process of extracting the metadata inserted into the audio stream based on the recognition.

In the transceiving system <NUM>' illustrated in <FIG>, the television receiver <NUM> extracts the metadata from the audio stream based on the identification information inserted into the MPD file, and uses the metadata for a process. Thus, it is possible to acquire the metadata inserted into the audio stream reliably without waste, and it is possible to perform a process using the metadata appropriately.

In the embodiment, the transceiving systems <NUM> and <NUM>' deal with the DASH/MP4, but an example in which an MPEG2-TS is dealt is similarly considered.

<FIG> illustrate an exemplary configuration of a transceiving system that deals with an MPEG2-TS. The transceiving system 10A of <FIG> includes a service transmission system 100A, a set top box (STB) 200A, and a television receiver (TV) 300A. The set top box 200A is connected with the television receiver 300A via a HDMI cable <NUM>. The transceiving system 10A' of <FIG> includes the service transmission system 100A and the television receiver (TV) 300A.

The service transmission system 100A transmits the transport stream TS of the MPEG2-TS via the RF transmission path or the communication network transmission path. The service transmission system 100A inserts the metadata into the audio stream. For example, access information for a connection to a predetermined network service, predetermined content information, or the like is considered as the metadata. Here, similarly to the above embodiment, the access information for a connection to a predetermined network service is assumed to be inserted.

The service transmission system 100A inserts the identification information indicating that the metadata is inserted into the audio stream into a layer of the container. The service transmission system 100A inserts the identification information into the audio elementary stream loop under control of a program map table (PMT) as a descriptor.

The set top box 200A receives the transport stream TS transmitted from the service transmission system 100A via the RF transmission path or the communication network transmission path. The video stream and the audio stream are included in the transport stream TS, and the metadata is inserted into the audio stream.

The set top box 200A transmits the audio stream to the television receiver 300A via the HDMI cable <NUM> together with the identification information indicating that the metadata is inserted into the audio stream.

Here, the set top box 200A transmits the audio stream and the identification information to the television receiver 300A by inserting the audio stream and the identification information into the blanking period of time of the image data obtained by decoding the video stream and transmitting the image data to the television receiver 300A. The set top box 200A inserts the identification information, for example, into the audio InfoFrame packet (see <FIG>).

The television receiver 300A receives the audio stream from the set top box 200A in the transceiving system 10A illustrated in <FIG> via the HDMI cable <NUM> together with the identification information indicating that the metadata is inserted into the audio stream. In other words, the television receiver 300A receives the image data in which the audio stream and the identification information are inserted into the blanking period of time from the set top box 200A.

Then, the television receiver 300A decodes the audio stream based on the identification information, extracts the metadata, and performs a process using the metadata. In this case, the television receiver 300A accesses a predetermined server on the network based on predetermined network service information serving as the metadata.

Further, the television receiver 300A receives the transport stream TS transmitted from the service transmission system 100A in the transceiving system 10A' illustrated in <FIG> via the RF transmission path or the communication network transmission path. The access information for a connection to a predetermined network service is inserted into the audio stream included in the transport stream TS as the metadata. The identification information indicating that the metadata is inserted into the audio stream is inserted into the layer of the container.

<FIG> illustrates an exemplary configuration of a TS generating unit 110A with which the service transmission system 100A is equipped. In <FIG>, portions corresponding to those in <FIG> are denoted by the same reference numerals. The TS generating unit 110A includes a control unit <NUM>, a video encoder <NUM>, an audio encoder <NUM>, and a TS formatter 114A.

The control unit <NUM> includes a CPU 111a, and controls the respective units of the TS generating unit 110A. The video encoder <NUM> performs encoding such as MPEG2, H. <NUM>/AVC, or H. <NUM>/HEVC on image data SV, and generates a video stream (a video elementary stream). Examples of the image data SV include image data reproduced from a recording medium such as a HDD and live image data obtained by a video camera.

The audio encoder <NUM> inserts metadata MD into the audio stream under control of the control unit <NUM>. For example, access information for a connection to a predetermined network service, predetermined content information, or the like is considered as the metadata MD. Here, similarly to the above embodiment, access information for a connection to a predetermined network service is assumed to be inserted.

The metadata MD is inserted into the user data region of the audio stream. Although a detailed description is omitted, the insertion of the metadata MD in each compression format is performed similarly to the case in the DASH/MP4 generating unit <NUM> in the above embodiment, and "SDO_payload()" is inserted as the metadata MD (see <FIG>).

The TS formatter 114A converts the video stream output from the video encoder <NUM> and the audio stream output from the audio encoder <NUM>, into PES packets, performs conversion into transport packets, performs multiplexing, and obtains the transport stream TS serving as a multiplexed stream.

The TS formatter 114A inserts the identification information indicating that the metadata MD is inserted into the audio stream under control of the PMT. The inserting of the identification information is performed using the audio user data descriptor (audio_userdata_descriptor). This descriptor will be described in detail later.

An operation of the TS generating unit 110A illustrated in <FIG> will briefly be described. The image data SV is supplied to the video encoder <NUM>. The video encoder <NUM> performs encoding such as H. <NUM>/AVC or H. <NUM>/HEVC on the image data SV, and generates the video stream including encoded video data.

The video stream generated by the video encoder <NUM> is supplied to the TS formatter 114A. The audio stream including the metadata MD embedded in the user data region, which is generated by the audio encoder <NUM> is supplied to the TS formatter 114A.

The TS formatter 114A obtains the transport stream TS as transmission data such that the streams supplied from the respective encoders are packetized and multiplied. The TS formatter 114A inserts the identification information indicating that the metadata MD is inserted into the audio stream under control of the PMT.

<FIG> illustrates an exemplary structure (syntax) of the audio user data descriptor (audio_userdata_descriptor). <FIG> illustrates content of main information (semantics) in the exemplary structure.

An <NUM>-bit field of "descriptor_tag" indicates a descriptor type. Here, an <NUM>-bit field of "descriptor_tag" indicates the audio user data descriptor. An <NUM>-bit field of "descriptor_length" indicates a length (size) of a descriptor, and indicates the number of subsequent bytes as a length of a descriptor.

An <NUM>-bit field of "audio_codec_type" indicates an audio encoding scheme (a compression format). For example, "<NUM>" indicates "MPEGH," "<NUM>" indicates "AAC, " "<NUM>" indicates "AC3," and "<NUM>" indicates "AC4. " As this information is added, at the reception side, it is possible to easily detect an encoding scheme of audio data in the audio stream.

A <NUM>-bit field of "metadata_type" indicates a type of metadata. For example, "<NUM>" indicates that "SDO_payload()" of ATSC including the access information for a connection to a predetermined network service is arranged in the field of "userdata(). " As this information is added, at the reception side, it is possible to easily detect a type of metadata, that is, what metadata it is and determine whether or not the metadata is acquired, for example.

<NUM>-bit flag information of "coordinated_control_flag" indicates whether or not the metadata is inserted into only the audio stream. For example, "<NUM>" indicates that the metadata is inserted into a stream of another component as well, and "<NUM>" indicates that the metadata is inserted into only the audio stream. As this information is added, at the reception side, it is possible to easily detect whether or not the metadata is inserted into only the audio stream.

A <NUM>-bit field of "frequency_type" indicates a type of insertion frequency of the metadata into the audio stream. For example, "<NUM>" indicates that one user data (metadata) is inserted into each audio access unit. "<NUM>" indicates that a plurality of pieces of user data (metadata) are inserted into one audio access unit. "<NUM>" indicates that at least one user data (metadata) is inserted into a first audio access unit for each group including a random access point. As this information is added, at the reception side, it is possible to easily detect the insertion frequency of the metadata into the audio stream.

<FIG> illustrates an exemplary configuration of the transport stream TS. In the exemplary configuration, there is a PES packet "video PES" of a video stream indicated by PID1, and there is a PES packet "audio PES" of an audio stream indicated by PID2. The PES packet is configured with a PES header (PES_header) and a PES payload (PES_payload). Time stamps of a DTS and a PTS are inserted into the PES header. There is the user data region including the metadata in the PES payload of the PES packet of the audio stream.

The transport stream TS includes a PMT as program specific information (PSI). The PSI is information describing a program to which each elementary stream included in the transport stream belongs. The PMT includes a program loop describing information associated with the entire program.

The PMT further includes an elementary stream loop including information associated with each elementary stream. In this exemplary configuration, there is a video elementary stream loop (a video ES loop) corresponding to the video stream, and there is an audio elementary stream loop (an audio ES loop) corresponding to the audio stream.

In the video elementary stream loop (the video ES loop), information such as a stream type and a packet identifier (PID) is arranged in association with the video stream, and a descriptor describing information associated with the video stream is arranged as well. A value of "Stream_type" of the video stream is set to "0x24," and the PID information is regarded to indicate PID1 allocated to the PES packet "video PES" of the video stream as described above. A HEVC descriptor is arranged as one of the descriptors.

In the audio elementary stream loop (the audio ES loop), information such as a stream type and a packet identifier (PID) is arranged in association with the audio stream, and a descriptor describing information associated with the audio stream is arranged as well. A value of "Stream_type" of the audio stream is set to "0x11," and the PID information is regarded to indicate PID2 allocated to the PES packet "audio PES" of the audio stream as described above. The audio user data descriptor (audio_userdata_descriptor) is arranged as one of the descriptors.

<FIG> illustrates an exemplary configuration of the set top box 200A. In <FIG>, portions corresponding to those in <FIG> are denoted by the same reference numerals. The receiving unit 204A receives the transport stream TS transmitted from the service transmission system 100A via the RF transmission path or the communication network transmission path.

A TS analyzing unit 205A extracts the packet of the video stream from the transport stream TS, and transfers the packet of the video stream to the video decoder <NUM>. The video decoder <NUM> reconfigures the video stream from the video packet extracted by the demultiplexer <NUM>, performs a decoding process, and obtains uncompressed image data. The TS analyzing unit 205A extracts the packet of the audio stream from the transport stream TS and reconfigures the audio stream. The audio framing unit <NUM> performs framing on the audio stream reconfigured as described above.

It is also possible to decode the audio stream through an audio decoder (not illustrated) and perform an audio output in parallel with transmission of the audio stream transferred from the TS analyzing unit 205A to the audio framing unit <NUM>.

Further, the TS analyzing unit 205A extracts various kinds of descriptors and the like from the transport stream TS, and transmits the extracted descriptors and the like to the CPU <NUM>. Here, the descriptor also includes the audio user data descriptor serving as the identification information indicating that the metadata is inserted into the audio stream (see <FIG>).

Although a detailed description is omitted, the remaining portions of the set top box 200A illustrated in <FIG> are configured similarly to the set top box <NUM> illustrated in <FIG> and perform similar operations.

<FIG> illustrates an exemplary configuration of the television receiver 300A. In <FIG>, portions corresponding to those in <FIG> are denoted by the same reference numerals. The receiving unit 306A receives the transport stream TS transmitted from the service transmission system 100A via the RF transmission path or the communication network transmission path.

A TS analyzing unit 307A extracts the packet of the video stream from the transport stream TS, and transfers the packet of the video stream to the video decoder <NUM>. The video decoder <NUM> reconfigures the video stream from the video packet extracted by the demultiplexer <NUM>, performs a decoding process, and obtains uncompressed image data. The TS analyzing unit 307A extracts the packet of the audio stream from the transport stream TS and reconfigures the audio stream.

Further, the TS analyzing unit 307A extracts the packet of the audio stream from the transport stream TS, and reconfigures the audio stream. The TS analyzing unit 307A extracts various kinds of descriptors and the like from the transport stream TS, and transmits the extracted descriptors and the like to the CPU <NUM>. Here, the descriptor also includes the audio user data descriptor serving as the identification information indicating that the metadata is inserted into the audio stream (see <FIG>).

Although a detailed description is omitted, the remaining portions of the television receiver 300A illustrated in <FIG> are configured similarly to the television receiver <NUM> illustrated in <FIG> and perform similar operations.

As described above, in the image display systems 10A and 10A' illustrated in <FIG>, the service transmission system 100A inserts the metadata into the audio stream, and inserts the identification information indicating that the metadata is inserted into the audio stream into the layer of the container. Thus, at the reception side (the set top box 200A and the television receiver 300A), it is possible to easily recognize that the metadata is inserted into the audio stream.

In the image display system 10A illustrated in <FIG>, the set top box 200A transmits the audio stream into which the metadata is inserted to the television receiver 300A through the HDMI together with the identification information indicating that the metadata is inserted into the audio stream. Thus, the television receiver 300A can easily recognize that the metadata is inserted into the audio stream and can acquire and use the metadata reliably without waste by performing the process of extracting the metadata inserted into the audio stream based on the recognition.

Further, in the image display system 10A' illustrated in <FIG>, the television receiver 300A extracts the metadata from the audio stream based on the identification information received together with the audio stream and uses the extracted metadata for a process. Thus, it is possible to acquire the metadata inserted into the audio stream reliably without waste and execute the process using the metadata appropriately.

Further, in the above embodiment, the set top box <NUM> is configured to transmit the image data and the audio stream to the television receiver <NUM>. However, the image data and the audio stream may be transmitted to a monitor device, a projector, or the like instead of the television receiver <NUM>. Instead of the set top box <NUM>, a recorder with a reception function, a personal computer, or the like may be used.

Further, in the above embodiment, the set top box <NUM> and the television receiver <NUM> are connected through the HDMI cable <NUM>. However, even whether the set top box <NUM> and the television receiver <NUM> are connected through a digital interface similar to the HDMI in a wired manner or a wireless manner, the invention can similarly be applied.

One of the main features of the present technology lies in that when the metadata is inserted into the audio stream by delivery of the DASH/MP4, the identification information indicating that the metadata is inserted into the audio stream is inserted into the MPD file, and thus, at the reception side, it is possible to easily recognize that the metadata is inserted into the audio stream (see <FIG> and <FIG>).

Claim 1:
A transmission device (<NUM>), comprising:
an information inserting unit (<NUM>) configured to insert, into a SupplementaryDescriptor or an audio user data descriptor of a Media Presentation Description, MPD, metafile, identification information in the form of a descriptor indicating whether or not metadata is inserted into an audio stream; and
a transmitting unit configured to transmit the MPD metafile including meta information for a reception device (<NUM>) to acquire the audio stream into which the metadata is inserted.