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

Description

A technique disclosed in the present specification includes a transmitting apparatus and a transmitting method for transmitting data for data broadcasting by a predetermined transmission method, and a receiving apparatus and a receiving apparatus for receiving data for data broadcasting transmitted by a predetermined transmission method. Regarding the method.

2. Description of the Related Art In current broadcasting systems, 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). That).

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 conforms to the data carousel transmission method defined by ISO/IEC 13818-6. The data is repeatedly distributed, and the receiver can acquire necessary data at any time during the broadcast time (for example, see Patent Document 2). In this data carousel transmission system, data is transmitted in module units divided into blocks. It is assumed that a transmission unit called a module is incorporated in the directory structure of an application, and multiple files are multiparted into a module to form a cache unit. Due to such a transmission method, it is considered that there are great restrictions in producing an application.

On the other hand, recently, for the purpose of cooperation between broadcasting and communication, it has been considered to apply more versatile HTML5 (Hyper Text Markup Language 5) 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 device and transmission method capable of suitably transmitting data for data broadcasting by the data carousel transmission system, and data transmitted by the data carousel transmission system. An object of the present invention is to provide an excellent receiving device and receiving method capable of suitably receiving broadcast data.

The present application has been made in consideration of the above problems, and the technology according to claim 1
A first encoder that encodes data of a data broadcasting application by a data carousel transmission method by specifying a file location by either a transmission path dependent specification method or a URI specification method;
A second encoder that encodes program specific information (PSI) including a program management table (PMT) in which a data encoding descriptor that specifies transmission arrangement information of an application information table (AIT) related to the data broadcasting application is arranged; ,
A transmission processing unit that multiplexes and processes a plurality of broadcast data including broadcast data encoded by the first and second encoders;
It is a transmitting device comprising.

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

According to the technique of claim 3 of the present application, the transmitting device of claim 1 stores the transmission arrangement information of the signaling information (DDMT, DCCT) applied when the URI designation method is selected, in the program management. The data encoding method descriptor arranged in the table (PMT) is further specified.

According to the technique of claim 4 of the present application, the transmitting device of claim 3 includes the signaling information (DDMT, DCCT) in a specific module of a data carousel to be encoded by the first encoder. Is configured.

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

According to the technique 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 for each content (application) transmitted by data broadcasting, and a content (application). The data content management table (DCCT) indicating the file structure, the content structure and the cache control for each data broadcast presentation unit (PU) in () is included.

According to the technique of claim 7 of the present application, the transmission device according to any one of claims 3 to 6 describes 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 one of claims 3 to 7 is configured such that, in each table included in the signaling information, a node common to each directory and each file The tag tag descriptor is arranged in the module information of the control message (DII) indicating the information of each module of the data carousel and associated with the module.

Further, the technology according to claim 9 of the present application is
A first encoding step of encoding a data of a data broadcasting application by a data carousel transmission method by designating a file location by either a transmission path dependent designation method or a URI designation method;
A second encoding for encoding program specific information (PSI) including a program management table (PMT) in which a data encoding 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 respectively;
Is a transmission method having

Further, the technology according to claim 10 of the present application is
A data carousel of a data broadcasting application whose file location is specified by either a transmission path-dependent specification method or a URI specification method, and data encoding for specifying transmission arrangement information of an application information table (AIT) relating to the data broadcasting application. 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 system descriptor is arranged;
An application data control unit that controls the processing of the data broadcasting application,
It is a receiving device comprising.

According to the technique of claim 11 of the present application, the application data control unit of the receiving device of claim 10 is described in the 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 based on the application information table (AIT). It is configured to determine whether it is the dependency designation method or the URI designation method.

According to the technique of claim 12 of the present application, the receiving device according to claim 10 or 11 is configured such that when a URI designation method is selected as a file location designation method of the data carousel, From the data carousel whose packet identifier (PID) of the elementary stream is specified in the program management table (PMT), the application data control unit sends a control message (DII) indicating information on each module of the data carousel. ) 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 configured to be resolved. ..

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

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

