How to start the application

Abstract

To provide a digital broadcast receiver capable of executing a function with a higher added value.SOLUTION: A broadcast receiver receives a broadcast wave of a digital broadcast service, controls operation including a start and an end of an application associated with a broadcast program on the basis of application related information, and selects control related to a restart of the application on the basis of user's operation. The broadcast receiver controls a restart or a non-restart of the application in accordance with user's control selection in the case that the start of the application is requested after the application is ended.SELECTED DRAWING: Figure 36

Description

[Technical Field]

[0001] The present invention relates to an application launch method. [Background technology]

[0002] One of the extension functions of digital broadcasting services is data broadcasting, which transmits digital data via broadcast waves and displays various information such as weather forecasts, news, recommended programs, etc. Many television receivers capable of receiving data broadcasting are already commercially available, and many technologies related to receiving data broadcasting have been published, including Patent Document 1 below. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2001-186486 A Summary of the Invention [Problem to be solved by the invention]

[0004] A feature of data broadcasting is that television receivers that support digital broadcasting services can receive data broadcasting on their own and can acquire and display a variety of information. However, because the amount of data that can be transmitted with data broadcasting is limited due to restrictions on radio wave bandwidth, it is difficult to achieve high-definition screen displays and sophisticated effects. This has made it difficult to implement useful, high-value-added functions on current digital broadcasting receivers.

[0005] An object of the present invention is to provide a digital broadcast receiver that can execute higher value-added functions. [Means for solving the problem]

[0006] The technology described in the claims is used as a means for solving the above problems. To take one example, the technology described in claim 1 is used. [Effects of the Invention]

[0007] By using the technology of the present invention, it is possible to provide a digital broadcast receiver that can execute functions with higher added value. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a system configuration diagram of a communication system according to an embodiment. [Figure 2A] FIG. 1 is a block diagram of a broadcast receiving device according to an embodiment. [Figure 2B] FIG. 2 is a software configuration diagram of the broadcast receiving device according to the embodiment. [Figure 3] FIG. 2 is a block diagram of a broadcasting station server according to an embodiment. [Figure 4] FIG. 2 is a block diagram of a service provider server according to an embodiment. [Figure 5A] FIG. 1 is a block diagram of a portable information terminal according to an embodiment. [Figure 5B] FIG. 2 is a software configuration diagram of the portable information terminal according to the embodiment. [Figure 6] FIG. 4 is a data structure diagram of application control information according to the embodiment. [Figure 7A] FIG. 4 is an operational sequence diagram when an application is started up in the broadcast receiving device according to the embodiment. [Figure 7B] FIG. 4 is an operational sequence diagram when an application is started up in the broadcast receiving device according to the embodiment. [Figure 7C] FIG. 4 is an operational sequence diagram when an application is started up in the broadcast receiving device according to the embodiment. [Figure 8A] FIG. 4 is an operational sequence diagram of the mobile information terminals according to the embodiment when they are linked together. [Figure 8B] FIG. 4 is an operational sequence diagram of the mobile information terminals according to the embodiment when they are linked together. [Figure 8C] FIG. 4 is an operational sequence diagram of the mobile information terminals according to the embodiment when they are linked together. [Figure 9] 4 is an operational sequence diagram when an application is started in the broadcast receiving device and the mobile information terminal according to the embodiment. FIG. [Figure 10A]FIG. 10 is a screen display diagram of a basic screen of a cooperative control application of the mobile information terminal according to the embodiment. [Figure 10B] FIG. 10 is a screen display diagram of a basic screen of a cooperative control application of the mobile information terminal according to the embodiment. [Figure 11] FIG. 2 is a screen display diagram of a data broadcast screen of the broadcast receiving device according to the embodiment. [Figure 12A] 4A and 4B are screen display diagrams of notification screens of the broadcast receiving device according to the embodiment; [Figure 12B] 10A and 10B are diagrams illustrating a screen display of a broadcast cooperative application launcher of the broadcast receiving device according to the embodiment. [Figure 13A] 10A and 10B are screen display diagrams of a broadcast cooperative application execution screen of the broadcast receiving device according to the embodiment. [Figure 13B] 10A and 10B are screen display diagrams of a broadcast cooperative application execution screen of the broadcast receiving device according to the embodiment. [Figure 13C] 10A and 10B are screen display diagrams of a broadcast cooperative application execution screen of the broadcast receiving device according to the embodiment. [Figure 13D] 10A and 10B are screen display diagrams of a broadcast cooperative application execution screen of the broadcast receiving device according to the embodiment. [Figure 14] FIG. 10 is a diagram showing an error display screen of the broadcast receiving device according to the embodiment. [Figure 15] FIG. 10 is a screen display diagram of a broadcast cooperative application execution screen of the mobile information terminal according to the embodiment. [Figure 16A] FIG. 2 is a screen display diagram of an EPG display screen of the broadcast receiving device according to the embodiment. [Figure 16B] FIG. 10 is a diagram showing detailed information on an EPG display screen of a broadcast receiving device according to an embodiment. [Figure 17] 10 is an operational sequence diagram of the broadcast receiving device according to the embodiment when acquiring a broadcast cooperative application. [Figure 18A] FIG. 10 is an operational sequence diagram when terminals cooperate with each other according to an embodiment. [Figure 18B] FIG. 10 is an operational sequence diagram when terminals cooperate with each other according to an embodiment. [Figure 18C] FIG. 10 is an operational sequence diagram when terminals cooperate with each other according to an embodiment. [Figure 18D] FIG. 10 is an operational sequence diagram when terminals cooperate with each other according to an embodiment. [Figure 19A] 10 is a screen display diagram of a broadcast cooperative application launcher of the broadcast receiving device according to the embodiment. [Figure 19B] 10 is a screen display diagram of a broadcast cooperative application launcher of the broadcast receiving device according to the embodiment. [Figure 19C] 10 is a screen display diagram of a broadcast cooperative application launcher of the broadcast receiving device according to the embodiment. [Figure 19D] 10 is a screen display diagram of a broadcast cooperative application launcher of the broadcast receiving device according to the embodiment. [Figure 19E] 3A and 3B are diagrams illustrating screen displays of a broadcast receiving device according to an embodiment. [Figure 19F] FIG. 10 is a screen display diagram of a broadcast cooperative application launcher of the mobile information terminal according to the embodiment. [Figure 20] 1 is a diagram showing a system configuration including a broadcast receiving device according to an embodiment and an example of use thereof; [Figure 21] 10 is an operational sequence diagram when a broadcast cooperative application of the broadcast receiving device according to the embodiment is started. [Figure 22] 10 is an operational sequence diagram when a broadcast cooperative application of the broadcast receiving device according to the embodiment is started. [Figure 23] 10 is an operational sequence diagram when a broadcast cooperative application of the broadcast receiving device according to the embodiment is started. [Figure 24] FIG. 10 is a screen display diagram of a start-up confirmation screen of the broadcast receiving device according to the embodiment. [Figure 25] FIG. 4 is a screen display diagram of a user setting screen of the broadcast receiving device according to the embodiment. [Figure 26] 1 is a diagram showing a system configuration including a broadcast receiving device according to an embodiment and an example of use thereof; [Figure 27] 10A and 10B are diagrams illustrating examples of a plurality of types of apps and transitions between apps according to an embodiment. [Figure 28] 10 is an operational sequence diagram when a broadcast cooperative application of the broadcast receiving device according to the embodiment is started. [Figure 29] 10A and 10B are diagrams showing an example of control of broadcast program playback and application execution according to an embodiment. [Figure 30] FIG. 10 is a screen display diagram of an example of a startup selection screen of the broadcast receiving device according to the embodiment. [Figure 31] FIG. 10 is a screen display diagram of an example of a startup selection screen of the broadcast receiving device according to the embodiment. [Figure 32]FIG. 10 is a screen display diagram illustrating an example of a multiple application execution screen of the broadcast receiving device according to the embodiment. [Figure 33] FIG. 10 is a screen display diagram illustrating an example of a multiple application execution screen of the broadcast receiving device according to the embodiment. [Figure 34] 1 is a diagram showing a system configuration including a broadcast receiving device according to an embodiment and an example of use thereof; [Figure 35] 10A and 10B are diagrams showing an example of control of broadcast program playback and application execution according to an embodiment. [Figure 36] 10 is an operational sequence diagram when a broadcast cooperative app of the broadcast receiving device according to the embodiment is restarted. [Figure 37] FIG. 10 is a screen display diagram of an example of a restart prevention screen of the broadcast receiving device according to the embodiment. [Figure 38] FIG. 10 is a screen display diagram illustrating an example of a restart confirmation screen of the broadcast receiving device according to the embodiment. [Figure 39] 10 is an operational sequence diagram when a broadcast cooperative app of the broadcast receiving device according to the embodiment is restarted. [Figure 40] FIG. 10 is a screen display diagram illustrating an example of an update confirmation screen of the broadcast receiving device according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, examples of embodiments of the present invention will be described with reference to the drawings. [Example]

[0010] First, an example of a digital broadcasting service that can be received by the broadcasting receiving device of this embodiment will be described. For example, in an example of BS / terrestrial digital broadcasting that can be received by the broadcast receiving device of this embodiment, multiple transport streams (TS) can be multiplexed and transmitted on one transponder (frequency channel). A TS is a series of TS packets of a predetermined length, each of which is formed by dividing a data sequence, such as a video / audio elementary stream (ES) or program specific information (PSI) / service information (SI), and each of which has a TS header added.

[0011] PSI is a unique information table defined in the MPEG (Moving Picture Experts Group)-2 system standard that identifies which program each ES included in a TS belongs to. PSI is composed of a PAT (Program Association Table), PMT (Program Map Table), CAT (Conditional Access Table), etc. The PAT defines the list of programs included in a TS using the PID (Packet Identifier) ​​of the PMT. The PMT defines the PID of the components of each program, etc. The CAT includes information related to conditional access.

[0012] SI is an extension of PSI that includes program information and other information, and includes information on the Electronic Program Guide (EPG) specified by the Association of Radio Industries and Businesses (ARIB) in ARIB STD-B10. SI is composed of BIT (Broadcaster Information Table), SDT (Service Description Table), EIT (Event Information Table), TOT (Time Offset Table), etc. BIT includes broadcast station identification information, affiliate information, and broadcast station SI transmission information. SDT includes information such as a network ID for identifying the network, a TS ID for identifying the TS, and a service ID (also known as a channel number) for identifying individual services (also known as channels) within the network. EIT includes a service ID for identifying individual services within the network, and information related to events, such as the name, broadcast date and time, and broadcast content of each event (also known as a program). TOT includes information related to the current date and time.

[0013] The TS also includes PCR (Program Clock Reference) information that serves as a reference for playback timing in a decoder, and a subset of the Broadcast Markup Language (BML) document based on the BML specifications defined in ARIB STD-B24.

[0014] In the broadcast receiving device of this embodiment, by receiving and decoding the TS composed of the video / audio ES and various information, it is possible to provide users with broadcast programs, EPG, data broadcast screens created using BML, etc.

[0015] Furthermore, the broadcast receiving device of this embodiment is compatible with a broadcasting and communication integration system that integrates functions using a broadband network with digital broadcasting services, and combines digital broadcasting services with the acquisition of additional content via the broadband network, computational processing in a server device, and presentation processing in collaboration with a mobile terminal device. To realize the broadcasting and communication integration system, the broadcast receiving device of this embodiment is capable of executing applications written in HTML (Hyper Text Markup Language) or similar. The broadcasting and communication integration system compatible with this broadcasting and communication integration system uses an extended BML specification, application control information (Application Information Table: AIT) in the broadcasting and communication integration system, and extended PSI / SI information required for transmitting applications via broadcast waves. The AIT provides or disseminates various information required to launch applications, such as the source where the application is acquired, and control information for controlling the launch / termination of applications.

[0016] The above explanation is based on the digital broadcasting service in Japan, but the application is not limited to Japan, including the broadcasting and communication cooperation system compatible with the broadcast receiving device of this embodiment.

[0017] Next, a specific configuration example of the embodiment of this example will be described.

[0018] [System Configuration] 1 is a system configuration diagram showing an example of a communication system of this embodiment that realizes a broadcast communication cooperation system. The communication system of this embodiment is composed of a broadcast receiving device 100 and an antenna 100a, a broadband network 200 such as the Internet and a router device 210, a broadcast station radio tower 300t, a broadcast station server 300, a service provider server 400, other application servers 500, a mobile telephone communication server 600 and a base station 600b of a mobile telephone communication network, and a mobile information terminal 700.

[0019] The broadcast receiving device 100 is a television receiver that has a function compatible with the broadcast / communication cooperation system in addition to an existing digital broadcast receiving function. The broadcast receiving device 100 receives broadcast waves transmitted from a radio wave tower 300t via an antenna 100a. The broadcast receiving device 100 can also connect to the Internet 200 via a router device 210, and can transmit and receive data via communication with each server device on the Internet 200.

[0020] Router device 210 is connected to Internet 200 via wireless or wired communication, and is also connected to broadcast receiving device 100 via wireless or wired communication and to mobile information terminal 700 via wireless communication. This allows each server device on Internet 200, broadcast receiving device 100, and mobile information terminal 700 to mutually transmit and receive data via router device 210. Note that communication between broadcast receiving device 100 and mobile information terminal 700 may be performed directly using a method such as Bluetooth (registered trademark) or NFC (Near Field Communication) without going through router device 210.

[0021] The radio tower 300t transmits broadcast waves including digital broadcast signals, AIT, control information related to application presentation, etc. from the broadcasting equipment of the broadcasting station. The control information related to application presentation is control information related to the superimposition of broadcast programs and applications on television receivers and whether or not applications can be presented. The broadcasting station is also assumed to have a broadcasting station server 300. The broadcasting station server 300 stores broadcast programs (video content, etc.) and metadata of each broadcast program, such as the program title, program ID, program summary, cast, and broadcast date and time, and is capable of providing the video content and each metadata to a service provider based on a contract. The video content and each metadata may be provided to the service provider via an API (Application Programming Interface) provided by the broadcasting station server 300.

[0022] The service provider server 400 is a server device prepared by a service provider to provide services through the broadcasting and communication collaboration system. The service provider server 400 stores, manages, and distributes video content and metadata provided by the broadcasting station server 300, as well as content and applications created for the broadcasting and communication collaboration system. It also has a function of searching for and providing a list of available applications in response to inquiries from television receivers. The storage, management, and distribution of the content and metadata and the storage, management, and distribution of the applications may be performed by different server devices. The broadcasting station and the service provider may be the same or different providers. Multiple service provider servers 400 may be provided for different services. The functions of the service provider server 400 may also be provided by the broadcasting station server 300.

[0023] The other application server 500 is a known server device that stores, manages, and distributes general applications, operating programs, content, and data other than those related to the broadcasting and communication cooperation system.

[0024] Mobile telephone communication server 600 is connected to Internet 200, and is also connected to mobile information terminal 700 via base station 600b. Mobile telephone communication server 600 manages telephone communications (calls) and data transmission / reception of mobile information terminal 700 via the mobile telephone communication network, and enables transmission / reception of data between mobile information terminal 700 and each server device on Internet 200. Note that communication between mobile information terminal 700 and broadcast receiving device 100 may be performed via base station 600b, mobile telephone communication server 600, Internet 200, and router device 210.

[0025] [Broadcast receiving device hardware configuration] 2A is a block diagram showing an example of the internal configuration of a broadcast receiving device 100. The broadcast receiving device 100 includes a main control unit 101, a system bus 102, a ROM 103, a RAM 104, a storage unit 110, a LAN communication unit 121, an extension interface unit 124, a digital interface unit 125, a tuner / demodulator unit 131, a first separation unit 132, a first video decoding unit 133, a first audio decoding unit 134, a first subtitle decoding unit 135, a data broadcast reception processing unit 141, a data broadcast engine 142, a streaming reception processing unit 151, a second separation unit 152, a second video decoding unit 153, a second audio decoding unit 154, a second subtitle decoding unit 155, an application control unit 161, an application engine 162, a video superimposition unit 171, an audio selection unit 172, a video display unit 173, a speaker 174, a video output unit 175, an audio output unit 176, a presentation synchronization control unit 181, and a terminal cooperation control unit 191.

[0026] The main control unit 101 is a microprocessor unit that controls the entire broadcast receiving device 100 in accordance with a predetermined operation program. The system bus 102 is a data communication path for transmitting and receiving data between the main control unit 101 and each operation block within the broadcast receiving device 100.

[0027] ROM (Read Only Memory) 103 is a memory that stores basic operation programs such as an operating system and other operation programs, and may be a rewritable ROM such as an EEPROM (Electrically Erasable Programmable ROM) or flash ROM. RAM (Random Access Memory) 104 serves as a work area when the basic operation programs and other operation programs are executed. ROM 103 and RAM 104 may be integrated with main control unit 101. ROM 103 may also use a partial storage area within storage unit 110, rather than being an independent configuration as shown in FIG. 2A.

[0028] The storage unit 110 stores the operating programs and operation setting values ​​of the broadcast receiving device 100, personal information of the user of the broadcast receiving device 100, etc. It can also store operating programs downloaded from a network and various data created by the operating programs. It can also store content such as moving images, still images, and audio acquired from broadcast waves or downloaded from a network. A portion of the storage unit 110 may replace all or part of the functions of the ROM 103. Furthermore, the storage unit 110 needs to retain the stored information even when power is not supplied to the broadcast receiving device 100 from an external source. Therefore, devices such as semiconductor element memories such as flash ROMs and solid state drives (SSDs), and magnetic disk drives such as hard disk drives (HDDs) are used.

[0029] It is assumed that the operation programs stored in the ROM 103 and the storage unit 110 can be updated and have their functions expanded by downloading them from each server device on the Internet 200 .

[0030] The LAN (Local Area Network) communication unit 121 is connected to the Internet 200 via a router device 210, and transmits and receives data to and from each server device on the Internet 200. The connection to the router device 210 may be a wired connection or a wireless connection such as Wi-Fi (registered trademark). The LAN communication unit 121 includes an encoding circuit, a decoding circuit, etc. The broadcast receiving device 100 may further include other communication units such as a Bluetooth (registered trademark) communication unit, an NFC communication unit, an infrared communication unit, etc.

[0031] The tuner / demodulator 131 receives broadcast waves from a radio tower 300t via the antenna 100a, and tunes (selects) to a channel of a service desired by the user under the control of the main controller 101. Furthermore, the tuner / demodulator 131 demodulates the received broadcast signal to acquire a TS. Note that while the example shown in FIG. 2A illustrates a configuration with one tuner / demodulator, the broadcast receiving device 100 may be configured to include multiple tuner / demodulators for purposes such as simultaneous display on multiple screens or recording of other programs. Furthermore, under the control of the main controller 101, access restriction control for the demodulated TS may be performed.

[0032] The first separation unit 132 receives the TS output from the tuner / demodulation unit 131, separates it into various data streams such as a video data stream, an audio data stream, a subtitle data stream, a program information data stream, an AIT data stream, and a BML data stream, and outputs the separated data streams. These data streams may be in ES format, for example. The first video decoding unit 133 decodes the video data stream received from the first separation unit 132 and outputs video information. The first audio decoding unit 134 decodes the audio data stream received from the first separation unit 132 and outputs audio information. The first subtitle decoding unit 135 decodes the subtitle data stream received from the first separation unit 132 and outputs subtitle information.

[0033] The data broadcasting reception processing unit 141 decodes the BML data string input from the first separation unit 132 and reproduces a BML document. The data broadcasting engine 142 is a BML browser that executes the BML document, and executes the BML document reproduced by the data broadcasting reception processing unit 141 to output data broadcasting screen information.

[0034] The streaming reception processing unit 151, under the control of the main control unit 101, accesses video content and the like stored in each server device on the Internet 200 via the LAN communication unit 121, and acquires a program stream (PS) of the video content and the like. Also, under the control of the main control unit 101, the streaming reception processing unit 151 may control DRM (Digital Rights Management) processing for the acquired PS.

[0035] Second separator 152 receives the PS output from streaming reception processor 151, separates it into various data streams such as a video data stream, an audio data stream, and a subtitle data stream, and outputs the separated data streams. These data streams may be in ES format, for example. Second video decoder 153, second audio decoder 154, and second subtitle decoder 155 perform the same processing as first video decoder 133, first audio decoder 134, and first subtitle decoder 135, respectively, and therefore their description will be omitted.

[0036] In addition, the first separation unit 132 and the second separation unit 152, the first video decoding unit 133 and the second video decoding unit 153, the first audio decoding unit 134 and the second audio decoding unit 154, and the first subtitle decoding unit 135 and the second subtitle decoding unit 155 may each be used interchangeably.

[0037] The application control unit 161 controls and manages the life cycle and events of each application by influencing the application engine 162 regarding the application created for the broadcasting and communication cooperation system based on the AIT data string input from the first separation unit or the AIT file acquired from each server device on the Internet 200. The application control unit 161 also controls the function constraints of the application as appropriate depending on the state of the application and the instructions in the AIT. The application engine 162 is an HTML browser that acquires and executes the application created for the broadcasting and communication cooperation system based on the control of the application control unit 161.

[0038] The video superimposition unit 171 receives the video information output from the first video decoding unit 133, the subtitle information output from the first subtitle decoding unit 135, the data broadcasting screen information output from the data broadcasting engine 142, the video information output from the second video decoding unit 153, the subtitle information output from the second subtitle decoding unit 155, and the application execution screen information output from the application engine 162, and performs processing such as selection and / or superimposition. The video superimposition unit 171 includes a video RAM (not shown), and drives the video display unit 173 and the like based on the video information input to the video RAM. Furthermore, under the control of the main control unit 101, the video superimposition unit 171 performs scaling processing, superimposition processing of EPG screen information created based on the program information data string output from the first separation unit 132, and the like, as necessary.

[0039] The audio selection unit 172 inputs audio information output from the first audio decoding unit 134, audio information output from the second audio decoding unit 154, and application execution audio information output from the application engine 162, and selects and outputs the audio information as appropriate in accordance with the control of the main control unit 101.

[0040] The video display unit 173 is a display device such as a liquid crystal panel, and provides the video information that has been selected and / or superimposed by the video superimposing unit 171 to the user of the broadcast receiving device 100. The speaker 174 provides the audio information that has been output from the audio selection unit 172 to the user of the broadcast receiving device 100. The video output unit 175 is a video output interface that outputs the video information that has been selected and / or superimposed by the video superimposing unit 171. The audio output unit 176 is an audio output interface that outputs the audio information that has been output from the audio selection unit 172. As mentioned above, when the broadcast receiving device 100 is a television receiver or the like, the video output unit 175 and the audio output unit 176 are not essential components of the present invention.

[0041] The presentation synchronization control unit 181 controls the presentation synchronization on the video display unit 173 and the speaker 174, or on the video output unit 175 and the audio output unit 176, of the video information, audio information, etc. obtained by decoding the TS obtained from the broadcast waves, the video information, audio information, etc. obtained by decoding the PS obtained from each server device on the Internet 200, and the application execution screen information and application execution audio information output from the application engine 162, based on, for example, PCR information, etc.

[0042] When linking with an external mobile terminal device, the terminal link control unit 191 manages and controls the discovery and authentication of the linked device (mobile terminal device), the connection between the broadcast receiving device 100 and the linked device, the linking of applications, etc.

[0043] The expansion interface unit 124 is a group of interfaces for expanding the functions of the broadcast receiving device 100, and in this embodiment is configured with an analog video / audio interface, a USB (Universal Serial Bus) interface, a memory interface, etc. The analog video / audio interface inputs analog video signals / audio signals from external video / audio output devices, outputs analog video signals / audio signals to external video / audio input devices, etc. The USB interface connects to a PC or the like to send and receive data. A HDD may be connected to record broadcast programs and content. A keyboard or other USB device may also be connected. The memory interface connects to a memory card or other memory medium to send and receive data.

[0044] The digital interface unit 125 is an interface that outputs or inputs encoded digital video data and / or digital audio data. The digital interface unit 125 is capable of outputting the TS acquired by the tuner / demodulator unit 131 and the PS acquired by the streaming reception processing unit 151 as is. The digital interface unit 125 may also be controlled to input the TS or PS input from the digital interface unit 125 to the first separation unit 132 or the second separation unit 152. The digital content stored in the storage unit 110 may be output or the digital content may be stored in the storage unit 110 via the digital interface unit 125. The digital interface unit 125 may be a DVI terminal, an HDMI terminal, or the like, and may output or input data in a format conforming to the DVI specification, the HDMI specification, or the like. The output or input may be in the form of serial data conforming to the IEEE 1394 specification, or the like.

[0045] The broadcast receiving device 100 may be a television receiver, an optical disc drive recorder such as a DVD (Digital Versatile Disc) recorder, a magnetic disc drive recorder such as an HDD recorder, a set-top box (STB), etc. It may also be a personal computer (PC), tablet terminal, game console, etc. equipped with a digital broadcast receiving function and a broadcast / communication linking function. If the broadcast receiving device 100 is a DVD recorder, HDD recorder, STB, etc., it may not be equipped with the video display unit 173 and the speaker 174. By connecting an external monitor and an external speaker to the video output unit 175 and the audio output unit 176, it becomes possible to perform the same operation as the broadcast receiving device 100 of this embodiment.

