JP6801799B2 - Transmitter and transmission method - Google Patents

Description

The present technology relates to a transmitting device and a transmitting method.

In the current broadcasting system, the MPEG-2 TS (Moving Picture Experts Group-2 Transport Stream) method and the RTP (Real Time Protocol) method are widely used as the media transport method (see, for example, Patent Document 1). ). As a next-generation digital broadcasting system, an MMT (MPEG Media Transport) system (see, for example, Non-Patent Document 1) is being studied.

Japanese Unexamined Patent Publication No. 2013-153291

ISO / IEC DIS 23008-1: 2013 (E) Information technology-High efficiency coding and media delivery in heterogeneous environments-Part1: MPEG media transport (MMT)

The purpose of this technology is to make it possible to satisfactorily realize a hybrid service of broadcasting and communication.

The concept of this technology is
A transmission stream generator that generates a transmission stream in which a first transmission packet containing a predetermined component and a second transmission packet containing information about the predetermined component are multiplexed in a time-division manner.
A transmitter that transmits the transmission stream through a predetermined transmission line, and
In the second transmission packet, information on a plurality of distribution protocols including at least location information and protocol identification information for acquiring the specific component in relation to the specific component to be acquired in the communication path, or the information thereof. It is in a transmission device including an information insertion unit that inserts acquisition information for acquiring information of a plurality of distribution protocols.

In the present technology, a transmission stream is generated in which a first transmission packet containing a predetermined component and a second transmission packet containing information about the predetermined component are time-division-multiplexed. For example, the transmission packet may be made to be an MMT (MPEG Media Transport) packet. The transmission unit transmits this transmission stream to the receiving side through a predetermined transmission line. For example, the predetermined transmission line may be a broadcast transmission line.

A plurality of delivery protocols, each of which includes at least location information and protocol identification information for acquiring the specific component in relation to the specific component to be acquired in the communication path, in the second transmission packet by the information insertion unit. Information, or acquisition information for acquiring information on these multiple delivery protocols, is inserted. For example, the plurality of delivery protocols may be configured to be two or more delivery protocols selected from the multicast delivery, MMTP / UDP delivery, MMTP / TCP delivery, MMTP / HTTP delivery and MPU / HTTP delivery protocols. ..

In this case, for example, when indicating that the Putcol identification information is MMTP / UDP distribution, the distribution protocol information may include a parameter for specifying UDP in addition to the URL. Further, in this case, for example, when indicating that the Putcol identification information is MMTP / TCP distribution, the distribution protocol information may include a parameter for specifying TCP in addition to the URL.

For example, a plurality of information of a specific component may be arranged in the second packet, and one of a plurality of distribution protocols may be inserted into each of the plurality of arranged information. Further, for example, one piece of information on a specific component may be arranged in the second packet, and information on a plurality of distribution protocols may be inserted into the one piece of information arranged. Further, for example, in the second packet, one piece of information of a specific component is arranged, and the acquired information for acquiring the information of a plurality of distribution protocols is inserted into the arranged one piece of information. May be done.

As described above, in the present technology, the information of a plurality of distribution protocols including at least the location information and the protocol identification information, respectively, or the plurality of distribution protocols for acquiring the specific component of the communication path in the second transmission packet. The acquisition information for acquiring the information of is inserted. Therefore, on the receiving side, a specific component can be satisfactorily received by the distribution protocol according to its own distribution network environment.

In the present technology, for example, the distribution protocol information may further include packet identification information. In this case, on the receiving side, even if the transmission packets of a plurality of components are multiplexed in the transmission stream, the transmission packets of the specific component can be reliably acquired based on the packet identification information.

Further, in the present technology, for example, information of another component that is multiplexed and distributed with a specific component may be added to each of the information of a plurality of distribution protocols. In this case, the receiving side can easily recognize which component is multiplexed with the specific component in the distributed transmission stream, or whether the distributed transmission stream contains only the specific component.

Further, in the present technology, for example, managed network information may be added to the information of the multicast distribution protocol among the information of a plurality of distribution protocols. In this case, the receiving side can easily determine whether or not it is possible to connect to the managed network for receiving the multicast distribution.

Another concept of this technology is
A receiver comprising a receiver that receives a time-division-multiplexed transmission stream of a first transmission packet containing a predetermined component and a second transmission packet containing information about the predetermined component through a predetermined transmission line.
The second transmission packet includes information on a plurality of delivery protocols including at least location information and protocol identification information for acquiring the specific component in relation to the specific component to be acquired in the communication path, or information on a plurality of distribution protocols. The acquisition information for acquiring the information of the plurality of distribution protocols is inserted, and the acquisition information is inserted.
It further includes a communication unit that selects one receivable delivery protocol from the plurality of delivery protocol information and receives a transmission stream having a third transmission packet including the specific component in the selected delivery protocol through the network. It is in the receiving device.

In the present technology, the receiving unit receives a transmission stream in which a first transmission packet containing a predetermined component and a second transmission packet containing information about the predetermined component are time-division-multiplexed through a predetermined transmission line. To. For example, the transmitted packet may be made to be an MMT packet. Further, for example, the predetermined transmission line may be a broadcast transmission line.

In the second transmission packet, information on a plurality of distribution protocols for acquiring the specific component or information on the plurality of distribution protocols is acquired in relation to the specific component to be acquired in the communication path. Information has been inserted. Each of the information of the plurality of delivery protocols includes at least location information and protocol identification information.

The communication unit selects one distribution protocol that can be received from the plurality of distribution protocol information. Then, the communication unit receives a transmission stream having a third transmission packet including a specific component in the selected delivery protocol through the network.

As described above, in the present technology, one receivable delivery protocol is selected from the information of the plurality of delivery protocols in relation to the specific component provided in the second transmission packet and delivered. Therefore, it is possible to receive a specific component satisfactorily with a distribution protocol according to its own distribution network environment.

In the present technology, for example, the information of the distribution protocol further includes the packet identification information, and the communication unit is based on the packet identification information of the transmission stream having the third received packet. A third transmission packet may be extracted. In this case, even if the transmission packets of a plurality of components are multiplexed in the transmission stream, the third transmission packet can be reliably acquired based on the packet identification information.

Yet another concept of the technology is
A receiver comprising a receiver that receives a time-division-multiplexed transmission stream of a first transmission packet containing a predetermined component and a second transmission packet containing information about the predetermined component through a predetermined transmission line.
The second transmission packet includes information on a plurality of delivery protocols including at least location information and protocol identification information for acquiring the specific component in relation to the specific component to be acquired in the communication path, or information on a plurality of distribution protocols. The acquisition information for acquiring the information of the plurality of distribution protocols is inserted, and the acquisition information is inserted.
The receiving device further includes a processing unit that processes a transmission stream received by the receiving unit.

According to this technology, a hybrid service of broadcasting and communication can be satisfactorily realized. It should be noted that the effects described in the present specification are merely exemplary and not limited, and may have additional effects.

It is a block diagram which shows the configuration example of the broadcasting / communication hybrid system as an embodiment. It is a figure which shows the stack model of the signal composition example of MMT / broadcasting. It is a figure which shows the configuration example of the MMT system broadcasting stream. It is a figure which shows the image of the broadcast signal of one channel (broadcast program) transmitted from a broadcast transmission system to a receiving terminal. It is a figure which shows the configuration example of the MMT packet and the configuration example of the MMTP payload (MMTP payload). It is a figure which shows the stack model of the signal composition example of MMT / communication. It is a figure which shows an example of the MMT distribution network environment. It is a figure which shows the structure example of PA message (Package Access Message) and MP table (MPT: MMT Package Table) schematicly. It is a figure which shows the explanation of the main parameter of a PA message. It is a figure which shows the explanation of the main parameter of an MP table. It is a figure which shows the structure example (Syntax) of a PA message. It is a figure which shows the structure example (Syntax) of the MP table (MPT). It is a figure which shows a part of the structure example (Syntax) of "MMT_general_location_info ()". It is a figure which shows the description example of the MP table (MPT) in which the information of a plurality of distribution protocols is inserted in relation to the specific component (asset) of a communication path. It is a figure which shows the structural example of the communication delivery descriptor. It is a figure which shows the content of the main information in the structural example of a communication delivery descriptor. It is a figure which shows the description example of the MP table (MPT) in which the information of a plurality of distribution protocols is inserted in relation to the specific component (asset) of a communication path. It is a figure which shows the structural example of the communication delivery descriptor. It is a figure which shows the description example of the MP table (MPT) in which the acquisition information for acquiring the information of a plurality of distribution protocols is inserted in relation to the specific component (asset) of a communication path. It is a figure which shows the structure example of the BD table which describes the information of a plurality of distribution protocols, and the content of each information. It is a flowchart which shows an example of view selection / reception processing in a receiving terminal. (A) It is a figure for demonstrating the reception sequence in the case of receiving the asset delivered by the multicast delivery protocol. (B) It is a figure for demonstrating the reception sequence in the case of receiving the asset delivered by the protocol of MMTP / UDP delivery. (C) It is a figure for demonstrating the reception sequence in the case of receiving the asset delivered by the protocol of MMTP / TCP delivery. (D) It is a figure for demonstrating the reception sequence in the case of receiving the asset delivered by the protocol of MMTP / HTTP delivery. It is a figure for demonstrating the cutting process in the multiplexed stream of MMTP / HTTP. (E) It is a figure for demonstrating the reception sequence in the case of receiving the asset delivered by the MPU / HTTP delivery protocol. It is a block diagram which shows the configuration example of a broadcast transmission system. It is a block diagram which shows the configuration example of a receiving terminal.

Hereinafter, embodiments for carrying out the invention (hereinafter referred to as “embodiments”) will be described. The explanation will be given in the following order.
1. 1. Embodiment 2. Modification example

