JP2017050788A - Broadcast receiving apparatus and caption presentation method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a receiving apparatus in which a hybrid cast application is capable of presenting a caption by a presentation method desired by a program distributor.SOLUTION: In a receiving apparatus (3), an application (hybrid cast application) to be executed by a middleware and a synthesis part. The middleware acquires meta information indicating a method for presenting a caption of a program, from a transmission apparatus (2). The hybrid cast application (the application to be executed by the synthesis part) acquires the meta information and presents the caption by the presentation method indicated by the meta information.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a broadcast receiver that presents subtitles and a subtitle presenting method using such a broadcast receiver.

  In Hybridcast, which is a broadcasting / communication cooperation service that has recently started, an extended API (Application Programming Interface) that can be controlled from an HTML (Hyper Text Markup Language) application is used to access broadcast resources such as broadcast video and program information. (See Non-Patent Documents 1 and 2).

  In addition, in the broadcasting for 8K (4K) currently being developed, a new caption / text super technology based on an encoding method based on TTML is employed (see Non-Patent Document 3).

Radio Industry Association, Multimedia Coding System for Digital Broadcasting (2nd Generation) Standard ARIB STD-B62 1.2 Edition (2nd volume), P8-P11, P55, issued July 3, 2015 IPTV Forum, IPTV Rules HTML5 Browser Specification IPTVFJ STD-0011 2.1 Edition, P73-P80, issued on December 15, 2014 The Japan Radio Industry Association, MMT Media Transport System for Digital Broadcasting Standards ARIB STD-B60 Version 1.2, P118-P125, issued on March 17, 2015

  However, in the conventional configuration described above, the function provided by the extended API that can be controlled from the HTML application (Hybridcast application) is not sufficient, and the program distributor (or the provider providing the HTML application) on the HTML application. There is a problem that subtitles cannot be presented in a desired presentation method (presentation timing, presentation layout, etc.).

  The present invention has been made in view of the above problems, and the main purpose of the present invention is to present an upper layer program desired by a program distributor (or an HTML application provider) on an HTML application. It is to realize a broadcast receiver capable of presenting subtitles by a method.

  In order to solve the above problems, a broadcast receiver according to one aspect of the present invention is realized as a function of the upper layer program in a broadcast receiver in which a lower layer program and an upper layer program operate. A subtitle presenting section that presents subtitles of a program on an HTML application, and an acquisition processing section that obtains meta information indicating the subtitle presenting method from the outside of the broadcast receiver, the function of the lower layer program The subtitle presenting unit obtains the meta information acquired by the acquisition processing unit, and presents the subtitle with reference to the meta information.

  The broadcast receiver according to one aspect of the present invention has an effect that the upper layer program can present subtitles on the HTML application in a presentation method desired by the program distributor (or the provider of the HTML application). Play.

It is a block diagram which shows an example of a structure of the system which concerns on Embodiments 1-6 of this invention, and the principal part structure of the transmitter which is included in the said system, and a receiver. It is the functional block diagram which showed the principal part structure of the application relevant process part with which the receiver which concerns on Embodiments 1-5 is provided. It is the figure which illustrated the source (structured document) of the HTML5 application which the receiver concerning Embodiment 1-6 performs. 6 is a diagram illustrating an example of a definition of a method “tuneTo” called by a receiving device according to the first embodiment. FIG. It is a figure which shows the example of the data structure of the broadcast signal which the transmitter which concerns on Embodiment 1-3 transmits. It is the figure which illustrated the data structure of the caption presentation control information referred in order for the receiver concerning Embodiments 1-3 to show a caption. It is a figure for demonstrating an example of the data format of captiondata which the receiver which concerns on Embodiments 1-3 refers. It is the figure which illustrated schematically the detail of the script tag in the source of the HTML5 application which the receiver concerning Embodiment 1 performs. It is the figure which illustrated the data (structured document) of the TTML format. It is a figure for demonstrating another example of the data format of captiondata which the receiver which concerns on Embodiments 1-3 refers. It is a figure for demonstrating another example of the data format of captiondata which the receiver which concerns on Embodiments 1-3 refers. FIG. 10 is a diagram illustrating an example of a definition of a method “getCurrentSubtitleInformation” called by a receiving apparatus according to the second embodiment. It is the figure which illustrated schematically the detail of the script tag in the source | sauce of the HTML5 application which the receiver concerning Embodiment 2 performs. It is a figure regarding Embodiment 3, and is the figure which illustrated schematically the definition of the broadcast video-audio object. It is the figure which illustrated schematically the detail of the script tag in the source | sauce of the HTML5 application which the receiver concerning Embodiment 3 performs. It is a figure regarding Embodiment 4, and is the figure which illustrated schematically the definition of the broadcast video-audio object, and the definition of subtitle list information. It is the figure which illustrated schematically the detail of the script tag in the source | sauce of the HTML5 application which the receiver concerning Embodiment 4 performs. It is a figure regarding Embodiment 5, and is the figure which illustrated schematically the definition of the broadcast video-audio object. It is the figure which illustrated schematically the detail of the script tag in the source of the HTML5 application which the receiver concerning Embodiment 5 performs. FIG. 10 is a functional block diagram illustrating a main configuration of an application-related processing unit included in a receiving device according to Embodiment 6. It is the figure which illustrated schematically the detail of the script tag in the source of the HTML5 application which the receiver concerning Embodiment 1, 2, 4, and 6 performs. FIG. 10 is a diagram for explaining an example of a data format of caption data referred to by a receiving apparatus according to the sixth embodiment. FIG. 10 is a diagram for explaining another example of the data format of captiondata referred to by the receiving apparatus according to the sixth embodiment.

  In this specification, MMT (MPEG Media Transport) is adopted as a program (content) transmission standard. MMT is a media transport method used on IP (Internet Protocol), and is a method that enables media transmission on various transmission paths. Specifically, the MMT can refer to components such as video, audio, subtitles, and data constituting a program via different transmission paths by specifying a packet ID, IP address, or URL in the control information. it can. Further, in this specification, 8K (or 4K) broadcasting realized by MMT is assumed.

Embodiment 1
Hereinafter, a system including a receiving apparatus according to an embodiment of the present invention will be described with reference to the drawings.