[0046] [Software configuration of broadcast receiving device] 2B is a software configuration diagram of the broadcast receiving device 100 of this embodiment, showing the software configuration in the ROM 103, RAM 104, and storage unit 110. In this embodiment, a basic operation program 1001 and other operation programs are stored in the ROM 103, and a receiving function program 1002, a BML browser program 1003, an HTML browser program 1004, and other operation programs are stored in the storage unit 110. The storage unit 110 is also assumed to include a content storage area 1011 for storing content such as moving images, still images, and audio, an authentication information storage area 1012 for storing authentication information and the like used when linking with an external mobile terminal device, and various information storage areas for storing various other information.

[0047] A basic operation program 1001 stored in ROM 103 is loaded into RAM 104, and the main control unit 101 executes the loaded basic operation program to form a basic operation execution unit 1101. A receiving function program 1002, a BML browser program 1003, and an HTML browser program 1004 stored in the storage unit 110 are loaded into RAM 104, and the main control unit 101 executes each of the loaded operation programs to form a receiving function execution unit 1102, a BML browser engine 1103, and an HTML browser engine 1104. The RAM 104 also includes a temporary storage area for temporarily storing data created when each operation program is executed, as needed.

[0048] For ease of explanation, the process of controlling each operation block by the main control unit 101 expanding the basic operation program 1001 stored in the ROM 103 into the RAM 104 and executing it will be described below as if the basic operation execution unit 1101 controls each operation block. Similar descriptions will be used for the other operation programs.

[0049] The reception function execution unit 1102 controls each operational block of the broadcast receiving device 100 to realize the broadcast reception function and the broadcast / communication cooperation function. In particular, the broadcast program playback unit 1102a mainly controls the tuner / demodulator unit 131, the first demultiplexer 132, the first video decoding unit 133, the first audio decoding unit 134, the first subtitle decoding unit 135, the data broadcast reception processing unit 141, and the data broadcast engine 142. The data broadcast engine 142 may be replaced by a BML browser engine 1103 deployed on the RAM 104. The communication content playback unit 1102b mainly controls the streaming reception processing unit 151, the second demultiplexer 152, the second video decoding unit 153, the second audio decoding unit 154, and the second subtitle decoding unit 155. The cooperation application control unit 1102c mainly controls the application control unit 161 and the application engine 162. The application engine 162 may be replaced by an HTML browser engine 1104 deployed on the RAM 104. The terminal cooperation management unit 1102d mainly controls the terminal cooperation control unit 191.

[0050] The operation programs may be stored in the ROM 103 and / or the storage unit 110 before the product is shipped. After the product is shipped, the operation programs may be acquired from another application server 500 or the like on the Internet 200 via the LAN communication unit 121. Alternatively, the operation programs may be stored in a memory card, an optical disk, or the like and acquired via the expansion interface unit 124 or the like.

[0051] [Broadcasting station server configuration] 3 is a block diagram showing an example of the internal configuration of the broadcast station server 300. The broadcast station server 300 is made up of a main control unit 301, a system bus 302, a RAM 304, a storage unit 310, and a LAN communication unit 321.

[0052] The main control unit 301 is a microprocessor unit that controls the entire broadcast station server 300 in accordance with a predetermined operation program. The system bus 302 is a data communication path for transmitting and receiving data between the main control unit 301 and each operation block within the broadcast station server 300. The RAM 304 serves as a work area when each operation program is executed.

[0053] The storage unit 310 stores a basic operation program 3001 and a content management / distribution program 3002, and further includes a video content storage area 3011 and a metadata storage area 3012. The video content storage area 3011 stores video content and the like of each broadcast program broadcast by a broadcast station. The metadata storage area 3012 stores metadata of each broadcast program, such as the program title, program ID, program summary, cast, broadcast date and time, etc.

[0054] In addition, the basic operation program 3001 and content management / distribution program 3002 stored in the storage unit 310 are each expanded into RAM 304, and the main control unit 301 executes the expanded basic operation program and content management / distribution program to form a basic operation execution unit 3101 and a content management / distribution execution unit 3102.

[0055] For ease of explanation, the process of controlling each operation block by the main control unit 301 expanding the basic operation program 3001 stored in the storage unit 310 into the RAM 304 and executing it will be described below as if the basic operation execution unit 3101 were to control each operation block. Similar descriptions will be used for the other operation programs.

[0056] The content management / distribution execution unit 3102 manages the video content and the metadata stored in the video content storage area 3011 and the metadata storage area 3012, and controls the provision of the video content and the metadata to the service provider based on a contract. Furthermore, when providing the video content and the metadata to the service provider, the content management / distribution execution unit 3102 also performs authentication processing of the service provider server 400 based on the contract, as necessary.

[0057] The LAN communication unit 321 is connected to the Internet 200 and communicates with a service provider server 400 and the like on the Internet 200. The LAN communication unit 321 includes an encoding circuit, a decoding circuit, and the like.

[0058] [Service provider server configuration] 4 is a block diagram showing an example of the internal configuration of the service provider server 400. The service provider server 400 is made up of a main control unit 401, a system bus 402, a RAM 404, a storage unit 410, and a LAN communication unit 421.

[0059] The main control unit 401 is a microprocessor unit that controls the entire service provider server 400 in accordance with a predetermined operation program. The system bus 402 is a data communication path for transmitting and receiving data between the main control unit 401 and each operation block in the service provider server 400. The RAM 404 serves as a work area when each operation program is executed.

[0060] The storage unit 410 stores a basic operation program 4001, a content management / distribution program 4002, and an application management / distribution program 4003, and further includes a video content storage area 4011, a metadata storage area 4012, and an application storage area 4013. The video content storage area 4011 and the metadata storage area 4012 store the video content and the like and each piece of metadata provided from the broadcast station server 300, as well as content produced by the service provider and metadata related to the content. The application storage area 4013 stores applications required to realize each service of the broadcasting / communication cooperation system, which are distributed in response to requests from each television receiver.

[0061] In addition, the basic operation program 4001, content management / distribution program 4002, and application management / distribution program 4003 stored in the storage unit 410 are each expanded into RAM 404, and the main control unit 401 executes the expanded basic operation program, content management / distribution program, and application management / distribution program to form a basic operation execution unit 4101, a content management / distribution execution unit 4102, and an application management / distribution execution unit 4103.

[0062] For ease of explanation, the process of the main control unit 401 controlling each operation block by loading the basic operation program 4001 stored in the storage unit 410 into the RAM 404 and executing it will be described below as if the basic operation execution unit 4101 were to control each operation block. Similar descriptions will be used for the other operation programs.

[0063] The content management / distribution execution unit 4102 acquires video content and the like and each piece of metadata from the broadcast station server 300, manages the video content and the like and each piece of metadata stored in the video content storage area 4011 and the metadata storage area 4012, and controls the distribution of the video content and the like and each piece of metadata to each television receiver. The application management / distribution execution unit 4103 manages the applications stored in the application storage area 4013 and controls the distribution of each application in response to a request from each television receiver. Furthermore, when distributing each application to each television receiver, the application management / distribution execution unit 4103 also performs authentication processing of each television receiver as necessary.

[0064] The LAN communication unit 421 is connected to the Internet 200, and communicates with the broadcast receiving device 100 and the mobile information terminal 700 via the broadcast station server 300 on the Internet 200 and the router device 210. The LAN communication unit 421 is assumed to include an encoding circuit, a decoding circuit, etc.

[0065] [Hardware configuration of mobile information terminal] 5A is a block diagram showing an example of the internal configuration of a mobile information terminal 700. The mobile information terminal 700 is composed of a main control unit 701, a system bus 702, a ROM 703, a RAM 704, a storage unit 710, a communication processing unit 720, an expansion interface unit 724, an operation unit 730, an image processing unit 740, an audio processing unit 750, and a sensor unit 760.

[0066] The main control unit 701 is a microprocessor unit that controls the entire portable information terminal 700. The system bus 702 is a data communication path for transmitting and receiving data between the main control unit 701 and each operating block within the portable information terminal 700.

[0067] The ROM 703 is a memory in which basic operation programs such as an operating system and other operation programs are stored, and a rewritable ROM such as an EEPROM or flash ROM is used. The RAM 704 serves as a work area when the basic operation programs and other operation programs are executed. The ROM 703 and RAM 704 may be integrated with the main control unit 701. Furthermore, the ROM 703 may not be an independent configuration as shown in FIG. 5A, but may use a partial storage area within the storage unit 710.

[0068] The storage unit 710 stores the operating programs and operation setting values ​​of the mobile information terminal 700, personal information of the user of the mobile information terminal 700, etc. It can also store operating programs downloaded from a network and various data created by the operating programs. It can also store content such as moving images, still images, and audio downloaded from a network. A portion of the storage unit 710 may replace all or part of the functions of the ROM 703. The storage unit 710 must also retain the stored information even when power is not being supplied to the mobile information terminal 700 from an external source. Therefore, for example, a flash ROM, SSD, HDD, or other such device is used.

[0069] It should be noted that the operating programs stored in the ROM 703 and storage unit 710 can be updated and have their functions expanded by downloading them from each server device on the Internet 200 .

[0070] The communication processing unit 720 is composed of a LAN communication unit 721, a mobile telephone network communication unit 722, and an NFC communication unit 723. The LAN communication unit 721 is connected to the Internet 200 via the router device 210 and transmits and receives data to and from each server device on the Internet 200. The connection to the router device 210 is assumed to be wireless, such as via Wi-Fi (registered trademark). The mobile telephone network communication unit 722 performs telephone communication (calls) and data transmission and reception via wireless communication with a base station 600b of the mobile telephone network. The NFC communication unit 723 performs wireless communication when in proximity to a compatible reader / writer. The LAN communication unit 721, the mobile telephone network communication unit 722, and the NFC communication unit 723 each include an encoding circuit, a decoding circuit, an antenna, etc. The communication processing unit 720 may further include other communication units, such as a Bluetooth (registered trademark) communication unit or an infrared communication unit.

[0071] The expansion interface unit 724 is a group of interfaces for expanding the functions of the mobile information terminal 700, and in this embodiment is configured with a video / audio interface, a USB interface, a memory interface, etc. The video / audio interface inputs video signals / audio signals from external video / audio output devices, outputs video signals / audio signals to external video / audio input devices, etc. The USB interface connects to a PC or the like to send and receive data. It may also be used to connect a keyboard or other USB device. The memory interface connects to a memory card or other memory medium to send and receive data.

[0072] The operation unit 730 is an instruction input unit that inputs operation instructions to the mobile information terminal 700, and in this embodiment, is configured with a touch panel 730t and operation keys 730k with an array of button switches, which are arranged on top of the display unit 741. Only one of these may be used. The mobile information terminal 700 may be operated using a keyboard or the like connected to the extended interface unit 724. The mobile information terminal 700 may be operated using a separate mobile terminal device connected by wired or wireless communication. The touch panel function may also be provided in the display unit 741.

[0073] The image processing unit 740 is composed of a display unit 741, an image signal processing unit 742, a first image input unit 743, and a second image input unit 744. The display unit 741 is a display device such as a liquid crystal panel, and provides image data processed by the image signal processing unit 742 to the user of the mobile information terminal 700. The image signal processing unit 742 includes a video RAM (not shown), and the display unit 741 is driven based on image data input to the video RAM. The image signal processing unit 742 also has functions such as format conversion and superimposition processing of menus and other on-screen display (OSD) signals as necessary. The first image input unit 743 and the second image input unit 744 are camera units that input image data of the surroundings or object by converting light input from a lens into an electrical signal using electronic devices such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor) sensor.

[0074] The audio processing unit 750 is made up of an audio output unit 751, an audio signal processing unit 752, and an audio input unit 753. The audio output unit 751 is a speaker, and provides an audio signal processed by the audio signal processing unit 752 to the user of the mobile information terminal 700. The audio input unit 753 is a microphone, and converts the user's voice, etc. into audio data and inputs it.

[0075] The sensor unit 760 is a group of sensors for detecting the state of the portable information terminal 700, and in this embodiment, is composed of a GPS receiver unit 761, a gyro sensor 762, a geomagnetic sensor 763, an acceleration sensor 764, an illuminance sensor 765, and a proximity sensor 766. These sensors make it possible to detect the position, inclination, direction, and movement of the portable information terminal 700, as well as the ambient brightness and the proximity of surrounding objects. The portable information terminal 700 may further include other sensors such as a barometric pressure sensor.

[0076] The portable information terminal 700 may be a mobile phone, a smartphone, a tablet terminal, etc. It may also be a PDA (Personal Digital Assistant) or a notebook PC. It may also be a digital still camera, a video camera capable of shooting video, a portable game console, or other portable digital devices.

[0077] 5A includes many components that are not essential to this embodiment, such as sensor unit 760, but the effects of this embodiment are not impaired even if these components are not provided. Furthermore, components not shown, such as a digital broadcast receiving function and an electronic money payment function, may be further added.

[0078] [Software configuration of mobile information terminal] 5B is a software configuration diagram of the mobile information terminal 700 of this embodiment, and shows the software configuration in the ROM 703, RAM 704, and storage unit 710. In this embodiment, a basic operation program 7001 and other operation programs are stored in the ROM 703, and a cooperative control program 7002, an HTML browser program 7003, and other operation programs are stored in the storage unit 710. The storage unit 710 is also assumed to include a content storage area 7011 for storing content such as moving images, still images, and audio, an authentication information storage area 7012 for storing authentication information used during cooperative operation with a television receiver, and various information storage areas for storing various other information.

[0079] A basic operation program 7001 stored in ROM 703 is loaded into RAM 704, and the main control unit 701 executes the loaded basic operation program to form a basic operation execution unit 7101. Also, a cooperative control program 7002 and an HTML browser program 7003 stored in the storage unit 710 are loaded into RAM 704, and the main control unit 701 executes each of the loaded operation programs to form a cooperative control execution unit 7102 and an HTML browser engine 7103. Also, the RAM 704 is provided with a temporary storage area for temporarily storing data created when each operation program is executed, as needed.

[0080] For ease of explanation, the process of controlling each operation block by the main control unit 701 loading the basic operation program 7001 stored in the ROM 703 into the RAM 704 and executing it will be described below as if the basic operation execution unit 7101 were to control each operation block. Similar descriptions will be used for the other operation programs.

[0081] The cooperative control execution unit 7102 manages device authentication and connection, transmission and reception of various data, etc. when the mobile information terminal 700 performs cooperative operation with the television receiver. The HTML browser engine 7103 is an HTML browser that runs applications created for the broadcasting and communication cooperative system on the mobile information terminal 700.

[0082] The operation programs may be stored in the ROM 703 and / or the storage unit 710 before shipping the product. After shipping the product, the operation programs may be acquired from another application server 500 or the like on the Internet 200 via the LAN communication unit 721 or the mobile telephone network communication unit 722. Alternatively, the operation programs may be stored in a memory card, an optical disk, or the like and acquired via the extended interface unit 724 or the like.

[0083] [Application Control Information (AIT) Overview] The application control information (AIT) in this embodiment is information intended to notify a television receiver or the like (the broadcast receiving device 100 in this embodiment) of the existence of an application (hereinafter, sometimes referred to as a broadcast-linked app) that links with a broadcast service and to instruct its control in the broadcast-communication linkage function supported by the broadcast receiving device 100. Note that the broadcast-linked app may be classified into (1) broadcast-managed applications that operate only in a broadcast reception state based on control signals such as start / stop included in a broadcast signal and are permitted to access broadcast resources based on the control signals, (2) non-broadcast-managed applications that are not controlled by broadcast signals for start / stop, etc. and are permitted to access broadcast resources based on means such as application authentication, and (3) other general applications that are not permitted to access broadcast resources.

[0084] The AIT may be transmitted by either of the following methods: transmitting an AIT in section format or extensible markup language (XML) format over broadcast waves using a data carousel (DC) method or the like; or distributing an AIT file in section format or XML format from a server device on the Internet 200 using http (Hypertext Transfer Protocol) or https (Hypertext Transfer Protocol Secure) or the like. Other methods may also be used.

[0085] 6 is a data configuration diagram showing an example of the data configuration of an AIT. The AIT is mainly composed of information such as an application type 901, an application identifier 902, an application control code 903, an application profile 904, application acquisition destination information 905, an application boundary and access authority setting 906, a startup priority 907, cache information 908, and a server access distribution parameter 909. In addition, other information may be included.

[0086] The application type 901 specifies the description format of the application. In this embodiment, the description format of the application is assumed to be HTML. The application identifier 902 is identification information for identifying each application, consisting of an organization identifier for identifying the operator and an application identifier assigned to each operator. Note that an application is a set of HTML documents and their reference resources, with the HTML document present in the location specified by the application acquisition destination information 905 being the entry document. The application control code 903 specifies the operation control for the target application, and describes one of (1) auto-start, (2) operable, (3) terminated, or (4) prefetch. The application profile 904 is a value indicating the television receiver functions required by the application, and indicates a combination of optional functions that the television receiver has. By referencing this value, it is determined whether the application can be used.

[0087] The application acquisition destination information 905 is information specifying the acquisition destination of the application, and is location information for acquiring the HTML document that is first referenced when the application is launched. Since it is assumed that the application will be transmitted via broadcast or stored on a server device on a communication network, the location information specified by the application acquisition destination information 905 is also specified to accommodate both broadcast acquisition and communication acquisition. The application boundary and access restriction setting 906 is information indicating the operable range of the broadcast-managed application as a set of one or more areas (URL: Uniform Resource Locator). It also sets access restrictions to broadcast resources for each area on a functional basis. The application boundary and access restriction setting 906 specifies the range of document transitions to prevent unexpected document transitions due to a chain of document transitions from an entry document when the application is launched, or access to inappropriate broadcast resources. It is also possible to set access permissions to specific broadcast resources on an area-by-area basis within the range of the document transitions.

[0088] The launch priority 907 specifies which application is to be launched first when data broadcasting via a broadcasting service and a broadcast-managed application via an HTML document are both present. It is possible to unconditionally specify data broadcasting as the highest priority in the PMT, to specify the launch priority of a specific application type in the PMT, and to specify the launch priority of the target application using the launch priority 907. The cache information 908 is information used for cache control when retaining application resources in preparation for application reuse. This information makes it possible to cache application resources for reuse even after the application has terminated. The server access distribution parameter 909 is a parameter set for distributing access in order to reduce the load on servers that are heavily accessed, such as those that acquire applications. The television receiver may operate to probabilistically delay the application of application control codes according to the parameter settings.

[0089] The operation of the broadcast receiving device 100 of this embodiment will be described below.

[0090] [Application startup sequence] First, a description will be given of the process of launching a broadcast-linked app based on the AIT transmitted by broadcast waves in the broadcast receiving device 100 of this embodiment. In the broadcast receiving device 100 of this embodiment, it is possible to specify which of the two is to be launched first when a data broadcast by a broadcast service and a broadcast-linked app are simultaneously present, based on information on the PMT and information such as the application control code 903 and launch priority 907 in the AIT.

[0091] 7A is an operational sequence diagram showing an example of the operational sequence of a broadcast-linked app when it is specified that the broadcast-linked app is to be launched with priority. The diagram shows a series of steps from when the broadcast receiving device 100 appropriately checks the PMT and AIT to when it launches a predetermined broadcast-linked app.

[0092] When the tuner / demodulator unit 131 of the broadcast receiving device 100 performs processing for selecting a channel desired by the user and acquires a TS, the main control unit 101 then acquires the PMT data sequence separated by the first separation unit 132 (S101) and checks the startup priority described in the PMT. If it is confirmed in the processing of S101 that the startup priority of the broadcast-linked app is high (S102), the application control unit 161 acquires the AIT data sequence separated by the first separation unit 132 (S103) and checks the application control code 903 of the acquired AIT data sequence (S104). If the application control code 903 is "automatic startup" in the processing of S104, the application control unit 161 further checks the application profile 904 of the acquired AIT data sequence (S105). If it is confirmed that the broadcast-linked app specified in the AIT can be executed, a transmission request for the broadcast-linked app is sent to a predetermined service provider server 400 via the LAN communication unit 121 based on the information described in the application acquisition destination information 905 (S106).

[0093] Upon receiving the request to transmit the broadcast-interactive app, the service provider server 400 performs authentication processing of the broadcast receiving device 100 as necessary under the control of the application management / distribution execution unit 4103, and then distributes the predetermined broadcast-interactive app stored in the application storage area 4013 via the LAN communication unit 421 (S107). Note that a known method may be used for the authentication processing, and detailed description thereof will be omitted. Next, under the control of the application control unit 161, the application engine 162 of the broadcast receiving device 100 launches the predetermined broadcast-interactive app received from the service provider server 400 via the LAN communication unit 121 (S108).

[0094] 7B is an operational sequence diagram showing an example of the operational sequence of a broadcast-linked app when it is specified that data broadcasting by a broadcast service is to be started first. The diagram shows a series of steps from when the broadcast receiving device 100 appropriately checks the PMT and AIT to when it starts a predetermined broadcast-linked app.

[0095] When the tuner / demodulator 131 of the broadcast receiving device 100 performs processing to select a channel desired by the user and acquires a TS, the main control unit 101 then acquires the PMT data string separated by the first separation unit 132 (S201) and checks the activation priority described in the PMT. If the processing of S201 confirms that the activation priority of data broadcasting by the broadcast service is high (S202), the data broadcasting reception processing unit 141 acquires the BML data string separated by the first separation unit 132 and plays back the BML document (S203). If automatic activation of data broadcasting is set by the BML document, or if the user makes a data broadcasting activation request using an operation terminal (mobile information terminal 700, remote control, etc.) (S204), the data broadcasting engine 142 executes the played BML document to generate data broadcasting screen information and displays it on the video display unit 173 (S205).

[0096] After the process of S205, or simultaneously with the process of S205, the application control unit 161 acquires the AIT data sequence separated by the first separation unit 132 (S206) and checks the application profile 904 of the acquired AIT data sequence (S207). If it is confirmed in the process of S207 that the broadcast-linked application specified in the AIT is executable, an entry button for the executable broadcast-linked application is displayed on the data broadcast screen. The entry button may be always displayed, and its color may be changed from an inactive color to an active color only when the broadcast-linked application is executable. The entry button may be switched between an inactive state and an active state by changing its shape.

[0097] When the user selects the entry button using the operation terminal (S208), the data broadcasting engine 142 executes the BML document and ends the process of generating data broadcasting screen information (S209). Subsequently, the application control unit 161 acquires the AIT data string separated by the first separation unit 132 (S210), and checks the application acquisition destination information 905 of the acquired AIT data string. Furthermore, based on the information described in the application acquisition destination information 905 checked in S210, a transmission request for the broadcast cooperative app is sent to a predetermined service provider server 400 via the LAN communication unit 121 (S211).

[0098] Upon receiving the request to transmit the broadcast-interactive app, the service provider server 400, under the control of the application management / distribution execution unit 4103, performs authentication processing of the broadcast receiving device 100 as necessary, and then distributes the predetermined broadcast-interactive app stored in the application storage area 4013 via the LAN communication unit 421 (S212). Next, under the control of the application control unit 161, the application engine 162 of the broadcast receiving device 100 starts the predetermined broadcast-interactive app that has been received from the service provider server 400 via the LAN communication unit 121 (S213).

[0099] 7C is an operational sequence diagram showing an example of the operational sequence of a broadcast-linked app when no priority startup is specified. The diagram shows a series of steps from when the broadcast receiving device 100 appropriately checks the PMT and AIT to when it starts a predetermined broadcast-linked app.

[0100] When the tuner / demodulator 131 of the broadcast receiving device 100 performs processing to select a channel desired by the user and acquires a TS, the main control unit 101 then acquires the PMT data sequence separated by the first separation unit 132 (S301) and checks the startup priority described in the PMT. If it is confirmed in the processing of S301 that the startup priority of the broadcast-linked app is high (S302), the application control unit 161 acquires the AIT data sequence separated by the first separation unit 132 (S303) and checks the application control code 903 of the acquired AIT data sequence (S304). If the application control code 903 is "startable" rather than "automatic startup" in the processing of S304, the display of the broadcast program continues without starting either the data broadcast by the broadcast service or the broadcast-linked app.

[0101]

[0073] After the process of S304 is completed, if the user uses the operation terminal to make a request to start data broadcasting (S305), similar to the processes from S205 onwards in Fig. 7B, the acquisition of a BML data string, the playback of a BML document, and the generation of data broadcasting screen information are performed (however, not shown). On the other hand, after the process of S304 is completed, if the user uses the operation terminal to make a request to start a broadcast-linked application launcher (S306), the application control unit 161 acquires the AIT data string separated by the first separation unit 132 (S307) and checks the application profile 904 of the acquired AIT data string (S308). Furthermore, the application control unit 161 displays a list of executable broadcast-linked applications on the video display unit 173 as a broadcast-linked application launcher (S309).

[0102] When the user uses the operation terminal to select a predetermined broadcast-linked app from the broadcast-linked app launcher displayed in S309 (S310), the application control unit 161 acquires the AIT data string separated by the first separation unit 132 (S311) and checks the application acquisition destination information 905 of the acquired AIT data string. Furthermore, based on the information described in the application acquisition destination information 905 checked in S311, a transmission request for the broadcast-linked app is sent to the predetermined service provider server 400 via the LAN communication unit 121 (S312).

