WO2015050175A1

WO2015050175A1 - Receiving device and receiving method

Info

Publication number: WO2015050175A1
Application number: PCT/JP2014/076333
Authority: WO
Inventors: 北里　直久
Original assignee: ソニー株式会社
Priority date: 2013-10-04
Filing date: 2014-10-01
Publication date: 2015-04-09

Abstract

An objective of the present invention is to desirably acquire transmission packets of each type from a transmission stream whereupon transmission packets of a plurality of types have been time-division multiplexed. A data stream whereupon transmission packets of a plurality of types are time-division multiplexed is received with a receiving unit. The transmission packets of each type are filtered and extracted from the received transmission stream with an extraction unit. As an example, the extraction unit is configured with hardware or firmware. As another example, the extraction unit comprises a plurality of filters which filter each of the transmission packets of the respective types. When a value of data of prescribed byte location of the transmission packet is a prescribed value, the filters filter and extract the transmission packets.

Description

Receiving apparatus and receiving method

The present technology relates to a receiving device and a receiving method, and more particularly to a receiving device that receives a transmission stream in which a plurality of types of transmission packets are time-division multiplexed.

Conventionally, digital broadcasting has been regulated and operated worldwide based on the MPEG2-TS system specifications. Over the course of 10-15 years after the start of operation, video coding technology has evolved and the demand for higher resolution and higher image quality has increased. On the other hand, with the spread and speeding up of the Internet, it has become possible to receive a video signal having an image quality equivalent to that of a broadcast via a communication path.

Under such circumstances, expectations for services that use broadcasting and communication in an integrated manner are increasing, and technically, sharing and integration of broadcasting and communication distribution specifications are required. As a result, as a broadcasting system specification, a method of transmitting by the IP method similar to the communication instead of the conventional MPEG2-TS method has been studied as a new broadcasting method (for example, see Non-Patent Document 1).

The purpose of the present technology is to make it possible to obtain each type of transmission packet satisfactorily from a transmission stream in which a plurality of types of transmission packets are time-division multiplexed.

The concept of this technology is
A receiving unit for receiving a transmission stream in which a plurality of types of transmission packets are time-division multiplexed;
The receiving apparatus includes an extraction unit that filters and extracts each type of transmission packet from the received transmission stream.

In this technology, the reception unit receives a transmission stream in which a plurality of types of transmission packets are time-division multiplexed. For example, the transmission packet may be a TLV (Type Length Value) packet. Then, each type of transmission packet is filtered and extracted from the received transmission stream by the extraction unit. For example, the extraction unit is configured by hardware or so-called firmware in which hardware and software are combined.

For example, the extraction unit has a plurality of filters for filtering each type of transmission packet, and this filter filters the transmission packet when the data value at a predetermined byte position of the transmission packet is at a predetermined value. And may be extracted. In this case, for example, the transmission packet is a variable length packet, and the filter is configured to filter and extract the entire transmission packet based on the packet length data included as one of header information of the transmission packet. May be.

In addition, for example, the extraction unit includes a filter for filtering transmission packets to be received by the CPU, a filter for filtering transmission packets of video data and / or audio data, and a filter for filtering clock data. May be. Here, the transmission packet of video data and / or audio data may be a multi-layer configuration packet having a multiplexed transport packet in an upper layer, for example, an MMT packet.

In addition, for example, the filter includes a shift register to which a transmission packet is input, a filter calculation unit that calculates whether a value of data at a predetermined byte position extracted from a register at a predetermined stage of the shift register is a predetermined value, A memory unit that holds a transmission packet output from the shift register as a filtered transmission packet when the calculation result that the filter calculation unit is at a predetermined value is obtained, and the shift register, the filter calculation unit, and the memory unit A filter control unit for controlling In this case, the shift register may be a variable shift register, and the filter control unit may set the number of stages of the shift register according to the type of transmission packet to be filtered.

According to the present technology, each type of transmission packet can be favorably acquired from a transmission stream in which a plurality of types of transmission packets are time-division multiplexed. Note that the effects described in the present specification are merely examples and are not limited, and may have additional effects.

It is a block diagram which shows the structural example of the transmission / reception system as embodiment. It is a figure which shows the stack model which shows the structural example of a broadcast signal. It is a figure which shows the structural example of the broadcast stream (broadcast signal) in the case of transmitting timed media (Timed | Media). It is a figure which shows the packet structure assumption (header part) in timed media (Timed | Media). It is a figure which shows the structural example of the broadcast stream (broadcast signal) in the case of transmitting a non-timed media (Non-Timed | Media). It is a figure which shows the structural example (Syntax) of the header (MMT | Packet | header) of the MMT packet which contains file data in a payload. It is a figure which shows the packet structure assumption (header part) in a non-timed media (Non-Timed | Media). It is a figure which shows the packet structure assumption (header part) in TLV-SI, the packet structure assumption in NTP, and the packet structure assumption (header part) in IP-SI. It is a figure which shows the packet structure assumption (header part) in MMT-SI. It is a block diagram which shows the structural example of a broadcast transmission system. It is a block diagram which shows the structural example of a receiver. It is a block diagram which shows the structural example of a demultiplexer. It is a figure for demonstrating filtering of the TLV packet containing TLV-SI in a TLV-SI filter. It is a figure for demonstrating filtering of the TLV packet containing NTP in an NTP filter, and filtering of the TLV packet containing IP-SI in an IP-SI filter. It is a figure for demonstrating filtering of the TLV packet containing MMT-SI in an MMT-SI filter. It is a figure for demonstrating the filtering of the TLV packet containing the time door set in a time door set filter, and the filtering of the TLV packet containing the non-time door set in a non-time door set filter. It is a filter branch diagram in a demultiplexer. It is a block diagram which shows the structural example of a demultiplexer. It is a block diagram which shows the structural example of a signaling / non-time door set filter part. It is a block diagram which shows the structural example of a signaling / non-time door set filter part. It is a figure which shows the control timing of the filter process in a signaling / non-time door set filter part. It is a block diagram which shows the structural example of an NTP filter part. It is a figure which shows the structural example of a time door set filter part.

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

<1. Embodiment>
[Configuration example of transmission / reception system]
FIG. 1 shows a configuration example of a transmission / reception system 10 as an embodiment. The transmission / reception system 10 includes a broadcast transmission system 100 and a receiver 200.

The broadcast transmission system 100 transmits an IP (Internet Protocol) broadcast signal including a transmission medium. There are two types of transmission media: timed media (non-timed media) and non-timed media (non-timed media). For example, timed media is stream data such as video, audio, and subtitles. Further, for example, non-timed media is file data such as HTML document data and other data.

The receiver 200 receives the above-described IP system broadcast signal transmitted from the broadcast transmission system 100. Then, the receiver 200 acquires transmission media such as video, audio, and file data from the broadcast signal, and presents images, sounds, and the like.

FIG. 2 is a stack model showing a configuration example of a broadcast signal. There is a physical layer (PHY) below. This physical layer includes a modulation scheme, an error correction scheme, and the like. Above this physical layer is a layer of TLV (Type Length Value) transmission packet. This TLV packet is a variable length packet.

* An IP packet is placed on top of this TLV transmission packet. There are IPv4 and IPv6 as IP, but IPv4 is assumed in this embodiment. Further, UDP (User Datagram Protocol) is placed on the IP packet.

MMT (MPEG Media Transport) packet is placed on this UDP. The payload part of this MMT packet includes MFU (MMT Fragment Unit) or signaling message (Signaling Message). As this MFU, stream data such as video and audio, HTML document data, and other file data such as other data are inserted.

Moreover, 64-bit data of NTP (Network Time Protocol) is placed on this UDP. Furthermore, IP-SI is placed on this UDP. This IP-SI is, for example, the same data as the signaling message (Signaling Message) included in the payload part of the MMT packet described above. In other words, this signaling message (Signaling Message) may be sent in the same layer as the MMT packet.

Also, a transmission control signal as signaling information is placed on the TLV transmission packet. This transmission control signal includes TLV-NIT and AMT. TLV-NIT is modulation frequency and broadcast service configuration information. AMT is an IP address related to a broadcast service. Both TLV-NIT and AMT are in section format.