[System overview and configuration]
The outline and configuration of the system will be described with reference to FIGS.

  FIG. 1 is a block diagram illustrating an example of a configuration of the system and a configuration of main parts of a transmission device and a reception device included in the system. FIG. 2 is a functional block diagram illustrating a functional configuration of an application-related processing unit included in the receiving device.

  As shown in FIG. 1, the system 1 includes a transmission device 2, a reception device 3 (broadcast receiver), a content server 5, and a content server 6.

  The transmission device 2 is a device that transmits content in which a plurality of components are assigned to one channel, and is a device managed by a broadcaster or the like.

  The receiving device 3 is a device that acquires an HTML application (Hybridcast application, structured document) via broadcast or communication, and reproduces the content by executing the acquired HTML application. The receiving device 3 is, for example, a television receiver, a mobile phone (smart phone), a tablet terminal, a PC, a portable game machine, or the like. The transmission device 2 and the reception device 3 are connected via the Internet. The transmission device 2 can transmit content and various other data to the reception device 3 via broadcast waves and the Internet.

  The content server 5 is a server that stores content transmitted by the transmission device 2. In the example illustrated in FIG. 1, the content server 5 is separate from the transmission device 2, but the transmission device 2 may include the content server 5.

  The content server 6 is a server managed by a business entity that manages the transmission device 2 or a business operator that is different from the business entity that manages the transmission device 2 (for example, a business operator that is trusted by the broadcaster that manages the transmission device 2). Is a server managed by. The receiving device 3 can acquire content and various other data not only from the transmitting device 2 but also from the content server 6 via the Internet.

  In the example shown in FIG. 1, the system 1 includes one transmission device 2, one reception device 3, one content server 5, and one content server 6. However, the present invention is not limited to this. The system 1 may include a plurality of transmission apparatuses 2, reception apparatuses 3, content servers 5, and content servers 6, respectively.

  Below, the structure of the transmitter 2 and the receiver 3 which comprise the system 1 is demonstrated.

(Configuration of transmitter 2)
As illustrated in FIG. 1, the transmission device 2 includes a component multiplexing unit 21, a broadcast transmission unit 22, and a communication transmission / reception unit 23.

  The component multiplexing unit 21 packetizes components such as video, audio, subtitles, and data, multiplexes them into one stream, and transmits them to the receiving device 3.

  Specifically, the component multiplexing unit 21 acquires program content from the content server 5. Then, the component multiplexing unit 21 controls the acquired program content (SI information, which will be described later), video, audio, and subtitles constituting the acquired program content, and HTML for presenting the program content Packetize applications and multiplex into one stream. The component multiplexing unit 21 transmits the generated stream to the reception device 3 via the broadcast transmission unit 22 or the communication transmission / reception unit 23.

  The component multiplexing unit 21 generates a plurality of streams (broadcast signals to be described later) from components such as video, audio, and subtitles constituting the program content, and the control information of the program content. Alternatively, the stream may be transmitted to the receiver 3 via the broadcast transmitter 22 and the remaining stream may be transmitted to the receiver 3 via the communication transceiver 23. In addition, the component multiplexing unit 21 may be configured to packetize storage destination information in which the HTML application is stored instead of the HTML application.

  The broadcast transmission unit 22 transmits data (contents and the like) via broadcast waves.

  The communication transmitting / receiving unit 23 communicates with other devices such as the receiving device 3 or the content server 6 and exchanges data by wireless communication means or wired communication means.

(Configuration of receiving apparatus 3)
As illustrated in FIG. 1, the reception device 3 includes a broadcast reception unit 31, an operation unit 32, a communication transmission / reception unit 33, a component demultiplexing unit 34, a video decoding unit 35, an audio decoding unit 36, a caption decoding unit 37, and application-related A processing unit 38, a display 39, a speaker 40, and a storage unit 41 are provided.

  The operation unit 32 receives an operation from the user and outputs an operation signal indicating the received operation. The operation unit 32 may be configured by input devices such as a keyboard, a mouse, a keypad, and operation buttons. Further, a touch panel in which the operation unit 32 and the display 39 are integrated may be used. The operation unit 32 may be a remote control device such as a remote controller that is separate from the receiving device 3.

  The broadcast receiving unit 31 receives data via broadcast waves. The broadcast receiving unit 31 is, for example, a broadcast receiving tuner.

  The communication transmitter / receiver 33 communicates with other devices such as the transmission device 2 or the content server 6 by wireless communication means or wired communication means, and exchanges data. The communication transceiver 33 is, for example, a LAN terminal or a wireless LAN interface.

  The component demultiplexer 34 demultiplexes the stream received via the broadcast receiver 31 and, based on the control information, demultiplexed video components into the video decoder 35 and audio components into the audio decoder 36. Then, the demultiplexed caption component is output to the caption decoding unit 37, and SI information and an HTML application described later are output to the application related processing unit 38, respectively. Further, the component demultiplexing unit 34 may output the operation signal output from the operation unit 32 to the application related processing unit 38.

  The video decoding unit 35 acquires the encoded video component from the component demultiplexing unit 34 and decodes the encoded video component.

  The audio decoding unit 36 acquires the encoded audio component from the component demultiplexing unit 34 and decodes the encoded audio component.

  The subtitle decoding unit 37 acquires the encoded subtitle component from the component demultiplexing unit 34 and decodes the encoded subtitle component.

  The application related processing unit 38 acquires SI information and an HTML application from the component demultiplexing unit 34. The application related processing unit 38 refers to the HTML application and specifies a component to be presented.

  FIG. 3 is a diagram illustrating a source (structured document) of an HTML5 application. Specifically, the application-related processing unit 38 specifies a component to be presented by referring to each param element constituting the content of the object element 211 of the structured document.

  Then, the application-related processing unit 38 acquires the video component, the audio component, and the subtitle component to be presented from the video decoding unit 35, the audio decoding unit 36, and the subtitle decoding unit 37, respectively, and presents the video component and the audio component. In both cases, the caption component is presented by the presentation method determined based on the SI information. This SI information includes meta information (Subtitle_info information described later) indicating a caption presentation method.

  Detailed processing of the application related processing unit 38 will be described later with reference to another drawing.

  The display 39 displays the video indicated by the video signal from the application related processing unit 38. As the display 39, for example, an LCD (liquid crystal display), an organic EL display, a plasma display, or the like can be applied.

  The speaker 40 outputs the sound indicated by the sound signal from the application related processing unit 38.