[0103] Upon receiving the transmission request for the broadcast-interactive app, the service provider server 400, under the control of the application management / distribution execution unit 4103, performs authentication processing for the broadcast receiving device 100 as necessary, and then distributes the predetermined broadcast-interactive app stored in the application storage area 4013 via the LAN communication unit 421 (S313). Next, under the control of the application control unit 161, the application engine 162 of the broadcast receiving device 100 starts the predetermined broadcast-interactive app that has been received from the service provider server 400 via the LAN communication unit 121 (S314).

[0104] 7A to 7C, an example is described in which the AIT is acquired from a broadcast wave. However, the AIT file may be acquired from a predetermined server device specified by the information description in the PMT or the like. Furthermore, the broadcast-linked app may be acquired from a broadcast wave, rather than from a server device (service provider server 400) on the network. That is, when the location information described in the application acquisition destination information 905 of the AIT indicates a broadcast wave, the application control unit 161 reproduces an HTML document from the HTML data string transmitted by a data carousel method or the like and separated and output by the first separation unit 132, and the application engine 162 executes the reproduced HTML document (broadcast-linked app).

[0105] Note that if there is no information on the PMT specifying the startup priority when data broadcasting by a broadcasting service and a broadcast-linked app exist simultaneously, the startup priority may be confirmed only by information such as the application control code 903 and startup priority 907 of the AIT. Similarly, if acquisition of the information on the PMT fails, the startup priority may be confirmed only by information such as the application control code 903 and startup priority 907 of the AIT. That is, the AIT may be checked periodically regardless of the information on the PMT, and if a broadcast-linked app specified as "automatic startup" in the application control code 903 of the AIT exists, startup of the broadcast-linked app may be prioritized, and if a broadcast-linked app specified as "automatic startup" in the application control code 903 of the AIT does not exist, startup of data broadcasting by a broadcasting service may be prioritized.

[0106] Furthermore, if there is no response from service provider server 400 for a predetermined time or longer when a distribution request for the broadcast-linked app is made in S106, S211, or S312, a message such as "Please wait a moment" may be displayed on video display unit 173. Alternatively, in this case, a message inquiring the user about stopping execution of the broadcast-linked app may be displayed.

[0107] Furthermore, it goes without saying that the start-up sequence of the broadcast-linked app is not limited to the three patterns described above, and the broadcast-linked app may be started up by a different sequence.

[0108] [Operation sequence when linking mobile information terminals] In the broadcast receiving device 100 of this embodiment, it is assumed that the functionality of a broadcast / communication cooperative service can be expanded by cooperative operation between the broadcast receiving device 100 and the mobile information terminal 700. For example, by installing an application (cooperative control app) provided by a television receiver manufacturer, it becomes possible to use the mobile information terminal 700 as a high-function remote control for the broadcast receiving device 100. In addition, by executing the broadcast cooperative app on the mobile information terminal 700, it becomes possible to display, for example, a service linked to a broadcast program being displayed on the broadcast receiving device 100 on the mobile information terminal 700. Note that in order to expand functionality through cooperative operation between the broadcast receiving device 100 and the mobile information terminal 700, it is desirable that the cooperative control app be running on the mobile information terminal 700, and the broadcast cooperative app running on the mobile information terminal 700 operates under the control of the cooperative control app.

[0109] 8A is an operational sequence diagram showing an example of the operational sequence when the cooperative control app is started on the mobile information terminal 700. The diagram shows a series of steps (first time) from when the mobile information terminal 700 performs authentication processing with the broadcast receiving device 100 until cooperative operation becomes possible. It is assumed that the cooperative control app is installed in advance in the storage unit 710 of the mobile information terminal 700 as a cooperative control program 7002.

[0110] When a user issues an instruction to launch a cooperative control app on the mobile information terminal 700 (S401), the cooperative control execution unit 7102 of the mobile information terminal 700 searches for television receivers on the network that are capable of communication (cooperative operation) (S402) and displays the search results as a list of television receivers on the display unit 741. If no television receivers that are capable of communication are found, a message to that effect is displayed and the processing ends. When the user selects an arbitrary television receiver (broadcast receiving device 100 in this embodiment) from the list of television receivers, the cooperative control execution unit 7102 displays a login screen for connecting to the broadcast receiving device 100 on the display unit 741. When the user inputs authentication information (such as a login name and password specified by the broadcast receiving device 100) into the login screen via the operation unit 730 (S403), the cooperative control execution unit 7102 stores the input authentication information in the authentication information storage area 7012 and simultaneously transmits the information to the broadcast receiving device 100 (S404). The authentication information may be transmitted to the broadcast receiving device 100 via the LAN communication unit 721 and the router device 210, or may be transmitted directly to the broadcast receiving device 100 via the NFC communication unit 723.

[0111] The terminal cooperation control unit 191 of the broadcast receiving device 100, which has received the authentication information via the LAN communication unit 121, checks whether the received authentication information is correct by referring to the authentication information storage area 1012 (S405). If the received authentication information is confirmed to be correct by the processing of S405, the terminal cooperation control unit 191 stores information about the mobile information terminal 700 in the authentication information storage area 1012 and authenticates the mobile information terminal 700 (S406). The mobile information terminal 700, which has been authenticated by the broadcast receiving device 100, displays the basic screen of the cooperation control app (e.g., an advanced remote control screen) on the display unit 741 (S407). If the received authentication information is not confirmed to be correct in S405, the terminal cooperation control unit 191 of the broadcast receiving device 100 returns an error to the mobile information terminal 700. Through the above processing, cooperation between the broadcast receiving device 100 and the mobile information terminal 700 becomes possible.

[0112] 8B is an operational sequence diagram showing an example of the operational sequence when the cooperative control app is started on the mobile information terminal 700. The diagram shows a series of steps (from the second time onwards) from when the mobile information terminal 700 performs authentication processing with the broadcast receiving device 100 until cooperative operation becomes possible.

[0113] When a user instructs the mobile information terminal 700 to launch a cooperative control app (S501), the cooperative control execution unit 7102 of the mobile information terminal 700 searches for television receivers on the network that can communicate with the mobile information terminal 700 and displays the search results as a list of television receivers on the display unit 741. If no television receivers that can communicate with the mobile information terminal 700 are found, a message to that effect is displayed and the processing ends. When the user selects an arbitrary television receiver (broadcast receiving device 100 in this embodiment) from the list of television receivers (S502), and the selected broadcast receiving device 100 is a device that has previously connected (operated cooperatively), the cooperative control execution unit 7102 reads out authentication information for the broadcast receiving device 100 from the authentication information storage area 7012 and transmits it to the broadcast receiving device 100 (S503).

[0114] The terminal cooperation control unit 191 of the broadcast receiving device 100, which has received the authentication information via the LAN communication unit 121, checks whether the received authentication information is correct by referring to the authentication information storage area 1012 (S504). If the received authentication information is confirmed to be correct by the processing of S504, it authenticates the mobile information terminal 700 (S505). The mobile information terminal 700, which has been authenticated by the broadcast receiving device 100, displays the basic screen of the cooperation control app on the display unit 741 (S506). Through the above processing, cooperation between the broadcast receiving device 100 and the mobile information terminal 700 becomes possible.

[0115] Note that, when starting up a broadcast cooperative app in the broadcast receiving device 100 following the processing of FIGS. 8A and 8B, the processing of FIGS. 7A to 7C may be performed after the processing of FIGS. 8A and 8B.

[0116] 8C is an operational sequence diagram showing an example of the operational sequence when the cooperative control app is launched on the mobile information terminal 700. The diagram shows a series of steps (from the second time onward) in which the mobile information terminal 700 performs authentication processing with the broadcast receiving device 100 and cooperative operation becomes possible. However, the diagram shows an example in which the broadcast receiving device 100, which executes the launch sequence of the broadcast cooperative app, requests the launch of the cooperative control app on the mobile information terminal 700.

[0117] When the tuner / demodulator 131 of the broadcast receiving device 100 performs processing to select a channel desired by the user and acquires a TS, the main control unit 101 then acquires the PMT data sequence separated by the first separation unit 132 (S601) and checks the startup priority described in the PMT. If it is confirmed in the processing of S601 that the startup priority of the broadcast-linked application is high (S602), the application control unit 161 acquires the AIT data sequence separated by the first separation unit 132 (S603) and checks the application control code 903 of the acquired AIT data sequence (S604). If the application control code 903 is "automatic startup" in the processing of S604, the application control unit 161 further checks the application profile 904 of the acquired AIT data sequence (S605). In the processing of S605, if it is confirmed that the broadcast-linked app specified in the AIT can be executed and if it is determined that linked control of the mobile terminal device is necessary, the terminal linkage control unit 191 selects the mobile information terminal 700 as the mobile terminal device by referring to the authentication information storage area 1012, and sends a linkage control app launch request to the selected mobile information terminal 700 (S606).

[0118] The selection of the mobile information terminal 700 by referring to the authentication information storage area 1012 may be based on the latest information in the authentication information storage area 1012 or the most frequently used information in the authentication information storage area 1012.

[0119] Furthermore, in the process of S606, if a mobile terminal device to which the cooperative control application start-up request should be sent cannot be found, a message indicating this may be displayed on the video display unit 173. Alternatively, in this case, a message inquiring the user about stopping execution of the broadcast cooperative application may be displayed.

[0120] The main control unit 701 of the mobile information terminal 700 launches the collaborative control app (collaborative control execution unit 7102) in response to the collaborative control app launch request received via the LAN communication unit 721 (S607), and the collaborative control execution unit 7102 then reads out the authentication information of the broadcast receiving device 100 from the authentication information storage area 7012 and transmits it to the broadcast receiving device 100 (S608).

[0121] The terminal cooperation control unit 191 of the broadcast receiving device 100, which has received the authentication information via the LAN communication unit 121, checks whether the received authentication information is correct by referring to the authentication information storage area 1012 (S609). If the processing of S609 confirms that the received authentication information is correct, it authenticates the mobile information terminal 700 (S610). The mobile information terminal 700, which has been authenticated by the broadcast receiving device 100, displays the basic screen of the cooperation control app on the display unit 741 (S611). Through the above processing, cooperation between the broadcast receiving device 100 and the mobile information terminal 700 becomes possible.

[0122] Note that, if the broadcast cooperative app is executed on both the broadcast receiving device 100 and the mobile information terminal 700 following the above-described processing, the processing shown in Fig. 9 may be performed. Fig. 9 is an operational sequence diagram showing an example of a start-up sequence of the broadcast cooperative app on the broadcast receiving device 100 and the mobile information terminal 700.

[0123] 8C, the application control unit 161 of the broadcast receiving device 100 acquires the AIT data sequence separated by the first separation unit 132 (S612), and checks the application acquisition destination information 905 of the acquired AIT data sequence. Furthermore, based on the information described in the application acquisition destination information 905 checked in S612, a transmission request for the broadcast cooperative app (TV side) is sent to a predetermined service provider server 400 via the LAN communication unit 121 (S613).

[0124] Upon receiving the transmission request for the broadcast-interactive app (television side), the service provider server 400, under the control of the application management / distribution execution unit 4103, performs authentication processing for the broadcast receiving device 100 as necessary, and then distributes the predetermined broadcast-interactive app (television side) stored in the application storage area 4013 via the LAN communication unit 421 (S614). Under the control of the application control unit 161, the application engine 162 of the broadcast receiving device 100 starts the predetermined broadcast-interactive app (television side) that has been received from the service provider server 400 via the LAN communication unit 121 (S615).

[0125] Next, the terminal cooperation control unit 191 of the broadcast receiving device 100 transmits to the mobile information terminal 700, information such as URL information of the acquisition source of the broadcast cooperation app (terminal side) to be executed on the mobile information terminal 700, which information was acquired from the AIT or the broadcast cooperation app (television side) executed in S615 (S616). The cooperation control execution unit 7102 of the mobile information terminal 700 transmits a transmission request of the broadcast cooperation app (terminal side) to a predetermined service provider server 400 via the LAN communication unit 721, based on the URL information of the acquisition source of the broadcast cooperation app (terminal side) received via the LAN communication unit 721 (S617).

[0126] Upon receiving the transmission request for the broadcast-linked app (terminal side), the service provider server 400, under the control of the application management / distribution execution unit 4103, performs authentication processing for the mobile information terminal 700 as necessary, and then distributes the predetermined broadcast-linked app (terminal side) stored in the application storage area 4013 via the LAN communication unit 421 (S618). The HTML browser engine 7103 of the mobile information terminal 700 starts the predetermined broadcast-linked app (terminal side) received from the service provider server 400 via the LAN communication unit 721 (S619).

[0127] 7A to 7C , the AIT file can be acquired from a predetermined server device, and the broadcast-linked app can be acquired from broadcast waves rather than from a server device on a network. When the broadcast-linked app is acquired from broadcast waves, the broadcast receiving device 100 may acquire the broadcast-linked app (terminal side) to be executed on the mobile information terminal 700 from the broadcast waves and transfer the acquired broadcast-linked app (terminal side) to the mobile information terminal 700 via the communication unit 121. Alternatively, the broadcast receiving device 100 may acquire the broadcast-linked app (terminal side) to be executed on the mobile information terminal 700 from the broadcast waves and store it in the storage unit 110, and in the process of S616 in FIG. 9 , transmit location information of the storage unit 110 of the broadcast receiving device 100 as URL information to be transmitted to the mobile information terminal 700. The broadcast receiving device 100 may acquire the broadcast-linked app (TV side) from broadcast waves, and the mobile information terminal 700 may acquire the broadcast-linked app (terminal side) from a server device on the network. The mobile information terminal 700 may also acquire the broadcast-linked app (terminal side) directly from broadcast waves using a digital broadcast receiving function that the mobile information terminal 700 has.

[0128] In addition, the operation sequences of Figures 7A to 7C, Figures 8A to 8C, and Figure 9 can be partially combined as appropriate, and some operation steps can be rearranged in order or operated simultaneously with other operation steps as appropriate.

[0129] [Mobile device linkage control app basic screen] 10A is a screen display diagram showing an example of a basic screen of the cooperative control app displayed by the process of S407 in Fig. 8A, the process of S506 in Fig. 8B, the process of S611 in Fig. 8C, etc. In this embodiment, the basic screen 741a of the cooperative control app has the function of a high-performance remote control compatible with the broadcast receiving device 100.

[0130] 10A, the basic screen 741a of the linked control app is configured with a power key 741a1, a network selection key (digital terrestrial, BS, CS) 741a2, number keys (1 to 12) 741a3, volume UP / DOWN keys 741a4, channel UP / DOWN keys 741a5, input switch key 741a6, program guide key 741a7, data key 741a8, linked app key 741a9, menu key 741aa, back key 741ab, cursor keys (up, down, left, right) 741ac, enter key 741ad, and color keys (blue, red, green, yellow) 741ae. Other operation keys may also be displayed.

[0131] For ease of use, the operation keys may have the same key layout / operation as that of a dedicated remote control attached to broadcast receiving device 100. Furthermore, power key 741a1, network selection key 741a2, numeric keys 741a3, etc. have the same functions as the operation keys of a known television remote control, and detailed description thereof will be omitted. Linked application key 741a9 is an operation key provided for the broadcast / communication linking function of this embodiment.

[0132] In the processing of S204 in Fig. 7B and S305 in Fig. 7C, it is assumed that data broadcasting can be started / ended by selecting the data key 741a8. Also, in the processing of S208 in Fig. 7B and S310 in Fig. 7C, it is assumed that the executable broadcast-linked application can be selected by operating the cursor keys 741ac and the enter key 741ad. Also, in the processing of S306 in Fig. 7C, it is assumed that a request to start the broadcast-linked application launcher can be made by selecting the linked application key 741a9.

[0133] In this way, by providing linked application key 741a9 or another operation key having a similar function on basic screen 741a of the linked control application, it becomes possible to easily select / launch each broadcast linked application used in the broadcast linked system of this embodiment. Also, linked application key 741a9 or another operation key having a similar function may be provided on a dedicated remote control attached to broadcast receiving device 100.

[0134] FIG. 10B is a screen display diagram showing an example of the basic screen of the collaborative control app displayed by processing S407 in FIG. 8A, processing S506 in FIG. 8B, processing S611 in FIG. 8C, etc., and is an example different from FIG. 10A.

[0135] The basic screen 741b of the cooperative control app is composed of a cooperative control in progress message 741b1 and a cooperative control app operation screen 741b2. Other objects may also be displayed. The cooperative control in progress message 741b1 is a message display that notifies the user that the mobile information terminal 700 is operating in cooperation with the broadcast receiving device 100. The cooperative control app operation screen 741b2 is an area where any screen display is performed by the cooperative control app, and detailed description thereof will be omitted in this embodiment. For example, the configuration within the cooperative control app operation screen 741b2 may be the same as the configuration of the basic screen 741a of the cooperative control app described above. A sub-screen of a broadcast program being displayed on the broadcast receiving device 100 may also be displayed.

[0136] 10B, by displaying cooperative control in progress message 741b1, the user of mobile information terminal 700 can easily understand that mobile information terminal 700 is operating in cooperative control with broadcast receiving device 100. Note that cooperative control in progress message 741b1 is not limited to text display, and may be symbol display, graphic display, etc. A different background color, etc. may be used as an alternative to cooperative control in progress message 741b1.

[0137] [Data broadcasting screen on broadcast receiving device] Fig. 11 is a screen display diagram showing an example of a data broadcast screen displayed by the processing of S205 in Fig. 7B. In this embodiment, it is assumed that three broadcast cooperative applications, i.e., cooperative application A, cooperative application B, and cooperative application C, are executable on the broadcast receiving device 100 based on the description in the AIT, etc. In this case, an entry button 173a2 for cooperative application A, an entry button 173a3 for cooperative application B, and an entry button 173a4 for cooperative application C are displayed at arbitrary positions on the data broadcast screen 173a.

[0138] On the data broadcasting screen 173a as shown in FIG. 11, when the entry button 173a2, entry button 173a3, entry button 173a4, etc. is selected using the cursor keys 741ac and the decision key 741ad on the basic screen 741a of the collaborative control app, the display of the data broadcasting screen 173a is terminated and collaborative app A, collaborative app B, collaborative app C, etc. are launched under the control of the application control unit 161 and the application engine 162.

[0139] When displaying data broadcast screen 173a, the frame color, interior color, shape, font, size, blinking status, etc. of each entry button may be changed as appropriate depending on the type of broadcast cooperative application, security status, etc. For example, if cooperative application A is a broadcast-managed application, the frame color of entry button 173a2 may be blue; if cooperative application B is a non-broadcast-managed application, the frame color of entry button 173a3 may be yellow; if cooperative application C is a general application, the frame color of entry button 173a4 may be red; etc. Alternatively, if cooperative application A is determined to be reliable in terms of security, the frame color of entry button 173a2 may be blue; if cooperative application B is determined not to be necessarily reliable in terms of security, the frame color of entry button 173a3 may be yellow; and if cooperative application C is determined to be a security risk, the frame color of entry button 173a4 may be red; etc.

[0140] In addition, the frame color, interior color, shape, font, size, blinking status, etc. of each entry button may be changed as appropriate depending on the function or genre of the broadcast-linked app, or depending on the expiration date of each broadcast-linked app, etc. The frame color, interior color, shape, font, size, blinking status, etc. of each entry button may be changed as appropriate depending on whether the broadcast-linked app has already been acquired from the network, etc. For example, if the linked app A has already been acquired from the network (cached in RAM 104 or storage 110), the frame color of entry button 173a2 may be blue; if the linked app B is being acquired, the frame color of entry button 173a3 may be yellow; and if the linked app C has not yet been acquired, the frame color of entry button 173a4 may be red.

[0141] In this way, the user of the broadcast receiving device 100 can easily grasp the types of broadcast cooperative applications that can be executed on the broadcast receiving device 100, the security status, and the like.

[0142] [Broadcast-linked app launcher screen on broadcast receiving device] FIG. 12A is a screen display diagram showing an example of a notification screen for making the user aware that there is a broadcast cooperative app that can be launched in the broadcast receiving device 100 of this embodiment.

[0143] For example, in the operation sequence shown in Fig. 7C, after the processing of S304, the display of the broadcast program continues without launching either the data broadcast by the broadcast service or the broadcast-linked app. On the other hand, in this case, if an icon 173b0 as shown in Fig. 12A is displayed to let the user know that there is a broadcast-linked app that can be launched, the usability of the broadcast receiving device 100 is improved. In other words, by displaying the icon 173b0, it is possible to prevent the user from missing the existence of a broadcast-linked app that can be launched.

[0144] The icon 173b0 may be displayed anywhere on the screen, but it is desirable that it be displayed in a location that does not interfere with viewing of the broadcast program. For example, it may be displayed in one of the four corners of the screen. The icon 173b0 may be displayed as text as shown in FIG. 12A, or may be a symbol, graphic, or the like. The icon 173b0 may be displayed all the time, or may be displayed for a predetermined period of time after the power is turned on or the channel is changed. Alternatively, the icon 173b0 may be displayed simultaneously with program information, channel numbers, and the like.

[0145] 12B is a screen display diagram showing an example of a broadcast cooperative app launcher displayed by the processing of S306 in FIG. 7C. In this embodiment, it is assumed that three broadcast cooperative apps, cooperative app A, cooperative app B, and cooperative app C, are executable on the broadcast receiving device 100 based on the description in the AIT or the like. In this case, a broadcast cooperative app launcher 173b1 is displayed at an arbitrary position on the broadcast program screen 173b, and furthermore, an entry button 173b2 for cooperative app A, an entry button 173b3 for cooperative app B, an entry button 173b4 for cooperative app C, and a back button 173b5 are displayed within the broadcast cooperative app launcher 173b1.

[0146] 12B is displayed, when an entry button 173b2, an entry button 173b3, an entry button 173b4, or the like is selected using cursor keys 741ac and enter key 741ad on the basic screen 741a of the cooperative control app, cooperative app A, cooperative app B, cooperative app C, or the like is started under the control of the application control unit 161 and the application engine 162. When the back button 173b5 is selected, the display of the broadcast cooperative app launcher 173b1 is terminated.

[0147] When displaying the broadcast linked app launcher 173b1 on the broadcast program screen 173b, the frame color, inner color, shape, font, size, blinking status, etc. of each entry button may be changed as appropriate depending on the type and security status of the broadcast linked app, the function and genre of the broadcast linked app, the acquisition status of the broadcast app from the network, etc., just as when displaying the entry button of each broadcast linked app on the data broadcast screen 173a of Figure 11.

[0148] Furthermore, the broadcast linked application launcher 173b1 may not be displayed if there is no broadcast linked application that can be executed by the broadcast receiving device 100. Alternatively, in this case, a message such as "There is no available application" may be displayed inside the broadcast linked application launcher 173b1.

[0149] [Broadcast linkage app execution screen on broadcast receiving device] FIG. 13A is a screen display diagram showing an example of a broadcast cooperative app execution screen displayed in the process of S108 in FIG. 7A, the process of S213 in FIG. 7B, the process of S314 in FIG. 7C, the process of S615 in FIG. 9, etc. The broadcast cooperative app of this embodiment is equipped with graphics capabilities and effect capabilities using HTML description, and is capable of overlay display with a broadcast program screen on the video display unit 173. For example, as shown in FIG. 13A, a broadcast cooperative app unit 173c1 that displays information such as a weather forecast and news is overlaid and displayed at an arbitrary position on the broadcast program screen 173c. The broadcast cooperative app unit 173c1 is composed of a first main object 173c2, a second main object 173c3, a third main object 173c4, a background object 173c5, etc. Other objects may also be displayed.

[0150] When the broadcast cooperative app section 173c1 is overlaid on the broadcast program screen 173c, the execution of the broadcast cooperative app can be terminated and the display can be switched to the data broadcast screen by selecting the data key 741a8 on the basic screen 741a of the cooperative control app. Furthermore, the execution of the broadcast cooperative app can be terminated and the display can be switched back to the broadcast program screen 173c only by selecting the cooperative app key 741a9 on the basic screen 741a of the cooperative control app. The above process may be realized by a different operation key.

[0151] In addition, while the broadcast cooperative application section 173c1 is overlaid on the broadcast program screen 173c, the transparency of the broadcast cooperative application section 173c1 can be changed by operating each operation key on the basic screen 741a of the cooperative control application. The transparency change process may be performed collectively on the entire broadcast cooperative application section 173c1, or may be performed individually on the first main object 173c2, the second main object 173c3, the third main object 173c4, and the background object 173c5. It may also be performed for each predetermined group (for example, multiple objects existing on the same graphics layer).

[0152] When performing the transparency change process, for example, an object is selected using cursor keys 741ac on basic screen 741a of the collaboration control app, and the transparency of the object is increased by pressing the “blue” key on color keys 741ae and decreased by pressing the “yellow” key. The transparency change process may also be performed using different operation keys. By simultaneously setting the transparency of the entire broadcast collaboration app unit 173c1 to 100%, the broadcast collaboration app unit 173c1 can be temporarily hidden. For example, when an emergency broadcast is distributed via broadcast waves, the transparency of the entire broadcast collaboration app unit can be set to 100%, and only the broadcast program screen of the emergency broadcast can be displayed on video display unit 173. Alternatively, a commercial detection unit (not shown) may detect that the broadcast program has switched from the main video to a commercial video and control the transparency of the entire broadcast collaboration app unit 173c1 to 100% (or a transparency that allows the broadcast program video to be clearly seen).

