Broadcast receiver and method for operating the broadcast receiver

Abstract

To excellently transmit content data acquired from broadcasting from a broadcasting receiver to an information processing device connected thereto.SOLUTION: This broadcasting receiver includes: an interface connectable to an information processing device; and a controller configured so as to acquire content data included in a broadcast stream and a first command regarding the content data, transfer the first command to the information processing device, and respond the content data to the information processing device in response to a request from the information processing device.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present technology relates to a broadcast receiver for receiving terrestrial digital television broadcasts and How a broadcast receiver works Regarding. [Background technology]

[0002] A mechanism is gaining attention in which applications on information processing devices such as smartphones and tablet terminals work in conjunction with broadcast programs received by broadcast receivers such as TV sets. For example, while receiving a sports program on a TV set, the information processing device presents information about the athletes participating in the sports program and the flow of the game, allowing the user to enjoy the program while using the information processing device as a second screen.

[0003] Patent Document 1 discloses a system 1 that displays, on a tablet computer, as examples of program-related information, a program guide (EPG) and guidance corresponding to a program currently being broadcast on a currently selected channel. In this system 1, the tablet computer is configured to display information by acquiring detailed information about a program currently being displayed on a video device from a metadata server. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2013-225897 A (paragraph 0024) Summary of the Invention [Problem to be solved by the invention]

[0005] Currently, a model is being considered in which applications within a broadcast receiver operate in conjunction with the broadcast, and various content data obtained from the broadcast is transmitted to applications in information processing devices such as smartphones and tablet terminals. However, there are still many issues that need to be resolved before such a model can be realized.

[0006] In view of the above circumstances, an object of the present technology is to provide a broadcast receiver, a broadcast receiving method, an information processing device, an information processing method, a broadcast device, and a broadcast method that are capable of effectively transmitting content data obtained from a broadcast from a broadcast receiver to an information processing device connected thereto. [Means for solving the problem]

[0007] In order to solve the above problems, a broadcast receiver according to one embodiment of the present technology includes an interface capable of being connected to an information processing device, and a first controller that acquires content data transmitted by a DDB message, acquires a first command transmitted by an event message for causing the information processing device connected via the interface to acquire the acquired content data, and transfers the first command to the information processing device.

[0008] The above-mentioned broadcast receiver may further include a storage for saving the acquired content data, and the first controller may be configured to respond to an acquisition request from the connected information processing device by sending the content data saved in the storage to the information processing device.

[0009] The first controller may be configured, when acquiring a second command transmitted from the event message, to set the content data standby operation mode in which the first command is generated and transferred to the information processing device each time content data transmitted by the DDB message is acquired.

[0010] The first controller may be configured to cancel the content data standby operation mode when the content data standby operation mode is set and a third command transmitted by the event message is acquired.

[0011] The first controller may be configured, when acquiring a fourth command transmitted from the event message for transmitting a message to the information processing device, to transfer the fourth command to the information processing device.

[0012] The first controller may be configured, when it acquires a fifth command transmitted from the event message and instructing the information processing device to access data on a network, to transfer the fifth command to the information processing device.

[0013] In the above-mentioned broadcast receiver, the first command includes information on a method for designating a time at which the controller transfers the first command to the information processing device, The first controller may be configured to determine a time to forward the first command based on the information.

[0014] In another aspect of the present technology, a broadcast receiving method includes a first controller acquiring content data transmitted by a DDB message, acquiring a first command transmitted by an event message for causing an information processing device connected via an interface to acquire the acquired content data, and transferring the first command to the information processing device.

[0015] An information processing device of another form related to the present technology includes an interface connectable to a broadcast receiver that acquires content data transmitted by a DDB message, acquires a first command transmitted by an event message for causing the information processing device to acquire the acquired content data, and transfers the first command to the information processing device, and a second controller that acquires, via the interface, the content data acquired by the broadcast receiver in response to the first command transferred from the broadcast receiver.

[0016] The second controller may be configured to launch an application capable of processing the acquired content data in response to the first command transferred from the broadcast receiver.

[0017] In an information processing method according to another aspect of the present technology, a second controller acquires content data transmitted by a DDB message, acquires a first command transmitted by an event message from a broadcast receiver for causing an information processing device to acquire the acquired content data, and transfers the first command to the information processing device, and in response to the first command, acquires the content data acquired by the broadcast receiver via the interface.

[0018] A broadcasting device according to another aspect of the present technology includes a data broadcasting unit that transmits content data by a DDB message and transmits a first command by an event message for causing an information processing device connected to the broadcast receiver via an interface to acquire the content data.

[0019] In another aspect of the broadcasting method according to the present technology, a data broadcasting unit transmits content data by a DDB message, and transmits a first command by an event message for causing an information processing device connected to the broadcast receiver via an interface to acquire the content data. Effect of the Invention

[0020] As described above, according to the present technology, content data acquired from a broadcast can be successfully transmitted from a broadcast receiver to an information processing device connected thereto. [Brief description of the drawings]

