JP2021106402A - Receiving device and receiving method - Google Patents

Abstract

To transmit control information about display switching of application, in a data broadcast transmission system based on an MMT system.SOLUTION: When a data asset management table is updated at time t2, a receiver checks the content thereof. The receiver has switched to execution of app3, i.e., a program non-linked application, during a period of time t1-t2, but since a pullback control descriptor is not arranged in the loop of asset 804 of the program non-linked application in the updated data asset management table, the app3 is ended immediately. As a result, the receiver can automatically start the app6, specified as the entry application after the time t2, just as required by a broadcasting station.SELECTED DRAWING: Figure 9

Description

The technology disclosed in the present specification relates to a transmitting device and a transmitting method for transmitting data by a predetermined transport method, and a receiving device and a receiving method, and in particular, MMT (MPEG Media) for data broadcasting application and control information related to the transmission thereof. The present invention relates to a transmitting device and a transmitting method for transmitting by a Transport) method, and a receiving device and a receiving method.

Digital broadcasting can provide various textual information such as news and weather forecasts, which is called data broadcasting, and interactive services. The data broadcasting application in operation at the time of the present application is described by the BML (Broadcast Markup Language) method defined by ARIB (Association of Radio Industries and Business and Broadcast) STD-B24.

Data broadcasting applications can be broadly divided into program-linked data broadcasting applications linked to broadcast programs and program-non-linked data broadcasting applications that are not particularly linked to broadcast programs, such as news and weather forecasts. The contents of a program-linked data broadcasting application are basically renewed as the broadcasting program is switched. Therefore, there is a request on the broadcasting station side to forcibly switch to the program-linked data broadcasting application and display it when the broadcasting program is switched while the program non-linked data broadcasting application is being executed. In a conventional broadcasting system that transmits a data broadcasting application in BML (Broadcast Markup Language) format to a data carousel, it is possible to forcibly return to a desired data broadcasting application by signaling a pullback flag (returnto_entry_flag) (for example,). See Patent Document 1).

Further, as a next-generation digital broadcasting system, an ultra-high resolution TV broadcasting standard based on the MMT (MPEG Media Transport) system, which is standardized as a new media transport system by MPEG, is being studied. In the MMT method, it is easy to use different transmission lines in combination, and it can be commonly used for a plurality of transmission lines for broadcasting and communication.

WO2006 / 075590

An object of the technique disclosed herein is to provide an excellent transmitter and transmission method, as well as a receiver and receiver, capable of suitably transmitting control information relating to transmission of a data broadcasting application.

The present application has been made in consideration of the above problems, and the technique according to claim 1 is based on the above-mentioned problems.
A transmitter that transmits each component that constitutes a broadcasting service as a transmission unit based on a predetermined transport method, and
An information transmission unit that transmits control information related to the transmission of the component, and
Equipped with
The information transmitting unit transmits control information regarding the pullback of the data broadcasting application transmitted from the transmitting unit.
It is a transmitter.

According to the technique according to claim 2 of the present application, in the transmission device according to claim 1, the predetermined transport method is MMT.

According to the technique according to claim 3 of the present application, the information transmission unit of the transmission device according to claim 1 is entered in conjunction with a broadcast program composed of video and audio components transmitted from the transmission unit. -It is configured to send control information instructing to pull back to the application.

According to the technique according to claim 4 of the present application, the information transmission unit of the transmission device according to claim 1 is in a first table showing control information regarding transmission of an application component transmitted by the transmission unit. , The pullback control descriptor instructing the pullback to the entry application is stored and sent on a component-by-component basis.

According to the technique according to claim 5 of the present application, the information transmission unit of the transmission device according to claim 4 stores the pullback control descriptor indicating the pullback target for each component for each component. It is configured to send the table.

According to the technique of claim 6 of the present application, the information transmitter of the transmitter according to claim 1 pulls back to the entry application in a second table showing information about the presentation unit of the data broadcasting application. It is configured to store and send a pullback control descriptor in the presentation unit.

According to the technique according to claim 7, the information transmitting unit of the transmitting device according to claim 6 stores the pullback control descriptor indicating a pullback target in a presentation unit for each data content. It is configured to send 2 tables.

According to the technique according to claim 8 of the present application, the information transmitting unit of the transmitting device according to claim 1 enters an entry application in a third table showing information about a data broadcasting application for each data content. The pullback control descriptor instructing the pullback of is stored and transmitted for each data content.

According to the technique according to claim 9 of the present application, the transmission unit of the transmission device according to claim 8 groups the files constituting the data broadcasting application into transmission units based on the predetermined transport method and transmits the files. Then, the information transmission unit is configured to transmit the third table in which the pullback control descriptor indicating the pullback target in transmission units is stored for each data content.

According to the technique according to claim 10, the information transmitting unit of the transmitting device according to claim 1 instructs a pullback to return to the entry application in a fourth table showing the operation control of the application. It is configured to store and send control descriptors for each application.

According to the technique according to claim 11 of the present application, the information transmission unit of the transmission device according to claim 10 stores the pullback control descriptor that specifies the application to be started next for each application. It is configured to send a table of.

According to the technique of claim 12 of the present application, the information transmitter of the transmitter according to claim 1 is a common descriptor applied to all applications in a fourth table showing the operation control of the application. It is configured to store and send a pullback control descriptor that directs pullback to the entry application.

According to the technique of claim 13 of the present application, the information transmitting unit of the transmitting device according to claim 12 indicates the pullback control description indicating the identification information of the application to be terminated for pulling back to the entry application. It is configured to send the fourth table with its children arranged as the common descriptor.

Further, the technique according to claim 14 of the present application is:
A transmission step in which each component constituting a broadcasting service is transmitted as a transmission unit based on a predetermined transport method, and
An information transmission step for transmitting control information regarding the transmission of the component, and
Have,
The information transmission step transmits control information regarding the pullback of the data broadcasting application transmitted in the transmission step.
It is a transmission method.

Further, the technique according to claim 14 of the present application is:
A receiver that receives each component of the broadcasting service transmitted in transmission units based on a predetermined transport method, and
An information receiving unit that receives control information related to the transmission of the component, and
Equipped with
The information receiving unit receives control information regarding the pullback of the data broadcasting application received by the receiving unit.
It is a receiving device.

Further, the technique according to claim 16 of the present application is:
A reception step that receives each component of a broadcasting service transmitted in transmission units based on a predetermined transport method, and
An information receiving step for receiving control information regarding the transmission of the component, and
Have,
In the information receiving step, control information regarding the pullback of the data broadcasting application received in the receiving step is received.
It is a receiving method.

According to the technique disclosed herein, it is possible to provide an excellent transmission device and transmission method, and a reception device and reception method capable of suitably transmitting control information regarding transmission of a data broadcasting application.

According to the technique disclosed in the present specification, for example, in a broadcasting system for transmitting a data broadcasting application based on the MMT method, an excellent transmission device and a transmission method capable of suitably transmitting control information regarding display switching of the application. , And a receiving device and a receiving method can be provided.

The effects described in the present specification are merely examples, and the effects of the present invention are not limited thereto. In addition, the present invention may exert additional effects in addition to the above effects.

Still other objectives, features and advantages of the techniques disclosed herein will become apparent by more detailed description based on embodiments and accompanying drawings described below.

FIG. 1 is a diagram schematically showing a configuration example of a digital broadcasting system 10 to which the technique disclosed in the present specification is applied. FIG. 2 is a diagram showing a protocol stack 200 of a broadcasting system using the MMT method. FIG. 3 is a diagram showing a configuration example of a broadcast transmission system 11 that transmits the broadcast signal shown in FIG. FIG. 4 is a diagram showing a configuration example of the receiver 12 that receives the broadcast signal shown in FIG. FIG. 5 is a diagram showing an image of a broadcast signal 500 transmitted from the broadcast transmission system 11 to the broadcast transmission line according to the MMT / TLV method. FIG. 6 is a diagram showing a mechanism for designating each asset of the package from the MP table in the PA message. FIG. 7 is a diagram for explaining a mechanism for acquiring a file constituting a data broadcasting application transmitted by MMT. FIG. 8 is a diagram showing an operation example of forcibly pulling back the application. FIG. 9 is a diagram showing a syntax example 900 of a data asset management table (DAMT) transmitted by a data transmission message. FIG. 10 is a diagram showing syntax example 1000 of the descriptor of the pullback control to the entry application placed in the data asset management table. FIG. 11 is a diagram showing a syntax example 1100 of a data content management table (DCCT). FIG. 12 is a diagram showing a syntax example 1200 of the data content management table used in the third embodiment. FIG. 13 is a diagram showing a syntax example 1300 of the descriptor of the pullback control to the entry application arranged in the information area of the data content of the data content management table. FIG. 14 is a diagram showing a syntax example 2000 of MH AIT (application information table). FIG. 15 is a diagram showing a syntax example 1500 of a descriptor (Forced_Return_descriptor) for pullback control to an entry application arranged in a loop of application information of MH-AIT. FIG. 16 is a diagram showing a syntax example 1600 of a pullback control descriptor (Forced_Return_descriptor) arranged in a common descriptor of MH-AIT. FIG. 17 is a flowchart showing a processing procedure for the receiver to control the execution of the data broadcasting application.