[0153] By performing the above-described processing, if you want to check the broadcast program screen in the background while the broadcast linked app is running, you can do so without terminating the broadcast linked app.

[0154] 13B is a screen display diagram showing an example of the broadcast cooperative app execution screen displayed in the process of S108 in FIG. 7A, the process of S213 in FIG. 7B, the process of S314 in FIG. 7C, the process of S615 in FIG. 9, etc., different from those described above. In the example shown in FIG. 13B, a broadcast cooperative app section 173c6 introducing recommended programs is overlaid and displayed at an arbitrary position on the broadcast program screen 173c. The broadcast cooperative app section 173c6 displays first recommended program information 173c7, second recommended program information 173c8, third recommended program information 173c9, etc. More recommended program information may be displayed by scrolling, page switching, etc.

[0155] The recommended program information may be information on a program recommended in relation to the currently displayed broadcast program (broadcast program screen 173c), information on a program recommended based on the user's viewing history, or information on a program that is currently a hot topic on the Internet, etc. It may also be information on a recommended program sent to the user by a friend of the user of broadcast receiving device 100. The recommended program may also be a program transmitted by broadcast waves of a digital broadcast service, or a VOD (Video On Demand) program distributed from a server device on the Internet 200. It may also be an information screen such as a homepage prepared on a server device on the Internet 200.

[0156] When the broadcast collaboration app section 173c6 is overlaid on the broadcast program screen 173c, the first recommended program information 173c7, the second recommended program information 173c8, the third recommended program information 173c9, etc. can be selected using the cursor keys 741ac and the decision key 741ad on the basic screen 741a of the collaboration control app, and the program images recommended in the first recommended program information 173c7, the second recommended program information 173c8, the third recommended program information 173c9, etc. will be displayed on the display section 173.

[0157] FIG. 13C is a screen display diagram illustrating an example in which a program video recommended by the broadcast cooperative application section 173c6 that introduces recommended programs is displayed. For example, when first recommended program information 173c7 of the broadcast cooperative application section 173c6 is selected using the cursor keys 741ac and the enter key 741ad on the basic screen 741a of the cooperative control application, a program video 173ca of the program recommended by the first recommended program information 173c7 is displayed on the display section 173. The program video 173ca may be paused or jumped to by a specified time by a user operating the operation terminal. Furthermore, when displaying the program video 173ca, the original broadcast program screen 173c may be displayed at any position in a PIP (Picture-In-Picture) format. In this case, the user may be able to change whether the program video 173ca of the recommended program or the original broadcast program screen 173c is the main screen by operating the operation terminal. The window size of the original broadcast program screen 173c may be adjustable by operating the operation terminal.

[0158] Furthermore, by displaying an icon display 173cb at an arbitrary position on the screen, which indicates that the program video 173ca of the recommended program is a video displayed by selecting any of the recommended program information displayed in the broadcast-linked application section 173c6, convenience for the user can be improved. Needless to say, the transparency of the broadcast-linked application section 173c6 may also be changed on the broadcast-linked application execution screen shown in FIG. 13B in the same manner as described above.

[0159] 13D is a screen display diagram showing an example of a broadcast-linked app execution screen different from those described above, which is displayed in the process of S108 in FIG. 7A, the process of S213 in FIG. 7B, the process of S314 in FIG. 7C, the process of S615 in FIG. 9, etc. In the example shown in FIG. 13D, a broadcast-linked app section 173cc, which serves as a portal for an SNS (Social Networking Service) service, is overlaid and displayed at an arbitrary position on a broadcast program screen 173c. The broadcast-linked app section 173cc displays an entry button 173cd for a first SNS service, an entry button 173ce for a second SNS service, an entry button 173cf for a third SNS service, etc. Entry buttons for even more SNS services may be displayed by scrolling, page switching, etc.

[0160] With the broadcast cooperation app section 173cc overlaid on the broadcast program screen 173c, the cursor keys 741ac and the enter key 741ad on the basic screen 741a of the cooperation control app can be used to select an entry button 173cd for the first SNS service, an entry button 173ce for the second SNS service, an entry button 173cf for the third SNS service, or the like, to activate functions assigned to each entry button, such as a chat function, a bulletin board function, or an internet telephone function. This allows users to enjoy the currently displayed broadcast program (broadcast program screen 173c) while exchanging information with others. At the same time, the basic screen 741a of the cooperation control app on the mobile information terminal 700 may be changed to a character input screen such as a software keyboard or a voice input screen for chatting or posting on a bulletin board by voice input.

[0161] Furthermore, in addition to the above-described examples, the broadcast cooperative app executable by the broadcast receiving device 100 of this embodiment may be one that uses a cooperative function between the broadcast receiving device 100 and the mobile information terminal 700, and further synchronizes with the timing of broadcasting a commercial, so that a related commercial app is presented on both the broadcast receiving device 100 and the mobile information terminal 700. Alternatively, for a paid service available on the broadcast receiving device 100, the broadcast cooperative app may check whether the user of the broadcast receiving device 100 has subscribed to the paid service, and change the display of the broadcast receiving device 100 and / or the mobile information terminal 700 depending on the result. In the broadcast receiving device 100 of this embodiment, regardless of which broadcast cooperative app is executed, it is possible to enjoy the effects described using Figures 13A, 13B, etc.

[0162] [Broadcast receiver error display screen] Figure 14 is a screen display diagram showing an example of an error display screen when it is determined that the broadcast-linked app cannot be executed by checking the application profile 904 of the acquired AIT data string in the processing of S105 in Figure 7A, the processing of S207 in Figure 7B, the processing of S308 in Figure 7C, the processing of S605 in Figure 8C, etc., when there is an insufficient description in the AIT, or when acquisition of the AIT has failed.

[0163] In the broadcast receiving device 100 of this embodiment, when it is determined that the broadcast-linked app cannot be executed, the reason why the broadcast-linked app cannot be executed, such as the result of checking the application profile 904, is displayed in an error message 173d1. For example, if the result of checking the application profile 904 indicates that a predetermined optional function is missing from the television receiver, this information is displayed in the error message 173d1. An error code and a link (such as a URL) to the television receiver manufacturer's website containing an explanation of the error code may also be displayed. Alternatively, when the broadcast-linked app is acquired from a network, the network connection status is naturally checked in advance. At this time, if the broadcast-linked app cannot be acquired due to, for example, an improper LAN cable connection, this information is displayed in the error message 173d1. Furthermore, the error message 173d1 may also be displayed when a network connection is established but the broadcast-linked app cannot be properly acquired due to poor error conditions. The error message 173d1 may also be displayed when the broadcast-linked app is not yet ready to be executed while the broadcast-linked app is being acquired. Error message 173d1 may also be displayed when the broadcast wave reception status is unstable and information such as the AIT can be received at first but then becomes unable to be received halfway through, etc. In such a case, if the broadcast-linked app obtained from each server device is cached as is, it can be used as is after the broadcast wave reception status is restored.

[0164] Furthermore, if the result of checking the application profile 904 indicates that the television receiver lacks a predetermined optional function, an error message 173d1 may be displayed recommending checking for or updating the latest television receiver firmware. Alternatively, the broadcast receiving device 100 may automatically check for or update the latest firmware. Alternatively, if the broadcast-linked app can be executed by adding paid optional hardware or optional software to the television receiver, information about the paid optional hardware or optional software may be displayed. Note that the error message 173d1 may be displayed on the mobile information terminal 700 rather than on the broadcast receiving device 100.

[0165] [Broadcast linkage app execution screen on mobile information terminal] Fig. 15 is a screen display diagram showing an example of the broadcast cooperative app (terminal side) execution screen displayed in the processing of S619 in Fig. 9. The broadcast cooperative app execution screen 741c shown in Fig. 15 is composed of a main window 741c1, a sub-window 741c2, a selection marker 741c3, cursor keys 741c4 and 741c5, an explanation display section 741c6, and an end button 741c7. Other objects may also be added.

[0166] In this embodiment, the broadcast cooperative app (terminal side) executed on the mobile information terminal 700 is an application for checking details of a broadcast program being displayed on the broadcast receiving device 100. The main window 741c1 displays the same image as the broadcast program screen being displayed on the broadcast receiving device 100, and the sub-window 741c2 displays an enlarged image of a position designated by a selection marker 741c3. The position of the selection marker 741c3 can be changed by selecting cursor keys 741c4 and 741c5. The commentary display area 714c6 displays commentary subtitles about the broadcast program being displayed on the main window 741c1, comments posted by other users about the broadcast program, and the like. The end button 741c7 is a button for terminating the operation of the broadcast cooperative app (terminal side).

[0167] By running the broadcast cooperative application (terminal side) on the mobile information terminal 700, the broadcast receiving device 100 and the mobile information terminal 700 can operate in cooperation with each other to expand the functionality of the broadcast communication cooperative service.

[0168] [EPG screen of broadcast receiver] 16A is a screen display diagram showing an example of an electronic program guide (EPG) display screen in the broadcast receiving device 100 of this embodiment. The EPG display screen 173e is a distribution schedule of broadcast programs in the digital broadcast service of this embodiment, which is created by the main control unit 101 based on the program information data string output from the first separation unit 132. By selecting the program guide key 741a7 on the basic screen 741a of the cooperation control app, the EPG display screen 173e is displayed on the video display unit 173.

[0169] In this embodiment, the EPG display screen 173e displays detailed information about each broadcast program broadcast on each channel in each time period in a matrix format with the vertical axis representing time and the horizontal axis representing service ID (channel). As shown in Fig. 16A, detailed information 173e1 about each broadcast program is mainly composed of a title area 173e2 and a detailed description area 173e3.

[0170] The title area 173e2 displays the program title of each broadcast program and symbols representing the attributes of each broadcast program. The symbols representing the attributes of each broadcast program are, for example, a symbolized "New" sign indicating that it is a new program, or a symbolized "Replay" sign indicating that it is a rebroadcast program. Alternatively, a symbolized "data" sign indicating that the program is compatible with data broadcasting via a broadcast service may be used. Furthermore, if the broadcast program is available with a broadcast-linked app that can be executed by the broadcast receiving device 100 of this embodiment, a symbolized "Linkage" sign indicating this may be used. The detailed explanation area 173e3 displays related information such as the program content and performers of each broadcast program, the URL of a website introducing each broadcast program, etc.

[0171] Note that the symbolized mark "Linkage" displayed in the title area 173e2 may not be displayed if the result of checking the application profile 904 indicates that the broadcast program cannot be executed on the information display device 100, even if the broadcast program has a broadcast-linked app available. Also, the symbolized mark "Linkage" displayed in the title area 173e2, which indicates that the broadcast program has an executable broadcast-linked app available, may have its color, shape, font, etc. changed depending on whether or not the program can be operated in cooperation with a mobile terminal device. If the program can be operated in cooperation with a mobile terminal device, a symbolized mark "Mobile" may be displayed together with the symbolized mark "Linkage."

[0172] Whether or not to display the symbolic mark "Linkage" or the symbolic mark "Mobile" can be controlled by acquiring information, which is previously written in EIT information including detailed information about each broadcast program, such as whether or not each broadcast program is a broadcast program for which a broadcast-linked app executable by the broadcast receiving device 100 of this embodiment is prepared, and whether or not the executable broadcast-linked app is capable of operating in conjunction with a mobile terminal device. Alternatively, the information acquired from program distribution information of digital broadcast programs prepared in a predetermined server device on the Internet 200 may be added to an electronic program guide created based on a program information data string acquired from broadcast waves of a digital broadcast service.

[0173] As described above, by displaying a symbolic mark "Linkage" indicating that a broadcast program has an executable broadcast-linked app available and a symbolic mark "Mobile" indicating that the program can be linked with a mobile terminal device on the EPG display screen 173e, the user can easily understand the compatibility of each broadcast program with the broadcast-communication linked service on the broadcast receiving device 100. Needless to say, the symbolic mark representing the predetermined characters that represent the attributes of each broadcast program may be replaced with the characters themselves, sentences, etc. The compatibility of each broadcast program with the broadcast-communication linked service may be indicated by changing the background color of the detailed information 173e1 of each broadcast program. Furthermore, the symbolic mark "Linkage" or the symbolic mark "Mobile" may not normally be displayed in the title area 173e2, but may be displayed as a pop-up only when the broadcast program is selected with the program selection cursor 173e4.

[0174] The broadcast receiving device 100 of this embodiment has a function of scheduling viewing and / or recording of each broadcast program on the EPG display screen 173 e. For example, while the EPG display screen 173 e is displayed, the user can use the cursor keys 741 ac on the basic screen 741 a of the cooperative control application to move the program selection cursor 173 e 4 on the EPG display screen 173 e, and select any broadcast program with the enter key 741 ad to schedule viewing and / or recording of the selected broadcast program.

[0175] In the above process, if the broadcast program for which the viewing reservation and / or recording reservation has been made is a broadcast program compatible with a broadcast-communication cooperative service, the viewing reservation and / or recording reservation may be used as a trigger to start acquiring a broadcast-interactive app prepared for the broadcast program without waiting for the broadcast start time of the broadcast program. That is, information specifying the acquisition source of the broadcast-interactive app (location information such as a URL) may be included in EIT information containing detailed information about each broadcast program. In this way, the broadcast receiving device 100 can grasp information about the acquisition source of the broadcast-interactive app prepared for each broadcast program when the broadcast program is selected with the program selection cursor 173e4. Therefore, the broadcast receiving device 100 can start acquiring the broadcast-interactive app before the broadcast start time of the broadcast program.

[0176] In addition, if the broadcast program for which the viewing reservation and / or recording reservation has been made is a broadcast program that supports a broadcast communication cooperative service and is capable of cooperative operation with a mobile terminal device, the broadcast cooperative app (terminal side) prepared for the mobile terminal device may also start acquiring the broadcast cooperative app before the broadcast start time of the broadcast program using the same process as described above. Also, as shown in Fig. 16B, a two-dimensional barcode 173e5 or the like indicating information (location information such as a URL) of the acquisition destination of the broadcast cooperative app (terminal side) prepared for the mobile terminal device may be displayed on the EPG display screen 173e to prompt the user to download the broadcast cooperative app (terminal side) prepared for the mobile terminal device.

[0177] In this way, if the broadcast receiving device 100 refers to the acquisition source information of the broadcast-linked app included in the EPG information and starts acquiring the broadcast-linked app before the broadcast start time of the broadcast program, it becomes possible to distribute the load on the service provider server 400 that stores the broadcast-linked app. Furthermore, even if the communication speed of the network between the service provider server 400 and the information display terminal 100 is insufficient, it becomes possible to effectively use the broadcast-linked app immediately after the broadcast start time of the broadcast program.

[0178] FIG. 17 is an operational sequence diagram showing an example of a broadcast cooperative app acquisition sequence when a broadcast program viewing reservation and / or recording reservation is made on the EPG display screen 173e.

[0179] While viewing a digital broadcast service, the main control unit 101 of the broadcast receiving device 100 acquires a program information data sequence output from the first separation unit 132 (S701). When the user requests the launch of an EPG screen using the operation terminal (S702), an EPG display screen 173e is displayed on the video display unit 173 (S703). When the user selects an arbitrary broadcast program on the EPG display screen 173e using the operation terminal to schedule viewing and / or recording of the broadcast program (S704), the main control unit 101 checks the program information data sequence acquired from the first separation unit 132 (S705), and further checks the location of the acquisition source of a broadcast-linked app linked to the broadcast program scheduled for viewing and / or recording (S706).

[0180] After the processing of S706, the application control unit 161 transmits a broadcast-interactive app transmission request to the predetermined service provider server 400 via the LAN communication unit 121 based on the confirmed URL (S707). The service provider server 400 that has received the broadcast-interactive app transmission request performs authentication processing of the broadcast receiving device 100 as necessary based on the control of the application management / distribution execution unit 4103, and then distributes the predetermined broadcast-interactive app stored in the application storage area 4013 via the LAN communication unit 421 (S708). Next, the application control unit 161 caches the predetermined broadcast-interactive app received from the service provider server 400 via the LAN communication unit 121 in the RAM 104 or the storage 110 (S709).

[0181] According to the transceiver 100 of the present embodiment described above, it is possible to execute functions with higher added value. [Example]

[0182] The following describes Example 2 of the present invention. The configuration, effects, etc. of this Example are the same as those of Example 1 unless otherwise specified. Therefore, the following mainly describes the differences between this Example and Example 1, and omits explanations of common points as much as possible to avoid duplication.

[0183] In the first embodiment, an embodiment in which mobile information terminal cooperation processing (hereinafter referred to as terminal cooperation) is performed has been described, but a more detailed embodiment will be described below.

[0184] When performing mobile information terminal linkage, there are cases where it is desired to limit the use of terminal linkage to only mobile information terminals 700 that are located in the same home as broadcast receiving device 100 (hereinafter, this restriction will be referred to as "same-home restriction"). For example, this may be the case when, in an application for using broadcast linkage (hereinafter, referred to as "broadcast linkage app"), the display screen of broadcast receiving device 100 and the display screen of mobile information terminal 700 are closely related, or when it is desired to ensure that the user of mobile information terminal 700 can view advertising video displayed on broadcast receiving device 100.

[0185] Note that one point that must be considered in the procedure is whether or not the broadcast-linked app in question imposes a same-house restriction. If it is assumed that all broadcast-linked apps are subject to a same-house restriction, this determination is not necessary. However, if there are cases where there is no restriction, the broadcast receiving device 100 must acquire control information regarding the presence or absence of a same-house restriction and change the operating procedure. This control information regarding the presence or absence of a restriction may be acquired from the broadcast signal (for example, described as an item in the AIT) or may be acquired from a server designated by the broadcast station.

[0186] In this embodiment, including the above procedure, a procedure for ensuring that the mobile information terminal 700 is present in the same home as the broadcast receiving device 100 will be described.

[0187] Typically, devices that exist within the same home are on a local network that is connected to the same router device 210. Therefore, if the mobile information terminal 700 is connected to the same local network as the broadcast receiving device 100, it can be determined that they exist within the same home. Note that whether or not a target device is connected to a local network can be determined using a known method, and therefore a description thereof will be omitted.

[0188] Furthermore, even if the mobile information terminal 700 is not on the local network, it can be determined that it is present in the same home by directly communicating with the broadcast receiving device 100 using NFC, Bluetooth, infrared communication, etc. In this case, the communication for acquiring the broadcast collaborative app, etc. may be the above-mentioned direct communication or may be via mobile telephone communication.

[0189] As described above, there are several possible methods for confirming that the devices are in the same house. The method to be used is described in, for example, the AIT, which is read by the broadcast receiving device 100.

[0190] Furthermore, once it is confirmed that the mobile information terminal 700 is in the same home, it may be considered to be in the same home until the program ends, or a certain valid time (for example, 10 minutes) may be set, during which it is considered to be in the same home, but once the valid time has elapsed, it is not considered to be in the same home unless a new confirmation is made. This valid time may be written in, for example, the AIT and read by the broadcast receiving device 100.

[0191] Furthermore, for example, an event signal may be set in the broadcast signal at any point during the program, and each time this event signal is received, it may be confirmed that the mobile information terminal 700 is in the same home.

[0192] Furthermore, the first two methods can be used in combination.

[0193] Next, a specific procedure for permitting terminal linkage only for mobile information terminals 700 present in the same home will be described. In this embodiment, restrictions are imposed when the mobile information terminal 700 acquires a broadcast-linked app or acquires information used in the broadcast-linked app (hereinafter, the broadcast-linked app and the information used in the broadcast-linked app, specifically, HTML documents, streaming video, etc., are collectively referred to as broadcast-linked information). There are two methods for acquiring broadcast-linked information: communication acquisition from the broadcast station server 300 or the provider server 400, and broadcast acquisition from broadcast waves. In the case of communication acquisition, there are two methods: acquisition after broadcast reception starts, and acquisition before broadcast reception starts. Furthermore, in the case of communication acquisition, there are two cases: the broadcast receiving device 100 acquires the information once, and the mobile information terminal 700 acquires it from the broadcast receiving device 100, and there are also cases where the mobile information terminal 700 acquires it directly from the broadcast station server 300 or the provider server 400. There are various methods, but from the viewpoint of the mobile information terminal 700, they can be roughly divided into two: obtaining from the broadcast receiving device 100, and obtaining from the broadcast station server 300 or the operator server 400.

[0194] In this embodiment, a case where the mobile information terminal 700 acquires broadcast cooperation information from the broadcast receiving device 100 will be described, and a case where the information is acquired from a server will be described in the next embodiment.

[0195] FIG. 18A shows the procedure of this example.

[0196] First, before performing terminal linkage, a linkage control app, which is an application that controls terminal linkage, is launched in each of the mobile information terminal 700 and the broadcast receiving device 100 (S10001, S10002). In this state, a terminal linkage request is made from the mobile information terminal 700 to the broadcast receiving device 100 (S10003). Next, an AIT is acquired from the broadcast signal (S10004). From the information in this AIT, it is determined whether the app for the target mobile information terminal has a same-house restriction (S10006). If there is a restriction, the process proceeds to step S10008. In the initial stage where a terminal linkage request is made, the process proceeds to step S10009, where it is determined whether the mobile information terminal 700 that made the terminal linkage request is located in the same home as the broadcast receiver 100 (S10009). If it is determined that they are not located in the same home, a linkage denial response is sent to the linkage control app on the mobile information terminal, and the process ends (S10011).

[0197] Here, if it is assumed that all broadcast-linked apps have the same-house restriction, the determination in S10006 is skipped. If there is a possibility that both apps have the same-house restriction and apps do not, the determination in S10006 is performed.

[0198] If it is determined that the mobile information terminal 700 is located within the same home, or if the app does not have a same-home restriction, the process proceeds to S10012, where a broadcast-linked app-related service is performed. This service (S10012) processes a broadcast-linked information distribution request (S10013) from the mobile information terminal 700, and distributes broadcast-linked information to the mobile information terminal 700 (S10018). This broadcast-linked information may be distributed by the broadcast receiving device 100 from a distribution server that is the provider server 300 (S10014, S10015, S10016), obtained from a broadcast signal (S10017), or stored in the broadcast receiving device 100. The broadcast receiving device 100 may receive the broadcast linked information (S10016, S10017) not only in response to a broadcast linked information distribution request (S10013) from the mobile information terminal 700, but also autonomously by the broadcast receiving device 100 or may acquire the information based on the occurrence of an event from a broadcast signal. Furthermore, the broadcast linked information may also be distributed to the mobile information terminal 700 (S10018) voluntarily by the broadcast receiving device 100.

[0199] After the series of processes of receiving (obtaining) and distributing broadcast linkage information is completed, the broadcast receiving device 100 determines whether the user is continuing to watch the same program (S10019), and if not, responds to the linkage control app on the mobile information terminal that linkage is not permitted, and the process ends (S10020).

[0200] If viewing continues, the process returns to S10005. If there is a home restriction, the process checks whether the mobile information terminal 700 is within the same home (S10009). It then determines whether a preset valid time has elapsed since the last check, or whether a confirmation request (S10007) has been generated from the broadcast signal or distribution server since the last check (S10008). If neither of these conditions is met, the process does not check whether the mobile information terminal 700 is within the same home (S10009), and proceeds via S10010 to the execution of the next broadcast-linked app-related service (S10012). Here, the process describes that the confirmation request from the broadcast signal (S10007) is to be acquired from the broadcast-linked information, but here, the process also describes that the event message is included in the broadcast-linked information. Furthermore, this confirmation request may be described in the AIT.

[0201] The procedure described above is a loop processing procedure involving the broadcast signal, broadcast receiving device 100, mobile information terminal 700, and distribution server in the section indicated by the arrow of S10022. The confirmation request of S10007 may be made at any time within the loop.

[0202] Furthermore, the authentication information described in the AIT may be incorporated into the authentication key used for authentication in the distribution server (S10015). This makes it possible to confirm that the authentication request is legitimate. Also, by changing the authentication information described in the AIT as the program progresses and configuring the distribution server to not perform authentication unless it uses an authentication key incorporating information synchronized with the program progress, it is possible to confirm that the same program is being continuously viewed. In this case, the information in the AIT is read and updated as appropriate (S10021). Note that the authentication information to be incorporated into the broadcast signal may be incorporated as broadcast-linked information in addition to being described in the AIT. Furthermore, as a method of essentially changing the authentication information, a method of changing the URL of the distribution server itself as the program progresses can also be used.

[0203] In this way, while executing the broadcast-linked app-related service (S10012), the mobile information terminal 700 checks whether it is in the same home as the broadcast receiving device 100 at predetermined valid time intervals or whenever there is a confirmation request from a broadcast signal or distribution server, thereby making it possible to appropriately execute broadcast-related apps that are restricted to being in the same home. Furthermore, by using authentication information incorporated in the broadcast signal for authentication by the distribution server, the legitimacy of the distribution request can be ensured, and by appropriately changing the authentication information in the broadcast signal, it is also possible to confirm that the same program is being continuously viewed.

[0204] According to the mobile information terminal cooperation technology according to the present embodiment described above, it is possible to realize the same-house restriction for mobile information terminals that cooperate with a broadcast receiving device. [Example]

[0205] In this embodiment, a case will be described in which the mobile information terminal 700 acquires broadcast cooperation information from a distribution server.

[0206] FIG. 18B shows the procedure of this example.

