JP6442897B2 - Transmission device, transmission method, reception device, and reception method - Google Patents

Description

  The technology disclosed in this specification includes a transmission apparatus and a transmission method for transmitting data for data broadcasting by a predetermined transmission method, and a reception apparatus and reception for receiving data for data broadcasting transmitted by a predetermined transmission method. Regarding the method.

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

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

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

  An object of the technology disclosed in the present specification is to provide an excellent transmission apparatus 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. An object of the present invention is to provide an excellent receiving apparatus and receiving method capable of suitably receiving broadcast data.

The present application has been made in consideration of the above problems, and the technology according to claim 1
A first encoder for designating a file location by either a transmission path dependent designation scheme or a URI designation scheme and encoding data of a data broadcasting application by a data carousel transmission scheme;
A second encoder for encoding program specific information (PSI) including a program management table (PMT) in which a data encoding scheme descriptor specifying transmission arrangement information of an application information table (AIT) relating to the data broadcast application is arranged; ,
A transmission processing unit that multiplexes a plurality of broadcast data including the broadcast data encoded by the first and second encoders and performs transmission processing;
It is the transmitter which comprises.

  According to the technique described in claim 2 of the present application, the transmitting apparatus according to claim 1 specifies the data carousel transmission path dependence specification method and the URI specification method in the application information table (AIT). It is configured.

  According to the technique described in claim 3 of the present application, the transmission apparatus according to claim 1 transmits the transmission arrangement information of signaling information (DDMT, DCCT) applied when the URI designation method is selected to the program management. The data encoding scheme descriptor arranged in the table (PMT) is further designated.

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

  According to the technology described in claim 5 of the present application, the transmitting device according to claim 3 or 4 uses the data directory management table for managing a directory structure of a file transmitted by data broadcasting as the signaling information. (DDMT) is included.

  According to the technology described in claim 6 of the present application, the transmission device according to any one of claims 3 to 5 uses, as the signaling information, a file configuration and content (application) for each content (application) transmitted by data broadcasting. ) Includes a data content management table (DCCT) indicating a file configuration, a content configuration, and cache control for each data broadcast presentation unit (PU).

  According to the technique described in claim 7 of the present application, the transmission device according to any one of claims 3 to 6 may express the signaling information in an XML (extensible Markup Language) notation format and a binary notation format. It is configured.

  According to the technique described in claim 8 of the present application, the transmission device according to any of claims 3 to 7 includes a common node / file for each directory and each file in each table included in the signaling information. In addition to designating a tag, a node tag descriptor is arranged in module information of a control message (DII) indicating information of each module of the data carousel, and is associated with the module.

Further, the technique according to claim 9 of the present application is
A first encoding step of encoding a data broadcasting application data by a data carousel transmission method by specifying a file location by either a transmission path dependency specifying method or a URI specifying method;
A second encoding that encodes program specific information (PSI) including a program management table (PMT) in which a data encoding scheme descriptor that specifies transmission arrangement information of an application information table (AIT) related to the data broadcasting application is arranged; Steps,
A transmission processing step of multiplexing and transmitting a plurality of broadcast data including the broadcast data encoded in the first and second encoding steps;
Is a transmission method.

