JP2011223353A - Digital-broadcast-data transmitting method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a digital-broadcast-data transmitting method capable of transmitting a highly convenient digital broadcast signal.SOLUTION: A data transmitting method includes the steps of performing conversion into a predetermined format by encoding broadcast information, generating metadata on the basis of attribute information, generating a service information table including information representing presence or absence of the metadata on the basis of broadcast additional information and the attribute information, generating a transport stream for transmission by multiplexing the converted broadcast information, the service information table and the metadata, and transmitting the generated transport stream.

Description

  Embodiments described herein relate generally to a digital broadcasting method data transmission method for transmitting digital broadcast program-related information data.

  In conventional digital broadcasting, signals such as video and audio are transmitted based on TS (Transport Stream) defined in MPEG-2 Systems (ISO / IEC13818-1). A data transmission method for transmitting a TS includes, for example, encoding a plurality of contents including video and audio, dividing the encoded data into predetermined lengths, packetizing the packets, and generating a TS by multiplexing the packets. The generated TS is subjected to transmission path coding or the like, and is transmitted by radio waves or a network.

  A receiving apparatus that receives a TS can acquire desired content by filtering, extracting, and synthesizing necessary signal packets.

JP 2002-251328 A

  In digital broadcasting, in order to specify a desired program from a received TS in a receiving apparatus and demultiplex each signal such as video and audio constituting the program, Program Specific Information / Service Information ( PSI / SI) is used.

  In addition, metadata indicating detailed information about a program may be multiplexed with a TS and transmitted. In this case, in the data transmission method described above, the metadata is stored in the elementary stream in the service for transmitting the program and transmitted to the receiving device.

The receiving device that receives the TS receives XML from the service ES in the description language type metadata (
Hereinafter, simply extract metadata and description). For this reason, the receiving apparatus cannot determine the presence / absence of metadata transmission until acquiring the Prpgram Map Table (PMT). For this reason, there exists a problem that the efficiency of the process in a receiver may fall.

  Further, since the metadata exists below the PMT, there is a problem that the metadata of a plurality of services cannot be transmitted at once.

  Accordingly, an object of the present invention is to provide a digital broadcasting data transmission method capable of transmitting a more convenient digital broadcasting signal.

  According to one embodiment, a digital broadcasting data transmission method includes a step of encoding program information and converting the program information into a predetermined format, a step of generating metadata based on attribute information, program additional information, and the attribute information And generating a service information table including information indicating the presence or absence of the metadata transmission, the converted program information, the service information table, and the metadata to multiplex the transmission transformer. Generating a port stream, and sending the generated transport stream.

