JP2018201219A - Control message generation device, distribution system, receiving device, and programs for them - Google Patents

Abstract

To provide a control message generation device capable of suppressing an expected value of a hop number required to when reception becomes possible.SOLUTION: A control message generation device comprises: a table generation part that generates a first table including reference information to each of assets configuring a first package, and a second table including reference information to each of assets configuring a second package; a package list table generation part that generates a package list table including reference information to the second table; and a control message generation part that generates a first control message including the first table and the package list table, and a second control message including the second table.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a control message generation device, a distribution system, a reception device, and a program thereof.

  In current digital television broadcasting such as digital terrestrial television broadcasting, MPEG (Moving Picture Experts Group) 2-TS (Transport Stream) standardized as ISO / IEC 13818-1 is used. In these digital television broadcasts, in addition to video and audio streams, tables called PAT (Program Association Table) and PMT (Program Map Table) are periodically transmitted (for example, Non-Patent Document 1). 2).

  The PMT is a table prepared for each program, and stores a PID that is reference information for a video stream and an audio stream constituting the program. The PAT is a table prepared only in the MPEG2-TS, and stores PID that is reference information for each PMT transmitted by the MPEG2-TS.

  When receiving a program, a receiving apparatus that receives digital television broadcast first acquires a PAT from MPEG2-TS. By referring to this PAT, the PID of the PMT of the program to be received can be known, so the receiving apparatus acquires the PMT of the program to be received from MPEG2-TS. Then, referring to this PMT, the PID of the video and audio stream of the received program can be known, so the receiving apparatus acquires the video and audio stream of the received program from the MPEG2-TS, and displays the video and audio. Is output.

“Video coding, audio coding and multiplexing system in digital broadcasting”, ARIB STD-B32 2.8 edition, Japan Radio Industry Association, December 18, 2012 “Program Sequence Information Used for Digital Broadcasting”, ARIB STD-B10 4.8 Edition, Japan Radio Industry Association, April 26, 2010

  However, in a system using MPEG2-TS, such as the above-mentioned digital television broadcast, as described above, until the receiving device can receive a video or audio stream constituting a program, There is a problem that two hops of acquiring the PMT are always necessary. Since two hops are required, the expected value of the time it takes for the video or audio stream to be received after the program to be received is specified is the period in which the PAT is transmitted and the period in which the PMT is transmitted. The sum of Therefore, if the time is to be shortened, the transmission period of PAT and PMT is shortened, and the band of video and audio is compressed. Also, if you try to reduce the pressure on the video and audio bandwidth, the PAT or PMT transmission cycle will be lengthened, and the time it takes to receive the video or audio stream after the program to be received is specified Will become longer.

  The present invention has been made in view of such circumstances, and provides a control message generation device, a distribution system, a reception device, and a program that can suppress the expected value of the number of hops until reception becomes possible.

(1) The present invention has been made to solve the above-described problems, and one correspondence of the present invention is that a first table including reference information for each asset constituting the first package, and a second table A table generation unit that generates a second table that includes reference information for each asset that constitutes a package; a package list table generation unit that generates a package list table that includes reference information for the second table; A control message generation unit comprising: a control message generation unit that generates a first control message including a first table and the package list table; and a second control message including the second table. Device.

(2) According to another aspect of the present invention, there is provided the control message generation device according to (1), wherein the reference information to the second table includes the second table. It is a packet ID of a packet storing a message.

(3) According to another aspect of the present invention, a first table that includes reference information for each asset that configures the first package, and a first table that includes reference information for each asset that configures the second package. A control message generating device that generates a first control message including a package list table including reference information to the second table, and a second control message including the second table, and the first control message. And a distribution device that distributes the second control message using a data flow.

(4) According to another aspect of the present invention, a first table including reference information for each asset constituting the first package and a second table including reference information for each asset constituting the second package. A receiving apparatus for receiving a data flow including a first control message including a package list table including reference information to the table and a second control message including the second table, wherein a desired package is received. A receiving unit that receives the data flow, a separating unit that separates the first control message from the data flow, and the first control message that is included in the first control message. 1, when the first package matches the desired package, the separation unit is instructed to separate the first package. A receiving apparatus characterized by comprising a control message processor for.

(5) According to another aspect of the present invention, there is provided the receiving device according to (4), wherein the control message processing unit refers to the first table included in the first control message. When the first package does not match the desired package, the package list table included in the first control message is referred to the second table corresponding to the desired package. The reference information is acquired, and using the acquired reference information, the separation unit is instructed to separate the second control message including the second table corresponding to the desired package.

(6) According to another aspect of the present invention, the computer includes a first table including reference information for each asset constituting the first package, and reference information for each asset constituting the second package. A table generation unit that generates a second table including the package list table generation unit that generates a package list table including reference information to the second table, a first table including the first table and the package list table A program for causing a control message generator to function as a control message generator that generates one control message and a second control message including the second table.

(7) According to another aspect of the present invention, a first table that includes reference information for each asset that constitutes the first package and a second table that includes reference information for each asset that constitutes the second package. A receiving device computer that receives a data flow that includes a first control message including a package list table including reference information to the table and a second control message including the second table, a desired package; A designation obtaining unit for obtaining information designating, a receiving unit for receiving the data flow, a separation unit for separating the first control message from the data flow, and the first table included in the first control message Referring to FIG. 5, when the first package matches the desired package, the separation unit is instructed to separate the first package. Is a program for functioning as a control message processor for.

  According to this invention, the expected value of the number of hops until reception becomes possible can be suppressed.