Hereinafter, embodiments of the techniques disclosed in the present specification will be described in detail with reference to the drawings.

FIG. 1 schematically shows a configuration example of a digital broadcasting system 10 to which the technique disclosed in the present specification is applied. The illustrated digital broadcasting system 10 includes a broadcasting transmission system 11 and a receiver 12.

The broadcast transmission system 11 applies the MMT method to the transmission of broadcast signals, and transmits each component constituting the broadcast service as an IP packet. Specifically, the code of the video signal and audio signal of the broadcast program, and the signal of the content (data broadcasting application, etc.) and the subtitle related to the broadcast program are put on the MMTP payload and converted into an MMTP packet, which is transmitted as an IP packet. Will be done. Further, these IP packets are transmitted in the form of TLV packets on the broadcast transmission line. Here, the components related to the main body of the broadcast program such as video, audio, and subtitles are timed media. In addition, content used for data broadcasting (such as a data broadcasting application described in an HTML: HyperText Transfer Protocol) format is non-timed media.

On the other hand, the receiver 12 receives the IP packet sent from the broadcast transmission system 11 on the broadcast transmission line. The receiver 12 and the receiver 12 decode the transmission media such as video, audio, and subtitles from the received packet, and present the image and audio. Further, when the receiver 12 acquires each file data for data broadcasting from the received packet, the receiver 12 activates an application engine such as an HTML browser to present data broadcasting linked to the broadcast program.

FIG. 2 shows a protocol stack 200 of a broadcasting system using the MMT method.

One broadcasting service is composed of video 201, audio 202, subtitle 203, application 204, and content download 205 components. The video 201 is encoded 211 in the HEVC (High Efficiency Video Coding) format, the audio 202 is encoded 212 in the AAC (Advanced Audio Coding) format, and the subtitle 203 is next film encoded 213. Application 204 also includes an EPG (Electronic Program Guide), but is encoded 214 in HTML5 format.

On the MMT layer 220, the coding components 211 to 214 of these timed media and non-timed media are made into MPU format and put on the MMTP payload to be MMTP packetized. Further, MMT-SI (signaling Information) 221 which is control information (indicating the configuration of a broadcast program) related to MMT which is a media transport method is also put on an MMTP payload and converted into an MMTP packet. The data transmission method 215 of the content download 205 includes four types: a subtitle / character super transmission method, an application transmission method, an event / message transmission method, and a general-purpose data transmission method, but detailed description thereof will be omitted.

In UDP (User Datagram Protocol) / IP layer 230, MMTP packets are converted into IP packets. Also, the NTP (Network Time Protocol) packet 206 containing the current time information for the timed media is also converted into an IP packet. Further, these IP packets are converted into TLV packets by the TLV layer 240 and transmitted on the broadcast transmission line 250 which is the lowest physical layer. Further, the TLV-SI241 related to the TLV multiplexing format for multiplexing IP packets is also converted into a TLV packet and transmitted on the broadcast transmission line 250. The transmission slot in which the TLV packet is multiplexed is identified by using the TLV stream identification information (TLV_stream_id) from the TMCC (Transmission and Multiplexing Control) signal 251 of the transmission line.

FIG. 3 shows a configuration example of the broadcast transmission system 11 that transmits the broadcast signal shown in FIG. The broadcast transmission system 11 corresponds to, for example, a key station (program production station) that is the producer of the main body of the broadcast program. The illustrated broadcast transmission system 11 includes a clock unit 301, a signal transmission unit 302, a video encoder 303, an audio encoder 304, a caption encoder 305, a signaling encoder 306, a file encoder 307, and an electronic device. It includes a data processing system (Electronic Data Processing System: EDPS) 308, a TLV signaling encoder 309, an IP service multiplexer (MUX) 310, a TLV multiplexer (MUX) 311 and a modulator / transmitter 312. ..

The clock unit 301 generates time information synchronized with the time information acquired from the NTP server (not shown), and sends an IP packet including this time information to the IP service multiplexer 310.

The signal transmission unit 302 is, for example, a recording / playback device for a studio of a TV broadcasting station, a VTR, or the like, and is a timed media such as video, audio, subtitles, or other stream data, or a non-timed media for a data broadcasting application. -The data (HTML document data, etc.) is sent to the video encoder 303, the audio encoder 304, the caption encoder 305, and the file encoder 307, respectively.

The EDPS308 is a scheduler of a TV broadcasting station and a source of files, and is a non-timed media data broadcasting application, control information indicating the configuration of a broadcast program, and control information related to IP packet multiplexing, respectively, as a file encoder. 307, Signaling Encoder 306, TLV Signaling Encoder 309.

The video encoder 303 HEVC-encodes the video signal transmitted from the signal transmission unit 302, further packetizes it, and sends an IP packet including an MMT packet of the video signal to the IP service multiplexer 310. Further, the audio encoder 304 AAC-encodes the audio signal transmitted from the signal transmission unit 302, further packetizes it, and sends an IP packet including the MMT packet of the audio signal to the IP service multiplexer 310. Further, the caption encoder 305 encodes the subtitle signal transmitted from the signal transmission unit 302, further packetizes it, and sends an IP packet including the MMT packet of the subtitle to the IP service multiplexer 310.

The signaling encoder 306 generates a signaling message (MMT-SI) describing control information indicating the configuration of a broadcast program, etc., based on the information transmitted from the EDPS 308, and the signaling message is arranged in the payload section. The IP packet including the MMT packet is sent to the IP service multiplexer 310. In the present embodiment, the signaling message is roughly classified into three types: PA (Package Access) message, M2 section message, and data transmission message.

The file encoder 307 encodes the data broadcasting application transmitted from the signal transmission unit 302 or the EDPS 308 into HTML5 format file data, further packets the data, and transmits the IP packet including the MMT packet to the IP service multiplexer 310. send.

The broadcast transmission system 11 is equipped with an IP service multiplexer 310 for each channel (broadcast program) to be transmitted. The one-channel IP service multiplexer 310 multiplexes IP packets containing each of the video, audio, subtitles, signaling message (MMT-SI), and data broadcasting applications sent from each encoder 303-307. Then, a TLV packet constituting one broadcasting service (channel) is generated.

The TLV signaling encoder 309 generates a TLV packet in which the control information (TLV-SI) relating to the multiplexing of the IP packet described above is arranged in the payload unit based on the information transmitted from the EDPS 308.

The TLV multiplexer 311 multiplexes the TLV packets generated by each IP service multiplexer 310-1 to 10-N and the TLV signaling encoder 309 to generate a TLV stream identified by the TLV stream identification information. ..

The modulation / transmission unit 312 performs RF modulation processing on the TLV stream generated by the TLV multiplexer 311 and sends it to the broadcast transmission line.

The operation of the broadcast transmission system 11 shown in FIG. 3 will be described.

The clock unit 301 generates time information synchronized with the time information acquired from an NTP server (not shown), and generates an IP packet including this time information.

The video signal transmitted from the signal transmission unit 302 is supplied to the video encoder 303. In the video encoder 303, the video signal is HEVC-encoded and further packetized to generate an IP packet including an MMT packet of the HEVC-encoded video signal. This IP packet is sent to the IP service multiplexer 310.

Further, the same processing is performed on the audio signal and the subtitle signal transmitted from the signal transmission unit 302. That is, an IP packet including an MMT packet of an AAC-encoded audio signal generated by the audio encoder 304 is sent to the IP service multiplexer 310, and an MMT packet of a caption-encoded signal generated by the caption encoder 305 is sent. The including IP packet is sent to the IP service multiplexer 310.