FIG. 1 is a diagram for explaining an example of a digital broadcasting data transmission method according to an embodiment. FIG. 2 is an explanatory diagram for explaining an example of SI data. FIG. 3 is an explanatory diagram for explaining an example of SI data. FIG. 4 is an explanatory diagram for explaining an example of SI data. FIG. 5 is an explanatory diagram for explaining an example of a service list descriptor inserted into SI. FIG. 6 is an explanatory diagram for describing an example of service_type illustrated in FIG. 5. FIG. 7 is an explanatory diagram for describing an example of a link descriptor inserted into SI. FIG. 8 is an explanatory diagram for describing an example of linkage_type illustrated in FIG. 7.

  Hereinafter, a digital broadcast data transmission method according to an embodiment will be described in detail with reference to the drawings.

  FIG. 1 is a diagram for explaining an example of a TS transmission method according to an embodiment.

  The data transmission apparatus 100 multiplexes a plurality of packets based on the input program information and program additional information, generates a TS, and transmits the generated TS via radio waves or a network.

  A program is an aggregate of broadcast data stream components that belong to the same service (organization channel) and whose start and end times are determined. The broadcast data stream component includes, for example, one or more of a video signal, an audio signal, and a caption signal.

  The data transmission device 100 includes a video encoder 111, a video conversion unit 112, an audio encoder 121, an audio conversion unit 122, a PSI / SI generation unit 131, a metadata generation unit 141, a multiplexer 150, and a transmission path encoding unit 160.

  The video encoder 111 encodes video data as input program information. The video encoder 111 transmits the encoded video data to the video conversion unit 112.

  The video conversion unit 112 converts the video data encoded by the video encoder 111 into a format compatible with the transmission method. That is, the video conversion unit 112 converts the video data into a PES (Packetized Elementary Stream). The video conversion unit 112 transmits the generated PES packet to the multiplexer 150.

  The audio encoder 121 encodes audio data as input program information. The audio encoder 121 transmits the encoded audio data to the audio conversion unit 122.

  The audio conversion unit 122 converts the audio data encoded by the audio encoder 121 into a format compatible with the transmission method. That is, the voice conversion unit 122 converts the voice data into PES packets. The voice conversion unit 122 transmits the generated PES packet to the multiplexer 150.

  The PSI / SI generating unit 131 generates a service information table (PSI / SI table) such as PSI or SI based on the input program additional information.

  PSI is a transmission control signal defined by the MPEG-2 Systems standard. The PSI is used for demultiplexing processing and reproduction processing in the receiving apparatus.

  SI is, for example, program arrangement information defined in ARIB STD-B10. SI is digital data that describes the distribution system, content, schedule, and timing of a broadcast data stream. The SI has a PSI configuration and a uniquely defined extension. The SI is used for display of an organized channel, display of program information, etc. performed for the viewer in the receiving apparatus.

  The PSI / SI generation unit 131, based on the input program additional information, for example, Program Association Table (PAT), Program Map Table (PMT), Conditional Access Table (CAT), and Network Information Table (NIT). Generate a table.

  In addition, the PSI / SI generation unit 131 generates an SI table such as a Service Description Table (SDT), an Event Information Table (EIT), and a Broadcaster Information Table (BIT) based on the input program additional information. The PSI / SI generating unit 131 transmits the generated service information table to the multiplexer 150.

  The metadata generation unit 141 generates metadata based on the attribute information regarding the input service. The metadata is, for example, description language type metadata in XML format defined in ARIB STD-B38. The metadata generation unit 141 transmits the generated metadata to the IP packet multiplexing unit 142. Further, the metadata generation unit 141 notifies the PSI / SI generation unit 131 that the metadata has been generated. When receiving a notification that metadata has been generated from the metadata generation unit 141, the PSI / SI generation unit 131 describes information indicating that metadata exists in the generated service information table.

  The metadata generation unit 141 notifies the PSI / SI generation unit 131 of the presence / absence of metadata transmission for each service, each broadcaster, each TS, or each network.

  The IP packet multiplexing unit 142 divides at least one piece of metadata generated by the metadata generation unit 131 into a fixed length as a file, and applies a FILE delivery over unidirectional transport (FLUTE) protocol. At this time, error correction coding may be used together in order to restore missing data at the time of reception. Further, this divided data is stored in a UDP packet or an IP packet. At this time, compression processing or the like may be performed on the header of the IP packet. Then, the datagram is encapsulated and transmitted to the multiplexer 150 by the ULE (Uniform Lightweight Encapsulation) method defined by RFC4326.

  The multiplexer 150 is a UDP / IP packet formed by the PES packet generated by the video conversion unit 112 and the audio conversion unit 122, the service information table generated by the PSI / SI generation unit 131, and the IP packet multiplexing unit 142. Multiplex with metadata. As a result, the multiplexer 150 generates a TS. The multiplexer 150 transmits the generated TS to the transmission path encoding unit 160.

  The transmission path encoding unit 160 performs error correction encoding processing, modulation processing, and the like on the TS generated by the multiplexer 150, and transmits the result through radio waves or a network. Thereby, the data transmission apparatus 100 can transmit TS in which content data such as video and audio, a service information table, and metadata are multiplexed to the reception apparatus.

  2 to 4 are explanatory diagrams for explaining an example of SI data generated by the PSI / SI generating unit 131. FIG. FIG. 2 shows an example of SDT generated by the PSI / SI generation unit 131. FIG. 3 shows an example of a BIT generated by the PSI / SI generation unit 131. FIG. 4 shows an example of NIT generated by the PSI / SI generation unit 131.

  2 to 4 are explanatory diagrams for explaining an example of PSI / SI data generated by the PSI / SI generation unit 131. FIG. FIG. 2 shows an example of SDT generated by the PSI / SI generation unit 131. FIG. 3 shows an example of a BIT generated by the PSI / SI generation unit 131. FIG. 4 shows an example of NIT generated by the PSI / SI generation unit 131.

  The SDT is information regarding services (organization channels) included in the TS. The BIT is information regarding broadcasters existing on the network. The NIT is information that associates transmission path information such as a modulation frequency with a broadcast service. That is, NIT indicates the service configuration of the entire network.

  SDT is a service description table. The SDT has a description of a list of all services included in a certain TS. When generating an SDT as a service information table, the PSI / SI generating unit 131 can collectively describe the presence / absence of metadata transmission for each service.

  As illustrated in FIG. 2, the SDT includes a field “service_id” and a field “Metadata_flag”. “Service_id” is a service identifier for specifying a formation channel. “Metadata_flag” is a flag indicating the presence or absence of metadata transmission. “Metadata_flag” is provided for each service (organization channel) specified by “service_id”.

  That is, when receiving notification of the presence / absence of metadata transmission for each service from the metadata generation unit 141, the PSI / SI generation unit 131 responds to the presence / absence of metadata transmission of the service corresponding to the identifier described in “service_id”. Then, the value of “Metadata_flag” is described to generate an SDT.

  BIT is a broadcaster information table. The BIT has a description in which all services are grouped by a business group (broadcaster). When generating the BIT as the service information table, the PSI / SI generating unit 131 can describe the presence / absence of metadata transmission in units of broadcasters.

  As shown in FIG. 3, the BIT has a field called “broadcaster_id” and a field called “Metadata_flag”. “Broadcaster_id” is a broadcaster identifier for specifying a broadcaster. “Metadata_flag” is a flag indicating the presence or absence of metadata transmission. “Metadata_flag” is provided for each broadcaster specified by “broadcaster_id”.

  That is, when receiving the notification of the presence / absence of metadata transmission for each broadcaster from the metadata generation unit 141, the PSI / SI generation unit 131 determines whether or not the metadata transmission of the broadcaster corresponding to the identifier described in “broadcaster_id” exists. In response to this, the value of “Metadata_flag” is described to generate a BIT.

  NIT is a network information table. The NIT has a list of all services that can be selected by the receiving device and a description of which TS each service is included in. Further, when generating the NIT as the service information table, the PSI / SI generation unit 131 can describe the presence / absence of metadata transmission for each TS or for the entire network.

  As shown in FIG. 4, the NIT has a field “original_network_id”, a field “transport_stream_id”, and a field “Metadata_flag”.

  “Original_network_id” is a network identifier for specifying a network such as BS digital broadcasting. “Transport_stream_id” is a TS identifier for specifying a TS in the network. “Metadata_flag” is a flag indicating the presence or absence of metadata transmission. “Metadata_flag” is provided for each network specified by “original_network_id” or for each transport stream specified by “transport_stream_id”.

  That is, when receiving notification of the presence / absence of metadata transmission for each network from the metadata generation unit 141, the PSI / SI generation unit 131 responds to the presence / absence of metadata transmission of the network corresponding to the identifier described in “original_network_id”. Then, the value of “Metadata_flag” is described to generate NIT.

  Further, when the PSI / SI generation unit 131 receives a notification of the presence / absence of metadata transmission for each TS from the metadata generation unit 141, the PSI / SI generation unit 131 responds to the presence / absence of metadata transmission of the TS corresponding to the identifier described in “transport_stream_id”. Then, the value of “Metadata_flag” is described to generate NIT.

  As described above, the PSI / SI generation unit 131 provides a “Metadata_flag” field in the SDT, BIT, or NIT. The PSI / SI generating unit 131 describes the presence / absence of metadata transmission for each service, for each broadcaster, for each TS, or for each network in the “Metadata_flag” field.

  As a result, the data transmission device 100 can notify the reception device of the presence or absence of metadata transmission for each service, for each broadcaster, for each TS, or for each network. Thereby, the receiving apparatus can determine the presence or absence of metadata transmission at the time of receiving the service information table. For this reason, the receiving apparatus can perform efficient processing. As a result, it is possible to provide a digital broadcast data transmission method capable of transmitting a more convenient digital broadcast signal.

  Further, by defining that the service is a metadata transmission dedicated service in the service type information, metadata regarding a plurality of services can be transmitted together in one service.

  FIG. 5 is an explanatory diagram for explaining an example of a service list descriptor inserted in the descriptor area of the service information table.

  SDT, BIT, and NIT have a descriptor area in the table. The descriptor area is a field into which a plurality of various descriptors can be inserted.

  For example, the PSI / SI generation unit 131 inserts the service list descriptor (service_list_descriptor) illustrated in FIG. 5 into the descriptor area of the PSI / SI table. For example, the PSI / SI generation unit 131 inserts a service list descriptor into the second descriptor area of the NIT.

  The service list descriptor is a descriptor for describing a list of each service and service type type in the TS. As illustrated in FIG. 5, the service list descriptor includes fields such as “descriptor_tag”, “descriptor_length”, “loop”, “service_id”, and “service_type”.

  “Descriptor_tag” is a field for describing a value indicating that the descriptor is a service list descriptor. “Descriptor_length” is a field for describing the descriptor length of the service list descriptor. “Loop” is a field for describing a loop according to the number of services in the TS.

  “Service_id” is a field for describing an identifier for identifying a service included in the TS. “Service_type” is a field for describing a value indicating the type of the service.

  The PSI / SI generating unit 131 inputs a predetermined value in “service_type” according to the type of service generated as a TS. The PSI / SI generation unit 131 determines the type of content based on program additional information input from the outside.

  Digital broadcasting services include digital TV services, digital audio services, data services, temporary video services, temporary audio services, temporary data services, engineering download services, pre-storage data services, storage-only data services, and bookmark list data services. There are different types. Further, in the present embodiment, a metadata dedicated service exists.

  The PSI / SI generating unit 131 includes a data table 131a in which a type of a digital broadcast service is associated with a value input to “service_type”.

  The PSI / SI generating unit 131 determines the type of service based on program additional information or attribute information input from the outside. The PSI / SI generation unit 131 refers to the data table 131a based on the determined type, and describes a value in “service_type”.

  FIG. 6 is an explanatory diagram for explaining a value input to “service_type” shown in FIG. 5 and a service type.

  When the type of digital broadcasting service is “digital TV service”, the PSI / SI generation unit 131 describes “0x01” in “service_type”. When the type of the digital broadcasting service is “digital audio service”, the PSI / SI generating unit 131 describes “0x02” in “service_type”. When the type of the digital broadcasting service is “digital data service”, the PSI / SI generating unit 131 describes “0xC0” in “service_type”.

  When the type of the digital broadcasting service is “temporary video service”, the PSI / SI generation unit 131 describes “0xA1” in “service_type”. When the type of digital broadcasting service is “temporary voice service”, the PSI / SI generation unit 131 describes “0xA2” in “service_type”. When the type of the digital broadcasting service is “temporary data service”, the PSI / SI generation unit 131 describes “0xA3” in “service_type”.

  When the type of digital broadcasting service is “engineering download service”, the PSI / SI generation unit 131 describes “0xA4” in “service_type”.

  When the type of digital broadcasting service is “pre-storage data service”, the PSI / SI generation unit 131 describes “0xA8” in “service_type”. When the type of the digital broadcasting service is “storage-only data service”, the PSI / SI generation unit 131 describes “0xA9” in “service_type”.

  When the type of the digital broadcasting service is “bookmark list data service”, the PSI / SI generation unit 131 describes “0xAA” in “service_type”.

  Further, when transmitting metadata of a plurality of services collectively within one service, the PSI / SI generation unit 131 defines “metadata dedicated service” as the type of digital broadcasting service, and sets “service_type” to “0xAB”. ".

  As described above, by defining and transmitting a service that exclusively transmits metadata as service type information, the data transmission apparatus 100 can efficiently transmit metadata of a plurality of services collectively. .

  As a result, it is possible to provide a digital broadcast data transmission method capable of transmitting a more convenient digital broadcast signal.

  When receiving a TS, a receiving device that receives a TS format broadcast signal separates the received TS into packets for each PID (packet ID). The receiving apparatus acquires the PSI / SI table from the separated packet. The receiving device reads the descriptor of the PSI / SI table and reads the service list descriptor inserted in the descriptor area.

  The receiving apparatus checks the value of “service_type” in the service description list. When the value of “service_type” is “0xAB”, the receiving apparatus recognizes that the service in which the service type information is described is metadata-dedicated data. In this case, the receiving apparatus can acquire the metadata of a plurality of services collectively by extracting the packet of the metadata dedicated data service.

  Further, the data transmission apparatus 100 can specify the transmission position of the metadata in the link type information of the link descriptor inserted in the SDT. In this case, the receiving apparatus can recognize the transmission position of the metadata related to the service by reading the link descriptor. For this reason, the data transmission apparatus 100 can cause the reception apparatus to perform efficient processing.

  FIG. 7 is an explanatory diagram for explaining an example of a link descriptor to be inserted into a descriptor area of SDT.

  For example, the PSI / SI generation unit 131 inserts the link descriptor (linkage_descriptor) illustrated in FIG. 7 into the descriptor area of the SDT.

  The link descriptor is a descriptor for describing a link destination to various data. 7, the service list descriptor includes fields such as “descriptor_tag”, “descriptor_length”, “transport_stream_id”, “original_network_id”, “service_id”, and “linkage_type”.

  “Descriptor_tag” is a field for describing a value indicating that the descriptor is a link descriptor. “Descriptor_length” is a field for describing the descriptor length of the link descriptor.

  “Transport_stream_id” is a field for describing a descriptor for specifying a TS including a link destination service. “Original_network_id” is a field for describing a descriptor for specifying a network in which a link destination service is transmitted. “Service_id” is a field for describing a descriptor of a link destination service.

  “Linkage_type” is a field for describing a value indicating the type of link destination service.

  The PSI / SI generating unit 131 inputs a predetermined value to “linkage_type” according to the type of service at the link destination. The PSI / SI generating unit 131 determines the type of service based on program additional information or attribute information input from the outside.

  Types of services linked by the link descriptor include information services, electronic program guide (EPG) services, CA alternative services, transport streams including all network / bouquet SI, alternative services, and data broadcasting services. . Further, in the present embodiment, a metadata dedicated service exists.

  The PSI / SI generating unit 131 includes a data table 131b that associates the type of service of the link destination with the value input to “linkage_type”.

  The PSI / SI generating unit 131 determines the type of service based on program additional information or attribute information input from the outside. The PSI / SI generation unit 131 refers to the data table 131b based on the determined type, and describes a value in “linkage_type”.

  FIG. 8 is an explanatory diagram for explaining a value input to “linkage_type” shown in FIG. 7 and a service type.

  When the type of service at the link destination is “information service”, the PSI / SI generation unit 131 describes “0x01” in “linkage_type”. When the link destination service type is “electronic program guide service”, the PSI / SI generation unit 131 describes “0x02” in “linkage_type”. When the type of the link destination service is “CA alternative service”, the PSI / SI generation unit 131 describes “0x03” in “linkage_type”.

  When the type of service at the link destination is “transport stream including all networks / bouquet SI”, the PSI / SI generating unit 131 describes “0x04” in “linkage_type”. When the type of the link destination service is “alternative service”, the PSI / SI generation unit 131 describes “0x05” in “linkage_type”. When the type of the service at the link destination is “data broadcasting service”, the PSI / SI generation unit 131 describes “0x06” in “linkage_type”.

  In addition, when the link destination service type is “metadata dedicated service”, the PSI / SI generation unit 131 describes “0x07” in “linkage_type”.

  As described above, the data transmission apparatus 100 transmits a link to a service that exclusively transmits metadata in the link descriptor. This makes it possible to specify the transmission position of metadata in service units. As a result, the data transmission apparatus 100 can easily make the reception apparatus recognize the transmission position of the metadata related to the service.

  As a result, it is possible to provide a digital broadcast data transmission method capable of transmitting a more convenient digital broadcast signal.

  When receiving a TS, the receiving apparatus separates the received TS into packets for each PID (packet ID). The receiving apparatus acquires the PSI / SI table from the separated packet. The receiving apparatus reads the descriptor of the SDT and reads the link descriptor inserted in the descriptor area.

  The receiving apparatus checks the value of “linkage_type” in the link descriptor. When the value of “linkage_type” is “0x07”, the receiving apparatus recognizes that the service indicated by “service_id” is metadata-only data. In this case, the receiving apparatus can easily acquire metadata about the service by extracting the packet of the service at the link destination.

  Note that the present invention is not limited to the above-described embodiments as they are, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. In addition, various inventions can be formed by appropriately combining a plurality of components disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, you may combine the component covering different embodiment suitably.

  For example, in the transmission of metadata, a data carousel transmission scheme that is modularized and mapped to the DSM-CC section format instead of the IP packet multiplexing scheme in the IP packet multiplexing unit 142 in FIG. 1 may be applied.

  DESCRIPTION OF SYMBOLS 100 ... Data transmission apparatus, 111 ... Video encoder, 112 ... Video converter, 121 ... Audio encoder, 122 ... Audio converter, 131 ... PSI / SI generator, 131a ... Data table, 131b ... Data table, 141 ... Metadata Generation unit 142... IP packet multiplexing unit 150 150 Multiplexer 160 Transmission path encoding unit