According to the technique of claim 15 of the present application, the application data control unit of the receiving device of claim 12 includes the signaling information (file configuration for each content (application) to be transmitted by data broadcasting, content ( Control the file/data cache for data carousel transmission using a data content management table (DCCT) that indicates the file configuration, content configuration, and cache control for each data broadcast presentation unit (PU) in the application) Is configured.

According to the technology of claim 16 of the present application, in the application data control unit of the receiving device of claim 13, the reception processing unit determines the module designated as the lock target in the signaling information (DCCT). Upon receipt, it is configured to force a cache in cache memory.

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

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

The technology according to claim 19 of the present application is
A data carousel of a data broadcasting application whose file location is specified by either a transmission path-dependent specification method or a URI specification method, and data encoding for specifying transmission arrangement information of an application information table (AIT) relating to the data broadcasting application. A reception processing step of 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 device and transmission method capable of suitably transmitting data for data broadcasting by the data carousel transmission method, and data transmitted by the data carousel transmission method It is possible to provide an excellent receiving device and receiving method capable of suitably receiving broadcast data.

The effects described in the present specification are merely examples, and the effects of the present invention are not limited to these. 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 the more detailed description based on the embodiments described below and the accompanying drawings.

FIG. 1 is a diagram schematically showing a configuration example of a digital broadcasting system 10 to which the technique disclosed in this specification is applied. FIG. 2 is a diagram schematically showing the configuration of a broadcast signal 200 assumed in the digital broadcasting system 10 according to this 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 is a diagram showing a data structure 500 of the PMT. FIG. 6 is a diagram showing a data structure 600 of the data encoding method descriptor. FIG. 7 is a diagram showing a data structure 700 of Additional_html5_info(). FIG. 8 is a diagram showing the data structure 800 of the data carousel. FIG. 9 is a diagram showing a data structure 900 of a DII message transmitted in the DSM-CC section (data carousel). It is the figure which showed. FIG. 10 is a diagram showing a data structure 1000 of the DDB message. FIG. 11 is a diagram showing a data structure 1100 of the application information table (AIT). FIG. 12 is a diagram showing the meaning indicated by each value of the application_type. FIG. 13 is a diagram showing the semantics of the application_control_code. FIG. 14 is a diagram showing a data structure 1400 of the application descriptor. FIG. 15 is a diagram showing the semantics of each parameter of the application descriptor. FIG. 16 is a diagram showing a data structure 1600 of the transmission protocol descriptor. FIG. 17 is a diagram showing the data structure 1700 of the selector byte in the transmission protocol descriptor in the case of the data carousel transmission of the 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 path 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 showing a signaling relationship for application acquisition in the case of data carousel transmission of the transmission path dependence designation method. FIG. 21 is a diagram showing a data structure 2100 of the selector byte in the transmission protocol descriptor in the case of HTTP/HTTPS transmission and data carousel transmission of the URI designation method. FIG. 22 is a diagram showing a file designating method in the case of data carousel transmission of the URI designating method. FIG. 23 is a diagram showing a data structure 2300 of the node tag descriptor arranged in each module_info of the DII message. FIG. 24 is a diagram showing a data structure 2400 of the DDMT in the binary notation format. FIG. 25 is a diagram showing a data structure 2500 of the DDMT in the XML notation format. FIG. 26 is a diagram showing a description example of the DDMT in the XML notation format. FIG. 27 is a diagram showing a DCCT data structure 2700 in the binary notation format. FIG. 28 is a diagram showing a DCCT data structure 2800 in the XML notation format. FIG. 29 is a diagram showing a description example 2900 of the DCCT in the XML notation format. FIG. 30 is a diagram for explaining a mechanism for transmitting, location, and presenting a data broadcasting application (content) transmitted by data carousel. FIG. 31 is a diagram showing a signaling relationship for application acquisition in the case of data carousel transmission of the URI designation method. FIG. 32 is a flowchart showing a processing procedure executed by the receiver 12 when selecting a digital broadcast. 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 a lock/unlock operation of the file/data cache in the receiver 12.

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

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

The broadcast transmission system 11 transmits an MPEG-2 TS system broadcast signal. The broadcast signal includes an elementary stream (ES) that constitutes the main part of the broadcast program such as video and audio, a data broadcasting application related to or linked 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 the broadcast signal sent from the broadcast sending 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, it activates an application engine such as an HTML browser and presents a data broadcast linked to a 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 detailed specifications follow, for example, the standard ARIB STD-B24 5.9 version.

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

Each of the components denoted by reference numerals 210 and 220 is an elementary stream that transmits video and audio that form the main part of the broadcast program.

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

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 the DSM-CC control message. The DII message describes the information of each module (DDB message) included in the data carousel. Each module in the data carousel can be identified by a module identifier (module_id).

As the DDB message, a content (file) such as a mono-media used in a data broadcasting application described in HTML5 format or a data broadcasting application such as JPEG or PNG is transmitted. In FIG. 2, the modules of data associated with these applications are indicated by “AppD”.

Further, as the DDB message, an application information table (AIT: Application Information Table), a data directory management table (DDMT: Data Management Table), and a data content management table (DCCT: Data Content Configuration) indicated by dotted lines are shown. , Can be optionally transmitted.

The AIT is a table that describes application control information such as a method of processing an application sent by the data carousel transmission method, a transmission method, and designation of a location. DDMT and DCCT are signaling information applied when the URI designation method is selected as the file location designation method of the data broadcasting application (described later). Of these, the DDMT is a table that manages the directory structure of files that make up an application that is sent by a data carousel of the URI designation method. The DCCT is a table that manages the content (file data) that constitutes an application sent by a data carousel of the URI designation method in a data broadcast presentation unit (Presentation Unit: PU), and controls the cache of the file data. Can be used. Details of the AIT, DDMT, and DCCT tables will be given 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 given later.

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

The component indicated 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 the AIT as a DDB message, the component 240 is unnecessary. That is, the component 240 is optional and is depicted by a dotted line. The AIT transmitted by the data carousel transmission method is identified by the module identifier, and the AIT transmitted by the packet by the component 240 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 identification information that describes which program each elementary stream included in the MPEG-2 TS stream belongs to. SI is program arrangement information and can be used for EPG (Electric Program Guide). The PSI is a PMT (Program Map Table) that describes a packet identifier (PID) of a TS packet that transmits each encoded signal that forms a moving image or audio included in one program or other broadcast programs, or a PMT of each broadcast program. PAT (Program Association Table) listing the packet identifiers (PIDs) of the PATs, and the like, including the program configuration information of the MPEG-2 TS stream (PAT PID is defined as 0). Details of the PMT will be given 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 a time stamp PCR (Program) that serves as a reference 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, for example, a recording/reproducing device such as a studio of a TV broadcasting station or a VTR, and outputs elementary streams constituting a main part of a broadcast program such as video and audio to a video encoder 303 and an audio encoder 304, respectively. send.

The video encoder 303 encodes the video signal sent from the signal sending unit 302, further packetizes it, and sends the video elementary stream including the TS packets of the video to the TS multiplexer 309. The audio encoder 304 also 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 broadcasting information system 308 is a scheduler and file supply source of a TV broadcasting station, and includes data such as data broadcasting application and monomedia described in HTML5 format, application control information, signaling information related to data such as data broadcasting application, and 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.

The data carousel encoder 305 encodes data such as data broadcasting application and monomedia sent from the broadcasting information system 308, application control information, signaling information about data such as data broadcasting application, and is further divided into blocks. , A data carousel composed of one or more DDB messages and a DII message in which information of each DDB message is described is assembled and sent to the TS multiplexer 309.

The AIT encoder 306 encodes the application control information sent from the broadcast information system 308, further packetizes it, and sends the elementary stream including the AIT TS packets to the TS multiplexer 309. However, the AIT encoder 306 is not necessary when transmitting the AIT as a DDB message by the data carousel transmission method. That is, the equipment of the AIT encoder 306 is arbitrary and is drawn by 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 the 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 it 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 that serves 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 containing video TS packets. This video elementary stream is sent to the TS multiplexer 309.

Further, the audio signal sent from the signal sending unit 302 is supplied to the audio encoder 304. In the audio encoder 304, the audio signal is encoded and further packetized to generate an elementary stream including audio TS packets. This audio elementary stream is sent to the TS multiplexer 309.

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

If the AIT is not transmitted as the DDB message of the data carousel, the AIT encoder 306 generates an elementary stream including TS packets of the AIT based on the 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 sent from the broadcast information system 308, and sends it to the TS multiplexer 309. To be

The TS multiplexer 309 multiplexes the TS streams sent from the encoders 303 to 307 to generate a broadcast stream. Then, in the modulation/transmission unit 310, digital modulation such as OFDM is performed on the broadcast stream, RF modulation processing such as up conversion is further performed, and the broadcast stream is transmitted 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, and a cache. A memory 407, a data broadcasting application engine 408, a system control unit 409, a combining unit 410, and an IP interface 411.

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

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

The video decoder 404 decodes the encoded video signal obtained by the demultiplexer 402 to obtain a baseband video signal. The audio decoder 405 also 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 the PMT information included in the PSI.

The application data control unit 406 processes each file data used in data broadcasting. In the present embodiment, it is assumed that each file data used in data broadcasting is transmitted from two systems of a broadcast signal and an IP network. The former is via the tuner/demodulator 401 and the demultiplexer 402, and the latter is It 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, transfers the file data cache memory 407 for the data broadcasting service. Control the cache processing of. Further, the application data control unit 406 controls activation of the application by the data broadcasting 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 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, the information designating the compulsory cache of each file used in the data broadcast 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 the cache memory 407 based on the compulsory cache information included in the DCCT. Details of the file/data pre-cache will be given later.

The combining unit 410 combines the baseband video signal with the display signal of the data broadcast output from the data broadcast application engine 408 to obtain a video signal for video display. The baseband audio signal obtained by the audio decoder 405 becomes an audio signal for audio output. The broadcast program main part including a video signal and an audio signal 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 so as to be superimposed on the screen of the main broadcast program.

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

The tuner/demodulation section 401 receives the IF or RF modulated signal, performs demodulation processing such as down conversion and digital demodulation processing such as OFDM demodulation to obtain a broadcast stream. In the demultiplexer 402, demultiplexing processing and depacketizing processing are performed on this broadcast stream, and a PCR packet, video elementary stream, audio elementary stream, data carousel, 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 reproduction unit 403. The clock reproduction unit 403 reproduces the original clock information STC from the PCR packet. That is, the clock reproduction unit 403 generates time information that matches the time information generated by the clock generation unit 301 on the broadcast transmission system 11 side.

The coded video signal extracted by the demultiplexer 402 is sent to the video decoder 404 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 activation of the application by the data broadcasting application engine 408 based on the DII message, DDMT, DCMT, and AIT included in the DDB message. The data broadcasting application engine 408 processes the file data of the data broadcasting application transmitted as a DDB message, and generates a display signal of the data broadcasting. Then, in the synthesizing unit 410, the display signal of the data broadcast is synthesized with the baseband video signal to obtain a video signal for video display.

Further, the encoded audio signal extracted by the demultiplexer 402 is sent to the audio decoder 405 to be decoded, and a baseband audio signal for audio output is obtained. The broadcast program main part including a video signal and an audio signal is output as video and audio from a monitor display (not shown).

In addition, 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, cache memory for file data for the data broadcasting service. The cache processing to 407 is controlled.

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

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

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

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

Further, in the AIT, it is designated whether the file location designation method of the data carousel is the transmission path dependence designation method or the URI designation method.

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

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

(2) The DCCT is a file structure for each content (application) transmitted by data broadcasting, a file structure for each data broadcast presentation unit (PU) in the content (application), a content structure such as a file to be cached in advance, and a cache. It is a table 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 described in an XML (eXtensible Markup Language) notation format and a 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, a node tag descriptor is arranged in each module information (moduleInfoByte) of the DII message to associate the directory with the module. This makes it possible to associate the DII message with the DDMT and DCCT tables.

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

Hereinafter, in the data carousel transmission system, an embodiment for realizing the above two file location designation systems when data of the HTML5 data broadcasting application is transmitted will be described in detail.

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

In table_id, a value "0x02" for identifying that the table is a PMT is described. Also, “1” is described in the section_syntax_indicator. The section length of the PMT is described in section_length. Further, service_id for identifying the service (broadcast channel) is described in program_number. The version_number describes the version information of the PMT. "1" is described in the current_next_indicator. “0x00” is described in section_number. “0x00” is described in last_section_number. 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. The loop length of the first loop 501 is described in the program_info_length field immediately before the loop 501. In the descriptor area descriptor() formed by the first loop 501 that is repeated by the number of program_info_length, program information descriptors such as a conditional access system descriptor, a digital copy control descriptor, and an emergency information descriptor, etc. Is described.

The second loop 502 is an ES loop that stores information on each elementary stream, and stream_type, elementary_PID, and ES_info_length are described as attribute information in each loop. The stream_type describes the format identification of the elementary stream targeted by the loop. Elementary_PID describes the identifier (PID) of the TS packet that transmits the associated elementary stream or payload. ES_info_length describes the length of the descriptor area that follows. Then, the ES descriptor is stored in the descriptor area descriptor() formed by a loop that is repeated by 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, etc. are described.

The data coding method descriptor is a descriptor indicating a data coding method in the case of a data broadcasting elementary stream. 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. Designates transmission arrangement information of signaling information (DDMT and DCCT).

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

The data encoding method descriptor includes descriptor_tag, descriptor_length, and data_component_id as attribute information. The descriptor_length describes the loop length of the subsequent loop 601. The data_component_id is used to identify the encoding method of the data of the corresponding elementary stream. The allocation of the 16-bit field value complies with the standard of the standardization organization. When the corresponding elementary stream is an application (for example, in the HTML5 description format), a value identifying the application transmission is described in data_component_id. The descriptor_tag describes an 8-bit tag value that identifies the data encoding method 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 extend the identifier number or to store supplementary information defined for each encoding method. The data structure of the information described in this area is separately defined for each data encoding method. In the present embodiment, the data transmission of the data broadcasting application in the HTML5 is shown, and the additional arrangement information for specifying the transmission arrangement of the AIT and the transmission arrangement information of the signaling information (DDMT and DCCT) applied when the URI specifying method is 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 method descriptor.

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

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 mentioned above, the AIT is transmitted either as a data carousel or as independent packets (see Figure 2).

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

When the signaling_flag is 1, a 16-bit length signaling_module_id describes the module ID in the data carousel of the signaling file DDMT transmitted as a DDB message. When the DDMT is transmitted, the DCMT is also transmitted. In this embodiment, the module IDs of DDMT and DCCT are serialized (that is, DCCT has a module ID of +1), and the description in Additional_html5_info is omitted. Details of the data structure of each table DDMT and DCCT will be given later.

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

Also, when application_data_flag is 1, each flag of multipart_use_flag indicating whether or not multipartized 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.

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

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

A number for identifying the type of data in the payload of the DSM-CC section is stored in table_id (table identifier). The value of this field applies the specific coding description to the subsequent fields in the DSM-CC section. When the type of the DSM-CC section is a DII message, the value of table_id is 0x3B, the value of table_id in the case of DDB message is ox3C, and the value of table_id in the case of private data is 0x3E.

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

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

The 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 shown in (1) and (2) below 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) When the table_id is 0x3C (when the DSM-CC section is the DDB message), the module ID is set.

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

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

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

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

