JP2020182242A - Transmission method - Google Patents

Abstract

To suitably transmit data for data broadcasting by a data carousel transmission system.SOLUTION: As a file allocation designation system, a transmission channel dependent designation system and a URI designation system are selectively used. In a data coding system descriptor to be disposed at PMT, data transmission of a data broadcasting application in HTML 5 is shown, and transmission arrangement information of signaling information applied when AIT and URI designation systems are selected is designated. In AIT, the URI designation system and the transmission channel dependent designation system of data carousel are designated.SELECTED DRAWING: Figure 2

Description

The techniques disclosed in the present specification include a transmission device and a transmission method for transmitting data for data broadcasting by a predetermined transmission method, and a receiving device and a reception device for receiving data for data broadcasting transmitted by a predetermined transmission method. Regarding the method.

In the current broadcasting system, the MPEG-2 TS (Moving Picture Experts Group-2 Transport Stream) method and the RTP (Real Time Transport Protocol) method are widely used as the media transport method (see, for example, Patent Document 1). That).

Further, in the data broadcasting service operated at the time of the present application, data for data broadcasting such as an application described in BML (Broadcast Markup Language) format is in accordance with the data carousel transmission method defined in ISO / IEC 13818-6. It is repeatedly distributed, and the receiver can acquire necessary data at any time during the broadcast time (see, for example, Patent Document 2). In this data carousel transmission method, data is transmitted in module units divided into blocks. It is assumed that a transmission unit called a module is incorporated into the directory structure of an application, and that multiple files are multiparted into a module to be a cache unit. Due to such a transmission method, it is considered that there are many restrictions on creating an application.

On the other hand, recently, for the purpose of linking broadcasting and communication, it has been studied to apply HTML5 (Hyper Text Markup Language 5), which has higher versatility, to the description format of a data broadcasting application (for example, Patent Document 3). checking).

The object of the technique disclosed in the present specification is an excellent transmission device and transmission method capable of suitably transmitting data for data broadcasting by a data carousel transmission method, and data transmitted by a data carousel transmission method. An object of the present invention is to provide an excellent receiving device and receiving method capable of suitably receiving broadcast data.

The present application has been made in consideration of the above-mentioned problems, and the technique according to claim 1 is a technique.
A first encoder that encodes data of a data broadcasting application by a data carousel transmission method by designating a file location by either a transmission line-dependent designation method or a URI designation method.
A second encoder that encodes program-specific information (PSI) including a program management table (PMT) in which a data encoding method descriptor that specifies transmission arrangement information of an application information table (AIT) related to the data broadcasting application is arranged. ,
A transmission processing unit that multiplexes and transmits a plurality of broadcast data including broadcast data encoded by the first and second encoders, respectively.
It is a transmission device provided with.

According to the technique according to claim 2 of the present application, the transmission device according to claim 1 specifies a transmission path-dependent designation method and a URI designation method of a data carousel in the application information table (AIT). It is configured.

According to the technique according to claim 3 of the present application, the transmission device according to claim 1 manages the transmission arrangement information of signaling information (DDMT, DCCT) applied when the URI designation method is selected. It is configured to be further specified in the data encoding method descriptor arranged in the table (PMT).

According to the technique of claim 4, the transmitter of claim 3 includes the signaling information (DDMT, DCCT) in a particular module of a data carousel encoded by the first encoder. It is configured as follows.

According to the technique according to claim 5 of the present application, the transmission device according to any one of claims 3 or 4 is a data directory management table that manages the directory structure of a file transmitted by data broadcasting as the signaling information. (DDMT) is configured to be included.

According to the technique according to claim 6 of the present application, the transmission device according to any one of claims 3 to 5 has a file structure and content (application) for each content (application) transmitted by data broadcasting as the signaling information. ) Is configured to include a file structure, a content structure, and a data content management table (DCCT) indicating cache control for each data broadcasting presentation unit (PU).

According to the technique according to claim 7 of the present application, the transmitting device according to any one of claims 3 to 6 expresses the signaling information in XML (eXtensible Markup Language) notation format and binary notation format. It is configured.

According to the technique according to claim 8 of the present application, the transmitter according to any one of claims 3 to 7 has a common node for each directory and each file in each table included in the signaling information. Along with specifying a tag, a node tag descriptor is placed in the module information of the control message (DII) indicating the information of each module of the data carousel, and is configured to be associated with the module.

Further, the technique according to claim 9 of the present application is:
The first encoding step of encoding the data of the data broadcasting application by the data carousel transmission method by designating the file location by either the transmission line-dependent designation method or the URI designation method.
A second encoding that encodes program-specific information (PSI) including a program management table (PMT) in which a data encoding method descriptor that specifies transmission arrangement information of the application information table (AIT) related to the data broadcasting application is arranged. Steps and
A transmission processing step of multiplexing and transmitting a plurality of broadcast data including broadcast data encoded in the first and second encoding steps, respectively.
It is a transmission method having.

In addition, the technique according to claim 10 of the present application
Data encoding that specifies the data carousel of a data broadcasting application whose file location is specified by either the transmission line-dependent specification method or the URI specification method and the transmission arrangement information of the application information table (AIT) related to the data broadcasting application. A reception processing unit that receives and processes a broadcast signal including program-specific information (PSI) including a program management table (PMT) in which a method descriptor is arranged, and a reception processing unit.
An application data control unit that controls the processing of data broadcasting applications,
It is a receiving device provided with.

According to the technique according to claim 11 of the present application, the application data control unit of the receiving device according to claim 10 is described in a data coding method descriptor arranged in the program management table (PMT). The application information table (AIT) is acquired based on the transmission arrangement information of the application information table (AIT), and the file location designation method of the data carousel is a transmission path based on the application information table (AIT). It is configured to determine whether it is a dependency designation method or a URI designation method.

According to the technique according to claim 12 of the present application, the receiving device according to any one of claims 10 or 11 is used when the URI designation method is selected as the file location designation method of the data carousel. A control message (DII) indicating information on each module of the data carousel from the data carousel in which the packet identifier (PID) of the elemental stream is specified in the program management table (PMT) by the application data control unit. ) And the module (DDB message) of the signaling information (DDMT, DCCT) applied when the URI designation method is selected, and is configured to resolve the location of the module contained in the data carousel. ..

According to the technique according to claim 13 of the present application, the application data control unit of the receiving device according to claim 12 is described in the data coding method descriptor arranged in the program management table (PMT). It is configured to acquire signaling information (DDMT, DCCT) based on the transmission arrangement information of the signaled signaling information (DDMT, DCCT).

According to the technique of claim 14 of the present application, the application data control unit of the receiving device according to claim 12 matches a URI that specifies the location of a desired application in the application information table (AIT). The node tag is searched by the signaling information (data directory management table that manages the directory structure of files transmitted by data broadcasting: DLMT), and the module identifier of the module associated with the node tag is the control message. It is configured to specify the corresponding module (DDB message) from the data carousel based on the combination of the module identifier and the download identifier obtained from (DII).

According to the technique according to claim 15 of the present application, the application data control unit of the receiving device according to claim 12 has the signaling information (file structure for each content (application) transmitted by data broadcasting), content ( Use the data content management table (DCCT), which shows the file configuration, content configuration, and cache control for each data broadcast presentation unit (PU) in the application), to control the cache of the file data transmitted to the data carousel. It is configured in.

According to the technique according to claim 16 of the present application, the application data control unit of the receiving device according to claim 13 causes the receiving processing unit to lock a module designated as a lock target in the signaling information (DCCT). When it is received, it is configured to be forcibly cached in the cache memory.

According to the technique according to claim 17 of the present application, the application data control unit of the receiving device according to claim 16 specifies a forced cache of a module designated as an unlock target in the signaling information (DCCT). It is configured to be released and deleted from the cache memory.

According to the technique of claim 18 of the present application, the application data control unit of the receiving device according to claim 15 specifies a forced cache of a module designated as an unlock target in the signaling information (DCCT). It is configured to be released and deleted from the cache memory.

In addition, the technique according to claim 19 of the present application
Data encoding that specifies the data carousel of a data broadcasting application whose file location is specified by either the transmission line-dependent specification method or the URI specification method and the transmission arrangement information of the application information table (AIT) related to the data broadcasting application. A reception processing step for receiving and processing a broadcast signal including program-specific information (PSI) including a program management table (PMT) in which a method descriptor is arranged, and a reception processing step.
Application data control steps that control the processing of data broadcasting applications,
It is a receiving method having.

According to the technique disclosed herein, an excellent transmission device and transmission method capable of suitably transmitting data for data broadcasting by the data carousel transmission method, and data transmitted by the data carousel transmission method. It is possible to provide an excellent receiving device and receiving method capable of preferably receiving broadcast data.

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 schematically showing a configuration of a broadcast signal 200 assumed in the digital broadcasting system 10 according to the present embodiment. FIG. 3 is a diagram schematically showing a configuration of a broadcast transmission system 11 that transmits the broadcast signal 200 shown in FIG. FIG. 4 is a diagram schematically showing the configuration of the receiver 12 that receives the broadcast signal 200 shown in FIG. FIG. 5 is a diagram showing a data structure 500 of PMT. FIG. 6 is a diagram showing a data structure 600 of the data encoding method descriptor. FIG. 7 is a diagram showing a data structure 700 of Additional_html5_info (). FIG. 8 is a diagram showing a data structure 800 of the data carousel. FIG. 9 is a diagram showing a data structure 900 of a DII message transmitted in the DSM-CC section (data carousel). It is a figure which showed. FIG. 10 is a diagram showing a data structure 1000 of a DDB message. FIG. 11 is a diagram showing a data structure 1100 of the application information table (AIT). FIG. 12 is a diagram showing the meaning of each value of applicaton_type. FIG. 13 is a diagram showing the semantics of application_control_code. FIG. 14 is a diagram showing the data structure 1400 of the application descriptor. FIG. 15 is a diagram showing the semantics of each parameter of the application descriptor. FIG. 16 is a diagram showing a data structure 1600 of a transmission protocol descriptor. FIG. 17 is a diagram showing a data structure 1700 of a selector byte in a transmission protocol descriptor in the case of data carousel transmission of a transmission line dependent designation method. FIG. 18 is a diagram showing a file designation method in the case of data carousel transmission of the transmission line dependent designation method. FIG. 19 is a diagram showing a directory structure in the case of data carousel transmission of a transmission line dependent designation method. FIG. 20 is a diagram showing a signaling relationship of application acquisition in the case of data carousel transmission of a transmission line-dependent designation method. FIG. 21 is a diagram showing a data structure 2100 of a selector byte in a transmission protocol descriptor in the case of HTTPS / HTTPS transmission and data carousel transmission of a URI designation method. FIG. 22 is a diagram showing a file designation method in the case of data carousel transmission of the URI designation method. FIG. 23 is a diagram showing the data structure 2300 of the node tag descriptor to be arranged in each model_info of the DII message. FIG. 24 is a diagram showing a data structure 2400 of DDMT in binary notation format. FIG. 25 is a diagram showing a data structure 2500 of DDMT in XML notation format. FIG. 26 is a diagram showing a description example of DDMT in XML notation format. FIG. 27 is a diagram showing a DCCT data structure 2700 in binary notation format. FIG. 28 is a diagram showing a data structure 2800 of DCCT in XML notation format. FIG. 29 is a diagram showing a description example 2900 of DCCT in XML notation format. FIG. 30 is a diagram for explaining a mechanism for transmitting, locating, and presenting a data broadcasting application (content) transmitted by a data carousel. FIG. 31 is a diagram showing a signaling relationship of application acquisition in the case of data carousel transmission of the URI designation method. FIG. 32 is a flowchart showing a processing procedure at the time of channel selection of digital broadcasting executed by the receiver 12. FIG. 33 is a flowchart showing a cache control procedure by locking and unlocking in the receiver 12. FIG. 34 is a diagram showing an example of locking and unlocking the cache of file data in the receiver 12.

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 transmits an MPEG-2 TS system broadcast signal. The broadcast signal includes an elemental stream (ES) that constitutes the main part of a broadcast program such as video and audio, and a data broadcasting application related to or linked to the main part of the broadcast program. In the following explanation, a data broadcasting service by HTML5 is assumed.