Claims (7)

Encoding program information and converting it into a predetermined format;
Generating metadata based on the attribute information;
Generating a service information table including information indicating presence / absence of the metadata transmission based on program additional information and the attribute information;
Multiplexing the converted program information, the service information table, and the metadata to generate a transport stream for transmission;
Sending the generated transport stream;
A data transmission method for digital broadcasting, comprising:   2. The service information table according to claim 1, wherein the step of generating the service information table inserts into the service information table information indicating the presence or absence of metadata transmission for each service, each broadcaster, each transport stream, or each network. The data transmission method described.   3. The data transmission method according to claim 2, wherein the step of generating the service information table inserts information indicating the presence or absence of metadata transmission for each service into a service description table as a service information table.   3. The data transmission method according to claim 2, wherein the step of generating the service information table inserts information indicating the presence / absence of metadata transmission for each broadcaster into a broadcaster information table as a service information table.   The step of generating the service information table inserts information indicating presence / absence of metadata transmission for each network or each transport stream into a network information table as a service information table. Data transmission method. The step of generating metadata includes generating metadata of a plurality of services in one service,
The step of generating the service information table includes inserting service type information indicating that a type of service generated by collectively combining a plurality of metadata is metadata dedicated data into the service information table. 2. The data transmission method according to 2. The step of generating the metadata includes generating service metadata in one service,
3. The data according to claim 2, wherein the step of generating the service information table inserts information for specifying a service having service metadata described in the service description table into the service information table. Delivery method.

Images