Transmission device, transmission method, reception device, and reception method

Abstract

To make it possible to satisfactorily realize a broadcast / communication hybrid service.SOLUTION: Generated is a delivery stream obtained by time-division multiplexing of a first delivery packet including a prescribed component and a second delivery packet including information pertaining to the prescribed component. The delivery stream is transmitted through a prescribed delivery path. Inserted into the second delivery packet, in relation to a specific component to be acquired in a communication pathway, is: a plurality of items of distribution protocol information for acquiring the specific component, each of the items including at least location information and protocol identification information; or acquisition information for acquiring the plurality of items of distribution protocol information. On the reception side, the specific component can be satisfactorily received in the distribution protocol corresponding to the reception-side distribution network environment.SELECTED DRAWING: Figure 14

Description

[Technical field]

[0001] The present technology relates to a transmitting device, a transmitting method, a receiving device, and a receiving method. [Background technology]

[0002] In current broadcasting systems, the MPEG-2 TS (Moving Picture Experts Group-2 Transport Stream) method and the RTP (Real Time Protocol) method are widely used as media transport methods (see, for example, Patent Document 1). The MMT (MPEG Media Transport) method (see, for example, Non-Patent Document 1) is being considered as a next-generation digital broadcasting method. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2013-153291 A [Non-patent literature]

[0004] [Non-Patent Document 1] ISO / IEC DIS 23008-1:2013(E) Information technology-High efficiency coding and media delivery in heterogeneous environments-Part1:MPEG media transport(MMT) Summary of the Invention [Problem to be solved by the invention]

[0005] The purpose of this technology is to make it possible to effectively realize hybrid broadcasting and communication services. [Means for solving the problem]

[0006] The concept of this technology is as follows: a transmission stream generating unit that generates a transmission stream by time-division multiplexing a first transmission packet including a predetermined component and a second transmission packet including information related to the predetermined component; a transmitting unit that transmits the transmission stream through a predetermined transmission path; and an information insertion unit that inserts, into the second transmission packet, information on a plurality of delivery protocols, each of which includes at least location information and protocol identification information for acquiring the specific component, in association with the specific component to be acquired through the communication path, or acquisition information for acquiring the information on the plurality of delivery protocols. Located in the transmitting device.

[0007] In the present technology, a transmission stream is generated by time-division multiplexing a first transmission packet including a predetermined component and a second transmission packet including information about the predetermined component. For example, the transmission packets may be MMT (MPEG Media Transport) packets. The transmission stream is transmitted to a receiving side by a transmitting unit through a predetermined transmission path. For example, the predetermined transmission path may be a broadcast transmission path.

[0008] The information inserting unit inserts, into the second transmission packet, information on a plurality of delivery protocols, each of which includes at least location information and protocol identification information for acquiring a specific component to be acquired on a communication path, or acquisition information for acquiring the information on the plurality of delivery protocols. For example, the plurality of delivery protocols may be two or more delivery protocols selected from the protocols of multicast delivery, MMTP / UDP delivery, MMTP / TCP delivery, MMTP / HTTP delivery, and MPU / HTTP delivery.

[0009] In this case, for example, when the protocol identification information indicates MMTP / UDP delivery, the delivery protocol information may include a parameter specifying UDP in addition to the URL. Also, in this case, for example, when the protocol identification information indicates MMTP / TCP delivery, the delivery protocol information may include a parameter specifying TCP in addition to the URL.

[0010] For example, a plurality of pieces of information on a specific component may be arranged in the second packet, and one piece of information among a plurality of delivery protocols may be inserted into each of the arranged pieces of information. Also, for example, one piece of information on a specific component may be arranged in the second packet, and information on a plurality of delivery protocols may be inserted into this arranged piece of information. Also, for example, one piece of information on a specific component may be arranged in the second packet, and acquisition information for acquiring information on a plurality of delivery protocols may be inserted into this arranged piece of information.

[0011] In this way, in the present technology, information on a plurality of delivery protocols, each of which includes at least location information and protocol identification information, for acquiring a specific component of a communication path, or acquisition information for acquiring the information on the plurality of delivery protocols is inserted into the second transmission packet, so that the receiving side can receive the specific component satisfactorily using a delivery protocol that corresponds to its own delivery network environment.

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

[0013] In addition, in the present technology, for example, information on other components that are multiplexed with a specific component and distributed may be added to each of the information on a plurality of distribution protocols. In this case, the receiving side can easily recognize which components are multiplexed with the specific component in the distributed transmission stream, or whether the distributed transmission stream contains only the specific component.

[0014] In addition, in the present technology, for example, managed network information may be added to the multicast delivery protocol information among the multiple delivery protocol information, so that the receiving side can easily determine whether or not it is possible to connect to the managed network for receiving the multicast delivery.

[0015] Another concept of the present technology is a receiving unit that receives a transmission stream obtained by time-division multiplexing a first transmission packet including a predetermined component and a second transmission packet including information related to the predetermined component through a predetermined transmission path; The second transmission packet is inserted with information on a plurality of delivery protocols, each of which includes at least location information and protocol identification information, for acquiring a specific component to be acquired through a communication path, or acquisition information for acquiring the information on the plurality of delivery protocols; a communication unit that selects one receivable delivery protocol from the plurality of pieces of delivery protocol information, and receives a transmission stream having a third transmission packet including the specific component in the selected delivery protocol through a network. in the receiving device.

[0016] In the present technology, a transmission stream in which a first transmission packet including a predetermined component and a second transmission packet including information on the predetermined component are multiplexed in a time division manner is received by a receiving unit through a predetermined transmission path. For example, the transmission packet may be an MMT packet. Also, for example, the predetermined transmission path may be a broadcast transmission path.

[0017] In the second transmission packet, information of a plurality of delivery protocols for acquiring a specific component to be acquired on a communication path or acquisition information for acquiring the information of the plurality of delivery protocols is inserted in association with the specific component to be acquired on the communication path, each of the information of the plurality of delivery protocols including at least location information and protocol identification information.

[0018] The communication unit selects one receivable delivery protocol from the plurality of pieces of delivery protocol information, and receives a transmission stream having a third transmission packet including a specific component in the selected delivery protocol through a network.

[0019] In this way, in the present technology, one receivable delivery protocol is selected from the information of multiple delivery protocols in relation to the specific component provided in the second transmission packet, and the specific component is delivered. Therefore, the specific component can be received satisfactorily using a delivery protocol that suits the delivery network environment of the user.

[0020] In the present technology, for example, the information of the delivery protocol may further include packet identification information, and the communication unit may extract the third transmission packet from the received transmission stream having the third packet based on the packet identification information. In this case, even if the transmission packets of multiple components are multiplexed in the transmission stream, the third transmission packet can be reliably obtained based on the packet identification information.

[0021] Yet another concept of the present technology is a receiving unit that receives a transmission stream obtained by time-division multiplexing a first transmission packet including a predetermined component and a second transmission packet including information related to the predetermined component through a predetermined transmission path; The second transmission packet is inserted with information on a plurality of delivery protocols, each of which includes at least location information and protocol identification information, for acquiring a specific component to be acquired through a communication path, or acquisition information for acquiring the information on the plurality of delivery protocols; The apparatus further includes a processing unit for processing the transmission stream received by the receiving unit. in the receiving device. Effect of the Invention

[0022] According to the present technology, it is possible to satisfactorily realize hybrid services of broadcasting and communication. Note that the effects described in this specification are merely examples and are not limiting, and additional effects may also be provided. [Brief description of the drawings]