Further, the technique according to claim 10 of the present application is
Data encoding that specifies data carousel of a data broadcast application in which a file location is specified by either a transmission path dependency specification method or a URI specification method, and transmission arrangement information of an application information table (AIT) related to the data broadcast application A reception processing unit for receiving a broadcast signal including program specific information (PSI) including a program management table (PMT) in which a system descriptor is arranged;
An application / data control unit that controls processing of the data broadcasting application;
It is the receiver which comprises.

  According to the technique described in claim 11 of the present application, the application data control unit of the receiving apparatus according to claim 10 is described in a data encoding scheme 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 determined 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 technology described in claim 12 of the present application, the receiving device according to claim 10 or 11, when the URI specifying method is selected as the file location specifying method of the data carousel, The application data control unit receives a control message (DII) indicating information on each module of the data carousel from the data carousel in which the elementary stream packet identifier (PID) is specified in the program management table (PMT). ) And a module (DDB message) of signaling information (DDMT, DCCT) applied when the URI designation method is selected, the location of the module included in the data carousel is resolved. .

  According to the technique described in claim 13 of the present application, the application data control unit of the receiving apparatus described in claim 12 is described in the data encoding scheme descriptor arranged in the program management table (PMT). The signaling information (DDMT, DCCT) is obtained based on the transmission arrangement information of the signaling information (DDMT, DCCT).

  According to the technique described in claim 14 of the present application, the application data control unit of the receiving apparatus according to claim 12 matches a URI that specifies a location of a desired application in the application information table (AIT). The node tag is searched with the signaling information (data directory management table: DDMT for managing the directory structure of a file transmitted by data broadcasting), and the module identifier of the module associated with the node tag is searched for in the control message. The module (DDB message) is designated from the data carousel based on the combination of the module identifier and the download identifier obtained from (DII).

  According to the technology described in claim 15 of the present application, the application / data control unit of the receiving device according to claim 12 is configured such that the signaling information (file configuration for each content (application) transmitted by data broadcasting, content ( The file data cache for data carousel transmission is controlled using a data content management table (DCCT) indicating the file structure, content structure and cache control for each data broadcast presentation unit (PU) in the application). It is configured.

  According to the technique of claim 16 of the present application, the application data control unit of the reception device of claim 13 is configured such that the reception processing unit selects a module designated as a lock target in the signaling information (DCCT). When received, it is configured to force cache in cache memory.

  According to the technique described in claim 17 of the present application, the application data control unit of the receiving apparatus according to claim 16 performs forced cache specification of a module specified as an unlock target in the signaling information (DCCT). It is configured to release and delete from the cache memory.

  According to the technique described in claim 18 of the present application, the application data control unit of the receiving apparatus according to claim 15 performs forced cache specification of a module specified as an unlock target in the signaling information (DCCT). It is configured to release and delete from the cache memory.

Moreover, the technology described in claim 19 of the present application is:
Data encoding that specifies data carousel of a data broadcast application in which a file location is specified by either a transmission path dependency specification method or a URI specification method, and transmission arrangement information of an application information table (AIT) related to the data broadcast application A reception processing step for receiving a broadcast signal including program specific information (PSI) including a program management table (PMT) in which a system descriptor is arranged;
An application data control step for controlling the processing of the data broadcasting application;
Is a receiving method.

  According to the technology disclosed in this specification, an excellent transmission apparatus 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 apparatus and receiving method that can suitably receive broadcast data.

  In addition, the effect described in this specification is an illustration to the last, and the effect of this invention is not limited to this. In addition to the above effects, the present invention may have additional effects.

  Other objects, features, and advantages of the technology disclosed in the present specification will become apparent from a more detailed description based on the embodiments to be described later and the accompanying drawings.

FIG. 1 is a diagram schematically illustrating a configuration example of a digital broadcasting system 10 to which the technology disclosed in this specification is applied. FIG. 2 is a diagram schematically showing the configuration of the broadcast signal 200 assumed in the digital broadcast system 10 according to the present embodiment. FIG. 3 is a diagram schematically showing the configuration of the 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 shows a data structure 500 of the PMT. FIG. 6 is a diagram showing a data structure 600 of the data encoding scheme descriptor. FIG. 7 is a diagram illustrating a data structure 700 of Additional_html5_info (). FIG. 8 shows a data structure 800 of the data carousel. FIG. 9 is a diagram illustrating a data structure 900 of a DII message transmitted in the DSM-CC section (data carousel). FIG. FIG. 10 shows a data structure 1000 of the DDB message. FIG. 11 shows a data structure 1100 of the application information table (AIT). FIG. 12 is a diagram illustrating the meanings indicated by each value of application_type. FIG. 13 is a diagram illustrating the semantics of application_control_code. FIG. 14 is a diagram showing a data structure 1400 of the application descriptor. FIG. 15 is a diagram illustrating the semantics of each parameter of the application descriptor. FIG. 16 shows a data structure 1600 of the 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 path dependence designation method. FIG. 18 is a diagram showing a file designation method in the case of data carousel transmission of the transmission line dependence designation method. FIG. 19 is a diagram showing a directory structure in the case of data carousel transmission of the transmission path dependence designation method. FIG. 20 is a diagram illustrating a signaling relationship of application acquisition in the case of data carousel transmission of a transmission path dependence designation method. FIG. 21 is a diagram showing a selector byte data structure 2100 in the transmission protocol descriptor in the case of HTTP / HTTPS transmission and URI-designated data carousel transmission. 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 a data structure 2300 of node tag descriptors arranged in each module_info of the DII message. FIG. 24 is a diagram showing a DDMT data structure 2400 in a binary notation format. FIG. 25 is a diagram showing a DDMT data structure 2500 in the XML notation format. FIG. 26 is a diagram illustrating a description example of DDMT in the XML notation format. FIG. 27 shows a DCCT data structure 2700 in binary notation format. FIG. 28 shows a DCCT data structure 2800 in the XML notation format. FIG. 29 is a diagram showing a description example 2900 of DCCT in the XML notation format. FIG. 30 is a diagram for explaining a mechanism for performing transmission, location, and presentation of a data broadcast application (content) transmitted by 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 when digital broadcasting is selected 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 file data cache locking and unlocking operations in the receiver 12.

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

  FIG. 1 schematically shows a configuration example of a digital broadcast system 10 to which the technology disclosed in this specification is applied. The illustrated digital broadcast system 10 includes a broadcast 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 elementary stream (ES) constituting a main part of a broadcast program such as video and audio, a data broadcast application related to or cooperating with the main part of the broadcast program, and the like. In the following description, a data broadcasting service based on HTML5 is assumed.

  On the other hand, the receiver 12 receives a broadcast signal transmitted from the broadcast transmission system 11. Then, the receiver 12 acquires an elementary stream such as 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 starts an application engine such as an HTML browser and presents the data broadcast 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, but the detailed specifications conform to, 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 broadcast system 10 according to the present embodiment. The illustrated broadcast signal 200 includes a plurality of transport stream components 210-250.

  Each component indicated by reference numerals 210 and 220 is an elementary stream for transmitting video and audio constituting the main part of the broadcast program.

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

  Each data carousel 231, 232,... Includes a DDB (DownloadDataBlock) message as a module whose data body is divided into blocks, and a DII (DownloadInfoIndication) message belonging to a DSM-CC control message. The DII message describes 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, for example, a content (file) such as a data broadcasting application described in HTML5 format or a monomedia used in a data broadcasting application such as JPEG or PNG is transmitted. In FIG. 2, the module of data associated with these applications is indicated by “AppD”.

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

  The AIT is a table describing application control information such as a processing method of an application sent by the 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 for the data broadcasting application (described later). Of these, DDMT is a table that manages the directory structure of files that make up an application that is sent in a data carousel of the URI designation method. The DCCT is a table for managing content (file data) constituting an application transmitted by a data carousel of a URI specification method in a data broadcast presentation unit (Presentation Unit: PU), for cache control of file data. Can be used. Details of the AIT, DDMT, and DCCT tables will be described later.

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

  Each data carousel 231, 232,... Includes 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 denoted by reference numeral 240 is a dedicated transport stream for packet-transmitting the AIT of the application sent by the component 230 by the data carousel transmission method. However, when the component 230 transmits an 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 system is identified by the module identifier, and the AIT transmitted by the component 240 in the packet is identified by the packet identifier (PID: Packet Identifier).

  The component indicated by reference numeral 250 transmits PSI (Program Specific Information) and SI (Service Information). PSI is program specifying information describing which program each elementary stream included in the MPEG-2 TS stream belongs to. SI is program sequence information, and can be used for EPG (Electric Program Guide). PSI is a PMT (Program Map Table) that describes the packet identifier (PID) of a TS packet that transmits video and audio included in one program, and other encoded signals that make up another broadcast program, and the PMT of each broadcast program MPEG-2 TS stream program configuration information such as PAT (Program Association Table) that lists the packet identifiers (PIDs) of PAT (PAT PID is defined as 0). Details of the PMT will be described later.

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

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

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

  The video encoder 303 encodes the video signal sent from the signal sending unit 302, further packetizes it, and sends a video elementary stream including video TS packets to the TS multiplexer 309. Also, the audio encoder 304 encodes the audio signal sent from the signal sending unit 302, further packetizes it, and sends an audio elementary stream including audio TS packets to the TS multiplexer 309.

  The broadcast information system 308 is a TV broadcast station scheduler and file supply source. Data broadcasting application and mono media data described in HTML5 format, application control information, signaling information related to data such as data broadcasting application, programs 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.

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

  The AIT encoder 306 encodes application control information sent from the broadcast information system 308, further packetizes it, and sends an elementary stream including AIT TS packets 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 not necessary. That is, the equipment of the AIT encoder 306 is arbitrary and drawn with a dotted line.

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

  The TS multiplexer 309 multiplexes TS packets sent from the encoders 303 to 307 to form the 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 result to the RF transmission path To do.

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

  In the clock generation unit 301, a clock signal STC for synchronizing the encoders 303 to 307 is generated, and a TS packet including a PCR serving as a reference for performing time synchronization for decoding on the receiver 12 side is generated. .

  The video signal sent from the signal sending 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 including video TS packets. This video elementary stream is sent to the TS multiplexer 309.

  The audio signal sent from the signal sending unit 302 is supplied to the audio encoder 304. The audio encoder 304 encodes and further packetizes the audio signal to generate an elementary stream including audio TS packets. This audio elementary stream is sent to the TS multiplexer 309.

  The data carousel encoder 305 configures a data carousel composed of a DDB message and a DII message based on information transmitted from the broadcast information system 308 and transmits the data carousel to the TS multiplexer 309.

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

  In addition, the PSI / SI encoder 307 generates an elementary stream including PSI and IS TS packets based on the program configuration information and program arrangement information transmitted from the broadcast information system 308, and sends them to the TS multiplexer 309. It is done.

  In the TS multiplexer 309, the TS stream sent from each of the encoders 303 to 307 is multiplexed to generate a broadcast stream. Modulation / transmission section 310 performs digital modulation such as OFDM on the broadcast stream, further performs RF modulation processing such as up-conversion, and sends the result to the RF transmission path.

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

  The tuner / demodulator 401 receives an IF (Intermediate Frequency) or RF modulation signal, performs a demodulation process such as down-conversion, and further performs a digital demodulation process such as OFDM demodulation to obtain a broadcast stream. The demultiplexer 402 performs demultiplex processing and depacketization processing on the broadcast stream to obtain a PCR packet, a video elementary stream, an audio elementary stream, a data carousel, an AIT (however, If the AIT is not transmitted as a data carousel DDB message), PSI / SI is output. The file data used for data broadcasting is a data broadcasting application described in, for example, 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. 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 using a part of 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 and data used in data broadcasting is transmitted from two systems of a broadcast signal and an IP network. The former is transmitted via a tuner / demodulator 401 and a demultiplexer 402, and the latter is Acquired by the application / data control unit 406 via the IP interface 411.

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

  In the present embodiment, information specifying a forced cache for each file used in data broadcasting is included in the signaling information (DCCT). 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 the file data pre-cache will be described later.

  The synthesizer 410 synthesizes the display signal of the data broadcast output from the data broadcast application engine 408 with the baseband video signal to obtain a video signal for video display. The baseband audio signal obtained by the audio decoder 405 is an audio signal for audio output. The main part of the broadcast program composed of video signals and audio signals is output as video and audio from a monitor display (not shown). Further, the data broadcast processed by the data broadcast application engine 408 is also displayed on the monitor / display with being superimposed on the main screen of the broadcast program.

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

  The tuner / demodulator 401 receives the IF or RF modulation signal, performs demodulation processing such as down-conversion, and further performs digital demodulation processing such as OFDM demodulation to obtain a broadcast stream. The demultiplexer 402 performs demultiplex processing and depacketization processing on the broadcast stream to obtain a PCR packet, a video elementary stream, an audio elementary stream, a data carousel, an AIT (however, If the AIT is not transmitted as a data carousel DDB message), the PSI / SI is extracted.

  The PCR packet extracted by the demultiplexer 402 is sent to the clock recovery unit 403. In the clock reproduction unit 403, the original clock information STC is reproduced 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 encoded video signal extracted by the demultiplexer 402 is sent to the video decoder 404 and decoded to obtain a baseband video signal. The data carousel extracted by the demultiplexer 402 is sent to the application data control unit 406. The application / data control unit 406 controls application activation by the data broadcast application engine 408 based on the DII message and the DDMT, DCMT, and AIT included in the DDB message. The data broadcast application engine 408 processes file data of the data broadcast application transmitted as a DDB message, and generates a display signal for the data broadcast. The synthesizing unit 410 synthesizes the display signal of the data broadcast with the baseband video signal to obtain a video signal for video display.

  Also, the encoded audio signal extracted by the demultiplexer 402 is sent to the audio decoder 405 and decoded to obtain a baseband 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 application data control unit 406 caches a file data cache memory for data broadcasting services 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.

  Conventional Japanese data broadcasting services use BML as the application description format, and based on the data carousel transmission method, a transmission unit called a module is incorporated in the directory structure of the application. It is assumed that it becomes a cache unit. There is a problem that restrictions on producing an application are large due to such a transmission method.

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

  Therefore, in the technique disclosed in this specification, when data of an HTML5 data broadcasting application is transmitted by a data carousel transmission method, a transmission path dependence specification method and a URI that have been conventionally applied as a file location specification method are used. The (Uniform Resource Indicator) designation method can be selectively used.

  The data encoding descriptor (data component descriptor) arranged in the PMT indicates data transmission of the data broadcasting application in HTML5, and signaling information applied when the transmission arrangement of AIT and the URI designation method are selected ( (DDMT and DCCT) transmission arrangement information is designated.

  In the AIT, the file carousel file location designation method is designated as a transmission line dependent designation method or a URI designation method.

  In addition, in order to realize the URI designation method, the above-described signaling information called DDMT and DCCT is transmitted. The signaling information is defined as (1) to (4) below.

(1) DDMT is a table for managing 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 configuration for each content (application) transmitted by data broadcasting, a file configuration for each data broadcast presentation unit (PU) in the content (application), a content configuration such as a pre-cache target file, and a cache. It is a table which shows 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 the signaling information are expressed in XML (extensible Markup Language) notation format and binary notation format.

(4) In the directory structure indicated by DDMT, a common node tag is designated for each directory and each file. Also in DCCT, it is specified by a node tag. Further, the node tag descriptor is arranged in each module information (moduleInfoByte) of the DII message, and the directory and the module are associated with each other. As a result, the DII message can be associated with the DDMT and DCCT tables.

  On the receiver 12 side, the data broadcasting application operation including the selection of the two file / location specifying methods is performed.

  In the following, an embodiment for realizing the above-described two file location designation methods when transmitting data of an HTML5 data broadcasting application in the data carousel transmission method will be described in detail.

  FIG. 5 shows a data structure 500 of the PMT. The PMT data structure basically conforms to the ISO / IEC 13818-1 standard.

  In table_id, a value “0x02” for identifying that the table is a PMT is described. Further, “1” is described in section_syntax_indicator. In section_length, the section length of the PMT is described. In the program_number, service_id for identifying the service (broadcast channel) is described. In version_number, version information of the PMT is described. “1” is described in the current_next_indicator. In section_number, “0x00” is described. In “last_section_number”, “0x00” is described. The PCR PID describes the packet identifier (PID) of the PCR of the service specified by program_number.

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

  The first loop 501 is a program loop. In the program_info_length field immediately before the loop 501, the loop length of the first loop 501 is described. A descriptor area descriptor () composed of the first loop 501 repeated for the number of program_info_lengths includes program information descriptors such as a conditional access system descriptor, a digital copy control descriptor, and an emergency information descriptor. Is described.

  The second loop 502 is an ES loop that stores information of each elementary stream, and stream_type, elementary_PID, and ES_info_length are described as attribute information in each loop. In stream_type, the format identification of the elementary stream targeted by the loop is described. In elementary_PID, an identifier (PID) of a TS packet that transmits a related elementary stream or payload is described. ES_info_length describes the length of the descriptor area that follows. Then, an ES descriptor is stored in a descriptor area descriptor () composed of a loop repeated for the number of ES_info_length lengths. As the ES descriptor, for example, a stream identification descriptor, a conditional access system descriptor, a digital copy control descriptor, a data encoding system descriptor, and the like are described.

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

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

  The data encoding scheme descriptor includes descriptor_tag, descriptor_length, and data_component_id as attribute information. In the descriptor_length, the loop length of the subsequent loop 601 is described. data_component_id is used to identify the encoding method of the data of the corresponding elementary stream. The 16-bit field value assignment is in accordance with the standards of the standardization organization. When the corresponding elementary stream is an application (for example, in HTML5 description format), a value for identifying application transmission is described in data_component_id. Descriptor_tag describes an 8-bit tag value that identifies the encoding method of the data of the corresponding elementary stream.

  Additional identification information (additional_data_component_info) is described in the area formed by the loop 601. The additional_data_component_info is used to expand the identifier number or store acquisition information defined for each encoding method. The data structure of information described in this area is separately defined for each data encoding method. In the present embodiment, additional identification information that indicates data transmission of a data broadcasting application in HTML5 and that specifies transmission arrangement information of signaling information (DDMT and DCCT) applied when an AIT transmission arrangement and a URI designation method are selected. (Additional_html5_info ()) is inserted into this area 601.

  FIG. 7 shows a data structure 700 of Additional_html5_info () inserted as additional identification information in the data encoding scheme descriptor.

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

  The ait_flag is set to 1 when the corresponding entry stream (of the data carousel) includes the module (DDB message) of the application information table AIT. As described above, the AIT is transmitted in either a data carousel or an independent packet (see FIG. 2).

  The application_data_flag is set to 1 when the corresponding entry stream (of the data carousel) includes an application data module (DDB message).

  When the signaling_flag is 1, the 16-bit signaling_module_id describes a module ID in the data carousel of the signaling file DDMT transmitted as the DDB message. When DDMT is transmitted, DCMT is also transmitted. In this embodiment, module IDs of DDMT and DCCT are serial numbers (that is, DCCT is a module ID of +1), and 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_module_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 the DDB message is described. In application_type, a value in an application format transmitted by AIT is described. When the application format is HTML5, application_type is 0x0010. In application_priority, the activation priority of the application type to be controlled by the AIT is described. AIT_version_number describes the version number described in the AIT.

  When application_data_flag is 1, each flag of multiple_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 transmitted. Is included.

  Specify the AIT transmission arrangement and the transmission arrangement information of signaling information (DDMT and DCCT) with Additional_html5_info () inserted in the data encoding scheme descriptor that is one of the ES descriptors in the second loop of the PMT. Please note that it is done.

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

  In table_id (table identifier), a number for identifying the shoulder of data in the payload of the DSM-CC section is stored. Depending on the value of this field, a specific coding description is applied to subsequent fields in the DSM-CC section. The value of table_id when the DSM-CC section type is a DII message is 0x3B, the value of table_id when it is a DDB message is ox3C, and table_id when it is private data is 0x3E.

  A 1-bit field section_index_indicator (section syntax instruction) indicates that the CRC 32 exists at the end of the section when 1 and that a checksum exists when 0.

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

  dsmcc_section_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 never exceeds 4095.

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

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

  tversion_number (version number) is set according to table_id as shown in (1) and (2) below.

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

  1-bit current_next_indicator (current next instruction) indicates that the sub-table is the current sub-table. In the case of 0, it indicates that the sub-table to be sent is not applied yet and is used as the next sub-table. When table_id is 0x3A to 0x3C, 1 is always specified.

  Section_number (section number) represents a section number. When the section transmits a DII message, section_number is always set to 0. When transmitting a DDB message, the lower 8 bits of the block number of the DDB are stored in section_number.

  Last_section_number (last section number) indicates the number of the last section (that is, the section having the largest section number) of the sub-table to which the section belongs.

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

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

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

  In downloadId (download identifier), a label for identifying a data carousel is described.

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

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

  tCDDownloadWindow is not used in data carousel transmission, and its value is set to zero. In tCDDownloadSCenario, a time-out time from the start of download to the end thereof is described in units of microseconds.

  The compatibilityDescriptor () stores a compatibilityDescriptor () structure defined in ISO / IEC13818-6.

  In numberOfModules (number of modules), the number of modules described in the subsequent loop in the DII message is described. Then, in the module information loop 901 repeated by numberOfModules (number of modules), information for each module to be transmitted in the data carousel is stored. As attribute information of each module, moduleId (module identifier), moduleVersion (module version), moduleInfoLength (module information length) are stored, and these are followed by a descriptor area consisting of a loop repeated by the number of moduleInfoLengths. ModuleInfoByte (module information) is stored. The moduleInfoByte (module information) can be a descriptor related to the corresponding module. In moduleId, the module identifier of the module described in the moduleInfoByte area is stored. In this embodiment, in the case of the URI designation method, a node tag descriptor that is pointer information for designating a corresponding module is described as moduleInfoByte (module information). The modules mentioned here are application data modules and DDMT and DCCT signaling modules. In the directory structure indicated by DDMT, a common node tag is specified for each directory and each file, and in DCCT, the node tag is specified (described later). Therefore, the directory is associated with the module through the node tag descriptor of the DII message. As a result, the DII message can be associated with the DDMT and DCCT tables. Details of the data structure of the node tag descriptor will be described later.

  PrivateDataLength (private data length) describes the byte length of the private data area, and privateData Byte (private data) is stored in a descriptor area composed of loops repeated by the number of 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 a data structure 1000 of a DDB message transmitted in the DSM-CC section (data carousel). A DDB message is a data structure that carries data blocks. A data block is obtained by dividing a module into fixed-length blocks. Block numbers are assigned to the DDB messages, and the receiver 12 side reconfigures the modules by arranging the data blocks in the order of the block numbers. Further, when transmitting a DDB message by MPEG-2 TS, only a DDB message having the same download ID must be included in the same PID packet. That is, it is not allowed to mix DDB messages of two different data carousels in one elementary stream.

  In dsmccdownloadDataHeader (), header information for identifying a DDB message in data carousel transmission is described. Details of the header information are not described, but include a download ID that uniquely identifies the data carousel.

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

  In blockNumber (block number), the position of the corresponding data block in the module is described. The block number of the first data block of the module must be zero. In the subsequent block data area blockDataByte composed of a loop repeated N times, the data block body is stored.

  As data blocks stored in blockDataByte, in addition to data broadcasting application data, blocks of signaling data such as DDMT and DCCT are included (provided that the URI designation method is selected as the file location designation method). A desired data block can be filtered from the data carousel using a node tag descriptor (described later) stored as module information of the DII message. However, the block of signaling data of DDMT and DCCT can be filtered using the transmission arrangement information (signaling_module_id) of Additional_html5_info () inserted in the data coding scheme descriptor in the second loop of the PMT. . That is, the receiver 12 side can filter the block of DDMT and DCCT signaling data at the stage of receiving the 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 a data structure 1100 of the application information table (AIT). The AIT is a signal that controls activation and termination of an application and access to a broadcast resource. The AIT is transmitted via broadcasting or a communication path. In this embodiment, as shown in FIG. 2, it is assumed that the AIT is transmitted as a data carousel as one of data blocks (DDB messages) or as an independent packet. The AIT shown in FIG. 11 is used when application control information is encoded in a section format defined in MPEG-2 Systems (ITU-T Rec. H222.0, ISO / IEC 13818-1). Note that an XML description method is also defined in the application information table (AIT), 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 application information (AI) table, and is 0x74 in this embodiment. The section_syntax_indicator (section syntax instruction) is a 1-bit field and is always “1”. sectoin_length (section length) defines the number of bytes of the section from the section length field to the end of the section including CRC32. In order to prevent the length of all sections from exceeding 4096, the section length shall not exceed 4093 (0xFFD in hexadecimal). application_type (application format) indicates the format of the application transmitted by AIT. FIG. 12 shows the meanings indicated by each value of application_type. version_number is the version number of the subtable and is incremented by +1 when there is a change in the information in the subtable. When the value of the version number becomes “31”, it returns to “0” next. The current_next_indicator (current next instruction) is always “1”. The section_number (section number) is an 8-bit field and represents a 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 having the same table identifier and application format is added. The last_section_number (last section number) is an 8-bit field that defines the last section number in the subtable to which the section belongs.

  common_descriptor_length (common descriptor loop length) is an 8-bit field, and defines the byte length of the subsequent descriptor (descriptor). This descriptor (descriptor) stores information of the common descriptor (descriptor) in a series of descriptor areas including common descriptor loops corresponding to the number of common_descriptor_lengths. The contents of the common descriptor apply to all applications in the AIT subtable.

  application_loop_length is an area in which the number of application information included in the MH AI table is written. Then, application information descriptor loops 1101 are arranged by the number indicated by application_loop_length. In addition, at the end of AIT, ITU-T recommendation H.264. A 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), and application_descriptor_loop_length (application information descriptor loop length) are stored as application attribute information. The application_identifier is a value that uniquely identifies the application. application_control_code is a control code for controlling the state of the application. application_descriptor_loop_length indicates the byte length of the subsequent application information descriptor area. Then, following the application attribute information, an application information descriptor descriptor () is stored in a descriptor area composed of the number of loops indicated by application_descriptor_loop_length. Descriptors in this descriptor area apply only to the corresponding application.

  The semantics of application_control_code are specified for each application format, but when 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 referring to this AIT table starts to start the application specified by application_identifier. If “PREFETCH” is designated as application_control_code, the receiver 12 that refers to the MH AIT table pre-reads the application specified by application_identifier. If “KILL” is instructed as application_control_code, the receiver 12 that refers to the AIT table ends execution of the application specified by application_identifier.

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

  FIG. 14 shows an application descriptor data structure 1400 stored in the descriptor area descriptor () in the application information descriptor loop 1101 of the AIT. 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 the AIT.

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

  Information of application_profile is written in a series of areas composed of loops corresponding to the number of application_profile_lengths. application_profile is a profile of a receiver that can execute this application. The requested function is indicated by a bitmap for each function requested to the receiver. However, the upper 3 bits indicate function bitmap switching. The bitmap is specified for each version. Also, version_major, version_minor, and version_micro are each a version defined by the application profile.

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

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

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

  The descriptor_tag is an 8-bit integer value 0x02 that identifies the descriptor. The descriptor_length is an 8-bit area in which the number of bytes of data of the descriptor 0 following the field is written.

  protocol_id (protocol identifier) indicates a protocol for transmitting an application. In the present embodiment, as the value of protocol_id, 0x0003 specifies HTTP / HTTPS transmission, 0x0004 specifies data carousel transmission of a transmission path dependent designation scheme, and 0x0006 defines data carousel transmission of URI designation. The transport_protocol_label (transmission protocol label) is a value that uniquely identifies the transmission means when transmitting one application through multiple paths, 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 defined for each protocol identifier, and the syntax is defined for each protocol identifier. In the present embodiment, the acquisition location of application data is written in 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 designated data carousel transmission). Therefore, the syntax of selector_byte is different. Details of the selector byte syntax in each case will be given later.

  As described above, in this embodiment, when data of an HTML5 data broadcasting application is transmitted by the data carousel transmission method, the transmission path dependence specification method and the URI (which have been conventionally applied) are used as the file location specification method. A Uniform Resource Indicator) designation method can be selectively used.

  First, the transmission path dependence designation method will be described. The transmission path-dependent file location designation method is a method for designating file data of a data broadcast application in a hierarchy of broadcast transmission paths such as a network identifier, a transport stream identifier, a service identifier, a component tag, and a 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 of the transmission path dependence designation method (as in the past), and the selector byte area. To specify the hierarchy of the above-mentioned broadcast transmission path.

  Further, in the transmission path dependency designation method, file data is transferred within the application based on the transmission path hierarchy (network identifier, transport stream identifier, service identifier, component tag, module identifier) as described above. Specify in the following namespace.

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

  In the conventional transmission path dependence designation method, signaling information such as DDMT and DCCT is not applied. Therefore, since DDMT and DCCT are not transmitted (in a data carousel), the transmission efficiency and processing efficiency of the data broadcasting application are good. However, because of the data carousel transmission system, it is thought that there are significant restrictions in producing applications (described above).

  Next, the URI designation method will be described. In this method, file data of a data broadcasting application can be designated with 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 based on the URI designation method, and the URI is designated in the selector byte area. In the application, file data is designated by URI.

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

  FIG. 17 shows a data structure 1700 of a selector byte in a transmission protocol descriptor in the case of data carousel transmission of a transmission path dependence designation method (as in the past).

  The remote_connection (remote connection) is 1 when the data carousel for transmitting the AIT and the application is not transmitted by the same service (including when the AIT acquires communication), and is 0 when the data carousel is transmitted by the same service. .

  When remote_connection is 1, that is, when the data carousel transmitting the AIT and the application is not transmitted by the same service, the parameters of original_network_id, transport_stream_id, and service_id are described. original_network_id is an original network identifier in which the application is transmitted. transport_stream_id is a transport stream identifier in which the application is transmitted. service_id is a service identifier to which the application is transmitted. When the remote_connection is 0, that is, when the data carousel transmitting 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 an application is transmitted is described. The component stream to which the data carousel is transmitted is specified by the component tag given by the stream identification descriptor, which is one of the ES descriptors arranged in the second loop of the PMT.

  FIG. 18 illustrates a file designation method in the case of data carousel transmission of a transmission path dependence designation scheme (as in the past).

  On the receiver 12 side, a data encoding scheme descriptor (data_component_descriptor) described in the second loop corresponding to the elementary stream of the data carousel of the PMT (see FIG. 5) (see FIG. 6). AIT is acquired based on the module identifier of AIT included in Additional_html5_info (see FIG. 7) inserted in (see FIG. 7) (when AIT is transmitted in the data carousel transmission system). . Alternatively, when the AIT is transmitted as an independent packet, the AIT is acquired based on the AIT packet identifier (AIT PID) described in the second loop corresponding to the AIT elementary stream. .

  In the descriptor area in the application information descriptor loop (see FIG. 11) of the AIT, an application descriptor (application_descriptor), a transmission protocol descriptor (transport_protocol_descriptor), a simple application location descriptor (simple_application_location_descriptor) and the like are stored. (As mentioned above).

  Filter the transmission protocol descriptor that matches the transport protocol label (= 1) of the application descriptor of the desired application, as indicated by reference number 1801, and further, the transmission protocol description, as indicated by reference number 1802. Specifies the component stream in which the data carousel is transmitted based on the selector byte (component tag) stored in the child. Also, DII messages can be filtered out of the data carousel.

  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 whose root is the location that can be acquired by the application indicated by the selector byte of the transmission protocol descriptor. In the illustrated example, the application string is a module identifier of the application (the illustrated example). 0010) and a resource name (index.html in the illustrated example).

  Each module in the data carousel is identified using a module identifier and a resource name. A section in which 0x3B is stored as a table identifier (table_id) can be acquired as a DII message from the data carousel. Also, resource names can be used to filter DDB messages.

  FIG. 19 illustrates a directory structure in the case of data carousel transmission of a transmission path dependence designation method (as in the past).