(Application-related processing unit 38)
The application related process part 38 is demonstrated using FIG. FIG. 2 is a block diagram showing a main configuration of the application related processing unit 38 in the present embodiment. As shown in FIG. 2, the application-related processing unit 38 includes a middleware unit and a synthesis unit.

  As illustrated in FIG. 2, the middleware unit functions as an SI information acquisition processing unit 381, an application data acquisition processing unit 382, and a caption acquisition processing unit 383. That is, the SI information acquisition processing unit 381, the application data acquisition processing unit 382, and the caption acquisition processing unit 383 are realized as middleware (lower layer program) functions.

  The SI information acquisition processing unit 381 (acquisition processing unit) acquires the above-described SI information and stores the acquired SI information in the storage unit 41.

  The application data acquisition processing unit 382 acquires an operation signal and an HTML application.

  The caption acquisition processing unit 383 acquires the decoded caption component.

  The synthesizing unit is a program (for example, an HTML5 browser) in a higher layer than the middleware having a function of executing an HTML application. In the present embodiment, the HTML application executed by the synthesizing unit is an application that performs presentation control of video, audio, and subtitles according to the description of HTML.

  The synthesizing unit that has executed the HTML application functions as a video / audio presentation processing unit 384 and a caption presentation processing unit 385, as shown in FIG.

  The video / audio presentation processing unit 384 specifies video components and audio components to be presented with reference to the HTML application. The video / audio presentation processing unit 384 acquires the specified video component and audio component from the video decoding unit 35 and the audio decoding unit 36, respectively, and presents the acquired video component and audio component.

  The caption presentation processing unit 385 (caption presentation unit) identifies a caption component to be presented with reference to the HTML application. The caption presentation processing unit 385 acquires the caption component to be presented from the caption acquisition processing unit 383 and presents the acquired caption component.

  Specifically, the caption presentation processing unit 385 acquires SI information (specifically, Subtitle_info information) related to the program from the SI information acquisition processing unit 381 when the user selects a program, and thereafter Then, the caption component is presented by the presentation method indicated by the Subtitle_info information. When the HTML application is not included in the broadcast signal, the video / audio presentation processing unit 384 and the caption presentation processing unit 385 acquire the video component, the audio component, and the caption component to be presented according to the SI information regarding the program, and the SI Each component is presented according to the presentation information included in the information and caption component.

(About tuneTo method)
When the user performs an operation of selecting a program for the HTML application, the HTML application calls the tuneTo method. FIG. 4 is a diagram showing two examples of the tuneTo method called by the HTML application.

  As can be seen from FIG. 4, each tuneTo method shown in FIG. 4 is an extension of the tuneTo method disclosed in Non-Patent Document 1. That is, the Subtitle_info information is the return value of the tuneTo method. Therefore, regardless of which tuneTo method is called, the HTML application can obtain the Subtitle_info information at that time as a return value. Here, the user performs an operation of selecting a program. However, when an HTML application is read in advance, the tuneTo method may be called by describing the operation of selecting a channel in the HTML application. .

(Example of data structure of broadcast signal)
A broadcast signal including each component and SI information presented by the HTML application will be described with reference to FIG. FIG. 5 is a diagram illustrating a data structure of a broadcast signal.

  A broadcast signal 100 shown in FIG. 5 is a content transmission unit according to the present embodiment. As shown in FIG. 5, the broadcast signal 100 includes each component of the program (caption asset 151, video asset 152, audio asset 153, and data asset 154), PA message 110, and M2 section message. The PA message 110 and the M2 selection message are SI information (MMT-SI).

  The caption asset 151 includes a TTML document file in which the caption text is described.

  The data asset 154 includes an HTML application. For example, if the data asset 154 is not included in the broadcast signal 100, the MPT 111 may include information indicating the storage location of the data asset 154 (HTML application) (for example, URL information indicating the content server 6). Good.

  In MMT, components such as video and audio are defined as assets. That is, a video asset is a video component, an audio asset is an audio component, and a caption asset is a caption component. Each asset has a component tag for identifying it from other assets.

  The M2 section message is information used to transmit the section extension format of MPEG-2 Systems. In the present embodiment, the M2 section message includes MH-AIT. MH-AIT is an AIT (Application Information Table) for MMT.

  The PA message 110 is control information indicating the asset configuration and the like. In MMT, a message includes a table having elements and attributes indicating specific information, and the table includes a descriptor indicating more detailed information. Specifically, the PA message 110 includes an MPT (MMT Package Table) 111 as shown in FIG.

  The MPT 111 indicates information constituting the package such as a list of assets, a packet ID for specifying an MMT packet including the asset, and a position of a broadcast signal. By analyzing the MPT 111, it is possible to specify the assets constituting the program.

  As shown in FIG. 5, the MPT 111 includes Data_Component_Descriptor information 130. Data_Component_Descriptor information 130 indicates a list of components constituting the program, and includes a component tag of each component. Further, as shown in FIG. 5, the aforementioned Subtitle_info information (Subtitle_info information 131) is included in the Data_Component_Descriptor information 130.

  FIG. 6 is a diagram illustrating a data structure of the Subtitle_info information 131 (caption presentation control information). As shown in FIG. 6, the Subtitle_info information 131 includes ISO_639_language_code (language code), type (subtitle type), OPM (operation mode), TMD (time control mode), DMF (display mode), and resolution (display). In the case where the value of the time control mode is 0010, reference_start_time (reference start time, that is, UTC time as the starting point of the time code in the TTML document) is further included.

  Those skilled in the technical field of the present invention who are familiar with the ARIB standard can clearly grasp the meaning of the information. Therefore, this information will not be described in detail here.

  When there are N subtitle components that make up a program (for example, there are two subtitle components consisting of a Japanese subtitle component and an English subtitle component), the subtitle components are linked to each subtitle component. N pieces of Subtitle_info information 131 are included in the MPT 111.