[0021] [Figure 1] 1 is a diagram showing an overall configuration of a system 1 according to a first embodiment of the present technology. [Diagram 2] 2 is a diagram showing a configuration relating to the exchange of content data and commands between a broadcast station 10, a broadcast receiver 20, and an external device 30 in the system 1 of FIG. [Diagram 3] 2 is a diagram showing a hardware configuration of a broadcast receiver 20 in the system of FIG. [Figure 4] 2 is a diagram showing a hardware configuration of an external device 30 in the system of FIG. 1. [Diagram 5] FIG. 13 is a diagram for explaining an operation using the Receive & Launch App (first command). [Figure 6] FIG. 13 is a diagram for explaining the operation using Set Receive & Launch App (second command) and Reset Receive & Launch App (third command). [Figure 7] FIG. 11 is a diagram for explaining an operation using Receive & Store Content (first command). [Figure 8] FIG. 13 is a diagram for explaining operations using Set Receive & Store Content (second command) and Reset Receive & Store Content (third command). [Figure 9] FIG. 13 is a diagram for explaining an operation using Send Message (fourth command). [Figure 10] This is a diagram explaining the operation using Launch App (fifth command). [Figure 11]FIG. 2 is a diagram showing the data structure of DII. [Figure 12] FIG. 13 is a diagram showing the data structure of a content descriptor. [Figure 13] FIG. 13 is a diagram showing the structure of an InfoDescriptor. [Figure 14] A diagram showing the data structure of a DSM-CC section that transmits stream descriptors. [Figure 15] FIG. 13 is a diagram showing the data structure of a general-purpose event message descriptor. [Figure 16] FIG. 13 is a diagram illustrating an example of the format of a command stored in private_data_byte. [Figure 17] FIG. 4 is a diagram showing the relationship between command codes, commands, and arguments. [Figure 18] FIG. 13 is a diagram showing an example of content description information written in JSON. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] Hereinafter, embodiments of the present technology will be described with reference to the drawings. <First embodiment> [Overall configuration of System 1] FIG. 1 is a diagram showing an overall configuration of a system 1 according to a first embodiment of the present technology.

[0023] The system 1 includes a broadcast station (broadcast device) 10, a broadcast receiver 20, an external device (information processing device) 30, and an external server 40.

[0024] The broadcast station 10 performs carousel transmission of terrestrial digital television broadcasting and data broadcasting. In this technology, the transmission of content data and commands transmitted from the broadcast receiver 20 to the external device 30 is assumed as the subject of carousel transmission. That is, the broadcast station 10 has a data broadcast unit 11 that transmits content data by DDB message, operates the broadcast receiver 20 and the external device 30 so as to transmit the content data from the broadcast receiver 20 to the external device 30 through an interface, and transmits commands by event messages to operate the external device 30 so as to cause the external device 30 to acquire the content data from the broadcast receiver 20. Assumed content data transmitted from the data broadcast unit 11 of the broadcast station 10 by the DDB message of the data carousel are, for example, application data, music data, image (video) data, message data, game data, and the like, which are based on HTML5 documents.

[0025] The broadcast receiver 20 has a data broadcast receiving unit 21 that receives terrestrial digital television broadcasts and data broadcast services, and a resident function unit 22 that is an application that transmits and communicates data between the data broadcast receiving unit 21 and a native application 31 of an external device 30. The resident function unit 22 transmits, for example, content data and commands acquired from a data carousel by the data broadcast receiving unit 21 to the native application 31 running on the external device 30 connected to the broadcast receiver 20. The broadcast receiver 20 may be in any specific product form, such as a television device or a set-top box.

[0026] For example, wireless communication such as WiFi (registered trademark) is used for the connection between the broadcast receiver 20 and the external device 30. Note that the connection between the broadcast receiver 20 and the external device 30 is not limited to a wireless connection, and may be a wired connection.

[0027] The external device 30 is, for example, an information processing device such as a smartphone or a tablet terminal. The external device 30 downloads a native application from an external server 40 in accordance with an instruction from a user, installs the application, and uses it. The native application 31 installed in the external device 30 communicates with the resident function unit 22 of the broadcast receiver 20 to exchange content data and commands.

[0028] The native application 31 is an application that runs on the platform of the external device 30. Application data, music data, image (video) data, and messages in HTML5 documents are processed by functions (e.g., an application unit such as an HTML browser 32) built into the native application 31.

[0029] The external server 40 is a server capable of distributing various data such as the native application 31 and data related to content data transmitted by broadcasting in response to a request from the external device 30.

[0030] Next, the basic operation of this system 1 will be described with reference to FIGS. 2 is a diagram showing a configuration related to the exchange of content data and commands between the broadcast station 10, the broadcast receiver 20, and the external device 30 in the system 1. As shown in FIG.

[0031] 1. First, the external device 30 accesses the external server 40 in accordance with an instruction from the user, and downloads the native application 31 selected by the user. The external device 30 installs the downloaded native application 31.

[0032] Here, the native application 31 has various application functions, such as an HTML browser 32 capable of processing application data made up of an HTML5 document, and an AV player capable of playing AV data.

[0033] 2. When the native application 31 is started, it first starts searching for the external device 30 via wireless communication such as WiFi (registered trademark). When the broadcast receiver 20 is discovered by the native application 31, the user selects the broadcast receiver 20 as a connection partner. Upon receiving this selection from the user, the native application 31 requests the broadcast receiver 20 to connect.