[0207] First, before performing terminal linkage, a linkage control app, which is an application that controls terminal linkage, is launched in each of the mobile information terminal 700 and the broadcast receiving device 100 (S10101, S10102). In this state, the mobile information terminal 700 sends a terminal linkage request to the broadcast receiving device 100 (S10103). Next, an AIT is acquired from the broadcast signal (S10104). Information such as a URL related to the distribution server is acquired from the information in the AIT, and this information is transmitted to the mobile information terminal 700 (S10105). Next, a time confirmation request is issued from the broadcast receiving device 100 to the distribution server (S10106), and based on this request, the distribution server transmits time information to the broadcast receiving device 100 (S10107). This allows the subsequent authentication key issuance (S10115) to be synchronized with the time on the distribution server, but this step may be omitted if the time difference is not a problem.

[0208] After this, the loop control indicated by the arrow at S10127 is entered.

[0209] First, the mobile information terminal 700 issues a request for issuing an authentication key or a broadcast linked information distribution request to the broadcast receiving device 100 (S10109). The authentication key is used in a broadcast linked information distribution request to the distribution server at a later stage (S10125). The broadcast linked distribution request at S10109 is a distribution request for information acquired from a broadcast signal, and corresponds to the procedure at S10126 at a later stage.

[0210] In either case, when the request of S10109 is issued from the mobile information terminal, it is determined whether the broadcast-linked app has a same-household restriction (S10111). If there is a restriction, the process proceeds to the next step S10112. If there is no restriction, step S10112 is skipped and the process proceeds to S10114. If all broadcast-linked apps have a same-household restriction, the determination of S10111 is not performed and the process proceeds to S10112. In S10112, it is determined whether the mobile information terminal that issued the request is within the same home. If not, the device linkage is terminated (S10113). If the mobile information terminal is within the same home, the requested procedure is performed: acquiring broadcast-linked information from the distribution server (S10125) or acquiring broadcast-linked information from the broadcast signal (S10126). Since acquisition from the broadcast signal is possible in addition to acquisition from the distribution server, the procedure of S10126 is also described.

[0211] First, the procedure for acquiring broadcast linkage information from the distribution server (S10125) will be described.

[0212] First, the broadcast receiver 100 issues the authentication key requested by the information-linked terminal 700. At this time, the authentication key includes time information at the time of issuance and is valid only for a predetermined period of time (for example, 10 minutes). The distribution server checks the authentication information, including whether the authentication key is within the valid period, and if the authentication is OK, allows the distribution of broadcast-linked information. Thereafter, the distribution of information is allowed within the valid period, but the distribution stops once the valid period has elapsed. For example, streaming video will no longer be viewable once the valid period has elapsed.

[0213] The preset validity period may be stored in the distribution server, or may be acquired by broadcast receiving device 100 from a broadcast signal (e.g., AIT) and the validity period information may be incorporated into the authentication key. The validity period information may be notified to mobile information terminal 700 in advance, so that the mobile information terminal 700 may request the issuance of an authentication key before the validity period expires. Alternatively, the validity period may be managed by broadcast receiving device 100, and an authentication key may be automatically issued to mobile information terminal 700 from broadcast receiving device 100 before the validity period expires after confirming that the mobile information terminal 700 is within the same home.

[0214] The validity period may be the same for the entire program, or may change as the program progresses. If no validity period is set, authentication may be performed once and remain valid for the duration of the program.

[0215] Furthermore, the authentication information described in the AIT may be incorporated into the authentication key used for authentication in the distribution server (S10117). This makes it possible to confirm that the authentication request is legitimate. Furthermore, by changing the authentication information described in the AIT as the program progresses and configuring the distribution server to not perform authentication unless it uses an authentication key incorporating information synchronized with the program progress, it is possible to confirm that the same program is being continuously viewed. In this case, the information in the AIT is read and updated as appropriate (S10124). Note that the authentication information to be incorporated into the broadcast signal may be incorporated as broadcast-linked information in addition to being described in the AIT. Furthermore, as a method for essentially changing the authentication information, a method can be used in which the URL of the distribution server itself is changed as the program progresses. Note that the URL change in this case is when the distribution server is the same but the entrance is different. However, it is also possible to change to a new distribution server due to a change in the broadcast-linked app, etc. In this case, the procedures of transmitting distribution server information (S10105), requesting time confirmation (S10106), and transmitting time information (S10107) are performed each time a change is made.

[0216] Next, the procedure for acquiring broadcast cooperation information from a broadcast signal (S10126) will be described.

[0217] In this case, after it is confirmed that the mobile information terminal 700 is in the same home, the broadcast receiving device 100 acquires broadcast linkage information from the broadcast signal (S10119), and then distributes the information to the mobile information terminal 700 (S10120).

[0218] In addition, when the broadcast linked information is changed as the program progresses, a notification of the change may be sent from the broadcast signal (S10110), and the notification may trigger the acquisition of the broadcast linked information. In this case, if the broadcast linked information is acquired from the distribution server, the broadcast receiving device 100 issues an authentication key to the mobile information terminal (S10115) and notifies the mobile information terminal of the change notification. If the validity period is within the validity period, the issuance of the authentication key may be omitted and only the change notification may be sent. In the case of acquisition from the broadcast signal, the broadcast receiving device 100 acquires the information (S10119) and distributes it to the mobile information terminal (S10120). In addition, in the case of acquisition from the broadcast signal, it may be possible to confirm that the mobile information terminal 700 is in the same home for each change notification, or, as in the second embodiment, this confirmation may be omitted if the validity period is within the validity period. Here, although the change notification from the broadcast signal (S10110) is described as being acquired from the broadcast linked information, the broadcast linked information is also described as including an event message. Furthermore, this change notice may be included in the AIT.

[0219] After a series of processes for receiving (obtaining) and distributing broadcast linkage information is completed, the broadcast receiving device 100 determines whether the user is continuing to watch the same program (S10121), and if not, responds to the linkage control app on the mobile information terminal that linkage is not permitted, and ends the process (S10123). If viewing is continuing, the process returns to S10108, and loop process S10127 continues.

[0220] In this way, by including time information in the authentication key used to authenticate the distribution server and managing the validity period, it is possible to periodically confirm that the mobile information terminal 700 is in the same home as the broadcast receiving device 100, and to appropriately execute broadcast-linked apps that have same-home restrictions. Furthermore, by using the authentication information embedded in the broadcast signal for authentication by the distribution server, the legitimacy of the distribution request can be ensured, and by appropriately changing the authentication information in the broadcast signal, it is also possible to confirm that the same program is being viewed continuously.

[0221] According to the mobile information terminal linkage technology of this embodiment described above, it is possible to achieve same-home restrictions even when a mobile information terminal linked to a broadcast receiving device obtains broadcast linkage information from a distribution server. [Example]

[0222] In the second and third embodiments, procedures for realizing the same-home restriction in terminal linkage were described. However, depending on the broadcast-linked app, use from outside the home may also be permitted. This embodiment describes such a case. For example, when a program itself, such as a television shopping program, is public relations or advertising, it is desirable for the broadcaster if the broadcast-linked app can be used both inside and outside the home. For such programs, once the program is registered in the broadcast receiving device 100, use of the broadcast-linked app may be permitted regardless of whether the mobile information terminal 700 is inside the home. In this case, convenience would be enhanced if there was a broadcast-linked app that converts the broadcast video itself into streaming data and distributes it from the broadcast receiving device 100 to the mobile information terminal 700 via the Internet. The streaming data may be encrypted by the broadcast receiving device 100 for copyright protection. Whether the broadcast-linked app permits use from outside the home, including distribution of broadcast video outside the home, is specified in data within the broadcast signal (e.g., AIT).

[0223] The specific procedure is shown in FIG. 18C . Since some of the procedure is common to Examples 2 and 3, the description of the overlapping parts with Examples 2 and 3 will be omitted. When a terminal link request (S10203) is received from outside the home, if the application is permitted for use outside the home, the broadcast receiving device 100 confirms whether the requestor is a registered mobile information terminal (S10205) and then permits linkage. Here, if necessary, authentication may be performed between the mobile information terminal 700 and the broadcast receiving device 100 to protect the copyright of the broadcast video and broadcast linkage information (S10207). In this case, the authentication may be performed by the distribution server (S10207). Information regarding the necessity of copyright protection and information regarding the authentication method for copyright protection are obtained from the broadcast signal (e.g., described in the AIT), and control is performed accordingly. If this information is not stored in the broadcast signal, a predetermined method is followed in the broadcast receiving device 100. For example, a predetermined copyright protection process may be performed. Furthermore, if such information is not stored in the broadcast signal, it may be predetermined that the broadcast receiving device 100 will not perform copyright protection processing.

[0224] Specific examples of authentication for copyright protection are shown below. Each of the following authentications may be performed alone. Alternatively, multiple authentications exemplified below may be performed in combination. Furthermore, the authentications exemplified below may be performed in combination with other authentication processes not exemplified below.

[0225] [ID and password authentication] When the mobile information terminal 700 is registered with the broadcast receiving device 100, an ID and password are issued, and the broadcast receiving device 100 permits cooperation by verifying this ID and password.

[0226] [Encryption key usage] In addition to the authentication using the ID and password, an encryption key for decrypting encrypted video data, etc. is transmitted from the broadcast receiving device 100 to the mobile information terminal. This encryption key may be obtained from the broadcast signal (for example, written in the AIT).

[0227] [Use of distribution server] In this method, an encryption key for decrypting encrypted video data, etc., is issued from the distribution server. The mobile information terminal 700 transmits an ID and password to the distribution server and obtains the encryption key. In this case, security is further enhanced by obtaining location information (specifically, a URL) of the distribution server from the broadcast signal (e.g., written in the AIT) and transmitting this location information from the broadcast receiving device 100 to the mobile information terminal 700. Since the mobile information terminal 700 cannot decrypt videos, etc. unless it can obtain the encryption key, the broadcast receiving device 100 may request authentication from the distribution server as authentication for copyright protection, or the authentication may be completed by the mobile information terminal 700 notifying the broadcast receiving device 100 that the encryption key has been obtained. Note that the distribution server may perform billing.

[0228] [Mutual authentication of encryption keys] The broadcast receiving device 100 and the mobile information terminal 700 mutually authenticate and confirm the encryption keys they each have, thereby authenticating copyright protection.

[0229] When information stored in a broadcast signal indicates that copyright protection is required by a predetermined method, if the copyright protection cannot be authenticated by the predetermined method, terminal linkage is not permitted. Also, even if there is no designation in the broadcast signal and authentication is performed by a default method of the broadcast receiving device 100, if the copyright protection cannot be authenticated by the default method, terminal linkage is not permitted.

[0230] If terminal linkage is permitted, thereafter, the presence of the mobile information terminal 700 within the same home is not confirmed. Instead, broadcast linkage information is delivered to the mobile information terminal 700 (S10217) and an authentication key for the distribution server is issued (S10212) in accordance with a request from the mobile information terminal 700 (S10211), autonomous control of the broadcast receiving device 100, and a request from the broadcast signal (S10210). In this case, control that sets the validity period does not have to be performed. The mobile information terminal 700 located outside the home acquires broadcast linkage information from the broadcast receiving device 100 or the distribution server using the issued authentication key (S10215). Furthermore, if the authentication key issued by the broadcast receiving device 100 incorporates authentication information acquired from the broadcast signal (e.g., described in the AIT), and the distribution server permits access if the authentication key incorporates the authentication information acquired from the broadcast signal, further optimization of outside-home use can be achieved.

[0231] Furthermore, in some cases, such as when offering a discount as a premium for viewing a program, it may be better not to permit unlimited use of the broadcast-linked app. In such cases, it is preferable to perform authentication once while the mobile information terminal is in the same home, and then permit use of the distribution server even if the mobile information terminal is not in the same home. In this case, it does not matter if the mobile information terminal 700 is not registered in the broadcast receiving device 100.

[0232] Specific procedures for this case are shown in FIG. 18D. Since some of the procedures are common to those shown in FIG. 18C, the overlapping portions will not be described. First, when the mobile information terminal 700 is located in the same home as the broadcast receiving device 100, the mobile information terminal 700 sends a terminal linkage request to the broadcast receiving device 100. The broadcast receiving device 100 confirms that the mobile information terminal 700 is located in the same home (S10305) and then permits linkage. If necessary, authentication may be performed between the mobile information terminal 700 and the broadcast receiving device 100 to protect the copyright of the broadcast video and broadcast linkage information (S10307). In this case, authentication may be performed by an external distribution server. Information regarding the necessity of copyright protection and information regarding the authentication method for copyright protection are obtained from the broadcast signal (e.g., described in the AIT), and control is performed accordingly. If this information is not stored in the broadcast signal, a predetermined method is followed in the broadcast receiving device 100. For example, a predetermined copyright protection process may be performed. Furthermore, if such information is not stored in the broadcast signal, it may be predetermined that the broadcast receiving device 100 will not perform copyright protection processing.

[0233] Specific examples of authentication for copyright protection are shown below. Each of the following authentications may be performed alone. Alternatively, multiple authentications exemplified below may be performed in combination. Furthermore, the authentications exemplified below may be performed in combination with other authentication processes not exemplified below.

[0234] [Encryption key usage] When the mobile information terminal 700 is in the same home, an encryption key for decrypting encrypted video data, etc. is transmitted from the broadcast receiving device 100 to the mobile information terminal. This encryption key may be obtained from the broadcast signal (for example, written in the AIT). The delivery of this encryption key within the same home constitutes authentication. Furthermore, if the encryption key can only be obtained from the broadcast signal at a certain point in the program and the delivery of the encryption key to the mobile information terminal 700 is limited to within the same home, it is possible to impose a restriction that the user must be in the same home at that time, which can also be used to provide a premium for viewing.

[0235] [Use of distribution server] In this method, a distribution server issues an encryption key for decrypting encrypted video data, etc. The mobile information terminal 700 transmits an ID and password to the distribution server to obtain the encryption key. In this case, security is enhanced by obtaining the distribution server's location information (specifically, a URL) from the broadcast signal (e.g., written in the AIT) and transmitting this location information from the broadcast receiving device 100 to the mobile information terminal 700. Since the mobile information terminal 700 cannot decrypt video data without obtaining the encryption key, the broadcast receiving device 100 may request authentication from the distribution server to protect copyright, or the mobile information terminal 700 may notify the broadcast receiving device 100 that the encryption key has been obtained to complete authentication. Access to the distribution server can be performed both inside and outside the home. However, by restricting the distribution server's location information to be obtained from the broadcast signal only at a certain point in the program and limiting the transfer of location information to the mobile information terminal 700 to within the same home, a restriction can be imposed, requiring the user to be within the same home at that time. This can also be used to provide a premium for viewing. The distribution server may also charge a fee.

[0236] [Mutual authentication of encryption keys] The broadcast receiving device 100 and the mobile information terminal 700 mutually authenticate and confirm the encryption keys they each have, thereby authenticating copyright protection. This authentication may also be performed either inside or outside the home.

[0237] When information stored in a broadcast signal indicates that copyright protection using a predetermined method is required, if the copyright protection cannot be authenticated using that predetermined method, terminal linkage is not permitted. Also, even if there is no designation in the broadcast signal and authentication is performed using a default method of the broadcast receiver 100, if the copyright protection cannot be authenticated using that default method, terminal linkage is not permitted. The procedure after terminal linkage is permitted is the same as the procedure in Figure 18C, so a description thereof will be omitted.

[0238] According to the mobile information terminal cooperation technology according to the present embodiment described above, it is possible to realize the use of a mobile information terminal that cooperates with a broadcast receiving device from outside the home while taking into consideration copyright protection. [Example]

[0239] In actual usage situations, it is more desirable to easily know whether a terminal-linked app is available for a program and which terminal-linked apps are available. In this embodiment, a method for displaying the availability status of terminal-linked apps will be described. A terminal-linked app refers to a broadcast-linked app used in device linkage.

[0240] FIG. 19A shows an example of a broadcast-linked app launcher screen (173b11) when a terminal-linked app is present. The broadcast-linked app is displayed as a boxed text icon. Broadcast-linked apps (173b12-173b14) for the broadcast receiving device 100 linked to the currently viewed program and broadcast-linked apps (173b15-173b17) for the mobile information terminal are displayed. In this example, the thickness of the frame surrounding the text and the color of the box indicate the app status. Main app A and B (173b12, 173b13) and terminal app A and B (173b15, 173b16) are available, while main app C (173b14) and terminal app C (173b17) are unavailable. A terminal app being unavailable means that none of the mobile information terminals 700 that are capable of communicating with the broadcast receiving device 100 have the function to execute the app.

[0241] Fig. 19B is a screen that appears after terminal application A is selected in Fig. 19A. It shows the state of each mobile information terminal 700 related to terminal application A. The mobile information terminals displayed on this screen are terminals that have previously collaborated with or are registered with broadcast receiving device 100.

[0242] Mobile terminal 1 (173b22) and mobile terminal 2 (173b23) whose icons have solid borders are in a state where they can communicate with broadcast receiving device 100, while mobile terminal 3 (173b24) and mobile terminal 4 (173b25) whose icons have dotted borders are not in a state where they can communicate with broadcast receiving device 100. Furthermore, mobile terminal 1 (173b22) and mobile terminal 3 (173b24) whose icons have white borders are capable of executing terminal app A, while mobile terminal 2 (173b23) and mobile terminal 4 (173b25) whose icons have gray borders are not capable of executing terminal app A. Furthermore, if an app is already running on the device, an icon with a design that indicates this may be used.

[0243] Additionally, icons are easier to understand visually if they are made of pictures, as shown below as an example.

[0244] 19C is an example of a launcher screen (173b31) showing a list of broadcast-linked apps. In addition to the broadcast receiving device 100, icons are shown for each type of mobile information terminal 700. Icons 173b32 and 173b33 are icons indicating the broadcast receiving device 100, icons 173b34 and 173b35 are icons indicating a smartphone-type mobile information terminal 700, and icon 173b36 is an icon indicating a head-mounted display-type mobile information terminal 700. Each app is for the device indicated by the icon.

[0245] In FIG. 19C, if the app cannot be used, a mark indicating that it is unavailable (in this case, a circle with a diagonal line) is displayed superimposed on the image of the device. Furthermore, for the broadcast receiving device 100, if the app is already running, a mark indicating this (in this case, a circle with a dot) may be displayed superimposed. This display prevents unnecessary actions such as proceeding with the launcher procedure even though the app is already running. For the mobile information terminal 700, a method is also possible in which a mark indicating that the app is running is displayed when the app is running on all devices that are capable of communicating with the broadcast receiving device and that can run the app.

[0246] FIG. 19D shows a screen (173b41) that appears after selecting application C (173b34) in FIG. 19C. The screen shows the state of a mobile information terminal 700 that is compatible with application C. On this screen, if the mobile information terminal 700 does not have the capability to execute a broadcast-linked application, is not capable of communicating with the broadcast receiving device 100, or is already running the broadcast-linked application, a mark representing that fact is displayed superimposed on the icon. In this example, if the mobile information terminal 700 does not have the capability to execute the application, a circle with a line (173b44, 173b46) is displayed; if the mobile information terminal 700 is not capable of communicating, a triangle with an exclamation point (173b45, 173b46) is displayed; and if the application is already running, a circle with a dot (173b43) is displayed.

[0247] Furthermore, it is desirable to have a display method that allows users to know that a broadcast-linked app is available when the situation changes, without having to start a launcher each time. For example, when the power is turned on, when the channel is changed, at the beginning of a program or during a program, when there is a change in the broadcast-linked app, when there is a change in the communication status between the broadcast receiving device 100 and the mobile information terminal 700, or when the execution status of the app changes, an icon is displayed for a predetermined period of time to show the status at that time.

[0248] An example of this case is shown in Figure 19E. When an icon indicating the type of device is displayed, it indicates that there is a broadcast-linked app that is compatible with that type of device. In this case, a circle with a diagonal line indicates that there are no usable devices of that type that can run the app. A circle with a dot indicates that the app is running on all usable devices of that type.

[0249] FIG. 19F shows a display screen (10401) on the mobile information terminal 700. When requesting terminal linkage from the mobile information terminal 700, it is convenient to know in a list which broadcast receiving devices 100 can use which broadcast-linked apps. FIG. 19F shows an example of such a list (10402). This table shows which broadcast receiving devices 100 in the home can use the broadcast-linked apps corresponding to the program you are looking up. Displaying the status of each broadcast receiving device 100 also enhances convenience, especially when using the device outside the home. This example shows display examples such as receiving the program, receiving another program, available, and having another program scheduled (when another program has been scheduled to be recorded midway through the program). Note that if the broadcast receiving device 100 has multiple tuners, displaying the status for each tuner would further enhance convenience. In table 10202, sub-numbers are used to distinguish between tuners within the same device. For example, receiving device B-1 and receiving device B-2 are tuners within the same broadcast receiving device 100. In the case of terminal linkage, if broadcast video and audio can be received as streaming data, there is no need to use the video section of broadcast receiving device 100, and broadcasting can be used if the tuner within broadcast receiving device 100 can be used, so it is convenient to know the usage status of each tuner.

[0250] In order to perform the display described in this embodiment, it is necessary to have information for each broadcast-linked app as to whether the app is compatible with the broadcast receiving device 100 or what type of mobile information terminal 700 the app is compatible with. Also, information is required for executing the compatible app on the broadcast receiving device 100 and the mobile information terminal 700. This information can be acquired by the broadcast receiving device 100 by, for example, writing it in the AIT.

[0251] According to the mobile information terminal collaboration technology of this embodiment described above, by displaying information about the broadcast collaboration app, the broadcast receiving device 100, and the mobile information terminal 700, it becomes possible to use a more convenient broadcast collaboration service. [Example]

[0252] The following describes a sixth embodiment of the present invention. The configuration, effects, and the like of this embodiment are the same as those of the first embodiment unless otherwise specified. Therefore, the following mainly describes the differences between this embodiment and the first embodiment, and omits as much as possible the description of common points to avoid duplication.

[0253] In this embodiment, an example will be given to explain the operation of the broadcast receiving device 100 in the process of launching a broadcast-linked app based on the AIT transmitted by the broadcast waves, particularly in the following cases. This case is when the broadcast-linked app is a broadcast-managed application, and information on the PMT and information such as the application control code 903 and launch priority 907 in the AIT (FIG. 6) specifies and instructs that the broadcast-linked app, which is a broadcast-managed application, be given priority to automatic launch. Note that hereinafter, the broadcast-managed application may be referred to as a "broadcast-managed application."

[0254] The broadcast receiving device 100 of the sixth embodiment has a function of controlling the start-up process of the broadcast-linked app for which the automatic start-up is specified in the digital broadcasting service in accordance with a user selection. When there is a provision or instruction for the automatic start-up, the broadcast receiving device 100 of the sixth embodiment does not automatically start the broadcast-linked app unconditionally, but controls it to automatically start only when the following conditions (1) to (3) are met: (1) When automatic start-up is set to be permissible in the user settings of the broadcast receiving device; (2) When a user who owns a predetermined terminal linked to the broadcast receiving device is watching, in other words, when automatic start-up is set to be permissible in the user settings of the linked terminal; (3) When a user is asked to confirm start-up each time, and the confirmation is affirmative.

[0255] 20 shows a system configuration and a usage example including a broadcast receiving device 100 of Example 6. The broadcast receiving device 100 receives broadcast waves from a broadcast station server 300 via a radio tower 300t, and separates the video of the broadcast program from information such as the AIT. The broadcast receiving device 100 appropriately acquires a broadcast-linked app from the service provider server 400 based on the information such as the AIT. The AIT may include information instructing automatic startup of a broadcast-linked app linked to the broadcast program.

[0256] There are one or more mobile information terminals 700 that perform terminal linkage with the broadcast receiving device 100. For example, one broadcast receiving device 100 can link with each of the mobile information terminals 700 of two users and is shared. For example, there is terminal A owned by user A and terminal B owned by user B. However, this is not limiting, and one user may use multiple mobile information terminals 700.

[0257] The broadcast receiving device 100 of Example 6 has an application launch control means 2000 including a user selection means 2001. The user selection means 2001 is a means for selecting whether or not to allow the launch and execution of a broadcast-linked application based on operations by users of the broadcast receiving device 100 and the mobile information terminal 700. The user selection means 2001 is configured by, for example, an instruction input unit and a user setting unit in the broadcast receiving device 100 and the mobile information terminal 700. When automatic launch of a broadcast-linked application is instructed in the AIT, the application launch control means 2000 controls the launch of the broadcast-linked application in accordance with the selection by the user and the user selection means 2001 of whether or not to allow the launch and execution of the broadcast-linked application.

[0258] [Automatic launch of broadcast-managed apps] In the sixth embodiment, when it is specified that a broadcast managed application is to be given priority for automatic startup, the operational sequence in which the broadcast receiving device 100 appropriately checks information such as the PMT and AIT and starts the broadcast managed application is the same as that described using Fig. 7A in the first embodiment. In the example of Fig. 7A, the application profile 904 in the AIT is checked to confirm whether the target broadcast managed application can be executed in the broadcast receiving device 100 (S105). If it is confirmed that the target broadcast managed application can be executed, the broadcast managed application will always be automatically started regardless of the selection made by the user of the broadcast receiving device 100.