<1. Embodiment>
[Broadcasting / communication hybrid system configuration example]
FIG. 1 shows a configuration example of the broadcasting / communication hybrid system 10. In the broadcast / communication hybrid system 10, a broadcast transmission system 100 and a distribution server 300 are arranged on the transmitting side, and a receiving terminal 200 is arranged on the receiving side. The distribution server 300 is connected to the receiving terminal 200 through the communication network 400.

The broadcast transmission system 100 transmits an IP (Internet Protocol) type broadcast signal including components (assets) such as video and audio as transmission media. The distribution server 300 sends a transmission stream in which IP packets including components (asset) such as video and audio are continuously arranged as a transmission medium to the receiving side through a communication network 400, for example, in response to a request from the receiving side. To deliver.

The receiving terminal 200 receives an IP-type broadcast signal sent from the broadcast transmission system 100, and also receives a transmission stream in which IP packets are continuously arranged from the distribution server 300. The receiving terminal 200 acquires transmission media (components) such as video and audio to be presented from the received signal obtained by such hybrid transmission of broadcasting and communication, and presents images, sounds, and the like.

In the broadcast signal of the IP system, information of a plurality of distribution protocols for acquiring the specific component is inserted in relation to the specific component to be acquired in the communication path. Each of the information of the plurality of delivery protocols includes at least location information and protocol identification information. The receiving terminal 200 selects one receivable distribution protocol from a plurality of distribution protocol information, and receives the distribution of a specific component by the distribution protocol.

FIG. 2 shows a stack model of an MMT / broadcast signal configuration example. A TLV (Type Length Value) transmission packet exists in the lower layer. An IP packet is placed on top of this TLV transmission packet. In addition, there is also a TLV transmission packet in which a transmission control signal is recorded as signaling information.

UDP (User Datagram Protocol) is placed on top of the IP packet. Then, an MMT (MPEG Media Transport) packet is placed on the UDP. The payload portion of the MMT packet includes an MFU (MMT Fragment Unit) including encoded data of components such as video and audio, or a signaling message including information about a transmission medium.

FIG. 3 shows a configuration example of an MMT system broadcast stream. FIG. 3A shows an elementary stream of video (Video ES). The elementary stream of this video is divided into chunks of a predetermined size and placed in the payload portion of the MFU as shown in FIG. 3 (b).

As shown in FIG. 3C, an MMT payload header is added to the MFU to form an MMTP payload. Then, as shown in FIG. 3D, an MMT header is further added to the MMTP payload to form an MMT packet. In addition, there is also an MMT packet including a signaling message in the payload part. As shown in FIG. 3E, a UDP header, an IP header, and a TLV header are added to the MMT packet to generate a TLV packet that constitutes an MMT system broadcast stream.

Although not shown, as the TLV packet, there is also a TLV packet including an MMT packet of another component such as audio. This MMT system broadcast stream has a first packet (MMT packet) including a transmission medium (component) and a second packet (MMT packet) including signaling information.

FIG. 4 shows an image of a broadcast signal of one channel (broadcast program) transmitted from the broadcast transmission system 100 to the receiving terminal 200. This broadcast signal includes MMT packets including signaling messages as well as MMT packets such as video and audio. As the signaling message, for example, there is a PA message (PA message) including an MP table (MP table) and the like.

FIG. 5A shows a configuration example of an MMT packet. The MMT packet is composed of an MMT packet header (MMTP header) and an MMTP payload (MMTP payload). The 2-bit field of "V" indicates the version of the MMT protocol. According to the first edition of the MMT standard, this field is set to "00". The 1-bit field of "C" indicates the packet counter flag (packet_counter_flag) information, and is "1" when the packet counter flag is present. The 2-bit field of "FEC" indicates the FEC type (FEC_type).

The 1-bit field of "X" indicates the extension header flag (extension_flag) information, and is set to "1" when the header of the MMT packet is extended. In this case, there is a field of "header_extension" described later. The 1-bit field of "R" indicates the RAP flag (RAP_flag) information, and is set to "1" when the MMT payload transmitted by this MMT packet includes the head of a random access point.

The 6-bit field of "type" is the payload type (payload_type) information and indicates the data type of the MMTP payload. For example, "0x00" indicates that the payload is an MPU (Media Processing Unit), and "0x02" indicates that the payload is a signaling message.

The 16-bit field of "packet_id" indicates a packet identifier (packet_id) for identifying the data type of the payload. The 32-bit field of "timestamp" indicates a type stamp for transmission, that is, the time when the MMT packet leaves the transmitting side. This time is represented in NTP short format. The 32-bit field of "packet_sequence_number" indicates the sequence number of the MMT packet having the same packet identifier (packet_id). The 32-bit field of "packet_counter" indicates the order of MMT packets in the same IP data flow regardless of the value of the packet identifier (packet_id).

When the 1-bit flag information of "X" described above is "1", the field of "header_extension" which is an MMT extension header is arranged after the 32-bit field of "packet_counter". After that, there are a "payload data" field and a "source_FEC_payload_ID" field that make up the MMTP payload.

FIG. 5B shows a configuration example (Syntax) of the MMTP payload (MMTP payload) arranged in the “payload data” field of the above-mentioned MMT packet. In this example, the case where the "type" of the MMT header is "0x00" is the MPU mode is shown. First there is header information. The 16-bit field of "length" indicates the byte size of the entire MMTP payload. The 4-bit field of "FT" indicates the field type. “0” indicates that “MPU metadata” is included, “1” indicates that “Movie Fragment metadata” is included, and “2” indicates that “MFU” is included.

Here, the MFU (MMT Fragment Unit) is a subdivided MPU, that is, a fragment. For example, in the case of video, this MFU can be set to correspond to one NAL unit. Further, for example, when sending via a communication network transmission line, this MFU may be configured with one or a plurality of MTU sizes.

Further, the MPU starts from a random access point (RAP: Random Access Pint) and includes one or a plurality of access units (AU: Access Unit). Specifically, for example, one GOP (Group Of Picture) picture may form one MPU. This MPU is defined for each asset (by component). Therefore, a video MPU containing only video data is created from the video assets, and an audio MPU containing only audio data is created from the audio assets.

The 1-bit flag information of "T" indicates whether to transmit timed media (Timed Media) or non-timed media (Non-Timed Media). “1” indicates timed media, and “0” indicates non-timed media.

The 2-bit field of "f_i" contains an integer number of data units (DU) in the field of "DU payload", or the first fragment (Fragment) obtained by fragmenting the data unit ( Indicates whether the first), middle, or last is included. “0” indicates that an integer number of data units are contained, “1” indicates that the first fragment is contained, “2” indicates that an intermediate fragment is contained, and “3”. Indicates that the last fragment is included.

The 1-bit flag information of "A" indicates whether or not a plurality of data units are contained in the "DU payload" field. "1" indicates that it is contained, and "0" indicates that it is not contained. The 8-bit field of "frag_counter" indicates the number of the fragment when "f_i" is 1 to 3.

The 32-bit field of "MPU_sequence_number" is a number indicating the order of MPUs and is information for identifying MPUs. For example, when one GOP constitutes one MPU, when the "MPU_sequence_number" of a certain GOP is "i", the "MPU_sequence_number" of the next GOP is "i + 1".

After this "MPU_sequence_number" field, "DU_length", "DU_header", and "DU_payload" fields are placed. The 16-bit field of "DU_length" does not exist when the above-mentioned "A = 0", that is, when the field of "DU payload" does not contain a plurality of data units. Also, the "DU_header" field does not exist when "FT = 0/1", that is, when it includes "MPU metadata" and "Movie Fragment metadata".

FIG. 6 shows a stack model of a signal configuration example of MMT / communication. As distribution options by MMT / communication, (A) multicast distribution, (B) MMTP / UDP distribution, (C) MMTP / TCP distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution can be considered.

"(A) Multicast delivery"
In the case of multicast distribution, IP packets exist in the lower layer. UDP (User Datagram Protocol) is placed on top of this IP packet. Then, an MMT (MPEG Media Transport) packet is placed on the UDP. The payload portion of this MMT packet includes an MPU containing encoded data of components such as video and audio.

In the case of this multicast distribution, it is the most desirable method for broadcasting / communication hybrid use in consideration of congestion handling. Further, in the case of this multicast distribution, since it is UDP transmission, the transmission efficiency is good, but there is a problem of packet loss, so there is a possibility that AL-FEC (Application Layer-Forward Error Correction) is required.

Further, in the case of this multicast distribution, only the receiving terminal directly connected to the managed network can be used. Further, in the case of this multicast distribution, there are cases where the multicast IP stream transmits an MMTP stream in which a plurality of assets (components) are multiplexed, and a case where an MMTP stream including only a single asset is transmitted.

"(B) MMTP / UDP delivery"
In the case of MMTP / UDP distribution, IP packets exist in the lower layer. UDP (User Datagram Protocol) is placed on top of this IP packet. Then, the MMT packet is placed on the UDP. The payload portion of this MMT packet includes an MPU containing encoded data of components such as video and audio.

In the case of this MMTP / UDP distribution, since it is unicast, there is a problem of congestion when using the broadcasting / communication hybrid. Further, in the case of this MMTP / UDP distribution, since it is UDP transmission, the transmission efficiency is good, but AL-FEC may be required. Further, in the case of multicast distribution, the total delay and synchronization are better than those of TCP.

Also, in the case of this MMTP / UDP distribution, since it is unicast, it can be widely used with general Internet-connected devices, but it may not be available by default depending on the router settings. In the case of this MMTP / UDP distribution, there are cases where the IP stream transmits an MMTP stream in which a plurality of assets (components) are multiplexed, and a case where an MMTP stream containing only a single asset is transmitted.