[0023] [Figure 1] 1 is a block diagram showing an example of the configuration of a broadcasting and communication hybrid system according to an embodiment. [Diagram 2] FIG. 1 is a diagram showing a stack model of an example of an MMT / broadcast signal configuration. [Diagram 3] FIG. 1 is a diagram illustrating an example of the configuration of an MMT broadcast stream. [Figure 4] FIG. 1 is a diagram showing an image of a broadcast signal of one channel (broadcast program) transmitted from a broadcast transmission system to a receiving terminal. [Diagram 5] 1A to 1C are diagrams illustrating an example of the configuration of an MMT packet and an example of the configuration of an MMTP payload. [Figure 6] FIG. 1 is a diagram illustrating a stack model of an example of a signal configuration of MMT / communication. [Figure 7] FIG. 1 illustrates an example of an MMT distribution network environment. [Figure 8]1 is a diagram illustrating an example of the configuration of a PA message (Package Access Message) and an MP table (MPT: MMT Package Table). FIG. [Figure 9] FIG. 13 is a diagram illustrating the main parameters of a PA message. [Figure 10] FIG. 13 is a diagram illustrating the main parameters of the MP table. [Figure 11] FIG. 13 is a diagram showing an example of the syntax of a PA message. [Figure 12] FIG. 2 is a diagram showing an example structure (Syntax) of an MP table (MPT). [Figure 13] A diagram showing a portion of an example structure (Syntax) of "MMT_general_location_info()". [Figure 14] 11 is a diagram showing an example of a description of an MP table (MPT) into which information on multiple delivery protocols is inserted in relation to a specific component (asset) of a communication path. FIG. [Figure 15] FIG. 13 is a diagram illustrating an example of the structure of a communication distribution descriptor. [Figure 16] A diagram showing the contents of main information in an example structure of a communication distribution descriptor. [Figure 17] 11 is a diagram showing an example of a description of an MP table (MPT) into which information on multiple delivery protocols is inserted in relation to a specific component (asset) of a communication path. FIG. [Figure 18] FIG. 13 is a diagram illustrating an example of the structure of a communication distribution descriptor. [Figure 19] FIG. 13 is a diagram showing an example of a description of an MP table (MPT) into which acquisition information for acquiring information of multiple delivery protocols is inserted in relation to a specific component (asset) of a communication path. [Figure 20] 13 is a diagram showing an example of the structure of a BD table in which information on a plurality of delivery protocols is described, and the contents of each piece of information. [Figure 21] 13 is a flowchart showing an example of a view selection / reception process in a receiving terminal. [Figure 22]FIG. 1A is a diagram illustrating a receiving sequence when receiving an asset distributed using a multicast distribution protocol. [Figure 23] FIG. 1B is a diagram for explaining a reception sequence when receiving an asset distributed using the MMTP / UDP distribution protocol. [Figure 24] FIG. 1C is a diagram for explaining a receiving sequence when receiving an asset distributed using the MMTP / TCP distribution protocol. [Diagram 25] FIG. 1D is a diagram for explaining a reception sequence when receiving an asset distributed using the MMTP / HTTP distribution protocol. [Figure 26] 11 is a diagram for explaining a cut-out process in an MMTP / HTTP multiplexed stream. FIG. [Figure 27] FIG. 1E is a diagram illustrating a receiving sequence when receiving an asset distributed using the MPU / HTTP distribution protocol. [Figure 28] 1 is a block diagram showing an example of the configuration of a broadcast transmission system. [Figure 29] FIG. 2 is a block diagram showing a configuration example of a receiving terminal. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] Hereinafter, modes for carrying out the invention (hereinafter, referred to as "embodiments") will be described. The description will be made in the following order. 1. Embodiment 2. Variations

[0025] <1. Preferred embodiment> [Example of a broadcasting / communication hybrid system configuration] 1 shows an example of the configuration of a broadcasting and communication hybrid system 10. In the broadcasting and communication hybrid system 10, a broadcasting 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 via a communication network 400.

[0026] The broadcast transmission system 100 transmits IP (Internet Protocol) broadcast signals including components (assets) such as video and audio as transmission media. The distribution server 300 distributes a transmission stream in which IP packets including components (assets) such as video and audio as transmission media are consecutively arranged to the receiving side via a communication network 400, for example, in response to a request from the receiving side.

[0027] The receiving terminal 200 receives IP broadcast signals sent from the broadcast transmission system 100, and also receives a transmission stream in which IP packets are arranged consecutively 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 by such hybrid transmission of broadcast and communication, and presents images, sounds, etc.

[0028] In the IP broadcast signal, information on a plurality of delivery protocols for acquiring a specific component is inserted in association with the specific component to be acquired via a communication path. Each of the plurality of pieces of delivery protocol information includes at least location information and protocol identification information. The receiving terminal 200 selects one receivable delivery protocol from the plurality of pieces of delivery protocol information, and receives the delivery of the specific component via that delivery protocol.

[0029] Figure 2 shows a stack model of an example of MMT / broadcast signal configuration. A TLV (Type Length Value) transmission packet exists in the lower layer. An IP packet is carried on top of this TLV transmission packet. There is also a TLV transmission packet that carries a transmission control signal as signaling information.

[0030] UDP (User Datagram Protocol) is carried on top of IP packets. MMT (MPEG Media Transport) packets are carried on top of UDP. The payload of these MMT packets contains MMT Fragment Units (MFUs) that contain coded data for components such as video and audio, or signaling messages that contain information about the transmission media.

[0031] Figure 3 shows an example of the structure of an MMT broadcast stream. Figure 3(a) shows a video elementary stream (Video ES). This video elementary stream is divided into chunks of a specified size and placed in the payload section of the MFU, as shown in Figure 3(b).

[0032] As shown in Fig. 3(c), an MMT payload header is added to the MFU to form an MMTP payload. Then, as shown in Fig. 3(d), an MMT header is added to this MMTP payload to form an MMT packet. Note that there are also MMT packets that contain a signaling message in the payload section. As shown in Fig. 3(e), 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 broadcast stream.

[0033] Although not shown in the figure, there are also TLV packets that include MMT packets of other components such as audio. This MMT broadcast stream has a first packet (MMT packet) that includes a transmission medium (component) and a second packet (MMT packet) that includes signaling information.

[0034] 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 for video, audio, etc. As a signaling message, for example, there exists a PA message including an MP table, etc.

[0035] FIG. 5(a) shows an example of the structure of an MMT packet. An MMT packet consists of an MMT packet header (MMTP header) and an MMTP payload (MMTP payload). The 2-bit field "V" indicates the version of the MMT protocol. When following the first edition of the MMT standard, this field is set to "00". The 1-bit field "C" indicates packet counter flag information, and is set to "1" if a packet counter flag exists. The 2-bit field "FEC" indicates the FEC type (FEC_type).

[0036] The 1-bit field "X" indicates extension header flag information, and is set to "1" when the header of the MMT packet is extended. In this case, the "header_extension" field described later exists. The 1-bit field "R" indicates RAP flag information, and is set to "1" when the MMT payload transmitted by this MMT packet includes the beginning of a random access point.

[0037] The 6-bit field of "type" is 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.

[0038] The 16-bit field "packet_id" indicates the packet identifier (packet_id) to identify the data type of the payload. The 32-bit field "timestamp" indicates the time stamp for transmission, i.e., the time when the MMT packet leaves the sender. This time is expressed in NTP short format. The 32-bit field "packet_sequence_number" indicates the sequence number of the MMT packet with the same packet identifier (packet_id). The 32-bit field "packet_counter" indicates the order of MMT packets in the same IP data flow, regardless of the value of the packet identifier (packet_id).

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

[0040] Figure 5(b) shows an example of the syntax of the MMTP payload placed in the "payload data" field of the above-mentioned MMT packet. Note that this example shows the case of MPU mode, where the "type" of the MMT header is "0x00". The header information comes first. The 16-bit "length" field indicates the byte size of the entire MMTP payload. The 4-bit "FT" field indicates the field type. "0" indicates that it contains "MPU metadata", "1" indicates that it contains "Movie Fragment metadata", and "2" indicates that it contains "MFU".

[0041] Here, an MFU (MMT Fragment Unit) is an MPU that has been divided, i.e., fragmented. For example, in the case of video, this MFU can be set to correspond to one NAL unit. Also, for example, when sending over a communication network transmission path, this MFU can be configured with one or more MTU sizes.

[0042] Moreover, an MPU starts from a random access point (RAP) and includes one or more access units (AU). Specifically, for example, the pictures of one GOP (Group Of Pictures) may constitute one MPU. This MPU is defined by asset (component). Therefore, a video MPU including only video data is created from a video asset, and an audio MPU including only audio data is created from an audio asset.

[0043] The 1-bit flag information "T" indicates whether timed media or non-timed media is being transmitted. "1" indicates timed media, and "0" indicates non-timed media.

[0044] The 2-bit field of "f_i" indicates whether the "DU payload" field contains an integer number of data units (DUs) or the first, middle, or last of a fragment obtained by fragmenting a data unit. "0" indicates that an integer number of data units are contained, "1" indicates that the first fragment is contained, "2" indicates that the middle fragment is contained, and "3" indicates that the last fragment is contained.

[0045] The 1-bit flag information of "A" indicates whether the "DU payload" field contains multiple data units or not. "1" indicates that it contains multiple data units, and "0" indicates that it does not contain multiple data units. The 8-bit field of "frag_counter" indicates which fragment it is when "f_i" is 1 to 3.

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

[0047] After this "MPU_sequence_number" field, the "DU_length", "DU_header", and "DU_payload" fields are placed. The 16-bit "DU_length" field does not exist when the above-mentioned "A=0" is satisfied, that is, when the "DU payload" field does not contain multiple data units. The "DU_header" field does not exist when "FT=0 / 1" is satisfied, that is, when "MPU metadata" or "Movie Fragment metadata" is included.

[0048] Figure 6 shows a stack model of an example of the signal configuration of MMT / communication. Possible delivery options for MMT / communication are (A) multicast delivery, (B) MMTP / UDP delivery, (C) MMTP / TCP delivery, (D) MMTP / HTTP delivery, and (E) MPU / HTTP delivery.

[0049] "(A) Multicast distribution" In the case of multicast distribution, IP packets exist at the lower layer. UDP (User Datagram Protocol) is placed on top of this IP packet. MMT (MPEG Media Transport) packets are placed on top of UDP. The payload of this MMT packet contains MPUs that contain the coded data of components such as video and audio.

[0050] This multicast delivery is the most desirable method for hybrid broadcasting and communication use, taking congestion countermeasures into consideration. In addition, this multicast delivery uses UDP transmission, so transmission efficiency is good, but there is a problem with packet loss, so AL-FEC (Application Layer-Forward Error Correction) may be required.