[0034] 3. The resident function unit 22 of the broadcast receiver 20 authenticates the native application 31 that has requested a connection. If the resident function unit 22 confirms that the native application 31 is valid (that is, that a connection to the resident function unit 22 should be permitted), it permits a connection to the native application 31. This brings the native application 31 of the external device 30 and the resident function unit 22 of the broadcast receiver 20 into a connected state in which they can communicate with each other.

[0035] 4. The data broadcast receiving unit 21 of the broadcast receiver 20 receives the content data and commands transmitted by the data carousel. The content data is transmitted by a DDB (DownloadDataBlock) message of the data carousel, and the commands are transmitted by an event message of the data carousel. The content data and commands received by the data broadcast receiving unit 21 are provided to the resident function unit 22.

[0036] 2, the resident function unit 22 of the broadcast receiver 20 has a command acquisition unit 212 and a content data acquisition unit 222. The command acquisition unit 212 performs processes such as transferring a command provided by the data broadcast receiving unit 21 to a native application 31 running on the external device 30 using the external device interface 213. The content data acquisition unit 222 performs processes such as saving the content data provided by the data broadcast receiving unit 21 in the file server 23.

[0037] 6. The native application 31 of the external device 30 accesses the file server 23 based on the received command and obtains the target content data from the file server 23. For example, if the content data is application data based on an HTML5 document, the native application 31 of the external device 30 starts an HTML browser built into the native application 31 and passes the application data to the HTML browser. As a result, the application data is processed by the HTML browser.

[0038] 7. In addition, the native application 31 of the external device 30 can appropriately request the resident function unit 22 of the broadcast receiver 20 to obtain data such as an electronic program guide delivered by data broadcasting, or give instructions such as changing channels.

[0039] The above is a description of the basic operation of the system 1 according to the first embodiment of the present technology.

[0040] [Hardware configuration of broadcast receiver 20] Next, the hardware configuration of the broadcast receiver 20 will be described. FIG. 3 is a diagram showing the hardware configuration of the broadcast receiver 20. As shown in FIG.

[0041] The broadcast receiver 20 includes a CPU (Central Processing Unit) 201, a RAM (Random Access Memory) 202, a ROM (read only memory) 203, a remote control I / O 204, a communication interface 205, a tuner 206, a demodulation unit 207, a TS decoder 208, an audio decoder 209, a video decoder 210, a presentation processing unit 211, a system bus 212, an external device interface 213, and a storage 214. A display unit 220 and an audio output unit 230 are connected to the broadcast receiver 20.

[0042] The CPU 201 (first controller) controls the entire broadcast receiver 20 and performs calculations for executing programs.

[0043] The RAM 202 is a randomly accessible memory that stores various programs and data that are interpreted and executed by the CPU 201.

[0044] The ROM 203 is a non-volatile memory in which various data used in the broadcast receiver 20, such as fonts, is fixedly stored.

[0045] A remote control I / O 204 inputs and outputs infrared signals and wireless signals to and from a remote controller (remote control) 240 .

[0046] The communication interface 205 handles communication with a network 50 such as the Internet and a local area network.

[0047] The tuner 206 receives terrestrial digital television broadcasts and data broadcast services selected by the user.

[0048] The demodulation unit 207 demodulates the terrestrial digital television broadcast and data broadcast service received by the tuner 206 to restore a TS (transport stream).

[0049] The TS decoder 208 separates the TS into audio streams, video streams, DDB messages, event messages, and the like by sorting the TS by elementary stream.

[0050] The audio decoder 209 decodes the audio stream separated by the TS decoder 208, and outputs the audio signal to a speaker unit 230 having an amplifier and a speaker.

[0051] The video decoder 210 decodes the video stream separated by the TS decoder 208 and supplies the decoded video stream to a presentation processing unit 211 .

[0052] In addition, the DDB message and the event message separated by the TS decoder 208 are supplied to the CPU 201. The CPU 201 operates as the data broadcast receiving unit 21 and the resident function unit 22 shown in Fig. 1. The data broadcast receiving unit 21 extracts each module divided into fixed-length block units and transmitted by the DDB message, and supplies it to the resident function unit 22 as content data. In addition, the CPU 201 acquires a command transmitted by an event message, and supplies it to the resident function unit 22.

[0053] The presentation processing unit 211 synthesizes the video signal from the video decoder 210 with the graphics images, characters, and the like generated by the CPU 201 , generates data to be presented on the screen of the display unit 220 , and outputs the data to the display unit 220 .

[0054] The external device interface 213 (interface) is an interface for connection with the external device 30. The external device interface 213 may be a wireless connection such as WiFi (registered trademark) or a wireless LAN (Local Area Network), or may be a wired connection such as Ethernet (registered trademark) or a USB (Universal Serial Bus).

[0055] The storage 214 is a data storage unit that stores content data acquired from a data broadcasting service, etc. The storage 214 may be any non-volatile storage device, such as a flash memory or a hard disk drive.

[0056] [Hardware configuration of external device 30] Next, the hardware configuration of the external device 30 will be described. The external device 30 is used as a secondary monitor for the broadcast receiver 20, and therefore may be an information processing device of a portable size. FIG. 4 is a diagram showing a hardware configuration of the external device 30. As shown in FIG.

[0057] The external device 30 is composed of a CPU 301, a RAM (main memory) 302, a ROM 303, a communication interface 305, an external device interface 306, a storage 307, a system bus 308, an input operation unit 309, an audio signal processing unit 310, a display control unit 311, a display unit 320, an audio output unit 330, etc.