FIG. 3 shows a configuration example of a broadcast stream (broadcast signal) in the case of transmitting timed media (Timed を Media). FIG. 3A shows a video elementary stream (Video ES). In this example, the encoded image data of each picture has a NAL (Network Abstraction Layer) unit configuration. This video elementary stream is divided into chunks of a predetermined size and arranged in the payload of an MFU (MMT Fragment Unit) as shown in FIG.

The MFU header (MFU Header) has a 13-byte structure. A fragmented MPU header (Fragmented MPU Header) is arranged in the first byte. In this fragmented MPU header, a 7-bit field of “FT” and a 1-bit field of “T” are provided in this order. “FT” indicates an MFU fragment type (MFU Fragment Type). “T” indicates whether it is timed media (Timed Media) or non-timed media (Non Timed Media). Here, it is set to “0”, indicating that it is timed media.

After this, the MFU header of timed media (Timed Media) is arranged. In this MPU header, a 32-bit field of “movie_fragment_sequence_number”, a 32-bit field of “sample_number”, a 16-bit field of “Offset”, an 8-bit field of “subsample_priority”, and an 8-bit field of “dependency_counter” are provided in this order. It has been.

“Movie_fragment_sequence_number” indicates the sequence number of the MFU in the MPU. “Sample_number” indicates an accumulated sample number of the MPU. “Offset” indicates an offset (from the top of mdat から box) of media data (Media data). “Subsample_priority” indicates the priority of this MFU in the MPU. “Dependency_counter” indicates the number of MFUs that are decoded depending on this MFU.

As shown in FIG. 3C, an MMT payload (MMT payload) is configured by adding an MMT payload header (MMT payload header) to the MFU. The MMT payload header has a structure of 11 bytes. This MMT payload header includes a 16-bit field of “length”, an 8-bit field of “type”, a 2-bit field of “fi”, a 1-bit field of “A”, a 1-bit field of “R”, and “M”. 1-bit field, “S” 3-bit field, “MPU_sequence_number” 32-bit field, “Frag_count” 8-bit field, and “DU_length” 16-bit field are provided in this order.

“Length” indicates the MMT payload length. “Type” indicates a data type. “0x00” and “0x01” indicate an MPU. “0x00” indicates that the data of the MMT payload is non-timed media (Non Timed Media), and “0x01” indicates that the data of the MMT payload is timed media (Timed Media). “0x02” indicates that the data of the MMT payload is a signaling message.

“F-i” indicates fragmentation information. “A” indicates whether or not there are a plurality of data units. “R” indicates the presence or absence of RAP (RandomandAccess Point). “M” indicates the presence / absence of “MPU_sequence_number”. “S” is a reserved area. “MPU_sequence_number” indicates the sequence number of the first MPU of the same packet ID. “Frag_count” indicates the number of a fragment. “DU_length” indicates the byte length of the data unit (data unit).

As shown in FIG. 3D, an MMT packet header (MMT packet header) is further added to the MMT payload to form an MMT packet (MMT packet). The MMT packet header has a 16-byte configuration. This MMT packet header includes a 2-bit field “V”, a 1-bit field “C”, a 2-bit field “FEC”, a 1-bit field “P”, a 1-bit field “E”, and “RES”. 9-bit field, “Packet_id” 16-bit field, “Packet_sequence_number” 32-bit field, “Timestamp” 32-bit field, and “Packet_counter” 32-bit field are provided in this order.

“V” indicates a version number. “C” indicates the presence / absence of “Packet_counter”. In this embodiment, it is assumed that “Packet_counter” exists. “FEC” indicates whether or not an FEC (Forward） Error Correction) is attached and what type it is attached. “P” indicates the presence / absence of “Private_user_data”. In this embodiment, it is assumed that there is no “Private_user_data”. “E” indicates the presence or absence of “header_extension”. Here, since it is timed media (Timed Media), it is set to “0”, indicating that there is no “header_extension”. “RES” is a reserved area.

“Packet_id” indicates a packet identification number. By this packet identification number, it is possible to identify an asset (Asset) included in the MMT payload, for example, video, audio, signaling message, and the like. “Packet_sequence_number” indicates a packet sequence number of the same packet identification number. “Timestamp” indicates the transmission time of the MMT packet (MMT packet). This “Timestamp” is used to absorb transmission jitter of the MMT packet on the receiving side. “Packet_counter” indicates the packet sequence number of all MMT packets.

As shown in FIG. 3 (e), a UDP header, an IP header, and a TLV header are added to the MMT packet to generate a TLV packet (TLV packet) constituting a broadcast stream. In addition, although illustration is abbreviate | omitted, as a TLV packet, the TLV packet containing the MMT packet of other transmission media, such as an audio | voice and a caption, exists further.

The UDP header has a structure of 8 bytes. In this UDP header, a 16-bit field of “Source port number”, a 16-bit field of “Destination port number”, a 16-bit field of “Data length”, and a 16-bit field of “Checksum” are provided in this order. . “Source port number” indicates a source port number. “Destination port number” indicates a destination port number. “Data length” indicates the data length. A specific signal can be identified by the source port number and the destination port number.

The IP header (IPv4 header) has a 20-byte structure. In this embodiment, it is assumed that there is no extension header in IPv4. This IP header has a 4-bit field of “version” at the top, a 32-bit field of “Source IP address” from 13 bytes to 16 bytes, and a 32-bit field of “Destination IP address” from 17 bytes to 20 bytes. “Version” indicates a version number. “Source IP address” indicates a source IP address. “Destination IP address” indicates a destination IP address.

In this embodiment, it is assumed that a specific broadcast channel has a specific IP address. Accordingly, a specific broadcast channel can be identified by “Source IP address” and “Destination IP address”. In the case of broadcasting, the destination address is, for example, a multicast address.

The TLV header has a 4-byte structure. In the TLV header, a synchronization signal field of “0x7F” is provided at the head, followed by an 8-bit field of “Packet type” and a 16-bit field of “Data length” in this order. “Packet type” indicates a packet type. “0x01” indicates an IPv4 packet. “0xFE” indicates a transmission control signal packet.

FIG. 4 collectively shows packet configuration assumptions (header portion) in the above-mentioned timed media (Timed Media). That is, in the case of timed media, it has a 4-byte TLV header, a 20-byte IP header, an 8-byte UDP header, a 16-byte MMT packet header, an 11-byte MMT payload header, and a 13-byte MFU header. Note that the IP header is a 1Pv4 header and has no extension header. Further, it is assumed that the MMT packet header does not have “private_user_data” and “header_extension”.

FIG. 5 shows a configuration example of a broadcast stream (broadcast signal) in the case of transmitting non-timed media. FIG. 5A shows file data (File data). Each of F1, F2, F3, F4, and F5 represents one file data. For example, F1 to F4 are file data used in a certain program, and F5 is file data used in the next program.

Since the file data of F1 to F4 has a small file size, they are arranged in the payload of the MFU as shown in FIG. 5 (b). On the other hand, since the file data of F5 has a large file size, as shown in FIG. 5B, the file data is divided into a plurality of pieces, here two pieces, and each is arranged in the payload of the MFU.

The MFU header (MFU Header) is composed of 5 bytes. A fragmented MPU header (Fragmented MPU Header) is arranged in the first byte. In this fragmented MPU header, a 7-bit field of “FT” and a 1-bit field of “T” are provided in this order. “FT” indicates an MFU fragment type (MFU Fragment Type). “T” indicates whether it is timed media (Timed Media) or non-timed media (Non Timed Media). Here, “1” is set, indicating that the media is non-timed.

After this, a 32-bit field of “item_ID” is provided. This “item_ID” indicates a file ID. Here, the file IDs of the MFUs in which the file data F1 to F5 are arranged in the payload have different values. It should be noted that the file IDs of the two MFUs in which the file data of F5-1 and F5-2, which are obtained by dividing the file data of F5, are arranged in the payload have the same value.

As shown in FIG. 5C, an MMT payload (MMT payload) is configured by adding an MMT payload header (MMT payload) to the MFU. In this case, the MFU having the file data of F1 to F4 has a small size and is therefore arranged in one MMT payload. On the other hand, each MFU having the file data F5-1 and F5-2 is arranged in one MMT payload. Although the detailed description is omitted, this MMT payload header has a structure of 11 bytes as in the case of the above-mentioned timed media (Timed Media).

Then, as shown in FIG. 5 (d), an MMT packet header (MMT packet header) is further added to the MMT payload to form an MMT packet (MMT packet). The MMT packet header has a 28-byte configuration in which a 12-byte extension is further provided in addition to the configuration of the above-mentioned timed media (Timed Media).