"(C) MMTP / TCP delivery"
In the case of MMTP / TCP distribution, IP packets exist in the lower layer. TCP (Transmission Control Protocol) is placed on top of this IP packet. Then, the MMT packet is placed on the TCP. The payload portion of this MMT packet includes an MPU containing encoded data of components such as video and audio.

In the case of this MMTP / TCP distribution, since it is unicast, it can be widely used in general Internet-connected devices. Further, in the case of this MMTP / TCP distribution, since it is unicast, there is a problem of congestion when using the broadcasting / communication hybrid. Further, in the case of this MMTP / TCP distribution, efficiency is sacrificed because it is TCP transmission, but since retransmission is possible, AL-FEC becomes unnecessary.

Further, in the case of this MMTP / TCP distribution, there are cases where the IP stream transmits an MMTP stream in which a plurality of assets (components) are multiplexed, and a case where an MMTP stream including only a single asset is transmitted.

"(D) MMTP / HTTP delivery"
In the case of MMTP / HTTP distribution, IP packets exist in the lower layer. TCP is placed on top of this IP packet. Then, HTTP (Hyper Text Transfer Protocol) is placed on TCP, and MMT packets are placed on it. The payload portion of this MMT packet includes an MPU containing encoded data of components such as video and audio.

In the case of this MMTP / HTTP distribution, since it is HTTP, it can be widely used in general Internet-connected devices. Further, in the case of this MMTP / HTTP distribution, since it is unicast, there is a problem of congestion when using the broadcasting / communication hybrid. Further, in the case of this MMTP / HTTP distribution, efficiency is sacrificed because it is TCP transmission, but since retransmission is possible, AL-FEC becomes unnecessary.

Further, in the case of this MMTP / HTTP distribution, there are cases where the IP stream transmits an MMTP stream in which a plurality of assets (components) are multiplexed, and a case where an MMTP stream including only a single asset is transmitted.

"(E) MPU / HTTP delivery"
In the case of MPU / HTTP distribution, IP packets exist in the lower layer. TCP is placed on top of this IP packet. Then, HTTP is placed on TCP, and the payload portion of this HTTP packet includes an MPU containing encoded data of components such as video and audio.

In the case of this MPU / HTTP distribution, since it is HTTP, it can be widely used in general Internet-connected devices. Further, in the case of this MPU / HTTP distribution, since it is unicast, there is a problem of congestion when using the broadcasting / communication hybrid. Further, in the case of this MPU / HTTP distribution, efficiency is sacrificed because it is TCP transmission, but since it can be retransmitted, AL-FEC becomes unnecessary.

Further, in the case of this MPU / HTTP distribution, since the MMT packet does not intervene, the transmission efficiency is improved as compared with the MMTP / HTTP distribution, but on the contrary, there is a problem that information such as the MMTP header is lost. Further, in the case of this MPU / HTTP distribution, the receiving terminal acquires individual MPU files of a single asset (component) by HTTP.

FIG. 7 shows an example of the MMT distribution network environment. The receiving terminals 200a, 200b, and 200c can be connected to the edge router (ER) of the managed network MNa via the home router (HR), respectively. Therefore, these receiving terminals 200a, 200b, and 200c can receive distribution from the MMT / multicast server whose IP address in the managed network is "a" by the protocol of (A) multicast distribution.

Further, these receiving terminals 200a, 200b, and 200c can be connected to the MMT server via the home router HR, the managed network MNa, and the like, respectively. Further, the home router (HR) to which these receiving terminals 200a, 200b, and 200c are connected is set so that UDP can be used. Therefore, these receiving terminals 200a, 200b, and 200c can be any of (B) MMTP / UDP distribution, (C) MMTP / TCP distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution from the MMT server. It is also possible to receive distribution using the protocol of.

Further, the receiving terminals 200g, 200h, and 200i can be connected to the edge router (ER) of the managed network MNb via the home router (HR), respectively. Therefore, these receiving terminals 200g, 200h, and 200i can receive distribution by the protocol of (A) multicast distribution from the MMT / multicast server whose IP address is "b" in the managed network.

Further, these receiving terminals 200g, 200h, and 200i can be connected to the MMT server via the home router HR, the managed network MNb, and the like, respectively. Further, the home router (HR) to which these receiving terminals 200g, 200h, and 200i are connected is set so that UDP can be used. Therefore, these receiving terminals 200g, 200h, and 200i can be delivered from the MMT server by any of (B) MMTP / UDP distribution, (C) MMTP / TCP distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution. It is also possible to receive distribution using the protocol of.

Further, the receiving terminal 200d can be connected to the MMT server via the home router HR, and the home router (HR) to which the receiving terminal 200d is connected is set so that UDP can also be used. Therefore, the receiving terminal 200d can receive distribution by any of the protocols of (B) MMTP / UDP distribution, (C) MMTP / TCP distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution. Is.

Further, the receiving terminals 200e and 200f can be connected to the MMT server via the home router HR, but the home router (HR) to which these receiving terminals 200e and 200f are connected can use UDP. Not set. Therefore, these receiving terminals 200e and 200f can receive distribution only by one of the protocols of (D) MMTP / HTTP distribution and (E) MPU / HTTP distribution.

FIG. 8 schematically shows the structure of a PA message (Package Access Message) and an MP table (MPT: MMT Package Table). In addition, FIG. 9 shows a description of the main parameters of the PA message, and FIG. 10 shows a description of the main parameters of the MP table.

“Message_id” is a fixed value that identifies a PA message in various signaling information. “Version” is an 8-bit integer value indicating the version of the PA message. For example, if some parameters that make up the MP table are also updated, they are incremented by +1. “Length” is the number of bytes indicating the size of the PA message, which is counted immediately after this field.

In the "extension" field, the index information of the table placed in the payload (Payload) field is placed. In this field, each field of "table_id", "table_version", and "table_length" is arranged as many as the number of tables. "Table_id" is a fixed value that identifies the table. "Table_version" indicates the version of the table. "Table_length" is the number of bytes indicating the size of the table.

An MP table (MPT) and a predetermined number of other tables (Other tables) are arranged in the fields of the payload (Payload) of the PA message. The structure of the MP table will be described below.

“Table_id” is a fixed value that identifies the MP table in various signaling information. “Version” is an 8-bit integer value indicating the version of the MP table. For example, if some parameters that make up the MP table are also updated, they are incremented by +1. “Length” is the number of bytes indicating the size of the MP table, which is counted immediately after this field.

The "pack_id" is identification information as an entire package including all assets (components) transmitted by broadcasting and communication as components. This identification information is text information. "Pack_id_len" indicates the size (number of bytes) of the text information. The "MPT_descripors" field is the descriptor storage area for the entire package. "MPT_dsc_len" indicates the size (number of bytes) of the field.

"Num_of_asset" indicates the number of assets (components) as elements that make up the package. The following asset loops are placed for this number of minutes. “Asset_id” is information (asset ID) that uniquely identifies an asset. This identification information is text information. "Asset_id_len" indicates the size (number of bytes) of the text information. "Gen_loc_info" is information indicating the location where the asset is acquired. The "asset_descriptors" field is a storage area for descriptors related to assets. "Asset_dsc_len" indicates the size (number of bytes) of the field.

Note that FIG. 11 shows a structural example (Syntax) of the PA message described above. Further, FIG. 12 shows a structural example (Syntax) of the above-mentioned MP table (MPT). The field of "gen_loc_info" in FIG. 8 corresponds to the field of "asset_location" in FIG. 12, and a plurality of "MMT_general_location_info ()" can be arranged as information indicating the location of the asset acquisition destination. Further, the field of "asset_descriptors" in FIG. 8 corresponds to the field of "asset_descriptors" in FIG.

FIG. 13 shows a part of the structural example (Syntax) of “MMT_general_location_info ()”. The 8-bit field of "location_type" indicates the type of information indicating the location where the asset is acquired (hereinafter, appropriately referred to as "location information"). In the case of the asset delivered by the above-mentioned (A) multicast delivery protocol, the "location_type" is set to "0x01" or "0x02", and the location information includes the source address (ipv4_src_addr, ipv6_src_addr) and the destination address (ipv4_dst_addr, ipv6_dst_addr), destination port number (dst_port), and packet identifier (packt_id) are inserted. In this case, "location_type" identifies that the distribution is multicast.

Further, in the case of an asset distributed by the above-mentioned (B) MMTP / UDP distribution, (C) MMTP / TCP distribution, (D) MMTP / HTTP distribution or (E) MPU / HTTP distribution protocol, "location_type" is It is set to "0x05", and a URL (Uniform Resource Locator) is arranged as location information.

Here, (B) in the case of an asset delivered by the protocol of MMTP / UDP delivery, "rtsp: // ~ .mmt" is specified as the schema, and UDP is further specified by the query field. A parameter to specify and a parameter to specify the packet identifier (packet_id) are added. After all, the URL in this case is expressed as "rtsp: // ~ .mmt? Pr = udp & pid = 1". In this case, "rtsp" and "pr = udp" identify the MMTP / UDP delivery.

(C) In the case of an asset distributed by the MMTP / TCP distribution protocol, "rtsp: // ~ .mmt" is specified as the schema, and TCP is specified by the query field. A parameter to be specified and a parameter to specify the packet identifier (packet_id) are added. After all, the URL in this case is expressed as "rtsp: // ~ .mmt? Pr = udp & pid = 1". In this case, "rtsp" and "pr = tcp" identify MMTP / TCP delivery.

Further, in the case of an asset delivered by the (D) MMTP / HTTP delivery protocol, "http: // ~ .mmt" is specified as the schema, and the packet identifier (Query Field) is used. A parameter that specifies packet_id) is added. After all, the URL in this case is expressed as "http: // ~ .mmt? Pr = pid = 1". In this case, "http" and "mmt" identify the MMTP / HTTP delivery.