Further, in the signaling encoder 306, a signaling message (MMT-SI) describing control information indicating the configuration of a broadcast program or the like is generated based on the information transmitted from the EDPS 308, and this signaling message is arranged in the payload section. An IP packet including the generated MMT packet is generated. This IP packet is sent to the IP service multiplexer 310.

Further, the data broadcasting application transmitted from the signal transmission unit 302 or the EDPS 308 is supplied to the file encoder 307. In the file encoder 307, the data broadcasting application is encoded in the HTML5 format, further packetized, and an IP packet including this MMT packet is generated. This IP packet is sent to the IP service multiplexer 310.

In each IP service multiplexer 310, an IP packet containing each of video, audio, subtitles, signaling message (MMT-SI), and file data (HTML5 document) sent from each encoder 303 to 307 is multi-ported. It is plexed to generate TLV packets that make up one channel.

The TLV signaling encoder 309 generates a TLV packet in which the control information (TLV-SI) relating to the multiplexing of the above IP packets is arranged in the payload unit based on the information transmitted from the EDPS 308.

In the TLV multiplexer 311, the TLV packets generated by each IP service multiplexer 310-1 to 10-N and the TLV signaling encoder 309 are multiplexed to generate a TLV stream. The modulation / transmission unit 312 performs RF modulation processing on the TLV stream generated by the TLV multiplexer 311 and sends the RF modulation signal to the broadcast transmission line.

FIG. 4 shows a configuration example of the receiver 12 that receives the broadcast signal shown in FIG. The receiver 12 shown is a tuner / demodulation unit 401, a demultiplexer (DEMUX) 402, a clock recovery unit 403, a video decoder 404, an audio decoder 405, a caption decoder 406, and a system control unit. It includes a 407, an application control unit 408, a cache memory 408, an application engine 409, an IP interface (I / F]) 410, and a synthesis unit 411. The illustrated receiver 12 includes, for example, a television receiver and a set-top box installed in the home, as well as a retransmitter of IPTV and CATV.

The tuner / demodulation unit 401 selects and receives a broadcast signal, performs demodulation processing, and obtains a TLV stream. The demultiplexer 402 performs demultiplexing processing and depackaging processing on the TLV stream. In this embodiment, the demultiplexer 402 includes a TLV filter 402-1, an IP filter 402-2, a UDP filter 402-3, an MMT filter 402-4, and an SI filter 402-5.

The TLV filter 402-1 filters the TLV packets to be broadcast and transmitted based on the TLV stream identification information. The IP filter 402-2 filters IP packets from TLV packets based on the IP address, and also filters IP packets received via the IP interface 410. In addition, the UDP filter 402-3 filters UDP packets. The MMT filter 402-4 filters the MMTP packet from the IP packet based on the information in the MMTP header (described later), and puts the video, audio, subtitles, and each coding component of the application on the MMTP packet. It is distributed to the video decoder 404, the audio decoder 405, the caption decoder 406, and the application engine 409. The SI filter 402-5 filters the signaling information SI and distributes it to the system control unit 407 and the application control unit 408, respectively. The SI filter 402-5 shall include an MMT-SI filter that filters MMT-SI from the MMT stream and a TLV-SI filter that filters TLV-SI from the TLV stream.

The clock recovery unit 403 generates time information synchronized with this time information based on the current time information contained in the NTP packet filtered by the IP filter 402-2 and the UDP filter 402-3 in the demultiplexer 402. Then, each timed media is output to the video decoder 404, the audio decoder 405, and the caption decoder 406 to decode each timed media.

The video decoder 404 decodes the coded video signal obtained by the demultiplexer 402 to obtain a baseband video signal. Further, the audio decoder 405 decodes the coded audio signal obtained by the demultiplexer 402 to obtain a baseband audio signal. Further, the caption decoder 406 decodes the subtitle coded signal obtained by the demultiplexer 402 to obtain the subtitle display signal.

The application control unit 408 controls the processing of the data broadcasting application based on the signaling information received via the SI filter 402-5. For example, when the application control unit 407 analyzes the MMT-SI and finds the data broadcasting application set as the default entry, the application control unit 409 instructs the application engine 409 to perform the data broadcasting presentation process.

In the broadcasting system 10 according to the present embodiment, it is assumed that the data broadcasting application is transmitted from two systems of the broadcasting signal and the IP network. In the former system, it is received by the tuner / demodulation unit 401, and in the latter system, it is received by the IP interface 410. In both cases, the MMT packet packetized in the demultiplexer 402 is sent to the application engine 409 by the MMT filter 402-4. It is sorted.

The application engine 409 is, for example, an HTML browser or the like, and processes file data (HTML5 document or the like) which is an entity of a data broadcasting application to generate a data broadcasting display signal. The application engine 409 can also acquire file data (monomedia used for displaying data broadcasting, linked applications, etc.) from the IP network via the IP interface 410, which is necessary for displaying data broadcasting. ..

The system control unit 410 controls the operation of each unit of the receiver 12 based on the signaling information received via the SI filter 402-5, the operation information from the user via the user operation unit (not shown), and the like. .. Further, the system control unit 410 controls the decoding timing in each of the decoders 404 to 406 based on the signaling information, and adjusts the presentation timing of the video, audio, and subtitles. The compositing unit 411 synthesizes the subtitle display signal and the data broadcasting display signal with the baseband video signal to obtain a video signal for video display. Further, the baseband audio signal obtained by the audio decoder 405 becomes an audio signal for audio output. The main part of the broadcast program composed of video signals and audio signals is output as video and audio from a monitor display (not shown). Further, the data broadcasting processed by the data broadcasting application engine 409 is also displayed superimposed on the screen of the main part of the broadcast program on the monitor display.

The IP interface 410 is composed of, for example, a network interface card, connects to an IP network such as the Internet or a home network, and performs transmission / reception processing of IP packets.

Further, in the present embodiment, it is assumed that the IP packet filtered based on the IP address by the IP filter 402-2 is transmitted or retransmitted from the IP interface 410 to the IP network. Further, if it is found that the broadcasting service can be filtered only by the IP address, the specific service can be extracted only by the IP filter 402-2 in the demultiplexer 402 and transferred from the receiver 12 to the outside.

The operation of the receiver 12 shown in FIG. 4 will be described.

The tuner / demodulation unit 401 receives the broadcast signal, performs demodulation processing, and obtains a TLV stream. In the demultiplexer 402, the TLV stream is subjected to demultiplexing processing and packetizing processing, and NTP time information, video, audio, subtitles, data broadcasting encoded signals, and signaling information are extracted. The information is distributed to the video decoder 404, the audio decoder 405, the caption decoder 406, the application engine 409, the system control unit 407, and the application control unit 408, respectively. Further, the IP packet received by the IP interface 410 is also subjected to the demultiplexing process and the packetization process in the same manner, and is distributed to each part.

Further, the NTP packet extracted by the demultiplexer 402 is distributed to the clock recovery unit 403. The clock recovery unit 403 generates time information synchronized with this time information based on the time information carried in the NTP packet. That is, the clock recovery unit 403 generates time information that matches the time information generated by the clock unit 301 on the broadcast transmission system 11 side.

The coded video signal extracted by the demultiplexer 402 is sent to the video decoder 404 for decoding, and a baseband video signal is obtained. Further, the subtitle coded signal extracted by the demultiplexer 402 is sent to the caption decoder 406 for decoding, and a subtitle display signal is obtained.

The application control unit 408 controls the processing of the data broadcasting application based on the signaling information received via the SI filter 402-5. The application engine 409 including an HTML browser processes the coded signal (HTML5 document) of the data broadcasting application extracted by the demultiplexer 402 according to the instruction from the application control unit 408, and displays the data broadcasting display signal. Is obtained.

In the synthesis unit 411, the display signal of the subtitle and the display signal of the data broadcasting are combined with the video signal of the baseband, and the video signal for screen display is obtained. Further, the encoded audio signal extracted by the demultiplexer 402 is sent to the audio decoder 405 for decoding, and a baseband audio signal for audio output is obtained. Then, the video signal and the audio signal are output from a monitor display (not shown).

In the digital broadcasting system 10 shown in FIG. 1, it is assumed that a broadcasting signal is transmitted from the broadcasting transmitting system 11 to the receiver 12 by the MMT method. FIG. 5 shows an image of a broadcast signal 500 transmitted from the broadcast transmission system 11 to the broadcast transmission line according to the MMT method.