FIG. 6 shows a configuration example (Syntax) of an MMT packet header including file data in a payload, that is, an MMT packet header (MMT packet header). In this example, a 12-byte extension (header extension) is provided. A 16-bit field of “Type” indicates the type of this extension, and here indicates that a file transmission parameter is arranged.

The 16-bit field of “length” indicates the size of the extension, and indicates the number of subsequent bytes, here 8 bytes. The 24-bit field of “content_id” indicates an ID (content ID) that identifies content that is a specific unit of use as the entire file group to be transmitted. An 8-bit field of “content_version” indicates a version of content having a specific content ID. When a part of files constituting the content is updated, it is incremented by +1.

The 16-bit field of “Part_id” is an ID for identifying each divided part when the entire content is divided into each packet. A 16-bit field of “Number_of_parts” indicates the number of divided parts when the entire content is divided into packets. The “Part_id” and “Number_of_parts” are clues for acquiring data of all files constituting the content on the receiving side.

The MMT packet includes an MMT packet including a signaling message in the payload. Whether the payload includes a signaling message or transmission media (stream data, file data) can be identified by an 8-bit field of “Type” present in the MMT payload header.

As described above, in a certain program, the file data of F1 to F4 are repeatedly sent in the layer of the MMT packet stream. The signaling message sent in correspondence with the file data F1 to F4 includes content information composed of the file data F1 to F4. In the next program, the file data F5-1 and F5-2 are repeatedly sent in the layer of the MMT packet stream. The signaling message sent corresponding to the file data of F5-1 and F5-2 includes content information composed of the file data of F5-1 and F5-2.

As shown in FIG. 5 (e), a UDP header, an IP header, and a TLV header are added to the MMT packet to generate a TLV packet (TLV packet) constituting a broadcast stream. The UDP header, the IP header, and the TLV header have a structure of 8 bytes, 20 bytes, and 4 bytes, respectively, as in the case of the above-mentioned timed media (Timed Media), although detailed description is omitted.

FIG. 7 collectively shows packet configuration assumptions (header part) in the above-mentioned non-timed media. That is, in the case of non-timed media, it has a 4-byte TLV header, a 20-byte IP header, an 8-byte UDP header, a 28-byte MMT packet header, an 11-byte MMT payload header, and a 5-byte MFU header. Note that the IP header is a 1Pv4 header and has no extension header. Further, it is assumed that the MMT packet header does not have “private_user_data”.

FIG. 8A shows a packet configuration assumption (header part) in TLV-SI. Here, TLV-SI indicates a transmission control signal (TLV-NIT / AMT) (see FIG. 2) as signaling information carried on the above-described TLV transmission packet. In the case of TLV-SI, it has a 4-byte TLV header and an 8-byte section header. The section header includes an 8-bit field “table_id” and a 5-bit field “version_number”.

“Table_id” is an ID indicating a section type (table). In the case of TLV-NIT, “table_id” indicates TLV-NIT. Similarly, in the case of AMT, “table_id” indicates AMT. “Version_number” indicates a version number to be updated every time the content is changed.

FIG. 8B shows a packet configuration assumption in NTP. As described above, the NTP is placed on the UDP (see FIG. 2). In the case of NTP, it has a 4-byte TLV header, a 20-byte IP header, an 8-byte UDP header, and an 8-byte NTP. In this case, the port number (transmission source, destination) of this UDP header is a value indicating the NTP protocol. Also, the IP address (source and destination) of the IP header is a value corresponding to the broadcast channel.

FIG. 8C shows a packet configuration assumption (header part) in IP-SI. As described above, the IP-SI is placed on the UDP (see FIG. 2). In the case of IP-SI, it has a 4-byte TLV header, a 20-byte IP header, an 8-byte UDP header, and a 3-byte IP-SI header (IP-SI header). In the IP-SI header, a 16-bit field of “message_id” and an 8-bit field of “version” are provided in this order. “Message_id” indicates a value corresponding to the message type of IP-SI. “Version” indicates a version number to be updated every time the content is changed.

FIG. 9 shows a packet configuration assumption (header part) in MMT-SI. Here, as described above, MMT-SI indicates a signaling message (Signaling Message) (see FIG. 2) included in the payload portion of the MMT packet. For MMT-SI, the same 4-byte TLV header, 20-byte IP header, 8-byte UDP header, 16-byte MMT packet header, 11 bytes as in the case of timed media (see FIG. 4) In addition to the MMT payload header, it has a 3-byte signaling message header.

This signaling message header has the same configuration as the IP-SI header described above, and a 16-bit field of “message_id” and an 8-bit field of “version” are provided in this order. “Message_id” indicates a value corresponding to the message type of the signaling message. “Version” indicates a version number to be updated every time the content is changed.

[Configuration of broadcast transmission system]
FIG. 10 shows a configuration example of the broadcast transmission system 100. The broadcast transmission system 100 includes a clock unit 111, a signal transmission unit 112, a video encoder 113, an audio encoder 114, a signaling generation unit 116, and a file encoder 117. The broadcast transmission system 100 includes a TLV signaling generator 118, N IP service multiplexers 119-1 to 119-N, a TLV multiplexer 120, and a modulation / transmission unit 121.

The clock unit 111 generates time information (NTP time information) synchronized with time information acquired from an NTP (Network Time Protocol) server (not shown), and sends an IP packet including the time information to the IP service multiplexer 119-1. send. The signal transmission unit 112 is, for example, a studio of a TV station or a recording / reproducing device such as a VTR, and a file such as stream data such as video, audio, and subtitles as timed media, HTML document data as non-timed media, etc. Send data to each encoder.

The video encoder 113 encodes the video signal sent from the signal sending unit 112, further packetizes it, and sends an IP packet including a video MMT packet to the IP service multiplexer 119-1. The audio encoder 114 encodes and further packetizes the audio signal transmitted from the signal transmission unit 112, and sends an IP packet including an audio MMT packet to the IP service multiplexer 119-1.

The signaling generator 116 generates a signaling message and sends an IP packet including an MMT packet in which the signaling message is arranged in the payload part to the IP service multiplexer 119-1. Alternatively, the signaling generator 116 generates a signaling message, and sends an IP packet in which this signaling message is carried in UDP to the IP service multiplexer 119-1.

The file encoder 117 combines or divides the file data sent from the signal sending unit 112 as necessary to generate an MMT packet including the file data (see FIGS. 5C and 5D), and this MMT. The IP packet including the packet is sent to the IP service multiplexer 119-1. The IP service multiplexer 119-1 performs time division multiplexing of the IP packet sent from each encoder or the like. At this time, the IP service multiplexer 119-1 adds a TLV header to each IP packet to form a TLV packet.

The IP service multiplexer 119-1 constitutes one channel portion included in one transponder. The IP service multiplexers 119-2 to 119-N have the same function as that of the IP service multiplexer 119-1, and constitute other channel portions included in one transponder.

The TLV signaling generating unit 118 generates signaling (Signaling) information, and generates a TLV packet in which this signaling (Signaling) information is arranged in the payload portion. The TLV multiplexer 120 multiplexes the TLV packets generated by the IP service multiplexers 119-1 to 119-N and the TLV signaling generation unit 118 to generate a broadcast stream (see FIGS. 3 (e) and 5 (e)). Is generated. The modulation / transmission unit 121 performs RF modulation processing on the broadcast stream generated by the TLV / multiplexer 120 and transmits the result to the RF transmission line.

The operation of the broadcast transmission system 100 shown in FIG. 10 will be briefly described. In the clock unit 111, time information synchronized with the time information acquired from the NTP server is generated, and an IP packet including the time information is generated. This IP packet is sent to the IP service multiplexer 119-1.

The video signal sent from the signal sending unit 112 is supplied to the video encoder 113. In this video encoder 113, the video signal is encoded and further packetized to generate an IP packet including a video MMT packet. This IP packet is sent to the IP service multiplexer 119-1. The same processing is also performed on the audio signal sent from the signal sending unit 112. The IP packet including the audio MMT packet generated by the audio encoder 114 is sent to the IP service multiplexer 119-1.

In the signaling generator 116, a signaling message is generated, and an IP packet including an MMT packet in which the signaling message is arranged in the payload part, or an IP packet on which this signaling message is placed on UDP is generated. This IP packet is sent to the IP service multiplexer 119-1.