[0058] The CPU 301 (second controller) performs overall control of the external device 30 and performs arithmetic processing for executing programs.

[0059] The RAM 302 is a randomly accessible memory that stores various programs and data that are interpreted and executed by the CPU 301.

[0060] The ROM 303 is a non-volatile memory in which various data used in the external device 30, such as fonts, is fixedly stored.

[0061] The communication interface 305 handles communication with a network 50 such as the Internet and a local area network.

[0062] The external device interface 306 (interface) is an interface for connection with the broadcast receiver 20. The external device interface 213 may be a wireless connection such as WiFi (registered trademark) or a wireless LAN (Local Area Network), or may be a wired connection such as Ethernet (registered trademark) or a USB (Universal Serial Bus).

[0063] The storage 307 stores various data such as content data transmitted from the broadcast receiver 20, various programs executed by the CPU 301, and the like.

[0064] The input operation unit 309 accepts various instructions and data input from a user. The input operation unit 309 may be configured using, for example, a touch sensor panel. Alternatively, the input operation unit 309 may be configured using mechanical keys.

[0065] The audio signal processing unit 310 generates an audio signal from the audio data and supplies it to an audio output unit 330 that has an amplifier and a speaker.

[0066] A display control unit 311 generates a display signal from the image data and supplies it to a display unit 320 having a display screen.

[0067] [About commands] Next, commands transmitted by event messages from broadcast stations in this system 1 will be described.

[0068] The commands include, for example: Receive & Launch App Set Receive & Launch App Reset Receive & Launch App Receive & Store Content Set Receive & Store Content ·Reset Receive & Store Content Send Message Launch App etc.

[0069] The contents of each command will be explained in the following operation examples.

[0070] [System 1 operation example] Next, some operation examples using the above commands in the system 1 of this embodiment will be described.

[0071] (Operation using Receive & Launch App) FIG. 5 is a diagram for explaining the operation using the Receive & Launch App (first command). In terms of the broadcasting order, the content data is transmitted by a DDB message, and then the Receive & Launch App for the content data is transmitted by an event message. The content data is assumed to be application data.

[0072] Next, we will explain how to use this Receive & Launch App. First, the application data (App) transmitted in the DDB message is acquired by the content data acquisition unit 222 in the resident function unit 22 of the broadcast receiver 20. The content data acquisition unit 222 stores the acquired application data (App) in the file server 23 in the broadcast receiver 20.

[0073] After that, the Receive & Launch App is transmitted by an event message from the broadcast station 10. Upon acquiring this Receive & Launch App, the command acquisition unit 221 of the broadcast receiver 20 immediately transfers this Receive & Launch App to the native application 31 running in the CPU 301 of the external device 30 via the external device interface 213.

[0074] When the native application 31 of the external device 30 receives the Receive & Launch App, it executes this command. That is, the native application 31 accesses the file server 23 of the broadcast receiver 20 via the external device interface 306, and obtains the target application data from the file server 23.

[0075] To explain the operation when acquiring the target application data in more detail, the Receive & Launch App stores the content ID of the target content data as an argument for identifying the target content data. The native application 31 transmits a file request with the content ID as an argument to the file server 23 of the broadcast receiver 20 via the external device interface 306. In response to the file request, the file server 23 of the broadcast receiver 20 returns the target application data to the native application 31 of the external device 30. In this way, the native application 31 of the external device 30 acquires the content data transmitted from the broadcast station 10.

[0076] Next, the native application 31 starts the HTML browser 32 based on the Receive & Launch App, and passes the target application data to the HTML browser 32. As a result, the application is executed in the HTML browser 32 based on the application data.

[0077] As described above, in this operation example, the content data (application data) is transmitted by a DDB message and stored in the file server 23 of the broadcast receiver 20. Meanwhile, a command (Receive & Launch App) that triggers the external device 30 to acquire and process the content data stored in the file server 23 is transmitted by an event message that is easy to synchronize with time, and is immediately transferred to the native application 31 of the external device 30 after the broadcast receiver 20 receives it. The native application 31 of the external device 30 accesses the file server 23 of the broadcast receiver 20 in accordance with this command to acquire the target content data, and starts a function corresponding to this content data to start processing the content data. Therefore, the processing of the content data in the external device 30 can be started at a timing determined by the broadcast station 10.

[0078] (Operation using Set Receive & Launch App and Reset Receive & Launch App) FIG. 6 is a diagram explaining the operation using Set Receive & Launch App (second command) and Reset Receive & Launch App (third command).

[0079] In terms of the broadcasting order, first, Set Receive & Launch App is transmitted by an event message, and then, before Reset Receive & Launch App is transmitted by an event message, content data is transmitted from the broadcasting station 10 by a DDB message at least once. In this operation example, the content data is also application data.

[0080] Next, we will explain how to use the Set Receive & Launch App and Reset Receive & Launch App.

[0081] First, a Set Receive & Launch App is transmitted by an event message from the broadcast station 10. When the command acquisition unit 221 of the broadcast receiver 20 acquires this Set Receive & Launch App, it goes into a content data standby operation mode as described below until a Reset Receive & Launch App is acquired.