The broadcast signal of one service (channel: broadcast program) is timed media related to the main part of the broadcast program such as video, audio, and subtitles, and non-timed media such as file data used for data broadcasting linked to the broadcast program. Consists of media. The media data in which these are encoded is converted into an MPU format, converted into an MMTP packet, and transmitted as an IP packet. In addition, signaling information (MMT-SI) related to MMT, which is a media transport method (indicating the configuration of a broadcast program, etc.), is also transmitted as an IP packet. These IP packets are transmitted as TLV streams in the form of TLV packets on the broadcast transmission line. Signaling information (TLV-SI) related to the TLV multiplexing format for multiplexing IP packets is also transmitted in the format of TLV packets.

In the MMT method, it is easy to use the data of the timed media and the non-timed media constituting one channel (broadcast program) in a combination of different transmission lines. In the example shown in FIG. 5, MMT transmission lines 501 to 504 for each type of data such as video, audio, subtitles, file data, and signaling information are used as the broadcast signal 500. Each MMT transmission line corresponds to one IP data flow. The IP data flow referred to here means that the values of the five fields of the source IP address, the destination IP address, the protocol type of the IP header, the source port number, and the destination port number of the IP header and the UDP header are all the same. Is a set of IP packets. In the figure, the transmission line for subtitle data is omitted for convenience. Further, the TLV-SI stream is also omitted in FIG.

The MMT type broadcasting system 11 is a method of transmitting IP packets on a broadcasting transmission line, and can be operated by mapping one IP address for each broadcasting service (or for each broadcasting station). In such a case, the receiver can access each MMT transmission line 501 to 504 of the desired broadcasting service (or desired broadcasting station) by filtering the broadcasting signal 500 based on the IP address. .. MMTP (MMT protocol) packets transmitted on each MMT transmission line 501 to 504 within the same IP address can be uniquely specified by packet identification information (packet_id: PID). Further, the MMTP packet on a different IP address can be specified by the combination of the packet identification information, the IP address, and the port number.

One channel (broadcast program) can be said to be a "package" composed of a plurality of assets of different types such as video, audio, subtitles, and file data (data broadcasting application). The "package" referred to here is a logical set of media data transmitted using an MMT transmission line. Also, the "asset" referred to here is an entity of data used to compose a multimedia presentation associated with unique asset identification information.

Each asset is composed of a set (logical group) of one or more MPUs that share the same asset identification information. The MPU can be said to be a format that serves as a transmission unit in the MMT system. Each MPU is transmitted to each asset on a dedicated ES (Elementary Stream), that is, MMT transmission lines 501 to 503. That is, the MMTP packet of the coded video signal consisting of the MPU logic group of the video signal having the common asset identification information is transmitted on the transmission line 501, and the MPU logic group of the voice signal having the common asset identification information is transmitted on the transmission line 502. An MMT packet of a coded voice signal consisting of is transmitted, and an MMT packet of a coded application consisting of an MPU logical group of a data broadcasting application having common asset identification information is transmitted on a transmission line 503. Each MPU is identified by the asset identification information and the sequence number of the MPU on the corresponding transmission line. Further, the MMT transmission line that transmits each medium can be identified by the asset identification information.

In addition, one package (broadcast program) may transmit a plurality of assets of the same type (that is, different asset identification information). For example, two or more data broadcasting applications are provided for the same broadcasting program. For example, a program-linked data broadcasting application linked to a broadcast program and a program non-linked data broadcasting application not linked to a broadcast program (for example, weather forecast, news, etc.) usually have different asset identification information as separate assets. Allotted and transmitted as separate MPU logical groups on different MMT transmission lines. FIG. 5 depicts a transmission line 503-1 of a broadcast program interlocking data broadcasting application and a transmission line 503-2 of a broadcast program non-interlocking data broadcasting application.

Further, the MMT method can be commonly used for a plurality of transmission lines for broadcasting and communication. For example, non-timed media such as data broadcasting applications (HTML5 documents, etc.) are transmitted together with the timed media using the broadcast signal transmission line 503 as shown in FIG. 5, as well as communication transmission such as an IP network. It can also be provided via a road (not shown).

In the transmission line 504, the MMTP packet including the MMT-SI, which is a transmission control signal indicating the configuration of the MMT package and the information related to the broadcasting service, is repeatedly transmitted by the carousel method. Examples of the MMT-SI signaling message transmitted on the transmission line 504 include PA message 510, M2 section message 520, and data transmission message 530.

For example, the PA message 510 is control information indicating the configuration of a broadcast program, and includes an MP (MMT Package) table 511 that describes information constituting the package such as a list of assets and their positions.

The PA message 510 is an entry point of the broadcasting service, and fixed packet identification information (for example, 0x0000) is assigned to the MMTP packet that transmits the PA message 510. Therefore, on the receiver side, the PA message 510 can be acquired by designating the fixed packet identification information on the MMT transmission line 504. Then, with reference to the MP table 511 transmitted in the PA message 510, each asset (video, audio, subtitle, file data (data broadcasting application), etc.) constituting the package (broadcast program) can be specified. ..

Further, the M2 section message 520 is a message for transmitting the section extension format of MPEG-2 Systems. A signaling table such as MH-AIT (Application Information Table) 521 is stored in the M2 section message 520. The MH-AIT521 is a table for transmitting dynamic control information related to the application and additional information necessary for execution. Specifically, a processing method (file data) of a data broadcasting application (file data) sent on the MMT transmission line (MH-AIT521). Specify the startup state applied to the application) and the location (URL). Application processing methods include AUTOSTART (AS), which indicates automatic application startup, PRESENT (PR), which indicates that the application is in an executable state, KILL, which indicates the termination of the application, and acquisition and retention (pre-cache) of the application. The PREFETCH shown can be mentioned.

Further, the data transmission message 530 is a message for transmitting control information regarding the transmission of the data broadcasting application. Each signaling table of the data directory management table 531, the data asset management table 532, and the data content management table 533 is stored in one data transmission message 530.

The data directory management table 531 is a table for managing a data broadcasting application in a directory unit (in other words, a data broadcasting application production unit). Since the directory structure of the directory contained in one package and the subdirectories and files (items) contained in the directory are described in the table, the file structure of the application and the structure for file transmission can be separated. can.

Further, the data asset management table 532 is a table for managing a data broadcasting application for each asset, and describes version information for each MPU with the configuration of the MPU in the asset.

Further, the data content management table 533 is a table for managing information on a presentation unit (Presentation Unit: PU) and a file of a data broadcasting application constituting each data content. The "data content" referred to here generally corresponds to the entire linked application data of one broadcast program. In this table, when the information is in the presentation unit (PU), the configuration information of the file of the data broadcasting application is described in the presentation unit (PU) of the data broadcasting, and the file data for the data broadcasting application is flexible and effective. It can be used for various cache control.

In the transmission method of the data broadcasting application by MMT, by utilizing the above three types of signaling tables 531 to 533 transmitted by the data transmission message, the transmission data structure of each file and the directory structure in the content (data broadcasting application) production can be obtained. Can independently represent the data structure of the usage unit such as application unit and presentation unit for effective utilization of cache memory in the receiver (for example, Japanese Patent Application No. 2014 already transferred to the applicant). -88630).

The packet identification information of the message or table transmitted as MMT-SI may be fixed or indirectly specified from another table. Of these, the PA message is the entry point of the broadcasting service and is assigned fixed packet identification information (for example, 0x0000). In the MP table transmitted by the PA message, each asset (video, audio, subtitle, file data (data broadcasting application), etc.) constituting the package (broadcast program) is specified. Therefore, as shown in FIG. 12, each asset (video, audio, subtitle, file data (data broadcasting application), etc.) constituting the package (broadcast program) can be specified by referring to the MP table.

FIG. 7 illustrates a mechanism for acquiring items of a data broadcasting application multiplexed on the same IP data flow.

The path name of the file that constitutes the data broadcasting application is specified in the application description such as HTML5. The path name referred to here is described by a combination of a directory node name and a file name. In addition, a node tag is specified as a descriptor that integrates a directory node and a file, and each signaling table is used as linking information.

When the path name is specified from the data broadcasting application, the node tag of the file with the specified path name can be obtained from the data directory management table in the data transmission message as shown by the reference number 701.