Also, the file data sent from the signal sending unit 112 is supplied to the file encoder 117. The file encoder 117 combines or divides file data as necessary, generates an MMT packet including the file data, and further generates an IP packet including the MMT packet. This IP packet is sent to the IP service multiplexer 119-1.

The IP service multiplexer 119-1 performs time division multiplexing of the IP packet sent from each encoder and the signaling generator 116. At this time, a TLV header is added to each IP packet to form a TLV packet. The IP service multiplexer 119-1 processes one channel portion included in one transponder, and the IP service multiplexers 119-2 to 119-N perform other processes included in the one transponder. The channel portion is processed in the same manner.

TLV packets obtained by the IP service multiplexers 119-1 to 119-N are sent to the TLV multiplexer 120. The TLV / multiplexer 120 also receives a TLV packet in which signaling information is placed in the payload portion from the TLV signaling generator 118.

In the TLV multiplexer 120, the TLV packets generated by the IP service multiplexers 119-1 to 119-N and the TLV signaling generator 118 are multiplexed to generate a broadcast stream. This broadcast stream is sent to the modulation / transmission unit 121. The modulation / transmission unit 121 performs RF modulation processing on the broadcast stream, and sends the RF modulation signal to the RF transmission path.

[Receiver configuration]
FIG. 11 shows a configuration example of the receiver 200. The receiver 200 includes a CPU 201, a tuner / demodulator 202, a demultiplexer 203, a system clock generator 204, a video decoder 205, an audio decoder 206, an application display data generator 207, and a combiner 208. Have.

The CPU 201 constitutes a control unit and controls the operation of each unit of the receiver 200. The tuner / demodulation unit 202 receives the RF modulation signal, performs demodulation processing, and obtains a broadcast stream (see FIGS. 3E and 5E). The demultiplexer 203 performs demultiplex processing and depacketization processing on this broadcast stream to obtain NTP time information, PTS (presentation time information), signaling information, video and audio encoded signals, and further a file Output data. Here, for example, file data constitutes data broadcast content.

The system clock generation unit 204 generates a system clock STC synchronized with the time information based on the NTP time information obtained by the demultiplexer 203. The video decoder 205 decodes the encoded video signal obtained by the demultiplexer 203 to obtain a baseband video signal. The audio decoder 206 decodes the encoded audio signal obtained by the demultiplexer 203 to obtain a baseband audio signal.

The application display data generation unit 207 obtains data broadcast display data based on the file data obtained by the demultiplexer 203 under the control of the CPU 201. In the broadcast stream, file data of the same content is repeatedly sent. The CPU 201 controls the filtering operation in the demultiplexer 203 so that only necessary file data is acquired in the demultiplexer 203.

The CPU 201 controls the decoding timing in each decoder based on PTS (presentation time information) and adjusts the presentation timing of video and audio. The synthesizer 208 synthesizes the display data of the data broadcast generated by the application display data generator 207 with the baseband video signal obtained by the video decoder 205 to obtain a video signal for video display. Note that the baseband audio signal obtained by the audio decoder 206 is an audio signal for audio output.

The operation of the receiver 200 shown in FIG. 11 will be briefly described. The tuner / demodulator 202 receives an RF modulation signal transmitted through the RF transmission path, performs demodulation processing, and obtains a broadcast stream (see FIGS. 3 (e) and 5 (e)). This broadcast stream is sent to the demultiplexer 203.

In this demultiplexer 203, demultiplex processing and depacketization processing are performed on this broadcast stream, and NTP time information, signaling information, video, audio encoded signals, file data constituting the data broadcast content, and the like. Extracted.

Various signaling information extracted by the demultiplexer 203 is sent to the CPU 201 via the CPU bus 209. This signaling information includes TLV-SI, IP-SI, and MMT-SI. As described above, TLV-SI is a transmission control signal (TLV-NIT / AMT) placed on a TLV transmission packet, IP-SI is signaling information placed on UDP, and MMT-SI is an MMT packet. Is a signaling message as signaling information included in the payload portion (see FIG. 2). The CPU 201 controls the operation of each unit of the receiver 200 based on this signaling information.

NTP time information extracted by the demultiplexer 203 is sent to the system clock generation unit 204. The system clock generation unit 204 generates a system clock STC synchronized with the time information based on the NTP time information. This system clock STC is supplied to the video decoder 205 and the audio decoder 206.

The encoded video signal extracted by the demultiplexer 203 is sent to the video decoder 205 and decoded to obtain a baseband video signal. The file data extracted by the demultiplexer 202 is sent to the CPU 201 via the CPU bus 209. The CPU 201 analyzes the file data, performs layout processing and rendering processing, and instructs the application display data generation unit 207 to generate display data. The application display data generation unit 207 generates data broadcast display data based on this instruction.

The video signal obtained by the video decoder 205 is supplied to the synthesis unit 208. The display data generated by the application display data generation unit 207 is supplied to the synthesis unit 208. The synthesizing unit 208 synthesizes these video signals and display data to obtain a video signal for video display. Also, the encoded audio signal extracted by the demultiplexer 203 is sent to the audio decoder 206 and decoded to obtain a baseband audio signal for audio output.

[Demultiplexer configuration]
The demultiplexer 203 will be further described. In this embodiment, the demultiplexer 203 is configured by hardware logic. FIG. 12 shows a configuration example of the demultiplexer 203.

The demultiplexer 203 includes a TLV-SI filter 301, a TLV-SI cache 302, an NTP filter 303, an IP-SI filter 304, an IP-SI cache 305, an MMT-SI filter 306, and an MMT-SI cache 307. have. The demultiplexer 203 also includes a video asset filter 308, a de-jitter buffer 309, an audio asset filter 310, a de-jitter buffer 311, and a non-time door. It has a set (Non-Timed フィルタ Asset) filter 312 and a non-time door set cache 313.

Each filter (module) is supplied from the tuner / demodulator 202 with a broadcast stream (TLV packet stream) and a packet sync (Sync) synchronized with the head timing of each TLV packet. Each filter filters and extracts the TLV packet when the value of data at a predetermined byte position of the TLV packet is a predetermined value. In this embodiment, each filter filters and extracts the entire TLV packet based on the packet length data included as one of the header information of the TLV packet.

The TLV-SI filter 301 filters TLV packets including TLV-SI. As described above, TLV-SI is a transmission control signal (TLV-NIT / AMT) as signaling information carried on a TLV transmission packet. As shown in FIG. 13, the TLV packet including this TLV-SI has a 4-byte TLV header (TLV-h) and an 8-byte section header (Section h).

In this case, the value indicating the packet type of the byte Byte No = 1 is “0xFE”, indicating a transmission control signal. Further, the value indicating the version number of the byte with Byte No. = 9 is different from the previous value when the contents are updated. When the transmission control signal is TLV-NIT, the value indicating the table identification of Byte No. = 4 is “0x40”, indicating TLV-NIT. When the transmission control signal is AMT, the value indicating the table identification of the byte of Byte No. = 4 is “0xFE”, indicating AMT. When the transmission control signal is AMT, the value indicating the table identification extension of the byte of Byte No. = 7-8 is “0x0000”.

Therefore, when the TLV-SI filter 301 performs a new acquisition of TLV-NIT, the value indicating the packet type of the byte of Byte No = 1 is “0xFE” and indicates the table identification of Byte No = 4. It is determined whether the value is “0x40”, and a TLV packet that satisfies this condition is extracted. In addition, when the TLV-SI filter 301 performs update acquisition of TLV-NIT, the value indicating the packet type of the byte of Byte No = 1 is “0xFE” and indicates the table identification of Byte No = 4. It is determined whether or not the value indicating the version number of the byte with Byte No = 9 is “0x40”, and a TLV packet satisfying this condition is extracted.

In addition, when the TLV-SI filter 301 acquires a new AMT, the value indicating the packet type of the byte with Byte No = 1 is “0xFE”, and the value indicating the table identification with Byte No = 4 is set. It is determined whether “0xFE” and the value indicating the table identification extension of the byte Byte No = 7-8 is “0x0000”, and a TLV packet satisfying this condition is extracted. In addition, when the TLV-SI filter 301 performs update acquisition of the AMT, the value indicating the packet type of the byte of Byte No = 1 is “0xFE”, and the value indicating the table identification of Byte No = 4 is set. A value indicating the table identification extension of the byte of Byte No = 7-8 is “0xFE”, and the value indicating the version number of the byte of Byte No = 9 is different from the previous value. And a TLV packet that satisfies this condition is extracted.