(Example of data format of caption data (captiondata))
Next, an example of the data format of captiondata will be described with reference to FIG.

  FIG. 7 is a diagram for explaining an example of the data format of captiondata that the caption presentation processing unit 385 according to the present embodiment acquires from the caption acquisition processing unit 383. 7A shows the definition of the data format of captiondata, and FIG. 7B shows an example of captiondata.

  For the values (0.ttml, 1.png, 2.aif) indicated by data in (b) of FIG. 7, the corresponding caption data (text data) is converted to JSON format, and binary data (png Data, aif, etc.) may be encoded into Base64 and then converted to JSON format.

  The subtitle stream acquired by the subtitle acquisition processing unit 383 includes meta information (information for acquiring subsample data, etc.) constituting the captiondata, and the captiondata is generated from the subtitle stream by the subtitle acquisition processing unit 383. Is done.

  As can be seen from FIG. 7, in the present embodiment, the caption data is described in JSON format. FIG. 7B shows a caption component acquired from the caption acquisition processing unit 383 (a TTML document in which captions to be presented by the broadcast receiver, caption images, and subsample data files such as caption audio). Is an example of captiondata converted into JSON format in accordance with the definition of the data format of captiondata in FIG.

  Note that captiondata does not have to be described in JSON format. That is, the captiondata may have any data structure including the type of information, the length of the field in which the information is stored, and the value stored in the field for each piece of information constituting the captiondata. .

  Further, the information for acquiring the sub-sample data included in the caption data may be only the file name of the TTML document. Alternatively, as the information for acquiring the subsample data, in addition to the file name of the TTML document, the file name of the subtitle image, the file name of the subtitle audio, and the file name of the external font are all or any part of the file name It may be included.

  In this embodiment, a TTML document is converted into a JSON format and sent. However, a TTML document that has been analyzed and extracted only corresponding text data may be used.

(Operations when tuning an HTML application)
The operation during channel selection of the HTML application will be described with reference to FIGS. 3 and 7 to 9. FIG. 8 is a description example of the script tag 212 for presenting the subtitle_info information 131 using the tuneTo method. FIG. 9 is a diagram illustrating data in the ttml format.

  As can be seen from FIG. 3, a script tag 212 is included in the source of the HTML application.

  The synthesizing unit that executes the HTML application including the script tag 212 illustrated in FIG. 8 as a source executes the tuneTo method when a program channel selection operation is performed on the HTML application.

  The synthesizing unit (video / audio presentation processing unit 384) presents the video and audio of the selected program, and the synthesizing unit (caption presentation processing unit 385) displays the selected program acquired from the return value of the tuneTo method. The Subtitle_info information 131 included in the SI information (SI information acquired by the SI information acquisition processing unit 381) is presented.

  Although not shown in FIG. 8, the caption presentation processing unit 385 performs caption presentation control according to the Subtitle_info information 131 and the HTML description.

  Specifically, the caption presentation processing unit 385 can refer to the HTML application in the storage unit 41 for the Subtitle_info information 131 included in the SI information acquired by the SI information acquisition processing unit 381 immediately after the program is selected. Each subtitle data is presented in accordance with the Subtitle_info information 131 and the HTML description recorded in the memory area.

  That is, the caption presentation processing unit 385 presents each caption data on the HTML application (in the HTML application screen).

(Operation of HTML application when receiving subtitle stream)
The operation when the HTML application presents each subtitle with the middleware receiving the subtitle stream as a trigger will be described with reference to FIG. 7, FIG. 9, and FIG.

  The script tag 212 included in the source of the HTML application according to the present embodiment is also shown in FIG. That is, the script tag 212 includes not only a description regarding the tuneTo method but also a description regarding the event listener addCaptionListener.

  The synthesis unit registers an event listener addCaptionListener in the broadcast video / audio object at the start of execution of the HTML application. As a result, when the subtitle acquisition processing unit 383 acquires the subtitle stream, the event registered by the addCaptionListener is fired, and the acquired subtitle stream is converted into the data format of the captiondata and notified to the subtitle presentation processing unit 385. The caption presentation processing unit 385 presents each caption data in the caption data according to the Subtitle_info information 131 and the HTML description included in the SI information acquired from the return value of the tuneTo method.

  For example, when the caption data to be presented is indicated by the caption data of FIG. 7B, the caption presentation processing unit 385 includes a 0.ttml file (TTML document file illustrated in FIG. 9) included in the caption data, 1. Get png file (subtitle image file) and 2.aif file (subtitle audio file), subtitle character string, subtitle image and subtitle described in TTML document according to Subtitle_info information 131 and HTML description Present audio.

(Advantages of the receiving device 3)
As described above, the receiving device 3 can present each caption data of a program according to the Subtitle_info information 131 and the description of HTML.

  Therefore, it can be said that the receiving device 3 can present each caption data in a manner desired by the program distributor (or the provider providing the HTML application) on the HTML application.

(About another example of the data format of captiondata)
Another example of the data format of captiondata will be described with reference to FIGS.

  10 and 11 are diagrams for explaining other examples of the data format of captiondata. FIG. 10A shows the definition of the data format of caption data according to another example, and FIG. 10B shows an example of the caption data.

  The captiondata in FIG. 10 is also different from the captiondata in FIG. 7 in the following points.

  In other words, the caption data of FIG. 10 is different from the caption data of FIG. 7 in that reference_start_time is included as caption meta information instead of MPU Time Stamp.

  Still another example of the data format of captiondata will be described with reference to FIG. (A) of FIG. 11 shows the definition of the data format of caption data according to still another example, and (b) and (c) of FIG. 11 show an example of such caption data.

  The caption data in FIG. 11 is different from the caption data in FIG. 10 in the following points.

  That is, the caption data in FIG. 11 is different from the caption data in FIG. 10 in that the information for acquiring each sub-sample data is described as the URL of the storage location information in which the data is stored instead of the data. ing.

  The URL may be described in a format of “http: // localhost / <service_id> / <asset_id> / <mpu_sequence_number> / <subsample_no>” as shown in FIG. 11B, for example. That is, the URL may be a URL indicating the acquisition destination of each subsample data.

  Alternatively, for example, as shown in (c) of FIG. 11, it may be described in a format of “http: // localhost / <service_id> / <asset_id> / <mpu_sequence_number> /”. That is, the URL may be a URL indicating the acquisition destination of the TTML document file.

  That is, the subtitle presentation processing unit 385 acquires and analyzes the TTML document file based on the caption data in (c) of FIG. 11, and information for acquiring other subsample data indicated in the TTML document file Other subsample data can be acquired with reference to the URL.

  Note that the caption presentation processing unit 385 does not acquire the data of FIG. 10 and the data of FIG. 11 in the form of a JSON message using WebSocket or the like, instead of acquiring the data in the form of the return value captiondata of the event listener addCaptionListener. Also good.