[0259] However, it should be considered that the user of the broadcast receiving device 100 may not want the broadcast-managed app to be automatically launched, for example, because they want to concentrate on watching a broadcast program. The broadcast receiving device 100 of the sixth embodiment has an app launch control means 2000 as a control function that takes this possibility into consideration. That is, even when there is an instruction to prioritize automatic launch of a broadcast-managed app based on information such as the PMT and AIT, and even when it is confirmed that the broadcast-managed app is executable based on information such as the AIT, the broadcast receiving device 100 of the sixth embodiment controls the launch of the app in accordance with the user's selection of whether to launch the app. An example of controlling whether to launch a broadcast-managed app will be described below.

[0260] [Operation sequence when broadcast managed app is launched (1)] Fig. 21 shows an example of an operation sequence when a broadcast-linked app is started when a broadcast-managed app, which is a broadcast-linked app, is specified to be started with priority, as a first configuration example and processing example of the broadcast receiving device 100 of Example 6. Fig. 21 shows a series of steps in which the broadcast receiving device 100 appropriately checks the information in the PMT and AIT, and further controls whether or not to automatically start a predetermined broadcast-linked app according to a user selection. In the first configuration example, a user setting in the broadcast receiving device 100 is used as the user selection means 2000.

[0261] 21, the broadcast receiving device 100 acquires a TS by performing a tuning process for a channel desired by the user using the tuner / demodulator 131 shown in FIG. 2A. Next, the broadcast receiving device 100 acquires the PMT data string separated by the first separator 132 using the main control unit 101 (S1101), and checks the startup priority described in the acquired PMT (S1102). In the processes of S1101 and S1102, the broadcast receiving device 100 checks that the startup priority of the broadcast-managed app, which is a broadcast-linked app, is high.

[0262] After confirming the above, the broadcast receiving device 100 acquires the AIT data string separated by the first separation unit 132 using the application control unit 161 (S1103), and checks the application control code 903 of the acquired AIT data string (S1104). If the application control code 903 is "automatic start" in the processes of S1103 and S1104, that is, if automatic start of the broadcast cooperative app is specified, the broadcast receiving device 100 further checks the application profile 904 of the acquired AIT data string (S1105).

[0263] In S1105, the broadcast receiving device 100 confirms that the broadcast cooperative app specified in the AIT can be executed on the broadcast receiving device 100 by checking the information in the application profile 904. If it is confirmed that the broadcast cooperative app can be executed, the broadcast receiving device 100 further refers to the operation setting values ​​stored in the storage unit 110 by the application control unit 161. As a result, the broadcast receiving device 100 confirms whether automatic startup of the broadcast cooperative app is permitted in the user settings of the broadcast receiving device 100 (S1106).

[0264] The operation setting value indicating whether the broadcast-linked app is to be automatically started can be selected and set by the user according to preference using a function setting menu or the like of the broadcast receiving device 100. The broadcast receiving device 100 provides the user with a function setting menu on a screen or the like as user selection means 2001. The user can set the user settings for various functions using the function setting menu on the screen by operating the remote control of the broadcast receiving device 100 or a linked mobile information terminal 700 or the like. The broadcast receiving device 100 saves the user setting information in the function setting menu in the memory of the broadcast receiving device 100 as an operation setting value.

[0265] If the broadcast receiving device 100 confirms in the process of S1106 that automatic startup of the broadcast-linked app is not permitted (“No”), that is, that the user does not want the broadcast-linked app to be automatically started (S1107-No), the broadcast receiving device 100 ends this process of Fig. 21. That is, the application control unit 161 does not acquire and start the broadcast-linked app specified in the AIT.

[0266] On the other hand, if the broadcast receiving device 100 confirms in the processing of S1106 that automatic startup of the broadcast cooperative app is permitted (“Yes”), that is, that the user desires automatic startup of the broadcast cooperative app (S1107-Yes), the broadcast receiving device 100 proceeds to S1108. In the processing of S1108, the application control unit 161 of the broadcast receiving device 100 transmits a distribution request for the broadcast cooperative app to a predetermined service provider server 400 via the LAN communication unit 121 based on the information described in the application acquisition destination information 905 of the AIT.

[0267] Upon receiving the broadcast-interactive app distribution request of S1108, the service provider server 400 performs authentication processing of the broadcast receiving device 100 as necessary under the control of the application management / distribution execution unit 4103 in Fig. 4, and then distributes the predetermined broadcast-interactive app stored in the application storage area 4013 via the LAN communication unit 421 (S1109). Note that a known method may be used for this authentication processing, and detailed description thereof will be omitted.

[0268] Next, the broadcast receiving device 100 starts a predetermined broadcast-linked app that has been received via the LAN communication unit 121 by the application engine 162 under the control of the application control unit 161 and distributed from the service provider server 400 (S1110). As a result, the broadcast-linked app is executed and an execution screen of the app is displayed.

[0269] As a modified example, the processes of S1106 and S1107 may be performed after the broadcast cooperative app is acquired in the processes of S1108 and S1109.

[0270] As in the first configuration example of FIG. 21 described above, in the sixth embodiment, if it is confirmed in the user settings of the broadcast receiving device 100 that automatic startup is permitted, the broadcast cooperative app can be started.

[0271] [Operation sequence when broadcast managed app is launched (2)] FIG. 22 shows, as a second configuration example and processing example of the broadcast receiving device 100 of Example 6, an example of an operation sequence at the time of starting a broadcast-linked app different from that shown in FIG. 21 when a broadcast-managed app, which is a broadcast-linked app, is specified to be started with priority. FIG. 22 shows an example of checking whether or not to automatically start a broadcast-linked app by referring to operation setting values, i.e., user setting information, stored in a mobile information terminal 700 that performs linked operation with the broadcast receiving device 100, i.e., the above-mentioned terminal linkage. In the second configuration example, user settings in the mobile information terminal 700 are used as the user selection means 2000. The user selects and sets whether or not to allow automatic start of a broadcast-linked app on the mobile information terminal 700.

[0272] 22, the broadcast receiving device 100 first performs the processes of S1201 to S1205, which are the same as the processes of S1101 to S1105 in Fig. 21. If the broadcast receiving device 100 confirms in S1205 that the broadcast cooperative application specified in the AIT is executable by checking the application profile 904, it then performs the process of S1206. In S1206, the broadcast receiving device 100 transmits a user setting confirmation request to the mobile information terminal 700 in cooperative operation via the application control unit 161. Here, it is assumed that the mobile information terminal 700 in cooperative operation or capable of terminal cooperation is, for example, terminal A in Fig. 20.

[0273] In response to the user setting confirmation request received by the cooperative control execution unit 7102 of Fig. 5B via the LAN communication unit 721, the mobile information terminal 700 refers to the operation setting values ​​for the broadcast receiving device 100 stored in the storage unit 710 of Fig. 5A. As a result, the mobile information terminal 700 confirms whether the broadcast cooperative app can be automatically started on the broadcast receiving device 100 in the user settings on the mobile information terminal 700 (S1207). The mobile information terminal 700 transmits the confirmation result of whether the automatic start is possible to the broadcast receiving device 100 via the LAN communication unit 721 by the cooperative control execution unit 7102 as the user setting confirmation result (S1208).

[0274] The operation setting value for whether or not to automatically start the broadcast-linked app in the broadcast receiving device 100, which is the user setting information of the mobile information terminal 700, can be set, for example, by the following means. That is, when the broadcast receiving device 100 and the mobile information terminal 700 are in a linked operation state, the user can select and set it according to their preference using a link function setting menu, which is one item in the function setting menu of the mobile information terminal 700. The mobile information terminal 700 provides the user with the function setting menu on a screen, etc. The user selects the link function setting menu from the function setting menu. The link function setting menu is a menu that allows settings related to linked operation. The user can set whether or not to automatically start the broadcast-linked app in the broadcast receiving device 100 by selecting from the link function setting menu. The mobile information terminal 700 saves the user setting information in the function setting menu in the memory of the mobile information terminal 700 as an operation setting value.

[0275] If the broadcast receiving device 100 confirms through the processes of S1206 to S1208 above that automatic startup of the broadcast cooperative app is not permitted, that is, that the user who owns the mobile information terminal 700 does not want the broadcast cooperative app to be automatically started on the broadcast receiving device 100 (S1209-No), the broadcast receiving device 100 ends this process in Fig. 22. That is, the application control unit 161 does not acquire or start the broadcast cooperative app specified in the AIT.

[0276] On the other hand, if the broadcast receiving device 100 confirms that automatic startup of the broadcast linked app is allowed, i.e., that the user who owns the mobile information terminal 700 wishes the broadcast linked app to be automatically started on the broadcast receiving device 100 (S1209-Yes), it proceeds to S1210.

[0277] In S1210, the broadcast receiving device 100 transmits a broadcast collaborative app distribution request to a predetermined service provider server 400 via the LAN communication unit 121 based on the information described in the application acquisition destination information 905 of the AIT by the application control unit 161.

[0278] Upon receiving the broadcast-linked app distribution request of S1210, the service provider server 400 performs authentication processing of the broadcast receiving device 100 as necessary based on the control of the application management / distribution execution unit 4103, and then distributes the specified broadcast-linked app stored in the application memory area 4013 via the LAN communication unit 421 (S1211).

[0279] Next, the broadcast receiving device 100 launches a predetermined broadcast-linked application distributed from the service provider server 400 and received via the LAN communication unit 121 by the application engine 162 based on the control of the application control unit 161 (S1212).

[0280] As in the second configuration example of Figure 22 described above, in Example 6, if there is a mobile information terminal 700 that is linked to the broadcast receiving device 100 and it is confirmed that automatic start-up is permitted in the user settings of the mobile information terminal 700, the broadcast-linked app can be started.

[0281] As a modified example, when checking the user settings in Fig. 22 above, if the mobile information terminal 700 is not operating in cooperation with the broadcast receiving device 100, the processes of S606 to S611 in Fig. 8C may be performed before the processes of S1206 to S1208. In this modified example, the process of starting the cooperation control app is performed to cause the mobile information terminal 700 to start operating in cooperation with the broadcast receiving device 100, and the user settings are checked in this state.

[0282] As a modified example, an embodiment in which control is performed to select the Yes side in S1209 or the No side in S1209 is possible in the following cases. Examples of such cases include when there is no mobile information terminal 700 to which the user setting confirmation request is sent in S1206, when there is no response to the request, or when the user setting confirmation result cannot be correctly acquired in S1208. Examples of such cases include when there is no mobile information terminal 700 capable of terminal linkage at that time, or when communication between the broadcast receiving device 100 and the mobile information terminal 700 is temporarily unavailable. In the former embodiment, the broadcast-linked app is launched even though permission for launching through the user settings could not be confirmed. In the latter embodiment, the broadcast-linked app is not launched because permission for launching through the user settings could not be confirmed. Which control operation to adopt in the above modified examples is either specified in the specifications of the broadcast receiving device 100 or can be selected and set by the user.

[0283] As a modified example, the processes of S1206 to S1209 may be performed after the broadcast cooperative app is acquired in the processes of S1210 to S1211.

[0284] [Operation sequence when broadcast managed app is launched (3)] Fig. 23 shows an example of an operation sequence when a different broadcast-linked app is launched when a broadcast-managed app, which is a broadcast-linked app, is specified to be launched with priority, as a third configuration example and processing example of the broadcast receiving device 100 of Example 6. Fig. 23 shows an example in which the user is asked in real time each time whether or not to launch the broadcast-linked app by a message on the screen, etc. In the third configuration example, an instruction input from the mobile information terminal 700 to the broadcast receiving device 100 is used as the user selection means 2000.

[0285] 23, the broadcast receiving device 100 first performs the processes of S1301 to S1305, which are the same as the processes of S1101 to S1105 in Fig. 21. If the broadcast receiving device 100 confirms in S1205 that the broadcast-linked app specified in the AIT is executable by checking the application profile 904, it then performs the process of S1306. In S1306, the broadcast receiving device 100 causes the application control unit 161 to display on the video display unit 173 a start-up confirmation screen for allowing the user to select whether or not to allow the broadcast-linked app to be started.

[0286] The user selects whether or not to start the broadcast-linked app on the start confirmation screen displayed in S1306 using the mobile information terminal 700, a remote control, or the like, which is an operation means (S1307). The broadcast receiving device 100 receives information on the selection as an instruction input.

[0287] If the broadcast receiving device 100 does not select the broadcast-linked app to be launched in accordance with the result of the user's selection of whether to launch the app in S1307, that is, if the user does not permit the launch at this point (S1308-No), the broadcast receiving device 100 ends the process in Fig. 23. That is, the application control unit 161 does not acquire or launch the broadcast-linked app specified in the AIT.

[0288] On the other hand, if the user selects to launch the broadcast-linked app in S1307, i.e., if the user allows the launch at this point (S1308-Yes), the broadcast receiving device 100 proceeds to S1309. In the processing of S1309, the application control unit 161 of the broadcast receiving device 100 transmits a broadcast-linked app distribution request to a predetermined service provider server 400 via the LAN communication unit 121 based on the information described in the application acquisition destination information 905.

[0289] Upon receiving the request to distribute the broadcast-linked app, the service provider server 400 performs authentication processing of the broadcast receiving device 100 as necessary based on the control of the application management / distribution execution unit 4103, and then distributes the specified broadcast-linked app stored in the application memory area 4013 via the LAN communication unit 421 (S1310).

[0290] Next, the broadcast receiving device 100 launches a predetermined broadcast-linked application distributed from the service provider server 400 and received via the LAN communication unit 121 by the application engine 162 based on the control of the application control unit 161 (S1311).

[0291] As a modified example, the processes of S1306 to S1308 may be performed after the broadcast cooperative app is acquired in the processes of S1309 to S1310.

[0292] As in the third configuration example of FIG. 23 described above, in the sixth embodiment, the user is prompted on the screen each time to confirm whether or not to start the broadcast cooperative app, and if it is confirmed that the broadcast cooperative app is acceptable, the broadcast cooperative app can be started.

[0293] 23, the mobile information terminal 700 functions as an operation means for the broadcast receiving device 100 through terminal cooperation, allowing the user to select whether to start the device. However, the present invention is not limited to this, and an embodiment is also possible in which the user can select whether to start the device using a remote control or the like provided in the broadcast receiving device 100, which is the main body of the device.

[0294] [Start confirmation screen] FIG. 24 shows an example of a launch possibility confirmation screen of the broadcast receiving device 100, which is displayed by the processing of S1306 in FIG. 23. In this embodiment, a message box 173f1 is displayed as the launch possibility confirmation screen on the screen of the video display unit 173 in FIG. 24. The message box 173f1 includes a message indicating that a predetermined broadcast-linked app is available, and displays "Yes" and "No" buttons for selecting whether or not to launch the broadcast-linked app. An example of the message is "Broadcast-linked app XXX is available. Do you want to launch broadcast-linked app XXX?" Another example of the message is "Broadcast-linked app XXX has been specified to be launched and is available. Do you want to allow it to be launched?"

[0295] 24 is displayed, the user selects whether to allow or disallow activation using the operation means (S1307). For example, the user selects "Yes" or "No" on the basic screen 741a of the cooperative control app of the mobile information terminal 700 in FIG. 10A using the cursor keys 741ac and the enter key 741ad. This allows the user to select whether to allow or disallow activation of the broadcast cooperative app presented in the message box 173f1 on the broadcast receiving device 100, depending on their own convenience and situation at the time.

[0296] As a modified example, instead of the message box 173f1, an icon 173b0 indicating the presence of an interlocking application, as shown in FIG. 12A, or other mark or image, may be displayed on the screen to allow the user to select an application. In this case, the user presses, for example, an interlocking application key 741a9 on the basic screen 741a of the interlocking control application. This launches a predetermined broadcast interlocking application. Furthermore, if the interlocking application key 741a9 corresponding to the selection of the icon 173b0 is not pressed for a predetermined period of time or longer, the display of the icon 173b0 may be erased.

[0297] [Effects, etc.] As described above, according to each configuration example of the broadcast receiving device 100 of the sixth embodiment, even when the PMT and AIT specify and instruct automatic startup with priority given to a broadcast-managed application, and the AIT confirms that the broadcast-managed application is executable, the startup of the broadcast-managed application can be appropriately controlled according to the user's selection. In other words, the broadcast receiving device 100 of this embodiment can execute functions with higher added value.

[0298] Which of the above first to third configuration examples or various modified examples is adopted may be specified in the specifications of the broadcast receiving device 100 or the like, or may be selectable by the user on the broadcast receiving device 100. For example, in the configuration examples of FIGS. 21 and 22, the user can select from two values ​​as the operation setting value: (a) "Allow launch of broadcast-managed app (Yes)" and (b) "Do not allow launch of broadcast-managed app (No)." This is not limited to this, and as a modified example, the user may select from multiple values ​​including (c) "Inquire at terminal" and (d) "Confirm on screen each time" in addition to the above (a) and (b). The broadcast receiving device 100 of this modified example performs control operations according to the first to third configuration examples in response to the setting value selected by the user. When the setting is (c), the processing of the second configuration example is performed, and when the setting is (d), the processing of the third configuration example is performed.

[0299] 21, in particular, the launch of the broadcast-linked app can be controlled according to the user's advance settings for the broadcast receiving device 100. The user can change the settings as needed according to their own convenience and use the broadcast-linked app.

[0300] FIG. 25 shows an example of a user setting menu displayed on the screen of the broadcast receiving device 100. In response to a user's operation of a remote control or the like, a user setting menu 173f2 is displayed on the screen. In the first configuration example, the menu 173f2 has "Allow broadcast-managed app launch" as one of the setting items. This item corresponds to "whether to allow automatic launch of a broadcast-linked app when automatic launch is specified." The user can set whether to allow or disallow the above (a) and (b) by turning a button on or off in the setting item of the menu 173f2. A similar function can also be realized on the screen of the mobile information terminal 700.

[0301] In particular, in the second configuration example of Figure 22, it is possible to set whether or not to automatically start the broadcast managed app on a user-by-user basis who owns the mobile information terminal 700, and it is also possible to select whether or not to automatically start the broadcast managed app depending on whether or not there is a mobile information terminal 700 that performs collaborative operation.

[0302] An example of the settings and usage will be described using FIG. 20 mentioned above. As user settings on the mobile information terminal 700, user A's terminal A has setting A, and user B's terminal B has a different setting B. For example, setting A allows automatic startup of the broadcast-linked app, and setting B prevents automatic startup of the broadcast-linked app. At the time of the processing of S1206 to S1209 in FIG. 22, if only user A's terminal A is operating in cooperation with the mobile information terminal 700, the terminal A is checked and startup is permitted. If only user B's terminal B is operating in cooperation with the mobile information terminal 700, the terminal B is checked and startup is not permitted. In this way, whether or not to start the broadcast-linked app can be set for each user's mobile information terminal 700, and the broadcast-linked app can be started and used depending on whether or not there is a mobile information terminal 700 that is linked with the mobile information terminal 700 at that time.

[0303] As a modified example, it is possible to perform control operations that take into consideration a combination of both the specifications or user settings in the broadcast receiving device 100 and the specifications or user settings in the mobile information terminal 700. For example, it is possible to implement either an embodiment in which the contents of the user settings in the mobile information terminal 700 take priority over the user settings in the broadcast receiving device 100, or an embodiment in which the contents of the user settings in the broadcast receiving device 100 take priority over the user settings in the mobile information terminal 700.

[0304] In the second configuration example, the user may be allowed to set whether to inquire of the mobile information terminal 700 to confirm whether or not the broadcast cooperative app can be launched. In this case, a setting item corresponding to "inquire of the terminal" in (c) above is provided in the user setting menu 173f2 in Fig. 25 above.

[0305] In particular, the third configuration example in Fig. 23 makes it possible to control whether or not to launch each broadcast-managed app provided for each broadcast program. The user can view the broadcast-managed app and confirmation information displayed on the screen, and allow the app to launch if they want to launch it at that time, or disallow its launch if they do not want to launch it at that time.

[0306] In the third configuration example, the user may be allowed to set whether to check on the screen each time the broadcast-linked app can be launched. In this case, a setting item corresponding to "Check on the screen each time" in (d) above is provided in the user setting menu 173f2 in FIG. 25 above.

[0307] Other embodiments include the following. In another embodiment, even if the user has previously selected and set the above (b) "No" in the configuration examples of FIGS. 21 and 22, an option is provided for forcibly starting the broadcast-managed application regardless of the setting value. In this embodiment, for example, in the data configuration of the AIT shown in FIG. 6, a setting value of (5) "Forced Start" is provided as a setting value of the parameter of the application control code 903 in addition to (1) to (4). Alternatively, a "Forced Start Setting" item may be provided separately as one of the parameters of the AIT (one of the "Other Information" in FIG. 6). For example, "Enabled" or "Disabled" can be selected as these setting values.

[0308] Furthermore, if the setting value of the application control code 903 is (5) "Forced Launch" or if the value of the "Forced Launch Setting" item is "Enabled," the broadcast receiving device 100 performs the following control. That is, the broadcast receiving device 100 performs control to forcibly launch the broadcast-managed application even if the operation setting value is set to (b) "No." In other words, in the control of this embodiment, forced launch is set as an item that is higher in rank and has priority than the user-selected item related to the automatic launch described above. In an embodiment that provides the forced launch option as described above, applications that are highly required to be displayed and provided, such as applications for displaying emergency information from the broadcast station or applications required for producing a specific commercial, can be displayed and provided to the user in an optimal manner.

[0309] In another embodiment, if a broadcast cooperative app is pre-installed inside the broadcast receiving device 100, the above-mentioned processes such as acquiring the broadcast cooperative app from the service provider server 400 (for example, S1108 to S1110 in FIG. 21) are not necessary.

[0310] The information included in the broadcast wave for controlling the broadcast-linked app is not limited to the PAT, AIT, etc., and may be applicable. For example, one of the parameters (901 to 909) of the AIT in FIG. 6 may be separated and configured and provided as independent control information. The control information may be provided in a form included in the broadcast wave, or may be provided in a form separate from the broadcast wave. The control information may be set in advance in the device. [Example]

[0311] The following describes Example 7 of the present invention. The configuration, effects, etc. of this example are the same as those of Example 1 unless otherwise specified. Therefore, the following mainly describes the differences between this example and Example 1, and omits explanations of common points as much as possible to avoid duplication.

[0312] The broadcast-linked application, which is an application used in the broadcast-communication linked system of this embodiment, is configured as an HTML document, and therefore can be linked to other HTML documents on the network. The broadcast-managed application's operations, such as start / stop, are controlled based on the application control code 903 of the AIT included in the broadcast signal of the broadcast wave. The operations, such as start / stop, of the non-broadcast-managed application and general application are not controlled by the above-mentioned broadcast signal. Note that, hereinafter, the non-broadcast-managed application may be referred to as the "non-broadcast application" and the general application may be referred to as the "general application."

[0313] Since links are possible in the HTML document constituting the broadcast-linked app, in Example 7, it is assumed that transition from the broadcast-managed app to a non-broadcast app or a general app is possible. Furthermore, in Example 7, it is assumed that the non-broadcast app or general app can be directly launched in response to a user's instruction from the aforementioned broadcast-linked app launcher screen, etc. For example, a broadcast station, a service provider, etc., includes information instructing transition to another HTML document constituting the non-broadcast app, etc., by describing a link such as a URL in the HTML document of the broadcast-managed app. In such a case, transition from the broadcast-managed app to the non-broadcast app, etc., may occur.

[0314] Because the launch / termination of the non-broadcast application and general application are not controlled by broadcast signals, a user may execute a non-broadcast application or general application while watching a broadcast program. When a user is running a non-broadcast application while watching a broadcast program, the user may also request the launch of a broadcast-managed application linked to the broadcast program. This request may be, for example, a launch instruction by application control code 903 in the AIT included in the broadcast signal. In other words, in this case, the user is requested to run the non-broadcast application or general application and the broadcast-managed application in parallel, or to select one of them. While running multiple different types of applications in parallel like this is technically possible, it may be undesirable from a control perspective and may be inconvenient for the user.

[0315] Therefore, the broadcast receiving device 100 of Example 7 has a function for controlling overlapping or parallel launch of the applications or launch and termination of each application so as to be able to deal with the above situation appropriately. When a request to launch and execute a second application is made while a first application is being executed, the function controls the operations, including launch and termination, of the applications according to a user selection. In particular, when a request to launch a broadcast-managed application is made while a broadcast-non-broadcast application or the like is being executed, the function controls the termination of the broadcast-non-broadcast application or the launch of the broadcast-managed application according to a user instruction input, setting, or the like. In Example 7, examples of the control operations of the broadcast receiving device 100 in the above cases and situations will be described.

[0316] Examples of control according to user selection by the above function are as follows: (1) The above function starts and runs the target broadcast-managed application while continuing any non-broadcast applications or general applications that were running at the time the above request was received. (2) The above function terminates any non-broadcast applications or general applications that were running at the time the above request was received, and starts and runs the target broadcast-managed application. (3) The above function keeps running any non-broadcast applications or general applications that were running at the time the above request was received, and does not start or run the target broadcast-managed application.

[0317] The means for user selection by the above function are as follows: (a) When the above request is received, the above function displays on the screen information informing the user of the status of the request to launch a broadcast-managed application other than the currently running non-broadcast application, etc., and information for allowing the user to select the application to be launched or terminated or the above control operation. The function accepts the user's selection instruction input operation on the screen. In accordance with the user's selection, the function executes the control content selected from (1) to (3) above, for example. (b) The above function accepts the user setting operation performed in advance by the user. When the above request is received, the function confirms the user setting information and executes the control content selected from (1) to (3) above, for example.