[0051] In addition, in the case of this multicast distribution, only receiving terminals directly connected to the managed network are available. In addition, in the case of this multicast distribution, there are cases where the multicast IP stream transmits an MMTP stream in which multiple assets (components) are multiplexed, and cases where the multicast IP stream transmits an MMTP stream that contains only a single asset.

[0052] "(B)MMTP / UDP Delivery" In the case of MMTP / UDP delivery, IP packets exist at the lower layer. UDP (User Datagram Protocol) is placed on top of this IP packet. MMT packets are placed on top of UDP. The payload of this MMT packet contains MPUs that contain the encoded data of components such as video and audio.

[0053] In the case of MMTP / UDP delivery, since it is unicast, there are congestion problems when used for hybrid broadcasting and communication. Also, since this MMTP / UDP delivery is UDP transmission, the transmission efficiency is good, but AL-FEC may be required. Also, in the case of multicast delivery, it is better than TCP in terms of total delay and synchronization.

[0054] In addition, this MMTP / UDP distribution is unicast, so it can be widely used on general Internet-connected devices, but depending on the router settings, it may not be available by default. In the case of this MMTP / UDP distribution, there are cases where the IP stream transmits an MMTP stream in which multiple assets (components) are multiplexed, and cases where it transmits an MMTP stream that contains only a single asset.

[0055] "(C)MMTP / TCP Delivery" In the case of MMTP / TCP delivery, IP packets exist at the lower layer. TCP (Transmission Control Protocol) is placed on top of this IP packet. And MMT packets are placed on top of TCP. The payload of this MMT packet contains MPUs that contain the encoded data of components such as video and audio.

[0056] This MMTP / TCP delivery is unicast, so it can be widely used by general Internet-connected devices. Also, because this MMTP / TCP delivery is unicast, there are congestion issues when used as a hybrid of broadcasting and communication. Also, because this MMTP / TCP delivery is TCP transmission, efficiency is sacrificed, but retransmission is possible, so AL-FEC is not required.

[0057] In the case of this MMTP / TCP distribution, there are cases where the IP stream transmits an MMTP stream in which multiple assets (components) are multiplexed, and cases where the IP stream transmits an MMTP stream that includes only a single asset.

[0058] "(D)MMTP / HTTP distribution" In the case of MMTP / HTTP delivery, IP packets exist at the lower layer. TCP is placed on top of this IP packet. HTTP (Hyper Text Transfer Protocol) is placed on top of TCP, and MMT packets are placed on top of that. The payload of this MMT packet contains MPUs that contain the encoded data of components such as video and audio.

[0059] This MMTP / HTTP delivery uses HTTP, so it can be used widely with general Internet-connected devices. Also, this MMTP / HTTP delivery uses unicast, so there are congestion issues when used in a hybrid broadcast / communication environment. Also, this MMTP / HTTP delivery uses TCP transmission, so efficiency is sacrificed, but retransmission is possible, so AL-FEC is not required.

[0060] In the case of this MMTP / HTTP distribution, there are cases where the IP stream transmits an MMTP stream in which multiple assets (components) are multiplexed, and cases where the IP stream transmits an MMTP stream that includes only a single asset.

[0061] "(E)MPU / HTTP Delivery" In the case of MPU / HTTP delivery, IP packets exist at the lower layer. TCP is placed on top of this IP packet. HTTP is placed on top of TCP, and the payload of this HTTP packet contains MPU, which contains the encoded data of components such as video and audio.

[0062] This MPU / HTTP distribution uses HTTP, so it can be used on a wide range of general-purpose Internet-connected devices. Also, this MPU / HTTP distribution uses unicast, so there are congestion issues when used in a hybrid broadcast / communication environment. Also, this MPU / HTTP distribution uses TCP transmission, so efficiency is sacrificed, but retransmission is possible, so AL-FEC is not required.

[0063] In addition, with this MPU / HTTP distribution, since there is no MMT packet involved, the transmission efficiency is better than with MMTP / HTTP distribution, but on the other hand, there is the issue of information loss, such as the MMTP header. Also, with this MPU / HTTP distribution, the receiving terminal obtains the individual MPU files of a single asset (component) via HTTP.

[0064] Fig. 7 shows an example of an MMT distribution network environment. Receiving terminals 200a, 200b, and 200c are each connectable to an edge router (ER) of a managed network MNa via a home router (HR). Therefore, these receiving terminals 200a, 200b, and 200c can receive distribution from an MMT / multicast server with an IP address of "a" in the managed network using a multicast distribution protocol (A).

[0065] Furthermore, these receiving terminals 200a, 200b, and 200c are each capable of connecting to an MMT server via a home router HR, a managed network MNa, and the like. Furthermore, the home router (HR) to which these receiving terminals 200a, 200b, and 200c are connected is set to enable the use of UDP. Therefore, these receiving terminals 200a, 200b, and 200c can receive distribution from the MMT server using any of the following protocols: (B) MMTP / UDP distribution, (C) MMTP / TCP distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution.

[0066] Moreover, the receiving terminals 200g, 200h, and 200i can be connected to an edge router (ER) of the managed network MNb via a home router (HR), respectively. Therefore, these receiving terminals 200g, 200h, and 200i can receive distribution from an MMT / multicast server with an IP address of "b" in the managed network using the (A) multicast distribution protocol.

[0067] Furthermore, these receiving terminals 200g, 200h, and 200i can be connected to the MMT server via a home router HR, a managed network MNb, and the like. Furthermore, the home router (HR) to which these receiving terminals 200g, 200h, and 200i are connected is set to enable the use of UDP. Therefore, these receiving terminals 200g, 200h, and 200i can receive distribution from the MMT server using any of the following protocols: (B) MMTP / UDP distribution, (C) MMTP / TCP distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution.

[0068] The receiving terminal 200d can connect to an MMT server via a home router HR, and the home router (HR) to which the receiving terminal 200d is connected is also set to enable the use of UDP. Therefore, the receiving terminal 200d can receive data delivered by any of the following protocols: (B) MMTP / UDP delivery, (C) MMTP / TCP delivery, (D) MMTP / HTTP delivery, and (E) MPU / HTTP delivery.

[0069] In addition, the receiving terminals 200e and 200f can connect to the MMT server via the home router HR, but the home router (HR) to which these receiving terminals 200e and 200f are connected is not set to enable the use of UDP. Therefore, these receiving terminals 200e and 200f can only receive distribution using either the (D) MMTP / HTTP distribution or (E) MPU / HTTP distribution protocol.

[0070] Fig. 8 shows a schematic structure of a PA message (Package Access Message) and an MP table (MPT: MMT Package Table). Fig. 9 shows an explanation of main parameters of the PA message, and Fig. 10 shows an explanation of main parameters of the MP table.

[0071] "message_id" is a fixed value that identifies the PA message in various signaling information. "version" is an 8-bit integer value that indicates the version of the PA message. For example, if even some of the parameters that make up the MP table are updated, it is incremented by +1. "length" is the number of bytes that indicates the size of the PA message, counted from immediately after this field.

[0072] The "extension" field contains index information for the table placed in the payload field. This field contains the fields "table_id", "table_version", and "table_length" for each table. "table_id" is a fixed value that identifies a table. "table_version" indicates the version of the table. "table_length" is the number of bytes that indicates the size of the table.

[0073] An MP table (MPT) and a predetermined number of other tables are placed in the payload field of the PA message. The configuration of the MP table will be described below.

[0074] "table_id" is a fixed value that identifies the MP table in various signaling information. "version" is an 8-bit integer value that indicates the version of the MP table. For example, if even some of the parameters that make up the MP table are updated, it is incremented by +1. "length" is the number of bytes that indicates the size of the MP table, counted from immediately after this field.

[0075] "pack_id" is identification information for the entire package, whose constituent elements are all assets (components) transmitted by broadcasting and communication. This identification information is text information. "pack_id_len" indicates the size (number of bytes) of that text information. The "MPT_descripors" field is a storage area for descriptors related to the entire package. "MPT_dsc_len" indicates the size (number of bytes) of that field.

[0076] "num_of_asset" indicates the number of assets (components) that make up the package. This number of asset loops are placed as follows: "asset_id" is information that uniquely identifies the asset (asset ID). This identification information is text information. "asset_id_len" indicates the size (number of bytes) of that text information. "gen_loc_info" is information that indicates the location from which the asset was obtained. The "asset_descriptors" field is a storage area for descriptors related to assets. "asset_dsc_len" indicates the size (number of bytes) of that field.

[0077] FIG. 11 shows an example structure (Syntax) of the above-mentioned PA message. FIG. 12 shows an example structure (Syntax) of the above-mentioned MP table (MPT). The "gen_loc_info" field in FIG. 8 corresponds to the "asset_location" field in FIG. 12, and multiple "MMT_general_location_info()" can be placed as information indicating the location of the asset acquisition destination. The "asset_descriptors" field in FIG. 8 corresponds to the "asset_descriptors" field in FIG. 12.