[Embodiment 2]
Another embodiment of the present invention will be further described with reference to FIGS. 12 and 13 as follows. For convenience of explanation, members having the same functions as those described in the embodiment are given the same reference numerals, and descriptions thereof are omitted.

  FIG. 12 is a diagram illustrating the getCurrentSubtitleInformation method that is called by the HTML application when a predetermined event is fired. FIG. 13 is a diagram schematically illustrating details of the script tag 212 included in the source of the HTML application according to the present embodiment.

[System overview and configuration]
The system according to the present embodiment is the same system as the system according to the first embodiment, except that the opportunity to acquire Subtitle_info information is different.

  Since the system according to the present embodiment is configured in the same manner as the system according to the first embodiment, description of the configuration of the system according to the present embodiment is omitted.

(About getCurrentSubtitleInformation method)
FIG. 12 shows an example of the definition of the getCurrentSubtitleInformation method. As can be seen from FIG. 12, the HTML application can obtain the Subtitle_info information at that time as a return value of the getCurrentSubtitleInformation method when a predetermined event is fired.

  The predetermined event may be, for example, an event “Reception of SI information including Subtitle_info information”, or “Subtitle_info information update (content different from Subtitle_info information included in previously received SI information). Event of “SI information including Subtitle_info information”) or “switching of subtitle selection language by the user”. Of the above, occurrence of a predetermined event due to reception of SI information is notified from the middleware unit (SI information acquisition processing unit 381) to the synthesis unit.

(Operations when tuning an HTML application)
An operation executed by the HTML application triggered by the occurrence of a predetermined event during program playback will be described with reference to FIG. FIG. 13 is a description example of a script tag 212 for presenting subtitle_info information 131 using the getCurrentSubtitleInformation method.

  The synthesis unit that executes the HTML application including the script tag 212 shown in FIG. 13 as a source executes the getCurrentSubtitleInformation method and acquires the subtitle_info information 131 when a predetermined event is fired.

  The synthesis unit (caption presentation processing unit 385) presents the Subtitle_info information 131 included in the SI information acquired by the SI information acquisition processing unit 381.

  Although not shown in FIG. 13, the caption presentation processing unit 385 performs caption presentation control according to the Subtitle_info information 131 and the HTML description.

  Specifically, the caption presentation processing unit 385 stores the Subtitle_info information 131 included in the SI information acquired by the SI information acquisition processing unit 381 immediately after the occurrence of a predetermined event is notified from an operation by middleware or a user. The subtitle data is recorded in a memory area that can be referred to by the HTML application in the unit 41, and each subtitle data is presented in accordance with the Subtitle_info information 131 and the HTML description.

(Advantages of the receiving device 3)
The receiving device 3 according to the present embodiment has the same effects as the receiving device 3 according to the first embodiment. Further, even when the subtitle_info information 131 to be distributed is updated during the broadcast period of the program or when the selection language of the subtitles to be presented is switched by the user's operation, the program distributor (or HTML application providing business) Each subtitle data can be presented in a desired manner.

(Additional notes of embodiment 2)
The getCurrentSubtitleInformation method may not be a method that the HTML application calls when an event is fired. That is, the timing at which the getCurrentSubtitleInformation method is called may be a timing according to the implementation of the HTML application source.

  For example, the source of the HTML application may be implemented so that the getCurrentSubtitleInformation method is called when a certain button (for example, a button for switching subtitles) on the application screen is operated.

[Embodiment 3]
Still another embodiment of the present invention will be described with reference to FIGS. 14 and 15 as follows. For convenience of explanation, members having the same functions as those described in the embodiment are given the same reference numerals, and descriptions thereof are omitted.

  FIG. 14 is a diagram schematically illustrating the definition of a broadcast video / audio object according to the present embodiment. FIG. 15 is a diagram schematically illustrating details of the script tag 212 included in the source of the HTML application according to the present embodiment.

[System overview and configuration]
The system according to the present embodiment is the same system as the system according to the second embodiment, except that when the middleware receives the subtitle stream, the HTML application acquires the Subtitle_info information via the event listener.

  Since the system according to the present embodiment is configured in the same manner as the system according to the first embodiment, description of the configuration of the system according to the present embodiment is omitted.

(About broadcast video and audio objects)
The broadcast video / audio object shown in FIG. 14 is an extension of the broadcast video / audio object of Non-Patent Document 1. As can be seen from FIG. 14, the broadcast video / audio object according to the present embodiment includes Subtitle_info information in the return value of the event listener addCaptionListener.

(Operation of HTML application when receiving subtitle stream)
An operation performed by the HTML application triggered by the middleware receiving a caption stream (caption component) will be described with reference to FIG. FIG. 15 is an example of a script tag for registering an event listener addCaptionListener in a broadcast video / audio object.

  The synthesizing unit registers the event listener addCaptionListener in the broadcast video / audio object at the start of execution of the HTML application including the script tag 212 shown in FIG. 15 as a source.

  Thereby, when the caption acquisition processing unit 383 receives the caption stream, the event registered by the addCaptionListener is fired, and the Subtitle_info information 131 and the caption data read from the storage unit 41 are notified to the caption presentation processing unit 385. The caption presentation processing unit 385 presents each caption data in the caption stream according to the notified Subtitle_info information 131 and the HTML description.

  Specifically, the subtitle presentation processing unit 385 can refer to the HTML application in the storage unit 41 for the Subtitle_info information 131 included in the SI information acquired by the SI information acquisition processing unit 381 immediately after the middleware receives the subtitle stream. The subtitle data in the subtitle stream is presented in accordance with the Subtitle_info information 131 and the HTML description.