On the other hand, the receiver 12 receives the broadcast signal sent from the broadcast transmission system 11. Then, the receiver 12 acquires an elementary stream such as a video or audio from the received broadcast signal, and presents an image or sound of the broadcast program. Further, when the receiver 12 acquires each file data for data broadcasting from the received broadcast signal, the receiver 12 activates an application engine such as an HTML browser to present data broadcasting linked to the broadcast program.

In the digital broadcasting system 10 according to the present embodiment, a digital broadcasting service to which the MPEG-2 TS system is applied is provided, and detailed specifications follow, for example, the standard ARIB STD-B24 5.9 version.

FIG. 2 schematically shows the configuration of the broadcast signal 200 assumed in the digital broadcasting system 10 according to the present embodiment. The illustrated broadcast signal 200 includes a plurality of transport stream components 210-250.

Each component represented by reference numbers 210 and 220 is an elementary stream that transmits the video and audio that make up the main part of the broadcast program.

The component indicated by reference numeral 230 downloads data to the receiver 12 and transmits content in the multimedia service. In this embodiment, each data is transmitted in a module unit divided into blocks based on the DSM-CC (Digital Storage Media Command and Control) data carousel specification defined in ISO / IEC 13818-6. To. Since the data is repeatedly transmitted from the broadcast transmission system 11, the receiver 12 can acquire the necessary data at any time during the broadcast time.

Each data carousel 231, 232, ... Includes a DDB (DownloadDataBlock) message as a module in which the data body is divided into blocks, and a DII (DownloadInfoIndication) message belonging to the DSM-CC control message. The DII message describes the information of each module (DDB message) included in the data carousel. Each module in the data carousel can be identified by a module identifier (module_id).

As the DDB message, contents (files) such as a data broadcasting application described in the HTML5 format and monomedia used in a data broadcasting application such as JPEG and PNG are transmitted. In FIG. 2, modules of data related to these applications are indicated by "AppD".

In addition, as DDB messages, an application information table (AIT: Application Information Table), a data directory management table (DDMT: Data Directory Management Table), and a data content management table (DCCT: Data Content Table) indicated by dotted lines are used. , Can be transmitted arbitrarily.

The AIT is a table that describes application control information such as a processing method of an application sent by a data carousel transmission method, a transmission method, and a location designation. DDMT and DCCT are signaling information applied when the URI designation method is selected as the file location designation method of the data broadcasting application (described later). Of these, the DDMT is a table that manages the directory structure of the files that make up the application sent by the data carousel of the URI designation method. In addition, DCCT is a table that manages the content (file data) that composes the application sent by the data carousel of the URI designation method in the data broadcasting presentation unit (Presentation Unit: PU), and is used for cache control of file data. It can be used. Details of each table of AIT, DDMT, and DCCT will be described later.

The DII message belongs to the DSM-CC control message and describes the information of each DDB message contained in the data carousel. Details of the DII message will be given later.

Each data carousel 231, 232, ... Contains one or more DDB messages and a DII message. However, the same DII message may be transmitted multiple times within one data carousel.

The component indicated by the reference number 240 is a dedicated transport stream that packet-transmits the AIT of the application transmitted by the data carousel transmission method in the component 230. However, when the component 230 transmits AIT as a DDB message, the component 240 is unnecessary. That is, the component 240 is arbitrary and is drawn with a dotted line. The AIT transmitted by the data carousel transmission method is identified by a module identifier, and the AIT packet-transmitted by the component 240 is identified by a packet identifier (PID: Packet Identifier).

The component represented by the reference number 250 transmits PSI (Program Special Information) and SI (Service Information). PSI is program-specific information that describes which program each elementary stream included in the MPEG-2 TS stream belongs to. Further, SI is program sequence information and can be used for EPG (Electronic Program Guide: Electronic Program Guide). PSI includes a PMT (Program Map Table) that describes a packet identifier (PID) of a TS packet that transmits video and audio included in one program and each encoded signal that constitutes another broadcast program, and a PMT of each broadcast program. It contains program configuration information of an MPEG-2 TS stream such as a PAT (Program Association Table) that lists the packet identifiers (PIDs) of the MPEG-2 TS stream (the PID of the PAT is defined as 0). Details of PMT will be given later.

FIG. 3 schematically shows the configuration of a broadcast transmission system 11 that transmits the broadcast signal 200 shown in FIG. Clock generation unit 301, signal transmission unit 302, video encoder 303, audio encoder 304, data carousel encoder 305, AIT encoder 306, PSI / SI encoder 307, broadcast information system 308, and It includes a TS multiplexer (MUX) 309 and a modulation / transmission unit 310.

The clock generation unit 301 generates a clock signal STC (System Time Lock) for synchronizing the encoders 303 to 307, and a time stamp PCR (Program) which is a reference for performing time synchronization for decoding on the receiver 12 side. Outputs a TS packet containing (Clock Reference).

The signal transmission unit 302 is, for example, a recording / playback device for a studio or VTR of a TV broadcasting station, and the elemental streams constituting the main part of a broadcast program such as video or audio are transmitted to the video encoder 303 and the audio encoder 304, respectively. send.

The video encoder 303 encodes the video signal transmitted from the signal transmission unit 302, further packets it, and sends a video elementary stream including the TS packet of the video to the TS multiplexer 309. Further, the audio encoder 304 encodes the audio signal transmitted from the signal transmission unit 302, further packetizes it, and sends an audio elemental stream including the audio TS packet to the TS multiplexer 309.

The broadcasting information system 308 is a scheduler of a TV broadcasting station and a source of files, and is a data broadcasting application or data such as monomedia described in HTML5 format, application control information, signaling information related to data such as a data broadcasting application, and a program. The configuration information and the program arrangement information are sent to the data carousel encoder 305, the AIT encoder 306, and the PSI / SI encoder 307, respectively.

The data carousel encoder 305 encodes signaling information related to data such as data broadcasting applications and monomedia, application control information, and data broadcasting applications transmitted from the broadcasting information system 308, and is further divided into blocks. A data carousel consisting of one or more DDB messages and a DII message containing information on each DDB message is assembled and sent to the TS multiplexer 309.

The AIT encoder 306 encodes the application control information transmitted from the broadcast information system 308, further packetizes it, and sends an elemental stream including the AIT TS packet to the TS multiplexer 309. However, when the AIT is transmitted as a DDB message by the data carousel transmission method, the AIT encoder 306 is unnecessary. That is, the equipment of the AIT encoder 306 is optional and is drawn by a dotted line.

The PSI / SI encoder 307 encodes the program configuration information and the program arrangement information transmitted from the broadcast information system 308, further packetizes them, and sends an elemental stream including TS packets of PSI and IS to the TS multiplexer 309. ..

The TS multiplexer 309 multiplexes the TS packets sent from the encoders 303 to 307 to form a broadcast signal 200 as shown in FIG.

The modulation / transmission unit 310 performs digital modulation such as OFDM modulation on the broadcast stream generated by the TS multiplexer 309, further performs RF (Radio Frequency) modulation processing such as up-conversion, and sends the broadcast stream to the RF transmission line. To do.

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

The clock generation unit 301 generates a clock signal STC for synchronizing each encoder 303 to 307, and also generates a TS packet including PCR as a reference for time synchronization for decoding on the receiver 12 side. ..

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 encoded and further packetized to generate an elementary stream containing the TS packet of the video. This video elementary stream is sent to the TS multiplexer 309.

Further, the audio signal transmitted from the signal transmission unit 302 is supplied to the audio encoder 304. In the audio encoder 304, the audio signal is encoded and further packetized to generate an elemental stream containing the TS packet of the audio. This audio elementary stream is sent to the TS multiplexer 309.

Further, in the data carousel encoder 305, a data carousel composed of a DDB message and a DII message is configured based on the information transmitted from the broadcast information system 308 and sent to the TS multiplexer 309.

Further, when the AIT is not transmitted as a DDB message of the data carousel, the AIT encoder 306 generates an elemental stream including the TS packet of the AIT based on the information transmitted from the broadcast information system 308. It is sent to the TS multiplexer 309.

Further, in the PSI / SI encoder 307, an elemental stream including TS packets of PSI and IS is generated based on the program configuration information and the program arrangement information transmitted from the broadcast information system 308, and sent to the TS multiplexer 309. Be done.

In the TS multiplexer 309, the TS streams sent from the encoders 303 to 307 are multiplexed to generate a broadcast stream. Then, the modulation / transmission unit 310 applies digital modulation such as OFDM to the broadcast stream, further performs RF modulation processing such as up-conversion, and transmits the broadcast stream to the RF transmission line.

FIG. 4 schematically shows the configuration of the receiver 12 that receives the broadcast signal 200 shown in FIG. The receiver 12 shown is a tuner / demodulation unit 401, a demultiplexer (DEMUX) 402, a clock reproduction unit 403, a video decoder 404, an audio decoder 405, an application data control unit 406, and a cache. A memory 407, a data broadcasting application engine 408, a system control unit 409, a synthesis unit 410, and an IP interface 411 are provided.

The tuner / demodulation unit 401 receives an IF (Intermediate Frequency) or RF modulation signal and performs demodulation processing such as down-conversion and digital demodulation processing such as OFDM demodulation to obtain a broadcast stream. The demultiplexer 402 performs demultiplexing processing and depacketizing processing on this broadcast stream to perform PCR packet, video elementary stream, audio elementary stream, data carousel, and AIT (however, however). Outputs PSI / SI (when AIT is not transmitted as a DDB message in the data carousel). The file data used for data broadcasting is, for example, a data broadcasting application described in HTML5 format.

The clock reproduction unit 403 reproduces the original clock information STC from the PCR packet, and controls the reproduction timing of the video decoder 404 and the audio decoder 405.

The video decoder 404 decodes the encoded video signal obtained by the demultiplexer 402 to obtain a baseband video signal. Further, the audio decoder 405 decodes the encoded audio signal obtained by the demultiplexer 402 to obtain a baseband audio signal.

The system control unit 409 controls the operation of each unit of the receiver 12 based on the PSI and SI obtained by the demultiplexer 402. In the present embodiment, the system control unit 409 controls the operation of the application data control unit 406 by using a part of the information of the PMT included in the PSI.

The application data control unit 406 processes each file data used in data broadcasting. In the present embodiment, it is assumed that each file / data used in data broadcasting is transmitted from two systems of a broadcasting signal and an IP network, the former is via the tuner / demodulation unit 401 and the demultiplexer 402, and the latter is. Each is acquired by the application data control unit 406 via the IP interface 411.

The application data control unit 406 moves to the cache memory 407 of the file data for the data broadcasting service based on the DII message of the data carousel output from the demultiplexer 402 and the DDMT and DCMT included in the DDB message. Controls the cache processing of. Further, the application data control unit 406 controls the activation of the application by the data broadcasting application engine 408 based on the DII message, the DDMT, the DCMT, and the AIT included in the DDB message. The data broadcasting application engine 408 is an HTML browser or the like, and processes a data broadcasting application by appropriately using the file data cached in the cache memory 407.

In the present embodiment, the signaling information (DCCT) includes information that specifies a forced cache for each file used in data broadcasting. The application data control unit 406 pre-caches the file data necessary for presenting the data broadcast in a timely manner in the cache memory 407 based on the forced cache information included in the DCCT. Details of file data pre-cache will be given later.

The compositing unit 410 synthesizes a data broadcasting display signal output from the data broadcasting application engine 408 with a 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). In addition, the data broadcasting processed by the data broadcasting application engine 408 is also displayed superimposed on the screen of the main part of the broadcast program on the monitor display.

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

The tuner / demodulation unit 401 receives an IF or RF modulation signal, performs demodulation processing such as down-conversion, and digital demodulation processing such as OFDM demodulation to obtain a broadcast stream. In the demultiplexer 402, the broadcast stream is demultiplexed and depacketized, and the PCR packet, the video elemental stream, the audio elemental stream, the data carousel, and the AIT (however, however) are performed. If the AIT is not transmitted as a DDB message in the data carousel), the PSI / SI is extracted.