[0078] FIG. 13 shows a part of the structure example (Syntax) of "MMT_general_location_info()". The 8-bit field of "location_type" indicates the type of information (hereinafter referred to as "location information") indicating the location of the asset acquisition destination. In the case of an asset distributed using the above-mentioned (A) multicast distribution protocol, "location_type" is set to "0x01" or "0x02", and the source address (ipv4_src_addr, ipv6_src_addr), destination address (ipv4_dst_addr, ipv6_dst_addr), destination port number (dst_port), and packet identifier (packt_id) are inserted as location information. In this case, "location_type" identifies it as multicast distribution.

[0079] In addition, if the asset is delivered using the above-mentioned (B) MMTP / UDP delivery, (C) MMTP / TCP delivery, (D) MMTP / HTTP delivery, or (E) MPU / HTTP delivery protocol, "location_type" is set to "0x05" and a URL (Uniform Resource Locator) is placed as the location information.

[0080] Here, if the asset is distributed using the (B) MMTP / UDP distribution protocol, "rtsp: / / ~.mmt" is specified as the schema, and a parameter specifying UDP and a parameter specifying the packet identifier (packet_id) are added in the query field. Ultimately, the URL in this case is expressed as "rtsp: / / ~.mmt?pr=udp&pid=1". In this case, "rtsp" and "pr=udp" identify it as MMTP / UDP distribution.

[0081] Also, if the asset is distributed using the (C)MMTP / TCP distribution protocol, "rtsp: / / ~.mmt" is specified as the schema, and a parameter specifying TCP and a parameter specifying the packet identifier (packet_id) are added in the query field. In this case, the URL is expressed as "rtsp: / / ~.mmt?pr=udp&pid=1". In this case, "rtsp" and "pr=tcp" identify it as MMTP / TCP distribution.

[0082] Also, if the asset is distributed using the (D) MMTP / HTTP distribution protocol, "http: / / ~.mmt" is specified as the schema, and a parameter specifying the packet identifier (packet_id) is added in the query field. In this case, the URL is expressed as "http: / / ~.mmt?pr=pid=1". In this case, "http" and "mmt" identify it as an MMTP / HTTP distribution.

[0083] Also, if the asset is distributed using the (E)MPU / HTTP distribution protocol, "http: / / ~.mp4" is specified as the schema. In other words, the URL in this case is expressed as "http: / / ~.mp4". In this case, "http" and "mp4" identify it as MPU / HTTP distribution.

[0084] "Inserting information about or acquiring information from multiple delivery protocols" In this embodiment, information on multiple delivery protocols or acquisition information for acquiring the information on multiple delivery protocols is inserted into the MP table (MPT) in association with an asset (component) transmitted by communication, i.e., a specific component to be acquired on a communication path. Each piece of information on multiple delivery protocols includes at least location information and protocol identification information. As an insertion method, for example, the following methods 1, 2, and 3 are considered.

[0085] "Method 1" In the case of method 1, multiple pieces of information about a specific component (asset) are placed in the MP table (MPT), and one piece of information from multiple distribution protocols is inserted into each of the multiple pieces of information placed. In this case, only one "MMT_general_location_info()" is written for each asset (see Figure 12).

[0086] We will further explain this method 1. Here, we will explain the use case where there are two sets of video and audio signals, 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. In addition, in this use case, it is assumed that distribution can be done using three protocols: (A) multicast distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution.

[0087] 14(a) shows an outline of an example of description of an MP table (MPT). The asset (component) "Asset1" indicates a video signal (Video1) to be broadcast. The asset (component) "Asset2" indicates an audio signal (Audio1) to be broadcast.

[0088] The asset (component) "Asset3" indicates (A) a video signal (Video2) transmitted by a multicast distribution protocol. The source address (ipv4_src_addr, ipv6_src_addr), destination address (ipv4_dst_addr, ipv6_dst_addr), destination port number (dst_port), and packet identifier (packt_id) are inserted into the "MMT_general_location_info()" of this asset.

[0089] In addition, a newly defined communication delivery descriptor (broadband_delivery_descriptor) is inserted into the "asset_descriptors" field of this asset. This descriptor describes the communication transmission protocol type (delivery protocol type) "type=broadband_delivery_type", information on other assets that are multiplexed with the asset and delivered "mg=multiplex_group", and information on available managed networks "ANmap1". Here, "type" indicates (A) multicast delivery, and "mg" indicates that the asset is multiplexed with other assets that make up group 1 and delivered.

[0090] FIG. 15 shows an example structure (Syntax) of a communication delivery descriptor (broadband_delivery_descriptor), and FIG. 16 shows the main information content (Semantics) in the example structure. The 16-bit field "descriptor_tag" indicates the descriptor type. In this case, it indicates that it is a communication delivery descriptor. The 8-bit field "descriptor_length" indicates the length (size) of the descriptor, and indicates the number of subsequent bytes as the length of the descriptor.

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

[0092] 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, it is set to an identification value of 1 or more of the multiplexed stream.

[0093] The "additional_network_info()" field contains related additional information. In the case of Type A, it is the 8-bit "available_network_map" field. This 8-bit "available_network_map" field indicates a bitmap of available managed networks. In this case, bits 0 to 7 are assigned to each carrier.

[0094] Returning to Figure 14, the asset (component) "Asset4" indicates a video signal (Video2) transmitted via the (D) MMTP / HTTP distribution protocol. A URL is inserted into the "MMT_general_location_info()" of this asset. In this case, as described above, "http: / / ~.mmt" is specified as the schema, and a parameter specifying the packet identifier (packet_id) is added by the query field.

[0095] In addition, the above-mentioned communication delivery descriptor (broadband_delivery_descriptor) is inserted into the "asset_descriptors" field of this asset (see Figure 15). Here, "type" indicates that it is (D)MMTP / HTTP delivery, and "mg" indicates that it will be multiplexed with other assets that make up group 2 and delivered.

[0096] The asset (component) "Asset5" represents a video signal (Video2) transmitted via the (E)MPU / HTTP distribution protocol. A URL is inserted into this asset's "MMT_general_location_info()". In this case, as mentioned above, "http: / / ~.mp4" is specified as the schema.

[0097] Also, the above-mentioned communication delivery descriptor (broadband_delivery_descriptor) is inserted into the "asset_descriptors" field of this asset (see Figure 15). Here, "type" indicates that it is (E)MPU / HTTP delivery, and "mg" is set to "0", indicating that it is not multiplexed. This allows the receiving side to understand that this "Asset5" will be delivered independently, as shown in Figure 14(b).

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

[0099] The asset (component) "Asset6" indicates (A) an audio signal (Audio2) transmitted using a multicast distribution protocol. The source address (ipv4_src_addr, ipv6_src_addr), destination address (ipv4_dst_addr, ipv6_dst_addr), destination port number (dst_port), and packet identifier (packt_id) are inserted into the "MMT_general_location_info()" of this asset.

[0100] In addition, the above-mentioned communication delivery descriptor (broadband_delivery_descriptor) is inserted into the "asset_descriptors" field of this asset (see FIG. 15). Here, "type" indicates (A) multicast delivery, and information on the available managed network, "ANmap1", is also described.

[0101] Additionally, "mg" indicates that the asset will be multiplexed with the other assets that make up Group 1 and distributed. This allows the receiving side to understand that this "Asset6" will be multiplexed with the above-mentioned "Asset3" and distributed, as shown in Fig. 14(b). The receiving side can obtain both "Asset3" and "Asset6" from this multiplexed stream.

[0102] The asset (component) "Asset7" indicates an audio signal (Audio2) transmitted via the (D)MMTP / HTTP distribution protocol. A URL is inserted into this asset's "MMT_general_location_info()". In this case, as mentioned above, "http: / / ~.mmt" is specified as the schema, and a parameter specifying the packet identifier (packet_id) is added by the query field.

[0103] Additionally, the above-mentioned communication delivery descriptor (broadband_delivery_descriptor) is inserted into the "asset_descriptors" field of this asset (see Figure 15). Here, "type" indicates that it is (D)MMTP / HTTP delivery, and "mg" indicates that it will be multiplexed with other assets that make up group 2 and delivered. This allows the receiving side to see that this "Asset7" will be multiplexed with the above-mentioned "Asset4" and delivered, as shown in Figure 14(b). The receiving side can obtain both "Asset4" and "Asset7" from this multiplexed stream.

[0104] The asset (component) "Asset8" indicates an audio signal (Audio2) that is transmitted using the (E)MPU / HTTP distribution protocol. A URL is inserted into this asset's "MMT_general_location_info()". In this case, as mentioned above, "http: / / ~.mp4" is specified as the schema.

[0105] Also, the above-mentioned communication delivery descriptor (broadband_delivery_descriptor) is inserted into the "asset_descriptors" field of this asset (see Figure 15). Here, "type" indicates that it is (E)MPU / HTTP delivery, and "mg" is set to "0", indicating that it is not multiplexed. This allows the receiving side to understand that this "Asset8" will be delivered independently, as shown in Figure 14(b).

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

[0107] "Method 2" In the case of method 2, one piece of information for a specific component (asset) is placed in the MP table (MPT), and information for multiple distribution protocols is inserted into this one piece of information. In this case, multiple "MMT_general_location_info()" are written for each asset (see Figure 12). In the MP table, "MMT_general_location_info()" is looped, so multiple entries are possible.