The TLV-SI filter 301 uses, for example, information of a 4-byte TLV header and an 8-byte section header in the TLV packet for the above-described determination. Therefore, the TLV-SI filter 301 can be configured using, for example, a 12-byte shift register.

Referring back to FIG. 12, the TLV-SI cache 302 temporarily stores TLV packets including transmission control signals (TLV-NIT, AMT) extracted by the TLV-SI filter 301. The CPU 201 extracts the stored transmission control signal (TLV-NIT, AMT) from the TLV-SI cache 302 through the CPU bus 209 and uses it.

The NTP filter 303 filters the TLV packet including the NTP and sends it to the system clock generation unit 204. As described above, the NTP is 64-bit time information placed on the UDP. As shown in FIG. 14, the TLV packet including the NTP has a 4-byte TLV header (TLV-h), a 20-byte IP header (IP-h), and an 8-byte UDP header (UDP-h).

In this case, the value indicating the packet type of the byte Byte No = 1 is “0x01”, indicating an IPv4 packet. Further, the IP address (source, destination) of the byte with Byte No. = 16-23 is an address corresponding to the broadcast channel. Further, the port number (transmission source, destination) of the byte of Byte No = 24-27 is a value indicating the NTP protocol.

Therefore, when the NTP filter 303 acquires the NTP, the value indicating the packet type of the byte of Byte No = 1 is “0x01” and the IP address of the byte of Byte No = 16-23 is the broadcast channel. And the port number of the byte with Byte No = 24-27 is a value indicating the NTP protocol, and a TLV packet satisfying this condition is extracted.

For example, the NTP filter 303 uses, for example, a 4-byte TLV header, a 20-byte IP header, and an 8-byte UDP header information in the TLV packet. Only the first 4 bytes are sufficient. Therefore, the NTP filter 303 can be configured using a 28-byte shift register.

Returning to FIG. 12, the IP-SI filter 304 filters the TLV packet including the IP-SI. As described above, the IP-SI is signaling information placed on the UDP. As shown in FIG. 14, the TLV packet including the IP-SI includes a 4-byte TLV header (TLV-h), 20 bytes. IP header (IP-h), 8-byte UDP header (UDP-h), and 3-byte IP-SI header (IP-SI-h).

In this case, the value indicating the packet type of the byte Byte No = 1 is “0x01”, indicating an IPv4 packet. Further, the IP address (source, destination) of the byte of Byte No = 16-23 is an address corresponding to IP-SI. The port number (transmission source, destination) of the byte with Byte No = 24-27 is a value indicating IP-SI. Also, the byte value of Byte No. = 32-33 is a value corresponding to the IP-SI message type. Further, the value indicating the version number of Byte No. = 34 is different from the previous value when the contents are updated.

Therefore, when the IP-SI filter 304 performs a new acquisition of the IP-SI, the value indicating the packet type of the byte of Byte No = 1 is “0x01” and the byte of Byte No = 16-23 The IP address is an address corresponding to IP-SI, the byte port number of Byte No = 24-27 is a value indicating IP-SI, and the byte value of Byte No = 32-33 is IP-SI. It is determined whether the value corresponds to the message type of SI, and a TLV packet that satisfies this condition is extracted.

In addition, when the IP-SI filter 304 performs update acquisition of the IP-SI, the value indicating the packet type of the byte of Byte No = 1 is “0x01” and the byte of Byte No = 16-23 The IP address is an address corresponding to IP-SI, the byte port number of Byte No = 24-27 is a value indicating IP-SI, and the byte value of Byte No = 32-33 is IP-SI. It is determined whether the value corresponding to the message type of SI and the value indicating the version number of the byte of Byte No = 34 is different from the previous value, and a TLV packet satisfying this condition is extracted.

For the above-described determination, the IP-SI filter 304 includes, for example, a 4-byte TLV header, a 20-byte IP header, an 8-byte UDP header, and a 3-byte IP-SI header in the TLV packet. Use information. Therefore, this IP-SI filter 301 can be configured using, for example, a 35-byte shift register.

Returning to FIG. 12, the IP-SI cache 305 temporarily accumulates the TLV packets including the IP-SI extracted by the IP-SI filter 304. The CPU 201 retrieves the stored IP-SI from the IP-SI cache 305 through the CPU bus 209 and uses it.

The MMT-SI filter 306 filters TLV packets including MMT-SI. The MMT-SI is a signaling message included in the payload part of the MMT packet as described above. As shown in FIG. 15, the TLV packet including the MMT-SI includes a 4-byte TLV header (TLV-h), a 20-byte IP header (IP-h), an 8-byte UDP header (UDP-h), It has a 16-byte MMT packet header (MMT-h), an 11-byte MMT payload header (MMT-payload-h), and a 3-byte MMT-SI header (MMT-SI-h).

In this case, the value indicating the packet type of the byte Byte No = 1 is “0x01”, indicating an IPv4 packet. Further, the IP address (source, destination) of the byte with Byte No. = 16-23 is an address corresponding to the broadcast channel. The port number (transmission source, destination) of the byte with Byte No. = 24-27 is a value indicating the MMP protocol. Further, the value indicating the packet ID of the byte with Byte No = 34-35 is a value indicating the signaling packet. Also, the byte value of Byte No = 59-60 is a value corresponding to specific MMT-SI information. Further, the value indicating the version number of Byte No. = 61 is different from the previous value when the contents are updated.

Therefore, when the MMT-SI filter 306 acquires a new MMT-SI, the value indicating the packet type of the byte of Byte No. = 1 is “0x01” and the byte of Byte No = 16-23 The IP address is an address corresponding to the broadcast channel, the byte port number of Byte No = 24-27 is a value indicating the MMT protocol, and the byte value of Byte No = 33-35 indicates a signaling packet. It is determined whether it is a value, and a TLV packet that satisfies this condition is extracted.

When the MMT-SI filter 306 acquires and updates the MMT-SI, the value indicating the packet type of the byte of Byte No = 1 is “0x01”, and the byte of Byte No = 16-23 The IP address is an address corresponding to the broadcast channel, the byte port number of Byte No = 24-27 is a value indicating the MMT protocol, and the byte value of Byte No = 33-35 indicates a signaling packet. And the byte value of Byte No = 59-60 is a value corresponding to the specific MMT-SI information, and the value indicating the version number of Byte No = 61 is different from the previous value. And a TLV packet that satisfies this condition is extracted.

For the above-described determination, the MMT-SI filter 306 includes, for example, a 4-byte TLV header, a 20-byte IP header, an 8-byte UDP header, a 16-byte MMT packet header in the TLV packet, Information of 11-byte MMT payload header and 3-byte MMT-SI header is used. Therefore, the MMT-SI filter 306 can be configured using, for example, a 62-byte shift register.

Returning to FIG. 12, the MMT-SI cache 307 temporarily accumulates the TLV packets including the MMT-SI extracted by the MMT-SI filter 306. The CPU 201 retrieves the stored MMT-SI from the MMT-SI cache 307 through the CPU bus 209 and uses it.

The video asset filter 308 filters TLV packets including video assets (video signals) that are timed media. As described above, the video asset is inserted as an MFU (MMT パケット Fragment Unit) in the payload of the MMT packet. The audio asset filter 310 filters TLV packets including an audio asset (audio signal) that is a timed media (TimedTimeMedia). As described above, the audio asset is inserted as an MFU (MMT パケット Fragment Unit) in the payload of the MMT packet.

As shown in FIG. 16, a TLV packet including timed media includes a 4-byte TLV header (TLV-h), a 20-byte IP header (IP-h), an 8-byte UDP header (UDP-h), 16 It has a byte MMT packet header (MMT-h).

In this case, the value indicating the packet type of the byte Byte No = 1 is “0x01”, indicating an IPv4 packet. Further, the IP address (source, destination) of the byte with Byte No. = 16-23 is an address corresponding to the broadcast channel. The port number (transmission source, destination) of the byte with Byte No. = 24-27 is a value indicating the MMP protocol. Further, the value indicating the packet ID of a byte with Byte No = 34-35 is a value corresponding to a specific asset (signal).