Further, in the case of an asset distributed by the (E) MPU / HTTP distribution protocol, "http: // ~ .mp4" is specified as the schema. That is, the URL in this case is expressed as "http: // ~ .mp4". In this case, "http" and "mp4" identify the MPU / HTTP delivery.

"Insert information of multiple distribution protocols or their acquisition information"
In this embodiment, the MP table (MPT) contains information on a plurality of distribution protocols, or a plurality of distributions, in relation to an asset (component) transmitted by communication, that is, a specific component to be acquired in the communication path. The acquisition information for acquiring the protocol information is inserted. The information of the plurality of delivery protocols includes at least location information and protocol identification information, respectively. As the insertion method, for example, the following methods 1, 2, and 3 can be considered.

"Method 1"
In the case of the method 1, a plurality of information of a specific component (asset) is arranged in the MP table (MPT), and one of a plurality of distribution ptrocols is inserted into each of the plurality of arranged information. .. In this case, only one "MMT_general_location_info ()" is described for each asset (see FIG. 12).

This method 1 will be further described. Here, a use case will be described in which there are two video and audio signal sets, one of which is the main signal and is transmitted by broadcasting, and the other is not the main signal and is transmitted by communication. Further, in this use case, it is assumed that distribution can be performed by three protocols: (A) multicast distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution.

FIG. 14A schematically shows a description example of the MP table (MPT). The assets (components) of "Asset1" indicate the video signal (Video1) to be broadcast and transmitted. The asset (component) of "Asset2" indicates an audio signal (Audio1) to be broadcast and transmitted.

The assets (components) of "Asset3" indicate (A) a video signal (Video2) that is communicated and transmitted by the protocol of multicast distribution. The source address (ipv4_src_addr, ipv6_src_addr), the destination address (ipv4_dst_addr, ipv6_dst_addr), the destination port number (dst_port), and the packet identifier (packt_id) are inserted into the "MMT_general_location_info ()" of this asset.

In addition, a newly defined communication delivery descriptor (broadband_delivery_descriptor) is inserted in the "asset_descriptors" field of this asset. This descriptor contains the communication transmission protocol type (delivery protocol type) "type = broadband_delivery_type", information on other assets that are multiplexed and delivered with the relevant asset "mg = multiplex_group", and available managed networks. Information "ANmap1" is described. Here, "type" is used to indicate (A) multicast distribution, and "mg" is used to indicate that the distribution is multiplexed with other assets constituting group 1.

FIG. 15 shows a structural example (Syntax) of the communication distribution descriptor (broadband_delivery_descriptor), and FIG. 16 shows the contents (Semantics) of the main information in the structural example. The 16-bit field of "descriptor_tag" indicates the descriptor type. Here, it is shown that it is a communication distribution descriptor. The 8-bit field of "descriptor_length" indicates the length (size) of the descriptor, and indicates the number of bytes thereafter as the descriptor length.

The 3-bit field of "broadband_delivery_type" indicates the communication transmission protocol type (delivery protocol type). For example, "1" indicates type A (type A), that is, (A) multicast distribution. “2” indicates type B (type B), that is, (B) MMTP / UDP delivery. “3” indicates type C (type C), that is, (C) MMTP / TCP delivery. “4” indicates type D, that is, (D) MMTP / HTTP delivery. “5” indicates type E, that is, (E) MPU / HTTP delivery. Further, "7" indicates that it is specified in the BD table (BDT: Broadband_Delivery_Table).

The 1-bit field of "ip_version" indicates the IP version. For example, "0" indicates "IPv4" and "1" indicates "IPv6". The 4-bit field of "multiplex_group" indicates the group ID of the multiplexed stream. If it is not multiplexed, it is set to "0", and if it is multiplexed, an identification value of one or more multiplexed streams is specified.

Related additional information is placed in the "additional_network_info ()" field. In the case of type A, it is an 8-bit field of "available_network_map". The 8-bit field of this "available_network_map" indicates the available managed network bitmap. In this case, bits 0 to 7 are assigned to each carrier.

Returning to FIG. 14, the asset (component) of "Asset4" shows the video signal (Video2) which is communicated and transmitted by the protocol of (D) MMTP / HTTP distribution. The URL is inserted in "MMT_general_location_info ()" of this asset. In this case, as described above, "http: // ~ .mmt" is specified as the schema, and a parameter for specifying the packet identifier (packet_id) is added by the query field.

In addition, the above-mentioned communication distribution descriptor (broadband_delivery_descriptor) is inserted in the "asset_descriptors" field of this asset (see FIG. 15). Here, "type" is defined as (D) MMTP / HTTP distribution, and "mg" is defined as being multiplexed and distributed with other assets constituting Group 2. ..

The asset (component) of "Asset 5" indicates a video signal (Video2) which is communicated and transmitted by the (E) MPU / HTTP distribution protocol. The URL is inserted in "MMT_general_location_info ()" of this asset. In this case, as described above, "http: // ~ .mp4" is specified as the schema.

In addition, the above-mentioned communication distribution descriptor (broadband_delivery_descriptor) is inserted in the "asset_descriptors" field of this asset (see FIG. 15). Here, "type" is defined as (E) MPU / HTTP delivery, and "mg" is defined as "0", indicating that it is not multiplexed. As a result, on the receiving side, as shown in FIG. 14 (b), it can be seen that this "Asset 5" is delivered independently.

The description order of "Asset3", "Asset4", and "Asset5" indicates, for example, the priority order.

The assets (components) of "Asset 6" indicate (A) an audio signal (Audio2) that is communicated and transmitted by the protocol of multicast distribution. The source address (ipv4_src_addr, ipv6_src_addr), the destination address (ipv4_dst_addr, ipv6_dst_addr), the destination port number (dst_port), and the packet identifier (packt_id) are inserted into the "MMT_general_location_info ()" of this asset.

In addition, the above-mentioned communication distribution descriptor (broadband_delivery_descriptor) is inserted in the "asset_descriptors" field of this asset (see FIG. 15). Here, "type" is assumed to indicate (A) multicast distribution, and available managed network information "ANmap1" is also described.

Further, "mg" is defined to indicate that the asset is multiplexed and distributed with other assets constituting the group 1. As a result, on the receiving side, as shown in FIG. 14 (b), it can be seen that this "Asset 6" is multiplexed and delivered with the above-mentioned "Asset 3". On the receiving side, both "Asset 3" and "Asset 6" can be obtained from this multiplexed stream.

The asset (component) of "Asset7" indicates an audio signal (Audio2) that is communicated and transmitted by the (D) MMTP / HTTP distribution protocol. The URL is inserted in "MMT_general_location_info ()" of this asset. In this case, as described above, "http: // ~ .mmt" is specified as the schema, and a parameter for specifying the packet identifier (packet_id) is added by the query field.

In addition, the above-mentioned communication distribution descriptor (broadband_delivery_descriptor) is inserted in the "asset_descriptors" field of this asset (see FIG. 15). Here, "type" is defined as (D) MMTP / HTTP distribution, and "mg" is defined as being multiplexed and distributed with other assets constituting Group 2. .. As a result, on the receiving side, as shown in FIG. 14B, it can be seen that this "Asset 7" is multiplexed and delivered with the above-mentioned "Asset 4". On the receiving side, both "Asset 4" and "Asset 7" can be obtained from this multiplexed stream.

The asset (component) of "Asset 8" indicates an audio signal (Audio2) which is communicated and transmitted by the (E) MPU / HTTP distribution protocol. The URL is inserted in "MMT_general_location_info ()" of this asset. In this case, as described above, "http: // ~ .mp4" is specified as the schema.

In addition, the above-mentioned communication distribution descriptor (broadband_delivery_descriptor) is inserted in the "asset_descriptors" field of this asset (see FIG. 15). Here, "type" is defined as (E) MPU / HTTP delivery, and "mg" is defined as "0", indicating that it is not multiplexed. As a result, on the receiving side, as shown in FIG. 14 (b), it can be seen that this "Asset 8" is delivered independently.

The description order of "Asset6", "Asset7", and "Asset8" indicates, for example, the priority order.

"Method 2"
In the case of the method 2, one piece of information on a specific component (asset) is arranged in the MP table (MPT), and information on a plurality of distribution ptrocols is inserted into the one piece of the arranged information. In this case, a plurality of "MMT_general_location_info ()" are described for each asset (see FIG. 12). In the MP table, "MMT_general_location_info ()" is a loop, so multiple descriptions are possible.

This method 2 will be further described. Here, as in the above description of "Method 1", there are two video and audio signal sets, one of which is the main signal and is transmitted by broadcasting, and the other is not the main signal and is transmitted by communication. Explain in use cases. Further, in this use case, it is assumed that distribution can be performed by three protocols: (A) multicast distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution.

FIG. 17A schematically shows a description example of the MP table (MPT). The assets (components) of "Asset1" indicate the video signal (Video1) to be broadcast and transmitted. The asset (component) of "Asset2" indicates an audio signal (Audio1) to be broadcast and transmitted.

The assets (components) of "Asset3" indicate the video signal (Video2) that is transmitted by communication. Three "MMT_general_location_info ()" are described in the "asset_location" field of this asset.

In the first "MMT_general_location_info ()", the location information in the case of (A) multicast distribution having the highest priority is inserted. That is, the source address (ipv4_src_addr, ipv6_src_addr), the destination address (ipv4_dst_addr, ipv6_dst_addr), the destination port number (dst_port), and the packet identifier (packt_id) are inserted into this "MMT_general_location_info ()".

In the second "MMT_general_location_info ()", the location information in the case of (D) MMTP / HTTP distribution having the next highest priority is inserted. That is, the URL is inserted in this "MMT_general_location_info ()". In this case, as described above, "http: // ~ .mmt" is specified as the schema, and a parameter for specifying the packet identifier (packet_id) is added by the query field.