[0108] We will further explain Method 2. As with the explanation of "Method 1" above, we will explain the use case where there are two sets of video and audio signals, 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. Also, in this use case, it is assumed that distribution can be done using three protocols: (A) multicast distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution.

[0109] 17(a) shows an outline of an example of description of an MP table (MPT). The asset (component) "Asset1" indicates a video signal (Video1) to be transmitted by broadcast. The asset (component) "Asset2" indicates an audio signal (Audio1) to be transmitted by broadcast.

[0110] The asset (component) "Asset3" indicates the video signal (Video2) being transmitted. Three "MMT_general_location_info()" are described in the "asset_location" field of this asset.

[0111] The first "MMT_general_location_info()" contains location information for the highest priority (A) multicast distribution. That is, the source address (ipv4_src_addr, ipv6_src_addr), destination address (ipv4_dst_addr, ipv6_dst_addr), destination port number (dst_port), and packet identifier (packt_id) are inserted into this "MMT_general_location_info()".

[0112] The second "MMT_general_location_info()" contains location information for MMTP / HTTP distribution, which has the next highest priority (D). In other words, a URL is inserted into this "MMT_general_location_info()". In this case, as described above, "http: / / ~.mmt" is specified as the schema, and a parameter specifying the packet identifier (packet_id) is added in the query field.

[0113] The third "MMT_general_location_info()" contains location information for (E)MPU / HTTP distribution, which has the lowest priority. In other words, a URL is inserted into this "MMT_general_location_info()". In this case, as described above, "http: / / ~.mp4" is specified as the schema.

[0114] In addition, a newly defined communication delivery descriptor (broadband_delivery_descriptor) is inserted into the "asset_descriptors" field of this asset. In this descriptor, the communication transmission protocol type (delivery protocol type) "type=broadband_delivery_type" and information on other assets that are multiplexed with the asset and delivered "mg=multiplex_group" are described in correspondence with the three "MMT_general_location_info()" described above. Note that when location information in the case of (A) multicast delivery is inserted into "MMT_general_location_info()", information on available managed networks "ANmap" is also described.

[0115] Here, corresponding to the first "MMT_general_location_info()", "type" indicates (A) multicast distribution, and "mg" indicates that the asset is multiplexed with other assets constituting group 1 and distributed. Also, "ANmap" is set to "ANmap1", indicating an available managed network.

[0116] Also, corresponding to the second "MMT_general_location_info()", "type" indicates that it is (D)MMTP / HTTP distribution, and "mg" indicates that it will be multiplexed with other assets that make up group 2 and distributed.

[0117] Also, corresponding to the third "MMT_general_location_info()", "type" indicates that it is (E)MPU / HTTP distribution, and "mg" is set to "0", indicating that it is not multiplexed. As a result, the receiving side can see that in the case of (E)MPU / HTTP distribution, "Asset3" will be distributed alone, as shown in Figure 17(b).

[0118] FIG. 18 shows an example structure (Syntax) of a communication delivery descriptor (broadband_delivery_descriptor). The 16-bit field "descriptor_tag" indicates the descriptor type. In this case, it indicates that it is a communication delivery descriptor. The 8-bit field "descriptor_length" indicates the length (size) of the descriptor, and indicates the number of subsequent bytes as the length of the descriptor.

[0119] The 8-bit field "number_of_delivery" indicates the number of delivery protocols that can be used for delivery. The 3-bit field "broadband_delivery_type", the 1-bit field "ip_version", the 4-bit field "multiplex_group", and the 8-bit field "available_network_map" are repeated for each delivery protocol.

[0120] The 3-bit field of "broadband_delivery_type" indicates the communication transmission protocol type (delivery protocol type) (see Figure 16). For example, "1" indicates type A, i.e. (A) multicast delivery. "2" indicates type B, i.e. (B) MMTP / UDP delivery. "3" indicates type C, i.e. (C) MMTP / TCP delivery. "4" indicates type D, i.e. (D) MMTP / HTTP delivery. "5" indicates type E, i.e. (E) MPU / HTTP delivery. Also, "7" indicates that it is specified in the BDT (broadband_delivery_Table).

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

[0122] Except for (A) multicast distribution in which "broadband_delivery_type" is set to "1", bits 0 through 7 of the 8-bit field of "available_network_map" are all set to "0", and this field is essentially unused.

[0123] The asset (component) "Asset4" represents the audio signal (Audio2) being transmitted. The "asset_location" field of this asset contains three "MMT_general_location_info()" entries.

[0124] The first "MMT_general_location_info()" contains location information for the highest priority (A) multicast distribution. That is, the source address (ipv4_src_addr, ipv6_src_addr), destination address (ipv4_dst_addr, ipv6_dst_addr), destination port number (dst_port), and packet identifier (packt_id) are inserted into this "MMT_general_location_info()".

[0125] The second "MMT_general_location_info()" contains location information for MMTP / HTTP distribution, which has the next highest priority (D). In other words, a URL is inserted into this "MMT_general_location_info()". In this case, as described above, "http: / / ~.mmt" is specified as the schema, and a parameter specifying the packet identifier (packet_id) is added in the query field.

[0126] The third "MMT_general_location_info()" contains location information for (E)MPU / HTTP distribution, which has the lowest priority. In other words, a URL is inserted into this "MMT_general_location_info()". In this case, as described above, "http: / / ~.mp4" is specified as the schema.

[0127] In addition, the above-mentioned communication delivery descriptor (broadband_delivery_descriptor) is inserted into 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" and information on other assets that are multiplexed with the asset and delivered "mg=multiplex_group" are described in correspondence with the three "MMT_general_location_info()" described above. When location information in the case of (A) multicast delivery is inserted into "MMT_general_location_info()", information on available managed networks "ANmap" is also described.

[0128] Here, corresponding to the first "MMT_general_location_info()", "type" indicates (A) multicast distribution, and "ANmap" is set to "ANmap1", indicating the available managed network. Also, "mg" indicates that the asset will be multiplexed with other assets that make up group 1 and distributed. As a result, the receiving side can see that in the case of (A) multicast distribution, "Asset4" will be multiplexed with the above-mentioned "Asset3" and distributed, as shown in FIG. 17(b). The receiving side can obtain both "Asset3" and "Asset4" from this multiplexed stream.

[0129] Also, corresponding to the second "MMT_general_location_info()", "type" indicates that it is (D) MMTP / HTTP distribution, and "mg" indicates that it will be multiplexed with other assets that make up group 2 and distributed. As a result, the receiving side can see that in the case of (D) MMTP / HTTP distribution, "Asset4" will be multiplexed with the above-mentioned "Asset3" and distributed, as shown in Figure 17(b). The receiving side can obtain both "Asset3" and "Asset4" from this multiplexed stream.

[0130] Also, corresponding to the third "MMT_general_location_info()", "type" indicates that it is (E)MPU / HTTP distribution, and "mg" is set to "0", indicating that it is not multiplexed. As a result, the receiving side can see that in the case of (E)MPU / HTTP distribution, "Asset4" will be distributed alone, as shown in Figure 17(b).

[0131] "Method 3" In the case of method 3, one piece of information for a specific component (asset) is placed in the MP table (MPT), and acquisition information for acquiring information for multiple distribution protocols is inserted into this piece of information. In this case, only one "MMT_general_location_info()" is written for each asset (see Figure 12).

[0132] We will further explain Method 3. As with the explanations of "Method 1" and "Method 2" above, we will explain the use case in which there are two sets of video and audio signals, 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. Also, in this use case, it is assumed that distribution can be done using three protocols: (A) multicast distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution.

[0133] 19(a) shows an outline of an example of description of an MP table (MPT). The asset (component) "Asset1" indicates a video signal (Video1) to be broadcast. The asset (component) "Asset2" indicates an audio signal (Audio1) to be broadcast.

[0134] The asset (component) "Asset3" indicates a video signal (Video2) to be 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 multiple delivery protocols related to this "Asset3". The receiving side refers to this URL and acquires a BD table (BDT: Broadband Delivery Table) as a metafile containing information on multiple delivery protocols via the communication network (see FIG. 19(b)).

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

[0136] In addition, for example, the communication delivery descriptor (broadband_delivery_descriptor) in the above-mentioned "Method 1" (see Figure 15) is inserted into the "asset_descriptors" field of this asset, and "type=broadband_delivery_type" is set to "7", indicating that information on multiple delivery protocols is specified in the BD table.

[0137] FIG. 20 shows an example of the structure (Syntax) of a BD table and the contents (Semantics) of each piece of information. This BD table is written in XML format. The "@version" information is the version number of this table. "BDI" is an item of BD information that is a distribution option for communications, and appears in a predetermined number of instances. Here, it is assumed that distribution can be performed using three protocols: (A) multicast distribution, (D) MMTP / HTTP distribution, and (E) MPU / HTTP distribution, so three instances appear. The order of description indicates the priority order.

[0138] "BDI" includes "@delivery_type" and "@multiplex_group". "@delivery_type" is the communication protocol type, and corresponds to "broadband_delivery_type" in the communication delivery descriptor in FIG. 18. "@multiplex_group" is the group ID of the multiplexed stream, and corresponds to "multiplex_group" in the communication delivery descriptor in FIG. 18. If no multiplexing is performed, this description does not appear, or a group ID indicating that no multiplexing is performed is described.