Therefore, in the video asset filter 308 and the audio asset filter 310, the value indicating the packet type of the byte of Byte No = 1 is “0x01”, and the IP address of the byte of Byte No = 16-23 is used as the broadcast channel. The corresponding address, the byte number of Byte No = 24-27 is a value indicating the MMT protocol, and the byte value of Byte No = 34-35 is a value corresponding to a video signal and an audio signal. It is determined whether there is a TLV packet that satisfies this condition.

For example, the video asset filter 308 and the audio asset filter 310 are each configured to include, for example, a 4-byte TLV header, a 20-byte IP header, an 8-byte UDP header, and 16 bytes in the TLV packet. MMT packet header information is used. Therefore, the video asset filter 308 and the audio asset filter 310 can be configured using, for example, a 48-byte shift register.

Referring back to FIG. 12, the de-jitter buffer 309 temporarily accumulates the TLV packet including the video asset extracted by the video asset filter 308. The video assets of each TLV packet accumulated in the de-jitter buffer 309 in this way are read at a timing corresponding to the time stamp inserted in the MMT packet header and accumulated in the video decoder buffer 205a. The de-jitter buffer 309 absorbs the transmission jitter of the MMT packet including the video signal.

Also, the de-jitter buffer 311 temporarily accumulates TLV packets including the audio asset extracted by the audio asset filter 310. The audio asset of each TLV packet stored in the de-jitter buffer 311 in this way is read at the time indicated by the time stamp inserted in the MMT packet header and stored in the audio decoder buffer 206a. The de-jitter buffer 311 absorbs the transmission jitter of the MMT packet including the audio signal.

The non-time door set filter 312 filters TLV packets including file data that is non-timed media. As described above, the file data is inserted into the payload of the MMT packet as MFU (MMT Fragment Unit). As shown in FIG. 16, a TLV packet including file data includes a 4-byte TLV header (TLV-h), a 20-byte IP header (IP-h), an 8-byte UDP header (UDP-h), and 28 bytes. MMT packet header (MMT-h). Here, since the MMT packet header has a 12-byte extension, the number of bytes is increased by 12 bytes compared to the MMT packet header in the above-mentioned timed media (see FIG. 6).

Also, the value indicating the byte content ID (Content_ID) of Byte No. = 52-54 is a value corresponding to the specific content. Further, the value indicating the version number of the byte content of Byte No = 55 is different from the previous value when the content is updated. The value indicating the byte part ID (Part_ID) of Byte No. = 56-59 is a value corresponding to a specific part.

Therefore, when a new acquisition is made, the non-time door set filter 312 has a value indicating the packet type of the byte of Byte ＝ No = 1 as “0x01” and the IP address of the byte of Byte No = 16-23 corresponds to the broadcast channel. Byte No. = 24-27 byte port number is a value indicating the MMT protocol, Byte No. = 34-35 byte value is a value corresponding to the file data, and Byte It is determined whether the byte value of No = 52-54 is a value corresponding to a specific content, and whether the byte value of Byte No = 56-59 is a value corresponding to a specific part, and this condition is satisfied. Extract the TLV packet. At the time of update acquisition, a condition is added that the value indicating the version number of the byte content of Byte No = 55 is different from the previous value.

For the above-described determination, the non-time door set filter 312 includes, for example, a 4-byte TLV header, a 20-byte IP header, an 8-byte UDP header, and a 28-byte MMT packet header in the TLV packet. Use information. Therefore, the non-time door set filter 312 can be configured using, for example, a 60-byte shift register.

FIG. 17 shows a filter branching diagram in the demultiplexer 203 of FIG. 12 described above. That is, a TLV packet including TLV-SI is filtered through determination based on a TLV header (TLV-h) and a section header (Section-h). Further, the TLV packet including the NPT is filtered through the determination based on the TLV header (TLV-h), the IP header (IP-h), and the UDP header (UDP-h).

Also, a TLV packet including IP-SI is filtered through determination based on a TLV header (TLV-h), an IP header (IP-h), a UDP header (UDP-h), and a message header (Message-h). A TLV packet including MMT-SI includes a TLV header (TLV-h), an IP header (IP-h), a UDP header (UDP-h), an MMT packet header (MMT-h), and an MMY payload header (MMT- Filtered through judgment based on payload-h) and message header (Message-h).

In addition, TLV packets including time door sets or non-time door sets are respectively TLV header (TLV-h), IP header (IP-h), UDP header (UDP-h), and MMT packet header (MMT-h). And it is filtered through the judgment by the MMY payload header (MMT-payload-h). In this case, however, the size of the MMT packet header (MMT-h) differs depending on whether it is a time door set or a non-time door set.

The configuration example of the demultiplexer 203 in FIG. 18 is a more generalized configuration of the demultiplexer 203 in FIG. The demultiplexer 203 includes a signaling / non-time door set filter unit 321-1 to 321-N, a video time door set filter unit 322, a video time door set filter unit 323, and an NTP filter unit 324. is doing.

Here, the signaling / non-time door set filter units 321-1 to 321-N correspond to the TLV-SI filter 301 and the TLV-SI cache 302, the IP-SI filter 304 and the IP-SI cache 305 in FIG. This corresponds to a set of the MMT-SI filter 306 and the MMT-SI cache 307, the non-time door set filter 312 and the non-time door set cache 313, respectively.

The signaling / non-time door set filter units 321-1 to 321-N temporarily store the TLV packet in the cache when the data value at the predetermined byte position of the TLV packet is at the predetermined value, and then the CPU 201 Are common in a configuration in which the signaling information or the non-time door set is read out and used through the CPU bus 209 and is the same module in hardware.

Further, the time door set filter unit 322 corresponds to a set of the video asset filter 308 and the de-jitter buffer 309 in FIG. 12 described above. The time door set filter unit 322 is configured to send the TLV packet to the video decoder 205 side after absorbing the transmission jitter by the de-jitter buffer 309 when the value of the data at the predetermined byte position of the TLV packet is a predetermined value. It is. The time door set filter unit 322 is a specific part of the video decoder 205 in the subsequent stage, and is a dedicated module.

The time door set filter unit 323 corresponds to the set of the audio asset filter 310 and the de-jitter buffer 311 in FIG. 12 described above. The time door set filter unit 323 is configured to send the TLV packet to the audio decoder 206 side after absorbing the transmission jitter by the de-jitter buffer 311 when the data value at the predetermined byte position of the TLV packet is a predetermined value. It is. The time door set filter unit 323 is a specific part called the audio decoder 206 in the subsequent stage, and is a dedicated module.

The NTP filter unit 324 corresponds to the NTP filter 303 in FIG. 12 described above. The NTP filter unit 324 is configured to send 64-bit information of NTP included in the TLV packet to the system clock generation unit 204 when the value of data at a predetermined byte position of the TLV packet becomes a predetermined value. The NTP filter unit 324 is a specific part called the system clock generation unit 204 in the subsequent stage, and is a dedicated module.

FIG. 19 shows a configuration example of the signaling / non-time door set filter unit 321 (321-1 to 321-N). The signaling / non-time door set filter unit 321 includes a filter control unit 411, a filter calculation unit 412, a variable shift register 413, a CPU port 414, and a cache memory (FIFO) 415.

The filter control unit 411 controls the operation of each unit of the signaling / non-time door set filter unit 321. The filter control unit 411 is supplied with a packet sync (Sync) synchronized with the head timing of each TLV packet. Based on a command received from the CPU 201 through the CPU port 414, the filter control unit 411 controls the operation of each unit according to information to be filtered (TLV-SI, IP-SI, MMT-SI, non-time door set).

The variable shift register 413 receives the TLV packet stream output from the tuner / demodulator 202 in byte units. The variable shift register 413 sequentially shifts the TLV packet stream to the subsequent stage in synchronization with the transmission clock. The filter control unit 411 sets the number of shift stages in the variable shift register 413 according to information to be filtered (TLV-SI, IP-SI, MMT-SI, non-time door set).

The number of shift stages is the number of stages required to simultaneously acquire header information for determining whether the TLV packet includes information to be filtered when the input TLV packet is shifted from the head. is there. For example, 12 levels are set for TLV-SI, 35 levels for IP-SI, 62 levels for MMT-SI, and 60 levels for non-time door sets (see FIGS. 12 to 16). .