In the third "MMT_general_location_info ()", the location information in the case of (E) MPU / HTTP distribution having the lowest priority is inserted. That is, the URL is inserted in this "MMT_general_location_info ()". In this case, as described above, "http: // ~ .mp4" is specified as the schema.

In addition, a newly defined communication delivery descriptor (broadband_delivery_descriptor) is inserted in the "asset_descriptors" field of this asset. In this descriptor, the communication transmission protocol type (delivery protocol type) "type = broadband_delivery_type" corresponding to the above-mentioned three "MMT_general_location_info ()" and other assets that are multiplexed and delivered with the relevant asset Information "mg = multiplex_group" is described. When the location information in the case of (A) multicast distribution is inserted in "MMT_general_location_info ()", the available managed network information "ANmap" is also described.

Here, corresponding to the first "MMT_general_location_info ()", "type" is assumed to indicate (A) multicast delivery, and "mg" is multiplexed with other assets constituting group 1. It is supposed to indicate that it will be delivered. Also, "ANmap" is referred to as "ANmap1" to indicate the available managed networks.

In addition, corresponding to the second "MMT_general_location_info ()", "type" is defined as (D) MMTP / HTTP distribution, and "mg" is multiplexed with other assets constituting group 2. It is supposed to indicate that it is delivered.

Further, corresponding to the third "MMT_general_location_info ()", "type" is defined as (E) MPU / HTTP distribution, "mg" is set to "0", and is not multiplexed. It is supposed to show that. As a result, on the receiving side, as shown in FIG. 17B, in the case of (E) MPU / HTTP distribution, it can be seen that "Asset3" is distributed independently.

FIG. 18 shows a structural example (Syntax) of the communication distribution descriptor (broadband_delivery_descriptor). The 16-bit field of "descriptor_tag" indicates the descriptor type. Here, it is shown that it is a communication distribution descriptor. The 8-bit field of "descriptor_length" indicates the length (size) of the descriptor, and indicates the number of bytes thereafter as the descriptor length.

The 8-bit field of "number_of_delivery" indicates the number of delivery protocols that can be delivered. The 3-bit field of "broadband_delivery_type", the 1-bit field of "ip_version", the 4-bit field of "multiplex_group", and the 8-bit field of "available_network_map" are repeated as many times as the number of distribution protocols.

The 3-bit field of "broadband_delivery_type" indicates the communication transmission protocol type (delivery protocol type) (see FIG. 16). For example, "1" indicates type A (type A), that is, (A) multicast distribution. “2” indicates type B (type B), that is, (B) MMTP / UDP delivery. “3” indicates type C (type C), that is, (C) MMTP / TCP delivery. “4” indicates type D, that is, (D) MMTP / HTTP delivery. “5” indicates type E, that is, (E) MPU / HTTP delivery. Further, "7" indicates that it is specified by BDT (broadband_delivery_Table).

The 1-bit field of "ip_version" indicates the IP version (see FIG. 16). For example, "0" indicates "IPv4" and "1" indicates "IPv6". The 4-bit field of "multiplex_group" indicates the group ID of the multiplexed stream (see FIG. 16). If it is not multiplexed, it is set to "0", and if it is multiplexed, an identification value of one or more multiplexed streams is specified. The 8-bit field of "available_network_map" indicates the available managed network bitmap. In this case, bits 0 to 7 are assigned to each carrier (see FIG. 16).

Note that, except for the case of (A) multicast distribution in which "broadband_delivery_type" is set to "1", all bits 0 to 7 of the 8-bit field of "available_network_map" are set to "0", and this field is substantially set to "0". Not used for.

The assets (components) of "Asset4" indicate the audio signals (Audio2) that are transmitted by communication. Three "MMT_general_location_info ()" are described in the "asset_location" field of this asset.

In the first "MMT_general_location_info ()", the location information in the case of (A) multicast distribution having the highest priority is inserted. That is, the source address (ipv4_src_addr, ipv6_src_addr), the destination address (ipv4_dst_addr, ipv6_dst_addr), the destination port number (dst_port), and the packet identifier (packt_id) are inserted into this "MMT_general_location_info ()".

In the second "MMT_general_location_info ()", the location information in the case of (D) MMTP / HTTP distribution having the next highest priority is inserted. That is, the URL is inserted in this "MMT_general_location_info ()". In this case, as described above, "http: // ~ .mmt" is specified as the schema, and a parameter for specifying the packet identifier (packet_id) is added by the query field.

In the third "MMT_general_location_info ()", the location information in the case of (E) MPU / HTTP distribution having the lowest priority is inserted. That is, the URL is inserted in this "MMT_general_location_info ()". In this case, as described above, "http: // ~ .mp4" is specified as the schema.

In addition, the above-mentioned communication distribution descriptor (broadband_delivery_descriptor) is inserted in the "asset_descriptors" field of this asset (see FIG. 18). In this descriptor, the communication transmission protocol type (delivery protocol type) "type = broadband_delivery_type" corresponding to the above-mentioned three "MMT_general_location_info ()" and other assets that are multiplexed and delivered with the relevant asset Information "mg = multiplex_group" is described. When the location information in the case of (A) multicast distribution is inserted in "MMT_general_location_info ()", the available managed network information "ANmap" is also described.

Here, corresponding to the first "MMT_general_location_info ()", "type" is defined as (A) multicast distribution, "ANmap" is defined as "ANmap1", and the available managed network Is shown. Further, "mg" is defined to indicate that the asset is multiplexed and distributed with other assets constituting the group 1. As a result, on the receiving side, as shown in FIG. 17 (b), in the case of (A) multicast distribution, it can be seen that "Asset 4" is multiplexed and distributed with the above-mentioned "Asset 3". On the receiving side, both "Asset 3" and "Asset 4" can be obtained from this multiplexed stream.

In addition, corresponding to the second "MMT_general_location_info ()", "type" is defined as (D) MMTP / HTTP distribution, and "mg" is multiplexed with other assets constituting group 2. It is supposed to indicate that it is delivered. As a result, on the receiving side, as shown in FIG. 17 (b), in the case of (D) MMTP / HTTP distribution, it can be seen that "Asset 4" is multiplexed and distributed with the above-mentioned "Asset 3". On the receiving side, both "Asset 3" and "Asset 4" can be obtained from this multiplexed stream.

Further, corresponding to the third "MMT_general_location_info ()", "type" is defined as (E) MPU / HTTP distribution, "mg" is set to "0", and is not multiplexed. It is supposed to show that. As a result, on the receiving side, as shown in FIG. 17 (b), in the case of (E) MPU / HTTP distribution, it can be seen that "Asset 4" is distributed independently.

"Method 3"
In the case of the method 3, one information of a specific component (asset) is arranged in the MP table (MPT), and the acquired information for acquiring the information of a plurality of distribution ptrocols is inserted into the arranged one information. Will be done. In this case, only one "MMT_general_location_info ()" is described for each asset (see FIG. 12).

This method 3 will be further described. Here, as in the above description of "method 1" and "method 2", there are two video and audio signal sets, one is the main signal and is transmitted by broadcasting, and the other is not the main signal and is transmitted by communication. The use case of being transmitted will be described. Further, in this use case, it is assumed that distribution can be performed by three protocols: (A) multicast distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution.

FIG. 19A schematically shows a description example of the MP table (MPT). The assets (components) of "Asset1" indicate the video signal (Video1) to be broadcast and transmitted. The asset (component) of "Asset2" indicates an audio signal (Audio1) to be broadcast and transmitted.

The assets (components) of "Asset3" indicate the video signal (Video2) that is transmitted by communication. One "MMT_general_location_info ()" is described in the "asset_location" field of this asset. For example, a URL is inserted into this "MMT_general_location_info ()" as acquisition information for acquiring information on a plurality of distribution protocols related to this "Asset3". On the receiving side, referring to this URL, a BD table (BDT: Broadband Delivery Table) as a metafile containing information on a plurality of distribution protocols is acquired via a communication network (see FIG. 19B).

This BD table contains BD information (BDI: Broadband Delivery), which is information on distribution protocols corresponding to each of the three protocols of (A) multicast distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution. Information) is included. The content of the BD information corresponding to each protocol is substantially the same as the content of the information inserted in the "MMT_general_location_info ()" and the communication distribution descriptor (broadband_delivery_descriptor) of the "Asset 3" in the above-mentioned "method 2". Is.

In addition, for example, the communication delivery descriptor (broadband_delivery_descriptor) (see FIG. 15) in the above-mentioned "method 1" is inserted in the "asset_descriptors" field of this asset, and "type = broadband_delivery_type" is set to "7". It is shown that information for multiple delivery protocols is specified in the BD table.

FIG. 20 shows a structural example (Syntax) of the BD table and the contents (Semantics) of each information. This BD table is written in XML format. The information of "@version" is the version number of this table. "BDI" is a BD information item that is a communication distribution option, and appears in a predetermined number. Here, since it is assumed that distribution can be performed by three protocols of (A) multicast distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution, three appear. It should be noted that this description order indicates the priority.

"BDI" includes "@delivery_type" and "@multiplex_group". “@Delivery_type” is a communication protocol type and corresponds to “broadband_delivery_type” in the communication delivery descriptor of FIG. “@Multix_group” is a group ID of the multiplexing stream, and corresponds to “multiplex_group” in the communication distribution descriptor of FIG. If it is not multiplexed, this description does not appear, or a group ID indicating that it is not multiplexed is described.