Then, as shown by reference number 702, from the data asset management table also in the data transmission message, the component tag and download identification of the asset to which the item with the node tag obtained in the data directory management table is transmitted are transmitted. Information, MPU sequence numbers, and item identification information can be obtained.

Furthermore, as shown by reference number 703, when the location information of the asset having the component tag obtained in the data asset management table is acquired from the MP table, the corresponding file is actually found as shown by reference number 704. You can identify the data assets to be transmitted.

Then, within the specified data asset, the download identification information obtained from the data asset management table and the download identification information described in the header area of the MMTP packet that transmits the item are used to repeat the file corresponding to the carousel. The unit of transmission can be uniquely identified. As shown by the reference number 705, among the items to be repeatedly transmitted, the item having the MPU sequence number and the item identification information obtained from the data asset management table can be specified as a desired file. It is assumed that the node tag is unique in the data transmission message, the MPU sequence number is unique in the asset (IP data flow), and the item identification information is unique in the service provider.

Data broadcasting applications can be broadly divided into program-linked data broadcasting applications linked to broadcast programs and program-non-linked data broadcasting applications that are not particularly linked to broadcast programs, such as news and weather forecasts. There is a request on the broadcasting station side to forcibly switch the display to the program-linked data broadcasting application in conjunction with the broadcasting program. "In conjunction with a broadcast program" means when the broadcast program is switched, or when the corner is switched in the broadcast program. Even if the program non-linked data broadcasting application is executed at such a timing, it is terminated and forced to the program-linked data broadcasting application specified as an entry in the broadcast program (or a corner in the program). There is a request from the broadcasting station to pull it back.

FIG. 8 schematically shows a case where a forced pullback to the program-linked data broadcasting application specified in the entry is performed.

In FIG. 8, an MMT type broadcasting transmission line is assumed, and video assets 801 and audio assets 802, and data broadcasting application assets 803 and 804 are transmitted via dedicated MMT transmission lines, respectively. However, the reference number 803 is an asset of the program-linked data broadcasting application, and the reference number 804 is an asset of the program non-linked data broadcasting application.

Further, along with the MMT transmission of the asset, as control information (MMT-SI) related to MMT, as shown by reference numbers 810 to 816, an event information table (EIT), an application information table (AIT), and data directory management. Various signaling tables such as a table (DDMT), a data asset management table (DAMT), a data content management table (DCCT), and an event message table (EMT) are transmitted. Of these, the event information table 811 describes the program name, broadcast date and time, program content, and the like, and is updated when the program is changed or ended. Further, the application information table shows a processing method of each application, and describes, for example, an application to be automatically started (AS) and an application in an executable state (PR). Executable applications are all program-linked and non-program-linked applications transmitted within assets 803,804. In addition, the application to be automatically started corresponds to a broadcast-linked data broadcasting application that is an entry in the broadcast program (or a corner in the program). The event message table 816 also transmits information about the event message.

The horizontal direction of FIG. 8 is assumed to correspond to the time axis, the on-air of the broadcast program P1 starts at time t1, the corner changes in the broadcast program P1 at time t2, and the broadcast program P1 ends at time t3. It is assumed that the next broadcast program P2 starts.

In the asset 803, the application to be transmitted is changed in conjunction with the switching of the program and the switching of the program corner. That is, the program-linked applications app1 and app2 are transmitted during the period t1 to t2, and the program-linked applications app6 and app7 are transmitted during the period t2 to t3. Further, after the time t3, the transmission of the program-linked application is stopped. On the other hand, in the asset 804, the program non-interlocking applications appp3 and app4 continue to be transmitted without being interlocked with the program switching or the program corner switching.

The application information table 811 indicates app1 to the application (AS) to be automatically started during the period t1 to t2, and is transmitted in the same period by the assets 803 and 804 as the application (PR) in the executable state. All other applications upp2, upp3, upp4 are shown. In addition, during the period t2 to t3, the application (AS) to be automatically started is indicated by app6, and all other applications transmitted in the same period by the assets 803 and 804 as executable applications (PR). Applications app7, app3, app4 of. Further, after time t3, the program non-linked application appp3 is shown as the application (AS) to be automatically started, and the application appp4 is shown as the application (PR) in the executable state.

The lowermost part of FIG. 8 shows the transition of the application reference relationship and the application display in each period. In the period of time t1 to t2, app1 is designated as an entry application, and app1 refers to the program-linked application appp2 and the program-non-linked application appp3. Further, app3 refers to the application appp4, which is also non-program-linked. Further, in the period of time t2 to t3, app6 is designated as an entry application, and app1 refers to the program-linked application app7 and the program-non-linked application app3. Further, app3 refers to the application appp4, which is a program non-interlocking type, as in the case before time t2.

The entry application app1 is automatically started in conjunction with the start of airing of the broadcast program P1 at time t1. After that, it is assumed that the display of the data broadcast shifts to the program non-linked application application3 in response to the user's remote control operation or the like. Then, when the time t2 is reached, the entry application is switched to the application 6 in conjunction with the change of the corner in the broadcast program P1. In such a case, the broadcasting station that broadcasts the broadcast program P1 is required to forcibly terminate the program non-interlocking application application 3 and return to the display of the program interlocking application application 6 as an entry.

In the transmission method of the conventional BML format data broadcasting application, it is possible to forcibly pull back to the desired data broadcasting application by signaling called a pullback flag (returnto_entry_flag).

On the other hand, in the present specification, in a broadcasting system adopting the MMT method, some examples of instructing forced switching of a data broadcasting application by a signaling message related to data transmission will be described.

In the first embodiment, the pullback control descriptor to the entry application is placed in the data asset management table (see FIG. 5) transmitted by the data transmission message to the entry application. Achieve forced pullback.

FIG. 9 shows a syntax example 900 of the data asset management table (DAMT) transmitted by the data transmission message. The data asset management table is a table for managing a data broadcasting application for each asset, and describes version information for each MPU with the configuration of the MPU in the asset.

The table_id (table identification) is an 8-bit fixed value indicating that the table is a data asset management table in various signaling information. version_ is an 8-bit integer parameter that indicates the version of this data asset management table. For example, if some parameters that make up the data asset management table are also updated, the version is incremented by +1. Length is a 16-bit length parameter that indicates the size of this data asset management table in bytes, which is counted immediately after this field.

number_of_data_components is an 8-bit parameter that indicates the number of data components contained in the package (ie, the number of assets in the data broadcasting application). For example, it is assumed that two types of data components, a program-linked data broadcasting application and a program-non-linked data broadcasting application, are transmitted in one package (broadcast program). Loops of the following data components (that is, assets) are arranged for the number of numbers_of_data_components, and information for each data component is stored. In each data component loop (or asset loop), the attribute information of the data component and the MPU information included in the data component are written.

The attribute information of the data component includes transaction_id (transaction identification information), component_tag, and download_id (download identification information). transition_id is an identifier having a version function of the data component. component_tag is a label for identifying the stream of the data component. It is assumed that component_tag has the same value as component_tag in the MH stream identification descriptor that is placed as an asset descriptor in the MP table. The download_id acts as a label for uniquely identifying the data content. Download identification information is written in the extension header of the MMTP packet that transmits the application (non-timed media) as needed.

number_of_mpus indicates the number of MPUs contained in the data component. Then, the attribute information of each MPU is stored in the loop of the MPUs arranged by the number of num_of_mpus. MPU_sequence_number is an MPU sequence number assigned to the MPU. number_of_items indicates the number of items (file data) contained in the MPU. Then, the information of each item is stored in the loop of the items arranged by the number of num_of_items.

The attribute information of the item and the information about the item are stored in the loop of one item. As the attribute information of the item, item_id, node_tag, item_size, item_version, and item_checksum are stored. item_id is a 32-bit value that uniquely identifies an item on the MMT transmission path. node_tag is a 16-bit value that identifies an item as a node tag corresponding to the item. By using 16-bit node_tag instead of 32-bit item_id as the signaling information, the bit size required for identifying the item on the data transmission message can be reduced. item_size represents the size of the item in bytes. item_version indicates the version of the item, and each time the content of the item is updated, the version is incremented by +1. item_checksum indicates the checksum of the item. Since it is considered that a large amount of information is always set for the checksum for all files, a 32-bit check_check_sum appears only when a 1-bit check_sum_flag is set and 1 is assigned to the checksum. .. checksum_flag is a flag indicating whether or not a checksum is described, and when this flag is 1, item_checksum is described. item_info_length indicates the byte length of the subsequent item information area, and information about the item is written in byte units (item_info_byte) in a series of areas consisting of loops for the number of bytes.