[0139] "BDI" also 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", they are information items inserted into "MMT_general_location_info()". "MC_info" is multicast information, and "location_url" is unicast location information, and either one will appear. "MC_info" will appear if multicast delivery is described as the communication protocol type in "@delivery_type", and "location_url" will appear in other cases.

[0140] "MC_info" includes "@sourceIPAddress", "@destinationIPAddress", "@portNumber", "@pid", and "ManagedNetworkName". "@sourceIPAddress" is the multicast source IP address. "@destinationIPAddress" is the multicast destination IP address. "@portNumber" is the multicast port number. "@pid" is the PID of the multicast MMT packet. "ManagedNetworkName" is the name of the managed network that is delivered via the multicast address. "location_url" includes "@url". "@url" is the delivery URL.

[0141] Returning to FIG. 19, the asset (component) "Asset4" indicates an audio signal (Audio2) to be transmitted via 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 multiple delivery protocols related to this "Asset4". The receiving side refers to this URL and acquires a BD table (BDT: Broadband Delivery Table) as a metafile containing information on multiple delivery protocols via the communication network (see FIG. 19(b)).

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

[0143] In addition, for example, the communication delivery descriptor (broadband_delivery_descriptor) in the above-mentioned "Method 1" (see Figure 15) is inserted into the "asset_descriptors" field of this asset, and "type=broadband_delivery_type" is set to "7", indicating that information on multiple delivery protocols is specified in the BD table.

[0144] Even in method 3, the "@multiplex_group" description in the BD table makes it easy for the receiving side to recognize the multiplexing relationship between "Asset3" and "Asset4" as shown in Figure 19(c). That is, in the case of (E) MPU / HTTP distribution, it can be seen that "Asset3" and "Asset4" will each be distributed individually. Also, in the case of (A) multicast distribution, it can be seen that "Asset3" and "Asset4" will be multiplexed and distributed. Also, in the case of (D) MMTP / HTTP distribution, it can be seen that "Asset3" and "Asset4" will be multiplexed and distributed.

[0145] [Acquisition process of communication path components (assets) at the receiving terminal] Next, a description will be given of a process for acquiring a specific component (asset) of a communication path in the receiving terminal 200. The receiving terminal 200 selects one receivable delivery protocol from a plurality of pieces of delivery protocol information described in an MP table (MPT) acquired from a broadcast signal, and receives the specific component using this delivery protocol.

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

[0147] In step ST3, the receiving terminal 200 judges whether the component corresponding to the selected view should be acquired via a communication path or a broadcast path. If the component is to be acquired via a broadcast path, the receiving terminal 200 acquires the component from the broadcast signal. On the other hand, if the component is to be acquired via a communication path, the receiving terminal 200 proceeds to the process of step ST4.

[0148] In step ST4, the receiving terminal 200 judges whether or not multicast delivery (multicast option) can be selected. The receiving terminal 200 makes this judgment based on information on a plurality of delivery protocols described in the MP table (MPT). When multicast delivery can be selected, the receiving terminal 200 judges in step ST5 whether or not it is connected to the managed network. When it is connected to the managed network, the receiving terminal 200 selects multicast delivery as the delivery protocol, and proceeds to the processing of step ST9.

[0149] If the multicast option is not possible in step ST4, or if the managed network is not connected in step ST5, the receiving terminal 200 proceeds to step ST6. In step ST6, the receiving terminal 200 determines whether or not a delivery protocol (other option) other than multicast delivery can be selected. The receiving terminal 200 makes this determination based on information on multiple delivery protocols described in the MP table (MPT).

[0150] When the other delivery protocol can be selected, the receiving terminal 200 judges in step ST7 whether the other delivery protocol is compatible. When the other delivery protocol is compatible, the receiving terminal 200 selects the other delivery protocol as the delivery protocol and proceeds to the process of step ST9. In this case, when there are multiple delivery protocols that the receiving terminal 200 can support, the receiving terminal 200 selects the delivery protocol with the highest priority.

[0151] If it is not possible to select another delivery protocol in step ST6, or if it is not possible for the receiving terminal 200 to support the other delivery protocol in step ST7, the receiving terminal 200 ends the process with an error in step ST8.

[0152] In step ST9, the receiving terminal 200 judges whether the stream received by multicast distribution or another distribution protocol is a multiplexed stream including components other than the corresponding component. If it is a multiplexed stream, in step ST10, the receiving terminal 200 receives the stream from the acquisition source, and in step ST11, the processing ends.

[0153] If it is not a multiplexed stream, the receiving terminal 200 receives the stream from the acquisition source in step ST12, and then proceeds to the processing of step ST13. In this step ST13, the receiving terminal 200 judges whether or not reception of the view configuration component is completed. If it is not completed, the receiving terminal 200 returns to the processing of step ST4 and repeats the same processing as described above. On the other hand, if it is completed, the receiving terminal 200 ends the processing in step ST14.

[0154] Note that the above-described view selection / reception process assumes that the multiplexed stream includes all view composing components, for example, when the view composing components are made up of video and audio components.

[0155] [Reception sequence] Next, a description will be given of a receiving sequence in the receiving terminal 200. First, (A) a case where an asset distributed by a multicast distribution protocol is received will be described with reference to Fig. 22. In the case of multicast distribution, a multicast server (MC server) exists.

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

[0157] In this case, the receiving terminal 200 sends a JOIN message to the edge router, which includes the multicast address and port number included in the location information. When the JOIN message is sent, the multicast IP stream from the multicast server is sent to the receiving terminal 200 via the edge filter.

[0158] The receiving terminal 200 can extract the desired asset (component) from this multicast IP stream by filtering with the packet identifier (Packet_id) included in the location information. When leaving this receiving state, the receiving terminal 200 sends a LEAVE message with the multicast address and port number added to the edge router.

[0159] Next, referring to Fig. 23, a case of receiving an asset distributed using the (B) MMTP / UDP distribution protocol will be described. In the case of this MMTP / UDP distribution, the RTSP (Real Time Streaming Protocol) protocol is used. In the case of this MMTP / UDP distribution, an RTSP server and an MMTP / UDP server exist. These servers exist as separate devices or as the same device. In the illustrated example, the case where they exist as the same device is shown.

[0160] The receiving terminal 200 receives a broadcast signal and acquires an MP table (MPT). From this MP table, the receiving terminal 200 acquires location information of assets distributed using the MMTP / UDP distribution protocol. In this case, the location information is a URL, with "rtsp: / / ~.mmt" specified as the schema, and further with a parameter specifying UDP and a parameter specifying a packet identifier added by the query field. In this case, the receiving terminal 200 can identify that it is MMTP / UDP distribution by "rtsp" and "pr=udp".

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

[0162] After that, the receiving terminal 200 sends an RTSP request of "PLAY". In response, an "OK" response is sent from the target server. At the same time, a transmission stream is sent to the receiving terminal 200 from the MMTP / UDP server. The receiving terminal 200 can extract the target asset (component) from this stream by filtering with the packet identifier (Packet_id) included in the location information. When leaving this receiving state, the receiving terminal 200 sends an RTSP request of "TEARDOWN". In response, an "OK" response is sent from the server.

[0163] Next, referring to Fig. 24, a case where an asset distributed using the (C) MMTP / TCP distribution protocol is received will be described. This MMTP / TCP distribution also uses the RTSP (Real Time Streaming Protocol) protocol. In this MMTP / TCP distribution, an RTSP server and an MMTP / TCP server exist. These servers may exist as separate devices, or may exist as the same device. The illustrated example shows the case where they exist as the same device.

[0164] The receiving terminal 200 receives a broadcast signal and acquires an MP table (MPT). From this MP table, the receiving terminal 200 acquires location information of assets distributed using the MMTP / TCP distribution protocol. In this case, the location information is a URL, with "rtsp: / / ~.mmt" specified as the schema, and further with a parameter specifying TCP and a parameter specifying a packet identifier added by the query field. In this case, the receiving terminal 200 can identify that it is MMTP / TCP distribution by "rtsp" and "pr=tcp".

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

[0166] After that, the receiving terminal 200 sends an RTSP request of "PLAY". In response, an "OK" response is sent from the target server. At the same time, a transmission stream is sent from the MMTP / TCP server to the receiving terminal 200. The receiving terminal 200 can extract the target asset (component) from this stream by filtering with the packet identifier (Packet_id) included in the location information. When leaving this receiving state, the receiving terminal 200 sends an RTSP request of "TEARDOWN". In response, an "OK" response is sent from the server.

[0167] Next, referring to Fig. 25, (D) a case where an asset distributed by the MMTP / HTTP distribution protocol is received 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 distribution, an HTTP server exists.

[0168] The receiving terminal 200 receives a broadcast signal and acquires an MP table (MPT). From this MP table, the receiving terminal 200 acquires location information of assets distributed using the MMTP / HTTP distribution protocol. In this case, the location information is a URL, with "http: / / ~.mmt" specified as the schema, and further with a parameter specifying a packet identifier (packet_id) added by the query field. The receiving terminal 200 can identify that it is MMTP / HTTP distribution by "http" and "mmt".