In addition, "BDI" includes "MC_info" and "location_url". Both "MC_info" and "location_url" are location information items. For example, in the above-mentioned "method 1" and "method 2", it is an item of information inserted in "MMT_general_location_info ()". "MC_info" is multicast information, "location_url" is unicast location information, and one of them appears. "MC_info" appears when multicast delivery is described as the communication protocol type in "@delivery_type", and "location_url" appears in other cases.

"MC_info" includes "@sourceIPAddress", "@destinationIPAddress", "@portNumber", "@pid", and "ManagedNetworkName". "@SourceIPAddress" is the source IP address of the multicast. "@DestinationIPAddress" is a multicast destination IP address. "@PortNumber" is a multicast port number. "@Pid" is the PID of the multicast MMT packet. "Managed Network Name" is the name of the managed network delivered by the multicast address. "Location_url" includes "@url". "@Url" is the distribution URL.

Returning to FIG. 19, the asset (component) of "Asset4" shows an audio signal (Audio2) to be communicated and transmitted. One "MMT_general_location_info ()" is described in the "asset_location" field of this asset. For example, a URL is inserted into this "MMT_general_location_info ()" as acquisition information for acquiring information on a plurality of distribution protocols related to this "Asset4". On the receiving side, referring to this URL, a BD table (BDT: Broadband Delivery Table) as a metafile containing information on a plurality of distribution protocols is acquired via a communication network (see FIG. 19B).

This BD table contains BD information (BDI: Broadband Delivery), which is information on distribution protocols corresponding to each of the three protocols of (A) multicast distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution. Information) is included. The content of the BD information corresponding to each protocol is substantially the same as the content of the information inserted in the "MMT_general_location_info ()" and the communication distribution descriptor (broadband_delivery_descriptor) of the "Asset 4" in the above-mentioned "method 2", for example. Is.

In the "asset_descriptors" field of this asset, for example, the communication delivery descriptor (broadband_delivery_descriptor) (see FIG. 15) in the above "method 1" is inserted, and "type = broadband_delivery_type" is set to "7". It is shown that information for multiple delivery protocols is specified in the BD table.

Also in this method 3, the description of "@multiplex_group" in the BD table makes it possible for the receiving side to easily recognize the multiplexing relationship between "Asset 3" and "Asset 4" as shown in FIG. 19 (c). That is, in the case of (E) MPU / HTTP distribution, it can be seen that each of "Asset3" and "Asset4" is distributed independently. Further, in the case of (A) multicast distribution, it can be seen that "Asset 3" and "Asset 4" are multiplexed and distributed. Further, in the case of (D) MMTP / HTTP distribution, it can be seen that "Asset 3" and "Asset 4" are multiplexed and distributed.

[Acquisition process of communication path component (asset) in receiving terminal]
Next, the acquisition process of the specific component (asset) of the communication path in the receiving terminal 200 will be described. The receiving terminal 200 selects one receivable distribution protocol from a plurality of distribution protocol information described in the MP table (MPT) acquired from the broadcast signal, and receives a specific component by this distribution protocol.

The flowchart of FIG. 21 shows an example of view selection / reception processing in the receiving terminal 200. The receiving terminal 200 starts the view selection / receiving process in step ST1. After that, when the viewer selects a specific view in step ST2, the receiving terminal 200 moves to the process of step ST3.

In step ST3, the receiving terminal 200 determines whether the component corresponding to the selected view should be acquired by the communication path or the broadcast path. If it is acquired by the broadcast path, the receiving terminal 200 acquires the component from the broadcast signal. On the other hand, if it is acquired by the communication path, the receiving terminal 200 moves to the process of step ST4.

In step ST4, the receiving terminal 200 determines whether or not multicast distribution (multicast option) can be selected. The receiving terminal 200 makes this determination based on the information of the plurality of distribution protocols described in the MP table (MPT). When the selection of multicast distribution is possible, the receiving terminal 200 determines in step ST5 whether or not it is connected to the corresponding managed network. When connected to the managed network, the receiving terminal 200 selects multicast distribution as the distribution protocol and proceeds to the process of step ST9.

When the multicast option is not available in step ST4, or when the user is not connected to the managed network in step ST5, the receiving terminal 200 moves to the process of step ST6. In step ST6, the receiving terminal 200 determines whether or not it is possible to select a distribution protocol (other option) other than multicast distribution. The receiving terminal 200 makes this determination based on the information of the plurality of distribution protocols described in the MP table (MPT).

When the other distribution protocol can be selected, the receiving terminal 200 determines in step ST7 whether or not the other distribution protocol can be supported. When it is possible, the receiving terminal 200 selects the other distribution protocol as the distribution protocol, and proceeds to the process of step ST9. In this case, the receiving terminal 200 selects the distribution protocol having the highest priority when there are a plurality of distribution protocols that it can handle.

When it is not possible to select another distribution protocol in step ST6, or when it is not possible to support the other distribution protocol in step ST7, the receiving terminal 200 terminates with an error in step ST8.

In step ST9, the receiving terminal 200 determines whether or not the stream received by the multicast distribution or another distribution protocol is a multiplexed stream including components other than the corresponding component. When it is a multiplexed stream, the stream is received from the acquisition destination in step ST10, and the process ends in step ST11.

When it is not a multiplexed stream, the receiving terminal 200 receives the stream from the acquisition destination in step ST12, and then proceeds to the process of step ST13. In this step ST13, the receiving terminal 200 determines whether or not the reception of the view component has been completed. When not completed, the receiving terminal 200 returns to the process of step ST4 and repeats the same process as described above. On the other hand, when completed, the receiving terminal 200 ends the process in step ST14.

The above-mentioned view selection / reception process assumes that the multiplexed stream includes all view component components. For example, the view configuration component may consist of video and audio components.

[Reception sequence]
Next, the reception sequence in the reception terminal 200 will be described. First, with reference to FIG. 22, the case of receiving the asset delivered by the protocol of (A) multicast delivery will be described. In the case of multicast distribution, there is a multicast server (MC server).

The receiving terminal 200 receives the broadcast signal and acquires the MP table (MPT). The receiving terminal 200 obtains the location information of the asset distributed by the multicast distribution protocol from this MP table. The location information in this case is a source address, a destination address, a destination port number, and a packet identifier. In this case, the receiving terminal 200 can identify the multicast distribution from the location type.

In this case, the receiving terminal 200 transmits a join message (JOIN message) to which the multicast address and the port number included in the location information are added to the edge router. Along with the transmission of this join message, the multicast IP stream from the multicast server is sent to the receiving terminal 200 via the edge filter.

In the receiving terminal 200, the target asset (component) can be obtained by filtering the multicast IP stream by the packet identifier (Packet_id) included in the location information. Upon exiting this reception state, the receiving terminal 200 transmits a LEAVE message with a multicast address and a port number added to the edge router.

Next, with reference to FIG. 23, the case of receiving the asset delivered by the (B) MMTP / UDP delivery protocol will be described. For this MMTP / UDP distribution, the RTSP (Real Time Streaming Protocol) protocol is used. In the case of this MMTP / UDP distribution, there are an RTSP server and an MMTP / UDP server. These servers either exist as separate devices or as the same device. In the illustrated example, the case where they exist as the same device is shown.

The receiving terminal 200 receives the broadcast signal and acquires the MP table (MPT). The receiving terminal 200 obtains the location information of the asset distributed by the MMTP / UDP distribution protocol from this MP table. The location information in this case is a URL, "rtsp: // ~ .mmt" is specified as the schema, and a parameter for specifying UDP and a parameter for specifying the packet identifier are added by the query field. In this case, the receiving terminal 200 can identify the MMTP / UDP distribution by "rtsp" and "pr = udp".

The receiving terminal 200 sends a "SETUP" RTSP request. At this time, the receiving terminal 200 inserts the location information into the header of the RTSP. In this case, as the location information, all of the location information acquired from the MP table is inserted, or the parameter for specifying the packet identifier is excluded and inserted. This RTSP request is sent to the target server, and an "OK" response is sent from the server.

After that, the receiving terminal 200 sends a "PLAY" RTSP request. In response to this, an "OK" response is sent from the target server. At the same time, the transmission stream is sent from the MMTP / UDP server to the receiving terminal 200. In the receiving terminal 200, the target asset (component) can be obtained by filtering from this stream by the packet identifier (Packet_id) included in the location information. Upon exiting this reception state, the receiving terminal 200 sends an RTSP request of "TEARDOWN". In response, the server sends an "OK" response.

Next, with reference to FIG. 24, a case where (C) an asset delivered by the MMTP / TCP delivery protocol is received will be described. The RTSP (Real Time Streaming Protocol) protocol is also used for this MMTP / TCP distribution. In the case of this MMTP / TCP distribution, there are an RTSP server and an MMTP / TCP server. These servers either exist as separate devices or as the same device. In the illustrated example, the case where they exist as the same device is shown.

The receiving terminal 200 receives the broadcast signal and acquires the MP table (MPT). The receiving terminal 200 obtains the location information of the asset distributed by the MMTP / TCP distribution protocol from this MP table. The location information in this case is a URL, "rtsp: // ~ .mmt" is specified as the schema, and a parameter for specifying TCP and a parameter for specifying a packet identifier are added by the query field. In this case, the receiving terminal 200 can identify the MMTP / TCP distribution by "rtsp" and "pr = tcp".

The receiving terminal 200 sends a "SETUP" RTSP request. At this time, the receiving terminal 200 inserts the location information into the header of the RTSP. In this case, as the location information, all of the location information acquired from the MP table is inserted, or the parameter for specifying the packet identifier is excluded and inserted. This RTSP request is sent to the target server, and an "OK" response is sent from the server.