The PCR packet extracted by the demultiplexer 402 is sent to the clock reproduction unit 403. The clock reproduction unit 403 reproduces the original clock information STC from the PCR packet. That is, the clock reproduction unit 403 generates time information that matches the time information generated by the clock generation 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 to obtain a baseband video signal. Further, the data carousel extracted by the demultiplexer 402 is sent to the application data control unit 406. The application data control unit 406 controls the activation of the application by the data broadcasting application engine 408 based on the DII message, the DDMT, the DCMT, and the AIT included in the DDB message. The data broadcasting application engine 408 processes the file data of the data broadcasting application transmitted as a DDB message, and generates a data broadcasting display signal. Then, in the synthesis unit 410, the display signal of the data broadcast is synthesized with the video signal of the baseband, and the video signal for video 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. 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, in the application data control unit 406, the cache memory of the file data for the data broadcasting service is based on the DII message of the data carousel output from the demultiplexer 402 and the DDMT and DCMT included in the DDB message. The cache processing to 407 is controlled.

In the conventional Japanese data broadcasting service, BML is adopted as the description format of the application, and the transmission unit called the module is incorporated in the directory structure of the application based on the data carousel transmission method, and multiple files are multiparted in the module. It is supposed to be converted into a cache unit. Due to such a transmission method, there is a problem that there are many restrictions on creating an application.

When HTML5 is applied to the description format of a data broadcasting application in the future, it is preferable to remove the restrictions derived from the transmission method as described above in order to maintain its high versatility.

Therefore, in the technique disclosed in the present specification, when the data of the data broadcasting application of HTML5 is transmitted by the data carousel transmission method, the transmission line-dependent designation method and the URI which have been conventionally applied as the file location designation method are used. (Uniform Data Indicator) Allows the specification method to be selectively used.

Then, in the data encoding method descriptor (data component descriptor) to be arranged in the PMT, the data transmission of the data broadcasting application in HTML5 is shown, and the transmission arrangement of the AIT and the signaling information to be applied when the URI designation method is selected ( DDMT and DCCT) transmission arrangement information is specified.

Further, in AIT, it is specified whether the file location designation method of the data carousel is the transmission line-dependent designation method or the URI designation method.

Further, in order to realize the URI designation method, the above-mentioned signaling information of DDMT and DCCT is transmitted. Signaling information is defined as follows (1) to (4).

(1) DDMT is a table that manages the directory structure of files transmitted by data broadcasting. As shown in FIG. 2, the DDMT is transmitted as a specific module (DDB message) of the data carousel.

(2) DCCT is a file structure for each content (application) transmitted by data broadcasting, a file structure for each data broadcasting presentation unit (PU) in the content (application), a content structure such as a file to be cached in advance, and a cache. It is a table showing control. As shown in FIG. 2, the DCCT is transmitted as a specific module (DDB message) of the data carousel.

(3) DDMT and DCCT as these signaling information are expressed in XML (eXtensible Markup Language) notation format and binary notation format.

(4) In the directory structure indicated by DDMT, specify a common node tag for each directory and each file. Also in DCCT, it is specified by a node tag. Furthermore, a node tag descriptor is placed in each module information (moduleInfoByte) of the DII message to associate the directory with the module. This allows the DII message to be associated with the DDMT and DCCT tables.

Then, on the receiver 12 side, the operation of the data broadcasting application including the selection of the above two file / location designation methods is performed.

Hereinafter, in the data carousel transmission method, an embodiment that realizes the above two file location designation methods when transmitting data of an HTML5 data broadcasting application will be described in detail.

FIG. 5 shows the PMT data structure 500. The data structure of PMT basically follows the provisions of ISO / IEC 13818-1.

In the table_id, a value "0x02" that identifies that the table is a PMT is described. In addition, "1" is described in statement_sync_indicator. The section length of the PMT is described in statement_length. Further, in program_number, a service_id that identifies the service (broadcast channel) is described. Version information of the PMT is described in version_number. "1" is described in "curent_next_indicator". "0x00" is described in statement_number. "0x00" is described in last_session_number. In the PCR PID, the packet identifier (PID) of the PCR of the service specified by program_number is described.

The PMT includes a first loop indicated by reference number 501 and a second loop indicated by reference number 502.

The first loop 501 is a program loop. The loop length of the first loop 501 is described in the program_info_length field immediately before the loop 501. Then, in the descriptor area descriptor () composed of the first loop 501 that is repeated for the number of programs_info_length, a program information descriptor such as a limited reception method descriptor, a digital copy control descriptor, and an emergency information descriptor, etc. Is described.

The second loop 502 is an ES loop that stores information on each elementary stream, and stream_type, elementary_PID, and ES_info_length are described as attribute information in each loop. The stream_type describes the format identification of the elementary stream targeted by the loop. The elementary_PID describes the identifier (PID) of the TS packet that carries the associated elemental stream or payload. The length of the descriptor area that follows is described in ES_info_length. Then, the ES descriptor is stored in the descriptor area descriptor () composed of a loop that is repeated for the length of ES_info_length. As the ES descriptor, for example, a stream identification descriptor, a limited reception method descriptor, a digital copy control descriptor, a data coding method descriptor, and the like are described.

The data encoding method descriptor is a descriptor indicating a data coding method in the case of an elementary stream for data broadcasting. As described above, in the present embodiment, the data transmission of the data broadcasting application in HTML5 is shown in the data encoding method descriptor arranged in the PMT, and the data transmission arrangement of the AIT and the URI designation method are applied. The transmission arrangement information of the signaling information (DDMT and DCCT) is specified.

FIG. 6 shows a data structure 600 of a data encoding descriptor which is one of ES descriptors.

The data encoding method descriptor includes descriptor_tag, descriptor_length, and data_component_id as attribute information. The loop length of the subsequent loop 601 is described in descriptor_length. The data_coment_id is used to identify the encoding method for the data in the relevant elementary stream. The allocation of this 16-bit field value follows the regulations of the standardization body. If the elementary stream in question is an application (eg, in HTML5 description format), a value that identifies it as an application transmission is described in data_component_id. An 8-bit tag value that identifies the encoding method of the data of the corresponding elementary stream is described in the descriptor_tag.

Additional identification information (additional_data_component_info) is described in the region composed of the loop 601. The additional_data_component_info is used to extend the identifier number or to store the captured information specified for each coding method. The data structure of the information described in this area is separately defined for each data coding method. In the present embodiment, the data transmission of the data broadcasting application in HTML5 is shown, and the transmission arrangement of the AIT and the additional identification information that specifies the transmission arrangement information of the signaling information (DDMT and DCCT) to be applied when the URI designation method is selected are added. (Additional_html5_info ()) is inserted into this region 601.

FIG. 7 shows a data structure 700 of Additional_html5_info () that is inserted as additional identification information in the data coding method descriptor.

signaling_flag is set to 1 if the corresponding entry stream (of the data carousel) contains a module of signaling information (DDB message). As described above, when the URI designation method is selected as the file location designation method of the data broadcasting application, the data carousel includes a module for transmitting each table DDMT and DCCT.

Ait_flag is set to 1 if the corresponding entry stream (of the data carousel) contains a module (DDB message) of the application information table AIT. As mentioned above, the AIT is transmitted either as a data carousel or as an independent packet (see Figure 2).

The application_data_flag is set to 1 if the corresponding entry stream (of the data carousel) contains a module of application data (DDB message).

When the signing_flag is 1, the 16-bit long signing_module_id describes the module ID in the data carousel of the signaling file DDMT transmitted as a DDB message. When the DDMT is transmitted, the DCMT is also transmitted. In the present embodiment, the module IDs of DDMT and DCCT are serial numbers (that is, DCCT is a module ID of +1), and the description in Additional_html5_info is omitted. Details of the data structure of each table DDMT and DCCT will be described later.

When ait_flag is 1, AIT attribute information ait_model_id, application_type, application_priority, and AIT_version_number are described. In ait_module_id, the module ID in the data carousel of the AIT file transmitted as a DDB message is described. In application_type, the value of the application format to be transmitted by AIT is described. When the application format is HTML5, application_type is 0x0010. In application_priority, the startup priority of the application type to be controlled by AIT is described. In AIT_version_number, the version number described in AIT is described.

When application_data_flag is 1, each flag of multipart_use_flag indicating whether or not multipart module transmission is applied to the data broadcasting application and multiple_app_flag indicating whether or not a plurality of applications are being transmitted. Is included.

Additional_html5_info () inserted in the data encoding descriptor, which is one of the ES descriptors in the second loop of PMT, specifies the transmission arrangement of AIT and the transmission arrangement information of signaling information (DDMT and DCCT). Please note that it will be done.

FIG. 8 shows the data structure 800 of the data carousel. The illustrated data carousel is a DSM-CC section that carries DII and DDB messages.

The table_id (table identifier) stores a number that identifies the shoulder of the data in the payload of the DSM-CC section. The value of this field applies a specific coding description to subsequent fields in the DSM-CC section. When the type of the DSM-CC section is a DII message, the table_id value is 0x3B, when the DDB message is a table_id value, the table_id value is ox3C, and when the private data is used, the table_id value is 0x3E.

The 1-bit field statement_index_indicator (section syntax instruction) indicates that CRC32 exists at the end of the section when it is 1, and that a checksum exists when it is 0.

In the 1-bit field private_indicator (private instruction), the inverted value of the value of the section syntax instruction is stored.

dsmcc_session_length (DSM-CC section length) indicates the byte length from immediately after the field to the end of the section. The value of this field does not exceed 4095.

The table_id_extension (table identifier extension) is set as described in (1) and (2) below according to the table_id.

(1) Set the table_id to 0x3B (when the DSM-CC section is a DII message) and set the lower 2 bytes of the transaction identifier.
(2) Set the module ID when table_id is 0x3C (when the DSM-CC section is a DDB message).

The version_number (version number) is set as described in (1) and (2) below according to the table_id.

(1) Set table_id to 0x3B (when the DSM-CC section is a DII message) and 0.
(2) Set the table_id to 0x3C (when the DSM-CC section is a DDB message) and the lower 5 bits of the module version.

The 1-bit curent_next_indicator (current next instruction) indicates that the subtable is the current subtable when it is 1. If it is 0, it means that the subtable to be sent is not applied yet and will be used as the next subtable. When table_id is 0x3A to 0x3C, 1 is always specified.

section_number (section number) represents the section number. If the section carries a DII message, set statement_number to 0 at all times. When transmitting a DDB message, the lower 8 bits of the DDB block number are stored in statement_number.

last_section_number (last section number) indicates the number of the last section (that is, the section with the highest section number) of the subtable to which the section belongs.

When table_id is 0x3B, the DII message is stored in the userNetworkMessage () of the DSM-CC section. When the table_id is 0x3C, the DII message is stored in the downloadDataMessage () of the DSM-CC section.

FIG. 9 shows the data structure 900 of the DII message transmitted in the DSM-CC section (data carousel).

In the dsmccMessageHeader (), header information that identifies the DII message in the data carousel transmission is described.

A label that identifies the data carousel is described in the downloadId (download identifier).

In blockSize (block length), the byte length of each block other than the end of the module of the data transmitted by the DDB message is described.

windowSize and ackPeriod are not used in data carousel transmission and their values are set to 0.

tCDownloadWindow is not used in data carousel transmission and its value is set to 0. Further, in the tCDownloadSCenario, the timeout time from the start to the end of the download is described in microseconds.

The competencyDescriptor () structure specified in ISO / IEC13818-6 is stored in the competebilityDescriptor ().