(Advantages of the receiving device 3)
The receiving device 3 according to the present embodiment has the same effects as the receiving device 3 according to the first and second embodiments.

[Embodiment 4]
Still another embodiment of the present invention will be described below with reference to FIGS. 16 and 17. For convenience of explanation, members having the same functions as those described in the embodiment are given the same reference numerals, and descriptions thereof are omitted.

  FIG. 16A schematically illustrates the definition of the broadcast video / audio object according to the present embodiment, and FIG. 16B schematically illustrates the definition of the caption list information according to the present embodiment. FIG. FIG. 17 is a diagram schematically illustrating details of the script tag 212 included in the source of the HTML application according to the present embodiment.

[System overview and configuration]
The system according to the present embodiment is different from that according to the first embodiment in that the HTML application of the receiving apparatus acquires Subtitle_list information (caption list information) instead of Subtitle_info information at a timing according to the implementation of the source. It is different from the system concerned.

  Since the system according to the present embodiment is configured in the same manner as the system according to the first embodiment, description of the configuration of the system according to the present embodiment is omitted.

(About broadcast video and audio objects)
The broadcast video / audio object shown in (a) of FIG. 16 is an extension of the broadcast video / audio object of Non-Patent Document 1. As can be seen from FIG. 16A, the broadcast video / audio object according to the present embodiment has a getSubtitleList method.

  The getSubtitleList method is a method for acquiring Subtitle_list information. The Subtitle_list information is generated from the Subtitle_info information 131 and SI information included in the MPT.

  As shown in FIG. 16B, the Subtitle_list information is composed of a language code (ISO_639_language_code) indicating the language of the subtitle stream and a URL indicating the storage location where the subtitle stream is stored.

  If there are N subtitle streams (subtitle components) constituting the program, the Subtitle_list information includes N combinations of these pieces of information.

(Operations when starting HTML applications)
An operation executed when the HTML application is activated will be described with reference to FIG.

  The synthesizing unit executes processing when the getSubtitleList method is called in an HTML application that includes the script tag 212 illustrated in FIG. 17 as a source.

  Thus, the synthesizing unit (caption presentation processing unit 385) presents Subtitle_list information included in the SI information acquired by the SI information acquisition processing unit 381 while presenting video, audio, and subtitles of the program. In addition, although the example which displays the information contained in Subtitle_list as a text was shown above, the receiver 3 defines the object which stores the information contained in Subtitle_list, and stores the acquired information in the memory | storage part 41 as said object May be.

  Note that when there are N subtitle streams constituting the program, the subtitle presented by the subtitle presentation processing unit 385 is a subtitle in a language designated by the user among a plurality of different languages.

  The user can grasp which other language can be selected as the subtitle language by looking at the Subtitle_list information presented by the synthesis unit.

(Additional notes of Embodiment 4)
The receiving device 3 that combines the features of the first embodiment and the features of the fourth embodiment is also included in the scope of the broadcast receiver according to the present invention. Such a caption presentation processing unit 385 of the receiving device 3 acquires both the Subtitle_info information and the Subtitle_list information, and presents the Subtitle_list information while presenting the caption by the presentation method indicated by the Subtitle_info information.

[Embodiment 5]
Still another embodiment of the present invention will be described below with reference to FIGS. 18 and 19. For convenience of explanation, members having the same functions as those described in the embodiment are given the same reference numerals, and descriptions thereof are omitted.

  FIG. 18 is a diagram schematically illustrating the definition of a broadcast video / audio object according to the present embodiment. FIG. 19 is a diagram schematically illustrating details of the script tag 212 in the source of the HTML5 application according to the present embodiment.

[System overview and configuration]
The system according to the present embodiment is the same system as the system according to the fourth embodiment except that when the middleware receives a subtitle stream, the HTML application acquires subtitle list information via the event listener.

  Since the system according to the present embodiment is configured in the same manner as the system according to the first embodiment, description of the configuration of the system according to the present embodiment is omitted.

(About broadcast video and audio objects)
The broadcast video / audio object shown in FIG. 18 is an extension of the broadcast video / audio object of Non-Patent Document 1. As can be seen from FIG. 18, the broadcast video / audio object according to the present embodiment includes subtitle list information in the return value of the event listener addCaptionListener.

(Operation of HTML application when receiving subtitle stream)
The operation executed by the HTML application triggered by the middleware receiving the subtitle stream will be described with reference to FIG.

  The synthesis unit registers an event listener addCaptionListner in the broadcast video / audio object at the start of execution of the HTML application including the script tag 212 shown in FIG. 19 as a source.

  As a result, when the caption acquisition processing unit 383 receives the caption stream, the event registered by the addCaptionListener fires, and the Subtitle_info information 131, the caption list information, and caption data read from the storage unit 41 are notified to the caption presentation processing unit 385. The caption presentation processing unit 385 presents the caption list information included in the SI information acquired by the SI information acquisition processing unit 381.

  Specifically, the subtitle presentation processing unit 385 refers to the subtitle list information included in the SI information acquired by the SI information acquisition processing unit 381 immediately after the middleware unit receives the subtitle stream by the HTML application in the storage unit 41. Record in possible memory area. Thereafter, the caption presentation processing unit 385 presents the caption list information recorded in the memory area.

(Advantages of the receiving device 3)
The receiving device 3 according to the present embodiment has the same effects as the receiving device 3 according to the fourth embodiment.

[Embodiment 6]
The following will describe still another embodiment of the present invention with reference to FIGS. For convenience of explanation, members having the same functions as those described in the embodiment are given the same reference numerals, and descriptions thereof are omitted.

  FIG. 20 is a functional block diagram showing the main configuration of the application-related processing unit 38 ′ included in the receiving device 3 ′ of the system 1 ′ according to the present embodiment. FIG. 21 is a diagram schematically illustrating details of the script tag 212 in the source of the HTML5 application executed by the receiving device 3 ′. 22 and 23 are diagrams for explaining examples of the data format of the captiondata referred to by the receiving device 3 '.