The loop of each module of the DII message, module m _{1, 2,} as a pointer information for each ... m _k, module identifier (module_id) and module name (module_name) is stored. If the module is multipart, the DDB message consists of a multipart resource (file name) list (Resource List: RL) and each multipart resource (file data). The

  In the directory structure in the data carousel transmission of the transmission path dependence designation method, the component designated by the selector byte (component tag) of the transmission protocol descriptor corresponds to the root directory. Further, each module whose module identifiers are listed in the loop of the module of the DII message corresponds to a subdirectory, and a multi-part file data is arranged immediately below each subdirectory.

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

  hrf = arib-dc: //7EE9.7FE/4.0448/40/0000/A. html

  A. html to B.I. When referring to html, the link tag is as follows.

  href =. . / 0001 / B. html

  FIG. 20 illustrates the application-related signaling relationship in the case of data carousel transmission using the transmission path dependence designation method.

  As indicated by reference 2001, the data carousel packet is specified based on the PID described in the second loop corresponding to the elementary stream of the data carousel of the PMT (see FIG. 5). can do.

  Also, as indicated by reference numeral 2002, Additional_html5_info (see FIG. 7) inserted in the data encoding descriptor (data_component_descriptor) (see FIG. 6) described in the second loop. ) Can be acquired based on the module identifier (ait_module_id) included in the AIT (provided that the AIT is transmitted by the data carousel transmission method). Alternatively, as indicated by reference numeral 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 elementary stream of the AIT AIT can be acquired based on the above.

  In the application information descriptor loop of the 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 4, the transmission path It can be recognized that the data carousel transmission is based on the dependency specification method. Based on the selector byte (component_tag) described in the transmission protocol descriptor, the DII message in the data carousel is acquired as indicated by reference numeral 2004.

  In this way, as indicated by reference numeral 2005, the module identifier and the resource name (in the example shown, “0010 / index.html”) included in the simple application location descriptor within the same application information descriptor. And a DDB message for transmitting the corresponding application (file data) can be specified based on a combination of downloadID described in the DII message.

  FIG. 21 shows a data structure 2100 of selector bytes in the transmission protocol descriptor in the case of HTTP / HTTPS transmission and URI-designated data carousel transmission.

  URL_base_length indicates the number of bytes of the base part of the URL for acquiring the application. URL_base_byte stores a character string of the base portion of the URL for acquiring an application in a series of areas consisting of loops equal to the number of URL_base_lengths.

  URL_extension_count indicates the number of URL extensions for acquiring an application. The URL_extension loop is arranged by the number of URL_extension_count. In one URL_extension loop, a URL_extension_byte indicating the number of bytes of the URL extension part for acquiring the application and a URL_extension area consisting of loops corresponding to the URL_extension_length are arranged, and the URL_extension is used to acquire the application The character string of the extension part of the URL is stored.

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

  Note that the selector byte shown in FIG. 21 is looped as a whole, so that it is possible to set a plurality of URL base parts from which applications can be acquired.

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

  On the receiver 12 side, a data encoding scheme descriptor (data_component_descriptor) described in the second loop corresponding to the elementary stream of the data carousel of the PMT (see FIG. 5) (see FIG. 6). AIT is acquired based on the module identifier of AIT included in Additional_html5_info (see FIG. 7) inserted in (see FIG. 7) (when AIT is transmitted in the data carousel transmission system). . Alternatively, when the AIT is transmitted as an independent packet, the AIT is acquired based on the AIT packet identifier (AIT PID) described in the second loop corresponding to the AIT elementary stream. .

  In the descriptor area in the application information descriptor loop (see FIG. 11) of the AIT, an application descriptor (application_descriptor), a transmission protocol descriptor (transport_protocol_descriptor), a simple application location descriptor (simple_application_location_descriptor) and the like are stored. (As 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. Further, when the URL for acquiring the application is obtained by completing the URL described in the folding method in the selector byte of the transmission protocol descriptor, as indicated by reference numeral 2202, the data carousel is selected from the data carousel. The DDB message carrying the signaling information DDMT can be filtered.

  In this embodiment, a common node tag is specified for each directory and each file in the directory structure indicated by DDMT. In other words, the node tag is also used 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. As a result, the DII message can be associated with the DDMT and DCCT tables.

  Details of the data structure of the node tag descriptor will be described later. As indicated by reference numeral 2203, the DII message is filtered from the data carousel based on the node tag value described in the DDMT. Further, as indicated by reference numeral 2204, the DDB message that transmits the desired application data is filtered based on the module identifier described in the DII message.

  FIG. 23 shows a node / tag descriptor data structure 2300 arranged in the module information (moduleInfoByte) of the DII message in the case of the URI designation method.

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

  The 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. If the node is a resource, 1 is entered.

  When the node level value is 0, that is, when the node is a module, a node tag node_tag of a 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 number of resources resource_number in the module and the node tag node_tag of each resource are described in a loop corresponding to the number of resources. .

  As described above, when the URI specification method is selected as the file location specification method in data carousel transmission, signaling information such as a data directory management table (DDMT) and a data content management table (DCCT) is transmitted as a DDB message. (See FIG. 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 a DDMT data structure 2400 in a binary notation format.

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

  base_directory_path_length represents the size of the information area of base_directory_path_byte in bytes. The base_directory_path_byte stores a path name to the base_directory (upper directory) in a series of information areas including loops corresponding to the number of base_directory_path_lengths. The base_directory_path_byte is expressed in, for example, an absolute URL format for accessing a corresponding directory.

  num_of_directory_nodes indicates the number of nodes in the directory described in the DDMT. Then, directory node loops 2401 are arranged by the number of num_of_directory_nodes.

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

  directory_node_path_length represents the size of the information area of directory_node_path_byte in bytes. directory_node_path_byte is composed of a series of information areas consisting of loops equal to the number of directory_node_path_lengths, and stores a path name to directory_node. The directory_node_path_byte is expressed in a relative URL format from the base_directory_path for accessing the corresponding directory, for example. For example, if the path name (URL) of base_directory is “http://www.xbc.com” and the bus name (URL) of a folder_directory is “index.html”, these character strings are concatenated, The complete URL “http://xbc.com/index.html” can be obtained.

  num_of_files indicates the number of files described in the DDMT. Then, file node loops 2402 are arranged by the number of num_of_files.

  In a 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. The 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 a node tag. Further, as described above, the node tag descriptor is arranged in the module information (moduleInfoByte) of the DII message to associate the directory with the module. The file_name_byte (file name) is stored in a series of file name areas composed of loops corresponding to the number of file_name_lengths.

  FIG. 25 shows a DDMT data structure 2500 in the XML notation format. The DDMT has a URL (@baseURI) of a directory serving as a root 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 a file node (file) included in the directory as an element.

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

  FIG. 26 shows a description example 2600 of the DDMT in the XML notation format.

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

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

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

  In a content loop, content_ID, content_version, content_cache_size, and information on a data broadcast presentation unit (Presentation Unit: PU) included in the content are written as information about the content. content_ID is an identifier of the content. The content_version indicates the content version. content_cache_size indicates the size for caching the content. Also, number_of_PU is the number of data broadcast presentation unit PUs included in the content, and PU loops 2702 are arranged by the number of number_of_PUs.

  In a loop of one PU, PU_tag that is identification information of the PU, PU_cache_size that indicates a size for caching the PU, and PU_primary_module_node_tag that identifies a file (primary module) that is the center of the data broadcast presentation unit (PU). Written.

  Also, a list of broadcast transmission files constituting the data broadcast presentation unit (PU) is written in the PU loop. Specifically, number_of_PU_member_nodes indicates the number of nodes included in the data broadcast presentation unit (PU) (that is, a member of the PU). Thereafter, a loop of PU member nodes corresponding to the number_number_of_PU_member_nodes is arranged, and the node_tag of the PU member node is written in the loop of each PU member node. PU member nodes include directory nodes and item nodes.

  In addition, in the PU loop, when a lock target file exists in the corresponding PU, information on the target file list is described. Specifically, number_of_lock_cache_nodes is the number of nodes to be locked, and as many lock cache node loops as number_of_lock_cache_nodes are arranged. A lock_cache_node_tag for identifying the lock cache node is written in the loop of one lock cache node.

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

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

  Further, in the loop of one PU, there are arranged number_of_linked_PU indicating the number of other PUs linked from this PU and linked_PU loops corresponding to the number of number_of_linked_PUs. In one linked_PU loop, linked_PU_tag, which is identification information of linked_PU, is written.

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

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

  Each presentation unit has, as attributes, an identification tag (@tag) of the presentation unit, a cache size at the time of presentation unit cache (@cacheSize), and a node tag (@primary) of the primary node in the presentation unit. It has a node (Member) constituting a presentation unit, a forced cache designation node (loclCacheNode), a forced cache release designation node (unlockCacheNode), and a link destination presentation unit (linkedPU) as elements.

  A node (Member) constituting a presentation unit has a node tag (@nodeTag) as an attribute. The forced cache specification 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 DCCT description example 2900 in the XML notation format.

  FIG. 30 illustrates a mechanism for transmitting a data broadcast application (content) transmitted in a data carousel, content location, and application presentation.

  FIG. 30A shows a directory structure of content. Each content 1, 2,... Is composed of a data broadcast application (app) and a material. Data broadcasting applications and materials are resources each having file data as an entity. 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 designated by a module identifier (moduleId). The application is composed of one or more HTML5 documents that are referred to when content is executed (when data broadcasting is presented). The material is an image file such as jpeg or png referred to from an HTML5 document, or monomedia data such as text. One data broadcast presentation unit PU is constituted by one HTML5 document and the material referred to therefrom. In the example shown in FIG. 30A, content1 is A11. html, A12. html, A13. It has one or more HTML documents such as html as resources of the data broadcasting application. Of these, A11. html is a resource that is directly referred to when content is executed.

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

  Similarly, the application A12 and the materials B12, B02, and B13 to which the application A12 refers are a resource group 3002 that constitutes one data broadcast presentation unit PU, and p2 is assigned as PU_tag (B07 is data by broadcasting). (This is material that can be acquired at any time by HTTP transmission by communication rather than carousel transmission, and is treated as not included in the resource group of the data broadcasting presentation unit). Similarly, the application A01 and the materials B03, B01, and B04 to which the application A01 refers are a resource group 3003 constituting one data broadcast 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. 30B, the resource A01. html is an HTML document that describes an application presentation screen that is referred to directly when content is executed and is displayed first. On the other hand, the resource A12. html and the resource A01. contained in the content common outside content1. html is A01. An HTML document describing an application presentation screen that transitions from a screen presented by executing html, A11. It has a link reference relationship with html. Each resource A01. html, A12. html, A01. The html forms resource groups 3001, 3002, and 3003 that constitute one data broadcast presentation unit PU. Then, the data broadcast presentation units 3001, 3002, and 3003 that are linked together constitute a larger resource group 3010. Resource A01. html, A12. html, A01. html is file data (primary module) which is the center of each data broadcast presentation unit PU.

  In addition, a large resource group, that is, the entire data content is configured by the entire content that is the entire application included in the package (one broadcast program). The entire data content is a range of data broadcast presentation units PU having a common content_ID. In DCCT, all data broadcast presentation unit PUs included in the content can be collectively specified by rotating the loop of the PU of the corresponding content_ID. In the example shown in FIG. 30B, the resource group 3020 of the entire content is formed by the applications included in content1 and common, and c1 is assigned as the content identifier.

  FIG. 30C schematically shows a state in which file data constituting the content is transmitted in a data carousel. File data such as applications and materials, which are content components, are transmitted in units of modules divided into blocks. Each module corresponds to a DDB message in the data carousel transmission line. In the data carousel transmission, a module identifier (moduleId) is assigned to each module. 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 modules obtained by dividing file data such as HTML document data and materials, respectively. .

  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, a node tag descriptor is arranged in each module information (moduleInfoByte), and each module is associated with the node tag. Therefore, by specifying the node tag, the directory and You can associate modules.

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

  As shown by reference 3101, the data carousel packet is designated based on the PID described in the second loop corresponding to the elementary stream of the data carousel of the PMT (see FIG. 5). can do.

  Further, as indicated 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. ) Can be acquired based on the module identifier (ait_module_id) included in the AIT (provided that the AIT is transmitted by the data carousel transmission method). Alternatively, as indicated by reference numeral 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 acquired based on the above.

  In the application information descriptor loop of the 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, specify the URL. It can be recognized that this is a data carousel transmission.

  Further, as indicated by reference numerals 3104 and 3105, Additional_html5_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 on the basis of the module identifier (signaling_module_id) of each of the signaling information of DDMT and DCCT included in (when AIT is transmitted by the data carousel transmission method) ).

  Then, as indicated by reference numeral 3106, it matches the URL character string described in the selector byte of the AIT transmission protocol descriptor in the DDMT directory node loop and file node loop (described above). Search for a file and get its node tag. Note that the same processing is performed when a fiber to another HTML5 document referred to by the application is designated as indicated by reference numeral 3111.

  If a node having a matching URL character string is not found in 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 a data broadcast application can be acquired without distinguishing between broadcast and communication.

  Next, as indicated by reference numeral 3107, a module tag corresponding to the node tag is searched for a node tag descriptor that matches the node tag in the module information loop (described above) of the DII message. To get.

  In this way, as indicated by reference numeral 3108, based on the combination of the obtained module identifier and the download identifier (downloadID) described in the DII message, the corresponding application (from the data carousel ( A DDB message for transmitting file data can be designated.

  If you want to cache the nodes (directories and files) linked to the application specified in “AUTOSTART (automatic start)”, as shown by the reference number 3109, it corresponds in the loop of the DCCT PU (described above). Search for a node tag to be searched, and further, as indicated by reference numeral 3110, search for a PU loop and perform pre-caching based on the linked PU tag, or forcibly cache or unlock the lock target file You can cancel the forced cache specification of a file.

  FIG. 32 shows, in the form of a flowchart, the procedure of the application data income and the start-up process that are executed when the receiver 12 performs the digital broadcast channel selection process.

  The tuner / demodulator 401 selects and receives a broadcast signal, and the demultiplexer 402 demultiplexes the broadcast stream to separate the original elementary streams, and each elementary stream. Depacketization processing is performed.

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

  Also, playback of 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 a baseband video signal.

  When the data carousel transmission is performed as an AIT module (DDB message) (Yes in step S3203), the application data control unit 406 adds the data encoding scheme descriptor arranged in the second loop of the PMT. The AIT is acquired based on the module identifier (ait_module_id) of the AIT 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 uses the AIT packet identifier (AIT PID) described in the second loop of the PMT. Based on this, the AIT is acquired from the independent component (step S3205).

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

  Here, when the protocol identifier is 4, that is, the transmission path dependence designation method, the application data control unit 406 designates with a selector byte (see FIG. 17) described in the AIT transmission protocol descriptor. The DII message is acquired from the component tag that has been set (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. Next, the application data control unit 406 acquires an entry module of the application based on the description content of the DII message (see FIGS. 18 and 20), and controls the cache processing of the module as necessary. (Step S3208).

  On the other hand, if the protocol identifier is 6, that is, the URI designation method, the application data control unit 406 obtains the DII message and each signaling information DDMT and DCCT from the data carousel in which the 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, included in Additional_html5_info (see FIG. 7) inserted in the data encoding scheme descriptor arranged in the second loop of the PMT (see FIG. 5). The DDMT and DCCT are acquired based on the module identifier (signaling_module_id) of each signaling information of DDMT and DCCT.

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

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

  In the present embodiment, the DCCT as signaling information includes, as information indicating cache control, the node tag of the lock target file, the node tag of the unlock target file, and the link destination of the current data broadcast presentation unit (PU). The node tag of the presentation unit is described. Therefore, the application / data control unit 406 forcibly caches a lock target file (for example, file data necessary for the next data broadcasting presentation unit to be changed) or unlocks a file (for example, a current data broadcast presentation unit). In this case, it is possible to cancel the designation of the forced cache of the file data that is unnecessary in (1) 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 application entry module acquired in accordance with each file location designation method of the transmission path dependence designation method or the URI designation method, and the file data cached in the cache 407, The activation of the application by the data broadcast application engine 408 is controlled (step S3211).

  As described above, in the present embodiment, the signaling information DCCT applied in the URI designation method includes the node tag of the lock target file, the node tag of the unlock target file, and the current information as information indicating cache control. The node tag of the link destination presentation unit of the data broadcast presentation unit (PU) is described. Therefore, the application / data control unit 406 forcibly caches a lock target file (for example, file data necessary for the next data broadcasting presentation unit to be changed) or unlocks a file (for example, a current data broadcast presentation unit). In this case, it is possible to cancel the designation of the forced cache of the file and data that are no longer necessary in the cache 407 and delete it from the cache 407. Also, file data of link destination presentation units can be cached in advance.

  A rough procedure for controlling the cache operation by locking and unlocking the module to be transmitted by the data carousel in the receiver 12 based on the signaling information DCCT will be described 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 designated as the primary module (to be the center of the data broadcasting presentation unit) by an instruction from the data broadcasting application control engine 408 or the like. Recognize that the presentation state of the data broadcast presentation unit (PU) has been entered.
(Operation 3) In the DCCT, the application data control unit 406 simultaneously acquires each member file (PU_member_node) included in the corresponding data broadcast presentation unit (PU) and stores it in the cache memory 407.
(Operation 4) Further, when the target of the lock cache is specified for the corresponding data broadcast presentation unit (PU) in the DCCT, the application / data control unit 406 does not acquire the lock cache target. These files (modules) are also acquired, cached in the cache memory 407, and separately managed as a lock cache target file.
(Operation 5) Conversely, in the DCCT, when the target for the data broadcasting presentation unit (PU) is designated as an unlock cache target, the application / data control unit 406 determines that the unlock target file is If it is cached in the cache memory 407, it is deleted and also deleted from the lock cache target file that has been separately managed.
(Operation 6) The data broadcast 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 or the file to be locked or unlocked is changed due to the update of the DCCT Then, the processing of (Operation 3) to (Operation 6) is performed.
(Operation 8) When the application operation in the data broadcast application engine 408 makes a transition to the presentation state of another data broadcast presentation unit (PU), the lock cache target file is temporarily held in the cache memory 407, The processing of (Operation 3) to (Operation 6) is performed. Files other than the lock cache target may be deleted from the cache memory 407.

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

  When the data broadcast application control engine 408 is presenting an application operation, that is, a data broadcast (Yes in step S3301), the application data control unit 406 includes a primary_module (data broadcast presentation unit in the data content management table). By accessing the application file designated at the center of (No in step S3302), it is recognized that the presentation state of the corresponding data broadcast presentation unit (PU) has been entered.

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

  Further, the application data control unit 406 checks whether or not the target of the lock cache is specified for the corresponding data broadcast presentation unit (PU) in the data content management table (step S3304). If the lock cache target is specified (Yes in step S3304), the application data control unit 406 also acquires each unacquired file (module) from the lock cache target, and stores the cache memory. The file 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 target of the unlock cache is designated for the corresponding data broadcast presentation unit (PU) in the DCCT (step S3306). If the unlock cache target 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 lock cache target file that has been separately managed (step S3307).

  Thereafter, when the update of the DCCT changes the configuration of the member node (PU_member_node) included in the data broadcast presentation unit (PU) currently in the presentation state or the file to be precached (Yes in step S3308), step Returning to S3303, the above processing is repeatedly executed in the data broadcast presentation unit (PU) currently in the presentation state.

  When the application operation in the data broadcast application engine 408 transits to the presentation state of another data broadcast presentation unit (PU) and the application file specified in the primary_module of the data broadcast presentation unit is accessed (step) In step S3309, the process returns to step S3303, and the above processing is repeatedly executed in the data broadcasting presentation unit (PU) to which the transition has been made.

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

  FIG. 34 shows an example of file data cache locking and unlocking operations 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 broadcast application control engine 408 is performing an application operation of the data broadcast presentation unit (PU) identified by PU_tag = 1, the application / data control unit 406 refers to the DCCT and the data currently in the presentation state. The application file “A01.html” designated as the Primary_module (center of the data broadcast presentation unit) of the broadcast presentation unit (PU_tag = 1), and the node_tag of each member (PU_member_node) “B01” and “B02” are data. When the modules corresponding to these node_tags are obtained from the content management table and obtained from the data carousel, as shown by reference numeral 3401, the cache memory 40 Cache to. However, since the lock cache target is not designated for this data broadcast presentation unit (PU), the cache operation is not performed. Note that the method for accessing the module that is 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 corresponding module from the data carousel).

  Next, it is assumed that the application operation in the data broadcast application engine 408 makes a transition to the presentation state of another data broadcast presentation unit (PU) identified by PU_tag = 3. In the same manner as described above, the application data control unit 406 selects the application file “A11.html” specified in the Primary_module (center of the data broadcast presentation unit) of the data broadcast presentation unit (PU_tag = 3) of the previous transition. When the node_tag of each member (PU_member_node) “B11”, “B12”, “B13” is obtained from the DCCT, modules corresponding to these node_tags are obtained from the data carousel, and as indicated by reference numeral 3402, Cache in cache memory 407. However, since the lock cache target is not designated for this data broadcast presentation unit (PU), the lock cache operation is not performed.

  The application data control unit 406 always analyzes the signaling information DDMT and DCCT received from the data carousel. Then, as indicated by reference numeral 3403, when detecting that the version of the DCCT has been updated from 1 to 2, the application / data control unit 406 causes the primary_module of the data broadcast presentation unit (PU_tag = 3) currently in the presentation state. In addition, each member file and the file to be locked cache are checked for changes. Since there is no change in the member file this time, each member file previously cached is retained in the cache memory 407. In addition, since “A12”, “B14”, “B12”, and “B15” are added as lock cache target files of the data broadcast presentation unit (PU_tag = 3), the application / data control unit 406 performs data / data control unit 406. Modules corresponding to these node_tags are acquired from the carousel, cached in the cache memory 407 as indicated by reference numeral 3404, and separately managed as a lock cache target file. In the figure, files managed as lock cache targets are indicated by underlines (hereinafter the same).

  Next, as shown by reference numeral 3405, upon receiving an event message instructing to update the presentation of the data broadcast, the data broadcast application engine 408 transitions the HTML5 document from the A11 file being executed to the A12 file. . On the other hand, almost simultaneously, the application / data control unit 406 refers to the DCCT whose version has been updated from 2 to 3, and the Primary_module of the data broadcast presentation unit (PU_tag = 3) in the present 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 primary_module “A12.html” and the member files “B14” and “B15” are already cached in the cache memory 407, the data broadcasting application engine 408 is stored in the cache memory 407. Data broadcasts can be quickly displayed using the stored files. That is, it is possible to present a timely data broadcast linked to a broadcast program. Further, since the lock cache target is not designated for this data broadcast presentation unit (PU), the lock cache operation is not performed. As indicated by reference numeral 3406, the lock cached files “A12”, “B14”, “B12”, and “B15” are held in the cache memory 407 as they are, while the unnecessary file “A11” is deleted. Has been.

  Further, when receiving an event message instructing to update the presentation of the data broadcast, the application data control unit 406 refers to the DCCT, with respect to the data broadcast presentation unit (PU_tag = 3) currently in the presentation state. “B17” is added as a lock cache target file, and “B14” is added as an unlock target file. Therefore, as indicated by reference numeral 3407, the application data control unit 406 acquires a module corresponding to the node_tag of the file “B17” from the data carousel, locks it in the cache memory 407, and locks the cache. The file “B12” is deleted from the cache memory 407 and removed from the lock target.

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

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

JP 2013-153291 A JP 2013-9337 A JP2013-66160A JP 2007-274193 A

  As described above, the technology disclosed in this specification has been described in detail with reference to specific embodiments. However, it is obvious that those skilled in the art can make modifications and substitutions of the embodiments without departing from the scope of the technology disclosed in this specification.

  The technology disclosed in this specification can be applied to various broadcasting systems that transmit file data used for data broadcasting by a data carousel transmission method. In the present specification, the embodiment applied to a broadcasting system adopting the MPEG-2 TS system as a transport system has been described, but the technology disclosed in the present specification is not limited to this.

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

  In short, the technology disclosed in the present specification has been described in the form of exemplification, and the description content 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 claims should be taken into consideration.

Note that the technology disclosed in the present specification can also be configured as follows.
(1) a first encoder that designates a file location by either a transmission path dependence designation scheme or a URI designation scheme and encodes data of a data broadcasting application by a data carousel transmission scheme;
A second encoder for encoding program specific information (PSI) including a program management table (PMT) in which a data encoding scheme descriptor specifying transmission arrangement information of an application information table (AIT) relating to the data broadcast application is arranged; ,
A transmission processing unit that multiplexes a plurality of broadcast data including the broadcast data encoded by the first and second encoders and performs transmission processing;
A transmission apparatus comprising:
(2) In the application information table (AIT), a data carousel transmission path dependence designation scheme and a URI designation scheme are designated.
The transmission device according to (1) above.
(3) Further specifying the transmission arrangement information of signaling information (DDMT, DCCT) applied when the URI designation scheme is selected, by the data encoding scheme descriptor arranged in the program management table (PMT).
The transmission device according to (1) above.
(4) The signaling information (DDMT, DCCT) is included in a specific module of a data carousel encoded by the first encoder.
The transmission device according to (3) above.
(5) As the signaling information, a data directory management table (DDMT) for managing a directory structure of a file transmitted by data broadcasting is included.
The transmission device according to any one of (3) and (4) above.
(6) As the signaling information, a file configuration for each content (application) transmitted by data broadcasting, a file configuration for each data broadcast presentation unit (PU) in the content (application), a data content indicating a content configuration and cache control Including the management table (DCCT),
The transmission device according to any one of (3) to (5) above.
(7) The signaling information is expressed in an XML (extensible Markup Language) notation format and a binary notation format.
The transmission device 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 Place a node tag descriptor in and associate it with a module,
The transmission device according to any one of (3) to (7) above.
(9) a first encoding step for encoding a data broadcasting application data by a data carousel transmission method by specifying a file location by either a transmission path dependency specifying method or a URI specifying method;
A second encoding that encodes program specific information (PSI) including a program management table (PMT) in which a data encoding scheme descriptor that specifies transmission arrangement information of an application information table (AIT) related to the data broadcasting application is arranged; Steps,
A transmission processing step of multiplexing and transmitting a plurality of broadcast data including the broadcast data encoded in the first and second encoding steps;
A transmission method.
(10) A data carousel of a data broadcast application in which a file location is specified by either a transmission path dependency specifying method or a URI specifying method, and transmission arrangement information of an application information table (AIT) related to the data broadcast application are specified. A reception processing unit for receiving and processing a broadcast signal including program specific information (PSI) including a program management table (PMT) in which a data encoding scheme descriptor is arranged;
An application / data control unit that controls processing of the data broadcasting application;
A receiving apparatus comprising:
(11) The application data control unit is configured to use the application information table based on transmission arrangement information of the application information table (AIT) described in a data encoding scheme 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 path dependent designation method or a URI designation method.
The receiving device according to (10) above.
(12) When the URI specification method is selected as the file location specification method of the data carousel,
The application data control unit receives a control message (DII) indicating information of each module of the data carousel from the data carousel in which the elementary stream packet identifier (PID) is specified in the program management table (PMT). And the location of the module included in the data carousel based on the signaling information (DDMT, DCCT) applied when the URI designation method is selected,
The receiving device according to any one of (10) and (11) above.
(13) The application data control unit is configured to transmit signaling information based on transmission arrangement information of signaling information (DDMT, DCCT) described in the data encoding scheme descriptor arranged in the program management table (PMT). (DDMT, DCCT)
The receiving device according to (12) above.
(14) The application data control unit sets a node tag that matches a URI that specifies a location of a desired application in the application information table (AIT), and the signaling information (the directory structure of a file transmitted by data broadcasting). Data directory management table (DDMT) to be managed is retrieved, and the module identifier of the module associated with the node tag is obtained from the control message (DII), and the obtained module identifier and download identifier are combined. Based on the data carousel, specify the corresponding module (DDB message),
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 broadcast presentation unit (PU) in the content (application), content configuration) A data content management table (DCCT) indicating cache control is used to control a cache of file data transmitted in a 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 a 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) in a cache memory.
The receiving device according to (15) above.
(19) Designate a data carousel of a data broadcast application in which a file location is designated by either a transmission path dependency designation method or a URI designation method, and transmission arrangement information of an application information table (AIT) related to the data broadcast application. A reception processing step of receiving a broadcast signal including program specific information (PSI) including a program management table (PMT) in which a data encoding scheme descriptor is arranged;
An application data control step for controlling the processing of the data broadcasting application;
Receiving method.