[0082] When application data (App1) is transmitted from the broadcast station 10 by a DDB message, the content data acquisition unit 222 of the broadcast receiver 20 acquires this application data (App1) and stores it in the file server 23.

[0083] Next, the file server 23 of the broadcast receiver 20 notifies the command acquisition unit 221 of the completion of saving the application data (App1). Upon receiving this notification, the command acquisition unit 221 generates a Receive & Launch App and transmits this Receive & Launch App to the native application 31 running in the external device 30 via the external device interface 213.

[0084] When the native application 31 of the external device 30 receives the Receive & Launch App, it executes the Receive & Launch App. That is, the native application 31 accesses the file server 23 of the broadcast receiver 20 via the external device interface 306, and acquires the target application data (App1) from the file server 23.

[0085] Next, the native application 31 starts the HTML browser 32 and passes the target application data (App1) to the HTML browser 32. As a result, the application is executed in the HTML browser 32 based on the application data (App1).

[0086] Thereafter, when the next application data (App2) is transmitted by the DDB message, the command acquisition unit 221 of the broadcast receiver 20 acquires it and stores this application data (App2) in the file server 23 in the same manner as described above. The subsequent operations are also the same as those for the application data (App1). That is, the file server 23 notifies the command acquisition unit 221 that the application data (App2) has been saved. Upon receiving this notification, the command acquisition unit 221 generates a Receive & Launch App and transmits it to the native application 31 running in the external device 30 via the external device interface 213.

[0087] The native application 31 of the external device 30 accesses the file server of the broadcast receiver 20 via the external device interface 306 in accordance with the Receive & Launch App, and acquires the target application data (App2) from the file server .

[0088] Next, the native application 31 provides the target application data (App2) to the HTML browser 32 based on the Receive & Launch App. At this time, if the HTML browser 32 is stopped, it is started, and the application data (App2) is provided to the started HTML browser 32. As a result, the application based on the application data (App2) is executed in the HTML browser 32.

[0089] When Reset Receive & Launch App is transmitted from the broadcasting station 10 via an event message and the command acquisition unit 221 of the broadcasting receiver 20 acquires this, the content data standby operation mode ends and the operating state returns to the state before Set Receive & Launch App was acquired, for example, the standby operation mode for a command such as Receive & Launch App transmitted via an event message.

[0090] In the above operation, the resident function unit 22 of the broadcast receiver 20 operates in the above content data standby operation mode from when the broadcast receiver 20 receives the Set Receive & Launch App command until when the broadcast receiver 20 receives the Reset Receive & Launch App command. This allows an operation in which the application executed in the native application 31 of the external device 30 is switched at the timing when the content data is transmitted by the DDB message.

[0091] Furthermore, in the above operation, no matter how many times the content data provided to the external device 30 is switched, the commands that need to be transmitted from the broadcast station 10 by event messages are limited to two in total: Set Receive & Launch App and Reset Receive & Launch App. Therefore, the operational cost of transmitting commands by event messages on the broadcast station 10 side can be reduced.

[0092] (Operation using Receive & Store Content) FIG. 7 is a diagram for explaining an operation using Receive & Store Content (first command). Up to this point, the case where application data is transmitted by a DDB message has been described. Here, the case where AV data such as music data and image (video) data is transmitted as content data by a DDB message will be described.

[0093] In terms of the broadcasting order, first, AV data such as music data and image (video) data is transmitted by a DDB message, and then Receive & Store Content related to that AV data is transmitted by an event message.

[0094] Next, we will explain how to use Receive & Store Content.

[0095] First, AV data (AV) such as music data and image (video) data is transmitted by a DDB message from the broadcast station 10. When the content data acquisition unit 222 of the broadcast receiver 20 acquires this AV data (AV), it stores this AV data (AV) in the file server 23.

[0096] After that, the Receive & Store Content is transmitted by an event message from the broadcast station 10. When the command acquisition unit 221 of the broadcast receiver 20 acquires this Receive & Store Content, it transfers this Receive & Store Content to the native application 31 running in the external device 30 via the external device interface 213.

[0097] When the native application 31 of the external device 30 acquires the Receive & Store Content, it executes this command. That is, the native application 31 accesses the file server 23 of the broadcast receiver 20 via the external device interface 306, and acquires the target AV data (AV) from the file server 23.

[0098] The native application 31 stores the acquired content data in the storage 307 of the external device 30. The AV data (AV) stored in the storage 307 of the external device 30 in this manner is played back using an application such as an AV player capable of processing the AV data (AV) at any timing designated by the user.

[0099] (Operations using Set Receive & Store Content and Reset Receive & Store Content) FIG. 8 is a diagram for explaining the operation using Set Receive & Store Content (second command) and Reset Receive & Store Content (third command).

[0100] The broadcast sequence is as follows: first, Set Receive & Store Content is transmitted by an event message, and then AV data (AV1) such as music data and image (video) data is transmitted at least once by a DDB message before Reset Receive & Store Content is transmitted by an event message.

[0101] Next, we will explain how to use Set Receive & Store Content and Reset Receive & Store Content.

[0102] First, Set Receive & Store Content is transmitted by an event message from the broadcast station 10. When the command acquisition unit 221 of the broadcast receiver 20 acquires this Set Receive & Store Content, it goes into a content data standby operation mode as described below until the next Reset Receive & Store Content is acquired.