After that, the receiving terminal 200 sends a "PLAY" RTSP request. In response to this, an "OK" response is sent from the target server. At the same time, the transmission stream is sent from the MMTP / TCP server to the receiving terminal 200. In the receiving terminal 200, the target asset (component) can be obtained by filtering from this stream by the packet identifier (Packet_id) included in the location information. Upon exiting this reception state, the receiving terminal 200 sends an RTSP request of "TEARDOWN". In response, the server sends an "OK" response.

Next, with reference to FIG. 25, the case of receiving the asset delivered by the protocol of (D) MMTP / HTTP delivery will be described. In the case of this MMTP / HTTP distribution, the HTTP (Hyper Text Transfer Protocol) protocol is used. In the case of this MMTP / HTTP delivery, there is an HTTP server.

The receiving terminal 200 receives the broadcast signal and acquires the MP table (MPT). The receiving terminal 200 obtains the location information of the assets distributed by the MMTP / HTTP distribution protocol from this MP table. The location information in this case is a URL, "http: // ~ .mmt" is specified as the schema, and a parameter for specifying the packet identifier (packet_id) is added by the query field. The receiving terminal 200 can identify that it is MMTP / HTTP delivery by "http" and "mmt".

The receiving terminal 200 sends an HTTP request to the HTTP server. At this time, the receiving terminal 200 inserts the location information into the header of the HTTP. In this case, "http: // ~ .mmt" included in the location information acquired from the MP table is inserted as the location information, and the parameter "pid = a" that specifies the packet identifier is added by the query field. , The parameter "msn = *" that specifies the MPU sequence number is added. The parameter "msn = *" is specified as "Please send the MPU with the MPU sequence number at that timing".

This HTTP request is sent to the target HTTP server, and the HTTP server sends an MMTP stream including an MPU having an MPU sequence number (= 10) at the timing of sending the HTTP request to the receiving terminal 200 as an HTTP response. Come on. The receiving terminal 200 takes a target asset (component) from this MMTP stream by filtering by the packet identifier (Packet_id) included in the location information.

The receiving terminal 200 sends an HTTP request requesting the MPU of the next MPU sequence number (= 11) to the HTTP server after the reception of the MMTP stream is completed or before the reception is completed. Then, the HTTP server sends an MMTP stream containing the MPU having the next MPU sequence number (= 11) to the receiving terminal 200 as an HTTP response. The receiving terminal 200 can take a target asset (component) from this MMTP stream by filtering by the packet identifier (Packet_id) included in the location information.

Hereinafter, in the same manner, the receiving terminal 200 sends an HTTP request requesting the MPU of the next MPU sequence number to the HTTP server, and sends an MMTP stream including the MPU of the next MPU sequence number as an HTTP response from the HTTP server. Receive and take the desired asset (component) from the MMTP stream.

At the time of HTTP request, the parameter "pid = a" included in the HTTP header specifies the type of assets such as video and audio. Video and audio may be multiplexed on the MMTP stream. In that case, the MPU sequence number has the MPU sequence number of the video for the video and the MPU sequence number of the audio for the audio. Even if the MPU sequence number is specified, it is not possible to know which asset (component) MPU sequence number is without the parameter "pid = a".

FIG. 26 shows the cutting process in the multiplexed stream of MMTP / HTTP. The HTTP server that receives the HTTP request requesting the MPU with the parameter “pid = a” indicating the video and the MPU sequence number n switches from the multiplexed stream from n-1 to n of the MPU sequence number of the video. To the switching from n to n + 1 is cut out and sent to the receiving terminal 200.

In this case, you may want to take audio from the same multiplexed stream. In this case, the receiving terminal 200 can recognize from the location information that the audio is multiplexed with the video. The receiving terminal 200 performs a process of extracting the target audio from the MMTP stream cut out by the MPU sequence number of the video by filtering by the packet identifier (Packet_id) included in the location information.

Next, with reference to FIG. 27, the case of receiving the asset delivered by the (E) MPU / HTTP delivery protocol will be described. In the case of this MPU / HTTP distribution, the HTTP (Hyper Text Transfer Protocol) protocol is used. In the case of this MPU / HTTP delivery, there is an HTTP server.

The receiving terminal 200 receives the broadcast signal and acquires the MP table (MPT). The receiving terminal 200 obtains the location information of the assets distributed by the MPU / HTTP distribution protocol from this MP table. The location information in this case is a URL, and "http: // ~ .mp4" is specified as the schema. The receiving terminal 200 can identify that it is MPU / HTTP distribution by "http" and "mp4".

The receiving terminal 200 sends an HTTP request to the HTTP server. At this time, the receiving terminal 200 inserts the location information into the header of the HTTP. In this case, "http: // ~ .mp4" included in the location information acquired from the MP table is inserted as the location information, and the parameter "msn = *" that specifies the MPU sequence number by the query field. Is added. The parameter "msn = *" is specified as "Please send the MPU at that timing".

This HTTP request is sent to the target HTTP server, and the HTTP server sends an MPU having an MPU sequence number (= 10) at the timing of sending the HTTP request to the receiving terminal 200 as an HTTP response.

The receiving terminal 200 sends an HTTP request requesting the MPU of the next MPU sequence number (= 11) to the HTTP server after the reception of the MPU is completed or before the reception is completed. Then, the MPU having the next MPU sequence number (= 11) is sent from the HTTP server to the receiving terminal 200 as an HTTP response.

Hereinafter, in the same manner, the receiving terminal 200 sends an HTTP request requesting the MPU of the next MPU sequence number to the HTTP server, and receives the MPU of the next MPU sequence number as the HTTP response from the HTTP server.

[Broadcast transmission system configuration]
FIG. 28 shows a configuration example of the broadcast transmission system 100. The broadcast transmission system 100 includes a signal transmission unit 101, a video encoder 102, an audio encoder 103, and a signaling generation unit 104. Further, the broadcast transmission system 100 includes a TLV signaling generation unit 105, N IP service multiplexers 106-1 to 106-N, a TLV multiplexer 107, and a modulation / transmission unit 108.

The signal transmission unit 101 is, for example, a studio of a TV station or a recording / playback device such as a VTR, and transmits video and audio stream data to each encoder. The video encoder 102 encodes the video data transmitted from the signal transmission unit 101, further packetizes it, and sends an IP packet including an MMT packet of the video to the IP service multiplexer 106-1. The audio encoder 103 encodes the audio data transmitted from the signal transmission unit 101, further packets it, and sends an IP packet including an audio MMT packet to the IP service multiplexer 106-1.

The signaling generator 104 generates a signaling message and sends an IP packet including an MMT packet in which the signaling message is arranged in the payload section to the IP service multiplexer 106-1. In this case, the signaling generator 104 arranges an MP table (MPT) in the PA message (see FIGS. 12 to 13). As described above, this MP table contains information on all assets (components) transmitted by broadcasting and communication. This information also includes location information for each asset.

The IP service multiplexer 106-1 performs time division multiplexing of IP packets sent from each encoder. At this time, the IP service multiplexer 106-1 adds a TLV header to each IP packet to obtain a TLV packet. The IP service multiplexer 106-1 constitutes one channel portion contained in one transponder. The IP service multiplexers 106-2 to 106-N have the same functions as the IP service multiplexers 106-1, and constitute another channel portion to be put in one transponder.

The TLV signaling generation unit 105 generates signaling information and generates a TLV packet that arranges the signaling information in the payload unit. The TLV multiplexer 107 multiplexes the TLV packets generated by the IP service multiplexers 106-1 to 106-N and the TLV signaling generator 105 to generate a broadcast stream. The modulation / transmission unit 108 performs RF modulation processing on the broadcast stream generated by the TLV / multiplexer 107 and sends it to the RF transmission line.

The operation of the broadcast transmission system 100 shown in FIG. 28 will be briefly described. The video data transmitted from the signal transmission unit 101 is supplied to the video encoder 102. In the video encoder 102, the video data is encoded and further packetized to generate an IP packet including a video MMT packet. This IP packet is sent to the IP service multiplexer 106-1. Further, the same processing is performed on the audio data transmitted from the signal transmission unit 101. Then, an IP packet including an audio MMT packet generated by the audio encoder 103 is sent to the IP service multiplexer 106-1.

Further, the signaling generation unit 104 generates a signaling message, and an IP packet including an MMT packet in which the signaling message is arranged in the payload unit is generated. This IP packet is sent to the IP service multiplexer 106-1. At this time, the MP table (MPT) is arranged in the PA message.

In the IP service multiplexer 106-1, time division multiplexing of IP packets sent from each encoder and the signaling generator 104 is performed. At this time, a TLV header is added to each IP packet to obtain a TLV packet. The IP service multiplexer 106-1 processes one channel portion to be put in one transponder, and the IP service multiplexers 106-2 to 106-N put the other transponder in one transponder. The processing of the channel portion is performed in the same manner.

The TLV packets obtained by the IP service multiplexers 106-1 to 106-N are sent to the TLV multiplexer 107. Further, a TLV packet for arranging signaling information in the payload unit is also sent from the TLV signaling generation unit 105 to the TLV multiplexer 107.

In the TLV multiplexer 107, the TLV packets generated by the IP service multiplexers 106-1 to 106-N and the TLV signaling generator 105 are multiplexed to generate a broadcast stream. This broadcast stream is sent to the modulation / transmission unit 108. The modulation / transmission unit 108 performs RF modulation processing on this broadcast stream, and sends the RF modulation signal as a broadcast signal to the RF transmission line.

[Receiver terminal configuration]
FIG. 29 shows a configuration example of the receiving terminal 200. The receiving terminal 200 has a CPU 201, a tuner / demodulation unit 202, a network interface unit 203, and a demultiplexer 204. Further, the receiving terminal 200 has a video decoder 205 and an audio decoder 206.

The CPU 201 constitutes a control unit and controls the operation of each unit of the receiving terminal 200. The tuner / demodulation unit 202 receives the RF modulated signal and performs demodulation processing to obtain a broadcast stream. The network interface unit 203 receives the transmission stream of the service distributed from the distribution server 300 via the communication network 400.