In addition, information on each MPU is stored in the MPU loop. Specifically, MPU_info_length indicates the byte length of the subsequent MPU information area, and information about the MPU is written in byte units (item_info_byte) in a series of areas composed of loops for the number of bytes.

At the end of the asset loop, a descriptor that describes information for each asset is placed. Specifically, descriptor_loop_length indicates the total byte length of descriptor. The descriptor stores a descriptor that describes information in asset units in a series of areas consisting of loops of several minutes of descriptor_loop_length. The stored descriptor is defined separately.

In the first embodiment, a descriptor for pullback control to the entry application (returnToEntry_descriptor) is arranged as a descriptor for describing information in asset units.

FIG. 10 shows a syntax example 1000 of a pullback control descriptor (returnToEntry_descriptor) to the entry application placed in the data asset management table.

descriptor_tag is an 8-bit integer value that identifies the descriptor 1000. descriptor_length is an area for writing the byte length of the data of the descriptor 1000 following this field. Then, return_to_entry_flag indicates whether or not to perform forced pullback.

Also in the first embodiment, there are two methods of applying the pullback control descriptor to the entry application. The first method is to place the pullback control descriptor shown in FIG. 10 in the descriptor area of the loop of the data asset including the auto-start application in the data asset management table, and place it in the loop of the other data assets. Does not place a pullback control descriptor. As a result, if the receiver is executing an application other than the application transmitted by the data asset including the auto-launch application, the receiver terminates the application and starts the entry application. Let us consider the operation of the receiver in this case. For example, when the time t2 is reached and the data asset management table is updated, the receiver checks the contents. The receiver switches to the execution of the program non-interlocking application application3 during the period t1 to t2, but the updated data asset management table includes the pullback control descriptor. Immediately terminates application3 transmitted with a data asset different from the data asset in which is described, and starts the entry application application6.

The second method places the pullback control descriptor in the loop of the data asset to be pulled back in the data asset management table. As a result, if the receiver is executing the application included in the data asset in which the descriptor is placed, the receiver terminates the application and starts the entry application. Let us consider the operation of the receiver in this case. For example, when the time t2 is reached and the data asset management table is updated, the receiver checks the contents. The receiver switches to the execution of the program non-interlocking application application3 during the period t1 to t2, but in the updated data asset management table, the pullback control description is returned to the data asset to which the application3 is transmitted. Since the child is placed, the application 3 is immediately terminated and the entry application application 6 is started.

In this way, by using the data asset management table, it is possible to control the forced pullback of the application on an asset-by-asset basis.

In the second embodiment, the pullback control descriptor to the entry application is placed in the data content management table (see FIG. 5) transmitted by the data transmission message to the entry application. Achieve forced pullback.

FIG. 11 shows a syntax example 1100 of a data content management table (DCCT) transmitted by a data transmission message. The data content management table is a table for managing a data broadcasting application for each presentation unit (PU). In this table, the configuration information of the file of the data broadcasting application is described in the presentation unit (PU) of the data broadcasting.

An 8-bit fixed value indicating that the table is a data / content management table is written in the table_id (table identifier) in various signaling information. Version_ is an 8-bit integer parameter indicating the version of the data content management table. For example, if some parameters that make up the table are also updated, the version is incremented by +1. Length is a 16-bit length parameter that indicates the size of the data / content management table in bytes, which is counted immediately after this field.

number_of_contents is an 8-bit parameter indicating the number of data contents transmitted in a package (broadcast program). The following data content loops are arranged for the number of numbers_of_contents, and information for each data content is stored. The data content generally corresponds to the entire linked application data of one broadcast program.

In one data content loop, content_id, content_version, content_size, PU_info_flag are described as attribute information of the data content, and a presentation unit (PU) of the data broadcasting application constituting the data content is described. Or information about the file is written. The content_id (content identification information) is a label that uniquely identifies the data content. The content_version is an area for writing the version number of the data content. The content_size is an area for writing the size of the data content. Further, PU_info_flag is a flag indicating whether or not the loop of the data content indicates information of the presentation unit (PU).

PU_info_flag = 1 indicates that the loop of the data content is information of the presentation unit (PU). In the subsequent area in this case, information on the presentation unit (PU) of the data broadcasting application constituting the data content is stored. The number of PUs included in the data content is written in number_of_PUs, and subsequently, loops of PUs are arranged by the number of numbers_of_PUs.

In the loop of one PU, PU_tag which is the identification information of the PU, PU_size which is an area for writing the size of the PU, and number_of_member_nodes indicating the number of node designations of the files or directories constituting the PU are written. Then, in the loop of the nodes arranged by the number of number_of_member_nodes, the node tag that identifies the file or directory constituting the PU is written.

Further, PU information is further written in the loop of one PU. Specifically, the byte length of the PU information is indicated in PU_info_length, and the PU information is written in byte units (PU_info_byte) in a series of areas composed of loops corresponding to the number of bytes.

On the other hand, PU_info_flag = 0 indicates that the loop of the data content is file information. In this case, the information of the files or directories constituting the data content is written in the subsequent area. Specifically, number_of_nodes indicating the number of node designations of the files or directories constituting the data content are written. Then, a node tag that identifies a file or directory constituting the data content is written in a loop of nodes arranged for the number of numbers_of_nodes.

As shown in FIG. 11, in the loop of the PU of the data content management table, the information of the PU can be stored for each presentation unit PU constituting the data content (however, when PU_info_flag = 1). .. In the second embodiment, this information area is used to arrange a descriptor for pullback control to the entry application (returnToEntry_descriptor) to control the forced pullback of the application in units of presentation of the application.

The syntax of the pullback control descriptor arranged in the information area for each PU may be the same as in FIG. The return_to_entry_flag of the pullback control descriptor indicates whether or not to perform forced pullback.

Also in the second embodiment, there are two methods of applying the pullback control descriptor to the entry application. In the first method, the pullback control descriptor is placed in the PU information area of the loop of the PU including the auto-start application in the data content management table, but the pullback control descriptor is placed in the loop of the other PUs. do not. Since the PU including the auto-start application can be identified by PU_tag = 0, the pullback control descriptor is placed only in the loop of the PU with PU_tag = 0, and the pullback control descriptor is placed in the loop of the PU in which PU_tag is not 0. Do not place. Indicates that the application contained in the PU that does not place the pullback control descriptor should be terminated when forcibly pulling back to the automatically started application. On the contrary, the second method is a loop of the PU that does not include the auto-start application, and the pullback control descriptor is placed in the PU information area of the PU to be pulled back. Indicates that the application included in the PU in which the pullback control descriptor is placed should be terminated when forcibly pulling back to the automatically started application.

Let us consider the operation on the receiver side when the pullback control descriptor is placed only in the loop of the PU with PU_tag = 0. For example, when the time t2 is reached and the data / content management table is updated, the receiver checks the contents. The receiver switches to the execution of the program non-interlocking application application3 during the period t1 to t2, but in the updated data content management table, the pullback control descriptor is PU_tag = 0. Since it is located at, app3 is terminated immediately. As a result, the receiver can automatically start upp6 specified in the entry application after time t2 as requested by the broadcasting station.

In this way, by arranging the pullback control descriptor (returnToEntry_descriptor) to the entry application in the loop of the PU of the data content management table, the forced pullback of the application can be controlled by the presentation unit (PU). ..

In the third embodiment as well, as in the second embodiment, the forced pullback to the entry application is realized by arranging the descriptor of the pullback control to the entry application in the data content management table. However, in the third embodiment, the pullback control descriptor is placed not in the loop of the PU but in the loop of the upper data content, and the pullback control descriptor is forcibly pulled back to the entry application in units of the data content higher than the PU. Control.

In the third embodiment, the information area of the data content for arranging the pullback control descriptor is newly defined in the data content loop of the data content management table. FIG. 12 shows a syntax example 1200 of the data content management table used in the third embodiment. The points different from the syntax example 1100 of FIG. 11 are shown surrounded by dotted lines. Hereinafter, this syntax example 1200 will be described, but the parameters that overlap with FIG. 11 will be described.

As shown by the reference number 1201, in the loop of the data content, the content_info_flag is defined after the PU_info_flag as the attribute information of the data content. The content_info_flag is a flag indicating whether or not the loop of the data content includes the information of the data content.