last_section_number (final 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 relevant section belongs.

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

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

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

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

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

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

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

A 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 a module information loop 901 that is repeated by numberOfModules (the number of modules), information for each module to be data-carousel transmitted is stored. As the attribute information of each module, a moduleId (module identifier), a moduleVersion (module version), and a moduleInfoLength (module information length) are stored, and subsequently, a descriptor area configured by a loop repeated by the number of moduleInfoLength. A moduleInfoByte (module information) is stored in. The moduleInfoByte (module information) can be a descriptor related to the corresponding module. The moduleId stores the module identifier of the module described in the moduleInfoByte area. In the present embodiment, in the case of the URI designating method, a node tag descriptor which is pointer information designating a corresponding module is described as moduleInfoByte (module information). The modules mentioned here are data modules of applications and signaling modules of DDMT and DCCT. In the directory structure shown by DDMT, a common node tag is specified for each directory and each file, and also in DCCT it is specified by the node tag (described later). Therefore, the directory is associated with the module through the node tag descriptor of the DII message. This makes it possible to associate the DII message with the DDMT and DCCT tables. Details of the data structure of the node tag descriptor will be given later.

The byte length of the private data area is described in privateDataLength (private data length), and privateDataByte (private data) is stored in the descriptor area formed by a loop 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.

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

In dsmcc D downloadDataHeader(), header information that identifies a DDB message in data carousel transmission is described. Although details of the header information are omitted, the header ID includes a downloadID that uniquely identifies the data carousel.

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

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 0. The data block body is stored in the block data area blockDataByte that is formed by a loop that is repeated only N times.

Blocks of signaling data such as DDMT and DCCT are included as data blocks stored in blockDataByte, in addition to application data for data broadcasting (provided that the URI specification method is selected as the file location specification method). A node tag descriptor (described later) stored as module information of the DII message can be used to filter a desired data block from the data carousel. However, the blocks 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 encoding method descriptor in the second loop of the PMT. .. That is, on the side of the receiver 12, the block of signaling data of DDMT and DCCT can be filtered when the PMT is received before reading the DII message. The details of the procedure for filtering the data block from the data carousel will be described later.

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

The table_id (table identification) is an 8-bit fixed value that identifies the 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 (hexadecimal number 0xFFD). The application_type (application format) indicates the format of the application transmitted by the AIT. The meaning of each value of the application_type is shown in FIG. version_number is the version number of the sub-table and is incremented by +1 when the information in the sub-table changes. Further, when the value of the version number becomes "31", the next step returns to "0". The current_next_indicator (current next instruction) is always "1". The section_number (section number) is an 8-bit field and represents the section number. The section number of the first section in the sub-table is 0x00. The section number is incremented by +1 each time a section having the same table identifier and application type is added. last_section_number (final section number) is an 8-bit field and defines the last section number in the sub table to which the section belongs.

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

The application_loop_length is an area in which the number of application information included in this MH AI table is written. Then, the application information descriptor loops 1101 are arranged by the number indicated by application_loop_length. Also, at the end of AIT, ITU-T Recommendation H.264. The cyclic redundancy code CRC_32 according to 222.0 is added.

In one application information descriptor loop 1101, application_identifier (application identifier), application_control_code (application control code), and application_descriptor_loop_length (application information descriptor loop length) are stored as application attribute information. application_identifier is a value that uniquely identifies an 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 attribute information of these applications, the application information descriptor descriptor() is stored in the descriptor area formed by the number of loops indicated by application_descriptor_loop_length. The descriptors in this descriptor area apply only to the corresponding application.

The semantics of application_control_code are specified for each application format, but if not specified for each application format, the semantics shown in FIG. 13 are used. If “AUTOSTART (automatic start)” is specified as the application_control_code, the receiver 12 that refers to this AIT table starts to start the application specified by the application_identifier. If "PREFETCH" is designated as the application_control_code, the receiver 12 that refers to this MH AIT table prefetches the application specified by the application_identifier. Further, if "KILL" is designated as the application_control_code, the receiver 12 that refers to this AIT table ends the execution of the application designated by the application_identifier.

In the descriptor area of 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 an application (whether HTTP/HTTPS transmission or data carousel transmission). In addition to the protocol for transmitting the application, the transmission protocol descriptor designates the file location designation method (whether the transmission path dependence designation method or the URI designation method) in the case of data carousel transmission. Other application information descriptors such as a simple application location descriptor (simple_application_location_descriptor) and an application boundary authority setting descriptor (application_boundary_and_permission_descriptor) are also placed in the loop 1101, but a detailed description thereof will be omitted.

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

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

The information of application_profile is written in a series of areas formed by loops for the number of application_profile_length. application_profile is a profile of a receiver in which this application can be executed. The requested function is indicated by a bit map for each function requested to the receiver. However, the upper 3 bits indicate function bitmap switching. The above bitmap is specified for each version. In addition, version_major, version_minor, and version_micro are versions of the application profile.

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 transmitting one application through a plurality of routes, and corresponds to the field of the same name in the transmission protocol descriptor.

FIG. 16 shows a data structure 1600 of the 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 indicating the designation of a transmission protocol such as broadcasting or communication and the file location designation method of the application data depending on the transmission protocol as the transmission means of the application. The transmission protocol descriptors are arranged in the common descriptor loop of the AIT or the 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 the data of the descriptor 0 following this 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 defines HTTP/HTTPS transmission, 0x0004 defines data carousel transmission of a transmission path dependence designation system, and 0x0006 defines URI-designated data carousel transmission. transport_protocol_label (transmission protocol label) is a value that uniquely identifies the transmission means when one application is transmitted through multiple routes, and corresponds to the field of the same name in the application descriptor (see FIG. 14). To do.

The selector_byte (selector byte) is an area for storing supplementary information defined for each protocol identifier, and the syntax is defined for each protocol identifier. In this 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 (data carousel transmission of the URI designation method), and when the protocol identifier is 4 (data carousel transmission of the transmission path dependence designation method) Therefore, the syntax of selector_byte is different. Details of the syntax of the selector byte in each case will be given later.

As described above, in the present embodiment, when data of an HTML5 data broadcasting application is transmitted by the data carousel transmission method, as a file location designation method, a transmission path dependence designation method and a URI (which are conventionally applied) are used. The 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 specification method is a method of specifying file data of a data broadcasting application in a hierarchy of a broadcasting transmission path 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 to indicate that it is the data carousel transmission of the (conventional) transmission line dependence specification method, and the selector byte area Specify the hierarchy of the above broadcast transmission path with.

Further, in the transmission path dependence designation method, file data is stored in an 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 the data carousel), the transmission efficiency and processing efficiency of the data broadcasting application are good. However, due to the data carousel transmission method, it is considered that there are significant restrictions on creating applications (described above).