The demultiplexer 204 performs demultiplexing and depackaging processing on the broadcast stream obtained by the tuner / demodulation unit 202 and the transmission stream obtained by the network interface unit 203 to encode signaling information, video, and audio. Output data etc.

The video decoder 205 decodes the encoded video data obtained by the demultiplexer 204 to obtain baseband video data. The audio decoder 206 decodes the encoded audio data obtained by the demultiplexer 204 to obtain baseband audio data.

The operation of the receiving terminal 200 shown in FIG. 29 will be briefly described. The tuner / demodulation unit 202 receives the RF modulation signal transmitted through the RF transmission line, performs demodulation processing, and obtains a broadcast stream. This broadcast stream is sent to the demultiplexer 204. Further, the network interface unit 203 receives the transmission stream of the service distributed from the distribution server 300 via the communication network 400 and sends it to the demultiplexer 204.

In the demultiplexer 204, demultiplexing processing and depackaging processing are performed on the broadcast stream from the tuner / demodulation unit 202 and the transmission stream from the network interface unit 203, and signaling information, video, audio encoded data, etc. are performed. Is extracted.

Various signaling information extracted by the demultiplexer 204 is sent to the CPU 201 via the CPU bus 207. This signaling information includes TLV-SI and MMT-SI. As described above, the TLV-SI is a transmission control signal (TLV-NIT / AMT) placed on the TLV transmission packet, and the MMT-SI is a signaling message as signaling information included in the payload portion of the MMT packet. (See FIG. 2). The CPU 201 controls the operation of each part of the receiving terminal 200 based on this signaling information.

The encoded video data extracted by the demultiplexer 204 is sent to the video decoder 205 for decoding, and the baseband video data is obtained. Further, the encoded audio data extracted by the demultiplexer 204 is sent to the audio decoder 206 for decoding, and the baseband audio data for audio output is obtained.

As described above, in the broadcasting / communication hybrid system 10 shown in FIG. 1, regarding the assets (components) of the communication path, the MP table contains at least location information and protocol identification information, respectively, of information on a plurality of distribution protocols, or information of a plurality of distribution protocols. The acquisition information for acquiring the information of the plurality of distribution protocols is inserted. Therefore, on the receiving side, the component can be satisfactorily received by the distribution protocol according to its own distribution network environment.

<2. Modification example>
In the above-described embodiment, an example in which the transmission packet is an MMT packet is shown. The present technology is not limited to this, and it goes without saying that the present technology can be applied to the case of handling other similar transmission packets.

In addition, the present technology can also have the following configurations.
(1) A transmission stream generator that generates a transmission stream in which a first transmission packet containing a predetermined component and a second transmission packet containing information about the predetermined component are multiplexed in a time-division manner.
A transmitter that transmits the transmission stream through a predetermined transmission line, and
In the second transmission packet, information on a plurality of distribution protocols including at least location information and protocol identification information for acquiring the specific component in relation to the specific component to be acquired in the communication path, or the information thereof. A transmission device including an information insertion unit that inserts acquisition information for acquiring information of a plurality of distribution protocols.
(2) The plurality of distribution protocols are two or more distribution protocols selected from the multicast distribution, MMTP / UDP distribution, MMTP / TCP distribution, MMTP / HTTP distribution, and MPU / HTTP distribution protocols in the above (1). The transmitter described.
(3) The transmission device according to (2) above, wherein when the Putcol identification information indicates that it is the MMTP / UDP distribution, the information of the distribution protocol includes a parameter for specifying UDP in addition to the URL.
(4) The transmission device according to (2) above, wherein when the Putcol identification information indicates that it is the MMTP / TCP distribution, the information of the distribution protocol includes a parameter for specifying TCP in addition to the URL.
(5) The transmitting device according to any one of (1) to (4) above, wherein the information of the distribution protocol further includes packet identification information.
(6) The transmission device according to any one of (1) to (5) above, wherein the transmission packet is an MMT packet.
(7) The transmission device according to any one of (1) to (6) above, wherein the predetermined transmission line is a broadcast transmission line.
(8) A plurality of information of the specific component is arranged in the second packet, and one of the plurality of distribution protocols is inserted into each of the arranged plurality of information (1). To the transmitter according to any one of (7).
(9) In the second packet, one piece of information on the specific component is arranged, and information on the plurality of distribution protocols is inserted into the arranged one piece of information according to the above (1) to (7). The transmitter according to any.
(10) In the second packet, one piece of information of the specific component is arranged, and the acquired information for acquiring the information of the plurality of distribution protocols is inserted into the arranged one piece of information. The transmitter according to any one of (1) to (7).
(11) The transmission according to any one of (1) to (10) above, wherein information of another component that is multiplexed and distributed with the specific component is added to each of the information of the plurality of distribution protocols. apparatus.
(12) The transmission device according to any one of (1) to (11) above, wherein managed network information is added to the information of the multicast distribution protocol among the information of the plurality of distribution protocols.
(13) A transmission stream generation step of generating a transmission stream in which a first transmission packet containing a predetermined component and a second transmission packet containing information about the predetermined component are multiplexed in a time-division manner.
A transmission step of transmitting the transmission stream through a predetermined transmission path by the transmission unit, and
In the second transmission packet, information on a plurality of distribution protocols including at least location information and protocol identification information for acquiring the specific component in relation to the specific component to be acquired in the communication path, or the information thereof. A transmission method having an information insertion step that inserts acquisition information for acquiring information for multiple delivery protocols.
(14) The receiver includes a receiver that receives a transmission stream in which a first transmission packet containing a predetermined component and a second transmission packet containing information about the predetermined component are time-division-multiplexed through a predetermined transmission line.
The second transmission packet includes information on a plurality of delivery protocols including at least location information and protocol identification information for acquiring the specific component in relation to the specific component to be acquired in the communication path, or information on a plurality of distribution protocols. The acquisition information for acquiring the information of the plurality of distribution protocols is inserted, and the acquisition information is inserted.
It further includes a communication unit that selects one receivable delivery protocol from the plurality of delivery protocol information and receives a transmission stream having a third transmission packet including the specific component in the selected delivery protocol through the network. Receiver.
(15) The information of the distribution protocol further includes packet identification information.
The receiving device according to (14), wherein the communication unit extracts the third transmission packet from the transmitted stream having the received third packet based on the packet identification information.
(16) The receiving device according to (14) or (15) above, wherein the transmission packet is an MMT packet.
(17) The receiving device according to any one of (14) to (16) above, wherein the predetermined transmission line is a broadcast transmission line.
(18) Reception in which the receiving unit receives a transmission stream in which a first transmission packet containing a predetermined component and a second transmission packet containing information about the predetermined component are multiplexed in a time-division manner through a predetermined transmission line. Have steps
The second transmission packet includes information on a plurality of delivery protocols including at least location information and protocol identification information for acquiring the specific component in relation to the specific component to be acquired in the communication path, or information on a plurality of distribution protocols. The acquisition information for acquiring the information of the plurality of distribution protocols is inserted, and the acquisition information is inserted.
It further has a communication step of selecting one receivable delivery protocol from the plurality of delivery protocol information and receiving a transmission stream having a third transmission packet including the specific component in the selected delivery protocol through the network. Receiving method.
(19) A receiving unit for receiving a transmission stream in which a first transmission packet containing a predetermined component and a second transmission packet containing information about the predetermined component are time-division-multiplexed through a predetermined transmission line is provided.
The second transmission packet includes information on a plurality of delivery protocols including at least location information and protocol identification information for acquiring the specific component in relation to the specific component to be acquired in the communication path, or information on a plurality of distribution protocols. The acquisition information for acquiring the information of the plurality of distribution protocols is inserted, and the acquisition information is inserted.
A receiving device further including a processing unit that processes a transmission stream received by the receiving unit.

10 ... Broadcast / communication hybrid system 100 ... Broadcast transmission system 101 ... Signal transmission unit 102 ... Video encoder 103 ... Audio encoder 104 ... Signaling generator 105 ... TLV signaling generator 106-1 to 106-N ... IP service multiplexer 107 ... TLV multiplexer 108 ... Modulation / transmitter 200 ... Receiver terminal 201 ... CPU
202 ・ ・ ・ Tuner / Demodulation unit 203 ・ ・ ・ Network interface unit 204 ・ ・ ・ Demultiplexer 205 ・ ・ ・ Video decoder 206 ・ ・ ・ Audio decoder 207 ・ ・ ・ CPU bus 300 ・ ・ ・ Distribution server 400 ・ ・ ・ Communication network

Claims (2)

A first transmission packet and the transmission stream generator for generating a transmission stream the second transmission packets are multiplexed containing information about the said predetermined components including a predetermined component,
A transmission unit for transmitting over Kiden feed stream through a predetermined transmission path,
In the second transmission packet, an information insertion unit that inserts distribution protocol information including protocol identification information and location information for acquiring the specific component in relation to the specific component to be acquired in the communication path is provided. Prepare,
The first transmission packet and the second transmission packet are MMT packets, and are
The predetermined transmission line is a transmission device that is a broadcast transmission line . A transmission stream generation step that generates a transmission stream in which a first transmission packet containing a predetermined component and a second transmission packet containing information about the predetermined component are multiplexed.
The transmitting unit, and a transmission step of transmitting over Kiden feed stream through a predetermined transmission path,
In the second transmission packet, an information insertion step of inserting the distribution protocol information including the protocol identification information and the location information for acquiring the specific component in relation to the specific component to be acquired in the communication path is performed. Have and
The first transmission packet and the second transmission packet are MMT packets, and are
The predetermined transmission line is a transmission method that is a broadcast transmission line .

Images