[0169] The receiving terminal 200 sends an HTTP request to the HTTP server. At this time, the receiving terminal 200 inserts location information into the HTTP header. In this case, "http: / / ~.mmt" contained in the location information obtained from the MP table is inserted as the location information, and the parameter "pid=a" specifying the packet identifier and the parameter "msn=*" specifying the MPU sequence number are added by the query field. The parameter "msn=*" specifies "please send an MPU having the MPU sequence number for that timing."

[0170] This HTTP request is sent to the target HTTP server, and an MMTP stream including an MPU with the MPU sequence number (=10) at the time the HTTP request was sent is sent as an HTTP response from the HTTP server to the receiving terminal 200. The receiving terminal 200 extracts the target asset (component) from this MMTP stream by filtering with a packet identifier (Packet_id) included in the location information.

[0171] After or before completing reception of the MMTP stream, the receiving terminal 200 sends an HTTP request to the HTTP server requesting the MPU with the next MPU sequence number (=11). Then, the HTTP server sends an MMTP stream including the MPU with the next MPU sequence number (=11) to the receiving terminal 200 as an HTTP response. The receiving terminal 200 can extract the desired asset (component) from this MMTP stream by filtering with a packet identifier (Packet_id) included in the location information.

[0172] Similarly, the receiving terminal 200 sends an HTTP request to the HTTP server requesting the MPU with the next MPU sequence number, receives an MMTP stream including the MPU with the next MPU sequence number from the HTTP server as an HTTP response, and extracts the desired asset (component) from the MMTP stream.

[0173] Note that when making an HTTP request, the parameter "pid=a" included in the HTTP header specifies the type of asset, such as video or audio. Video and audio may be multiplexed into an MMTP stream. In that case, the MPU sequence number is determined as follows: video has its own MPU sequence number, and audio has its own MPU sequence number. Even if an MPU sequence number is specified, without the parameter "pid=a", it is not clear which asset (component) the MPU sequence number belongs to.

[0174] 26 shows the cut-out process for an MMTP / HTTP multiplexed stream. The HTTP server receives an HTTP request in which the parameter “pid=a” indicates a video and requests an MPU with an MPU sequence number of n, cuts out from the multiplexed stream the portion from when the MPU sequence number of the video switches from n-1 to n to when it switches from n to n+1, and sends it to the receiving terminal 200.

[0175] In this case, it may be necessary to extract 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 extracts the desired audio by filtering the MMTP stream extracted by the video MPU sequence number using the packet identifier (Packet_id) included in the location information.

[0176] Next, a case where an asset distributed by the (E) MPU / HTTP distribution protocol is received will be described with reference to Fig. 27. In the case of this MPU / HTTP distribution, the HTTP (Hyper Text Transfer Protocol) protocol is used. In the case of this MPU / HTTP distribution, an HTTP server exists.

[0177] The receiving terminal 200 receives a broadcast signal and acquires an MP table (MPT). From this MP table, the receiving terminal 200 acquires location information of assets distributed using the MPU / HTTP distribution protocol. In this case, the location information 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".

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

[0179] This HTTP request is sent to the target HTTP server, and the HTTP server sends to the receiving terminal 200, as an HTTP response, an MPU having the MPU sequence number (=10) at the time the HTTP request was sent.

[0180] After or before the reception of the MPU is completed, the receiving terminal 200 sends an HTTP request to the HTTP server requesting the MPU with the next MPU sequence number (=11). The HTTP server then sends the MPU with the next MPU sequence number (=11) to the receiving terminal 200 as an HTTP response.

[0181] Thereafter, in a similar manner, the receiving terminal 200 sends an HTTP request requesting the MPU with the next MPU sequence number to the HTTP server, and receives the MPU with the next MPU sequence number from the HTTP server as an HTTP response.

[0182] [Broadcast transmission system configuration] 28 shows an example of the configuration of a broadcast transmission system 100. This broadcast transmission system 100 has a signal transmission unit 101, a video encoder 102, an audio encoder 103, and a signaling generation unit 104. This broadcast transmission system 100 also has 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.

[0183] The signal sending unit 101 is, for example, a TV station studio or a recording and playback device such as a VTR, and sends video and audio stream data to each encoder. The video encoder 102 encodes the video data sent from the signal sending unit 101, packetizes it, and sends IP packets including video MMT packets to the IP service multiplexer 106-1. The audio encoder 103 encodes the audio data sent from the signal sending unit 101, packetizes it, and sends IP packets including audio MMT packets to the IP service multiplexer 106-1.

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

[0185] The IP service multiplexer 106-1 performs time division multiplexing of the IP packets sent from each encoder. At this time, the IP service multiplexer 106-1 adds a TLV header to each IP packet to make it a TLV packet. The IP service multiplexer 106-1 constitutes one channel portion to be placed in one transponder. The IP service multiplexers 106-2 to 106-N have the same function as the IP service multiplexer 106-1, and constitute the other channel portions to be placed in that one transponder.

[0186] The TLV signaling generator 105 generates signaling information and generates a TLV packet in which the signaling information is placed in the payload section. 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 transmits it to an RF transmission path.

[0187] The operation of the broadcast transmission system 100 shown in Fig. 28 will be briefly described. Video data transmitted from the signal transmission unit 101 is supplied to the video encoder 102. In this video encoder 102, the video data is encoded and further packetized to generate IP packets including video MMT packets. These IP packets are sent to the IP service multiplexer 106-1. The same process is also performed on the audio data transmitted from the signal transmission unit 101. Then, IP packets including audio MMT packets generated by the audio encoder 103 are sent to the IP service multiplexer 106-1.

[0188] In addition, the signaling generation unit 104 generates a signaling message, and generates an IP packet including an MMT packet in which the signaling message is placed in the payload section. This IP packet is sent to the IP service multiplexer 106-1. At this time, an MP table (MPT) is placed in the PA message.

[0189] The IP service multiplexer 106-1 performs time division multiplexing of the IP packets sent from each encoder and the signaling generator 104. At this time, a TLV header is added to each IP packet to form a TLV packet. This IP service multiplexer 106-1 processes one channel portion to be put into one transponder, and the IP service multiplexers 106-2 to 106-N similarly process the other channel portions to be put into that one transponder.

[0190] The TLV packets obtained by the IP service multiplexers 106-1 to 106-N are sent to a TLV multiplexer 107. This TLV multiplexer 107 also receives a TLV packet from a TLV signaling generation unit 105, in which signaling information is placed in the payload portion.

[0191] In the TLV multiplexer 107, the TLV packets generated in the IP service multiplexers 106-1 to 106-N and the TLV signaling generating unit 105 are multiplexed to generate a broadcast stream. This broadcast stream is sent to the modulation / transmission unit 108. In the modulation / transmission unit 108, the broadcast stream is subjected to RF modulation processing, and the RF modulated signal is sent to an RF transmission path as a broadcast signal.

[0192] [Receiving device configuration] 29 shows an example of the configuration of a receiving terminal 200. This receiving terminal 200 has a CPU 201, a tuner / demodulator unit 202, a network interface unit 203, and a demultiplexer 204. This receiving terminal 200 also has a video decoder 205 and an audio decoder 206.

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

[0194] The demultiplexer 204 performs demultiplexing and depacketizing processes on the broadcast stream obtained by the tuner / demodulator unit 202 and the transmission stream obtained by the network interface unit 203, and outputs signaling information, video, audio encoded data, etc.

[0195] 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.

[0196] The operation of receiving terminal 200 shown in Fig. 29 will be briefly described. In tuner / demodulation unit 202, an RF modulated signal transmitted through an RF transmission path is received and demodulated to obtain a broadcast stream. This broadcast stream is sent to demultiplexer 204. In addition, in network interface unit 203, a transmission stream of a service distributed from distribution server 300 via communication network 400 is received and sent to demultiplexer 204.

[0197] The demultiplexer 204 performs demultiplexing and depacketizing processes on the broadcast stream from the tuner / demodulator 202 and the transmission stream from the network interface 203, and extracts signaling information, video, audio encoded data, and the like.

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

[0199] The encoded video data extracted by the demultiplexer 204 is sent to a video decoder 205 where it is decoded to obtain baseband video data, and the encoded audio data extracted by the demultiplexer 204 is sent to an audio decoder 206 where it is decoded to obtain baseband audio data for audio output.

[0200] As described above, in the broadcasting and communication hybrid system 10 shown in Fig. 1, information on a plurality of delivery protocols, each of which includes at least location information and protocol identification information, or acquisition information for acquiring information on the plurality of delivery protocols, is inserted into the MP table for the assets (components) of the communication path. Therefore, the receiving side can receive the components satisfactorily using a delivery protocol that matches its own delivery network environment.

[0201] <2. Modifications> In the above embodiment, an example in which the transmission packet is an MMT packet has been described. However, the present technology is not limited to this, and it goes without saying that the present technology can be applied to cases in which other similar transmission packets are handled.