Next, the URI designation method will be described. In this method, the file data of the data broadcasting application can be designated by an arbitrary URI.

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

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

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

remote_connection (remote connection) is 1 if the data carousel for transmitting the AIT and the application is not transmitted by the same service (including the case where the AIT is for communication acquisition), and 0 if they are transmitted by the same service. ..

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

The component_tag value indicating the service component to which the application is transmitted is described in the component_tag. The component stream provided by the stream identifier descriptor, which is one of the ES descriptors arranged in the second loop of the PMT, specifies the component stream in which the data carousel is transmitted.

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

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

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

As indicated by reference numeral 1801, the transmission protocol descriptor that matches the transport protocol label (=1) of the application descriptor of the desired application is filtered, and further indicated by reference numeral 1802. Specifies the component stream in which the data carousel is transmitted, based on the selector bytes (component tags) stored in the child. Also, DII messages can be filtered from within 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 rooted at the retrievable location of the application indicated by the selector byte of the transmission protocol descriptor. In the illustrated example, the application string is the module identifier of the application (in 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 resource name. From the data carousel, the section in which 0x3B is stored as the table identifier (table_id) can be acquired as a DII message. Also, resource names can be used to filter DDB messages.

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

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

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

From the HTML document of communication acquisition to A. When referencing a module (file data) called html, link tags are as follows.

href=arib-dc: //7EE9.7FEFE9.0448/40/0000/A. html

In addition, A. html to B.I. When referencing html, the link tag is as follows.

href=. ． /0001/B. html

FIG. 20 illustrates a signaling relationship for application acquisition in the case of data carousel transmission of the transmission path dependence designation method.

As indicated by reference 2001, the packet of the data carousel 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 2002, Additional_html5_info (see FIG. 7) inserted in the data encoding method descriptor (data_component_descriptor) (see FIG. 6) described in the second loop. AIT can be acquired based on the module identifier (ait_module_id) of the AIT included in () (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. Based on, the AIT can be obtained.

In the application information descriptor loop (see FIG. 11) of the AIT, since the protocol identifier of the transmission protocol descriptor of the application for which application_control_code is specified as “AUTOSTART” is 4, the transmission line It is possible to recognize that the data carousel transmission is a dependent specification method. Then, 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 resource name (“0010/index.html” in the illustrated example) included in the simple application location descriptor in the same application information descriptor. And a downloadID described in the DII message, a DDB message for transmitting the corresponding application (file data) can be specified.

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

URL_base_length indicates the number of bytes of the base part of the URL for acquiring the application. The URL_base_byte stores a character string of the base part of the URL for obtaining the application in a series of areas formed by a loop for the number of URL_base_length.

URL_extension_count indicates the number of extension parts of the URL for acquiring the application. As many URL_extension loops as URL_extension_counts are arranged. Then, in one URL_extension loop, a URL_extension_byte indicating the number of bytes of the extension part of the URL for obtaining the application and a URL_extension area including a loop for the number of URL_extension_length are arranged, and the application is obtained in the URL_extension. 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 obtaining the application in a folding method, and the URL can be completed by connecting the character strings.

Since the selector byte shown in FIG. 21 is entirely in a loop, it is possible to set a plurality of base parts of the URL from which the application can be obtained.

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

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

An application descriptor (application_descriptor), a transmission protocol descriptor (transport_protocol_descriptor), a simple application location descriptor (simple_application_location_descriptor), etc. are stored in the descriptor area in the application information descriptor loop (see FIG. 11) of the AIT. Has been done (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 described in the folding method in the selector byte of the transmission protocol descriptor is completed and the URL for obtaining the application is obtained, as shown by reference numeral 2202, from the data carousel, , DDB messages carrying signaling information DDMT can be filtered.

In the present embodiment, a common node tag is specified for each directory and each file in the directory structure indicated by DDMT. In addition, it is specified by the node tag even 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 to associate the directory with the module. This makes it possible to associate the DII message with the DDMT and DCCT tables.

Details of the data structure of the node tag descriptor will be given 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 carries the desired application data is filtered based on the module identifier described in the DII message.

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

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

The node_level is a 1-bit value indicating the level of the node designated by the node tag, and 0 is entered when the node is a module and 1 is entered when the node is a resource.

When the value of the node level is 0, that is, when the node is a module, the node tag node_tag of the module of 16-bit length is described.

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

As described above, when the URI designation method is selected as the file location designation 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 Figure 2). DDMT and DCCT are described in XML notation format and binary notation format. These signaling information will be described.

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

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

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

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

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

The directory_node_path_length represents the size of the information area of the directory_node_path_byte in bytes. The directory_node_path_byte is composed of a series of information areas consisting of loops for the number of directory_node_path_length, and stores the path name to the directory_node. The directory_node_path_byte is described 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, You can get the full URL "http://xbc.com/index.html".

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 the loop of one file node, node_tag and file_name_byte (file name) are stored as information of each file data included in the base directory. The node_tag is a value that commonly specifies each directory and each file in the directory structure indicated by the DDMT. Also in DCCT, it is specified by the 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 including a loop for the number of file_name_length.

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

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

Each file node has a node tag (@nodeTag) of the file node and a 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 structure for each content (application) transmitted by data broadcasting, a file structure for each data broadcast presentation unit (PU) in the content (application), a content structure such as a pre-cache target file, and cache control. It's a table. FIG. 27 shows a DCCT data structure 2700 in the binary notation format.

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

The number_of_content is an 8-bit parameter indicating the number of contents transmitted in the data carousel. The content is, for example, data broadcasting application described in HTML5 format, or file data such as monomedia 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 about a data broadcast presentation unit (Presentation Unit: PU) included in the content are written as information about the content. content_ID is a content identifier. content_version indicates the version of the content. The content_cache_size indicates the size for caching the content. Also, number_of_PU is the number of data broadcast presentation units PU included in the content, and PU loops 2702 corresponding to the number of number_of_PU are arranged.

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

Further, in the PU loop, a list of broadcast transmission files forming the data broadcast presentation unit (PU) is written. 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). Then, as many loops of PU member nodes as the number of number_of_PU_member_nodes are 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.

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

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

The file to be locked here is composed of, for example, a broadcast file list used from the current data broadcast presentation unit (PU) to the next data broadcast presentation unit (PU). On the production side of the broadcast program, by presenting the lock/unlock target file list with the signaling information of the data broadcast, the receiver side can perform the cache control operation by the lock/unlock. For example, on the receiver side, the file data necessary for the next transition data broadcasting presentation unit can be locked in the cache (that is, compulsory cache). As a result, it is possible to realize a timely data broadcasting service linked to a broadcast program. The unlock target file is composed of, for example, a broadcast file list that is unnecessary in the current data broadcast presentation unit (PU). By designating the unlock target file (that is, canceling the designation of the compulsory cache), unnecessary files can be deleted from the cache memory 407, and the memory size can be saved.

Also, in one PU loop, number_of_linked_PUs indicating the number of other PUs linked from this PU, and as many linked_PU loops as number_of_linked_PUs are arranged. In one loop of linked_PU, linked_PU_tag that is identification information of linked_PU is written.

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

Each data content has a content identifier (@id) as an attribute, a content version (@version), a cache size (@cacheSize) when the entire content is cached, 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 (@cacheSize) at the time of presentation unit cache, and a node tag (@primary) of the primary node in the presentation unit. It has a node (Member) that constitutes a presentation unit, a compulsory cache designation node (loclCacheNode), a compulsory cache release designation node (unlockCacheNode), and a link destination presentation unit (linkedPU) as elements.

The node (Member) that constitutes the presentation unit has a node tag (@nodeTag) as an attribute. The compulsory cache designated node (locCacheNode) has a node tag (@nodeTag) as an attribute. The forced cache release designation node (unlockCacheNode) has a node tag (@nodeTag) as an attribute. The link destination presentation unit (linkedPU) has a presentation unit identification tag (@puTag) as an attribute.

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

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

FIG. 30A shows the directory structure of content. Each content content 1, 2,... Is composed of a data broadcasting application (app) and material. The data broadcasting application and the material are resources whose substance is file data. Each resource can be identified by a 16-bit node_tag in the 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 the module identifier (moduleId). The application is composed of one or more HTML5 documents that are referred to when the content is executed (when the data broadcast is presented). The material is an image file such as jpeg or png referred to from the HTML5 document, monomedia data such as text, or the like. One HTML5 document and the material referenced from it constitute one data broadcast presentation unit PU. In the example illustrated in FIG. 30A, content1 is A11. html, A12. html, A13. It has one or more HTML documents such as html as a resource of the data broadcasting application. Of these, A11. html is a resource that is directly referenced when the content is executed.

FIG. 30B shows a reference relationship between resources at the time of executing content (at the time of presenting a data broadcast). In the illustrated example, the application A11 that is directly referred to when the content is executed and the materials B11 and B02 referred to by the same are a resource group 3001 that constitutes one data broadcast presentation unit PU, and p1 is assigned as PU_tag ( Note that B14 is a material that can be acquired at any time by HTTP transmission by communication, not by data carousel transmission by broadcasting, and is hereinafter 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 that the application A12 refers to are a resource group 3002 that configures one data broadcast presentation unit PU, and p2 is assigned as PU_tag (note that B07 indicates data by broadcasting. -It is a material that can be acquired at any time by HTTP transmission by communication rather than by carousel transmission, and is treated below as not included in the resource group of the data broadcast presentation unit). Similarly, the application A01 and the materials B03, B01, B04 referred to by it are a resource group 3003 that constitutes one data broadcast presentation unit PU, and p3 is assigned as PU_tag.

Also, 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 the application presentation screen that is first displayed and is directly referenced when the content is executed. On the other hand, the resource A12. html and the resource A01.contained in the content common outside the content1. html is A01. It is an HTML document that describes an application presentation screen that transitions from the 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 respectively configure one data broadcast presentation unit PU. Then, the data broadcast presentation units 3001, 3002, and 3003 that are linked to each other constitute a higher-level large resource group 3010. Resource A01. html, A12. html, A01. The html is file data (primary module) that is a main part of each data broadcast presentation unit PU.

Further, a larger resource group, that is, the entire data content is constituted by the entire content which is the entire application included in the package (one broadcast program). The entire data content is a range of the data broadcast presentation unit PU having a common content_ID. It is possible to collectively specify all the data broadcast presentation units PU included in the content by rotating the loop of the PU of the corresponding content_ID in the DCCT. In the example shown in FIG. 30B, the applications included in the content1 and common form a resource group 3020 for the entire content, and c1 is assigned as the content identifier.

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

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

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

As indicated by reference 3101, the packet of the data carousel 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.

Also, as indicated by reference numeral 3102, Additional_html5_info (see FIG. 7) inserted in the data encoding method descriptor (data_component_descriptor) (see FIG. 6) arranged in the second loop. AIT can be acquired based on the module identifier (ait_module_id) of the AIT included in () (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 AIT packet identifier (AIT PID) described in the second loop corresponding to the AIT elementary stream. Based on, the AIT can be obtained.

In the AIT application information descriptor loop (see FIG. 11), since the protocol identifier of the transmission protocol descriptor of the application for which the application_control_code is designated as “AUTOSTART (automatic start)” is 6, the URL designation It can be recognized that the method is data carousel transmission.

Further, as indicated by reference numerals 3104 and 3105, Additional_html5_info (see FIG. 7) inserted in the data encoding method descriptor (data_component_descriptor) (see FIG. 6) described in the second loop (see FIG. 7). It is possible to acquire DDMT and DCCT based on the module identifier (signaling_module_id) of each 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 directory node loop and the file node loop (described above) of the DDMT. Search the file to get its node tag. Note that when a transition to another HTML5 document referenced by the application is designated, the same processing is performed as indicated by reference numeral 3111.

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

Then, as indicated by reference numeral 3107, in the loop of the module information of the DII message (described above), the node tag descriptor matching the above node tag is searched for, and the module identifier corresponding to the node tag is searched. 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) ( It is possible to specify a DDB message for transmitting (file data).

If you want to cache the node (directory and file) linked to the application specified in "AUTOSTART (automatic start)", it is applicable in the DCCT PU loop (described above) as indicated by reference numeral 3109. Node tag to be searched, and further, as indicated by reference numeral 3110, a PU loop is searched to perform pre-caching based on the PU tag of the link destination, and forcible cache or unlock target of the lock target file. You can also cancel the forced cache specification of a file.

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

The tuner/demodulation unit 401 receives a broadcast signal by channel selection, and the demultiplexer 402 demultiplexes this broadcast stream to separate each of the original elementary streams, and also each elementary stream. De-packetization processing is performed.

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

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

When the AIT is transmitted as a module (DDB message) by the data carousel (Yes in step S3203), the application data control unit 406 uses the data encoding method 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 placed in the obtained application information descriptor loop of the AIT to determine the file location designation method of data carousel transmission (step S3206).

Here, in the case where the protocol identifier is 4, that is, the transmission path dependence designation method, the application data control unit 406 designates with the selector byte (see FIG. 17) described in the transmission protocol descriptor of the AIT. The DII message is acquired from the registered component tag (step S3207). Specifically, the section in which 0x3B is stored as the table identifier (table_id) is acquired as a DII message from the data carousel. Next, the application data control unit 406 acquires the 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, when the protocol identifier is 6, that is, in the URI designation method, the application data control unit 406 acquires the DII message and each signaling information DDMT and DCCT from the data carousel whose PID is designated in the PMT ( Step S3209). Specifically, the section in which 0x3B is stored as the table identifier (table_id) is acquired as a DII message from the data carousel. Further, as shown in FIG. 31, it is included in Additional_html5_info (see FIG. 7) inserted in the data encoding descriptor located in the second loop of the PMT (see FIG. 5). The DDMT and the DCCT are acquired based on the module identifier (signaling_module_id) of the signaling information of each of the DDMT and the DCCT.

The application data control unit 406 uses the obtained DDI message and each signaling information DDMT and DCCT to solve 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 loop of the application information descriptor of the AIT, the file that matches the URL character string described in the selector byte of the transmission protocol descriptor as the location of the desired application. • Retrieving the node tag of the data from the DDMT, then retrieves the module identifier of the module associated with that node tag in the DII message module information loop. Then, based on the obtained combination of the module identifier and the download identifier, the 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 entry module of the application by using the above location solving means (see FIGS. 22 and 31), and controls the cache processing of the module as necessary. Yes (step S3211).

In the present embodiment, the DCCT as the signaling information is, as the information indicating the 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). Describes the node tag of the presentation unit. Therefore, the application data control unit 406 forcibly caches the lock target file (for example, file data necessary for the next transition data broadcast presentation unit) or unlocks the target file (for example, the current data broadcast presentation unit). It is possible to cancel the specification of the compulsory cache for (file data that becomes unnecessary in step 2) and delete it from the cache 407, or to cache file data in link destination presentation units in advance.

Then, the application data control unit 406 uses the entry module of the application acquired according to the file location specification method of each of the transmission path dependence specification method or the URI specification method and the file data cached in the cache 407, The activation of the application by the data broadcasting application engine 408 is controlled (step S3211).

As described above, in the present embodiment, the signaling information DCCT applied by the URI designation method is, as information indicating cache control, the node tag of the lock target file, the node tag of the unlock target file, and the current 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 the lock target file (for example, file data necessary for the next transition data broadcast presentation unit) or unlocks the target file (for example, the current data broadcast presentation unit). It is possible to cancel the specification of the compulsory cache (for file/data which is not required in step 1) and delete it from the cache 407. Also, the file data for each link presentation unit can be cached in advance.

In the receiver 12, a rough procedure for controlling the cache operation by locking and unlocking the module for data carousel transmission 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 (which is the center of the data broadcast presentation unit) by an instruction from the data broadcast application control engine 408 or the like. Recognize that the presentation state of the data broadcast presentation unit (PU) is entered.
(Operation 3) In the DCCT, the application data control unit 406 also acquires each member file (PU_member_node) included in the corresponding data broadcast presentation unit (PU) at the same time and holds it in the cache memory 407.
(Operation 4) Further, in the DCCT, when the lock cache target is designated for the corresponding data broadcast presentation unit (PU), the application/data control unit 406 determines that the lock cache target is not acquired. Each file (module) is 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 corresponding data broadcast presentation unit (PU) is designated as the target of the unlock cache, 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 which is separately managed.
(Operation 6) The data broadcasting application engine 408 executes the application file specified in the primary module from the cache memory 407.
(Operation 7) After that, when the configuration of the member file (PU_member_node) or the lock cache target file or the unlock target file included in the data broadcast presentation unit (PU) currently in the presentation state changes due to the update of the DCCT, , (Operation 3) to (Operation 6) described above are performed.
(Operation 8) When a transition to a presentation state of another data broadcast presentation unit (PU) is caused by an application operation in the data broadcast application engine 408, the lock cache target file is temporarily held in the cache memory 407, The processes of (Operation 3) to (Operation 6) are performed. Files not subject to the lock cache may be deleted from the cache memory 407.

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

When the data broadcast application control engine 408 is performing an application operation, that is, presenting a data broadcast (Yes in step S3301), the application data control unit 406 determines whether the primary_module (data broadcast presentation unit) in the data content management table. By accessing the application file specified in (center of) (Yes 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 currently presented data broadcast presentation unit (PU) 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 broadcasting 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 lock cache target is designated 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) among the lock cache targets, and 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 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 designated (Yes in step S3306), the application data control unit 406 deletes the unlock target file, if cached in the cache memory 407. At the same time, the file is also deleted from the lock cache target file that was separately managed (step S3307).

After that, if 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 pre-cached is changed due to the update of the DCCT (Yes in step S3308), the step Returning to S3303, the above process is repeatedly executed in the data broadcast presentation unit (PU) that is 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 designated in the primary_module of the data broadcast presentation unit is accessed (step After returning to step S3303, the above process is repeatedly executed in the transition destination data broadcast presentation unit (PU).

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

FIG. 34 shows an example of locking and unlocking the file data cache 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 signaling information is included.

When the data broadcast application control engine 408 is performing the 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. Data of the application file “A01.html” specified in 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”, “B02” When the modules corresponding to these node_tags are acquired from the data carousel by acquiring them from the content management table, they are cached in the cache memory 407 as indicated by reference numeral 3401. However, since the object of the lock cache is not designated for this data broadcast presentation unit (PU), the cache operation is not performed. It should be noted that the method of accessing the module transmitted from the data_carousel from the node_tag is as described with reference to FIG. 31 (based on the combination of the module identifier (moduleId) and the downloadID corresponding to the node_tag in the DII message, You can filter the appropriate modules from the data carousel).

Next, it is assumed that an application operation in the data broadcast application engine 408 causes a transition to a presentation state of another data broadcast presentation unit (PU) identified by PU_tag=3. Similarly to the above, the application data control unit 406 determines that the application file “A11.html” specified in the Primary_module (center of the data broadcast presentation unit) of the transition destination data broadcast presentation unit (PU_tag=3), and , When each node_tag of each member (PU_member_node) “B11”, “B12”, and “B13” is obtained from the DCCT, the module corresponding to these node_tag is obtained from the data carousel, and as indicated by reference numeral 3402, The data is cached in the cache memory 407. However, since the target of the lock cache is not specified for this data broadcast presentation unit (PU), the lock cache operation is not performed.

The application/data control unit 406 constantly analyzes the signaling information DDMT and DCCT received from the data carousel. Then, as indicated by reference numeral 3403, when detecting that the version of DCCT is updated from 1 to 2, the application/data control unit 406 causes the primary_module of the data broadcast presentation unit (PU_tag=3) that is currently in the presentation state. Also, check each member file and the file for lock cache for any changes. Since there is no change in the member file this time, each member file previously cached is retained in the cache memory 407. Further, since “A12”, “B14”, “B12”, and “B15” are added as the files to be locked and cached in the data broadcast presentation unit (PU_tag=3), the application data control unit 406 determines that the data 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, the files managed as lock cache targets are underlined (the same applies hereinafter).

Then, as indicated by reference numeral 3405, when an event message instructing to update the presentation of the data broadcast is received, the data broadcast application engine 408 makes a transition of the HTML5 document from the A11 file being executed to the A12 file. .. At the same time, the application/data control unit 406 refers to the DCCT whose version is updated from 2 to 3, and the Primary_module of the data broadcast presentation unit (PU_tag=3) currently in the presentation state is “A12.html”. It is detected that the member file is changed to "B14", "B15", and "B16". As described above, since the Primary_module “A12.html” and the member files “B14” and “B15” are already locked in the cache memory 407, the data broadcasting application engine 408 stores them in the cache memory 407. The data broadcast can be quickly displayed by using the held file. That is, it is possible to present a timely data broadcast linked to a broadcast program. Further, since the target of the lock cache is not specified 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 retained in the cache memory 407 as they are, while the unnecessary file “A11” is deleted. Has been done.

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

In the currently used BML (Broadcast Markup Language) data broadcasting service, a script calls an API (Application Programming Interface) called “LockModuleOnMemory()” to pre-cache a specific file in a cache memory in advance. It is possible to set (for example, refer to Patent Document 4). With this method, it is necessary to incorporate special specifications that presuppose broadcast operation into the specifications of applications such as scripts.

On the other hand, according to the technology disclosed in the present specification, the transmitting side such as a broadcasting station transmits the information related to the data broadcasting including the information designating the compulsory cache, and the receiving side receives the information. The cache control of each file for data broadcasting is performed based on the compulsory cache information included in the signaling related to the data broadcasting. Therefore, according to the technology disclosed in the present specification, in the data broadcasting by the new HTML5, 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 JP, 2013-66160, A JP 2007-274193 A

The technology disclosed in the present specification has been described above in detail with reference to the specific embodiments. However, it is obvious that a person skilled in the art can make modifications and substitutions of the embodiment without departing from the gist 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 system. In the present specification, the embodiment applied to the broadcasting system that adopts the MPEG-2 TS method as the transport method has been described, but the technology disclosed in the present specification is not limited to this.

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

In short, the technology disclosed in the present specification has been described in the form of exemplification, and the contents described in the present specification should not be interpreted in a limited manner. To determine the gist of the technology disclosed in this specification, the claims should be taken into consideration.

Note that the technology disclosed in this specification may have the following configurations.
(1) A first encoder that encodes data of a data broadcasting application by a data carousel transmission method by designating a file location by either a transmission path dependence designation method or a URI designation method,
A second encoder for encoding program specific information (PSI) including a program management table (PMT) in which a data encoding descriptor that specifies transmission arrangement information of an application information table (AIT) related to the data broadcasting application is arranged; ,
A transmission processing unit that multiplexes and transmits a plurality of broadcast data including broadcast data encoded by the first and second encoders;
A transmitter comprising:
(2) In the application information table (AIT), a transmission line dependence designation method and a URI designation method of the data carousel are designated.
The transmitter according to (1) above.
(3) The transmission arrangement information of the signaling information (DDMT, DCCT) applied when the URI specifying method is selected is further specified by the data encoding method descriptor arranged in the program management table (PMT).
The transmitter according to (1) above.
(4) The signaling information (DDMT, DCCT) is included in a specific module of a data carousel to be encoded by the first encoder,
The transmitter according to (3) above.
(5) As the signaling information, a data directory management table (DDMT) for managing the directory structure of files transmitted by data broadcasting is included.
The transmitter according to any one of (3) and (4) above.
(6) As the signaling information, a file structure for each content (application) transmitted in the data broadcast, a file structure for each data broadcast presentation unit (PU) in the content (application), a data content indicating the content structure and cache control Including management table (DCCT),
The transmitter according to any one of (3) to (5) above.
(7) The signaling information is described in XML (eXtensible Markup Language) notation format and binary notation format.
The transmitter according to any one of (3) to (6) above.
(8) In each table included in the signaling information, a common node tag is specified for each directory and each file, and module information of a control message (DII) indicating information of each module of the data carousel. Place the node tag descriptor in and associate it with the module,
The transmitter according to any one of (3) to (7).
(9) A first encoding step of encoding a data of a data broadcasting application by a data carousel transmission method by designating a file location by either a transmission path dependence designation method or a URI designation method,
A second encoding for encoding program specific information (PSI) including a program management table (PMT) in which a data encoding 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 respectively;
A transmission method having.
(10) Designate a data carousel of a data broadcasting application whose file location is designated by either a transmission path dependent designation method or a URI designation method, and transmission arrangement information of an application information table (AIT) relating to the data broadcasting application. 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 descriptor is arranged;
An application data control unit that controls the processing of the data broadcasting application,
A receiver comprising the.
(11) The application data control unit is configured to transmit the application information table based on the transmission arrangement information of the application information table (AIT) described in the data encoding method descriptor arranged in the program management table (PMT). (AIT) and determines whether the file location specification method of the data carousel is the transmission path dependence specification method or the URI specification method based on the application information table (AIT).
The receiving device according to (10) above.
(12) When the URI designation method is selected as the file location designation method of the data carousel,
The application data control unit, from the data carousel whose packet identifier (PID) of the elementary stream is designated in the program management table (PMT), to the control message (DII) indicating the information of each module of the data carousel. ) And the signaling information (DDMT, DCCT) applied when the URI designation method is selected, the location of the module included in the data carousel is resolved.
The receiving device according to any one of (10) or (11) above.
(13) The application data control unit, based on the transmission arrangement information of the signaling information (DDMT, DCCT) described in the data encoding method descriptor arranged in the program management table (PMT), signaling information Get (DDMT, DCCT),
The receiving device according to (12) above.
(14) The application data control unit assigns a node tag matching a URI designating a location of a desired application in the application information table (AIT) to the signaling information (a directory structure of a file to be transmitted by data broadcasting). The data directory management table (DDMT) to be managed is searched, the module identifier of the module associated with the node tag is acquired 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 controller controls the signaling information (file structure for each content (application) transmitted in data broadcasting, file structure for each data broadcast presentation unit (PU) in the content (application), content structure). A data content management table (DCCT) indicating cache control is used to control the cache of file data transmitted by the data carousel.
The receiving device according to (12) above.
(16) When the reception processing unit receives the module designated as a lock target in the signaling information (DCCT), the application data control unit compulsorily caches the cache memory.
The receiving device according to (15) above.
(17) The application data control unit cancels the forced cache designation of a module designated as an 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 in advance.
The receiving device according to (15) above.
(19) Designate the data carousel of the data broadcasting application whose file location is designated by either the transmission path dependent designation method or the URI designation method, and the transmission arrangement information of the application information table (AIT) relating to the data broadcasting 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 descriptor is arranged;
An application data control step for controlling the processing of the data broadcasting application,
A receiving method having.

10... Digital broadcasting system 11... Broadcast transmission system, 12... Receiver 301... Clock generation unit, 302... Signal transmission unit 303... Video encoder, 304... Audio encoder 305... Caption encoder, 306... AIT encoder 307... PSI /SI encoder, 308... Broadcast information system 309... TS multiplexer, 310... Modulation/transmission unit 401... Tuner/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 ... synthesis unit 411 ... IP interface

Claims (4)

Transmitting an application, transmitting an application information table in which a transmission protocol descriptor specifying a protocol for transmitting the application and a location for obtaining the application is arranged, transmitting signaling information regarding transmission of the application, and A transmission unit for transmitting a table in which descriptors designating transmission information of the application information table and transmission information of the signaling information are arranged,
The signaling device includes a data directory management table (DDMT) for managing a directory structure of transmission data, and a node tag for associating the transmission data with a directory or a file is arranged in the data directory management table. Sending the application,
Transmitting an application information table in which a transmission protocol descriptor specifying a protocol for transmitting the application and a location for obtaining the application is arranged;
Sending signaling information about the transmission of the application,
Transmitting a table in which descriptors designating transmission information of the application information table and transmission information of the signaling information are arranged,
Have
The transmission method, wherein the signaling information includes a data directory management table (DDMT) for managing a directory structure of transmission data, and a node tag for associating the transmission data with a directory or a file is arranged in the data directory management table. An application, an application information table in which a transmission protocol descriptor designating a protocol for transmitting the application and a location for obtaining the application is arranged, signaling information regarding transmission of the application, and transmission information of the application information table And a reception processing unit that performs reception processing of a table in which descriptors designating transmission information of the signaling information are arranged,
An acquisition process of the application is performed based on the received application information table, signaling information related to the transmission of the application, and a table in which a descriptor specifying the transmission information of the application information table and the transmission information of the signaling information is arranged. An application data control unit to control,
Equipped with,
The signaling device includes a data directory management table (DDMT) that manages a directory structure of transmission data, and a node tag for associating the transmission data with a directory or a file is arranged in the data directory management table. An application information table in which a descriptor designating an application, a protocol for transmitting the application, and a location for obtaining the application is arranged, signaling information regarding transmission of the application, transmission information of the application information table, and the A reception processing step of performing reception processing of a table in which descriptors specifying transmission information of signaling information are arranged,
An acquisition process of the application is performed based on the received application information table, signaling information related to the transmission of the application, and a table in which a descriptor specifying the transmission information of the application information table and the transmission information of the signaling information is arranged. Application data control step to control,
Have
The receiving method, wherein the signaling information includes a data directory management table (DDMT) for managing a directory structure of transmission data, and a node tag for associating the transmission data with a directory or a file is arranged in the data directory management table.