DESCRIPTION OF SYMBOLS 10 ... Digital broadcasting system 11 ... Broadcast transmission system, 12 ... Receiver 301 ... Clock generation part, 302 ... Signal transmission part 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 / demodulation unit, 402 ... Demultiplexer 403 ... Clock reproduction 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 ... Composition unit 411 ... IP interface

Claims (15)

In any of the specified type of transmission line depends specified scheme or URI specification method to specify the location to send the application, and transmits the signaling information for transmission of the application location in the URI specification method is specified, relating to the application transmitting device comprising a transmitter for transmitting the table arranged descriptors specifying a transmission arrangement information of the the transmission arrangement information of the application information table indicating the designation mode signaling information. In the application information table, to specify the transmission path depends specified scheme or URI specifying method data carousel,
The transmission device according to claim 1. The signaling information includes a data directory management table (DDMT) that manages the directory structure of the files that make up the application.
The transmission device according to claim 1. The signaling information includes a content file configuration, a presentation unit (PU) file configuration in the content, and a data content management table (DCCT) indicating cache control.
The transmission device according to claim 1. The signaling information is expressed in an XML (extensible Markup Language) notation format and a binary notation format.
The transmission device according to claim 1. In each table included in the signaling information, specify a node tag for a directory or file;
The transmission device according to any one of claims 1 to 5. Designating a location by either a transmission path dependence designation scheme or a URI designation scheme and transmitting an application;
Transmitting signaling information related to transmission of an application whose location is specified by the URI specification method;
Sending a table disposed descriptors specifying the transmission arrangement information of the the transmission arrangement information of the application information table indicating the specified scheme for the application signaling information,
A transmission method. It shows the application location is specified in any of the specified type of transmission line depends specified scheme or URI specified scheme, signaling information relating to transmission of the application location is specified in the URI specification method, the designation scheme for the application a reception processing unit for transmitting allocation information of the application information table and receives processed was placed the specified descriptor table and a transmission arrangement information of the signaling information,
An application data control unit that controls processing of the application based on the received table ;
A receiving apparatus comprising: The application data control unit acquires the application information table based on the transmission arrangement information of the application information table specified in the descriptor arranged in the table, and a location designation method based on the application information table Is a transmission path dependent designation method or a URI designation method,
The receiving device according to claim 8. The application data control unit obtains signaling information (DDMT, DCCT) based on transmission arrangement information of signaling information (DDMT, DCCT) specified in a descriptor arranged in the table;
The receiving device according to claim 8. The application / data control unit controls application caching using the signaling information (content file configuration, file configuration of presentation unit (PU) in content, data content management table: DCCT indicating cache control). ,
The receiving device according to claim 8. The application data control unit caches a file designated as a lock target in the signaling information (DCCT) in a cache memory;
The receiving device according to claim 11. The application data control unit releases the cache of the file designated as the unlock target in the signaling information (DCCT) and deletes it from the cache memory;
The receiving device according to claim 12. The application data control unit pre-caches in a cache memory a file designated as a link destination presentation unit in the signaling information (DCCT).
The receiving device according to claim 11. It shows the application location is specified in any of the specified type of transmission line depends specified scheme or URI specified scheme, signaling information relating to transmission of the application location is specified in the URI specification method, the designation scheme for the application a reception processing step of transmitting location information of the application information table and receives processed was placed the specified descriptor table and a transmission arrangement information of the signaling information,
An application data control step for controlling processing of the application based on the received table ;
Receiving method.