[0103] When AV data (AV1) is transmitted from the broadcast station 10 by a DDB message, the command acquisition unit 221 of the broadcast receiver 20 acquires this AV data (AV1) and stores it in the file server 23.

[0104] Next, the file server 23 of the broadcast receiver 20 notifies the command acquisition unit 221 of the completion of saving the AV data (AV1). Upon receiving this notification, the command acquisition unit 221 generates Receive & Store Content and transfers this Receive & Store Content to the native application 31 running in the external device 30 via the external device interface 213.

[0105] When the native application 31 of the external device 30 acquires the Receive & Store Content, it accesses the file server 23 of the broadcast receiver 20 via the external device interface 306, acquires the target AV data (AV1) from the file server 23, and stores it in the storage 307 in the external device 30.

[0106] Thereafter, when the next AV data (AV2) is transmitted by the DDB message, the command acquisition unit 221 of the broadcast receiver 20 acquires it and stores this AV data (AV2) in the file server 23 in the same manner as described above. The subsequent operations are also the same as in the case of the AV data (AV1). That is, the file server 23 notifies the command acquisition unit 221 that the storage of the AV data (AV2) has been completed. Upon receiving this notification, the command acquisition unit 221 generates Receive & Store Content and transfers it to the native application 31 running in the external device 30 via the external device interface 213.

[0107] The native application 31 of the external device 30 accesses the file server 23 of the broadcast receiver 20 through the external device interface 306 in accordance with Receive & Store Content, acquires the target AV data (AV2) from the file server 23, and stores it in the storage 307. The AV data (AV1, AV2) thus stored in the storage 307 of the external device 30 is played back at any timing designated by the user using an application such as an AV player capable of processing the AV data (AV1, AV2).

[0108] When the broadcast station 10 broadcasts Reset Receive & Store Content via an event message and the command acquisition unit 221 of the broadcast receiver 20 acquires this, the content data standby operation mode ends and the operation state returns to the state before acquiring Set Receive & Store Content, for example, the standby operation mode for a command such as Receive & Store Content transmitted via an event message.

[0109] In the above operation, the resident function unit 22 of the broadcast receiver 20 operates in the above content data standby operation mode from when the broadcast receiver 20 receives the Set Receive & Store Content command until when it receives the Reset Receive & Store Content command. As a result, no matter how many times AV data such as music data and image (video) data to be transmitted to the external device 30 is switched, the commands that need to be transmitted from the broadcast station 10 by event messages are limited to two in total: Set Receive & Launch App and Reset Receive & Launch App. Therefore, the operating costs of transmitting commands by event messages on the broadcast station 10 side can be reduced.

[0110] (Actions using Send Message) FIG. 9 is a diagram for explaining an operation using Send Message (fourth command).

[0111] This operation is an operation for transferring a Send Message transmitted by an event message from the broadcast station 10 from the broadcast receiver 20 to the external device 30. Send Message is a command in which the message body in text format is stored as content data as an argument.

[0112] Next, we will explain how to use this Send Message. First, a Send Message is transmitted by an event message from the broadcast station 10. Upon receiving this Send Message, the command acquisition unit 221 of the broadcast receiver 20 transfers this Send Message to the native application 31 of the external device 30 via the external device interface 213.

[0113] When the native application 31 of the external device 30 receives the Send Message transferred from the command acquisition unit 221 of the broadcast receiver 20, it performs a specific operation, such as presenting the body of the message, in response to the Send Message.

[0114] (Operation using Launch App) FIG. 10 is a diagram for explaining the operation using Launch App (fifth command).

[0115] This operation is an operation of transferring the Launch App broadcast by the broadcast station 10 in an event message from the broadcast receiver 20 to the external device 30. A URL (Uniform Resource Locator) indicating the access destination of the data is added as an argument to the Launch App.

[0116] Next, we will explain how to use this Launch App. A launch app is transmitted by an event message from the broadcast station 10. When the command acquisition unit 221 of the broadcast receiver 20 acquires this launch app, it transfers this launch app to the native application 31 of the external device 30 via the external device interface 213.

[0117] When the native application 31 of the external device 30 acquires the Launch App transferred from the command acquisition unit 221 of the broadcast receiver 20, it accesses the external server 40 using the communication interface 305 based on the URL stored as an argument of the Launch App, and downloads the target data.

[0118] [Content Descriptor] Next, we will explain the content descriptor that is stored and transmitted in the DII (Download Info Indication) of the data carousel as information necessary for transmitting content data such as application data, AV data, and messages transmitted from the broadcast station 10 in a data carousel from the broadcast receiver 20 to an external device 30.

[0119] FIG. 11 is a diagram showing the data structure of the DII. The data structure of this DII is an excerpt from the standard, ARIB STD-B24, 5.1, Data Broadcasting Coding and Transmission Methods for Digital Broadcasting. The meaning of each descriptor is described in the above standard.

[0120] In the data structure of this DII, the above content descriptor can be stored in moduleInfoByte as information about modules, which are units into which data is divided.

[0121] FIG. 12 is a diagram showing the data structure of the content descriptor.

[0122] The descriptor_tag is 8-bit data indicating the descriptor type, and here, a tag value indicating the content descriptor is described.