In numberOfModules (number of modules), the number of modules described in the subsequent loop in the DII message is described. Then, in the loop 901 of the module information repeated by the numberOfModules (number of modules), the information for each module transmitted by the data carousel is stored. As the attribute information of each module, moduleId (module identifier), moduleVersion (module version), and moduleInfoLength (module information length) are stored, and subsequently, a descriptor area composed of a loop that is repeated for the number of moduleInfoLength. The moduleInfoByte (module information) is stored in. The moduleInfoBite (module information) can be a descriptor for the corresponding module. The module identifier of the module described in the moduleInfoBite area is stored in the moduleId. In the present embodiment, in the case of the URI designation method, a node tag descriptor which is pointer information for designating the corresponding module is described as moduleInfoByte (module information). The module referred to here is a data module of an application and a signaling module of DDMT and DCCT. In the directory structure shown by DDMT, a node tag common to each directory and each file is specified, and in DCCT, it is also specified by a node tag (described later). Therefore, the directory and module are associated through the node tag descriptor of the DII message. This allows the DII message to be associated with the DDMT and DCCT tables. The details of the data structure of the node tag descriptor will be described later.

The byte length of the private data area is described in the privateDataLength (private data length), and the privateDataByte (private data) is stored in the descriptor area composed of loops repeated for the number of times of the privateDataLength. Examples of private data include a data structure defined by a data encoding method and a data structure defined for each business operator.

FIG. 10 shows the data structure 1000 of the DDB message transmitted in the DSM-CC section (data carousel). A DDB message is a data structure that transmits a block of data. A data block is a module divided into fixed-length block units. A block number is assigned to the DDB message, and the receiver 12 side reconfigures the module by arranging the data blocks in the order of the block number. Further, when transmitting a DDB message by MPEG-2 TS, only a DDB message having the same download ID must be included in a packet having the same PID. That is, it is not permissible to mix DDB messages of two different data carousels in one elementary stream.

Header information that identifies the DDB message in the data carousel transmission is described in the dsmcdownloadDataHeader (). The details of the header information will be omitted, but include a downloadID that uniquely identifies the data carousel.

In the moduleId, the identifier of the module to which the corresponding data block belongs is described. Further, in the module version, the version information of the module to which the corresponding data block belongs is described.

The blockNumber (block number) describes the position of the corresponding data block in the module. The block number of the data block at the beginning of the module must be 0. The data block body is stored in the block data area blockDataByte, which is composed of a loop that is repeated N times.

The data block stored in the blockDataBite includes a block of signaling data such as DDMT and DCCT in addition to the application data of data broadcasting (provided that the URI designation method is selected as the file location designation method). The node tag descriptor (described later) stored as the module information of the DII message can be used to filter the desired data block from the data carousel. However, the block of signaling data of DDMT and DCCT can be filtered by using the transmission arrangement information (signing_module_id) of Additional_html5_info () inserted in the data encoding method descriptor in the second loop of PMT. .. That is, on the receiver 12 side, the block of signaling data of DDMT and DCCT can be filtered at the stage of receiving PMT before reading the DII message. The details of the procedure for filtering data blocks from the data carousel will be described later.

FIG. 11 shows the data structure 1100 of the application information table (AIT). AIT is a signal that controls the start and end of an application and access to broadcast resources. AIT is transmitted via broadcasting or a communication path. In the present embodiment, as shown in FIG. 2, the AIT is assumed to be transmitted in a data carousel as one of data blocks (DDB messages) or transmitted as an independent packet. The AIT shown in FIG. 11 is used when the application control information is encoded by the section format defined in MPEG-2 Systems (ITU-T Rec. H222.0, ISO / IEC 13818-1). The application information table (AIT) also defines an XML description method, which may be used in the case of data carousel transmission.

The table_id (table identification) is an 8-bit fixed value that identifies the table as an application information (AI) table, and is 0x74 in this embodiment. The statement_sync_indicator (section syntax instruction) is a 1-bit field and is always set to "1". sectoin_length (section length) specifies the number of bytes in the section from the section length field to the end of the section containing CRC32. To ensure that the length of all sections does not exceed 4096, the section length shall not exceed 4096 (0xFFD in hexadecimal). application_type (application format) indicates the format of the application transmitted by AIT. The meaning of each value of applicaton_type is shown in FIG. version_number is the version number of the sub-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 representing 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 identifier 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 defines the byte length of the subsequent descriptor (descriptor). This descriptor stores the information of the common descriptor (descriptor) in a series of descriptor areas composed of a common descriptor loop for the number of command_descriptor_length. The contents of the common descriptor apply 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 application information descriptor loop 1101 is arranged for the number indicated by application_loop_length. At the end of AIT, ITU-T Recommendation H. The cyclic redundancy code CRC_32 according to 222.0 is added.

In one application information descriptor loop 1101, application_identifier (application identifier), application_control_code (application control code), application_descriptor_loop_length (application information descriptor loop length) are stored as attribute information of the application. The application_identifier is a value that uniquely identifies the application. The application_control_code is a control code that controls the state of the application. The application_descriptor_loop_length indicates the byte length of the subsequent application information descriptor area. Then, following the attribute information of these applications, the application information descriptor descriptor () is stored in the descriptor area consisting of the number of loops indicated by application_descriptor_loop_length. The descriptors in this descriptor area apply only to the corresponding application.

The semantics of application_control_code are specified for each application format, but if they are not specified for each application format, the semantics shown in FIG. 13 are used. If "AUTOSTART (automatic start)" is instructed as application_control_code, the receiver 12 that has referred to this AIT table starts the application specified by application_identifier. If "PREFETCH" is instructed as application_control_code, the receiver 12 that refers to this MH AIT table pre-reads the application specified by application_identifier. If "KILL" is instructed as application_control_code, the receiver 12 referring to this AIT table ends the execution of the application specified by application_identifier.

In the descriptor area in the application information descriptor loop 1101 of AIT, for example, an application descriptor (application_descriptor) and a transmission protocol descriptor (transport_protocol_descriptor) are stored as application information descriptor descriptors. The application descriptor specifies the protocol through which the application is transmitted (either HTTP / HTTPS transmission or data carousel transmission). Further, in addition to the protocol for transmitting the application, the transmission protocol descriptor specifies the file location designation method (whether the transmission path-dependent designation method or the URI designation method) in the case of data carousel transmission. Other application information descriptors such as a simple application location descriptor (application_application_location_descriptor) and an application boundary authority setting descriptor (application_boundary_and_permission_descriptor) are also arranged in the loop 1101, but detailed description thereof will be omitted.

FIG. 14 shows the application descriptor data structure 1400 stored in the descriptor area descriptor () in the application information descriptor loop 1101 of the AIT. In addition, FIG. 15 shows the semantics of each parameter of the application descriptor. One application descriptor is always arranged for each application in the application information descriptor loop 1101 of AIT.

The descriptor_tag is an 8-bit integer value 0x00 that identifies the descriptor. Descriptor_length is an area for writing the number of bytes of data of the descriptor following this field.

Information on application_profile is written in a series of regions consisting of loops of several minutes of application_profile_length. The application_profile is a profile of the receiver on which this application can be executed. The required function is shown by a bitmap for each function requested from the receiver. However, the upper 3 bits indicate functional bitmap switching. The above bitmap is specified for each version. In addition, version_major, version_minor, and version_micro are versions specified in the application profile, respectively.

service_bound_flag is a flag indicating whether or not this application is valid only for the current service. Visibility indicates whether or not it is visible to the user and other applications during the execution of this application. The application_priority is a relative priority between applications when a plurality of applications are operated.

The transport_protocol_label (transmission protocol label) is a value that uniquely identifies the transmission means when one application is transmitted by a plurality of routes, and corresponds to a field having the same name in the transmission protocol descriptor.

FIG. 16 shows a transmission protocol descriptor data structure 1600 stored in the descriptor area descriptor () in the application information descriptor loop 1101 of the AIT. The transmission protocol descriptor is a descriptor intended to indicate the specification of a transmission protocol such as broadcasting or communication and the file location specification method of application data depending on the transmission protocol as the transmission means of the application. The transmission protocol descriptors are arranged in the AIT common descriptor loop or the application information descriptor loop 1101 by the number of transmission protocol labels of the application descriptor.

Descriptor_tag is an 8-bit integer value 0x02 that identifies the descriptor. Descriptor_length is an 8-bit area for writing the number of bytes of the data of the descriptor 0 following this field.

The protocol_id (protocol identifier) indicates the protocol for transmitting the application. In the present embodiment, as the value of protocol_id, 0x0003 defines HTTP / HTTPS transmission, 0x0004 defines transmission line-dependent designated data carousel transmission, and 0x0006 defines URI-designated data carousel transmission. The transport_protocol_label (transmission protocol label) is a value that uniquely identifies the transmission means when one application is transmitted by multiple routes, and corresponds to the field of the same name in the application descriptor (see FIG. 14). To do.

The selector_byte (selector byte) is an area for storing supplementary information specified for each protocol identifier, and the syntax is specified for each protocol identifier. In the present embodiment, the acquisition location of the application data is written in the selector_byte. When the protocol identifier is 3 (that is, HTTP / HTTPS transmission) and the protocol identifier is 6 (URI-designated data carousel transmission), and when the protocol identifier is 4 (transmission path-dependent designation method data carousel transmission). So, the protocol of selector_byte is different. Details of the selector byte syntax in each case will be given later.

As described above, in the present embodiment, when the data of the HTML5 data broadcasting application is transmitted by the data carousel transmission method, the transmission line-dependent designation method and the URI (URI), which have been conventionally applied as the file location designation method, are used. The Uniform Resource Indicator) designation method can be selectively used.

First, a transmission line-dependent designation method will be described. The transmission line-dependent file location specification method is a method of specifying file data of a data broadcasting application in a hierarchy of broadcasting transmission lines such as network identifier, transport stream identifier, service identifier, component tag, and module identifier. ..

In the transmission protocol descriptor arranged in the application information descriptor loop 1101 of the AIT, the protocol identifier is set to 4, indicating that the data carousel transmission is the (conventional) transmission path-dependent specification method, and the selector byte area. Specify the hierarchy of the above broadcast transmission line with.

Further, in the transmission line-dependent specification method, file data is stored in the application based on the transmission line hierarchy (network identifier, transport stream identifier, service identifier, component tag, module identifier) as described above. Specify in the following namespace.

arib-dc: // <newwork_id>. <Transport_stream_id>. <Service_id> / <component_tag> / <module_id> / <resource_name>

In the conventional transmission line-dependent designation method, signaling information such as DDMT and DCCT is not applied. Therefore, since DDMT and DCCT are not transmitted (in the data carousel), the transmission efficiency and processing efficiency of the data broadcasting application are good. However, due to the data / carousel transmission method, it is considered that there are many restrictions on creating an application (described above).

Next, the URI designation method will be described. In this method, it is possible to specify the file data of the data broadcasting application by an arbitrary URI.

In the transmission protocol descriptor arranged in the application information descriptor loop 1101 of the AIT, the protocol identifier is set to 6, indicating that the data carousel transmission is of the URI designation method, and the URI is specified in the selector byte area. Also, in the application, the file data is specified by URI.

Further, in the URI designation method, signaling information such as DDMT or DCCT is applied. DDMT is a table that manages the directory structure of files transmitted by data broadcasting. Further, the DCCT is a table showing the file structure for each content, the file structure for each data broadcasting presentation unit (PU) in the content, the content structure such as the file to be cached in advance, and the cache control. By applying DDMT and DCCT, a sufficient degree of freedom in application production can be ensured. In addition, broadcasting and communication can be handled in an integrated manner. However, as the DDMT and DCCT are transmitted by the data carousel, the transmission efficiency and processing efficiency of the data broadcasting application are slightly sacrificed.

FIG. 17 shows the data structure 1700 of the selector bytes in the transmission protocol descriptor in the case of (conventional) transmission line dependent designation method data carousel transmission.

remote_connection (remote connection) is 1 if the data carousel that transmits the AIT and the application is not transmitted by the same service (including the case where the AIT is communication acquisition), and 0 if it is transmitted by the same service. ..

When remote_connection is 1, that is, when the data carousel that transmits the AIT and the application is not transmitted by the same service, the parameters of original_newwork_id, transport_stream_id, and service_id are described. original_newwork_id is the original network identifier in which the application is being transmitted. transport_stream_id is the transport stream identifier in which the application is being transmitted. service_id is the service identifier in which the application is being transmitted. If remote_connection is 0, that is, the data carousel that transmits the AIT and the application is transmitted by the same service, the description of these parameters is omitted.