1 is a schematic block diagram illustrating a configuration of a distribution system 10 according to an embodiment of the present invention. It is a schematic block diagram which shows the structure of the control message production | generation apparatus 11 in the embodiment. It is a schematic block diagram which shows the structure of the receiver 17 in the same embodiment. It is a conceptual diagram which shows the structure of the IP data flow which the delivery apparatus 16 in the embodiment delivers. It is a table | surface which shows the data structure of PA message in the same embodiment. It is a table | surface (the 1) which shows the data structure of MP table in the same embodiment. It is a table | surface (the 2) which shows the data structure of MP table in the same embodiment. It is a table | surface (the 3) which shows the data structure of MP table in the same embodiment. It is a table | surface (the 1) which shows the data structure of the reference information in the embodiment. It is a table | surface (the 2) which shows the data structure of the reference information in the embodiment. It is a table | surface (the 3) which shows the data structure of the reference information in the embodiment. It is a table | surface (the 1) which shows the data structure of the package list table in the embodiment. It is a table | surface (the 2) which shows the data structure of the package list table in the embodiment. 7 is a flowchart illustrating operations of a designation acquisition unit 72, a reception control unit 73, and a control message processing unit 74 in the same embodiment. It is a conceptual diagram which shows the structure of the IP data flow which the delivery apparatus 16 in the modification 1 of the embodiment delivers. It is a table | surface (the 1) which shows the data structure of MP table in the modification 2 of the embodiment. It is a table | surface (the 2) which shows the data structure of MP table in the modification 2 of the embodiment. It is a table | surface (the 3) which shows the data structure of MP table in the modification 2 of the embodiment. It is a table | surface (the 1) which shows the data structure of the reference information in the modification 2 of the embodiment. It is a table | surface (the 2) which shows the data structure of the reference information in the modification 2 of the embodiment. It is a table | surface (the 1) which shows the data structure of the package list table in the modification 2 of the embodiment. It is a table | surface (the 2) which shows the data structure of the package list table in the modification 2 of the embodiment.

  Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a schematic block diagram showing a configuration of a distribution system 10 according to an embodiment of the present invention. The distribution system 10 includes a control message generation device 11, a plurality of video transmission devices 12, a plurality of audio transmission devices 13, a plurality of data transmission devices 14, a multiplexing device 15, a distribution device 16, a reception device 17, and an output device 18. Composed. The distribution system 10 distributes content to the receiving device 17 using the IP data flow. The IP data flow is, for example, a multicast flow using UDP / IP, and is determined by a source IP address, a destination IP address, and a destination port number. The IP data flow may be transmitted via a bidirectional transmission path such as the Internet, or may be transmitted via a one-way transmission path such as terrestrial digital broadcasting or satellite digital broadcasting.

  The control message generator 11 generates an MMT (MPEG Media Transport) control message (Signaling Message) and inputs it to the multiplexer 15. In the present embodiment, the control message generated by the control message generator 11 is a PA message (Package Access message) including an MP table (MMT Package table) and a package list table, and a PA message including only the MP table. . The MP table stores the package ID of the target package and the reference information (MMT_general_location_info) to the assets constituting the package. The package list table stores reference information (packet ID and the like) to the MP table of each package included in the data flow transmitting the package list table. In the present embodiment, the package list table does not include reference information to the MP table included in the PA message together with the package list table, but may include it.

  The PA message is a kind of control message (Signaling Message) in MMT. Assets are media such as video streams, audio streams, data streams, hypertext files, and image files. A package is a collection of one or more assets that make up content. For example, assets constituting a movie package are a video stream, an audio stream, and a subtitle data stream. When the video stream includes a low-resolution video for mobile use and a high-resolution video for stationary use, both are included in the package. Note that some of the assets constituting the package may be distributed from a device different from the distribution device 16 using a transmission path different from the transmission path between the distribution device 16 and the reception device 17. Details of the MP table, package list table, and PA message will be described later.

  The video transmission device 12 generates a video stream among the assets constituting the content and inputs the video stream to the multiplexing device 15. The audio transmission device 13 generates an audio stream among the assets constituting the content and inputs the audio stream to the multiplexing device 15. The data transmission device 14 generates a data stream among the assets constituting the content and inputs the data stream to the multiplexing device 15. The data stream is, for example, information displayed accompanying a video, subtitles superimposed on the video, or the like.

  The multiplexer 15 stores the input control message, video stream, audio stream, and data stream in MMT packets, and multiplexes the MMT packets in time series. The multiplexing device 15 sets the packet ID of the MMT packet to a value set in advance for each stored stream or control message. In particular, the multiplexing device 15 sets the packet ID of the MMT packet storing the PA message storing both the MP table and the package list table to “0”. The distribution device 16 stores the MMT packet multiplexed by the multiplexing device 15 in an IP packet, generates an IP data flow, and distributes it.

  The receiving device 17 receives the IP data flow distributed by the distribution device 16. The receiving device 17 generates a decoded signal of the content included in the received IP data flow and inputs it to the output device 18. The output device 18 includes, for example, a liquid crystal display and a speaker, displays the video represented by the input decoded signal on the liquid crystal display, and outputs the sound represented by the decoded signal from the speaker.

  FIG. 2 is a schematic block diagram showing the configuration of the control message generator 11. The control message generator 11 includes an MP table generator 21, a package list table generator 22, and a PA message generator 23. The MP table generation unit 21 generates an MP table for each package transmitted by the distribution device 16. The package list table generation unit 22 generates a package list table including a package ID corresponding to each MP table generated by the MP table generation unit 21 and a packet ID of an MMT packet storing the MP table. The package list table may not include the package ID and packet ID of the MP table stored in the same PA message as the package list table.

  The PA message generator 23 (control message generator) generates a PA message storing the MP table generated by the MP table generator 21. However, the PA message generator 23 also stores the package list table generated by the package list table generator 22 in the PA message storing the specific MP table. The PA message generation unit 23 inputs the generated PA message to the multiplexing device 15.

  FIG. 3 is a schematic block diagram showing the configuration of the receiving device 17. The reception device 17 includes a reception unit 70, a separation unit 71, a designation acquisition unit 72, a reception control unit 73, a control message processing unit 74, a video decoding unit 75, an audio decoding unit 76, a data rendering unit 77, a video synthesis unit 78, an audio A composition unit 79 is included.

  The receiving unit 70 receives the IP data flow distributed by the distribution device 16 in accordance with an instruction from the reception control determining unit 73. The separating unit 71 separates the PA message included in the MMT packet having the packet ID “0” from the IP data flow received by the receiving unit 70 and inputs the PA message to the control message processing unit 74. Further, the separation unit 71 separates the control message designated by the control message processing unit 74, the video stream, the audio stream, and the data stream from the IP data flow received by the reception unit 70. The separation unit 71 inputs the separated control message to the control message processing unit 74. The separating unit 71 inputs the separated video stream to the video decoding unit 75 and inputs the separated audio stream to the audio decoding unit 76. The separation unit 71 inputs the separated data stream to the data rendering unit 77.

  The designation acquisition unit 72 acquires designation of a service to be received, which is input by a user using an input device such as a remote controller. The designation of the service is performed, for example, when the user inputs a service ID (service identifier). The reception control unit 73 instructs the reception unit 70 to receive the IP data flow that is transmitting the service acquired by the designation acquisition unit 72. In addition, the reception control unit 73 notifies the control message processing unit 74 of the package ID of the service acquired by the designation acquisition unit 72. For example, the lower 16 bits of the package ID match the service ID.

  The control message processing unit 74 acquires the MP table of the package ID notified from the reception control unit 73 from the control message separated by the separation unit 71. The control message processing unit 74 refers to the acquired MP table, determines a video stream, an audio stream, and a data stream to be played back, and designates the determined stream to the separation unit 71. Details of the MP ID acquisition method of the package ID notified from the reception control unit 73 will be described later.

  The video decoding unit 75 decodes the video stream input from the separation unit 71 and generates a video signal. The audio decoding unit 76 decodes the audio stream input from the separation unit 71 and generates an audio signal. The data rendering unit 77 renders the data stream input from the separation unit 71 to generate a video signal and an audio signal. The data rendering unit 77 also generates a signal that specifies a method for combining the generated video signal and the video signal generated by the video decoding unit 75 by rendering the data stream.

  For example, if the data stream is a caption data stream, the synthesis method specified by the signal generated by the data rendering unit 77 is the video generated by the data rendering unit 77 to the video represented by the video signal generated by the video decoding unit 75. This is a method of superimposing the subtitles represented by the signal. If the data stream displays information on the left outer side and the lower outer side of the video represented by the video signal generated by the video decoding unit 75, the combining method specified by the signal generated by the data rendering unit 77 is Then, the video represented by the video signal generated by the video decoding unit 75 is reduced, and the video represented by the video signal generated by the data rendering unit 77 is arranged on the left outer side and the lower outer side of the reduced video.

  The video synthesizing unit 78 synthesizes the video signal generated by the video decoding unit 75 and the video signal generated by the data rendering unit 77 according to a signal designating the synthesis method generated by the data rendering unit 77, and outputs the output device 18. A video signal of a video to be displayed on the screen is generated. The voice synthesis unit 79 superimposes the voice signal generated by the voice decoding unit 76 and the voice signal generated by the data rendering unit 77 to generate a voice signal of the voice to be output to the output device 18.

  FIG. 4 is a conceptual diagram showing a configuration of an IP data flow distributed by the distribution device 16. In the example shown in FIG. 4, a plurality of packages are transmitted by one IP data flow DF. For example, if the transmission medium is a broadcast wave, the IP data flow DF is transmitted by a TLV (Type Length Value) stream. If the transmission medium is a LAN (Local Area Network), the IP data flow DF is transmitted by an IP packet.

  The IP data flow DF includes PA messages PA1, PA2, video streams V1, V2, audio streams A1, A2, and data streams D1, D2. Among these, the video stream V1, the audio stream A1, and the data stream D1 constitute the first package. The video stream V2, the audio stream A2, and the data stream D2 form a second package.

  The PA message PA1 stores an MP table MP1 of the first package and a package list table PL1. The MP table MP1 stores the package ID of the first package and the packet ID of the MMT packet that transmits each of the video stream V1, the audio stream A1, and the data stream D1, which are assets constituting the package.

  The package list table PL1 is a packet ID of an MMT packet that transmits each PA message (for example, PA message PA2) that stores an MP table (for example, the MP table MP2) of the package transmitted by the IP data flow DF. Is stored. Each of the MP tables (for example, the MP table MP2) of the second and subsequent packages includes the package ID of the package and the assets (for example, the video stream V2, the audio stream A2, and the data stream D2) that constitute the package. Is stored. The packet ID of the MMT packet that transmits the packet is stored.

  Since the PA message PA1 is stored in an MMT packet having a predetermined packet ID (for example, “0”), the separating unit 71 can separate the PA message PA1 from the IP data flow DF without reference information. . Since the IP data flow DF has such a configuration, when receiving the first package, the receiving device 17 extracts the PA message PA1 from the MMT packet having the packet ID “0”, and Further, by extracting the MP table MP1 from the PA message PA1, the configuration of the first package can be grasped and received.

  Further, when receiving the second package, the receiving device 17 extracts the PA message PA1 from the MMT packet having the packet ID “0”, and further extracts the package list table PL1 from the PA message PA1. Thus, the packet ID of the MMT packet storing the MP table MP2 of the package is obtained. The receiving device 17 can grasp and receive the configuration of the second package by extracting the PA message PA2 from the MMT packet of this packet ID and further extracting the MP table MP2 from the PA message PA2. . When receiving the third and subsequent packages, the receiving device 17 can grasp and receive the configuration of the package in the same manner as the second package.

  FIG. 5 is a table showing the data structure of the PA message. The data structure of the PA message in this embodiment conforms to ISO / IEC 23008-1. In the table, no. Is a column indicating the serial number of the row in the table. The data structure is a column indicating the data structure of the PA message. The number of bits is a column indicating the number of bits of the data structure. The bit string notation is a column indicating the data format of the data structure of the number of bits. Uimsbf in bit string notation is an abbreviation for unsigned integer most significant bit first, and an unsigned integer and the most significant bit mean the head.

  In FIG. 1 “PA_message () {” will be referred to as “No. Up to 18 “}” represents the data structure of the PA message. No. placed at the top of the message. 2, “message_id” is a 16-bit area indicating the ID (Identifier) of the PA message. Next No. “Version” of 3 is an 8-bit area indicating the version number of the PA message. Next No. “Length” of 4 is a 32-bit area indicating the number of bytes of the PA message after the area. The following No. “Extension {” in FIG. Up to 12 indicates a PA message-specific extension to a data structure common to control messages. Next No. 6 “number_of_tables” is an 8-bit area indicating the number N of tables stored in the PA message.

  The following No. 7, “for (i = 0; i <N; i ++) {” is hereinafter referred to as “}”. 11 is repeated N times, that is, the number of stored tables. Next No. is arranged. 8 "table_id" is an 8-bit area indicating the ID of the table stored in the PA message.

  Next No. is arranged. “Table_version” of No. 9 is the immediately preceding No. This is an 8-bit area indicating the version number of the table indicated by the table ID 8. Next No. “Table_length” of No. 10 is the last No. This is an 8-bit area indicating the length of the table indicated by the table ID 8. The following No. No. 11 “}” indicates no. 7 corresponds to “{” and No. 12 “}” indicates no. 5 corresponds to “{”.

  The following No. 13 “message_payload {” will be referred to as “No. 17 indicates that the payload of the PA message is stored. The following No. 14, “for (i = 0; i <N1; i ++) {” is hereinafter referred to as “}”. 16 is repeated N times, that is, the number of stored tables. The following No. “Table ()” 15 is an area in which a table is arranged. The arrangement order of the tables is No. This is the same as the arrangement order of 8 “table_id”. The following No. No. 16 “}” indicates no. 14 corresponding to “{”, No. 17 “}” indicates no. 13 corresponds to “{” and No. 18 “}” indicates no. This corresponds to “{” of 1.

  6 to 8 are tables showing the data structure of the MP table. The data structure of the MP table in this embodiment conforms to ISO / IEC 23008-1. In the table, no. Is a column indicating the serial number of the row in the table. The data structure is a column indicating the data structure of the MP table. The number of bits is a column indicating the number of bits of the data structure. The value is a column indicating the value taken by the data structure of the number of bits. The bit string notation is a column indicating the data format of the data structure of the number of bits. Uimsbf in bit string notation is an abbreviation for unsigned integer most significant bit first, and an unsigned integer and the most significant bit mean the head. The bit string notation bslbf is an abbreviation for bit string left bit first, and the bit string and the left bit mean the head.

  In FIG. No. 1 “MPT () {” will be referred to as “No. Up to 60 “}” represents the data structure of the MP table. No. placed at the top of the table. “Table_id” of 2 is an 8-bit area indicating the ID of the MP table. In the present embodiment, “0x40” representing Complete MPT is used as the MP table ID. Next No. is arranged. “Version” of 3 is an 8-bit area indicating the version number of the MP table. Next No. “Length” of 4 is a 16-bit area indicating the number of bytes of the MP table after the area.

Next No. “Reserved” of 5 is a 6-bit reserved area.
Next No. 6 "MPT_mode" is a 2-bit area indicating a processing mode when the MP table is a subset. Although conforming to ISO / IEC 23008-1, the detailed description is omitted. The following No. 7 “If (table_id == SUBSET_0_MPT_TABLE_ID) {” is “No. 2 when the value of “table_id” is “SUBSET_0_MPT_TABLE_ID”. Indicates that up to 20 areas are arranged.

  The following No. “MMT_package_id {” in FIG. 13 indicates that the area up to “}” is an area related to the package ID. Next No. “MMT_package_id_length” of 9 is an 8-bit area indicating the number of bytes N1 of the package ID. The following No. No. 10 “for (i = 0; i <N1; i ++) {” will be referred to as “No. This indicates that the area up to 12 is repeated N1 times, that is, the number of bytes of the package ID. Next No. is arranged. 11 "MMT_package_id_byte" is an area indicating 1 byte in the package ID. The following No. No. 12 “}” indicates no. 10 corresponds to “{” and “}” in No. 13 8 corresponds to “{”.

  The following No. 14 “MPT_descriptors {” is hereinafter referred to as “No. It indicates that up to 19 “}” is an area related to a descriptor (descriptor) related to the MP table. Next No. is arranged. Fifteen “MPT_descriptors_length” is a 16-bit area indicating the total length N2 of the descriptors that are arranged. The following No. 16 “for (i = 0; i <N2; i ++) {” is referred to as “No. Indicates that the area up to 18 is repeated N2 times, that is, the total length of the descriptor. Next No. 17 “MPT_descriptors_byte” is an area indicating one byte in the descriptor. The following No. No. 18 “}” indicates no. No. 16 corresponding to “{”. No. 19 “}” indicates no. 14 corresponding to “{”, No. 20 “}” indicates no. 7 corresponds to “{”.

  Next, in FIG. 21 “number_of_assets” is an 8-bit area indicating the number of assets for which information is provided in the MP table. The following No. 22 “for (i = 0; i <N3; i ++) {” is hereinafter referred to as “No. It indicates that the area up to 59 is repeated N3 times, that is, the number of assets for which information is provided in the MP table.

  The following No. No. 23 “asset {” will be referred to as “No. 29 indicates that the area up to “}” is an area related to the asset ID. Next No. 24 “asset_id_length” is an 8-bit area indicating the number of bytes N4 of the arranged asset IDs. The following No. No. 25 “for (i = 0; i <N4; i ++) {” will be referred to as “No. This indicates that the area up to 27 is repeated N4 times, that is, the number of bytes of the asset ID. Next No. 26 “asset_id_byte” is an area indicating one byte in the asset ID. The following No. No. 27 “}” indicates no. This corresponds to 25 “{”.

  Next No. 28 “mime_type” is a 32-bit area indicating the MIME (Multipurpose Internet Mail Extension) type of the asset indicated by the asset ID. The following No. No. 29 “}” indicates no. 23 corresponds to “{”. The following No. 30 “If (asset_scheme_code ==“ GURL ”) {” is “No” when the value of “asset_scheme_code” is “GURL”. Indicates that up to 36 areas are arranged.

Next No. 31 "packet_id" is GFD (General
File Delivery) is a 32-bit area indicating the session ID. Next No. 32 “number_of_codepoints” is an 8-bit area indicating the number N8 of code points of the GFD session. The following No. No. 33 “for (i = 0; i <N8; i ++) {” will be referred to as “No. This indicates that the area up to 35 is repeated N8 times, that is, the number of code points. Next No. “CodePoint ()” 34 is an area indicating a code point table. The following No. No. 35 “}” indicates no. No. 33 corresponding to “{”. No. 36 “}” indicates no. Corresponds to 30 “{”.

  Next No. is arranged. 37 “reserved” is a 7-bit reserved area. Next No. is arranged. 38, “asset_clock_relation_flag” is a 1-bit area indicating whether or not the asset uses NTP (Network Time Protocol) as a clock reference destination. The following No. No. 39 “if (asset_clock_relation_flag == 1) {” 38 when the value of “asset_clock_relation_flag” of 38 is “1”. Indicates that up to 46 areas are arranged.

  Next No. 40 “asset_clock_relation_id” is an 8-bit area indicating the ID of the clock referred to by the asset. Next, in FIG. “Reserved” 41 is a 7-bit reserved area. Next No. 42 “asset_timescale_flag” is a flag indicating whether or not “asset_timescale” is arranged.

  The following No. 43 “if (asset_timescale_flag == 1) {” When the value of “asset_timescale_flag” of 42 is “1”, No. Indicates that up to 45 areas are arranged. Next No. 44 “asset_timescale” is a 32-bit area indicating the frequency of the clock referred to by the asset. The following No. 45 “}” indicates no. No. 43 corresponding to “{”. No. 46 “}” indicates no. This corresponds to 39 “{”.

  The following No. 47 “asset_location {” is hereinafter referred to as “No. The area up to “}” of 52 indicates an area related to the reference information (also referred to as location information) of the asset. Next No. 48 “location_count” is an 8-bit area indicating the number N6 of reference information related to the asset. The following No. 49, “for (i = 0; i <N6; i ++) {” is hereinafter referred to as “No. This indicates that the area up to 51 is repeated N6 times, that is, the number of reference information. Next No. 50 “MMT_general_location_info ()” is reference information (also referred to as location information) related to the asset. Details will be described later. The following No. No. 51 “}” indicates no. No. 49 corresponding to “{”. 52 “}” indicates no. This corresponds to 47 “{”.

  The following No. 53 “asset_descriptors {” will be referred to as “No. Up to 58 “}” indicates a descriptor area related to the asset. Next No. 54 “asset_descriptors_length” is a 16-bit area indicating a total N5 of descriptor lengths related to the asset. The following No. No. 55 “for (i = 0; i <N5; i ++) {” is hereinafter referred to as “No. Indicates that the region up to 57 is repeated N5 times, that is, the total length of the descriptor. Next No. is arranged. 56 “asset_descriptors_byte” is an area indicating one byte in the descriptor. The following No. No. 57 “}” indicates no. No. 55 corresponds to “{”. 58 “}” indicates no. No. 53 corresponding to “{”. 59 “}” indicates no. No. 22 corresponds to “{”. No. 60 “}” indicates no. This corresponds to “{” of 1.

9 to 11 are tables showing the data structure of the reference information. The data structure of the reference information (general_location_info) in this embodiment is ISO / IEC.
23008-1. In the table, no. Is a column indicating the serial number of the row in the table. The data structure is a column indicating the data structure of the reference information. The number of bits is a column indicating the number of bits of the data structure. The value is a column indicating the value taken by the data structure of the number of bits. The bit string notation is a column indicating the data format of the data structure of the number of bits. Uimsbf in bit string notation is an abbreviation for unsigned integer most significant bit first, and an unsigned integer and the most significant bit mean the head. The bit string notation bslbf is an abbreviation for bit string left bit first, and the bit string and the left bit mean the head. Further, char in the bit string notation means a character.

  In FIG. 1 “MMT_general_location_info () {” is hereinafter referred to as “No. Up to “}” of 63 represents the data structure of the reference information. Next No. is arranged. 2 "location_type" is an 8-bit area indicating the type of reference information. When “location_type” is “0x00”, this indicates that the location (data path) is the same IP data flow as the IP data flow transmitting this “location_type”. Note that 0x indicates that the subsequent character string is a hexadecimal number.

  When “location_type” is “0x01”, it indicates that the location is UDP / IP (version 4). When “location_type” is “0x02”, it indicates that the location is UDP / IP (version 6). When “location_type” is “0x03”, it indicates that the location is MPEG-2TS distributed in the broadcast network. When “location_type” is “0x04”, this indicates that the location is an elementary stream in MPEG-2TS distributed over the IP broadcast network.

  When “location_type” is “0x05”, it indicates that the location is a URL (Uniform Resource Locator). When “location_type” is “0x06”, it indicates that the location is a continuous area in the file specified by the URL. When “location_type” is “0x07”, this indicates that the location is in the control message transmitting this “location_type”. When “location_type” is “0x08”, this indicates that the location is a control message transmitted by the data path transmitting this “location_type”.

  When “location_type” is “0x09”, this indicates that the control message is transmitted by the UDP / IP data flow transmitting this “location_type”. When “location_type” is “0x0A”, this indicates a control message transmitted by the UDP / IP (version 4) data flow. When “location_type” is “0x0B”, this indicates a control message transmitted by the UDP / IP (version 6) data flow. When “location_type” is “0x0C”, this indicates an elementary stream in MPEG2-TS distributed on an IP (version 6) broadcast network.

  The following No. 3 “if (location_type == 0x00) {” 2 when the value of “location_type” of “2” is “0x00”. 4 indicates that the area is arranged. Next No. 4, “packet_id” is a 16-bit area indicating the packet ID of the MMT packet.

  The following No. “} Else if (location_type == 0x01) {” in No. 5 No. 2 when the value of “location_type” is “0x01”. Indicates that up to 9 areas are arranged. Next No. 6 “ipv4_src_addr” is a 32-bit area indicating the IPv4 address of the transmission source. Next No. 7 “ipv4_dst_addr” is a 32-bit area indicating a destination IPv4 address. Next No. “Dst_port” 8 is a 16-bit area indicating the port number of the destination. Next No. 9, “packet_id” is a 16-bit area indicating the packet ID of the MMT packet.

  The following No. 10 “} else if (location_type == 0x02) {” 2 when the value of “location_type” of “2” is “0x02”. Indicates that up to 14 areas are arranged. Next No. 11 “ipv6_src_addr” is a 128-bit area indicating the IPv6 address of the transmission source. Next No. is arranged. 12 “ipv6_dst_addr” is a 128-bit area indicating the destination IPv6 address. Next No. is arranged. “Dst_port” 13 is a 16-bit area indicating the destination port number. Next No. is arranged. 14, “packet_id” is a 16-bit area indicating the packet ID of the MMT packet.

  The following No. 15 “} else if (location_type == 0x03) {” 2 when the value of “location_type” is “0x03”. Indicates that up to 19 areas are arranged. Next No. The 16 “network_id” is a 16-bit area indicating the ID of the broadcast network that transmits MPEG2-TS. Next No. 17 "MPEG_2_transport_stream_id" is an ID of MPEG2-TS. Next No. is arranged. 18 “reserved” is a 3-bit reserved area. Next No. 19 "MPEG_2_PID" is the PID of the MPEG2-TS packet that transmits the elementary stream.

  The following No. No. 20 “} else if (location_type == 0x04) {” No. 2 in FIG. 10 when the value of “location_type” of 2 is “0x04”. Indicates that up to 25 areas are arranged. Next No. 21 “ipv6_src_addr” is a 128-bit area indicating the IPv6 address of the transmission source. Next No. 22 “ipv6_dst_addr” is a 128-bit area indicating a destination IPv6 address. Next No. is arranged. “Dst_port” 23 is a 16-bit area indicating a destination port number. Next, as shown in FIG. 24 “reserved” is a 3-bit reserved area. Next No. “MPEG_2_PID” of 25 is the PID of the MPEG2-TS packet transmitting the elementary stream.

  The following No. 26 "} else if (location_type == 0x05) {" 2 when the value of “location_type” of “2” is “0x05”. Indicates that up to 30 areas are arranged. Next No. is arranged. “URL_length” of 27 is an 8-bit area indicating the number of URL bytes N1. The following No. 28, “for (i = 0; i <N1; i ++) {” is hereinafter referred to as “No. It indicates that the area up to 30 is repeated N1 times, that is, the number of URL bytes. Next No. is arranged. 29 “URL_byte” is an area indicating one byte in the URL. The following No. 30 “}” indicates no. This corresponds to 28 “{”.

  The following No. 31 “} else if (location_type == 0x06) {” 2 when the value of “location_type” of “2” is “0x06”. Indicates that up to 37 areas are arranged. Next No. “URL_length” of 32 is an 8-bit area indicating the number of URL bytes N2. The following No. No. 33 “for (i = 0; i <N2; i ++) {” will be referred to as “No. It indicates that the area up to 35 is repeated N2 times, that is, the number of URL bytes. Next No. is arranged. 34 “URL_byte” is an area indicating one byte in the URL. The following No. No. 35 “}” indicates no. It corresponds to “{” of 33. Next No. is arranged. 36 “byte_offset” is a 16-bit area indicating an offset position from the head of the file indicated by the URL. Next No. “Length” of 37 is a 16-bit area indicating the number of bytes from the offset position.

  The following No. No. 38 “} else if (location_type == 0x07) {” When the value of “location_type” of 2 is “0x07”, it indicates that nothing is arranged.

  The following No. No. 39 “} else if (location_type == 0x08) {” 2 when the value of “location_type” of “2” is “0x08”. It shows that 40 areas are arranged. Next No. 40 “message_id” is an 8-bit area indicating the ID of the control message.

  The following No. 41 “} else if (location_type == 0x09) {” 2 when the value of “location_type” is “0x09”. It shows that up to 43 areas are arranged. Next No. is arranged. 42 “packet_id” is a 16-bit area indicating the packet ID of the MMT packet. Next No. is arranged. “Message_id” 43 is an 8-bit area indicating the ID of the control message.

  The following No. 44 "} else if (location_type == 0x0A) {" No. 2 in FIG. 11 when the value of “location_type” of 2 is “0x0A”. It shows that up to 49 areas are arranged. Next No. is arranged. 45 “ipv4_src_addr” is a 32-bit area indicating the IPv4 address of the transmission source. Next No. is arranged. 46 “ipv4_dst_addr” is a 32-bit area indicating the destination IPv4 address. Next, in FIG. 47 “dst_port” is a 16-bit area indicating the destination port number. Next No. is arranged. 48 “packet_id” is a 16-bit area indicating the packet ID of the MMT packet. Next No. is arranged. 49 “message_id” is an 8-bit area indicating the ID of the control message.

  The following No. 50 "} else if (location_type == 0x0B) {" 2 when the value of “location_type” of “2” is “0x0B”. Indicates that up to 55 areas are arranged. Next No. is arranged. 51 “ipv6_src_addr” is a 128-bit area indicating the IPv6 address of the transmission source. Next No. 52 “ipv6_dst_addr” is a 128-bit area indicating the destination IPv6 address. Next No. “Dst_port” 53 is a 16-bit area indicating a destination port number. Next No. “Packet_id” 54 is a 16-bit area indicating the packet ID of the MMT packet. Next No. “Message_id” 55 is an 8-bit area indicating the ID of the control message.

  The following No. 56 "} else if (location_type == 0x0C) {" 2 when the value of “location_type” of “2” is “0x0C”. It shows that up to 62 areas are arranged. Next No. 57 “ipv4_src_addr” is a 32-bit area indicating the IPv4 address of the transmission source. Next No. 58 “ipv4_dst_addr” is a 32-bit area indicating a destination IPv4 address. Next No. “Dst_port” 58 is a 16-bit area indicating the port number of the destination. Next No. 60 “reserved” is a 3-bit reserved area. Next No. 61, “MPEG_2_PID” is the PID of the MPEG2-TS packet that transmits the elementary stream. The following No. No. 62 “}” indicates no. This corresponds to 56 “{”. The following No. No. 63 “}” indicates no. This corresponds to “{” of 1.

  12 and 13 are tables showing the data structure of the package list table. In the table, no. Is a column indicating the serial number of the row in the table. The data structure is a column indicating the data structure of the package list table. The number of bits is a column indicating the number of bits of the data structure. The value is a column indicating the value taken by the data structure of the number of bits. The bit string notation is a column indicating the data format of the data structure of the number of bits. Uimsbf in bit string notation is an abbreviation for unsigned integer most significant bit first, and an unsigned integer and the most significant bit mean the head. Further, char in the bit string notation means a character.

  In FIG. 1 “Package_List_Table () {” will be referred to as No. 1 in FIG. Up to 30 “}” represents the data structure of the package list table. No. placed at the top of the table. 2, “table_id” is an 8-bit area indicating the ID of the package list table. Next No. “Version” of 3 is an 8-bit area indicating the version number of the package list table. Next No. “Length” of 4 is a 16-bit area indicating the number of bytes of the package list table after the area.

Next No. “Num_of_package” of 5 is an 8-bit area indicating the number N2 of packages whose reference information is described in the package list table.
The following No. No. 6 “for (i = 0; i <N2; i ++) {” will be referred to as “No. The region up to 9 is repeated N2 times, that is, the number of packages in which reference information is described. Next No. 7, “package_id” is a 16-bit area indicating the package ID of a package describing reference information to the MP table. In addition, this No. 7 instead of “package_id” in FIG. 9 to No. 12 may be arranged so that an arbitrary-length package ID can be described. Next No. 8, “MMT_general_location_info ()” is reference information to the MP table, and is an area indicating the reference information shown in FIGS. 9 to 11. The package list table includes these Nos. 7 and no. 8 associates the package ID with the reference information (packet ID) to the MP table. The following No. No. 9 “}” indicates no. 6 corresponds to “{”.

Next No. Ten “num_of_ip_delivery” is an 8-bit area indicating the number N3 of IP services describing this reference information. The following No. 11 “for (i = 0; i <N3; i ++) {” is referred to as “No. This indicates that the area up to 29 is repeated N3 times, that is, the number of IP services in which reference information is described.
Next No. Twelve “transport_file_id” is a 32-bit area indicating a label for uniquely identifying a file transmitted by the IP service.
Next No. 13 “location_type” is an 8-bit area indicating the type of reference information. When “location_type” is “0x01”, it indicates an IPv4 data flow. When “location_type” is “0x02”, it indicates that the location is UDP / IP (version 6).

  The following No. 14 “if (location_type == 0x01) {” 13 when the value of “location_type” of “13” is “0x01”. Indicates that up to 17 areas are arranged. Next No. is arranged. 15 “ipv4_src_addr” is a 32-bit area indicating the IPv4 address of the transmission source. Next No. 16 “ipv4_dst_addr” is a 32-bit area indicating the destination IPv4 address. Next No. 17 "dst_port" is a 16-bit area indicating the destination port number.

  The following No. 18 “if (location_type == 0x02) {” 13 when the value of “location_type” is “0x02”. Indicates that up to 21 areas are arranged. Next No. 19 “ipv6_src_addr” is a 128-bit area indicating the IPv6 address of the transmission source. Next No. is arranged. 20 “ipv6_dst_addr” is a 128-bit area indicating a destination IPv6 address. Next No. is arranged. “Dst_port” 21 is a 16-bit area indicating a destination port number.

  No. in FIG. 22 “if (location_type == 0x05) {” indicates “No. 13 when the value of “location_type” is “0x05”. It shows that up to 27 areas are arranged. Next No. is arranged. “URL_length” of 23 is an 8-bit area indicating the number of URL bytes N1. The following No. 24, “for (i = 0; i <N1; i ++) {” is hereinafter referred to as “No. This indicates that the area up to 26 is repeated N1 times, that is, the number of URL bytes. Next No. 25 “URL_byte” is an area indicating one byte in the URL. The following No. No. 26 “}” indicates no. 24 corresponding to “{”, the following No. No. 27 “}” indicates no. This corresponds to 22 “{”.

  Next No. 28 “descriptors ()” is an area indicating a descriptor related to the IP service. The following No. No. 29 “}” indicates “No.” in FIG. 11 corresponds to “{” and the following No. 30 “}” indicates No. 30 in FIG. This corresponds to “{” of 1.

  FIG. 14 is a flowchart illustrating the operations of the designation acquisition unit 72, the reception control unit 73, and the control message processing unit 74. First, the designation acquisition unit 72 acquires designation of a desired service (Sa1). Next, the reception control unit 73 instructs the reception unit 70 to receive the IP data flow transmitting the desired service (Sa2). The correspondence between the service and the IP data flow may be stored in advance by the reception control unit 73, or information indicating the correspondence such as AMT (Address Map Table) may be distributed from the service providing side. (See Non-Patent Documents 1 and 2).

  When the receiving unit 70 receives the IP data flow according to the instruction, the separating unit 71 separates the PA message stored in the MMT packet having the packet ID “0” from the IP data flow. The control message processing unit 74 acquires the PA message separated by the separation unit 71 (Sa3). Next, the control message processing unit 74 acquires the MP table in the acquired PA message (Sa4), and the package ID of the MPT table is the package ID of the desired service acquired by the designation acquisition unit 72 in step Sa1. Is determined (Sa5).

  For example, the control message processing unit 74 may store the association between the service and the package ID in advance, and obtain the package ID of the desired service by referring to the association. Alternatively, information indicating the association between the service and the package ID is distributed from the service provider side, and the control message processing unit 74 may acquire the package ID of the desired service by referring to the information. .

  When it is determined in step Sa5 that they do not match (Sa5-No), the process proceeds to step Sa11. The control message processing unit 74 acquires the package list table in the PA message acquired in step Sa3 (Sa11). Next, the control message processing unit 74 refers to the acquired package list table and acquires the packet ID associated with the package ID of the desired service (Sa12).

  The control message processing unit 74 instructs the separation unit 74 to separate the PA message of the acquired packet ID. The separation unit 74 separates the PA message having the designated packet ID from the IP data flow received by the reception unit 70. The control message processing unit 74 acquires the separated PA message. That is, the control message processing unit 74 acquires the PA message of the packet ID acquired in step Sa12 (Sa13).

  Next, the control message processing unit 74 acquires the MP table in the acquired PA message (Sa14), and proceeds to step Sa6. On the other hand, when it is determined in step Sa5 that they match (Sa5-Yes), the process directly proceeds to step Sa6.

  In step Sa6, the control message processing unit 74 instructs the separation unit 71 to separate the assets described in the acquired MP table. According to the instruction, the separation unit 71 inputs the video stream to the video decoding unit 75, the audio stream to the audio decoding unit 76, and the data stream to the data rendering unit 77 among the separated assets. To do. As a result, the output device 18 displays the video of the package and outputs audio.

Since the MP table of the desired service is repeatedly transmitted by the received IP data flow, the control message processing unit 74 monitors the MP table (Sa7).
The control message processing unit 74 determines whether there is a change from the previous one in the transmitted MP table (Sa8). When it is determined that there is a change (Sa8-Yes), the control message processing unit 74 reacquires the MP table (Sa9), and returns to Step Sa6.

  When it is determined in step Sa8 that there is no change (Sa8-No), the designation acquisition unit 72 determines whether a desired service has been changed (Sa10). When the desired service has not been changed (Sa10-No), the process returns to step Sa7. If the desired service has been changed, the process returns to step Sa1.

  As described above, the distribution system 10 includes the control message generation device 11, the distribution device 16, and the reception device 17. The control message generation device 11 includes reference information for the first MP table (first table) and the second MP table (second table) including reference information for each asset constituting the first package. A first PA message (first control message) including a package list table including Further, the control message generator 11 generates a second PA message (second control message) including the second MP table. The distribution device 16 distributes the first and second PA messages generated by the control message generation device 11 using an IP data flow (data flow). The receiving device 17 receives the data flow.

  As a result, the distribution system 10 can enable the receiving device 17 to receive only the first control message with respect to the first package, that is, to receive in one hop. In addition, the second package can be received with two hops by acquiring the first control message and the second control message. Therefore, the expected value of the number of hops until the package can be received can be suppressed.

The receiving device 17 includes a designation acquiring unit 72, a receiving unit 70, a separating unit 71, and a control message processing unit 74. The designation acquisition unit 72 acquires information for specifying a desired package. The receiving unit 70 receives an IP data flow. The separation unit 71 separates the first PA message from the IP data flow. The control message processing unit 74 refers to the first MP table included in the first PA message, and separates the separation of the first MP package when the first package matches the desired package. The unit 71 is instructed.
Thereby, the receiving device 17 can receive the first package in one hop.

In addition, the control message processing unit 74 refers to the first MP table included in the first PA message, and when the first package does not match the desired package, the control message processing unit 74 includes the first message in the first PA message. The reference information to the second MP table corresponding to the desired package is acquired by referring to the package list table to be stored, and the second MP table corresponding to the desired package is included using the acquired reference information. The separation unit 71 is instructed to separate the two PA messages.
Thereby, the receiving device 17 can receive the second package in two hops.

  In the above-described embodiment, when only one package is included in the IP data flow at the same time, the PA message whose packet ID is “0” may not include the package list table. A package list table including only information related to one package included in the package may be included, or a value of “num_of_package” may be set to “0” to generate a package list table including no reference information regarding the package. .

  In the above-described embodiment, the MP table and the package list table have been described as being stored in the PA message, but may be stored in other control messages. However, the control message for storing the package list table together with the MP table is preferably a PA message having a packet ID “0”. This is because the PA message with the packet ID “0” is a control message that the receiving device 17 acquires first.

[Modification 1 of Embodiment]
In the above-described embodiment, the control message generation device 11 stores the package list table only in the PA message whose packet ID is “0”, but may be stored in other PA messages. FIG. 15 is a conceptual diagram showing a configuration of an IP data flow in the first modification. In the figure, portions corresponding to the respective portions in FIG. 4 are denoted by the same reference numerals and description thereof is omitted.

  The IP data flow DFa differs from the IP data flow DF of FIG. 4 in that it includes a PA message PA2 instead of the PA message PA. PA message PA2 includes package list table PL2 in addition to MP table MP2. The package list table PL2 includes at least reference information to MP tables other than the MP table MP2. Note that both the package list tables PL1 and PL2 may include reference information to all the MP tables transmitted by the IP data flow DFa.

[Modification 2 of the embodiment]
Hereinafter, Modification 2 of the embodiment will be described with reference to the drawings. This modification differs from the above-described embodiment in the data structure of the MP table, reference information (MMT_general_location_info ()), and package list table. 16, 17 and 18 are tables showing the data structure of the MP table in this modification. The data structure shown in these figures is different from the data structure shown in FIGS. 6, 7, and 8 in the following four points.

  The first point is No. of FIG. The value of “table_id” of 2 is “0x20”. The second point is that the MP table of this modification is No. 1 in FIG. 23 to No. Instead of No. 28, No. 28 in FIG. 23 to No. 28. The third point is that the MP table of this modification is No. 1 in FIG. Instead of No. 28, No. 28 in FIG. 29 has “asset_type”. The fourth point is that the MP table of this modification is No. 1 in FIG. 30 to No. It is a point which does not have 36.

  Hereinafter, the second point will be described. No. in FIG. “Identifier_type” 23 is also called an identifier type, and is an 8-bit area indicating the ID system of the MMTP packet flow stored thereafter. Here, the value of “identifier_type” is “0x00” indicating that the asset ID is stored. No. 24 “asset_id_scheme” is also referred to as an asset ID format, and is a 32-bit area indicating the format of an asset ID stored thereafter. No. 25 “asset_id_length” is also referred to as an asset ID length, and is an 8-bit area indicating the length of an asset ID byte stored thereafter in byte units. The following No. 26, “for (i = 0; i <N4; i ++) {” is hereinafter referred to as No. 26. This indicates that the area up to 28 is repeated N4 times, that is, the number of asset ID lengths. Next No. 27 “asset_id_byte” is also referred to as an asset ID byte, and is an area indicating one byte in the asset ID. The following No. No. 28 “}” indicates no. 26 corresponds to “{”.

  Hereinafter, the third point will be described. No. in FIG. “Asset_type” of 29 is also referred to as an asset type. This is a 32-bit area indicating the type of asset indicated by 27 asset ID bytes. When the value of “asset_type” is “hvc1”, the asset type is ITUT-T recommendation H.264. This indicates that the HEVC is defined by H.265. In addition, “asset_type”, when the value is “mp4a”, indicates that the type of the asset is ISO / IEC14496-3 audio.

  Further, “asset_type” indicates that the type of asset is timed text (caption / character super) when the value is “stpp”. “Asset_type” indicates that the asset type is an application when the value is “aapp”. Further, “asset_type” indicates that the type of asset is synchronous general-purpose data when the value is “asgd”. Further, “asset_type” indicates that the asset type is asynchronous general-purpose data when the value is “aagd”.

  19 and 20 are tables showing the data structure of the reference information (MMT_general_location_info ()) in this modification. The data structures shown in these figures are different from the data structures shown in FIGS. 9, 10, and 11 in the following four points. No. of FIG. 31 to No. 46 and No. 46 in FIG. 47 to No. The difference is that 62 is not provided.

  21 and 22 are tables showing the data structure of the package list table in this modification. The data structures shown in these figures differ from the data structures shown in FIGS. 12 and 13 in the following two points. The first point is that the package list table in this modification is No. 1 in FIG. 7 in place of No. 7 in FIG. 7 to No. It is a point having 10. No. in FIG. 7, “MMT_package_id_length” is also referred to as a package ID length, and is an 8-bit area indicating the length of a package ID byte stored thereafter in byte units. The following No. 8 “for (j = 0; j <M; j ++) {” This indicates that the area 9 is repeated M times, that is, the length of the package ID byte. Next No. is arranged. “MMT_package_id_byte” of 9 is also called a package ID byte, and is an 8-bit area indicating 1 byte in the package ID. The following No. No. 10 “}” indicates no. 8 corresponds to “{”.

  The second point is that the package list table in this modification is No. 1 in FIG. Instead of No. 28, No. 28 in FIG. 32 to No. 34. No. in FIG. 32 “descriptor_loop_length” is also called a descriptor length, and is a 16-bit area indicating the total byte length of the descriptor stored thereafter. The following No. 33, “for (j = 0; j <M; j ++) {” This indicates that 33 areas are repeated M times, that is, by the descriptor length. The following No. 34 “descriptor ()” is also referred to as a descriptor area, and is one byte in the area for the descriptor indicating the detailed information of the IP service. The following No. No. 34 “}” indicates no. This corresponds to 32 “{”.

Note that any or all of the MP table, MMT_general_location_info (), and the package list table in the first modification may be the same as in the second modification.
Further, in the above-described modification 2, all of the MP table, MMT_general_location_info (), and package list table are different from the above-described embodiment, but the difference is that the MP table, MMT_general_location_info (), and package list table are different. It may be a part.

  Also, a program for realizing the functions of the control message generator 11 and the receiver 17 in FIG. 1 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed. By doing so, these devices may be realized. Here, the “computer system” includes an OS and hardware such as peripheral devices.

  The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, the “computer-readable recording medium” dynamically holds a program for a short time like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory in a computer system serving as a server or a client in that case, and a program that holds a program for a certain period of time are also included. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

Further, each functional block of the control message generation device 11 in FIG. 2 and the reception device 17 in FIG. 3 described above may be individually chipped, or a part or all of them may be integrated into a chip. Further, the method of circuit integration is not limited to LSI, and implementation using a dedicated circuit or a general-purpose processor is also possible. Either hybrid or monolithic may be used. Some of the functions may be realized by hardware and some by software.
In addition, when a technology such as an integrated circuit that replaces an LSI appears due to progress in semiconductor technology, an integrated circuit based on the technology can be used.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design changes and the like within a scope not departing from the gist of the present invention.

DESCRIPTION OF SYMBOLS 10 ... Distribution system 11 ... Control message generation device 12 ... Video transmission device 13 ... Audio transmission device 14 ... Data transmission device 15 ... Multiplexing device 16 ... Distribution device 17 ... Reception device 18 ... Output device 21 ... MP table production | generation part 22 ... Package List table generation unit 23 ... PA message generation unit 70 ... reception unit 71 ... separation unit 72 ... designation acquisition unit 73 ... reception control unit 74 ... control message processing unit 75 ... video decoding unit 76 ... audio decoding unit 77 ... data rendering unit 78 ... Video synthesis unit 79 ... Speech synthesis unit

Claims (1)

A table generating unit that generates a first table that includes reference information for each asset that configures the first package, and a second table that includes reference information for each asset that configures the second package;
A package list table generating unit that generates a package list table including reference information to the second table;
A control message generator for generating a first control message including the first table and the package list table, and a second control message including the second table;
Comprising
Reference information to the second table is:
A package ID indicating the second package;
A packet ID of a packet storing the second control message including the second table;
A control message generation device characterized by the above.

Images