[0123] The "descriptor_length" is 8-bit data indicating the length (size) of the content descriptor. This data indicates the number of subsequent bytes as the length of the content descriptor.

[0124] The content_category is 8-bit data that indicates the category of the content data. The categories include application, music, image (video), game, message, etc.

[0125] The content_id_length is 8-bit data indicating the length (size) of the content ID.

[0126] The content_id_byte is 8-bit data indicating a content ID. A content ID having a length ranging from 0 to the length indicated by the content_id_length can be described in the content_id_byte.

[0127] content_name_flag is a flag that is set if the content has a name.

[0128] bc_metadata_flag is a flag that is set when related data of content data is transmitted in a data carousel.

[0129] bb_metadata_flag is a flag that is set when data related to the content data can be acquired from the external server 40 .

[0130] The module_link_flag is a flag that is set when content data is transmitted through a plurality of modules.

[0131] Reserved are 4 bits reserved for flags.

[0132] content_name_length and content_name_byte are written when content_name_flag is set. content_name_length is 8-bit data indicating the length of the content name. content_name_byte is 8-bit data indicating the content name. In content_name_byte, a name of any length ranging from 0 to the length indicated in content_name_length can be written.

[0133] The component_tag and metadata_module_id are written when the bc_metadata_flag is set. The component_tag is data that specifies the component stream in which the carousel is transmitted. The metadata_module_id is the module ID of the module in which the related data of the content data is stored. In this way, the related data is specified by the combination of the component_tag and the metadata_module_id.

[0134] The metadata_url_length and metadata_url_byte are written when bb_metadata_flag is set. The metadata_url_length is data indicating the length of the URL where the related data of the content data is stored. The metadata_url_byte is the data of that URL. For this metadata_url_byte, one URL can be written using multiple 8-bit metadata_url_bytes so that it can correspond to URLs with lengths ranging from 0 to the length indicated by metadata_url_length.

[0135] The number_of_module and rough_content_size are described when the module_link_flag is set. The number_of_module is data indicating the number of modules when the content data is transmitted by a plurality of modules. The rough_content_size is data indicating the size of the content data.

[0136] The command acquisition unit 221 of the broadcast receiver 20 receives data transmitted in module units by the DDB (Download Data Block) message of the data carousel based on the information stored in the received DII message. At this time, if the above content descriptor is stored in the moduleInfoByte of the DII message, the command acquisition unit 221 reads this content descriptor, recognizes what content data is transmitted by which module of which data carousel, and receives the content data. At this time, if the category of the content data is application, AV data, etc., preparations are made to store the content data in the file server 23 of the broadcast receiver 20 based on the rough_content_size described in the content descriptor.

[0137] [Other ways to write content descriptors] In the data structure of DII, the moduleInfoByte can store a descriptor (InfoDescriptor) of information about a module, which is a unit into which data is divided. Here, InfoDescriptor is a data structure prepared by the standard for storing information about a module.

[0138] FIG. 13 is a diagram showing the structure of the InfoDescriptor. Here, in text_char, multiple 8-bit character string information related to the file to be transmitted as a module can be described using the character code defined by the data encoding method or operation. The content descriptor is described in this text_char.

[0139] The content descriptor contains the following information: The c_id is an ID for identifying the content data. c_name is the name of the content data. c_category is the category of content data. "app" means that it is a command. There are other categories such as AV data. c_size is the size of the content data (in kilobytes). The c_m_number indicates the number of modules that transmit the content data. Meta_module is a module ID of data related to the content data. The Meta_url indicates the location on the network where data related to the content data is located.

[0140] [Command data structure] Next, the data structure of a command will be described.

[0141] The commands are transmitted by event messages. The data of the event message is described in a stream descriptor and transmitted in the DSM-CC section format for stream descriptors.

[0142] FIG. 14 is a diagram showing the data structure of a DSM-CC section that transmits a stream descriptor. This is an excerpt from the standard, ARIB STD-B24, version 5.1. The meaning of each descriptor is described in the above standard.

[0143] In the DSM-CC section, a general-purpose event message descriptor can be stored in stream_descriptor.

[0144] FIG. 15 is a diagram showing the data structure of the general-purpose event message descriptor. The event_msg_group_id is an identifier for identifying an event message group that an application should receive. Here, a value indicating that the event message group transmits a command related to the processing of content data is described in the event_msg_group_id.

[0145] time_mode is data indicating a method for specifying the time at which an event message is to be generated. When event_msg_group_id is a value indicating an event message group that stores commands related to content data processing, if time_mode is "0", it indicates that the event message is generated (transferred to external device 30) immediately after being received by broadcast receiver 20. If time_mode is "1", it indicates that the event message is generated by broadcast receiver 20 in accordance with absolute time expressed in the Modified Julian Calendar and Japan Standard Time. If time_mode is "2", it indicates that the event message is generated by broadcast receiver 20 in accordance with NPT time data. If time_mode is "3", it indicates that the event message is generated by broadcast receiver 20 in accordance with a relative time (milliseconds) specification from the program start time.

[0146] One or more commands can be written in the private_data_byte.

[0147] FIG. 16 is a diagram showing an example of the format of a command stored in private_data_byte.

[0148] The command_code is an 8-bit command code. The relationship between command codes, commands, and arguments is shown in Figure 17.