In component_tag, a component tag value indicating a service component to which the application is transmitted is described. The component tag given in the stream identification descriptor, which is one of the ES descriptors placed in the second loop of the PMT, specifies the component stream to which the data carousel is transmitted.

FIG. 18 illustrates a file designation method in the case of (conventional) transmission line dependent designation method data carousel transmission.

On the receiver 12 side, the data encoding descriptor (data_component_descriptor) (FIG. 6) described in the second loop corresponding to the elemental stream of the data carousel of the PMT (see FIG. 5). Acquire an AIT based on the AIT module identifier contained in the Additional_html5_info (see FIG. 7) inserted in (see) (provided that the AIT is transmitted by the data carousel transmission method). .. Alternatively, when the AIT is transmitted as an independent packet, the AIT is acquired based on the packet identifier (AIT PID) of the AIT described in the second loop corresponding to the elemental stream of the AIT. ..

In the descriptor area in the application information descriptor loop of AIT (see FIG. 11), an application descriptor (application_descriptor), a transmission protocol descriptor (transport_protocol_descriptor), a simple application location descriptor (simple_application_location_descript), etc. are stored. Has been (mentioned above).

The transmission protocol descriptor that matches the transport protocol label (= 1) of the application descriptor of the desired application is filtered as shown by reference number 1801, and the transmission protocol description is further shown by reference number 1802. Specifies the component stream through which the data carousel is transmitted, based on the selector bytes (component tags) stored in the child. You can also filter DII messages from within the data carousel.

In addition, the simple application location descriptor includes a character string (application character string) indicating the URL of the entry point of the corresponding application. This application string is a relative path rooted at the retrievable location of the application indicated by the selector byte of the transmission protocol descriptor, and in the example shown, the application string is the module identifier of the application (example shown). Then, it consists of a combination of 0010) and the resource name (index.html in the illustrated example).

Also, each module in the data carousel is identified using a module identifier and a resource name. From the data carousel, the section in which 0x3B is stored as the table identifier (table_id) can be obtained as a DII message. You can also use the resource name to filter DDB messages.

FIG. 19 illustrates a directory structure in the case of (conventional) transmission line dependent designation method data carousel transmission.

In the loop of each module of the DII message, the module identifier (module_id) and the module name (module_name) are stored as pointer information for each module m ₁ , m ₂ , ... m _k . When the module is multiparted, the DDB message is composed of a list of multiparted resources (file names) (Resource List: RL) and each multiparted resource (file data). File.

In the directory structure of data carousel transmission using the channel-dependent specification method, the component specified by the selector byte (component tag) of the transmission protocol descriptor corresponds to the root directory. In addition, each module in which the module identifier is listed in the module loop of the DII message corresponds to a subdirectory, and the multipart file data is arranged directly under each subdirectory, which is a directory structure.

From the HTML document of communication acquisition, A. When referring to the module (file data) called html, the link tag is as follows.

ref = arib-dc: // 7EE9.7FE9.0448 / 40/0000 / A. html

In addition, A. From html to B. When referring to html, the link tag is as follows.

ref =. .. / 0001 / B. html

FIG. 20 illustrates the signaling relationship of application acquisition in the case of data carousel transmission of the transmission line dependent designation method.

Specify a packet in the data carousel based on the PID described in the second loop that corresponds to the elemental stream of the data carousel in the PMT (see Figure 5), as shown in reference 2001. can do.

Further, as shown by the reference number 2002, the additional_https5_info (see FIG. 7) inserted in the data encoding descriptor (data_component_descriptor) (see FIG. 6) described in the second loop. ), The AIT can be acquired based on the module identifier (ait_module_id) of the AIT (provided that the AIT is transmitted by the data carousel transmission method). Alternatively, as shown by reference number 2003, when the AIT is transmitted as an independent packet, the packet identifier (AIT PID) of the AIT described in the second loop corresponding to the elemental stream of the AIT. AIT can be obtained based on.

Since the protocol identifier of the transmission protocol descriptor of the application for which application_control_code is specified as "AUTOSTART" in the application information descriptor loop of AIT (see FIG. 11) is 4, the transmission path. It can be recognized that the data carousel transmission is a dependency specification method. Then, based on the selector byte (coment_tag) described in the transmission protocol descriptor, the DII message in the data carousel is acquired as shown by the reference number 2004.

In this way, as indicated by reference number 2005, the module identifier and resource name contained in the simplified application location descriptor within the same application information descriptor ("0010 / index.html" in the illustrated example). And the DDB message to transmit the corresponding application (file data) can be specified based on the combination with the downstreamID described in the DII message.

FIG. 21 shows the data structure 2100 of the selector byte in the transmission protocol descriptor in the case of HTTPS / HTTPS transmission and data carousel transmission of the URI designation method.

URL_base_length indicates the number of bytes in the base part of the URL for acquiring the application. The URL_base_byte stores the character string of the base part of the URL for acquiring the application in a series of areas including a loop of several minutes of the URL_base_length.

URL_extension_count indicates the number of extension parts of the URL for acquiring the application. URL_extension loops are arranged for the number of URL_extension_counts. Then, in one URL_extension loop, a URL_extension area consisting of a URL_extension_byte indicating the number of bytes of the extension part of the URL for acquiring the application and a loop for the number of URL_extension_strings is arranged, and the URL_extension is used to acquire the application. Stores the character string of the extension part of the URL of.

In short, the selector byte shown in FIG. 21 describes the character string of the URL for acquiring the application in a folding manner, and the URL can be completed by concatenating the character strings.

Since the selector bytes shown in FIG. 21 are looped as a whole, it is possible to set a plurality of base portions of URLs from which applications can be acquired.

FIG. 22 shows a file designation method in the case of data carousel transmission of the URI designation method.

On the receiver 12 side, the data encoding descriptor (data_component_descriptor) (FIG. 6) described in the second loop corresponding to the elemental stream of the data carousel of the PMT (see FIG. 5). Acquire an AIT based on the AIT module identifier contained in the Additional_html5_info (see FIG. 7) inserted in (see) (provided that the AIT is transmitted by the data carousel transmission method). .. Alternatively, when the AIT is transmitted as an independent packet, the AIT is acquired based on the packet identifier (AIT PID) of the AIT described in the second loop corresponding to the elemental stream of the AIT. ..

In the descriptor area in the application information descriptor loop of AIT (see FIG. 11), an application descriptor (application_descriptor), a transmission protocol descriptor (transport_protocol_descriptor), a simple application location descriptor (simple_application_location_descript), etc. are stored. Has been (mentioned above).

As indicated by reference numeral 2201, the transmission protocol descriptor that matches the transport protocol label (= 1) of the application descriptor of the desired application is filtered. Furthermore, when the URL described in the selector byte of the transmission protocol descriptor in the folding method is completed and the URL for acquiring the application is obtained, as shown by reference number 2202, the URL is stored in the data carousel. , Signaling information DDB messages that carry DDMT can be filtered.

In this embodiment, in the directory structure represented by DDMT, a common node tag is specified for each directory and each file. In addition, it is also specified by the node tag in DCCT. Further, in the case of the URI designation method, the node tag descriptor is arranged in the module information (moduleInfoByte) of the DII message, and the directory and the module are associated with each other. This allows the DII message to be associated with the DDMT and DCCT tables.

Details of the data structure of the node tag descriptor will be described later. DII messages are filtered from the data carousel based on the node tag values described in the DDMT, as indicated by reference number 2203. In addition, as indicated by reference number 2204, DDB messages that carry the desired application data are filtered based on the module identifier contained in the DII message.

FIG. 23 shows the data structure 2300 of the node tag descriptor, which is arranged in the module information (modularInfoByte) of the DII message in the case of the URI designation method.

The descriptor_tag is an 8-bit integer value 0x00 that identifies the descriptor. Descriptor_length is an area for writing the number of bytes of data of the descriptor following this field.

node_level is a 1-bit value indicating the level of the node specified by the node tag. If the node is a module, 0 is entered, and if the node is a resource, 1 is entered.

If the node level value is 0, that is, the node is a module, the node tag node_tag of the 16-bit long module is described.

On the other hand, when the node level value is 1, that is, when the node is a resource, the node tag node_tag of each resource is described in the resource number resource_number in the module and the loop for the number of resources following it. ..

As described above, when the URI designation method is selected as the file location designation method in the data carousel transmission, the signaling information of the data directory management table (DDMT) and the data content management table (DCCT) is transmitted as a DDB message. (See Figure 2). DDMT and DCCT are expressed in XML notation format and binary notation format. These signaling information will be described.

DDMT is a table that manages the directory structure of files transmitted by data broadcasting. FIG. 24 shows the DDMT data structure 2400 in binary notation format.

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

base_direction_path_length represents the size of the information area of base_direction_path_byte in bytes. base_direction_path_byte stores the path name to base_direction (upper directory) in a series of information areas consisting of loops of several minutes of base_direction_path_length. base_directory_path_byte is represented, for example, in the absolute URL format for accessing the corresponding directory.

number_of_direction_nodes indicates the number of nodes in the directory described in the DDMT. Then, loop 2401 of the directory node is arranged for the number of number_of_direction_nodes.

In the loop of one directory node, the information of each directory node stored in the DDMT and the information of each file data contained in the base directory are stored.

direction_node_path_length represents the size of the information area of directoryy_node_path_byte in bytes. The directory_node_path_byte is composed of a series of information areas consisting of loops of several minutes of the directoryy_node_path_length, and stores the path name to the directoryy_node. directory_node_path_byte is represented, for example, in the form of a URL relative to base_direction_path for accessing the corresponding directory. For example, if the path name (URL) of base_direction is "http://www.xbc.com" and the bus name (URL) of a certain folder_direction is "index.html", these character strings are concatenated. You can get the complete URL "http://xbc.com/index.html".

number_of_files indicates the number of files listed in the DDMT. Then, loops 2402 of the file node are arranged for the number of num_of_files.

In the loop of one file node, node_tag and file_name_byte (file name) are stored as information of each file data included in the base directory. node_tag is a value that specifies each directory and each file in common in the directory structure indicated by DDMT. Also in DCCT, it is specified by the node tag. Further, as described above, the node tag descriptor is placed in the module information (moduleInfoByte) of the DII message to associate the directory with the module. file_name_byte (file name) is stored in a series of file name areas consisting of loops of several minutes of file_name_length.

Further, FIG. 25 shows the data structure 2500 of the DDMT in the XML notation format. DDMT has a URL (@baseURI) of the root directory as an attribute and a directory node (directory) as an element.

Each directory has a directory node tag (@nodeTag) and a directory node URL (@uri) as attributes, and has a file node (file) included in the directory as an element.

Each file node has a node tag (@nodeTag) of the file node and a name (@name) of the file node as attributes.

A description example 2600 of DDMT in XML notation format is shown in FIG.

DCCT indicates a file configuration for each content (application) transmitted by data broadcasting, a file configuration for each data broadcasting presentation unit (PU) in the content (application), a content configuration such as a file to be cached in advance, and cache control. It is a table. FIG. 27 shows the DCCT data structure 2700 in binary notation format.

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

The number_of_content is an 8-bit parameter that indicates the number of contents transmitted in the data carousel. The content is, for example, file data such as a data broadcasting application described in HTML5 format or monomedia used in the application. The following content loops 2701 are arranged for the number of number_of_content, and information for each content is stored.

In the loop of one content, information about the content_ID, the content_version, the content_cache_size, and the data broadcasting presentation unit (Presentation Unit: PU) included in the content is written as the information about the content. content_ID is an identifier for the content. content_version indicates the content version. content_cache_size indicates the size to cache the content. Further, the number_of_PU is the number of data broadcasting presentation unit PUs included in the content, and loops 2702 of the PUs are arranged by the number of the number_of_PU.

In the loop of one PU, PU_tag which is the identification information of PU, PU_cache_size which indicates the size to cache the PU, and PU_primary_module_node_tag which identifies the file (primary module) which is the center of the data broadcasting presentation unit (PU). Written.