[0202] The present technology can also be configured as follows. (1) a transmission stream generating unit that generates a transmission stream by time-division multiplexing a first transmission packet including a predetermined component and a second transmission packet including information about the predetermined component; a transmitting unit that transmits the transmission stream through a predetermined transmission path; and an information insertion unit that inserts, into the second transmission packet, information on a plurality of delivery protocols, each of which includes at least location information and protocol identification information for acquiring the specific component, in association with the specific component to be acquired through the communication path, or acquisition information for acquiring the information on the plurality of delivery protocols. Transmitting device. (2) The multiple delivery protocols are two or more delivery protocols selected from the group consisting of multicast delivery, MMTP / UDP delivery, MMTP / TCP delivery, MMTP / HTTP delivery, and MPU / HTTP delivery. The transmitting device according to (1) above. (3) When the protocol identification information indicates that the transmission is the MMTP / UDP transmission, the transmission protocol information includes a parameter that specifies UDP in addition to the URL. The transmitting device according to (2) above. (4) When the protocol identification information indicates that the delivery is the MMTP / TCP delivery, the delivery protocol information includes a parameter that specifies TCP in addition to the URL. The transmitting device according to (2) above. (5) The information of the above delivery protocol further includes packet identification information. A transmitting device according to any one of (1) to (4). (6) The above transmission packet is an MMT packet. A transmitting device according to any one of (1) to (5). (7) The above-mentioned specified transmission path is a broadcast transmission path. A transmitting device according to any one of (1) to (6). (8) A plurality of pieces of information about the specific component are arranged in the second packet, and information about one of the plurality of delivery protocols is inserted into each of the plurality of pieces of information arranged. A transmitting device according to any one of (1) to (7). (9) In the second packet, one piece of information about the specific component is placed, and information about the plurality of delivery protocols is inserted into the placed piece of information. A transmitting device according to any one of (1) to (7). (10) In the second packet, one piece of information on the specific component is arranged, and acquisition information for acquiring information on the plurality of delivery protocols is inserted into the arranged piece of information. A transmitting device according to any one of (1) to (7). (11) Information on other components that are multiplexed with the specific component and distributed is added to each of the information on the plurality of distribution protocols. A transmitting device according to any one of (1) to (10). (12) Among the above-mentioned multiple delivery protocol information, managed network information is added to the multicast delivery protocol information. A transmitting device according to any one of (1) to (11). (13) a transmission stream generating step of generating a transmission stream by time-division multiplexing a first transmission packet including a predetermined component and a second transmission packet including information about the predetermined component; a transmitting step of transmitting the transmission stream through a predetermined transmission path by a transmitting unit; and an information insertion step of inserting, into the second transmission packet, information on a plurality of delivery protocols, each of which includes at least location information and protocol identification information for acquiring the specific component, in association with the specific component to be acquired through the communication path, or acquisition information for acquiring the information on the plurality of delivery protocols. Transmission method. (14) A receiving unit that receives a transmission stream obtained by time-division multiplexing a first transmission packet including a predetermined component and a second transmission packet including information related to the predetermined component through a predetermined transmission path, The second transmission packet is inserted with information on a plurality of delivery protocols, each of which includes at least location information and protocol identification information, for acquiring a specific component to be acquired through a communication path, or acquisition information for acquiring the information on the plurality of delivery protocols; a communication unit that selects one receivable delivery protocol from the plurality of pieces of delivery protocol information, and receives a transmission stream having a third transmission packet including the specific component in the selected delivery protocol through a network. Receiving device. (15) The information of the above delivery protocol further includes packet identification information; The communication unit extracts the third transmission packet from the received transmission stream having the third packet based on the packet identification information. The receiving device according to (14) above. (16) The above transmission packet is an MMT packet. The receiving device according to (14) or (15) above. (17) The above-mentioned specified transmission path is a broadcast transmission path. A receiving device according to any one of (14) to (16). (18) A receiving step of receiving, by a receiving unit, a transmission stream obtained by time-division multiplexing a first transmission packet including a predetermined component and a second transmission packet including information about the predetermined component through a predetermined transmission path, The second transmission packet is inserted with information on a plurality of delivery protocols, each of which includes at least location information and protocol identification information, for acquiring a specific component to be acquired through a communication path, or acquisition information for acquiring the information on the plurality of delivery protocols; The method further includes a communication step of selecting one receivable delivery protocol from the plurality of delivery protocol information, and receiving, via a network, a transmission stream having a third transmission packet including the specific component in the selected delivery protocol. Receiving method. (19) A receiving unit that receives a transmission stream obtained by time-division multiplexing a first transmission packet including a predetermined component and a second transmission packet including information about the predetermined component through a predetermined transmission path, The second transmission packet is inserted with information on a plurality of delivery protocols, each of which includes at least location information and protocol identification information, for acquiring a specific component to be acquired through a communication path, or acquisition information for acquiring the information on the plurality of delivery protocols; The apparatus further includes a processing unit for processing the transmission stream received by the receiving unit. Receiving device. [Explanation of symbols]

[0203] 10. Broadcasting and communication hybrid system 100 Broadcast transmission system 101 Signal sending unit 102 Video Encoder 103 Audio Encoder 104 Signaling generation unit 105 TLV signaling generation unit 106-1~106-N···IP Service Multiplexer 107···TLV·Multiplexer 108 Modulation / Transmission Unit 200: Receiving terminal 201···CPU 202 Tuner / demodulator 203 Network interface unit 204 Demultiplexer 205...Video decoder 206 Audio Decoder 207···CPU bus 300...Distribution server 400 Communication network

Claims

1. a transmission stream generating unit that generates a transmission stream by multiplexing a first transmission packet including a predetermined component and a second transmission packet including a table storing information about the predetermined component; a transmitting unit that transmits the transmission stream through a predetermined transmission path; An information insertion unit that inserts information on a delivery protocol including protocol identification information and location information for acquiring a specific component, in association with the specific component to be acquired via the communication path, into the table. Transmitting device.

2. The delivery protocol is a delivery protocol selected from the group consisting of multicast delivery, MMTP / UDP delivery, MMTP / TCP delivery, MMTP / HTTP delivery, and MPU / HTTP delivery. The transmitting device according to claim 1 .

3. When the protocol identification information indicates the MMTP / UDP delivery, the delivery protocol information includes a parameter that specifies UDP. The transmitting device according to claim 2.

4. When the protocol identification information indicates the MMTP / TCP delivery, the delivery protocol information includes a parameter that specifies TCP. The transmitting device according to claim 2.

5. The location information further includes packet identification information. The transmitting device according to claim 1 .

6. The first transmission packet and the second transmission packet are MMT packets. The transmitting device according to claim 1 .

7. The predetermined transmission path is a broadcast transmission path. The transmitting device according to claim 1 .

8. A plurality of pieces of information about the specific component are arranged in the table, and information about the delivery protocol indicating at least one of a plurality of delivery protocols is inserted into each of the arranged pieces of information. The transmitting device according to claim 1 .

9. In the table, one piece of information about the specific component is arranged, and a plurality of pieces of information about the delivery protocol corresponding to the arranged piece of information are inserted. The transmitting device according to claim 1 .

10. When the protocol identification information indicates that the delivery is performed using HTTP, URL information for acquiring the specific component is inserted into the location information; The above delivery protocol information includes a parameter that specifies HTTP. The transmitting device according to claim 1 .

11. The information of the delivery protocol is added with information of other components that are multiplexed with the specific component and delivered. The transmitting device according to claim 1 .

12. Among the above-mentioned delivery protocol information, the multicast delivery protocol information includes information about available networks. The transmitting device according to claim 1 .

13. a transmission stream generating step of generating a transmission stream by multiplexing a first transmission packet including a predetermined component and a second transmission packet including a table storing information about the predetermined component; a transmitting step of transmitting the transmission stream through a predetermined transmission path by a transmitting unit; An information insertion step of inserting information of a delivery protocol including protocol identification information and location information for acquiring a specific component to be acquired via a communication path into the table in association with the specific component. Transmission method.

14. a receiving unit that receives a transmission stream obtained by multiplexing a first transmission packet including a predetermined component and a second transmission packet including a table that stores information about the predetermined component through a predetermined transmission path; In the table, information on a delivery protocol including protocol identification information and location information for acquiring a specific component to be acquired via a communication path are inserted in association with the specific component, and The communication unit further includes: a communication unit that selects one receivable delivery protocol from the delivery protocol information; and receives, via a network, a transmission stream having a third transmission packet including the specific component in the selected delivery protocol, using the location information. Receiving device.

15. The location information further includes packet identification information; The communication unit extracts the third transmission packet from the received transmission stream having the third transmission packet based on the packet identification information.

15. A receiving device according to claim 14.

16. The first transmission packet and the second transmission packet are MMT packets.

15. A receiving device according to claim 14.

17. The predetermined transmission path is a broadcast transmission path.

15. A receiving device according to claim 14.

18. a receiving step of receiving, by a receiving unit, a transmission stream in which a first transmission packet including a predetermined component and a second transmission packet including a table storing information about the predetermined component are multiplexed, through a predetermined transmission path; In the table, information on a delivery protocol including protocol identification information and location information for acquiring a specific component to be acquired via a communication path are inserted in association with the specific component, and The method further includes a communication step of selecting one receivable delivery protocol from the information of the delivery protocol, and receiving a transmission stream having a third transmission packet including the specific component in the selected delivery protocol through a network using the location information. Receiving method.

Images