[0149] The no_of_ss_target_apps is 8-bit data indicating the number of applications of the external device 30 to which the command is transmitted.

[0150] The app_category is 8-bit data that indicates the application category (such as the OS type).

[0151] The app_id_length is 8-bit data that indicates the length (size) of the application.

[0152] The app_id_byte is 8-bit data that indicates the length (size) of the application. For this app_id_byte, one app_id can be described using multiple 8-bit app_id_bytes so that data of lengths ranging from 0 to the length indicated by app_id_length can be supported.

[0153] "no_of_text_data" is data that indicates the number of text data such as messages sent with Send Message or URLs sent with Launch App.

[0154] The text_data byte is the text data of the message body and the URL itself. To accommodate data lengths ranging from 0 to the length indicated by no_of_text_data, multiple 8-bit text_data bytes can be used to describe the body and URL of a single message.

[0155] The content_id_byte is data that identifies the content data that is the target of the command. For this content_id_byte, multiple 8-bit content_id_bytes can be used to describe one content_id so that data of a length ranging from 0 to the length indicated by no_of_content_id_byte can be handled.

[0156] The no_of_content_id_byte is 8-bit data indicating the maximum number of content_id_bytes.

[0157] [JSON example] JSON (JavaScript Object Notation) is a data format that uses object notation in Java (registered trademark) Script and is used for transferring data between software programs.

[0158] FIG. 18 is a diagram showing an example of content description information written in JSON. In JSON, pairs of keys and values ​​are separated by a colon (:) and are listed in a comma-separated list. Values ​​can be arrays or objects. This allows arrays and objects to be nested to multiple levels.

[0159] This is an example of how to write a Receive & Launch App command. It is assumed that multiple applications are specified in an object with "AppList" as the key as the applications that are the target of the Receive & Launch App command. Each application is represented by an object with "AppID" as the key. In the object with "AppID" as the key, a category (AppCategory) key-value pair is written as information that identifies a single application. Furthermore, in this example, a content ID (ContentID) key and value are written as information that specifies the content data that is the target of the Receive & Launch App command.

[0160] The present technology can also be configured as follows. (1) an interface capable of being connected to an information processing device; a first controller that acquires content data transmitted by a DDB message, acquires a first command that is transmitted by an event message and is for causing the information processing device connected through the interface to acquire the acquired content data, and transfers the first command to the information processing device; A broadcast receiver comprising:

[0161] (2) The broadcast receiver according to (1), A storage device for storing the acquired content data is further provided. The first controller is configured to transmit the content data stored in the storage to the information processing device in response to an acquisition request from the connected information processing device. Broadcast receiver.

[0162] (3) A broadcast receiver according to (1) or (2), The first controller is configured to set the content data standby operation mode in which the first controller generates the first command and transfers the first command to the information processing device every time the first controller acquires the content data transmitted by the DDB message when the first controller acquires the second command transmitted by the event message. Broadcast receiver.

[0163] (4) The broadcast receiver according to (3), The first controller is configured to cancel the setting of the content data standby operation mode when the first controller acquires a third command transmitted by the event message while the content data standby operation mode is set. Broadcast receiver.

[0164] (5) A broadcast receiver according to any one of (1) to (4), The first controller is configured to, when acquiring a fourth command transmitted from the event message and for transmitting a message to the information processing device, transfer the fourth command to the information processing device. Broadcast receiver.

[0165] (6) A broadcast receiver according to any one of (1) to (5), The first controller is configured to, when acquiring a fifth command transmitted from the event message and instructing the information processing device to access data on a network, transfer the fifth command to the information processing device. Broadcast receiver.

[0166] (7) A broadcast receiver according to any one of (1) to (6), the first command includes information regarding a method for designating a time at which the controller transfers the first command to the information processing device; The first controller is configured to determine a time to forward the first command based on the information. Broadcast receiver. [Explanation of symbols]

[0167] 10…Broadcasting station 11…Data Broadcasting Department 20...Broadcast receiver 21...Data broadcasting receiver 22…Resident Function Department 23...File server 30…External device 31…Native application 32...HTML browser 40…External server 50…Network 201...CPU 202...RAM 203...ROM 205...Communication interface 206…Tuner 207…Demodulation section 208...TS decoder 209...Audio decoder 210...Video decoder 211... Presentation processing unit 212…System bus 213…External device interface 214…Storage 221…Command acquisition section 222…Content data acquisition unit 230...Audio output section 240…Remote controller 301...CPU 302...RAM 303...ROM 305…Communication interface 306…External device interface 307…Storage

Claims

1. a tuner for receiving broadcasts; an interface for communicating with an information processing device; receiving a connection request from a native application of the information processing device; Verifying that the native application is authentic and connecting to the information processing device; obtaining from the broadcast a URL of HTML content and a first command for causing the native application to download the HTML content and execute the HTML content on an HTML browser of the native application; a controller configured to transfer the URL to the information processing device in response to the acquired first command; A broadcast receiver comprising:

2. The tuner receives the broadcast, The controller receiving a connection request from a native application of the information processing device; Verifying that the native application is authentic and connecting to the information processing device; obtaining from the broadcast a URL of HTML content and a first command for causing the native application to download the HTML content and execute the HTML content on an HTML browser of the native application; The URL is transferred to the information processing device in response to the acquired first command. How a broadcast receiver works.

Images