Further, in the loop of the PU, a list of broadcast transmission files constituting the data broadcasting presentation unit (PU) is written. Specifically, number_of_PU_member_nodes indicates the number of nodes included in the data broadcasting presentation unit (PU) (that is, members of the PU). After that, loops of PU member nodes are arranged as many as the number of number_of_PU_member_nodes, and the node_tag of the PU member nodes is written in the loop of each PU member node. PU member nodes include directory nodes and item nodes.

Further, in the loop of the PU, if the lock target file exists in the corresponding PU, the information of the target file list is described. Specifically, number_of_lock_cache_nodes is the number of nodes to be locked, and loops of lock cache nodes are arranged for the number of number_of_lock_cache_nodes. A lock_cache_node_tag that identifies the lock cache node is written in the loop of one lock cache node.

Further, in the loop of the PU, if the unlock target file exists in the corresponding PU, the information of the target file list is described. Specifically, number_of_unlock_cache_nodes is the number of nodes to be unlocked, and loops of lock cache nodes are arranged as many as the number of number_of_unlock_cache_nodes. An unlock_cache_node_tag that identifies the unlock cache node is written in the loop of one unlock cache node.

The lock target file referred to here is composed of, for example, a broadcast file list used in the data broadcasting presentation unit (PU) to be referred to next from the current data broadcasting presentation unit (PU). By presenting the lock and unlock target file list with the signaling information of data broadcasting on the production side of the broadcast program, the receiver side can perform the cache control operation by locking and unlocking. For example, on the receiver side, the file data required for the next data broadcasting presentation unit to be transitioned can be locked (that is, forced cache) in the cache. As a result, a timely data broadcasting service linked to the broadcasting program can be realized. Further, the unlock target file is composed of, for example, a broadcast file list that is unnecessary in the current data broadcasting presentation unit (PU). By specifying the file to be unlocked (that is, canceling the specification of the forced cache), unnecessary files can be deleted from the cache memory 407, and the memory size can be saved.

Further, in the loop of one PU, a number_of_linked_PU indicating the number of other PUs linked from this PU and a loop of linked_PU as many as the number of number_of_linked_PU are arranged. In the loop of one linked_PU, linked_PU_tag which is the identification information of linked_PU is written.

Further, FIG. 28 shows a DCCT data structure 2800 in XML notation format. The DDMT has a data content as an element.

Each data content has a content identifier (@id), a content version (@version), a cache size at the time of caching the entire content (@cacheSize) as attributes, and a presentation unit (PU) as an element. ..

Each presentation unit has the identification tag (@tag) of the presentation unit, the cache size (@cacheSize) at the time of the presentation unit cache, and the node tag (@primary) of the primary node in the presentation unit as attributes. As an element, it has a node (Member) that constitutes a presentation unit, a forced cache designation node (locclCacheNode), a forced cache release designation node (unlockCacheNode), and a link destination presentation unit (linkedPU).

The node (Member) constituting the presentation unit has a node tag (@nodeTag) as an attribute. The forced cache designation node (loclCacheNode) has a node tag (@nodeTag) as an attribute. The forced cache release designation node (unlockCacheNode) has a node tag (@nodeTag) as an attribute. The link destination presentation unit (linkedPU) has a presentation unit identification tag (@puTag) as an attribute.

FIG. 29 shows a description example 2900 of DCCT in XML notation format.

FIG. 30 illustrates the transmission of the data broadcasting application (content) transmitted by the data carousel, the location of the content, and the mechanism for presenting the application.

FIG. 30A shows the content directory structure. Each content 1, 2, ... Consists of a data broadcasting application (application) and a material. Data broadcasting applications and materials are resources whose substance is file data. Each resource can be identified by a 16-bit node_tag in data carousel transmission. As shown in FIG. 30C, it is transmitted as a module (DDB message) in the data carousel transmission of the corresponding component, and can be specified by a module identifier (moduleId). The application consists of one or more HTML5 documents that are referenced when the content is executed (when the data broadcast is presented). The material is an image file such as jpg or png referenced from the HTML5 document, monomedia data such as text, or the like. One HTML5 document and the material referred to from the HTML5 document constitute one data broadcasting presentation unit PU. In the example shown in FIG. 30 (A), content1 is A11. html, A12. html, A13. It has one or more HTML documents such as html as a resource of a data broadcasting application. Of these, A11. The html is a resource that is directly referenced when the content is executed.

FIG. 30B shows the reference relationship between the resources when the content is executed (when the data broadcasting is presented). In the illustrated example, the application A11 directly referred to when the content is executed and the materials B11 and B02 referred to by the application A11 are resource groups 3001 constituting one data broadcasting presentation unit PU, and p1 is assigned as the PU_tag (PU_tag). In addition, B14 is a material that can be acquired at any time by HTTP transmission by communication instead of being transmitted by data carousel by broadcasting, and is treated below as not included in the resource group of the data broadcasting presentation unit). ..

Similarly, application A12 and materials B12, B02, and B13 referred to therein are resource groups 3002 constituting one data broadcasting presentation unit PU, and p2 is assigned as PU_tag (Note that B07 is data by broadcasting). -It is a material that can be acquired at any time by HTTP transmission by communication instead of carousel transmission, and will be treated as not included in the resource group of the data broadcasting presentation unit below). Similarly, the application A01 and the materials B03, B01, and B04 referred to therein are resource groups 3003 constituting one data broadcasting presentation unit PU, and p3 is assigned as PU_tag.

In addition, a link reference relationship can be established between a plurality of HTML5 documents (well-known). In the example shown in FIG. 30 (B), resource A01. html is an HTML document that describes the application presentation screen that is directly referenced and displayed first when the content is executed. On the other hand, resource A12, which is included in the same content1. Resource A01. Included in html and external content common of content1. HTML is A01. This is an HTML document that describes an application presentation screen that transitions from the screen presented by executing html. A11. Has a link reference relationship with html. Each resource A01. html, A12. html, A01. The html forms resource groups 3001, 3002, and 3003, each of which constitutes one data broadcasting presentation unit PU. Then, the linked data broadcasting presentation units 3001, 3002, and 3003 form a larger resource group 3010 at a higher level. Resource A01. html, A12. html, A01. HTML is a file data (primary module) that is central to each data broadcasting presentation unit PU.

Also, the entire application contained in the package (one broadcast program), and the entire content, constitutes a large resource group, that is, the entire data content. The entire data content is the range of the data broadcasting presentation unit PU having a common content_ID. By turning the loop of the PU of the corresponding content_ID in DCCT, all the data broadcasting presentation unit PUs included in the content can be specified at once. In the example shown in FIG. 30B, the application included in content1 and common forms a resource group 3020 for the entire content, and c1 is assigned as the content identifier.

FIG. 30C schematically shows how the file data constituting the content is transmitted by the data carousel. File data such as applications and materials, which are components of content, are transmitted in module units divided into blocks. Each module corresponds to a DDB message in the data carousel transmission line. In data carousel transmission, each module is assigned a module identifier (moduleId). In the illustrated example, content1 is transmitted as an ES stream of component1, and i11, i12, i13, and i14 are assigned as module identifiers to each module that divides file data such as HTML document data and materials. ..

As shown in FIG. 24, in the signaling information DDMT, a common node tag is specified for each directory and each file in the directory structure. Also, in the DII message, the node tag descriptor is placed in each module information (modelInfoByte) to associate each module with the node tag. Therefore, by specifying the node tag, the directory can be used. Modules can be associated.

FIG. 31 illustrates the signaling relationship of application acquisition in the case of data carousel transmission of the URI designation method.

Specify a packet in the data carousel based on the PID described in the second loop that corresponds to the elemental stream of the data carousel in the PMT (see FIG. 5), as shown in reference 3101. can do.

Further, as shown by reference numeral 3102, additional_html5_info (see FIG. 7) inserted in the data encoding descriptor (data_component_descriptor) (see FIG. 6) arranged in the second loop. ), The AIT can be acquired based on the module identifier (ait_module_id) of the AIT (provided that the AIT is transmitted by the data carousel transmission method). Alternatively, as shown by reference number 3103, when the AIT is transmitted as an independent packet, the packet identifier (AIT PID) of the AIT described in the second loop corresponding to the elementary stream of the AIT. AIT can be obtained based on.

In the application information descriptor loop of AIT (see FIG. 11), since the protocol identifier of the transmission protocol descriptor of the application whose application_control_code is specified as "AUTOSTART (automatic start)" is 6, the URL is specified. It can be recognized that it is a data carousel transmission of the method.

Further, as shown by reference numerals 3104 and 3105, there is an additional_https5_info (see FIG. 7) inserted in the data encoding descriptor (data_component_descriptor) (see FIG. 6) described in the second loop. DDMT and DCCT can be acquired based on the module identifier (signing_model_id) of each signaling information of DDMT and DCCT included in (However, when AIT is transmitted by the data carousel transmission method). ).

Then, as shown by the reference number 3106, it matches the URL character string described in the selector byte of the transmission protocol descriptor of the AIT in the loop of the directory node and the loop of the file node (described above) of the DDMT. Find the file and get its node tag. When a fiber to another HTML5 document referred to in the application is specified, the same processing is performed as shown by reference number 3111.

If a node with a matching URL character string is not found in the DDMT, the file data of the corresponding application can be acquired via communication (Internet) based on the URL. That is, one of the advantages of the URI designation method is that the data broadcasting application can be acquired without distinguishing between broadcasting and communication.

Then, as shown by reference number 3107, in the loop (described above) of the module information of the DII message, the node tag descriptor matching the above node tag is searched, and the module identifier corresponding to the node tag is searched. To get.

In this way, as shown by reference number 3108, the corresponding application (from the data carousel) based on the combination of the obtained module identifier and the download identifier (downloadID) described in the DII message. You can specify a DDB message to carry (file data).

If you want to cache the nodes (directories and files) linked to the application specified in "AUTOSTART", it corresponds to the loop of PU of DCCT (described above) as shown by reference number 3109. Search for the node tag to be used, and as shown by reference number 3110, search the PU loop to perform pre-cache based on the linked PU tag, and forcibly cache or unlock the locked file. You can cancel the forced cache specification of the file.

FIG. 32 shows in the form of a flowchart the procedure of application data acquisition and activation processing executed when the digital broadcasting channel selection process is performed in the receiver 12.

The tuner / demodulation unit 401 selects and receives the broadcast signal, and the demultiplexer 402 demultiplexes the broadcast stream and separates it into the original elementary streams, and each elementary stream. Depacketize the process.

First, the system control unit 409 reads the PID of the PAT of the corresponding broadcast channel from the elementary stream of PSI / SI with reference to the PAT of PID = 0, and acquires the PMT (step S3201).

In addition, playback of the video and audio of the selected broadcast channel is started (step S3202). Specifically, the video decoder 404 and the audio decoder 405 decode the encoded video signal and the encoded audio signal, respectively, while synchronizing the reproduction timing based on the clock information STC reproduced by the clock reproduction unit 403. , Get the baseband video signal.

When the AIT is transmitted as a module (DDB message) in the data carousel (Yes in step S3203), the application data control unit 406 is set in the data encoding descriptor arranged in the second loop of the PMT. The AIT is acquired based on the AIT module identifier (ait_module_id) included in the inserted Additional_html5_info (see FIG. 7) (step S3204). Alternatively, when the AIT is transmitted as an independent packet (No in step S3203), the application data control unit 406 is assigned to the packet identifier (AIT PID) of the AIT described in the second loop of the PMT. Based on this, the AIT is acquired from an independent component (step S3205).

Next, the application data control unit 406 determines the file location specification method for data carousel transmission by referring to the protocol identifier of the transmission protocol descriptor arranged in the application information descriptor loop of the acquired AIT (step). S3206).

Here, when the protocol identifier is 4, that is, the transmission path-dependent designation method, the application data control unit 406 is designated by the selector byte (see FIG. 17) described in the transmission protocol descriptor of the AIT. The DII message is acquired from the component tag (step S3207). Specifically, a section in which 0x3B is stored as a table identifier (table_id) is acquired as a DII message from the data carousel. The application data control unit 406 then acquires the application entry module based on the content of the DII message (see FIGS. 18 and 20) and controls the cache processing of the module as needed. (Step S3208).