[System overview and configuration]
The system according to the present embodiment is different from Embodiments 1 to 3 in that the HTML application does not present the caption based on the Subtitle_info information, but presents the caption with reference to caption data including information regarding the presentation time of the caption. It is different from the system concerned.

  As shown in FIG. 1, the system 1 ′ includes a transmission device 2, a reception device 3 ′ (broadcast receiver), a content server 5, and a content server 6.

(Configuration of receiving device 3 ')
As illustrated in FIG. 1, the reception device 3 ′ includes a broadcast reception unit 31, an operation unit 32, a communication transmission / reception unit 33, a component demultiplexing unit 34, a video decoding unit 35, an audio decoding unit 36, a caption decoding unit 37, an application A related processing unit 38 ′, a display 39, a speaker 40, and a storage unit 41 are provided.

  The application related processing unit 38 ′ acquires SI information and an HTML application from the component demultiplexing unit 34. The application related processing unit 38 refers to the HTML application and specifies a component to be presented.

  The application-related processing unit 38 ′ acquires the video component, the audio component, and the caption component to be presented from the video decoding unit 35, the audio decoding unit 36, and the caption decoding unit 37, respectively, and the video component, the audio component, and the caption component are obtained. Present.

  Detailed processing of the application-related processing unit 38 'will be described later with reference to another drawing.

(Application-related processing unit 38 ')
The application related processing unit 38 ′ will be described with reference to FIG. As shown in FIG. 20, the application-related processing unit 38 ′ includes a middleware unit and a synthesis unit.

  The synthesis unit has a function of executing an HTML application.

  As shown in FIG. 20, the synthesizing unit that has executed the HTML application functions as a video / audio presentation processing unit 384 and a caption presentation processing unit 385 '.

  The caption presentation processing unit 385 'specifies a caption component to be presented with reference to the HTML application. The caption presentation processing unit 385 'acquires the caption component to be presented from the caption acquisition processing unit 383, and presents the acquired caption component.

  Specifically, as can be seen from FIG. 21, the synthesis unit registers the event listener addCaptionListener in the broadcast video / audio object at the start of the execution of the HTML application including the script tag 212 shown in FIG. 21 as a source. Thereby, when the caption acquisition processing unit 383 receives the caption stream of the program, the event registered by addCaptionListener is fired, and caption data obtained by converting the received caption stream is notified to the caption presentation processing unit 385 ′. The data format of the captiondata is as shown in FIG.

  That is, as shown in FIG. 22, captiondata is composed of the presentation start time, presentation period, ID, style element, subtitle text data, and subsample data (binary data) of subtitles and subsample data. Yes.

  The presentation start time information includes Subtitle_info information 131 acquired by the SI information acquisition processing unit 381, information extracted by the subtitle acquisition processing unit 383 from the MMTP packet of the subtitle component, and the subtitle acquisition processing unit 383 by the TTML document. The information is calculated from data calculated from data extracted from a file, but may be information calculated from any of the above data.

  The caption presentation processing unit 385 ′ that has acquired the caption data presents the caption and other subsample data by the presentation method specified by the caption data. That is, the subtitle text data and each sub-sample data are presented from the presentation start time designated by the caption data to the length of time designated by the caption data.

  In the present embodiment, the presentation start time and the length of the presentation period are sent as time information. However, the presentation start time and the presentation end time may be used as long as the information can control the presentation time of the caption. That's fine. In the present embodiment, the actual data of each caption data is included in the caption data and sent, but instead of the data, the storage location information in which the data is stored may be included and sent as a URL.

(About another example of captiondata)
The data format of captiondata is not limited to that shown in FIG. That is, the data format of captiondata may be as shown in FIG.

  That is, as shown in FIG. 23, the caption data may include the meta information of the presentation start time, the presentation period, the ID, and the style element for the caption and each subsample data.

  In the present embodiment, the presentation start time and the length of the presentation period are sent as time information. However, the presentation start time and the presentation end time may be used as long as the information can control the presentation time of the caption. That's fine. In the present embodiment, the actual data of each caption data is included in the caption data and sent, but instead of the data, the storage location information in which the data is stored may be included and sent as a URL.

(Advantages of the receiving device 3)
The receiving device 3 according to the present embodiment has the same effects as the receiving device 3 according to the first to third embodiments.

(Other supplementary notes)
In the example of FIG. 11 and FIG. 13, the synthesizing unit presents the Subtitle_info information as it is according to the description of the script.

  In this regard, the script shown in FIGS. 11 and 13 may include a function for converting the Subtitle_info information into words that can be understood by general consumers. And a synthetic | combination part may show the said wording according to the script in which such a function was incorporated.

  In the example of FIG. 17, the synthesizing unit presents the Subtitle_list information as it is according to the script description.

  In this regard, the script shown in FIGS. 11 and 13 may include a function for converting the Subtitle_list information into words that can be understood by general consumers. And a synthetic | combination part may show the said wording according to the script in which such a function was incorporated.

[Example of software implementation]
Control blocks of the receiving devices 3 and 3 ′ (particularly, the SI information acquisition processing unit 381, the application data acquisition processing unit 382, the caption acquisition processing unit 383, the video / audio presentation processing unit 384, and the caption presentation processing units 385 and 385 ′). May be realized by a logic circuit (hardware) formed in an integrated circuit (IC chip) or the like, or may be realized by software using a CPU (Central Processing Unit).

  In the latter case, the receiving devices 3 and 3 'are a CPU that executes instructions of a program that is software that realizes each function, and a ROM (Read Only) in which the program and various data are recorded so as to be readable by a computer (or CPU). Memory) or a storage device (these are referred to as “recording media”), a RAM (Random Access Memory) for expanding the program, and the like. And the objective of this invention is achieved when a computer (or CPU) reads the said program from the said recording medium and runs it. As the recording medium, a “non-temporary tangible medium” such as a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, or the like can be used. The program may be supplied to the computer via an arbitrary transmission medium (such as a communication network or a broadcast wave) that can transmit the program. The present invention can also be realized in the form of a data signal embedded in a carrier wave in which the program is embodied by electronic transmission.

[Summary]
The broadcast receiver (reception devices 3 and 3 ′) according to the first aspect of the present invention is a broadcast receiver in which a lower layer program (middleware) and an upper layer program (synthesizing unit) are operated. The subtitle presenting section (for example, the subtitle presenting processing section 385) that presents the subtitles of the program on the HTML application and meta information (for example, Subtitle_info information) indicating the subtitle presenting method is broadcasted. An acquisition processing unit (for example, an SI information acquisition processing unit 381) that is acquired from outside the receiver (transmitting device 2, 2 ′), and is implemented as a function of the lower layer program, The caption presentation unit acquires the meta information acquired by the acquisition processing unit, and presents the caption with reference to the meta information.

  According to said structure, if the said meta information is made into the content which the distributor (or provider of HTML application) of the said program desires, the said broadcast receiver will be the provider (or provider of HTML application). ) Has an effect that the upper layer program can present subtitles on the HTML application in the desired presentation method.

  In the broadcast receiver according to aspect 2 of the present invention, in the aspect 1, the caption presentation unit acquires the meta information acquired by the acquisition processing unit when a predetermined event is fired. Also good.

  The broadcast receiver according to aspect 3 of the present invention is the broadcast receiver according to aspect 1 or 2, wherein the caption presentation unit acquires the meta information acquired by the acquisition processing unit when the program is selected. May be.

  According to the above configuration, the broadcast receiver receives subtitles presented in the presentation method desired by the distributor (or HTML application provider) immediately after the user starts viewing the program. There is a further effect that can be seen.

  In the broadcast receiver according to aspect 4 of the present invention, in any of the aspects 1 to 3, the meta information (information included in caption data included in the caption stream) acquired by the acquisition processing unit is TTML. In addition to information for obtaining document subsample data (file name of TTML document), information for obtaining image subsample data (file name of image), information for obtaining audio subsample data (Sound file name) and information for acquiring sub-sample data of external character font (external character font file name) may be included in whole or in part.

  According to said structure, the said broadcast receiver has the further effect that the upper layer program can show a subtitle using an image, an audio | voice, and / or an external character font.

  The broadcast receiver according to aspect 5 of the present invention is the broadcast receiver according to any one of the aspects 1 to 4, wherein the caption presentation unit has a language specified by a user among a plurality of different languages as the caption of the program. Subtitles are presented, and the acquisition processing unit is configured to obtain a list (Subtitle_list information) of the plurality of languages from the outside of the broadcast receiver. The above list may be presented together with subtitles in the language specified in.

  According to said structure, the said broadcast receiver has the further effect that the said user can confirm the list | wrist of the several language which the said user can designate as a language of a subtitles through the upper layer program. .

  In the broadcast receiver according to aspect 6 of the present invention, in the aspect 1, the meta information acquired by the acquisition processing unit may be information related to the caption presentation time (for example, reference_start_time).

  According to said structure, the said broadcast receiver has the further effect that the upper layer program can show a subtitle at the timing which the said distributor (or provider of an HTML application) desires.

  The subtitle presentation method according to aspect 7 of the present invention is a subtitle presentation method for a broadcast receiver in which a lower layer program and an upper layer program operate, and the upper layer program presents a program subtitle on an HTML application. A subtitle presenting step, and an acquisition step in which the lower layer program obtains meta information indicating the subtitle presenting method from outside the broadcast receiver. The acquired meta information may be acquired, and the subtitles may be presented with reference to the meta information.

  According to said structure, the caption presentation method which concerns on the said aspect 7 has an effect similar to the broadcast receiver which concerns on the said aspect 1. FIG.

  The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope shown in the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments. Is also included in the technical scope of the present invention. Furthermore, a new technical feature can be formed by combining the technical means disclosed in each embodiment.

DESCRIPTION OF SYMBOLS 1 System 2 Transmission apparatus 3, 3 'Reception apparatus 5, 6 Content server 34 Component demultiplexing part 35 Video decoding part 36 Audio decoding part 37 Subtitle decoding part 38 Application related process part 38' Application related process part 381 SI information acquisition process Part (acquisition processing part)
383 caption acquisition processing unit (acquisition processing unit)
385 Subtitle presentation processing unit (subtitle presentation unit)

Claims (7)

In a broadcast receiver in which a lower layer program and an upper layer program operate,
A subtitle presenting section that is implemented as a function of the upper layer program and presents a subtitle of a program on an HTML application;
An acquisition processing unit that acquires meta information indicating the subtitle presentation method from the outside of the broadcast receiver, the acquisition processing unit being realized as a function of the lower layer program,
The subtitle presenting section acquires the meta information acquired by the acquisition processing section, and presents the subtitle with reference to the meta information.   The broadcast receiver according to claim 1, wherein the caption presentation unit acquires the meta information acquired by the acquisition processing unit when a predetermined event is fired.   The broadcast receiver according to claim 1, wherein the subtitle presenting unit acquires the meta information acquired by the acquisition processing unit when the program is selected.   The meta information acquired by the acquisition processing unit is information for acquiring sub-sample data of an image, information for acquiring sub-sample data of audio, in addition to information for acquiring sub-sample data of a TTML document 4. The broadcast receiver according to claim 1, wherein the broadcast receiver includes all or a part of information for acquiring sub-sample data of an external character font. 5. The subtitle presenting unit is configured to present subtitles in a language specified to the user among a plurality of different languages as subtitles of the program,
The acquisition processing unit is configured to acquire the list of the plurality of languages from outside the broadcast receiver,
The broadcast receiver according to any one of claims 1 to 4, wherein the subtitle presenting section presents the list together with subtitles in a language designated by the user.   The broadcast receiver according to claim 1, wherein the meta information acquired by the acquisition processing unit is information regarding a presentation time of the caption. In a subtitle presentation method of a broadcast receiver in which a lower layer program and an upper layer program operate,
A subtitle presenting step in which the upper layer program presents a subtitle of a program on an HTML application;
An acquisition step in which the lower-layer program acquires meta-information indicating the subtitle presentation method from the outside of the broadcast receiver;
The subtitle presenting method characterized in that, in the subtitle presenting step, the meta information obtained in the obtaining step is obtained, and the subtitle is presented with reference to the meta information.

Images