[0318] FIG. 26 illustrates a system configuration and usage example including a broadcast receiving device 100 according to a seventh embodiment. The broadcast receiving device 100 receives broadcast waves from a broadcast station server 300 via a radio tower 300t and separates the video of the broadcast program from information such as the AIT. The broadcast receiving device 100 acquires a broadcast-managed app, which is a broadcast-linked app, from a service provider server 400 or the like as appropriate based on the information such as the AIT. The broadcast receiving device 100 also acquires non-broadcast apps and general apps from the service provider server 400 or other application servers 500 as appropriate. A mobile information terminal 700 that performs terminal linkage with the broadcast receiving device 100 may also be present, and various apps may be acquired and executed between the broadcast receiving device 100 and the mobile information terminal 700 in a terminal linkage state.

[0319] The broadcast receiving device 100 of the seventh embodiment has a multiple application execution control means 2600 including a user selection means 2601. The user selection means 2601 is a means for selecting the content of control, such as operations including launching and terminating multiple types of applications and parallel execution, based on operations by users of the broadcast receiving device 100 and the mobile information terminal 700. The user selection means 2601 includes, for example, an instruction input unit related to the above (a) that receives and processes instruction inputs in the broadcast receiving device 100, the mobile information terminal 700, etc. The user selection means 2601 includes, for example, a user setting unit related to the above (b) that receives and processes user settings.

[0320] For example, when a broadcast program is being viewed and an off-broadcast application or a general application is being executed and an instruction to launch a broadcast-managed application is given in the AIT of the broadcast wave, the multiple application execution control means 2600 controls the termination of the off-broadcast application, etc., or the launch of the broadcast-managed application, etc., depending on the selection of the control operation corresponding to the case by the user and the user selection means 2601.

[0321] [Examples of multiple types of apps] 27 shows an example of the document structure of multiple types of applications, the launch of each application, transitions between applications, etc. The broadcast wave 2010 includes video of a broadcast program, information such as AIT, and information such as BML. As described above, in the broadcast communication cooperation function, the AIT notifies the broadcast receiving device 100 of the existence of a broadcast cooperation application and instructs it to control the launch, termination, etc. of the application. For example, the AIT information included in the broadcast wave 2010 launches a broadcast managed application 2011.

[0322] In the seventh embodiment, the broadcast-linked applications are broadly classified into (a) broadcast-managed applications, (b) non-broadcast applications, and (c) general applications. Broadcast-managed applications operate in a broadcast reception state based on a control signal included in a broadcast signal, and are permitted to access broadcast resources. Non-broadcast applications operate in a state where their start / stop, etc., is not controlled by the broadcast signal, and are permitted to access broadcast resources based on authentication, etc. General applications operate independently of broadcast signals, and are not permitted to access broadcast resources.

[0323] In FIG. 27, App1, which is a broadcast-managed application 2011, is composed of four documents, for example, HTML11 to HTML14. App2, which is a non-broadcast application 2012, is composed of two documents, for example, HTML21 and HTML22. App3, which is a general application 2013, is composed of two documents, for example, HTML31 and HTML32. Transitions between each HTML document are possible via links indicated by solid arrows. For example, transitions are possible from HTML13 of App1 to HTML21 of App2 or HTML31 of App3. Dashed arrows indicate examples of transitions between HTML documents.

[0324] 27, for example, in response to a user operation 2020 on the broadcast-linked application launcher screen described above, App2, which is a non-broadcast application 2012, or App3, which is a general application 2013, can be launched. App2 is executed by loading HTML21, for example, and App3 is executed by loading HTML31, for example.

[0325] An example of the independent execution of each application during playback of a broadcast program (say, broadcast program A) via the broadcast wave 2010 is as follows: (a1) The AIT instructs the launch of App1, which is a broadcast managed application 2011, and App1 is launched and executed. App1 is permitted to access broadcast program A. Then, when the same AIT instructs the termination of App1, App1 is terminated.

[0326] (a2) Based on a selection operation such as a user's instruction input, an instruction to launch App2, which is a non-broadcast application 2012, is issued via the broadcast-linked application launcher screen or a link from HTML 13 of App1, and App2 is launched and executed. App2 is permitted to access Broadcast Program A. When an instruction to terminate App2 is issued, App2 is terminated. (a3) ​​Similarly, based on a selection operation by the user, an instruction to launch App3, which is a general application 2013, is issued via the broadcast-linked application launcher screen or a link from HTML 13 of App1, and App3 is launched and executed. App3 is not permitted to access Broadcast Program A. When an instruction to terminate App3 is issued, App3 is terminated.

[0327] [Operation sequence when launching a broadcast managed app] 28 shows a control operation sequence in the broadcast receiving device 100 of the seventh embodiment when a broadcast-managed application is requested to be launched by the AIT of the broadcast signal or the like while a non-broadcast application is being executed during viewing of a broadcast program. Note that the following description will be given for a non-broadcast application, but the same applies to a general application. In FIG. 28, it is assumed that the launch of the broadcast-managed application with priority is specified and instructed by the information on the PMT and the information such as the application control code 903 and launch priority 907 in the AIT.

[0328] In the broadcast receiving device 100, while a user is watching a broadcast program, for example, the user selects a desired non-broadcast application from a broadcast-linked application launcher screen, and accordingly, an instruction to launch the non-broadcast application is issued. Then, the broadcast receiving device 100 displays, for example, an execution screen of the non-broadcast application superimposed on the broadcast program screen (S1401). If the broadcast program is switched in the state of S1401, the contents of information such as the PMT and AIT in the broadcast signal are updated. Even after the update, the non-broadcast application continues to be executed because its launch / termination and other operations are not controlled by the broadcast signal.

[0329] Next, the broadcast receiving device 100 acquires the PMT data sequence separated by the first separation unit 132 using the main control unit 101 (S1402) and checks the startup priority described in the PMT (S1403). In the process of S1403, it is confirmed that the startup priority of the broadcast-managed application, for example, is high. Then, the broadcast receiving device 100 acquires the AIT data sequence separated by the first separation unit 132 using the application control unit 161 (S1404) and checks the application control code 903 of the acquired AIT data sequence (S1405). In the process of S1405, if the application control code 903 is "auto-start," the broadcast receiving device 100 further checks the application profile 904 of the AIT data sequence (S1406). In S1406, the broadcast receiving device 100 checks whether the broadcast-managed application specified in the AIT is executable.

[0330] If it is confirmed that the application can be executed, the broadcast receiving device 100 causes the application control unit 161 to display a launch selection screen (see FIG. 30, etc., described below) on the video display unit 173 (S1407). The launch selection screen is a screen that includes information for allowing the user to select control operations related to the launch / termination of the currently running non-broadcast application and the broadcast-managed application for which automatic launch is requested, in other words, the application to be launched or terminated. In the seventh embodiment, the launch selection screen allows the user to select the control operations, such as whether to continue or terminate the execution of the non-broadcast application, and whether to launch the broadcast-managed application. In other words, it allows the user to select whether to allow the non-broadcast application and the broadcast-managed application to be executed in parallel.

[0331] The user selects a control operation related to the start or end of the above-mentioned multiple types of apps on the start selection screen displayed in S1407 using their own operating means, such as the mobile information terminal 700 or the remote control of the broadcast receiving device 100 (S1408). The broadcast receiving device 100 receives the user's selection result as an instruction input. If the start of the above-mentioned broadcast-managed app is not selected according to the user's selection result in S1408 (S1409-No), the broadcast receiving device 100 ends this processing in FIG. 28. That is, the application control unit 161 does not acquire or start the broadcast-managed app specified in the AIT. The non-broadcast app continues to run.

[0332] On the other hand, if activation of the broadcast-managed application is selected (S1409-Yes), the process proceeds to S1410. In S1410, the broadcast receiving device 100 causes the application control unit 161 to terminate the operation of the non-broadcast application that is currently being executed.

[0333] Next, the transmission / reception device 100 transmits a broadcast managed application distribution request to the predetermined service provider server 400 via the LAN communication unit 121 based on the information described in the application acquisition destination information 905 of the AIT (S1412). The service provider server 400 that has received the distribution request of S1412 performs authentication processing of the broadcast receiving device 100 as necessary based on the control of the application management / distribution execution unit 4103, and then distributes the predetermined broadcast managed application stored in the application storage area 4013 via the LAN communication unit 421 (S1412). Then, the broadcast receiving device 100 starts the broadcast managed application received via the LAN communication unit 121 by the application engine 162 based on the control of the application control unit 161 (S1413).

[0334] In the above embodiment, if launching of the broadcast-managed application is selected in S1409, control is performed to terminate the non-broadcast application in S1410. This is not limited to this, and the following control is also possible. The broadcast receiving device 100 checks whether termination of the non-broadcast application is selected during S1409 or in the next step. Depending on the user's selection in this step, if termination of the non-broadcast application is selected, the broadcast receiving device 100 executes S1410, and if not, proceeds to S1411.

[0335] As a modified example, the processes of S1407 to S1410 for checking activation and terminating non-broadcast applications may be performed after the broadcast-managed application is acquired in S1411 to S1412.

[0336] [Control example] FIG. 29 shows an example of control of playback and execution of a broadcast program and multiple types of applications, corresponding to the processing of FIG. 28 of the seventh embodiment. The horizontal axis represents time. The vertical axis represents the association of playback of video of a broadcast program by a broadcast signal of broadcast waves and control instructions by the AIT with (A) first control, (B) second control, and (C) third control. (A) First Control represents (A1) execution of App2, which is a non-broadcast application, and (A2) execution of App1, which is a broadcast-managed application. Similarly, (B) Second Control represents (B1) execution of App2 and (B2) execution of App1. (C) Third Control represents (C1) execution of App2 and (C2) execution of App1. As described above, App1, which is a broadcast-managed application, has a higher startup priority than App2, which is a non-broadcast application.

[0337] First, as an example of broadcast program playback, broadcast program A is played from time t1 to t3. It is switched to broadcast program B from t3 to t4, and broadcast program B is played from t4 to t6. With the switch to broadcast program B, the AIT instructs the launch of App1, a broadcast-managed application linked to broadcast program B.

[0338] (A) In the case of the first control, as shown in (A1), for example, App2, a non-broadcast application, is launched at time t2 by a user operation or the like and executed from t2. While App2 is being executed, an instruction to launch App1 is issued at t3. At this time, the user selection means 2601 selects to continue App2 and launch App1 from t3 to t4. In accordance with the user selection, the multiple application execution control means 2600 of the broadcast receiving device 100 launches App1 at t4 as shown in (A2) while continuing the execution of App2, and controls the display state of the screen accordingly. Thereafter, for example, from t4 to t5, App1 and App2 are executed in parallel, and at t5, App2 is terminated by a user operation or the like. Execution of App1 continues from t5 to t6, and at t6, App1 is terminated in accordance with an instruction to terminate App1 from the AIT.

[0339] (B) In the case of the second control, App2 is executed from t2 to t3 as shown in (B1), and in response to an instruction to start App1 at t3, the user selects to end App2 and start App1. In accordance with the user's selection, broadcast receiving device 100 ends the execution of App2 and starts App1 at t4 as shown in (B2). Thereafter, App1 is executed from t4 to t6.

[0340] (C) In the case of the third control, App2 is running from t2 to t3 as shown in (C1), and in response to an instruction to start App1 at t3, the user selects to continue running App2 and not start App1. Broadcast receiving device 100 continues running App2 in accordance with the user's selection, and does not start or run App1 at t4 as shown in (C2). Thereafter, App2 is run from t4 to t5.

[0341] [Startup selection screen] 30 shows an example of a launch selection screen displayed by the processing of S1407 in FIG. 28 in the seventh embodiment. This screen displays a message box 173g1. The message box 173g1 includes a message display indicating that a non-broadcast application is currently running, that a broadcast-managed application has been instructed to be launched and is ready for launch, and prompting the user to confirm and select whether or not to launch the application. The message box 173g1 in this example includes "Yes" and "No" buttons that allow the user to select whether or not to launch the application.

[0342] With message box 173g1 displayed, the user selects "Yes" or "No," for example, using cursor keys 741ac and enter key 741ad on the basic screen 741a of the cooperative control app. That is, the user selects "Yes" if they want to launch a broadcast-managed app at that time, or selects "No" if they want to continue running a non-broadcast app. This screen allows the user to easily select, according to their own convenience and desires at the time, whether to launch a new broadcast-managed app on a broadcast receiving device 100 that is currently running any desired non-broadcast app. The above control is similarly possible for general apps.

[0343] Note that instead of the message box 173g1, the icon 173b0 in FIG. 12A or other mark may be displayed to prompt a predetermined user operation, and the operation may control the launch of a broadcast-managed application or the termination of a non-broadcast application. For example, a mark or message indicating a request to launch a broadcast-managed application may be displayed in the corner of the screen by OSD. If the predetermined user operation is not performed after the icon or other icon is displayed, the display is erased.

[0344] Fig. 31 shows an example of another launch selection screen. The launch selection screen of Fig. 31 displays a message box 173g2. The message box 173g2 includes a display of a message or the like that allows the user to select a control operation related to the launch or termination of multiple types of apps including the above-mentioned broadcast non-app and broadcast managed app. The message box 173g2 includes, as information on specific control options, (1) launch the broadcast managed app while the broadcast non-app is running, (2) terminate the broadcast non-app and launch the broadcast managed app, (3) do not launch the broadcast managed app, etc.

[0345] With the message box 173g2 displayed, the user can select from the options using, for example, the color key 741ae on the basic screen 741a of the cooperative control app. For example, blue corresponds to control (1), red corresponds to control (2), and yellow corresponds to control (3). The above screen also allows the user to easily select whether to terminate or start each app depending on the situation at the time.

[0346] The start-up selection screen is not limited to a form displayed when a request is made, but can also be a form displayed when a user sets it. In this case, the broadcast receiving device 100 displays a user setting menu on the screen of the video display unit 173, for example, as shown in FIG. 25, and displays control options such as (1) to (3) above on the menu, allowing the user to set their selection. When a request is made, the broadcast receiving device 100 executes control in accordance with this user setting information.

[0347] [Multiple app execution screen] In the case of controlling the termination of the non-broadcast application and the activation and execution of the broadcast-managed application, the broadcast receiving device 100 controls the display of the screen of the video display unit 173 in the same manner as in the above example. That is, the broadcast receiving device 100 terminates the execution screen of the non-broadcast application that was displayed on the screen of the video display unit 173 in an area separate from the screen of the broadcast program or in an area that overlaps with the screen of the broadcast program, for example, and displays a new execution screen of the broadcast-managed application.

[0348] Furthermore, when broadcast receiving device 100 launches a broadcast-managed application while continuing execution of the non-broadcast application, i.e., when controlling the execution of both applications in parallel, broadcast receiving device 100 may control the display on the screen of video display unit 173 as follows. For example, broadcast receiving device 100 appropriately adjusts the size and display position of the execution screen of both or one of the applications so that the execution screen of the non-broadcast application and the execution screen of the broadcast-managed application do not entirely overlap. Furthermore, adjustments may be made so that both execution screens overlap in part.

[0349] For example, the broadcast receiving device 100 may perform a process of reducing the size of the execution screen of a currently running non-broadcast app so that it does not interfere with the display of the execution screen of a newly launched broadcast-managed app. Conversely, the size of the execution screen of a newly launched broadcast-managed app may be reduced so that it does not interfere with the display of the execution screen of a currently running non-broadcast app. Alternatively, the non-broadcast app may be temporarily iconized, and only the execution screen of the broadcast-managed app may be displayed, and the display of the execution screen of the non-broadcast app may be restored when the user selects the icon of the non-broadcast app. Alternatively, both apps may be iconized, and the execution screen may be displayed in response to the user selecting the icon.

[0350] For example, the broadcast receiving device 100 may display a broadcast program playback screen within the screen of the video display unit 173, overlay an execution screen of a non-broadcast application on a partial area of ​​the broadcast program playback screen, and further overlay an execution screen of a broadcast managed application on a partial area of ​​the execution screen of the non-broadcast application. The broadcast receiving device 100 may also divide all or a partial area of ​​the screen of the video display unit 173 to display the broadcast program and the execution screens of both applications in parallel.

[0351] FIG. 32 shows an example screen of the video display unit 173 corresponding to the above-described example of controlling the parallel execution of multiple applications. In the screen of FIG. 32, an execution screen of a newly launched broadcast managed application is displayed superimposed on a partial area 173g3 on a screen 173g displaying a broadcast program. At the same time, an execution screen of the currently running non-broadcast application is displayed in a reduced size or as an icon, etc., in a partial area 173g4 within the area 173g3. When the user selects and operates 173g4, the execution screen of the non-broadcast application is displayed in an enlarged size in the area 173g3, and conversely, an execution screen of the broadcast managed application is displayed in a reduced size or as an icon, etc., in the area 173g4. A mark or a message indicating that there is an instruction to launch the broadcast managed application may be displayed in the area 173g4.

[0352] The screen shown in the above example allows the user to easily understand and recognize the status of broadcast programs and the execution of multiple types of apps.

[0353] FIG. 33 shows another example screen of video display unit 173 corresponding to the above-described example of controlling parallel execution of multiple applications. The screen of FIG. 33 is divided into multiple areas, and displays, in parallel, a broadcast program screen 173g, an execution screen 173g5 of a non-broadcast application, an execution screen 173g6 of a newly launched broadcast-managed application, and an area 173g7 displaying information for launch selection, etc. Area 173g7 may display a mark or message indicating that there is an instruction to launch a broadcast-managed application, or may display information listing applications such as the broadcast-linked application launcher of FIG. 12B. Furthermore, if there are two or more non-broadcast applications, general applications, or two or more broadcast-managed applications, this screen may display the execution screens of each application in parallel.

[0354] [Effects, etc.] As described above, according to the broadcast receiving device 100 of the seventh embodiment, even if a request to start a broadcast-managed application is issued by the AIT or the like while the broadcast receiving device 100 is executing a non-broadcast application or a general application, the broadcast receiving device 100 can appropriately control the start and end of various applications according to the user's selection. In other words, the broadcast receiving device 100 of this embodiment can execute functions with higher added value. The user can select and use a non-broadcast application or a broadcast-managed application according to the situation and convenience at the time the request is issued.

[0355] The choice of which control method to adopt for each control, variant, or screen display in Example 7 will be determined by the specifications of the broadcast receiving device 100, etc., or the user will be able to select and set the method for the broadcast receiving device 100, etc.

[0356] The following modifications of the seventh embodiment are possible. As a first modification, after the processing up to S1406 in FIG. 28, the broadcast non-application may be terminated and the broadcast managed application may be started automatically in S1410 to S1413 without confirming the user's selection in S1407 to S1408. Similarly, after the processing up to S1406, the broadcast non-application may be continued and the broadcast managed application may be started automatically without confirming the user's selection. Similarly, while the broadcast non-application or the general application is running, the broadcast managed application may not be started automatically without confirming the user's selection. In this modification, the user does not have to perform many operations.

[0357] As a second modified example, instead of confirming the user's selection instruction input on the launch confirmation screen, the execution of multiple types of apps may be controlled using user settings on the broadcast receiving device 100 or the mobile information terminal 700, as in the sixth embodiment. For example, the user can select and set, according to their preferences, whether or not to launch a broadcast-managed app while a non-broadcast app or a general app is running, using user setting information in the function setting menu or the like. The broadcast receiving device 100 stores the setting value in the storage unit 110. When a request to launch a broadcast-managed app is made while a non-broadcast app or the like is running, the broadcast receiving device 100 refers to and checks the contents of the user setting information of the broadcast receiving device 100, for example, during the processing of steps S1407 to S1409. The broadcast receiving device 100 determines and decides on the control of the launch, etc., based on the contents. In this modified example, the user can change the user setting as needed according to their own convenience, etc., and use multiple types of broadcast-linked apps.

[0358] The same can be achieved by using the user settings of the mobile information terminal 700. As in the sixth embodiment, the start and end of the above-mentioned multiple types of apps can be flexibly controlled depending on whether or not there is a linked mobile information terminal 700, or depending on the user settings of each linked mobile information terminal 700.

[0359] In another modified example, as a control example related to the second control (B) in Figure 29 above, the broadcast receiving device 100 may display information that the non-broadcast app has been terminated midway and the broadcast-managed app has been started, and after terminating the broadcast-managed app, may automatically or by a predetermined user operation restart and execute the non-broadcast app that was terminated midway. In this modified example, the user can easily return to using the non-broadcast app.

[0360] As another example of a modification, in a control example related to the third control (C) in FIG. 29 above, when a request to launch a broadcast-managed app is received, the broadcast receiving device 100 suspends the broadcast-managed app in accordance with a user selection and continues the currently running broadcast-non-broadcast app. After that, the broadcast receiving device 100 launches the suspended broadcast-managed app, for example, after the broadcast-non-broadcast app is terminated. In this case, an example of screen display control is to display a message or mark in the corner of the execution screen of the broadcast-non-broadcast app indicating that there is a request to launch the broadcast-managed app or that the launch is suspended. This prompts the user to terminate the broadcast-non-broadcast app and launch the broadcast-managed app. In this modification, the user can move on to using the broadcast-managed app at a convenient time. [Example]

[0361] The following describes Example 8 of the present invention. The configuration, effects, etc. of this example are the same as those of Example 1 unless otherwise specified. Therefore, the following mainly describes the differences between this example and Example 1, and omits explanations of common points as much as possible to avoid duplication.

[0362] The broadcast receiving device 100 of the eighth embodiment has a function of suitably controlling the restart of a once-terminated app in accordance with a user's selection when the app is restarted. Although automatic restart of a broadcast-linked app is technically possible, it may be undesirable from a control standpoint or may be inconvenient for the user. In contrast, the broadcast receiving device 100 of the eighth embodiment enables restart of a broadcast-linked app and controls the restart in accordance with a user's selection of whether to allow the restart. This allows the app to be restarted in accordance with the user's selection even in cases where the app is terminated due to a user's mistaken operation.

[0363] The broadcast receiving device 100 of Example 8 performs the following control when an app that has been instructed to be preferentially and automatically started by the AIT or the like is terminated by a user operation or the like, and the instruction to start by the AIT is still in effect. That is, (1) the broadcast receiving device 100 controls restart in accordance with the user's selection, that is, in accordance with input of an instruction or confirmation of a user setting. (2) The broadcast receiving device 100 displays information such as an icon on the screen to allow the user to select whether or not to restart the app, and restarts the app only if the user requests it by selecting the information.

[0364] 34 shows a system configuration including a broadcast receiving device 100 according to an eighth embodiment. The broadcast receiving device 100 includes an application restart control means 3400. The application restart control means 3400 includes a user selection means 3401 and a storage unit 3402. The user selection means 3401 accepts a selection operation related to the operation of controlling the restart of an application based on an operation by a user of the broadcast receiving device 100 or the mobile information terminal 700. The user selection means 3401 is realized by an instruction input or a user setting on the screen of the broadcast receiving device 100 or the mobile information terminal 700, as in the sixth embodiment and the like.

[0365] The application restart control means 3400 stores information about the execution and status of the application as application execution information 3411 in the storage unit 3402. The application execution information 3411 includes cache data that holds information about the terminated application. When and if a situation related to restarting the broadcast-managed application occurs, the application restart control means 3400 controls whether or not to restart the application in question, in accordance with the user selection made by the user selection means 3401. When restarting the application, the application restart control means 3400 uses the application execution information 3411.

[0366] FIG. 35 shows examples of the reproduction of a broadcast program by a broadcast signal, instructions by an AIT, execution and control of a broadcast-managed application, and user operations and selections, all of which are related on a time axis in the eighth embodiment.

[0367] The broadcast managed application, which is a type of broadcast cooperative application used in the broadcast communication cooperative system of this embodiment, has its operations such as start / stop controlled based on information such as the application control code 903 of the AIT included in the broadcast signal. Of course, the operation of the broadcast managed application may be controlled based on an instruction operation by the user.

[0368] When the AIT or the like is used to control the launch operation of a broadcast-managed application linked to a broadcast program, information such as the application control code 903 in the AIT for instructing the launch is included in the broadcast signal at least at the start of the broadcast program. Furthermore, this information must be included in the broadcast signal not only at the start of the broadcast program but also continuously throughout the broadcast of the broadcast program. This is because users do not always watch a broadcast program from the beginning, but may start watching it halfway through. If the broadcast signal does not contain the above information when playing a broadcast program from the middle, the broadcast-managed application cannot be launched.

[0369] Therefore, information such as the AIT is transmitted continuously from the beginning to the end of the broadcast program. For example, the information may be transmitted periodically, such as once every few seconds. The broadcast receiving device 100 periodically references and acquires information such as the AIT contained in the broadcast signal to check whether the information content has been updated. This allows the launch of a broadcast-managed app to be controlled even when the user starts watching a broadcast program partway through.

[0370] Meanwhile, information such as application control code 903 for instructing the termination of execution of a broadcast-managed app may be included in the broadcast signal at the minimum timing when the app is to be terminated, for example, at the end of a broadcast program. Alternatively, if the broadcast-managed app is to be terminated at any timing during the broadcast of a broadcast program, for example, at a time designated by the broadcast station, termination instruction information may be included in the broadcast signal at that timing. Upon receiving the termination instruction, broadcast receiving device 100 terminates execution of the broadcast-managed app.