On the other hand, when the protocol identifier is 6, that is, the URI designation method, the application data control unit 406 acquires the DII message and each signaling information DDMT and DCCT from the data carousel whose PID is designated by the PMT ( Step S3209). Specifically, a section in which 0x3B is stored as a table identifier (table_id) is acquired as a DII message from the data carousel. Also, as shown in FIG. 31, it is included in the Additional_html5_info (see FIG. 7) inserted in the data encoding descriptor located in the second loop of the PMT (see FIG. 5). The DDMT and DCCT are acquired based on the module identifier (signing_module_id) of each signaling information of the DDMT and DCCT.

The application data control unit 406 resolves the location of the file data related to the data broadcasting application to be started by using the acquired DDI message and each signaling information DDMT and DCCT (step S3210). Specifically, as shown in FIG. 31, a file that matches the URL character string described in the selector byte of the transmission protocol identifier as the desired application location in the loop of the application information descriptor of AIT. -When the node tag of the data is searched from the DDMT, the module identifier of the module associated with the node tag is subsequently searched in the module information loop of the DII message. Then, based on the combination of the obtained module identifier and the download identifier, the module (DDB message) for transmitting the corresponding application (file data) is specified from the data carousel.

Then, the application data control unit 406 acquires the entry module of the application by using the above-mentioned location solving means (see FIGS. 22 and 31), and controls the cache processing of the module as needed. (Step S3211).

In the present embodiment, the DCCT as the signaling information is the node tag of the lock target file, the node tag of the unlock target file, and the link destination of the current data broadcasting presentation unit (PU) as the information indicating the cache control. Describes the node tag of the presentation unit. Therefore, the application data control unit 406 forcibly caches the lock target file (for example, the file data required for the next transition data broadcast presentation unit) or unlocks the lock target file (for example, the current data broadcast presentation unit). It is possible to cancel the designation of the forced cache of (file data that is no longer needed) and delete it from the cache 407, or to cache the file data of the link destination presentation unit in advance.

Then, the application data control unit 406 uses the entry module of the application acquired according to each file location designation method of the transmission path-dependent designation method or the URI designation method, and the file data cached in the cache 407. Control the startup of the application by the data broadcasting application engine 408 (step S3211).

As described above, in the present embodiment, the signaling information DCCT applied by the URI designation method includes the node tag of the lock target file, the node tag of the unlock target file, and the current state as information indicating cache control. The node tag of the link destination presentation unit of the data broadcasting presentation unit (PU) is described. Therefore, the application data control unit 406 forcibly caches the lock target file (for example, the file data required for the next transition data broadcast presentation unit) or unlocks the lock target file (for example, the current data broadcast presentation unit). It is possible to cancel the designation of the forced cache of (files and data that are no longer needed) and delete it from the cache 407. It is also possible to cache the file data of the link destination presentation unit in advance.

The general procedure for controlling the cache operation by locking and unlocking the module transmitted in the data carousel based on the signaling information DCCT in the receiver 12 is shown below.

(Operation 1) The application data control unit 406 acquires the latest information while appropriately detecting and updating the signaling information DDMT and DCCT transmitted in the data carousel.
(Operation 2) The application data control unit 406 responds by accessing the application file (which is the center of the data broadcasting presentation unit) specified in the prime mode by the instruction from the data broadcasting application control engine 408 or the like. Recognize that the data broadcasting presentation unit (PU) has entered the presentation state.
(Operation 3) In DCCT, the application data control unit 406 also simultaneously acquires each member file (PU_member_node) included in the corresponding data broadcasting presentation unit (PU) and holds it in the cache memory 407.
(Operation 4) Further, when the lock cache target is specified for the corresponding data broadcast presentation unit (PU) in the DCCT, the application data control unit 406 has not acquired the lock cache target. Each file (module) of is also acquired, cached in the cache memory 407, and separately managed as a lock cache target file.
(Operation 5) On the contrary, when the corresponding data broadcasting presentation unit (PU) is designated as the unlock cache target in the DCCT, the application data control unit 406 sets the unlock target file. If it is cached in the cache memory 407, it is deleted and also deleted from the separately managed lock cache target file.
(Operation 6) The data broadcasting application engine 408 executes the application file specified in the primary module from the cache memory 407.
(Operation 7) After that, when the configuration of the member file (PU_member_node) included in the data broadcasting presentation unit (PU) currently in the presentation state and the file to be locked or unlocked is changed due to the update of DCCT. , The above processes (operation 3) to (operation 6) are performed.
(Operation 8) When the application operation in the data broadcasting application engine 408 causes a transition to the presentation state of another data broadcasting presentation unit (PU), the file to be locked cache is temporarily held in the cache memory 407 and then held in the cache memory 407. The above processes (operation 3) to (operation 6) are performed. Files other than the lock cache target may be deleted from the cache memory 407.

FIG. 33 shows the cache control procedure by locking and unlocking in the receiver 12 in the form of a flowchart.

When the data broadcasting application control engine 408 is performing the application operation, that is, the presentation of the data broadcasting (Yes in step S3301), the application data control unit 406 is in the data content management table, and the primary_module (data broadcasting presentation unit). By accessing the application file specified in (center of) (Yes in step S3302), it is recognized that the presentation state of the corresponding data broadcasting presentation unit (PU) has been entered.

The application data control unit 406 resets the cache memory 407, acquires the primary_model of the data broadcasting presentation unit (PU) currently presented in DCCT, and the node tag (PU_member_node_tag) of each member, and caches the cache. -Holding in the memory 407 (step S3303). The data broadcasting application engine 408 executes the application file specified in prime_module from the cache memory 407.

Further, the application data control unit 406 checks whether or not the lock cache target is specified for the corresponding data broadcasting presentation unit (PU) in the data content management table (step S3304). Then, when the target of the lock cache is specified (Yes in step S3304), the application data control unit 406 also acquires each file (module) that has not been acquired among the lock cache targets, and cache memory. It is cached in 407 and separately managed as a lock cache target file (step S3305).

Further, the application data control unit 406 checks whether or not the unlock cache target is specified for the corresponding data broadcasting presentation unit (PU) in the DCCT (step S3306). Then, when the target of the unlock cache is specified (Yes in step S3306), the application data control unit 406 deletes the unlock target file if it is cached in the cache memory 407. At the same time, it is also deleted from the separately managed lock cache target file (step S3307).

After that, if the configuration of the member node (PU_member_node) included in the data broadcasting presentation unit (PU) currently being presented or the file to be pre-cached changes due to the update of DCCT (Yes in step S3308), step. Returning to S3303, the above process is repeatedly executed in the data broadcasting presentation unit (PU) currently in the presentation state.

In addition, when the application operation in the data broadcasting application engine 408 transitions to the presentation state of another data broadcasting presentation unit (PU) and the application file specified in the primary_model of the data broadcasting presentation unit is accessed (step). Yes) in S3309, the process returns to step S3303, and the above process is repeatedly executed in the data broadcasting presentation unit (PU) to which the transition has occurred.

The above processing is repeatedly executed until the data broadcasting application engine 408 finishes the application operation (No in step S3310).

FIG. 34 shows an example of locking and unlocking the cache of file data in the receiver 12.

The application data control unit 406 analyzes various signaling messages received from the data carousel. A data content management table (DCCT), which is one of the signaling information, is included.

When the data broadcasting application control engine 408 is performing the application operation of the data broadcasting presentation unit (PU) identified by PU_tag = 1, the application data control unit 406 refers to the DCCT and is currently presenting the data. Data of the application file "A01.html" specified in the Primary_mode (center of the data broadcasting presentation unit) of the broadcast presentation unit (PU_tag = 1), and the node_tag of each member (PU_member_node) "B01" and "B02". -Obtaining from the content management table and getting the modules corresponding to these nod_tags from the data carousel, they are cached in cache memory 407, as indicated by reference number 3401. However, since the lock cache target is not specified for this data broadcasting presentation unit (PU), the cache operation is not performed. The method of accessing the module transmitted from the node_tag to the data carousel is as described with reference to FIG. 31 (based on the combination of the module identifier (moduleId) corresponding to the node_tag in the DII message and the downloadID). You can filter the applicable modules from the data carousel).

Next, it is assumed that the application operation in the data broadcasting application engine 408 transitions to the presentation state of another data broadcasting presentation unit (PU) identified by PU_tag = 3. In the same manner as described above, the application data control unit 406 includes the application file "A11.html" designated as the Primary_module (center of the data broadcasting presentation unit) of the data broadcasting presentation unit (PU_tag = 3) to which the transition is made, and , Each member (PU_member_node) "B11", "B12", "B13" when the node_tag is obtained from DCCT, the module corresponding to these node_tag is obtained from the data carousel, and as shown by reference number 3402, Cache in cache memory 407. However, since the lock cache target is not specified for this data broadcasting presentation unit (PU), the lock cache operation is not performed.

The application data control unit 406 constantly analyzes the signaling information DDMT and DCCT received from the data carousel. Then, as shown by the reference number 3403, when it is detected that the version of DCCT has been updated from 1 to 2, the application data control unit 406 detects the primary_model of the data broadcasting presentation unit (PU_tag = 3) currently in the presentation state. Also, check whether each member file and the file to be locked cached have been changed. Since there is no change in the member files this time, each previously cached member file is kept in the cache memory 407. Further, since "A12", "B14", "B12", and "B15" have been added as lock cache target files for the data broadcast presentation unit (PU_tag = 3), the application data control unit 406 can use the data. Modules corresponding to these node_tags are acquired from the carousel, cached in the cache memory 407 as shown by reference number 3404, and separately managed as a lock cache target file. In the figure, the files managed as lock cache targets are underlined (the same applies hereinafter).

The datacasting application engine 408 then transitions the HTML5 document from the running A11 file to the A12 file upon receiving an event message instructing the update of the datacasting presentation, as indicated by reference number 3405. .. On the other hand, almost at the same time, the application data control unit 406 refers to the DCCT whose version has been updated from 2 to 3, and the Primary_model of the data broadcasting presentation unit (PU_tag = 3) currently in the presentation state is "A12.html". It is detected that the member file has been changed to "B14", "B15", and "B16". As described above, since the Prime_model "A12.html" and the member files "B14" and "B15" are already lock-cached in the cache memory 407, the data broadcasting application engine 408 is stored in the cache memory 407. Data broadcasts can be displayed quickly using the retained files. That is, it is possible to present timely data broadcasting linked to a broadcast program. Further, since the lock cache target is not specified for this data broadcasting presentation unit (PU), the lock cache operation is not performed. As shown by reference number 3406, the lock-cached files "A12", "B14", "B12", and "B15" are retained in the cache memory 407 as they are, while the unnecessary files "A11" are deleted. Has been done.

Further, upon receiving the event message instructing the update of the data broadcasting presentation, the application data control unit 406 refers to the DCCT and refers to the data broadcasting presentation unit (PU_tag = 3) currently in the presentation state. "B17" has been added as a lock cache target file, and "B14" has been added as an unlock target file. Therefore, as shown by reference number 3407, the application data control unit 406 acquires the module corresponding to the node_tag of the file "B17" from the data carousel, lock-caches it in the cache memory 407, and lock-caches it. Delete the file "B12" from the cache memory 407 and remove it from the lock target.

In the data broadcasting service by BML (Broadcast Markup Language) currently in operation, a specific file is pre-cached and stored in the cache memory in advance by calling an API (Application Programming Interface) called "LockModuleOnMemory ()" from a script. It is possible to keep it (see, for example, Patent Document 4). In this method, it is necessary to incorporate special specifications premised on broadcasting operation into the specifications of applications such as scripts.

On the other hand, according to the technology disclosed in the present specification, the transmitting side such as a broadcasting station transmits the information related to the data broadcasting including the information specifying the forced cache, and the receiver side receives the information. The cache control of each file for data broadcasting is performed based on the forced cache information included in the signaling related to data broadcasting. Therefore, according to the technology disclosed in the present specification, in data broadcasting by the new HTML5, a highly versatile format is maintained without incorporating special specifications premised on broadcasting operation in the specifications of applications such as scripts. be able to.