content_info_flag = 1 indicates that the loop of the data content includes the information of the data content. In this case, an area for storing data content information is defined at the end of the data content loop. Specifically, as shown by reference number 1202, the byte length of the data content information is indicated in content_info_length, and the data content information is stored in byte units (content_info_byte) in a series of areas consisting of loops for the number of bytes. Written.

In the third embodiment, the information area of the data content is used to arrange a descriptor for pullback control to the entry application (returnToEntry_descriptor), and the forced pullback of the application is controlled for each presentation unit of the application.

FIG. 13 shows a syntax example 1300 of a descriptor (returnToEntry_descriptor) for pullback control to the entry application, which is arranged in the information area of the data content of the data content management table.

descriptor_tag is an 8-bit integer value that identifies the descriptor 1300. descriptor_length is an area for writing the byte length of the data of the descriptor 1300 following this field. In PU_number_of_target_to_return, the number of PUs included in the data content specified to be terminated when the application is forcibly pulled back is written. Then, in the loop arranged by the number of PU_number_of_target_to_return, a PU tag that identifies each PU to be terminated when the application is forcibly pulled back is written.

Let us consider the operation on the receiver side in this case. For example, when the time t2 is reached and the data / content management table is updated, the receiver checks the contents. The receiver has switched to the execution of the program non-linked application application3 during the period t1 to t2, but in the updated data content management table, the data content including the program non-linked application application3 Since the tag of the presentation unit (PU) including application3 is specified in the pullback control descriptor arranged in the loop, application3 is terminated immediately. As a result, the receiver can automatically start upp6 specified in the entry application after time t2 as requested by the broadcasting station.

In this way, by arranging the pullback control descriptor (returnToEntry_descriptor) to the entry application in the data content newly defined in the data content loop of the data content management table, it is presented for each data content. The unit (PU) can control the forced pullback of the application.

In the fourth embodiment, the entry is made by arranging the pullback control descriptor to the entry application in the MH-AIT (application information table) (see FIG. 5) transmitted by the M2 section message. -Achieve forced pullback to the application.

FIG. 14 shows a syntax example 1400 of MH-AIT transmitted by an M2 section message. MH-AIT is a table that transmits dynamic control information related to an application and additional information necessary for execution. Specifically, a processing method (file data) of a data broadcasting application (file data) sent on an MMT transmission line (MH-AIT). Specify the startup state applied to the application) and the location (URL).

The table_id (table identification) is an 8-bit fixed value that identifies the table as an application information (AI) table in various signaling information, and is set to 0x89 in this embodiment. The statement_synchrox_indicator (section syntax instruction) is a 1-bit field and is always set to "1". sectoin_length (section length) is a 12-bit field that defines the byte length of the section from the section length field to the end of the section containing CRC32. This value shall not exceed 4093 (0xEFD in hexadecimal). application_type (application format) is a 16-bit field that indicates the value of the application being transmitted by AIT. In DVB, 0x0001 is assigned to the DVB-J application. It is also set to 0x0001 in the ARIB-J application. version_number is a 5-bit field that is the partition number of the subtable. version_number is the version number of the MH AI table, and is incremented by +1 when the information in the sub-table changes. Moreover, when the value of the version number becomes "31", it returns to "0" next. The current_next_indicator (current next instruction) is always set to "1". section_number (section number) is an 8-bit field that represents the section number. The section number of the first section in the subtable is 0x00. The section number is incremented by +1 each time a section with the same table identification and application format is added. The last_session_number (last section number) is an 8-bit field that specifies the last section number in the subtable to which the section belongs.

command_descriptor_length (common descriptor loop length) is an 8-bit field that indicates the byte length of the subsequent descriptor (descriptor in the description area), and the descriptor (description in the description area) is divided into a series of areas consisting of loops for this number of bytes. Child) is written. The descriptor in this common descriptor area applies to all applications in the AIT subtable.

The application_loop_length is an area for writing the number of application information included in this MH AI table. Then, the loop of application information is arranged for the number of minutes indicated by application_loop_length. Then, at the end of the table, the ITU-T Recommendation H. A cyclic redundancy check CRC32 (CRC) according to 222.0 is added.

Application_identifier (application identifier), application_control_code (application control code), and application information are arranged in one application information loop.

The application_identifier (application identifier) is a parameter that identifies the application. Further, application_control_code (application control code) defines a control code for controlling the state of the application in an 8-bit field. The semantics of application control code depend on the value of the application format. Table 1 shows the semantics of the application control code when it does not depend on the application format. Further, application_descriptor_loop_length (application information descriptor loop length) indicates the byte length of the application information descriptor, and the descriptor (application information descriptor) is written in a series of areas composed of loops corresponding to the number of bytes. The application information descriptor in this descriptor area is different from the common descriptor and is applied only to the application specified by application_identifier in this loop.

As shown in FIG. 14, an application information descriptor (descriptor) for storing the information of the corresponding application is arranged in the loop of the application information of the MH-AIT. In the fourth embodiment, the descriptor of the pullback control to the entry application is arranged in this descriptor area, and the forced pullback of the application is controlled for each application. In the fourth embodiment, two types of pullback control descriptor syntax can be considered. The first method is a method of applying the pullback control descriptor (returnToEntry descriptor) shown in FIG. 10 described above. As a result, the execution of the application specified by the descriptor is terminated, and the entry application for which automatic startup (autostart) is specified is started. Let us consider the operation on the receiver side in this case. For example, when the time t2 is reached and the MH-AIT is updated, the receiver checks the contents. The receiver switches to the execution of the program non-linked application application3 during the period t1 to t2, but in the updated MH-AIT, the pullback control description is returned to the application information loop of the program non-linked application. Since the child is placed, app3 is terminated immediately. As a result, the receiver can automatically start upp6 specified in the entry application after time t2 as requested by the broadcasting station. In this embodiment, as a modification, it is conceivable to use one bit of the reserved_for_future existing in the application information loop of the MH-AIT or the application control descriptor as the returnToEntry.

The second method is a method of applying the pullback control descriptor (Forced_Return_descriptor) shown in FIG.

descriptor_tag is an 8-bit integer value that identifies the descriptor 1500. descriptor_length is an area for writing the byte length of the data of the descriptor 1500 following this field. In addition, application_identifier indicates application identification information that identifies the application to be executed next when the application is forcibly pulled back.

In the MH-AIT application information loop, a pullback control descriptor (Forced_Return_descriptor) is placed for an application that should be terminated when the application is forcibly pulled back, and the corresponding application is individually instructed to terminate. To explain by applying to the operation example shown in FIG. 8, a pullback control descriptor (Forced_Return_descriptor) is arranged for the program non-linked applications application3 and application4.

Let us consider the operation on the receiver side in this case. For example, when the time t2 is reached and the MH-AIT is updated, the receiver checks the contents. The receiver switches to the execution of the program non-linked application application3 during the period t1 to t2, but in the updated MH-AIT, the storage area of the application information descriptor of the program non-linked application appp3. Since the pullback control descriptor (Forced_Return_descriptor) is arranged in, application3 is terminated immediately. Then, after the time t2, the receiver can automatically start the application application 6 whose application identification information is indicated by the pullback control descriptor (Forced_Return_descriptor) as requested by the broadcasting station.

In this way, by using MH-AIT, it is possible to control the forced pullback of the application on an application-by-application basis.

In the fifth embodiment as well, as in the fourth embodiment, by arranging the pullback control descriptor (Forced_Return_descriptor) in the MH-AIT, forced pullback to the entry application is realized. However, in the fifth embodiment, the pullback control descriptor (Forced_Return_descriptor) is used as a common descriptor (comon_descriptor) applied to all applications in the AIT subtable, not as an application information descriptor applied only to a specific application. To place.

FIG. 16 shows a syntax example 1600 of the pullback control descriptor (Forced_Return_descriptor) arranged in the common descriptor of the MH-AIT.

descriptor_tag is an 8-bit integer value that identifies the descriptor 1600. descriptor_length is an area for writing the byte length of the data of the descriptor 1600 following this field. The number of applications specified to be terminated when the application is forcibly pulled back is written in number_of_target_to_return. Then, in the loop arranged by the number of number_of_target_to_return, application identification information (application_identifier) that identifies each application designated to be terminated at the time of forced pullback of the application is written.