[0371] Furthermore, when terminating a broadcast-managed app at any timing during the broadcast of a broadcast program, for example, at a point based on a user operation, the following control operations can be performed: For example, broadcast receiving device 100 terminates execution of a broadcast-managed app based on the user's operation to change the frequency channel, i.e., select the channel or program to be played, or issue an instruction to terminate the app, using mobile information terminal 700 or a remote control.

[0372] The example of the AIT in FIG. 35 shows an example in which instruction information is continuously and periodically included while a broadcast program is being aired, as described above. For example, there is a broadcast managed application M1 linked to broadcast program A. During the period from time t1 to t3 when broadcast program A is being aired, AITs are periodically distributed, including the beginning and end. The first AIT at t1 includes at least an instruction to automatically start the broadcast managed application M1. The last AIT at t3 includes at least an instruction to automatically end the broadcast managed application M1. As a result, as shown in (a), the broadcast managed application M1 is automatically executed during the period from t1 to t3. During the period from t1 to t3, AITs are distributed in the same manner as at t2. The same applies to broadcast program B and broadcast managed application M2.

[0373] There are cases where a broadcast-managed app is terminated based on a user instruction during the broadcast of the above-mentioned broadcast program. Even in this case, while the broadcast of the broadcast program continues, the PMT, AIT, etc. included in the broadcast signal may continue to instruct the app to be automatically launched with priority while the broadcast program continues.

[0374] (b) of FIG. 35 shows an example in which broadcast managed app M2 is started in the middle of broadcast program B and then terminated in the middle of broadcast program B. Assume that broadcast program B is played back by changing the frequency channel (ch) at time t5, for example, through the user operation of (c). Thereafter, broadcast managed app M2 is started in response to an instruction to start broadcast managed app M2 by an AIT at, for example, a regular time t6. Also, assume that an instruction to change the frequency channel (ch) or terminate broadcast managed app M2 is given at time t7, for example, through the user operation of (c). As a result, broadcast managed app M2 is terminated.

[0375] However, when a broadcast-managed app is terminated by the user's instruction, it goes without saying that it is undesirable for the same broadcast-managed app to be automatically restarted based on the descriptions in the PMT, AIT, etc. For example, after an app is terminated, the AIT is checked periodically immediately, and the app is automatically restarted in accordance with the automatic startup instructions in the AIT. From the user's perspective, the app is restarted immediately despite the user's instruction to terminate the app. Therefore, a configuration that disables the automatic restart of the same broadcast-managed app as described above is conceivable.

[0376] On the other hand, it should also be considered that the instruction to terminate a broadcast-managed app may be an error on the part of the user. If this possibility is taken into consideration, it is not desirable to completely disable automatic restart of the same broadcast-managed app. From the user's perspective, if the app is terminated by mistake, it is inconvenient because it cannot be immediately restarted or restored.

[0377] The broadcast receiving device 100 of the eighth embodiment has a function of performing control taking into consideration restart of the above-mentioned application. In the eighth embodiment, an example of control of restart of the broadcast managed application in the broadcast receiving device 100 will be described in which the execution of the broadcast managed application is terminated based on a user instruction or operation at any timing during a broadcast program, and the automatic start of the same application with priority is still instructed by information such as an AIT included in the broadcast wave.

[0378] (d) of Figure 35 shows a case where broadcast managed application M2 is terminated in the middle of broadcast program B as in (b), but the instruction to start it continues in the AIT at time t8, so broadcast managed application M2 is immediately restarted.

[0379] (e) to (g) in Fig. 35 show examples of control by the broadcast receiving device 100 of the eighth embodiment. In the eighth embodiment, in a case like (d), confirmation of user selection is performed as in (e). In response to this, the first control as in (f) prevents the broadcast managed application M2 from being restarted and re-executed. Furthermore, the second control as in (g) controls the broadcast managed application M2 to be restarted and re-executed. The user selection as in (e) is input of an instruction on the screen, confirmation of user setting information, etc.

[0380] [Operation sequence when restarting the broadcast managed app] FIG. 36 shows an example of a control operation sequence including a process for restarting a broadcast managed app in the broadcast receiving device 100 of Example 8. FIG. 36 shows a series of control operation flows when it is specified and instructed that a broadcast managed app be preferentially started. The broadcast receiving device 100 terminates the broadcast managed app that was automatically started based on the AIT of the broadcast signal when the user starts watching a broadcast program, in response to a user instruction. Furthermore, the broadcast receiving device 100 appropriately checks the PMT and AIT, and controls whether or not to restart the broadcast managed app that was once terminated, in response to a user selection.

[0381] 36, the broadcast receiving device 100 acquires a TS by performing tuning processing of a frequency channel desired by the user using the tuner / demodulator unit 131. Then, at S1500, the broadcast receiving device 100 performs processing similar to, for example, S101 to S108 in FIG. 7A described above. That is, the broadcast receiving device 100 checks the startup priority from the PMT, checks instructions such as automatic startup using the application control code in the AIT, checks the executable state from the application profile, and appropriately acquires a broadcast managed application, which is a predetermined broadcast-linked application, from a provider server or the like. The broadcast receiving device 100 starts the broadcast managed application using the application engine 162 under the control of the application control unit 161.

[0382] After the process of S1500, in S1509, the broadcast receiving device 100 causes the application control unit 161 to temporarily store, in other words, cache, information about the launched broadcast managed application and its status in a temporary storage area (storage unit 3402 in FIG. 34 ) of the RAM 104 as application execution information 3411. The process of S1509 may be performed in accordance with the cache information 908 of the AIT described above.

[0383] The application execution information 3411 includes information such as PMT and AIT acquired during the processing of S1500, data of the HTML document that constitutes the broadcast managed application, attributes related to the application such as the broadcast program name and service ID (frequency channel), etc. For the sake of explanation, this information is referred to as application execution information 3411, but it is also possible to manage the information individually.

[0384] 36, it is assumed that the user issues an instruction to terminate the broadcast-managed application using the mobile information terminal 700, a remote control, or the like at any desired timing during the broadcast program, without waiting for the broadcast program to end (S1510). This corresponds to time t7 of the user operation in (c) in FIG. 35. Then, the broadcast receiving device 100 causes the application engine 162 to terminate execution of the broadcast-managed application (S1511).

[0385] When the broadcast managed application is terminated in S1511, the broadcast receiving device 100 again acquires a PMT data string by the main control unit 101 (S1512), and acquires an AIT data string by the application control unit 161 (S1513). The acquisition of information in S1512 and S1513 may be one of the processes executed continuously and periodically while the broadcast program is being aired, as shown in Fig. 35, or the broadcast receiving device 100 may perform processing to instantly acquire and refer to the information. Note that the PMT includes information indicating the AIT, and here both the PMT and the AIT are referenced and acquired.

[0386] Next, in the process of S1514, the broadcast receiving device 100 checks whether the information in the AIT of S1513 above instructs the startup of the same application as when the application was temporarily stored in S1509, for example, automatic startup with priority given to the broadcast-managed application. In other words, in S1514, it is checked whether execution of the same HTML document is instructed, and whether the display content by the broadcast-managed application has been updated. In S1514, if the information content of the AIT of S1513 is the same as the information content of the AIT of the application execution information 3411 when the application was temporarily stored in S1509, that is, if the startup of the same application and the execution of the same document are instructed and the display content has not been updated (Yes), the process proceeds to S1516. In S1514, if the information content of the AIT in S1513 is different from the information content of the AIT in the application execution information 3411 at the time of temporary storage in S1509, that is, if an instruction to launch a different application or execute a different document has been issued and the display content has been updated (No), the process proceeds to S1515.

[0387] It should be noted that, for example, while a broadcast program is being aired, there is a possibility that the information content of the AIT included in the broadcast signal may be partially changed. For example, this may be the case when the description of a link to an HTML document to which a transition can be made is changed among multiple HTML documents that constitute the same broadcast-linked application. Alternatively, this may be the case when the description of a link is changed so that a transition can be made to an HTML document of a different application. In S1514, the presence or absence of such a change is also included in the determination.

[0388] When proceeding to S1515, the broadcast receiving device 100 prevents the broadcast managed application that was terminated in S1511 from being restarted. In this case, the broadcast receiving device 100 may perform processing such as starting up a predetermined broadcast managed application or updating display content again using the information content of the changed PMT and AIT acquired in S1512 and S1513, in the same manner as the processing of S101 to S108 in Fig. 7A. Then, this processing in Fig. 36 ends.

[0389] Fig. 37 shows a restart prevention screen, which is an example of a screen displayed at S1515 above. The broadcast receiving device 100 may display a screen and information such as that shown in Fig. 37 at S1515 above. The screen of Fig. 37 displays a predetermined mark 173h1 or a message indicating that restart of the broadcast-managed app has been prevented on a broadcast program screen 173h, for example, in a corner of the screen. This allows the user to recognize that restart of the app has been prevented.

[0390] On the other hand, if the process proceeds to S1516, the broadcast receiving device 100 performs control to restart the broadcast managed application that was terminated in S1511. In S1516, the broadcast receiving device 100 displays, on the screen of the video display unit 173, information for restarting the broadcast managed application that was terminated in S1511 in response to a user selection operation.

[0391] FIG. 38 shows a restart confirmation screen, which is an example of the screen displayed in S1516. This screen displays a message box 173h2 for confirming whether to restart on a broadcast program screen 173h. Alternatively, this screen may display a restart icon 173h3 in a corner of the screen. The broadcast receiving device 100 accepts a user selection operation on the information on this screen, in other words, an instruction input operation to select whether to restart or not. The message box 173h2 includes a message for confirming whether to restart the broadcast managed app and "Yes" and "No" buttons. The broadcast receiving device 100 restarts the app in response to the "Yes" selection operation.

[0392] Icon 173h3 indicates a predetermined broadcast-managed app. The broadcast receiving device 100 restarts the app by selecting icon 173h3. Icon 173h3 may be the same as icon 173b0, which indicates to the user which broadcast-linked app can be launched, as shown in FIG. 12A. Furthermore, after a predetermined time has elapsed since displaying message box 173h2 or icon 173h3, the broadcast receiving device 100 automatically erases the message box 173h2 or icon 173h3, preventing restart in this case. Since the confirmation information remains displayed for a predetermined time, the user can restart the app by selecting icon 173h3 remaining on the screen. The user can easily select whether or not to restart the app from the above screen, depending on their own convenience at the time.

[0393] 36, in S1517, the user selects the restart icon 173h3 or the like using the mobile information terminal 700, a remote control, or other operating means. Here, for example, it is assumed that the user selects the restart icon 173h3 on the screen from the mobile information terminal 700. The same applies to selecting the "Yes" button in the message box 173h2. In accordance with the user's selection, the broadcast receiving device 100 internally instructs the broadcast managed application that was terminated in S1511 to be restarted.

[0394] When restarting a broadcast managed application, first, in S1518, the broadcast receiving device 100 causes the application control unit 161 to read data of the HTML document that constitutes the application in the application execution information 3411 that was temporarily stored in S1509. Then, in S1519, the broadcast receiving device 100 causes the application engine 162 to execute the HTML document under the control of the application control unit 161. This restarts the broadcast managed application that was terminated in S1511.

[0395] If the user does not want to restart the broadcast-managed app that was instructed in S1510 and ended in S1511, the user can use the operating means to input an instruction not to restart in S1517, or can leave it as is without inputting an instruction. For example, the user can select the "No" button in message box 173h2, press the back key 741ab described above, etc. In this way, broadcast receiving device 100 does not internally issue an instruction to restart, and the restart confirmation screen is also cleared.

[0396] As described above, according to the broadcast receiving device 100 of the eighth embodiment, even when a broadcast-managed app is terminated by a user operation or the like during a broadcast program and the same app continues to be instructed to be preferentially automatically started by information such as the AIT of the broadcast wave, restart of the app can be suitably controlled according to the user's selection. The user can control whether or not to restart the app with a simple operation. The user can quickly restart the app even in the case of an operation error, which is highly convenient. In other words, the broadcast receiving device 100 of this embodiment can execute functions with higher added value.

[0397] As a modification of the eighth embodiment, the process of restarting an application in steps S1516 to S1519 may be executed in accordance with confirmation of user setting information in the broadcast receiving device 100 or the mobile information terminal 700, as in the sixth embodiment. For example, the broadcast receiving device 100 provides a screen for user setting regarding whether restarting the application is permitted, and stores a setting value based on a user operation in the storage unit 110 (or the storage unit 710 in the case of the mobile information terminal 700) in advance. The broadcast receiving device 100 checks the setting value in the broadcast receiving device 100 or the mobile information terminal 700, instead of the restart confirmation screen in step S1516. If restart is permitted with the setting value, the broadcast receiving device 100 restarts the application.

[0398] As a modification of the eighth embodiment, the broadcast receiving device 100 may adjust and control the transparency of the display of the broadcast managed app on the screen instead of terminating the broadcast managed app in S1511. The display of the broadcast managed app when it is running may be set to transparency = 0%, and the display of the broadcast managed app when it is terminated may be set to transparency = 100%. When terminating the app in S1511, the broadcast receiving device 100 does not terminate the app as a computer process but maintains it, and changes the transparency of the display of the app's execution screen on the screen to 100% to make it invisible to the user. Furthermore, when restarting the app in S1516 to S1517, the broadcast receiving device 100 restores the transparency of the display of the app on the screen to its original state of 0%, making it visible to the user. In this modification, the processes in S1518 to S1519 do not require the reading and execution of the HTML document of the app execution information 3411 in the temporary storage area, thereby reducing the processing load. The transmittance may be a value other than 0% or 100%. [Example]

[0399] The following describes a ninth embodiment of the present invention. The configuration, effects, etc. of this embodiment are the same as those of the eighth embodiment unless otherwise specified. Therefore, the following mainly describes the differences between this embodiment and the eighth embodiment, and omits explanations of common points as much as possible to avoid duplication.

[0400] The broadcast managed application used in the broadcast communication cooperation system of Example 9 is not only controlled for its operations such as start / stop based on information such as AIT included in the broadcast signal, but also capable of controlling event operations such as page update based on event messages appropriately included in the broadcast signal. In this example, page update refers to a change in part or all of information such as text and images constituting an application screen displayed on the display unit 173 by execution of the broadcast managed application, or a transition from an HTML document corresponding to the screen to an HTML document corresponding to another application screen linked thereto. The page update is also illustrated in the above-mentioned FIG. 27 as a transition between applications and between HTML documents. An HTML document corresponds to a page. An update corresponds to a change in an HTML document constituting an application.

[0401] If an AIT or other message included in the broadcast wave continues to instruct the broadcast-managed app to automatically start up with priority, event messages for controlling the event operation of that app will also continue to be included in the broadcast wave as necessary. Even if the user terminates the broadcast-managed app of their own volition, page updates may occur based on event messages or other messages in the broadcast wave. In this case, the execution and display content of the app will change due to page updates before and after termination.

[0402] In this case, it should be considered that the user may wish to restart the broadcast-managed app that was once terminated. In other words, the user may wish to view page information newly provided by a page update. The broadcast receiving device 100 of the ninth embodiment has a function to appropriately control the restart of the app, taking into consideration the case and situation of the page update, etc.

[0403] [Operation sequence when restarting the broadcast managed app] 39 shows an example of an operation sequence for controlling restart of a broadcast managed app in the broadcast receiving device 100 of Example 9 when a command to give priority to starting the broadcast managed app is given. In FIG. 39, the broadcast receiving device 100 terminates the broadcast managed app that was automatically started when viewing of a broadcast program is started, in response to a command from the user. Furthermore, the broadcast receiving device 100 appropriately checks the AIT and the like, and if the information content has not been updated, controls whether or not to restart the terminated broadcast managed app in accordance with an event message newly acquired from the broadcast wave and in accordance with the user's selection.

[0404] In Figure 39, the processes of S1600 to S1615 are the same as the processes of S1500 to S1515 in Figure 36. An event message is included in the broadcast wave as appropriate. In S1600, the broadcast receiving device 100 launches a predetermined broadcast-managed application by performing processes similar to those of S101 to S108 in Figure 7A. After S1600, in S1609, the broadcast receiving device 100 stores information about the launched broadcast-managed application in a temporary storage area as application execution information 3411.

[0405] As an example, assume that up to S1609, the first page (e.g., HTML11 of App1 in FIG. 27) to the third page (e.g., HTML13) of a certain broadcast-managed application are executed through transitions between pages and viewed by the user. In S1609, the contents of this execution and viewing are cached as application execution information 3411.

[0406] At S1610, a user operation instructs the broadcast managed application to be terminated during a broadcast program. At S1611, the broadcast receiving device 100 terminates execution of the broadcast managed application. At S1612, the broadcast receiving device 100 acquires a PMT data sequence again, and at S1613, acquires an AIT data sequence.

[0407] Next, in S1614, if the AIT information acquired in S1613 above is not identical to the AIT information content of the application execution information 3411 temporarily stored in S1609 above (No), the process proceeds to S1615. In this case, the broadcast managed application terminated in S1611 is not restarted. In S1615, the process of starting the predetermined broadcast managed application is performed again using the updated PMT and AIT acquired in S1612 and S1613.

[0408] On the other hand, if the information in the AIT acquired in S1613 is identical to the information content of the AIT in the application execution information 3411 temporarily stored in S1609 (Yes), the process proceeds to S1616, where control is performed to restart the broadcast-managed application terminated in S1611. From S1616 onwards, the broadcast receiving device 100 of the ninth embodiment monitors and acquires event messages contained in the broadcast waves until the frequency channel is changed or the information such as the PMT and AIT contained in the broadcast waves is updated. Note that if the frequency channel is changed or the information such as the PMT and AIT contained in the broadcast waves is updated, the broadcast receiving device 100 proceeds to the process in S1615 and performs the same process. The event message may be distributed periodically, for example, like the AIT. The broadcast receiving device 100 may acquire the event message periodically, for example.

[0409] As an example, assume that in step S1616, a transition to and display of the fourth page (HTML14 of App1 in FIG. 27) and subsequent pages of the broadcast managed application is instructed as a page update due to an event. The user has not yet viewed the fourth page and subsequent pages.

[0410] At S1616, the broadcast receiving device 100 acquires the event message separated by the first separation unit 132 via the application control unit 161. Next, the broadcast receiving device 100 analyzes the acquired event message and determines the analysis result. At S1617, the broadcast receiving device 100 checks whether the event message acquired at S1616 instructs the broadcast managed app that was terminated at S1611 to perform a page update or the like. If at S1617 the event is not an instruction for a page update or the like (No), the process of FIG. 39 is terminated. In other words, the broadcast managed app that was terminated at S1611 is not restarted.

[0411] On the other hand, if the event is an instruction for a page update or the like (Yes) in S1617, the process proceeds to S1618, where control is performed to restart the broadcast-managed application terminated in S1611. In S1618, the broadcast receiving device 100 reads the HTML document of the application execution information 3411 temporarily stored in S1609. This document is the one before the page update. Furthermore, in S1619, the broadcast receiving device 100 transmits the event message acquired in S1616 to the application engine 162, and the application engine 162 executes the HTML document read in S1618 under the control of the application control unit 161. During the processing of S1619, the broadcast receiving device 100 applies the instruction content of the event message of S1616 to the HTML document, thereby reflecting the page update. As a result, the broadcast-managed application terminated in S1611 is restarted. The display content of the application screen after the restart is the state after the page update.

[0412] As an example, after the restart, the broadcast managed app screen will display the fourth page and subsequent pages. After restarting, the user can view the pages from page 4 onward that were not viewed before the shutdown.

[0413] At the time of the restart, the broadcast receiving device 100 may be controlled so as to automatically transition to and display a new page (for example, the fourth page) after the page update. At this time, the broadcast receiving device 100 may also display a message on the screen indicating that a page update has occurred or that a transition has been made to a new page. In this case, the user does not have to go through the trouble of performing operations such as transitioning between pages.

[0414] Furthermore, upon restarting, the broadcast receiving device 100 may control the display to restore the page before the page update (for example, the third page), display a message on the screen to confirm the page update, and, in response to a user operation, transition to a new page after the page update (for example, the fourth page). In this case, the user can easily recognize the status of the page update.

[0415] FIG. 40 shows an update confirmation screen, which is an example of a screen that prompts the user regarding restarting in the case of a page update and allows the user to restart according to their selection. For example, the broadcast receiving device 100 displays a screen like that shown in FIG. 40 when the event in S1617 is a page update. This screen displays a message box 173h4. The message box 173h4 includes a message indicating that the page content of the broadcast-managed app has been updated and a button for selecting whether or not to restart. If restart is selected on this screen, the broadcast receiving device 100 restarts the app. This screen allows the user to easily recognize the situation, restart the app according to the situation at the time, and view the updated page content.

[0416] As described above, the broadcast receiving device 100 of the ninth embodiment can suitably control the restart of a broadcast managed app that has been terminated in response to a page update or the like due to an event message acquired from broadcast waves and in response to a user selection. In other words, the broadcast receiving device 100 of the present embodiment can execute functions with higher added value.

[0417] As a variation of the ninth embodiment, the broadcast receiving device 100 may execute the above-described processes of S1616 to S1619, i.e., the process of restarting an app that reflects a page update due to an event message, in accordance with confirmation of user setting information on the broadcast receiving device 100 or the mobile information terminal 700, as in the sixth embodiment. For example, the broadcast receiving device 100 provides a screen for user setting regarding whether or not to allow restart of the above-described app and restart in the event of a page update due to an event, and stores setting values ​​based on user operations. When acquiring the event message in S1616, the broadcast receiving device 100 checks the setting values ​​and determines whether or not to restart the app.

[0418] Although the embodiments of the present invention have been described above using Examples 1 to 9, the configurations for realizing the technology of the present invention are not limited to these examples and can be modified in various ways. For example, part of the configuration of one example can be replaced with the configuration of another example, or the configuration of another example can be added to the configuration of one example. All of these fall within the scope of the present invention. Furthermore, the numerical values, messages, etc. appearing in the text and figures are merely examples, and the effects of the present invention can be achieved even if different ones are used. Some or all of the functions of the present invention described above may be realized in hardware, for example, by designing an integrated circuit, or in software, for example, by a microprocessor unit interpreting and executing an operating program that realizes each function, or may be realized by a combination of hardware and software. Furthermore, the control lines and information lines shown in the figures are those considered necessary for explanation and do not necessarily represent all control lines and information lines on the product. In reality, it can be assumed that almost all components are interconnected.

[0419] The software for controlling the broadcast receiving device 100 may be stored in the ROM 103, storage unit 110, etc. of the broadcast receiving device 100 before shipping the product. Alternatively, the software may be acquired from another application server 500, etc. on the Internet 200 via the LAN communication unit 121 after shipping the product. Alternatively, software stored on a memory card, optical disk, etc. may be acquired via the extended interface unit 124, etc. Similarly, the software for controlling the mobile information terminal 700 may be stored in the ROM 703, storage unit 710, etc. of the mobile information terminal 700 before shipping the product. Alternatively, the software may be acquired from another application server 500, etc. on the Internet 200 via the LAN communication unit 721 or mobile telephone network communication unit 722 after shipping the product. Alternatively, software stored on a memory card, optical disk, etc. may be acquired via the extended interface unit 724, etc. [Explanation of symbols]

[0420] 100: Broadcast receiving device, 132: First separation unit, 133: First video decoding unit, 134: First audio decoding unit, 135: First subtitle decoding unit, 141: Data broadcasting reception processing unit, 142: Data broadcasting engine, 151: Streaming reception processing unit, 152: Second separation unit, 153: Second video decoding unit, 154: Second audio decoding unit, 155: Second subtitle decoding unit, 161: Application control unit, 162: Application engine, 171: Video superimposition unit, 172: Audio selection unit selection unit, 173: video display unit, 174: speaker, 175: video output unit, 176: audio output unit, 181: presentation synchronization control unit, 191: terminal cooperation control unit, 300: broadcasting station server, 400: service provider server, 500: other application server, 600: mobile telephone communication server, 600b: base station, 700: mobile information terminal, 3400: application restart control means, 3401: user selection means, 3402: memory unit, 3411: application execution information.

Claims

[Claim 1] 1. An application launch method for launching an application for accessing broadcast resources in a broadcast receiving device, comprising: the applications for accessing the broadcast resources include a broadcast-managed application activated by application control information included in the broadcast signal, and a non-broadcast-managed application activated by information other than the application control information included in the broadcast signal; a receiving step of receiving a broadcast signal; a document transition range setting step of setting a range of document transition within the broadcast managed application based on application control information included in the received broadcast signal; a first application launch step of launching the broadcast managed application based on the application control information; a launcher screen display step of displaying a launcher screen on the broadcast receiving device by an application launcher provided in the broadcast receiving device; a second application launching step of launching the non-broadcast managed application based on a user operation via the displayed launcher screen; a communication step of communicating with an external mobile terminal; a third application launching step of launching the non-broadcast managed application based on a launch request received in the communication step and initiated by a user operation via the external mobile terminal; Equipped with the first application launch step, when the application control information includes information indicating automatic launch of the broadcast managed application, confirms whether the broadcast managed application is executable, and if executable, acquires and launches the broadcast managed application; The confirmation of whether the broadcast managed application can be executed is performed by checking the functions of the broadcast receiving device required by the broadcast managed application by referring to an application profile included in the application control information. How to launch the application.

Images