Japanese Unexamined Patent Publication No. 2013-153291 Japanese Unexamined Patent Publication No. 2013-9337 Japanese Unexamined Patent Publication No. 2013-66160 JP-A-2007-274193

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 technique disclosed herein can be applied to various broadcasting systems that transmit file data used for data broadcasting by a data carousel transmission method. Although the present specification has described embodiments applied to a broadcasting system that employs the MPEG-2 TS system as the transport system, the techniques disclosed in the present specification are not limited thereto.

Further, although the embodiment in which HTML5 is used as the description format of the data broadcasting application has been described in the present specification, the technology disclosed in the present specification is not limited to this, and is applied to various data broadcasting services. can do.

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

The technology disclosed in the present specification can also have the following configuration.
(1) A first encoder that encodes data of a data broadcasting application by a data carousel transmission method by designating a file location by either a transmission line-dependent designation method or a URI designation method.
A second encoder that encodes program-specific information (PSI) including a program management table (PMT) in which a data encoding method descriptor that specifies transmission arrangement information of an application information table (AIT) related to the data broadcasting application is arranged. ,
A transmission processing unit that multiplexes and transmits a plurality of broadcast data including broadcast data encoded by the first and second encoders, respectively.
A transmitter equipped with.
(2) In the application information table (AIT), the transmission path-dependent designation method and the URI designation method of the data carousel are specified.
The transmitter according to (1) above.
(3) The transmission arrangement information of the signaling information (DDMT, DCCT) applied when the URI designation method is selected is further specified by the data encoding method descriptor arranged in the program management table (PMT).
The transmitter according to (1) above.
(4) The signaling information (DDMT, DCCT) is included in a specific module of the data carousel encoded by the first encoder.
The transmitter according to (3) above.
(5) The signaling information includes a data directory management table (DDMT) that manages the directory structure of files transmitted by data broadcasting.
The transmitter according to any one of (3) or (4) above.
(6) As the signaling information, a file configuration for each content (application) transmitted by data broadcasting, a file configuration for each data broadcasting presentation unit (PU) in the content (application), and a data content indicating the content configuration and cache control. Include management table (DCCT),
The transmitter according to any one of (3) to (5) above.
(7) The signaling information is expressed in XML (eXtensible Markup Language) notation format and binary notation format.
The transmitter according to any one of (3) to (6) above.
(8) In each table included in the signaling information, a common node tag is specified for each directory and each file, and module information of a control message (DII) indicating information of each module of the data carousel is specified. Place a node tag descriptor in and associate it with the module,
The transmitter according to any one of (3) to (7) above.
(9) The first encoding step of encoding the data of the data broadcasting application by the data carousel transmission method by designating the file location by either the transmission line-dependent designation method or the URI designation method.
A second encoding that encodes program-specific information (PSI) including a program management table (PMT) in which a data encoding method descriptor that specifies transmission arrangement information of the application information table (AIT) related to the data broadcasting application is arranged. Steps and
A transmission processing step of multiplexing and transmitting a plurality of broadcast data including broadcast data encoded in the first and second encoding steps, respectively.
Transmission method with.
(10) Specify the data carousel of the data broadcasting application whose file location is specified by either the transmission line-dependent designation method or the URI designation method, and the transmission arrangement information of the application information table (AIT) related to the data broadcasting application. A reception processing unit that receives and processes a broadcast signal containing program-specific information (PSI) including a program management table (PMT) in which a data coding method descriptor is arranged, and a reception processing unit that receives and processes a broadcast signal.
An application data control unit that controls the processing of data broadcasting applications,
A receiving device comprising.
(11) The application data control unit uses the application information table based on the transmission arrangement information of the application information table (AIT) described in the data coding method descriptor arranged in the program management table (PMT). (AIT) is acquired, and based on the application information table (AIT), it is determined whether the file location designation method of the data carousel is either a transmission line-dependent designation method or a URI designation method.
The receiving device according to (10) above.
(12) When the URI designation method is selected as the file location designation method of the data carousel.
The application data control unit uses a control message (DII) indicating information on each module of the data carousel from the data carousel in which the packet identifier (PID) of the elemental stream is specified in the program management table (PMT). ) And the signaling information (DDMT, DCCT) applied when the URI designation method is selected to resolve the location of the module contained in the data carousel.
The receiving device according to any one of (10) and (11) above.
(13) The application data control unit is based on the transmission arrangement information of the signaling information (DDMT, DCCT) described in the data coding method descriptor arranged in the program management table (PMT). Obtain (DDMT, DCCT),
The receiving device according to (12) above.
(14) The application data control unit sets a node tag that matches the URI that specifies the location of a desired application in the application information table (AIT), and a directory structure of a file to be transmitted by the signaling information (data broadcasting). Search in the data directory management table (DDMT) to be managed), obtain the module identifier of the module associated with the node tag from the control message (DII), and use the combination of the obtained module identifier and download identifier. Based on, specify the corresponding module (DDB message) from the data carousel,
The receiving device according to (12) above.
(15) The application data control unit includes the signaling information (file configuration for each content (application) transmitted by data broadcasting, file configuration for each data broadcasting presentation unit (PU) in the content (application), and content configuration. Data content management table (DCCT) showing cache control is used to control the cache of file data transmitted to the data carousel.
The receiving device according to (12) above.
(16) When the reception processing unit receives a module designated as a lock target in the signaling information (DCCT), the application data control unit forcibly caches the module in the cache memory.
The receiving device according to (15) above.
(17) The application data control unit cancels the forced cache designation of the module designated as the unlock target in the signaling information (DCCT) and deletes it from the cache memory.
The receiving device according to (16) above.
(18) The application data control unit pre-caches a module designated as a link destination presentation unit in the signaling information (DCCT) into a cache memory.
The receiving device according to (15) above.
(19) Specify the data carousel of the data broadcasting application whose file location is specified by either the transmission line-dependent designation method or the URI designation method, and the transmission arrangement information of the application information table (AIT) related to the data broadcasting application. A reception processing step for receiving and processing a broadcast signal including program-specific information (PSI) including a program management table (PMT) in which a data coding method descriptor is arranged, and a reception processing step.
Application data control steps that control the processing of data broadcasting applications,
Receiving method having.

10 ... Digital broadcasting system 11 ... Broadcast transmission system, 12 ... Receiver 301 ... Clock generator, 302 ... Signal transmission unit 303 ... Video encoder, 304 ... Audio encoder 305 ... Caption encoder, 306 ... AIT encoder 307 ... PSI / SI encoder, 308 ... Broadcast information system 309 ... TS multiplexer, 310 ... Modulation / transmission unit 401 ... Tuner / demodulator unit, 402 ... Demultiplexer 403 ... Clock playback unit, 404 ... Video decoder 405 ... Audio decoder 406 … Application data control unit 406… Cache memory 408… Data broadcasting application engine 409… System control unit, 410… Synthesis unit 411… IP interface

Claims (19)

A first encoder that encodes data of a data broadcasting application by a data carousel transmission method by designating a file location by either a transmission line-dependent designation method or a URI designation method.
A second encoder that encodes program-specific information (PSI) including a program management table (PMT) in which a data encoding method descriptor that specifies transmission arrangement information of an application information table (AIT) related to the data broadcasting application is arranged. ,
A transmission processing unit that multiplexes and transmits a plurality of broadcast data including broadcast data encoded by the first and second encoders, respectively.
A transmitter equipped with. In the application information table (AIT), the transmission path-dependent designation method and the URI designation method of the data carousel are specified.
The transmitting device according to claim 1. The transmission arrangement information of the signaling information (DDMT, DCCT) applied when the URI designation method is selected is further specified by the data encoding method descriptor arranged in the program management table (PMT).
The transmitting device according to claim 1. The signaling information (DDMT, DCCT) is included in a particular module of the data carousel encoded by the first encoder.
The transmitting device according to claim 3. The signaling information includes a data directory management table (DDMT) that manages the directory structure of files transmitted by data broadcasting.
The transmitter according to any one of claims 3 or 4. As the signaling information, a file configuration for each content (application) transmitted by data broadcasting, a file configuration for each data broadcasting presentation unit (PU) in the content (application), a data content management table indicating the content configuration and cache control ( DCCT) included,
The transmitter according to any one of claims 3 to 5. The signaling information is expressed in XML (eXtensible Markup Language) notation format and binary notation format.
The transmitter according to any one of claims 3 to 6. In each table included in the signaling information, a common node tag is specified for each directory and each file, and a node is added to the module information of the control message (DII) indicating the information of each module of the data carousel. Place a tag descriptor and associate it with a module,
The transmitter according to any one of claims 3 to 7. The first encoding step of encoding the data of the data broadcasting application by the data carousel transmission method by designating the file location by either the transmission line-dependent designation method or the URI designation method.
A second encoding that encodes program-specific information (PSI) including a program management table (PMT) in which a data encoding method descriptor that specifies transmission arrangement information of the application information table (AIT) related to the data broadcasting application is arranged. Steps and
A transmission processing step of multiplexing and transmitting a plurality of broadcast data including broadcast data encoded in the first and second encoding steps, respectively.
Transmission method with. Data encoding that specifies the data carousel of a data broadcasting application whose file location is specified by either the transmission line-dependent specification method or the URI specification method and the transmission arrangement information of the application information table (AIT) related to the data broadcasting application. A reception processing unit that receives and processes a broadcast signal including program-specific information (PSI) including a program management table (PMT) in which a method descriptor is arranged, and a reception processing unit.
An application data control unit that controls the processing of data broadcasting applications,
A receiving device comprising. The application data control unit uses the application information table (AIT) based on the transmission arrangement information of the application information table (AIT) described in the data coding method descriptor arranged in the program management table (PMT). Is acquired, and based on the application information table (AIT), it is determined whether the file location designation method of the data carousel is either a transmission line-dependent designation method or a URI designation method.
The receiving device according to claim 10. When the URI specification method is selected as the file location specification method of the data carousel,
The application data control unit uses a control message (DII) indicating information on each module of the data carousel from the data carousel in which the packet identifier (PID) of the elemental stream is specified in the program management table (PMT). ) And the module (DDB message) of the signaling information (DDMT, DCCT) applied when the URI designation method is selected, and the location of the module included in the data carousel is resolved.
The receiving device according to claim 10 or 11. The application data control unit has a signaling information (DDMT, DCCT) based on the transmission arrangement information of the signaling information (DDMT, DCCT) described in the data coding method descriptor arranged in the program management table (PMT). DCCT),
The receiving device according to claim 12. The application data control unit sets a node tag that matches the URI that specifies the location of a desired application in the application information table (AIT) to the signaling information (data that manages the directory structure of a file transmitted by data broadcasting). -Search in the directory management table (DDMT), obtain the module identifier of the module associated with the node tag from the control message (DII), and based on the combination of the obtained module identifier and download identifier. Specify the corresponding module (DDB message) from the data carousel,
The receiving device according to claim 12. The application data control unit controls the signaling information (file configuration for each content (application) transmitted by data broadcasting, file configuration for each data broadcasting presentation unit (PU) in the content (application), content configuration and cache control. Using the data content management table (DCCT) shown, control the cache of file data transmitted in the data carousel.
The receiving device according to claim 12. When the reception processing unit receives a module designated as a lock target in the signaling information (DCCT), the application data control unit forcibly caches the module in the cache memory.
The receiving device according to claim 15. The application data control unit cancels the forced cache designation of the module designated as the unlock target in the signaling information (DCCT) and deletes it from the cache memory.
The receiving device according to claim 16. The application data control unit pre-caches a module designated as a link destination presentation unit in the signaling information (DCCT) into a cache memory.
The receiving device according to claim 15. Data encoding that specifies the data carousel of a data broadcasting application whose file location is specified by either the transmission line-dependent specification method or the URI specification method and the transmission arrangement information of the application information table (AIT) related to the data broadcasting application. A reception processing step for receiving and processing a broadcast signal including program-specific information (PSI) including a program management table (PMT) in which a method descriptor is arranged, and a reception processing step.
Application data control steps that control the processing of data broadcasting applications,
Receiving method having.