For each TLV packet, the filter calculation unit 412 evaluates whether the header information obtained from the variable shift register 413, that is, the value of data at a predetermined byte position of the TLV packet is a predetermined value, and calculates whether the filter path is ignored or not. The result is sent to the filter control unit 411. In this case, the calculation result is a filter path when the data value at the predetermined byte position is at the predetermined value, and is ignored otherwise. The filter control unit 411 sends a predetermined byte to the filter calculation unit 412 for the above-described evaluation calculation in accordance with information to be filtered (TLV-SI, IP-SI, MMT-SI, non-time door set). A position and a predetermined value are set in advance.

For example, in the case of new acquisition of TLV-NIT, 1 byte and 4 bytes are set as a predetermined byte position, and “0xFE” and “0x40” are set as predetermined values (see FIG. 13). Also, for example, in the case of TLV-NIT update acquisition, 1 byte, 4 bytes, and 9 bytes are set as the predetermined byte positions, and “0xFE”, “0x40”, and “other than the previous value” are set as the predetermined values. It is set (see FIG. 13). Although detailed description is omitted, the same applies to other cases (see FIGS. 13 to 16).

The cache memory 415 temporarily accumulates the TLV packet output from the variable shift register 413 under the control of the filter control unit 411 when it is the calculation result of the filter path. Information (TLV-SI, IP-SI, MMT-SI, non-time door set) stored in the cache memory 415 is read out and used by the CPU 201 through the CPU port 414. In this case, the CPU 201 sequentially reads and uses information (data) written in the cache memory 415 by an interrupt process accompanying polling or writing.

FIG. 20 also shows a configuration example of the signaling / non-time door set filter unit 321. 20, portions corresponding to those in FIG. 19 are denoted by the same reference numerals, and detailed description thereof is omitted as appropriate. FIG. 20 shows the configuration of the variable shift register 413 in FIG. 19 in more detail.

The variable shift register 413 has a one-shot register group 503 including R1-Rn registers 501-1 to 501-n, a selector 502, and OR1-ORn one-shot registers connected in series. The selector 502 is supplied with a shift register (SR) stage select signal from the filter control unit 411, and a stage for taking out an output signal is set.

As a result, the number of stages of the variable shift register 413 is used to simultaneously acquire header information for determining whether or not the TLV packet includes information to be filtered when the input TLV packet is shifted from the head. The number of stages required for For example, 12 levels are set for TLV-SI, 35 levels for IP-SI, 62 levels for MMT-SI, and 60 levels for non-time door sets (see FIGS. 12 to 16). .

The one-shot registers OR1 to ORn of the one-shot register group 503 latch the outputs of the registers 501-1 to 501-n based on the one-shot enable signal supplied from the filter control unit 411, respectively. The filter control unit 411 generates a one-shot enable signal at a timing when the input TLV packet is shifted by the number of stages set as described above.

Thus, the header information necessary for determining whether the TLV packet includes information to be filtered is simultaneously latched in part or all of the one-shot registers OR1 to ORn. This header information is supplied to the filter calculation unit 412, and as described above, whether or not the value of the data at the predetermined byte position is a predetermined value is calculated and the calculation result is sent to the filter control unit 411.

Then, when it is the calculation result of the filter path, a cache write enable signal is supplied from the filter control unit 411 to the cache memory 415, and the TLV packet output from the variable shift register 413 is written into the cache memory 415. At this time, the filter control unit 411 sets the generation period of the cache write enable signal based on the packet length data included as the header information of the TLV packet. As a result, the entire TLV packet output from the variable shift register 413 is written into the cache memory 415.

FIG. 21 shows the control timing of the filter processing in the signaling / non-time door set filter unit 321. FIG. 21A shows a transmission clock synchronized with each byte of the TLV packet stream. FIG. 21B is a packet sync (Sync) indicating the head timing of the TLV packet. FIG. 21C shows a TLV packet stream (shift register input data) input to the variable shift register 413.

FIG. 21D shows a one-shot enable signal supplied from the filter control unit 411 to the one-shot registers OR1 to ORn. This one-shot enable signal is generated at the timing when the input TLV packet is shifted by N stages. This N is the number of stages required to simultaneously acquire header information for determining whether the TLV packet includes information to be filtered when the input TLV packet is shifted from the head. Also, the number of setting stages of the variable shift register 413.

FIG. 21 (e) shows the calculation result of the filter calculation unit 412. At the timing when the one-shot enable signal is generated from the filter control unit 411, header information for determining whether the TLV packet includes information to be filtered is simultaneously included in some or all of the one-shot registers OR1 to ORn. Latched. The filter calculation unit 412 calculates whether the value of the data at the predetermined byte position is a predetermined value among the header information latched in this way, and sends the calculation result to the filter control unit 411.

FIG. 21 (f) shows a TLV packet stream (shift register selector output data) output from the variable shift register 413 and therefore the selector 502. FIG. 21G shows a cache write enable signal supplied from the filter control unit 411 to the cache memory 415. The filter control unit 411 generates a cache write enable signal when the calculation result is a filter path, and controls sequential writing of TLV packets to the cache memory 415. As a result, the entire TLV packet that has passed through the set number of shift register stages is written into the cache memory 415.

FIG. 22 shows a configuration example of the NTP filter unit 324. The NTP filter unit 324 includes a filter control unit 611, a filter calculation unit 612, a variable shift register 613, a CPU port 614, and an NTP register 615.

The filter control unit 611 controls the operation of each unit of the NTP filter unit 324. The filter control unit 611 is supplied with a packet sync (Sync) synchronized with the head timing of each TLV packet. The filter control unit 611 controls the operation of each unit according to information (NTP) to be filtered based on a command received from the CPU 201 through the CPU port 614.

The variable shift register 613 receives a TLV packet stream output from the tuner / demodulator 202 in byte units. The variable shift register 613 sequentially shifts the TLV packet stream to the subsequent stage in synchronization with the transmission clock. The filter control unit 611 sets the number of shift stages in the variable shift register 613 according to information (NTP) to be filtered. This shift stage number is used to simultaneously acquire header information necessary to determine whether the TLV packet includes information (NTP) to be filtered when the input TLV packet is shifted from the head. The number of steps. For example, 28 levels are set (see FIG. 14).

The filter calculation unit 612 evaluates, for each TLV packet, whether the header information obtained from the variable shift register 613, that is, the data value at a predetermined byte position of the TLV packet is a predetermined value, and calculates whether the filter path is ignored or not. The result is sent to the filter control unit 611. In this case, the calculation result is a filter path when the data value at the predetermined byte position is at the predetermined value, and is ignored otherwise.

Note that the filter control unit 611 presets a predetermined byte position and a predetermined value in the filter calculation unit 612 for the above-described evaluation calculation in accordance with information (NTP) to be filtered. For example, 1 byte, 16-23 bytes, and 24-27 bytes are set as predetermined byte positions, and “0xFE”, “value corresponding to a broadcast channel”, and “value indicating NTP protocol” are set as predetermined values. (See FIG. 14).

The NTP register 615 temporarily stores the TLV packet output from the variable shift register 613 under the control of the filter control unit 611 when the result is the calculation result of the filter path. Information (NTP) stored in the NTP register 615 is supplied to the system clock generation unit 204.

Although detailed description is omitted, the configuration of the variable shift register 613 is the same as the configuration of the variable shift register 413 of the signaling / non-time door set filter unit 321 of FIG. 19 described above (see FIG. 20).

FIG. 23 shows a configuration example of the time door set filter unit 320 (322, 323). The time door set filter unit 320 includes a filter control unit 711, a filter calculation unit 712, a variable shift register 713, a CPU port 714, a dejitter buffer 715, and a dejitter control unit 716.

The filter control unit 711 controls the operation of each unit of the time door set filter unit 320. The filter control unit 711 is supplied with a packet sync (Sync) synchronized with the head timing of each TLV packet. Based on a command received from the CPU 201 through the CPU port 714, the filter control unit 711 controls the operation of each unit according to information to be filtered (time door set).

The variable shift register 713 receives the TLV packet stream output from the tuner / demodulator 202 in byte units. The variable shift register 713 sequentially shifts the TLV packet stream to the subsequent stage in synchronization with the transmission clock. The filter control unit 711 sets the number of shift stages in the variable shift register 713 according to information to be filtered (time door set).

This shift stage number is a stage number for simultaneously obtaining header information for judging whether the TLV packet includes information to be filtered when the input TLV packet is shifted from the head. For example, 48 stages are set (see FIG. 16).