When a pullback control descriptor (Forced_Return_descriptor) is arranged as a common descriptor of the MH-AIT and applied to the operation example shown in FIG. 8 in the AIT subtable, the application is individually instructed to end. To explain by applying to the operation example shown in FIG. 8, the pullback control descriptor (Forced_Return_descriptor) shows the application identification information of the program non-linked applications appp3 and appp4.

Let us consider the operation on the receiver side in this case. For example, when the time t2 is reached and the MH-AIT is updated, the receiver checks the contents. The receiver switches to the execution of the program non-interlocking application application3 during the period t1 to t2, but the pullback control descriptor (Forced_Return_descriptor) arranged as a common descriptor in the updated MH-AIT. Since the application identification information of the program non-interlocking application application3 is shown, the application 3 is terminated immediately. As a result, the receiver can automatically start upp6 specified in the entry application after time t2 as requested by the broadcasting station.

In this way, by using MH-AIT, it is possible to control the forced pullback of the application on an application-by-application basis.

FIG. 17 shows the processing procedure for the receiver to control the execution of the data broadcasting application in the form of a flowchart in each of the first to fifth embodiments described above.

While the broadcast program is on the air, each signaling message including the M2 section message and the data transmission message is basically carousel-transmitted, and the receiver acquires the latest signaling table from the signaling message (step S1701). .. The signaling table acquired by the receiver shall include the MH-AIT, the data asset management table, and the data content management table.

Then, the receiver activates the data broadcasting application (step S1702). The receiver automatically starts, for example, an application for which automatic start (autostart) is specified by MH-AIT. In addition, the receiver executes the application specified by the remote control operation of the user (viewer of the broadcast program). In the following, for the sake of simplification of the explanation, it is assumed that the user does not instruct the termination of the running application.

Unless the signaling table is updated (No in step S1703), the receiver continues to operate the application.

Here, when the signaling tables such as the MH-AIT, the data asset management table, and the data content management table are updated (Yes in step S1703), the "kill" is added to the running application in the MH-AIT. Check if there is a description such as "(End)" is specified (step S1704).

If there is no description such as "kill" for the running application in the updated signaling table (No in step S1704), the running application is pulled back for forced pullback to the entry application. It is checked whether the end is instructed based on the control descriptor (step S1705).

Then, when "kill (end)" is specified in the MH-AIT (Yes in step S1704), the running application is instructed to end the running application based on the pullback control descriptor. If so (Yes in step S1705), the running application is terminated (step S1706).

If an application (entry application) to be automatically started is specified after the running application is terminated (Yes in step S1707), the receiver executes the application.

As described above, the techniques disclosed in the present specification have been described in detail with reference to the specific embodiments. However, it is self-evident that a person skilled in the art can modify or substitute the embodiment without departing from the gist of the technique disclosed herein.

The techniques disclosed herein can be applied to various broadcasting systems that employ MMT as the transport method. In addition, the techniques disclosed herein can be applied to various broadcasting systems that transmit control information relating to the transmission of data broadcasting applications.

In short, the techniques disclosed in this specification have been described in the form of examples, and the contents of the present specification should not be interpreted in a limited manner. The scope of claims should be taken into consideration in order to determine the gist of the technology disclosed herein.

The technology disclosed in the present specification can also have the following configuration.
(1) A transmitter that transmits each component that constitutes a broadcasting service as a transmission unit based on a predetermined transport method.
An information transmission unit that transmits control information related to the transmission of the component, and
Equipped with
The information transmitting unit transmits control information regarding the pullback of the data broadcasting application transmitted from the transmitting unit.
Transmitter.
(2) The predetermined transport method is MMT.
The transmitter according to (1) above.
(3) The information transmitting unit transmits control information instructing to return to the entry application in conjunction with a broadcast program composed of video and audio components transmitted from the transmitting unit.
The transmitter according to (1) above.
(4) The information transmitting unit stores a pullback control descriptor instructing a pullback to the entry application for each component in the first table showing control information regarding the transmission of the components of the application transmitted by the transmitting unit. And send
The transmitter according to (1) above.
(5) The information transmission unit transmits the first table in which the pullback control descriptor indicating the pullback target for each component is stored for each component.
The transmitter according to (4) above.
(6) The information transmission unit stores and transmits the pullback control descriptor instructing the pullback to the entry application in the second table showing the information regarding the presentation unit of the data broadcasting application in the presentation unit.
The transmitter according to (1) above.
(7) The information transmission unit transmits the second table in which the pullback control descriptor indicating the pullback target in the presentation unit is stored for each data content.
The transmitter according to (6) above.
(8) The information transmission unit stores and transmits a pullback control descriptor instructing pullback to the entry application in a third table showing information about the data broadcasting application for each data content. do,
The transmitter according to (1) above.
(9) The transmission unit groups the files constituting the data broadcasting application into transmission units based on the predetermined transport method and transmits the files.
The information transmission unit transmits the third table in which the pullback control descriptor indicating the pullback target in transmission units is stored for each data content.
The transmitter according to (8) above.
(10) The information transmission unit stores and transmits a pullback control descriptor instructing pullback to the entry application in the fourth table showing the operation control of the application for each application.
The transmitter according to (1) above.
(11) The information transmission unit transmits the fourth table storing the pullback control descriptor for each application that specifies the application to be started next.
The transmitter according to (10) above.
(12) The information transmission unit stores and transmits a pullback control descriptor instructing pullback to the entry application as a common descriptor applied to all applications in the fourth table showing the operation control of the application. do,
The transmitter according to (1) above.
(13) The information transmission unit transmits the fourth table in which the pullback control descriptor indicating the identification information of the application to be terminated for pulling back to the entry application is arranged as the common descriptor.
The transmitter according to (12) above.
(14) A transmission step of transmitting each component constituting a broadcasting service as a transmission unit based on a predetermined transport method, and
An information transmission step for transmitting control information regarding the transmission of the component, and
Have,
The information transmission step transmits control information regarding the pullback of the data broadcasting application transmitted in the transmission step.
Sending method.
(15) A receiving unit that receives each component of a broadcasting service transmitted in a transmission unit based on a predetermined transport method.
An information receiving unit that receives control information related to the transmission of the component, and
Equipped with
The information receiving unit receives control information regarding the pullback of the data broadcasting application received by the receiving unit.
Receiver.
(16) A reception step for receiving each component of a broadcasting service transmitted in a transmission unit based on a predetermined transport method, and
An information receiving step for receiving control information regarding the transmission of the component, and
Have,
In the information receiving step, control information regarding the pullback of the data broadcasting application received in the receiving step is received.
Reception method.

10 ... Digital broadcasting system 11 ... Broadcast transmission system, 12 ... Receiver 301 ... Clock unit, 302 ... Signal transmission unit 303 ... Video encoder, 304 ... Audio encoder 305 ... Caption encoder 306 ... Signaling encoder 307 ... File Encoder, 308 ... EDPS
309 ... TLV signaling encoder 310 ... IP service multiplexer 311 ... TLV multiplexer 312 ... Modulation / transmitter 401 ... Tuner / demodulation unit, 402 ... Demultiplexer 402-1 ... TLV filter, 402-2 ... IP filter 402-3 ... UDP filter, 402-4 ... MMT filter 402-5 ... SI filter, 403 ... Clock recovery unit 404 ... Video decoder, 405 ... Audio decoder 406 ... Caption decoder, 407 ... System control unit 408 ... Application Control unit 409 ... Data broadcasting application engine 410 ... IP interface, 411 ... Synthesis unit

Claims (3)

An application that is transmitted in transmission units based on a predetermined transport method, a receiver that receives an application information table, and a receiver.
A control unit that controls the state of the application based on the control code included in the application information table.
Equipped with
The application descriptor placed in the application information loop in the application information table contains control information regarding switching from an application in an executable state to an automatically started application.
When the application information table is updated, the control unit determines to start the automatically started application based on the control information and the control code.
Receiver. The predetermined transport method is MMT (MPEG Media Transport).
The receiving device according to claim 1. A receiving step that receives an application and an application information table transmitted in transmission units based on a predetermined transport method.
A control step that controls the state of the application based on the control code included in the application information table, and
Have,
The application descriptor placed in the application information loop in the application information table contains control information regarding switching from an application in an executable state to an automatically started application.
In the control step, when the application information table is updated, it is determined to start the automatically started application based on the control information and the control code.
Reception method.

Images