The filter calculation unit 712 evaluates, for each TLV packet, whether the header information obtained from the variable shift register 713, that is, the value of the data at a predetermined byte position of the TLV packet is a predetermined value, and calculates whether the filter path is ignored. The result is sent to the filter control unit 711. In this case, the calculation result is a filter path when the data value at the predetermined byte position is at the predetermined value, and is ignored otherwise. The filter control unit 711 presets a predetermined byte position and a predetermined value in the filter calculation unit 712 for the above-described evaluation calculation in accordance with information to be filtered (time door set).

For example, 1 byte, 16-23 bytes, 24-27 bytes, 34-35 are set as the predetermined byte positions, and “0xFE”, “value corresponding to the broadcast channel”, “value indicating the NTP protocol” are set as the predetermined values. , “Value corresponding to a specific asset (signal)” is set (see FIG. 16).

The de-jitter buffer 715 temporarily accumulates the TLV packet output from the variable shift register 713 under the control of the filter control unit 711 when it is the calculation result of the filter path. The information (time door set) accumulated in the de-jitter buffer 715 is read by the de-jitter control unit 716 at a timing according to the time indicated by the time stamp (timestamp) inserted in the MMT packet header, and the decoder buffer It is sent to the (video decode buffer 205a, audio decode buffer 206a) with transmission jitter absorbed.

Although detailed description is omitted, the configuration of the variable shift register 713 is the same as the configuration of the variable shift register 413 of the signaling / non-time door set filter unit 321 of FIG. 19 described above (see FIG. 20).

As described above, in the transmission / reception system 10 illustrated in FIG. 1, the demultiplexer 203 of the receiver 200 includes a plurality of filters configured by hardware logic that filters and extracts each type of TLV packet from the TLV packet stream. Part (extraction part), and each type of TLV packet can be acquired satisfactorily.

<2. Modification>
In the above embodiment, an example in which the multiplexed transport packet is an MMT packet has been described. However, the present technology can be similarly applied when the multiplexed transport packet is an RTP (Real-Time Transport Protocol) packet.

In the above-described embodiment, the demultiplexer 203 as the extraction unit has been described as being configured with hardware logic. However, it is also conceivable to configure the demultiplexer 203 with so-called firmware that combines hardware and software. Even in such a case, it is needless to say that the present technology can be applied.

Moreover, this technique can also take the following structures.
(1) a receiving unit that receives a transmission stream in which a plurality of types of transmission packets are time-division multiplexed;
A receiving apparatus comprising: an extraction unit that filters and extracts each type of transmission packet from the received transmission stream.
(2) The extraction unit
A plurality of filters for filtering each type of transmission packet;
The receiving device according to (1), wherein the filter filters and extracts the transmission packet when a data value at a predetermined byte position of the transmission packet is a predetermined value.
(3) The transmission packet is a variable length packet,
The receiving device according to (2), wherein the filter filters and extracts the entire transmission packet based on packet length data included as one of header information of the transmission packet.
(4) The extraction unit
A filter for filtering transmission packets to be received data into the CPU;
A filter for filtering transmission packets of video data and / or audio data;
The receiving apparatus according to (2) or (3), further including a filter that filters clock data.
(5) The reception device according to (4), wherein the transmission packet of the video data and / or the audio data is a multi-layer configuration packet having a multiplexed transport packet in an upper layer.
(6) The reception device according to (5), wherein the multiplexed transport packet is an MMT packet.
(7) The filter is
A shift register to which the transmission packet is input;
A filter calculation unit for calculating whether the value of the data at the predetermined byte position fetched from the register at a predetermined stage of the shift register is at the predetermined value;
A memory unit that holds a transmission packet output from the shift register as the filtered transmission packet when the filter calculation unit obtains a calculation result indicating that the value is at a predetermined value;
The receiving apparatus according to any one of (2) to (6), further including a filter control unit that controls the shift register, the filter operation unit, and the memory unit.
(8) The shift register is a variable shift register,
The filter control unit
The receiving device according to (7), wherein the number of stages of the shift register is set according to a type of the transmission packet to be filtered.
(9) The receiving device according to any one of (1) to (8), wherein the transmission packet is a TLV packet.
(10) The receiving device according to any one of (1) to (9), wherein the extraction unit includes hardware or a combination of hardware and software.
(11) a reception step of receiving a transmission stream in which a plurality of types of transmission packets are time-division multiplexed;
A receiving method comprising: an extracting step of filtering and extracting each type of transmission packet from the received transmission stream by an extraction unit.

A main feature of the present technology is that a receiver that receives a TLV packet stream including a plurality of types of TLV packets includes a plurality of filter units (extraction units) that filter and extract each type of TLV packet. Thus, each type of TLV packet can be acquired well (see FIG. 12).

DESCRIPTION OF SYMBOLS 10 ... Transmission / reception system 100 ... Broadcast transmission system 111 ... Clock part 112 ... Signal transmission part 113 ... Video encoder 114 ... Audio encoder 116 ... Signaling generation part 117 ... File Encoder 118... TLV signaling generation unit 119-1 to 119-N... IP service multiplexer 120... TLV and multiplexer 121... Modulation / transmission unit 200.
202: Tuner / demodulator 203 ... Demultiplexer 204 ... System clock generator 205 ... Video decoder 205a ... Video decoder buffer 206 ... Audio decoder 206a ... Audio decoder buffer 207 ..Application display data generation unit 208... Synthesis unit 301... TLV-SI filter 302... TLV-SI cache 303... NTP filter 304. Cache 306 ... MMT-SI filter 307 ... MMT-SI cache 308 ... Video asset filter 309 ... Dejitter buffer 310 ... Audio asset filter 311 ... Dejitter buffer 312 ... Non Time door set Filter 313: Non-time door set cache 321, 321-1 to 321-N: Signaling / non-time door set

filter unit

320, 322, 323 ... Time door set filter unit 324: NTP filter unit 411: Filter control unit 412: Filter operation unit 413: Variable shift register unit 414: CPU port 415: Cache memory (FIFO)
501-1 to 501-n. Register 502 ... Selector 503 ... One-shot register group 611 ... Filter control unit 612 ... Filter operation unit 613 ... Variable shift register 614 ... CPU Port 615 NTP register 711 Filter control unit 712 Filter operation unit 713 Variable shift register 714 CPU port 715 Dejitter buffer 716 Dejitter control unit

Claims

A receiving unit for receiving a transmission stream in which a plurality of types of transmission packets are time-division multiplexed;
A receiving apparatus comprising: an extraction unit that filters and extracts each type of transmission packet from the received transmission stream.
The extraction unit
A plurality of filters for filtering each type of transmission packet;
The receiving device according to claim 1, wherein the filter filters and extracts the transmission packet when the value of data at a predetermined byte position of the transmission packet is a predetermined value.
The transmission packet is a variable length packet,
The receiving apparatus according to claim 2, wherein the filter filters and extracts the entire transmission packet based on packet length data included as one of header information of the transmission packet.
The extraction unit
A filter for filtering transmission packets to be received data into the CPU;
A filter for filtering transmission packets of video data and / or audio data;
The receiving device according to claim 2, further comprising a filter that filters clock data.
The receiving apparatus according to claim 4, wherein the transmission packet of the video data and / or the audio data is a multi-layer configuration packet having a multiplexed transport packet in an upper layer.
The receiving apparatus according to claim 5, wherein the multiplexed transport packet is an MMT packet.
The above filter
A shift register to which the transmission packet is input;
A filter calculation unit for calculating whether the value of the data at the predetermined byte position fetched from the register at a predetermined stage of the shift register is at the predetermined value;
A memory unit that holds a transmission packet output from the shift register as the filtered transmission packet when the filter calculation unit obtains a calculation result indicating that the value is at a predetermined value;
The receiving device according to claim 2, further comprising: a filter control unit that controls the shift register, the filter operation unit, and the memory unit.
The shift register is a variable shift register,
The filter control unit
The receiving apparatus according to claim 7, wherein the number of stages of the shift register is set according to a type of transmission packet to be filtered.
The receiving device according to claim 1, wherein the transmission packet is a TLV packet.
The receiving device according to claim 1, wherein the extraction unit is configured by hardware or a combination of hardware and software.
A reception step of receiving a transmission stream in which a plurality of types of transmission packets are time-division multiplexed;
A receiving method comprising: an extracting step of filtering and extracting each type of transmission packet from the received transmission stream by an extraction unit.