JP7660726B2 - Digital broadcast receiving device and method for controlling application operation - Google Patents

Description

The present invention relates to a digital broadcast receiving device and a method for controlling application operation.

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, and recommended programs. 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.

JP 2001-186486 A

A feature of data broadcasting is that television receivers that support digital broadcasting services can receive data broadcasting on their own and can obtain 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 bands, it is difficult to achieve high-definition screen displays or sophisticated effects. This has made it difficult to implement useful, high-value-added functions on current digital broadcasting receivers.

The object of the present invention is to provide a digital broadcast receiver that can perform functions with higher added value.

As a means for solving the above problems, the technology described in the claims is used.
As an example, the technique described in claim 1 is used.

By using the technology of this invention, it is possible to provide a digital broadcast receiver that can perform functions with higher added value.

FIG. 1 is a system configuration diagram of a communication system according to an embodiment. FIG. 1 is a block diagram of a broadcast receiving device according to an embodiment. FIG. 2 is a software configuration diagram of a broadcast receiving device according to an embodiment. FIG. 2 is a block diagram of a broadcasting station server according to an embodiment. FIG. 4 is a block diagram of a service provider server according to an embodiment. FIG. 1 is a block diagram of a portable information terminal according to an embodiment. FIG. 2 is a software configuration diagram of the portable information terminal according to the embodiment. FIG. 4 is a data configuration diagram of application control information according to the embodiment. FIG. 4 is an operational sequence diagram when an application is started up in the broadcast receiving device according to the embodiment. FIG. 4 is an operational sequence diagram when an application is started up in the broadcast receiving device according to the embodiment. FIG. 4 is an operational sequence diagram when an application is started up in the broadcast receiving device according to the embodiment. FIG. 4 is an operation sequence diagram when the mobile information terminal according to the embodiment is linked; FIG. 4 is an operation sequence diagram when the mobile information terminal according to the embodiment is linked; FIG. 4 is an operation sequence diagram when the mobile information terminal according to the embodiment is linked; 4 is an operational sequence diagram when an application is started in the broadcast receiving device and the portable information terminal according to the embodiment. FIG. 4 is a screen display diagram of a basic screen of a linkage control application of the portable information terminal according to the embodiment. FIG. 4 is a screen display diagram of a basic screen of a linkage control application of the portable information terminal according to the embodiment. FIG. 4 is a screen display diagram of a data broadcast screen of the broadcast receiving device according to the embodiment. FIG. 4 is a screen display diagram of a notification screen of the broadcast receiving device according to the embodiment. 4 is a screen display diagram of a broadcast cooperative application launcher of the broadcast receiving device according to the embodiment. 4 is a screen display diagram of a broadcast cooperative application execution screen of the broadcast receiving device according to the embodiment. 4 is a screen display diagram of a broadcast cooperative application execution screen of the broadcast receiving device according to the embodiment. 4 is a screen display diagram of a broadcast cooperative application execution screen of the broadcast receiving device according to the embodiment. 4 is a screen display diagram of a broadcast cooperative application execution screen of the broadcast receiving device according to the embodiment. FIG. 4 is a screen display diagram of an error display screen of the broadcast receiving device according to the embodiment. FIG. 4 is a screen display diagram of a broadcast cooperative application execution screen of the portable information terminal according to the embodiment. FIG. 4 is a screen display diagram of an EPG display screen of the broadcast receiving device according to the embodiment. 4 is a diagram showing detailed information on an EPG display screen of the broadcast receiving device according to the embodiment. 4 is an operational sequence diagram of a broadcast receiving device according to an embodiment when acquiring a broadcast cooperative application. FIG. 4 is an operational sequence diagram during terminal cooperation according to the embodiment. FIG. 4 is an operational sequence diagram during terminal cooperation according to the embodiment. FIG. 4 is an operational sequence diagram during terminal cooperation according to the embodiment. FIG. 4 is an operational sequence diagram during terminal cooperation according to the embodiment. 4 is a screen display diagram of a broadcast cooperative application launcher of the broadcast receiving device according to the embodiment. 4 is a screen display diagram of a broadcast cooperative application launcher of the broadcast receiving device according to the embodiment. 4 is a screen display diagram of a broadcast cooperative application launcher of the broadcast receiving device according to the embodiment. 4 is a screen display diagram of a broadcast cooperative application launcher of the broadcast receiving device according to the embodiment. FIG. 2 is a screen display diagram of the broadcast receiving device according to the embodiment. 11 is a screen display diagram of a broadcast cooperative application launcher of the portable information terminal according to the embodiment. 1 is a diagram showing a system configuration including a broadcast receiving device according to an embodiment and an example of use thereof; 4 is an operational sequence diagram when a broadcast cooperative application of the broadcast receiving device according to the embodiment is started. 4 is an operational sequence diagram when a broadcast cooperative application of the broadcast receiving device according to the embodiment is started. 4 is an operational sequence diagram when a broadcast cooperative application of the broadcast receiving device according to the embodiment is started. FIG. 13 is a screen display diagram of a start confirmation screen of the broadcast receiving device according to the embodiment. FIG. 4 is a screen display diagram of a user setting screen of the broadcast receiving device according to the embodiment. 1 is a diagram showing a system configuration including a broadcast receiving device according to an embodiment and an example of use thereof; 1A and 1B are diagrams illustrating an example of a plurality of types of apps and transitions between the apps according to an embodiment. 4 is an operational sequence diagram when a broadcast cooperative application of the broadcast receiving device according to the embodiment is started. 5A and 5B are diagrams showing an example of control of broadcast program playback and application execution according to an embodiment. FIG. 4 is a screen display diagram of an example of a startup selection screen of the broadcast receiving device according to the embodiment. FIG. 4 is a screen display diagram of an example of a startup selection screen of the broadcast receiving device according to the embodiment. FIG. 4 is a screen display diagram of an example of a multiple application execution screen of the broadcast receiving device according to the embodiment. FIG. 4 is a screen display diagram of an example of a multiple application execution screen of the broadcast receiving device according to the embodiment. 1 is a diagram showing a system configuration including a broadcast receiving device according to an embodiment and an example of use thereof; 5A and 5B are diagrams showing an example of control of broadcast program playback and application execution according to an embodiment. 11 is an operational sequence diagram when a broadcast cooperative app of the broadcast receiving device according to the embodiment is restarted. FIG. 13 is a screen display diagram of an example of a restart prevention screen of the broadcast receiving device according to the embodiment. FIG. 11 is a screen display diagram of an example of a restart confirmation screen of the broadcast receiving device according to the embodiment. 11 is an operational sequence diagram when a broadcast cooperative app of the broadcast receiving device according to the embodiment is restarted. FIG. 13 is a screen display diagram showing an example of an update confirmation screen of the broadcast receiving device according to the embodiment.

Below, examples of embodiments of the present invention are described with reference to the drawings.

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 one example of BS/terrestrial digital broadcasting that can be received by the broadcast receiving device of this embodiment, a plurality of 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 obtained by dividing a data sequence such as a video/audio elementary stream (ES) or program specific information (PSI)/service information (SI) and adding a TS header.

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

SI is an extension of PSI to include program information, etc., and includes information on the Electronic Program Guide (EPG) defined 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, series information, broadcast station SI transmission information, etc. The SDT includes information such as a network ID for identifying the network, a TS ID for identifying the TS, and a service ID (so-called channel number) for identifying individual services (so-called channels) within the network. The 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 (so-called program). The TOT includes information related to the current date and time.

The TS also includes PCR (Program Clock Reference) information, which is the basis for playback timing in the decoder, and BML (Broadcast Markup Language) documents that are subsetted based on the BML specifications defined in ARIB STD-B24.

The broadcast receiving device of this embodiment receives and decodes the TS composed of the video/audio ES and various information, etc., and is therefore capable of providing the user with broadcast programs, EPGs, data broadcast screens produced using BML, etc.

The broadcast receiving device of this embodiment is compatible with a broadcasting and communication cooperation system that combines a digital broadcasting service with a function that utilizes a broadband network, and combines the acquisition of additional content via a broadband network, computation processing in a server device, and presentation processing in cooperation with a mobile terminal device with the digital broadcasting service. In order to realize the broadcasting and communication cooperation system, the broadcast receiving device of this embodiment is capable of executing applications described in HTML (Hyper Text Markup Language) or the like. In addition, the broadcasting and communication cooperation system compatible with this broadcasting receiving device uses an extended BML specification, application control information (Application Information Table: AIT) in the broadcasting and communication cooperation system, and extended PSI/SI information required when transmitting an application by broadcast waves. The AIT is information for providing or disseminating various information required to start an application, such as the acquisition destination of the application, and control information for controlling the start/end of the application.

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

Next, we will explain a specific configuration example of the embodiment in this example.

[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, an antenna 100a, a broadband network 200 such as the Internet and a router device 210, a radio tower 300t of a broadcast station, a broadcast station server 300, a service provider server 400, other application servers 500, a mobile telephone communication server 600, a base station 600b of a mobile telephone communication network, and a mobile information terminal 700.

The broadcast receiving device 100 is a television receiver that has a function corresponding to 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 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 by communicating with each server device on the Internet 200.

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

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 a television receiver 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 such as the program title, program ID, program summary, cast, broadcast date and time of each broadcast program, 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 through an API (Application Programming Interface) provided by the broadcasting station server 300.

The service provider server 400 is a server device prepared by a service provider to provide services through the broadcasting and communication cooperation system. The service provider server 400 stores, manages, and distributes video content and metadata provided by the broadcasting station server 300, and content and applications created for the broadcasting and communication cooperation 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. A plurality of service provider servers 400 may be prepared for each different service. The functions of the service provider server 400 may also be provided by the broadcasting station server 300.

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 collaboration system.

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

[Hardware configuration of broadcast receiving device]
2A is a block diagram showing an example of the internal configuration of the broadcast receiving device 100. The broadcast receiving device 100 is composed of 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 expansion interface unit 124, a digital interface unit 125, a tuner/demodulation 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.

The main control unit 101 is a microprocessor unit that controls the entire broadcast receiving device 100 according to a predetermined operating program. The system bus 102 is a data communication path for transmitting and receiving data between the main control unit 101 and each operating block within the broadcast receiving device 100.

ROM (Read Only Memory) 103 is a memory in which basic operation programs such as an operating system and other operation programs are stored, and may be a rewritable ROM such as an EEPROM (Electrically Erasable Programmable ROM) or a 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 portion of the storage area in storage unit 110, rather than being an independent configuration as shown in FIG. 2A.

The storage unit 110 stores the operation program 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 operation programs downloaded from the network and various data created by the operation programs. It can also store content such as video, still images, and audio obtained from broadcast waves or downloaded from the network. A portion of the storage unit 110 may replace all or part of the functions of the ROM 103. In addition, the storage unit 110 needs to retain the stored information even when power is not being supplied from an external source to the broadcast receiving device 100. Therefore, for example, devices such as flash ROM, semiconductor element memory such as SSD (Solid State Drive), and magnetic disk drive such as HDD (Hard Disc Drive) are used.

The operating programs stored in the ROM 103 and the storage unit 110 can be updated and their functions expanded by downloading them from each server device on the Internet 200.

The LAN (Local Area Network) communication unit 121 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 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, and the like. 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, and the like.

The tuner/demodulator 131 receives broadcast waves from the radio tower 300t via the antenna 100a, and tunes (selects) the channel of the service desired by the user under the control of the main controller 101. Furthermore, the tuner/demodulator 131 demodulates the received broadcast signal to obtain the 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 of multiple screens and recording of other programs. In addition, access restrictions for the demodulated TS may be controlled under the control of the main controller 101.

The first separation unit 132 inputs the TS output from the tuner/demodulation unit 131, separates it into various data strings such as a video data string, an audio data string, a subtitle data string, a program information data string, an AIT data string, a BML data string, etc., and outputs them. These data strings may be in ES format, for example. The first video decoding unit 133 decodes the video data string input from the first separation unit 132 and outputs video information. The first audio decoding unit 134 decodes the audio data string input from the first separation unit 132 and outputs audio information. The first subtitle decoding unit 135 decodes the subtitle data string input from the first separation unit 132 and outputs subtitle information.

The data broadcasting reception processing unit 141 decodes the BML data string input from the first separation unit 132 and reproduces the 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.

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 the program stream (PS) of the video content and the like. In addition, under the control of the main control unit 101, it may also control DRM (Digital Rights Management) processing for the acquired PS.

The second separation unit 152 inputs the PS output from the streaming reception processing unit 151, separates it into various data strings such as a video data string, an audio data string, and a subtitle data string, and outputs them. These data strings may be in ES format, for example. The second video decoding unit 153, the second audio decoding unit 154, and the second subtitle decoding unit 155 perform the same processing as the first video decoding unit 133, the first audio decoding unit 134, and the first subtitle decoding unit 135, respectively, and therefore their explanations are omitted.

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.

The application control unit 161, based on the AIT data string input from the first separation unit or the AIT files acquired from each server device on the Internet 200, works on the application engine 162 with respect to applications created for the broadcasting and communication cooperation system, and controls and manages the life cycle and events for each application. In addition, depending on the state of the application and the instructions of the AIT, it appropriately controls the functional constraints of the application. The application engine 162 is an HTML browser that acquires and executes applications created for the broadcasting and communication cooperation system based on the control of the application control unit 161.

The video superimposition unit 171 inputs the video information output from the first video decoding unit 133, the subtitle information output from the first subtitle decoding unit 135, the data broadcast 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 is equipped with a video RAM (not shown), and the video display unit 173 and the like are driven based on the video information input to the video RAM. In addition, the video superimposition unit 171 performs scaling processing and superimposition processing of EPG screen information created based on the program information data string output from the first separation unit 132, as necessary, based on the control of the main control unit 101.

The audio selection unit 172 inputs the audio information output from the first audio decoding unit 134, the audio information output from the second audio decoding unit 154, and the application execution audio information output from the application engine 162, and selects and outputs the audio information as appropriate according to the control of the main control unit 101.

The video display unit 173 is a display device such as a liquid crystal panel, and provides the video information selected and/or superimposed by the video superimposition unit 171 to the user of the broadcast receiving device 100. The speaker 174 provides the audio information 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 selected and/or superimposed by the video superimposition unit 171. The audio output unit 176 is an audio output interface that outputs the audio information output from the audio selection unit 172. As described 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.

The presentation synchronization control unit 181 controls the presentation synchronization on the video display unit 173 and speaker 174, or on the video output unit 175 and audio output unit 176, of the video information and audio information obtained by decoding the TS obtained from the broadcast waves, the video information and audio information 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.

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, application linking, etc.

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 composed of an analog video/audio interface, a USB (Universal Serial Bus) interface, a memory interface, etc. The analog video/audio interface inputs analog video/audio signals from external video/audio output devices, outputs analog video/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.

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 directly outputting the TS acquired by the tuner/demodulator unit 131 and the PS acquired by the streaming reception processing unit 151. The digital interface unit 125 may also control the TS or PS inputted from the digital interface unit 125 to be inputted to the first separation unit 132 or the second separation unit 152. The digital content stored in the storage unit 110 may be outputted 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 or an HDMI terminal, etc., and may output or input data in a format conforming to the DVI specification or the HDMI specification, etc. The data may be outputted or inputted in a serial data format conforming to the IEEE 1394 specification, etc.

The broadcast receiving device 100 may be a television receiver, an optical disk drive recorder such as a DVD (Digital Versatile Disc) recorder, a magnetic disk drive recorder such as a HDD recorder, a STB (Set Top Box), etc. It may also be a PC (Personal Computer), tablet terminal, game console, etc. equipped with a digital broadcast receiving function and a broadcast communication linkage function. If the broadcast receiving device 100 is a DVD recorder, HDD recorder, STB, etc., the video display unit 173 and speaker 174 may not be provided. By connecting an external monitor and an external speaker to the video output unit 175 and audio output unit 176, the same operation as the broadcast receiving device 100 of this embodiment is possible.

[Software configuration of broadcast receiving device]
2B is a software configuration diagram of the broadcast receiving device 100 of this embodiment, and shows the software configuration in the ROM 103, the RAM 104, and the 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.

The basic operation program 1001 stored in ROM 103 is expanded in RAM 104, and the main control unit 101 executes the expanded basic operation program to form a basic operation execution unit 1101. The reception function program 1002, BML browser program 1003, and HTML browser program 1004 stored in the storage unit 110 are each expanded in RAM 104, and the main control unit 101 executes each of the expanded operation programs to form a reception 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 necessary.

In the following, for simplicity, the process in which the main control unit 101 controls each operation block by expanding the basic operation program 1001 stored in the ROM 103 into the RAM 104 and executing it will be described as the basic operation execution unit 1101 controlling each operation block. Similar descriptions will be used for the other operation programs.

The receiving function execution unit 1102 controls each operation block of the broadcast receiving device 100 to realize the broadcast receiving function and the broadcast communication cooperation function. In particular, the broadcast program playback unit 1102a mainly controls the tuner/demodulation unit 131, the first separation unit 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 the BML browser engine 1103 deployed on the RAM 104. In addition, the communication content playback unit 1102b mainly controls the streaming reception processing unit 151, the second separation unit 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 linkage management unit 1102d mainly controls the terminal linkage control unit 191.

The operating programs may be stored in the ROM 103 and/or the storage unit 110 beforehand at the time of product shipment. After product shipment, they may be acquired via the LAN communication unit 121 from other application servers 500 on the Internet 200. In addition, the operating programs stored on a memory card, optical disk, etc. may be acquired via the expansion interface unit 124, etc.

[Broadcast 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.

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.

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 such as the program title, program ID, program summary, cast, broadcast date and time, etc., of each broadcast program.

The basic operation program 3001 and the content management/distribution program 3002 stored in the storage unit 310 are each expanded in the 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.

In the following, for ease of explanation, the process in which the main control unit 301 expands the basic operation program 3001 stored in the storage unit 310 into the RAM 304 and executes it to control each operation block will be described as the basic operation execution unit 3101 controlling each operation block. Similar descriptions will be used for the other operation programs.

The content management/distribution execution unit 3102 manages the video content and each piece of metadata stored in the video content storage area 3011 and metadata storage area 3012, and controls the provision of the video content and each piece of metadata to the service provider based on a contract. Furthermore, when providing the video content and each piece of 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.

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

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

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 within the service provider server 400. The RAM 404 serves as a work area when each operation program is executed.

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 by 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, for distribution in response to requests from each television receiver.

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 in the 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.

In the following, for ease of explanation, the process in which the main control unit 401 expands the basic operation program 4001 stored in the storage unit 410 into the RAM 404 and executes it to control each operation block will be described as the basic operation execution unit 4101 controlling each operation block. Similar descriptions will be used for the other operation programs.

The content management/distribution execution unit 4102 acquires video content and other metadata from the broadcast station server 300, manages the video content and other metadata stored in the video content storage area 4011 and metadata storage area 4012, and controls the distribution of the video content and other 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 for each television receiver, as necessary.

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 equipped with an encoding circuit, a decoding circuit, etc.

[Hardware configuration of mobile information terminal]
5A is a block diagram showing an example of the internal configuration of a portable information terminal 700. The portable 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.

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.

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

The storage unit 710 stores the operating program and operating 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 video, 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 from an external source to the mobile information terminal 700. Therefore, for example, a flash ROM, SSD, HDD, or other device is used.

The operating programs stored in the ROM 703 and the storage unit 710 can be updated and their functions expanded by downloading them from each server device on the Internet 200.

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 made via a wireless connection such as Wi-Fi (registered trademark). The mobile telephone network communication unit 722 performs telephone communication (calls) and data transmission and reception through wireless communication with the base station 600b of the mobile telephone communication network. The NFC communication unit 723 performs wireless communication when in close proximity to a corresponding 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 and an infrared communication unit.

The expansion interface unit 724 is a group of interfaces for expanding the functions of the portable information terminal 700, and in this embodiment, is composed of 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 devices. The memory interface connects to a memory card or other memory medium to send and receive data.

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 arranged on top of the display unit 741 and operation keys 730k arranged with button switches. Only one of them 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.

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 is equipped with a video RAM (not shown), and the display unit 741 is driven based on the image data input to the video RAM. The image signal processing unit 742 also has a function of performing format conversion, superimposition processing of menus and other OSD (On Screen Display) signals, etc. 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 CMOS (Complementary Metal Oxide Semiconductor) sensor.

The audio processing unit 750 is composed 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 the 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.

The sensor unit 760 is a group of sensors for detecting the state of the mobile 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 mobile information terminal 700, as well as the brightness of the surroundings, the proximity of surrounding objects, and the like. The mobile information terminal 700 may also be equipped with other sensors, such as an air pressure sensor.

The mobile information terminal 700 may be a mobile phone, a smartphone, a tablet terminal, or the like. 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 recording video, a portable game console, or other portable digital device.

The example configuration of the mobile information terminal 700 shown in FIG. 5A includes many components that are not essential to this embodiment, such as the sensor unit 760, but the effect of this embodiment is not diminished even if these components are not included in the configuration. In addition, components not shown, such as a digital broadcast receiving function and an electronic money payment function, may be added.

[Software configuration of mobile information terminal]
5B is a software configuration diagram of the portable information terminal 700 of this embodiment, and shows the software configuration in the ROM 703, the RAM 704, and the storage unit 710. In this embodiment, a basic operation program 7001 and other operation programs are stored in the ROM 703, and a linkage 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 linkage operation with a television receiver, and various information storage areas for storing various other information.

The basic operation program 7001 stored in the ROM 703 is expanded in the RAM 704, and the main control unit 701 executes the expanded basic operation program to constitute a basic operation execution unit 7101. The cooperative control program 7002 and HTML browser program 7003 stored in the storage unit 710 are expanded in the RAM 704, and the main control unit 701 executes each of the expanded operation programs to constitute a cooperative control execution unit 7102 and an HTML browser engine 7103. The RAM 704 also includes a temporary storage area for temporarily storing data created when each operation program is executed, as necessary.

In the following, for simplicity, the process in which the main control unit 701 loads the basic operation program 7001 stored in the ROM 703 into the RAM 704 and executes it to control each operation block will be described as the basic operation execution unit 7101 controlling each operation block. Similar descriptions will be used for the other operation programs.

The linkage control execution unit 7102 manages device authentication and connection, sending and receiving of various data, etc., when the mobile information terminal 700 performs linkage operation with the television receiver. The HTML browser engine 7103 is an HTML browser that executes applications created for the broadcasting and communication linkage system on the mobile information terminal 700.

The operating programs may be stored in the ROM 703 and/or the storage unit 710 beforehand at the time of product shipment. After product shipment, they may be acquired from other application servers 500 on the Internet 200 via the LAN communication unit 721 or the mobile telephone network communication unit 722. In addition, the operating programs stored in a memory card, optical disk, etc. may be acquired via the expansion interface unit 724, etc.

[Overview of Application Control Information (AIT)]
The application control information (AIT) of this embodiment is information intended to inform a television receiver or the like (in this embodiment, the broadcast receiving device 100) of the existence of an application (hereinafter, sometimes referred to as a broadcast linking application) that links to a broadcast service in the broadcast communication linking function supported by the broadcast receiving device 100, and to instruct its control. The broadcast linking application may be classified into (1) a broadcast managed application that operates only in a broadcast reception state based on a control signal such as start/end included in a broadcast signal, and is permitted to access broadcast resources based on the control signal, (2) a non-broadcast managed application that is not controlled by a broadcast signal for start/end, and is 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.

The AIT can be transmitted by broadcasting waves using a data carousel (DC) method or the like in which the AIT in section format or XML (extensible Markup Language) format is transmitted, or by distributing the 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.

Figure 6 is a data configuration diagram showing an example of the data configuration of the 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, application boundary and access authority settings 906, startup priority 907, cache information 908, and server access distribution parameters 909. In addition, other information may be included.

The application type 901 specifies the description method of the application. In this embodiment, the description method of the application is HTML. The application identifier 902 is identification information for identifying an application unit, which is composed of an organization identification for identifying a business operator and an application identification numbered for each business operator. Note that an application unit is a set of HTML documents and their reference resources, with the HTML document existing at the location specified by the application acquisition destination information 905 as the entry document. The application control code 903 specifies the operation control for the target application, and one of (1) automatic start, (2) operable, (3) terminated, and (4) prefetch is described. The application profile 904 is a value indicating the functions of the television receiver required by the application, and indicates a combination of optional functions of the television receiver. By referring to this value, the availability of the application is determined.

The application acquisition destination information 905 is information that specifies the acquisition destination of the application, and is location information for acquiring the HTML document that is first referenced when the application is started. Since it is assumed that the application will be transmitted by broadcast or placed on a server device on a communication network, the location information specified by the application acquisition destination information 905 is also specified to correspond to both broadcast acquisition and communication acquisition. The application boundary and access restriction setting 906 is information that indicates the operable range as a broadcast managed application as a set of one or more areas (URL: Uniform Resource Locator). In addition, access restrictions for each area are set on a functional basis. The application boundary and access restriction setting 906 specifies the range of document transition to prevent transition to an unexpected document due to a chain of document transitions from an entry document when the application is started, access to inappropriate broadcast resources, etc. In addition, it is possible to set access rights to specific broadcast resources on an area basis within the range of the document transition.

The start priority 907 specifies which of the two is to be started first when data broadcasting by a broadcasting service and a broadcast-managed application by an HTML document are present at the same time. It is possible to unconditionally specify data broadcasting as the highest priority on the PMT, to specify the start priority of a specific application type on the PMT, and to specify the start priority of the target application in the start priority 907. The cache information 908 is information used for cache control when holding application resources in preparation for reuse of the application. This information makes it possible to cache application resources that are assumed to be reused even after the application is terminated. The server access distribution parameter 909 is a parameter set for distributing access in order to reduce the load on a server where access is concentrated at the application acquisition destination, etc. The television receiver may operate to probabilistically delay the application of the application control code according to the setting of this parameter.

The operation of the broadcast receiving device 100 of this embodiment is described below.

[Application startup sequence]
First, a description will be given of a process for starting a broadcast-linked app based on an AIT transmitted by a broadcast wave 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 started 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 an application control code 903 and a start priority 907 in the AIT.

Figure 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. This figure shows a series of steps from when the broadcast receiving device 100 appropriately checks the PMT and AIT to when it launches a specific broadcast-linked app.

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

The service provider server 400, which has received the request to send the broadcast-linked app, 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 (S107). Note that a known method may be used for the authentication processing, and detailed explanations will be omitted. Next, the application engine 162 of the broadcast receiving device 100, based on the control of the application control unit 161, launches the specified broadcast-linked app received from the service provider server 400 via the LAN communication unit 121 (S108).

Figure 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 launched with priority. This figure shows a series of steps from when the broadcast receiving device 100 appropriately checks the PMT and AIT to when it launches a specific broadcast-linked app.

When the tuner/demodulator 131 of the broadcast receiving device 100 selects the channel desired by the user and acquires the TS, the main control unit 101 then acquires the PMT data sequence separated by the first separation unit 132 (S201) and checks the startup priority described in the PMT. When it is confirmed in the process of S201 that the startup priority of the data broadcast by the broadcast service is high (S202), the data broadcast reception processing unit 141 acquires the BML data sequence separated by the first separation unit 132 and plays the BML document (S203). If the BML document sets automatic startup of the data broadcast, and if the user uses an operation terminal (mobile information terminal 700, remote control, etc.) to request the startup of the data broadcast (S204), the data broadcast engine 142 executes the played BML document to generate data broadcast screen information and displays it on the video display unit 173 (S205).

After the processing of S205, or simultaneously with the processing of S205, the application control unit 161 acquires the AIT data string separated by the first separation unit 132 (S206), and checks the application profile 904 of the acquired AIT data string (S207). In the processing of S207, if it is confirmed that the broadcast linked app specified in the AIT can be executed, an entry button to the executable broadcast linked app is displayed on the data broadcast screen. The entry button may be always displayed, and the color scheme may be changed from an inactive color to an active color only when the broadcast linked app can be executed. The entry button may be switched between an inactive state and an active state by changing its shape.

When the user selects the entry button using the operation terminal (S208), the data broadcasting engine 142 ends the process of executing the BML document to generate data broadcasting screen information (S209). Next, 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 confirmed in S210, a request to send a broadcast-linked app is sent to a specified service provider server 400 via the LAN communication unit 121 (S211).

The service provider server 400, which has received the request to send the broadcast-linked app, 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 (S212). Next, the application engine 162 of the broadcast receiving device 100, based on the control of the application control unit 161, launches the specified broadcast-linked app distributed from the service provider server 400 and received via the LAN communication unit 121 (S213).

Figure 7C is an operational sequence diagram showing an example of the operational sequence of a broadcast-linked app when no priority startup is specified. This diagram shows a series of steps taken by the broadcast receiving device 100 to appropriately check the PMT and AIT and start a specific broadcast-linked app.

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. When 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). In the processing of S304, if the application control code 903 is "startable" rather than "automatic startup", the display of the broadcast program continues without starting either the data broadcast by the broadcast service or the broadcast linked app.

If the user uses the operation terminal to request the start of data broadcasting after the processing of S304 has been completed (S305), the BML data string is acquired, the BML document is played, and data broadcasting screen information is generated, as in the processing of S205 and subsequent steps in FIG. 7B (however, not shown). On the other hand, if the user uses the operation terminal to request the start of a broadcast-linked app launcher after the processing of S304 has been completed (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 apps on the video display unit 173 as a broadcast-linked app launcher (S309).

When the user uses the operation terminal to select a specific 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 confirmed in S311, a request to send the broadcast linked app is sent to the specific service provider server 400 via the LAN communication unit 121 (S312).

The service provider server 400, which has received the request to send the broadcast-linked app, 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 (S313). Next, the application engine 162 of the broadcast receiving device 100, based on the control of the application control unit 161, launches the specified broadcast-linked app distributed from the service provider server 400 and received via the LAN communication unit 121 (S314).

In the broadcast-linked app startup sequence described using Figures 7A to 7C, an example is described in which the AIT is acquired from broadcast waves, but the AIT file may be acquired from a specified server device specified by the information description of the PMT, etc. Also, the broadcast-linked app may be acquired from broadcast waves, 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 broadcast waves, 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).

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 the 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 the startup priority 907 of the AIT. In other words, regardless of the information on the PMT, the AIT may be checked periodically, and if a broadcast-linked app specified as "automatic startup" exists in the application control code 903 of the AIT, startup of the broadcast-linked app may be prioritized, and if a broadcast-linked app specified as "automatic startup" does not exist in the application control code 903 of the AIT, startup of the data broadcasting by the broadcasting service may be prioritized.

In addition, if there is no response from the service provider server 400 for a predetermined period of time or more 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 the video display unit 173. Alternatively, in this case, a message may be displayed inquiring the user about stopping execution of the broadcast-linked app.

It goes without saying that the start-up sequence of the broadcast-linked app is not limited to the three patterns mentioned above, and it may be started up using a different sequence.

[Operation sequence when mobile information terminals are linked]
In the broadcast receiving device 100 of this embodiment, it is assumed that the function of the broadcast communication cooperative service can be expanded by the cooperative operation between the broadcast receiving device 100 and the mobile information terminal 700. For example, by installing an application (cooperative control app) prepared by a television receiver manufacturer, it is possible to use the mobile information terminal 700 as a high-function remote control for the broadcast receiving device 100. In addition, it is possible to execute the broadcast cooperative app on the mobile information terminal 700 and 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 the function by the cooperative operation between the broadcast receiving device 100 and the mobile information terminal 700, it is preferable that the cooperative control app is running on the mobile information terminal 700, and the broadcast cooperative app running on the mobile information terminal 700 is controlled by the cooperative control app.

Figure 8A 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. This figure shows a series of steps (first time) in which the mobile information terminal 700 performs authentication processing with the broadcast receiving device 100 and cooperative operation becomes possible. Note that the cooperative control app is assumed to have been installed in advance in the storage unit 710 of the mobile information terminal 700 as a cooperative control program 7002.

When the user instructs the mobile information terminal 700 to start the cooperative control app (S401), the cooperative control execution unit 7102 of the mobile information terminal 700 searches for television receivers that can communicate (cooperative operation) on the network (S402) and displays the search results as a list of television receivers on the display unit 741. If a television receiver that can communicate cannot be found, the processing is terminated by displaying that fact. 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 (login name and password specified by the broadcast receiving device 100, etc.) on 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 it to the broadcast receiving device 100 (S404). The process of transmitting the authentication information to the broadcast receiving device 100 may be performed via the LAN communication unit 721 and the router device 210, or may be performed directly to the broadcast receiving device 100 via the NFC communication unit 723.

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 information of the mobile information terminal 700 is stored in the authentication information storage area 1012 and the mobile information terminal 700 is authenticated (S406). The mobile information terminal 700, which has been authenticated by the broadcast receiving device 100, displays the basic screen of the cooperation control application (e.g., a high-function 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. By the above processing, the broadcast receiving device 100 and the mobile information terminal 700 are in a state where they can cooperate with each other.

Figure 8B 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. This figure shows a series of steps (from the second time onwards) in which the mobile information terminal 700 performs authentication processing with the broadcast receiving device 100 and cooperative operation becomes possible.

When the user instructs the mobile information terminal 700 to start the linkage control app (S501), the linkage control execution unit 7102 of the mobile information terminal 700 searches for television receivers on the network that can communicate, and displays the search results as a list of television receivers on the display unit 741. If no television receivers that can communicate are found, a message to that effect is displayed and the process ends. If 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 been connected (linked operation), the linkage control execution unit 7102 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 (S503).

The terminal linkage 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 processing of S504 confirms that the received authentication information is correct, 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 linkage control app on the display unit 741 (S506). Through the above processing, the broadcast receiving device 100 and the mobile information terminal 700 are ready for linked operation.

Note that when launching a broadcast-linked app in the broadcast receiving device 100 following the processing of Figures 8A to 8B, the processing of Figures 7A to 7C can be performed after the processing of Figures 8A to 8B.

Figure 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. This figure shows a series of steps (from the second time onwards) in which the mobile information terminal 700 performs authentication processing with the broadcast receiving device 100 and cooperative operation becomes possible. However, this figure 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.

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

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 on the most frequently used information in the authentication information storage area 1012.

In addition, in the process of S606, if a mobile terminal device to which a request to start the linked control app 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 may be displayed inquiring the user about whether to stop execution of the broadcast linked app.

The main control unit 701 of the mobile information terminal 700 starts the collaborative control app (the collaborative control execution unit 7102) in response to the collaborative control app start request received via the LAN communication unit 721 (S607), and the collaborative control execution unit 7102 further 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).

The terminal linkage 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). Having been authenticated by the broadcast receiving device 100, the mobile information terminal 700 displays the basic screen of the linkage control app on the display unit 741 (S611). Through the above processing, the broadcast receiving device 100 and the mobile information terminal 700 are ready for linked operation.

If the broadcast-linked app is to be executed on both the broadcast receiving device 100 and the mobile information terminal 700 following the above-mentioned process, the process shown in FIG. 9 can be performed. FIG. 9 is an operational sequence diagram showing an example of a start-up sequence of the broadcast-linked app on the broadcast receiving device 100 and the mobile information terminal 700.

That is, after the processing of S601 to S611 in FIG. 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 confirmed in S612, a transmission request for the broadcast cooperation app (TV side) is sent to a specified service provider server 400 via the LAN communication unit 121 (S613).

The service provider server 400, which has received the transmission request for the broadcast-linked app (television side), 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 (television side) stored in the application memory area 4013 via the LAN communication unit 421 (S614). Based on the control of the application control unit 161, the application engine 162 of the broadcast receiving device 100 launches the specified broadcast-linked app (television side) distributed from the service provider server 400 and received via the LAN communication unit 121 (S615).

Next, the terminal cooperation control unit 191 of the broadcast receiving device 100 transmits to the mobile information terminal 700, information such as the URL information of the acquisition destination 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 (TV side) executed in S615 (S616). The cooperation control execution unit 7102 of the mobile information terminal 700 transmits a transmission request for the broadcast cooperation app (terminal side) to a specified service provider server 400 via the LAN communication unit 721 based on the URL information of the acquisition destination of the broadcast cooperation app (terminal side) received via the LAN communication unit 721 (S617).

The service provider server 400, which has received the request to send the broadcast-linked app (terminal side), performs authentication processing of the mobile information terminal 700 as necessary under the control of the application management/distribution execution unit 4103, and then distributes the specified broadcast-linked app (terminal side) stored in the application memory area 4013 via the LAN communication unit 421 (S618). The HTML browser engine 7103 of the mobile information terminal 700 launches the specified broadcast-linked app (terminal side) received from the service provider server 400 via the LAN communication unit 721 (S619).

Note that the AIT file can be acquired from a specified server device, and the broadcast-linked app can be acquired from broadcast waves rather than from a server device on the network, which are the same as the operation sequences of Figures 7A to 7C. Note that when acquiring the broadcast-linked app 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 Figure 9, the location information of the storage unit 110 of the broadcast receiving device 100 may be transmitted as URL information to be transmitted to the mobile information terminal 700. The broadcast receiving device 100 may acquire the broadcast linked app (television 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 acquire the broadcast linked app (terminal side) directly from the broadcast waves using a digital broadcast receiving function that the mobile information terminal 700 has.

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

[Mobile terminal linkage control app basic screen]
Fig. 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 is provided with a function as a high-function remote control compatible with the broadcast receiving device 100.

As shown in FIG. 10A, the basic screen 741a of the linked control app is composed of a power key 741a1, a network selection key (digital terrestrial, BS, CS) 741a2, number keys (1-12) 741a3, volume up/down key 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.

For ease of use, each of the operation keys may have the same key arrangement/operation as that of a dedicated remote control provided with the broadcast receiving device 100. In addition, the 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 explanations are omitted. The linked application key 741a9 is an operation key provided for the broadcast communication linkage function of this embodiment.

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 app can be selected by operating the cursor key 741ac and the decision key 741ad. Also, in the processing of S306 in FIG. 7C, it is assumed that a request to start the broadcast linked app launcher can be made by selecting the linked app key 741a9.

In this way, by providing the linked application key 741a9 or another operation key having a similar function on the 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. In addition, the linked application key 741a9 or another operation key having a similar function may be provided on a dedicated remote control attached to the broadcast receiving device 100.

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

The basic screen 741b of the collaborative control app is composed of a collaborative control message 741b1 and a collaborative control app operation screen 741b2. Other objects may also be displayed. The collaborative control message 741b1 is a message display for making the user aware that the mobile information terminal 700 is operating in collaboration with the broadcast receiving device 100. The collaborative control app operation screen 741b2 is an area in which any screen display is performed by the collaborative control app, and detailed explanation is omitted in this embodiment. For example, the configuration within the collaborative control app operation screen 741b2 may be the same as the basic screen 741a of the aforementioned collaborative control app. A sub-screen of a broadcast program displayed on the broadcast receiving device 100, etc. may also be displayed.

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

[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 process 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 by the broadcast receiving device 100 according to the description of 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.

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 linkage control app on the data broadcast screen 173a as shown in FIG. 11, the display of the data broadcast screen 173a is terminated and linkage app A, linkage app B, linkage app C, etc. are launched under the control of the application control unit 161 and the application engine 162.

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

In addition, the frame color, internal 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. The frame color, internal color, shape, font, size, blinking status, etc. of each entry button may be changed as appropriate depending on whether the broadcast linked app has been acquired from the network or not. For example, if the linked app A has already been acquired from the network (already cached in RAM 104 or storage 110), the frame color of entry button 173a2 is blue; if the linked app B is being acquired, the frame color of entry button 173a3 is yellow; if the linked app C has not been acquired, the frame color of entry button 173a4 is red, etc.

In this way, the user of the broadcast receiving device 100 can easily understand the types of broadcast-linked apps that can be executed on the broadcast receiving device 100, the security status, etc.

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

For example, in the operation sequence shown in FIG. 7C, after processing of S304, the broadcast program continues to be displayed without launching either the data broadcast by the broadcast service or the broadcast linked app. On the other hand, in this case, if icon 173b0 as shown in FIG. 12A is displayed to make the user aware 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 icon 173b0, it is possible to prevent the user from overlooking the existence of a broadcast linked app that can be launched.

The icon 173b0 may be displayed anywhere on the screen, but it is preferable that it be displayed in a location that does not interfere with viewing of a broadcast program. For example, the four corners of the screen. The icon 173b0 may be displayed as text as shown in FIG. 12A, or may be a symbol, figure, etc. The icon 173b0 may be displayed at all times, 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 the display of program information, channel number, etc.

Figure 12B is a screen display diagram showing an example of a broadcast linked app launcher displayed by the processing of S306 in Figure 7C. In this embodiment, it is assumed that three broadcast linked apps, linked app A, linked app B, and linked app C, are in a state that can be executed by the broadcast receiving device 100 due to the description in the AIT, etc. In this case, the broadcast linked app launcher 173b1 is displayed at an arbitrary position on the broadcast program screen 173b, and further, an entry button 173b2 for linked app A, an entry button 173b3 for linked app B, an entry button 173b4 for linked app C, and a back button 173b5 are displayed within the broadcast linked app launcher 173b1.

When the broadcast cooperative app launcher 173b1 as shown in FIG. 12B is displayed, if the entry button 173b2, entry button 173b3, entry button 173b4, etc. is selected using the cursor keys 741ac and the decision key 741ad on the basic screen 741a of the cooperative control app, cooperative app A, cooperative app B, cooperative app C, etc. are launched under the control of the application control unit 161 and the application engine 162. If the back button 173b5 is selected, the display of the broadcast cooperative app launcher 173b1 ends.

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 in the case of displaying the entry buttons of each broadcast linked app on the data broadcast screen 173a of Figure 11.

In addition, if there is no broadcast linked app that can be executed on the broadcast receiving device 100, the broadcast linked app launcher 173b1 may not be displayed. Alternatively, in this case, a message such as "There are no available applications" may be displayed inside the broadcast linked app launcher 173b1.

[Broadcast linkage app execution screen of broadcast receiving device]
FIG. 13A is a screen display diagram showing an example of a broadcast cooperative application 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 application of this embodiment has graphics performance and effect performance by HTML description, and is capable of overlay display with the broadcast program screen on the video display unit 173. For example, as shown in FIG. 13A, a broadcast cooperative application unit 173c1 that displays information such as a weather forecast and news is overlaid at an arbitrary position on the broadcast program screen 173c. The broadcast cooperative application unit 173c1 is composed of a first main object 173c2, a second main object 173c3, a third main object 173c4, and a background object 173c5, etc. Other objects may be further displayed.

When the broadcast linked app section 173c1 is overlaid on the broadcast program screen 173c, it is possible to terminate the execution of the broadcast linked app and move to the data broadcast screen by selecting the data key 741a8 on the basic screen 741a of the linked control app. Also, it is possible to terminate the execution of the broadcast linked app and return to the display of only the broadcast program screen 173c by selecting the linked app key 741a9 on the basic screen 741a of the linked control app. The above process may be realized by a different operation key.

In addition, when the broadcast linking app section 173c1 is overlaid on the broadcast program screen 173c, the transparency of the broadcast linking app section 173c1 can be changed by operating each operation key on the basic screen 741a of the linking control app. The transparency change process may be performed collectively on the entire broadcast linking app section 173c1, or may be performed individually on each of 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 (e.g., multiple objects existing on the same graphics layer).

When performing the above-mentioned process of changing the transparency, for example, the cursor key 741ac on the basic screen 741a of the cooperation control application is used to select an object, and the "blue" key of the color key 741ae is used to increase the transparency of the object, and the "yellow" key is used to decrease the transparency of the object. The above-mentioned process of changing the transparency may be performed using different operation keys. If the entire broadcast cooperation application section 173c1 is collectively set to a transparency of 100%, the broadcast cooperation application section 173c1 can be temporarily hidden. For example, when an emergency broadcast is distributed by airwaves, it is possible to set the entire broadcast cooperation application section to a transparency of 100% and display only the broadcast program screen of the emergency broadcast on the video display section 173. Alternatively, a CM detection section (not shown) may detect that the broadcast program has changed from the main video to the CM video, and control the entire broadcast cooperation application section 173c1 to a transparency of 100% (or a transparency at which the video of the broadcast program can be clearly confirmed) collectively.

By performing the above-mentioned 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 closing the broadcast linked app.

Figure 13B is a screen display diagram showing an example of the broadcast linked app execution screen displayed in the process of S108 in Figure 7A, the process of S213 in Figure 7B, the process of S314 in Figure 7C, the process of S615 in Figure 9, etc., different from the above. In the example shown in Figure 13B, a broadcast linked app section 173c6 that introduces recommended programs is overlaid at an arbitrary position on the broadcast program screen 173c. The broadcast linked app section 173c6 displays first recommended program information 173c7, second recommended program information 173c8, third recommended program information 173c9, etc. Even more recommended program information may be displayed by scrolling, page switching, etc.

The recommended program information may be information on a program recommended in relation to the broadcast program being displayed (broadcast program screen 173c), may be information on a program recommended based on the user's viewing history, or may be 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 the broadcast receiving device 100. The recommended program may also be a program transmitted by broadcast waves of a digital broadcasting service, or may be a VOD (Video On Demand) program distributed from each 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.

When the broadcast linking 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 linking control app, and the program videos recommended in the first recommended program information 173c7, the second recommended program information 173c8, the third recommended program information 173c9, etc. are displayed on the display section 173.

Figure 13C is a screen display diagram showing an example of a case where a program video recommended by the broadcast linkage application section 173c6 that introduces the recommended program is displayed. For example, when the first recommended program information 173c7 of the broadcast linkage application section 173c6 is selected using the cursor key 741ac and the decision key 741ad on the basic screen 741a of the linkage control application, the 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 time-specified jumped by the user's operation of the operation terminal. In addition, 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, it may be possible to change which of the program video 173ca of the recommended program and the original broadcast program screen 173c is to be the main screen by the user's operation of the operation terminal. The size of the window of the original broadcast program screen 173c may be adjusted by the user's operation on the operating terminal.

In addition, by displaying an icon display 173cb at any position on the screen indicating 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, user convenience 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.

Figure 13D is a screen display diagram showing an example of a broadcast linkage app execution screen that is different from the above, and is displayed in the process of S108 in Figure 7A, the process of S213 in Figure 7B, the process of S314 in Figure 7C, the process of S615 in Figure 9, etc. In the example shown in Figure 13D, a broadcast linkage app section 173cc, which serves as a portal for a SNS (Social Networking Service) service, is overlaid and displayed at an arbitrary position on the broadcast program screen 173c. The broadcast linkage 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.

With the broadcast cooperation application section 173cc overlaid on the broadcast program screen 173c, the cursor keys 741ac and the decision key 741ad on the basic screen 741a of the cooperation control application can be used to select the entry button 173cd for the first SNS service, the entry button 173ce for the second SNS service, the entry button 173cf for the third SNS service, etc., to activate the functions assigned to each entry button, such as a chat function, a bulletin board function, or an Internet telephone function. This makes it possible to enjoy the broadcast program being displayed (broadcast program screen 173c) while exchanging information with others. At the same time, the basic screen 741a of the cooperation control application 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.

In addition to the above-mentioned examples, the broadcast linking app that can be executed by the broadcast receiving device 100 of this embodiment may be one that uses a linking 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 linking 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 linking app is executed, it is possible to enjoy the effects described using Figures 13A and 13B, etc.

[Broadcast receiving device error display screen]
FIG. 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 FIG. 7A, the processing of S207 in FIG. 7B, the processing of S308 in FIG. 7C, the processing of S605 in FIG. 8C, etc., when there is an insufficient description of the AIT, or when acquisition of the AIT has failed.

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 the error message 173d1. For example, when the result of checking the application profile 904 indicates that a predetermined optional function is lacking on the television receiver side, the error message 173d1 indicates this. An error code and a guide (URL, etc.) to the television receiver manufacturer's homepage in which an explanation of the error code is described may 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, for example, if the broadcast linked app cannot be acquired due to a defective connection of the LAN cable, the error message 173d1 indicates this. In addition, the error message 173d1 may be displayed when the network connection is established but the broadcast linked app cannot be acquired correctly due to a poor error situation. The error message 173d1 may be displayed when the broadcast linked app is not yet in a state where it can be executed while the broadcast linked app is being acquired. Also, the error message 173d1 may be displayed when the broadcast wave reception is unstable and, although the AIT and other information was initially received, the AIT and other information can no longer be received midway through. 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 is restored.

In addition, if the result of checking the application profile 904 indicates that the television receiver is lacking a specific optional function, an error message 173d1 may be displayed recommending checking or updating the latest firmware for the television receiver. Alternatively, the broadcast receiving device 100 may automatically check or update the latest firmware. Alternatively, if the broadcast linking app can be made executable 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 instead of the broadcast receiving device 100.

[Broadcast linkage app execution screen on mobile information terminal]
Fig. 15 is a screen display diagram showing an example of a broadcast cooperative application (terminal side) execution screen displayed in the process of S619 in Fig. 9. The broadcast cooperative application 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, a commentary display section 741c6, and an end button 741c7. Other objects may be further added.

In this embodiment, the broadcast linkage app (terminal side) executed by the mobile information terminal 700 is an application for checking details of the 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 the position specified by the selection marker 741c3. The position of the selection marker 741c3 can be changed by selecting the cursor keys 741c4 and 741c5. The commentary display section 714c6 displays commentary subtitles about the broadcast program being displayed in the main window 741c1 and comments posted by other users about the broadcast program. The end button 741c7 is a button for ending the operation of the broadcast linkage app (terminal side).

By running the broadcast linkage app (terminal side) on the mobile information terminal 700, it becomes possible to expand the functionality of the broadcast communication linkage service through the linkage operation between the broadcast receiving device 100 and the mobile information terminal 700.

[EPG screen of broadcast receiving device]
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. The EPG display screen 173e is displayed on the video display unit 173 by selecting the program guide key 741a7 on the basic screen 741a of the linkage control application.

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

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 mark for "New" meaning that it is a new program, or a symbolized mark for "Replay" meaning that it is a rebroadcast program. Alternatively, it may be a symbolized mark for "data" meaning that it is compatible with data broadcasting by a broadcast service. In addition, if the broadcast program is prepared for a broadcast linkage app that can be executed by the broadcast receiving device 100 of this embodiment, it may be a symbolized mark for "Linkage" indicating this fact. The detailed explanation area 173e3 displays related information such as the program content and performers of each broadcast program, and the URL of a homepage introducing each broadcast program.

The symbolized mark of "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 a broadcast-linked app is prepared for the broadcast program. The symbolized mark of "Linkage" displayed in the title area 173e2, which indicates that the broadcast program has an executable broadcast-linked app, may further have its color, shape, font, etc. changed depending on whether or not the program can be linked with a mobile terminal device. If the program can be linked with a mobile terminal device, a symbolized mark of "Mobile" may be displayed together with the symbolized mark of "Linkage".

The presence or absence of the symbolized mark for "Linkage" or the symbolized mark for "Mobile" may be controlled by acquiring information, which is previously recorded in the 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 on 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 the program distribution information of a digital broadcast program prepared on a specific server device on the Internet 200 may be added to an electronic program guide created based on a program information data string acquired from the broadcast waves of a digital broadcast service.

As described above, by displaying on the EPG display screen 173e a symbolized mark of "Linkage" indicating that the broadcast program has an executable broadcast linkage app available, or a symbolized mark of "Mobile" indicating that the broadcast program can be linked with a mobile terminal device, the user can easily understand the compatibility of each broadcast program with the broadcast communication linkage service in the broadcast receiving device 100. Needless to say, the symbolized mark of a specific character representing the attribute of each broadcast program may be replaced with the character itself or a sentence. The compatibility of each broadcast program with the broadcast communication linkage service may be indicated by changing the background color of the detailed information 173e1 of each broadcast program. In addition, the symbolized mark of "Linkage" or the symbolized mark of "Mobile" may not be displayed in the title area 173e2 normally, but may be displayed in a pop-up only when each broadcast program is selected by the program selection cursor 173e4.

The broadcast receiving device 100 of this embodiment has a function for making a reservation for viewing and/or recording of each broadcast program from the EPG display screen 173e. For example, when the EPG display screen 173e is displayed, the program selection cursor 173e4 on the EPG display screen 173e is moved using the cursor keys 741ac on the basic screen 741a of the linkage control application, and an arbitrary broadcast program is selected using the decision key 741ad, thereby making a reservation for viewing and/or recording of the selected broadcast program.

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 cooperation service, the viewing reservation and/or recording reservation may be used as a trigger to start acquiring a broadcast cooperation app prepared for the broadcast program without waiting for the broadcast start time of the broadcast program. That is, information specifying the acquisition destination of the broadcast cooperation app (location information such as a URL) is written in EIT information including detailed information of each broadcast program. In this way, the broadcast receiving device 100 can grasp the information on the acquisition destination of the broadcast cooperation app prepared for each broadcast program at the time the broadcast program is selected with the program selection cursor 173e4. Therefore, the broadcast receiving device 100 can start acquiring the broadcast cooperation app before the broadcast start time of the broadcast program.

If the broadcast program for which the viewing reservation and/or recording reservation has been made is compatible with a broadcast communication cooperation service and is capable of cooperation with a mobile terminal device, the broadcast cooperation app (terminal side) prepared for the mobile terminal device may also start acquiring the broadcast 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 on the acquisition destination (location information such as a URL) of the broadcast cooperation 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 cooperation app (terminal side) prepared for the mobile terminal device.

In this way, if the broadcast receiving device 100 refers to the acquisition destination information for 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.

Figure 17 is an operational sequence diagram showing an example of a broadcast linkage app acquisition sequence when a broadcast program viewing and/or recording reservation is made from the EPG display screen 173e.

While viewing a digital broadcast service, the main control unit 101 of the broadcast receiving device 100 acquires the program information data sequence output from the first separation unit 132 (S701). When the user uses the operation terminal to request the launch of an EPG screen (S702), the EPG display screen 173e is displayed on the video display unit 173 (S703). When the user uses the operation terminal to select an arbitrary broadcast program on the EPG display screen 173e 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 destination of the broadcast linkage app linked to the broadcast program that has been scheduled for viewing and/or recording (S706).

After the processing of S706, the application control unit 161 transmits a request to transmit the broadcast-linked app to the specified service provider server 400 via the LAN communication unit 121 based on the confirmed URL (S707). The service provider server 400 that receives the request to transmit the broadcast-linked app 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 (S708). Next, the application control unit 161 caches the specified broadcast-linked app received from the service provider server 400 via the LAN communication unit 121 in the RAM 104 or the storage 110 (S709).

The transceiver device 100 of this embodiment described above can perform functions with higher added value.

The following describes Example 2 of the present invention. Note that the configuration and effects of this example are the same as those of Example 1 unless otherwise specified. For this reason, the following mainly describes the differences between this example and Example 1, and explanations of common points are omitted as much as possible to avoid duplication.

In Example 1, we also described an implementation example in which mobile information terminal linkage processing (hereinafter referred to as terminal linkage) is performed, but we will now explain a more detailed implementation example.

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

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 the same-house restriction, this determination is not necessary, but if there are cases where there are no restrictions, the broadcast receiving device 100 must obtain 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 obtained from the broadcast signal (for example, described as an item in the AIT) or may be obtained from a server designated by the broadcast station.

In this embodiment, including the above steps, we will explain the steps to ensure that the mobile information terminal 700 is present in the same home as the broadcast receiving device 100.

Normally, 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 a known method can be used to determine whether the target device is connected to a local network, and so a description of this will be omitted.

In addition, 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-linked app, etc., may be the above-mentioned direct communication or may be via mobile telephone communication.

As mentioned above, there are multiple ways to confirm that devices are in the same house, but the method to be used is described, for example, in the AIT and read by the broadcast receiving device 100.

Furthermore, once it has been 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 (e.g., 10 minutes) may be set, during which it is considered to be in the same home, but once the valid time has elapsed, it will not be considered to be in the same home unless a new confirmation is made. This valid time may be written, for example, in the AIT and read by the broadcast receiving device 100.

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

It is also possible to combine the first two methods.

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

In this embodiment, a case where the mobile information terminal 700 acquires broadcast linkage information from the broadcast receiving device 100 is described, and the case where the information is acquired from a server is described in the next embodiment.

Figure 18A shows the procedure for this example.

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

If it is assumed that all broadcast-linked apps have the same-house restriction, the determination in S10006 is skipped. If there are both apps with and without the same-house restriction, the determination in S10006 is performed.

If it is determined that the mobile information terminal 700 is in 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. In this service (S10012), a broadcast-linked information distribution request (S10013) from the mobile information terminal 700 is processed, and broadcast-linked information is distributed to the mobile information terminal 700 (S10018). This broadcast-linked information includes information distributed by the broadcast receiving device 100 from the distribution server that is the operator server 300 (S10014, S10015, S10016), information obtained from a broadcast signal (S10017), information stored in the broadcast receiving device 100, and the like. The broadcast receiving device 100 may receive the broadcast linkage information (S10016, S10017) not only in response to a broadcast linkage information distribution request (S10013) from the mobile information terminal 700, but may also autonomously acquire the information or may acquire the information based on the occurrence of an event from a broadcast signal. Furthermore, the broadcast receiving device 100 may also distribute the broadcast linkage information to the mobile information terminal 700 (S10018) on its own initiative.

After the series of broadcast linkage information reception (acquisition) and distribution processes are 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 side that linkage is not permitted, and the process ends (S10020).

If viewing continues, the procedure returns to S10005, and if there is a home restriction, it is confirmed whether the mobile information terminal 700 is within the same home (S10009), but it is determined whether a preset valid time has elapsed since the last check, or whether a confirmation request (S10007) has occurred from the broadcast signal or distribution server since the last check (S10008). If neither condition is met, it does not check whether it is within the same home (S10009), and goes through S10010 to execute the next broadcast linked app related service (S10012). Here, the confirmation request from the broadcast signal (S10007) is described as being obtained from the broadcast linked information, but here the event message is also described as being included in the broadcast linked information. Furthermore, this confirmation request may be described in the AIT.

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 in S10022. The confirmation request in S10007 may be made at any time within the loop.

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. Furthermore, by changing the authentication information described in the AIT as the program progresses and not performing authentication unless the authentication key in the distribution server incorporates information synchronized with the program's 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 in the broadcast signal may be incorporated as broadcast linkage 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.

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 every preset valid time or every time there is a confirmation request from a broadcast signal or distribution server, thereby making it possible to appropriately execute broadcast-related apps that have same-home restrictions. Furthermore, by using the authentication information embedded in the broadcast signal for authentication at the distribution server, the legitimacy of the distribution request can be ensured, and by appropriately changing the authentication information of the broadcast signal, it is also possible to confirm that the same program is being continuously viewed.

The mobile information terminal linking technology according to the present embodiment described above makes it possible to realize the same-house restriction for mobile information terminals that link with a broadcast receiving device.

In this embodiment, we will explain the case where the mobile information terminal 700 obtains broadcast linkage information from a distribution server.

Figure 18B shows the procedure for this example.

First, before performing terminal linkage, a linkage control app, which is an application that controls terminal linkage, is started in each of the mobile information terminal 700 and the broadcast receiving device 100 (S10101, S10102). In this state, the mobile information terminal 700 requests terminal linkage to the broadcast receiving device 100 (S10103). Next, the 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 the information is transmitted to the mobile information terminal 700 (S10105). Next, the broadcast receiving device 100 issues a time confirmation request 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 performed in accordance with the time of the distribution server, but if the time difference is not a problem, this may be omitted.

From this point on, the loop control indicated by the arrow at S10127 will begin.

First, the mobile information terminal 700 issues a request for issuing an authentication key or a request for broadcast linked information distribution to the broadcast receiving device 100 (S10109). The authentication key is used in a broadcast linked information distribution request to the distribution server in the following step (S10125). The broadcast linked distribution request in S10109 is a distribution request for information obtained from a broadcast signal, and corresponds to the procedure in S10126 in the following step.

In any case, when the request of S10109 is issued from the mobile information terminal, it is determined whether the broadcast linked app has a same-house restriction (S10111), and if there is a restriction, proceed to the next step S10112, and if not, skip step S10112 and proceed to S10114. If all broadcast linked apps have same-house restrictions, the determination of S10111 is not made and proceed to S10112. In S10112, it is determined whether the mobile information terminal that issued the request is in the same house, and if not, the terminal linkage is terminated (S10113). If it is in the same house, the requested procedure is performed, which is to obtain broadcast linked information from the distribution server (S10125) or to obtain broadcast linked information from the broadcast signal (S10126). In addition to obtaining information from the distribution server, obtaining information from the broadcast signal may also be acceptable, so the procedure of S10126 is also described.

First, we will explain the procedure for acquiring broadcast linkage information from the distribution server (S10125).

First, the broadcast receiver 100 issues the authentication key requested by the information linkage terminal 700. At this time, the authentication key includes the 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 allows the distribution of broadcast linkage information if the authentication is OK. Thereafter, information distribution is allowed within the valid period, but distribution is stopped when the valid period has elapsed. For example, streaming video will no longer be viewable once the valid period has elapsed.

The preset validity time may be stored in the distribution server, or the broadcast receiving device 100 may obtain it from a broadcast signal (e.g., AIT) and incorporate the validity time information into the authentication key. The portable information terminal 700 is notified of the validity time information in advance, and issuance of an authentication key is requested before the validity time expires. Alternatively, the validity time may be managed by the broadcast receiving device 100, and an authentication key may be automatically issued to the portable information terminal 700 from the broadcast receiving device 100 before the validity time expires after confirming that the portable information terminal 700 is in the same home.

The validity period may be the same throughout a single program, or may change as the program progresses. Also, if no validity period is set, authentication may be performed once and remain valid for the duration of the program.

Furthermore, the authentication information described in the AIT may be incorporated into the authentication key used for authentication in the distribution server (S10117). This allows confirmation that the authentication request is legitimate. Furthermore, if the authentication information described in the AIT is changed as the program progresses and the distribution server does not perform authentication unless the authentication key is one in which information synchronized with the program progress is incorporated, it is possible to confirm that the same program is being watched continuously. In this case, the information in the AIT is read and updated as appropriate (S10124). Note that the authentication information to be incorporated in the broadcast signal may be incorporated as broadcast linkage information in addition to being described in the AIT. Furthermore, as a method of practically changing the authentication information, a method of changing the URL of the distribution server itself as the program progresses can also be used. Note that the URL change in this case is when the distribution server is the same but the entrance is different, but it may also be changed to a new distribution server due to a change in the broadcast linkage app, etc. In this case, each time a change is made, the following steps are performed: sending distribution server information (S10105), requesting time confirmation (S10106), and sending time information (S10107).

Next, we will explain the procedure for acquiring broadcast linkage information from a broadcast signal (S10126).

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).

In addition, when the broadcast linkage information is changed as the program progresses, a notification of the change may be issued from the broadcast signal (S10110), and the notification may trigger the acquisition of the broadcast linkage information. In that case, if the 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 that a change notification has been received. If the information is acquired within the valid time, the issuance of the authentication key may be omitted, and only the notification of 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 confirmed that the mobile information terminal 700 is in the same house for each change notification, and as in the second embodiment, if the information is acquired within the valid time, the confirmation may be omitted. Here, the change notification from the broadcast signal (S10110) is described as being acquired from the broadcast linkage information, but here, the event message is also described as being included in the broadcast linkage information. Furthermore, this change notification may be described in the AIT.

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

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 at the distribution server, the legitimacy of the distribution request can be ensured, and by appropriately changing the authentication information of the broadcast signal, it is also possible to confirm that the same program is being continuously viewed.

The mobile information terminal linkage technology according to the present embodiment described above makes it possible to realize the same-home restriction even when a mobile information terminal linked to a broadcast receiving device acquires broadcast linkage information from a distribution server.

In the second and third embodiments, the procedure for realizing the same-house restriction in terminal linkage has been described, but depending on the broadcast linkage app, use from outside the home may also be permitted. In this embodiment, such a case will be described. For example, when a program such as a TV shopping program itself is used for public relations and advertising, it is desirable for the broadcaster to be able to use the broadcast linkage app regardless of whether the program is in the home or outside the home. In the case of such a program, once it is registered in the broadcast receiving device 100, the broadcast linkage app may be permitted to be used regardless of whether the mobile information terminal 700 is in the home. In this case, convenience is further improved if there is a broadcast linkage 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 linkage app permits use from outside the home, including distribution of the broadcast video to outside the home, is described in the data (e.g., AIT) in the broadcast signal.

Specific steps are shown in FIG. 18C. Some of the steps are common to Examples 2 and 3, so the explanation 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 checks whether the request source is a registered mobile information terminal (S10205) and then permits the link. Here, if necessary, authentication may be performed between the mobile information terminal 700 and the broadcast receiving device 100 for copyright protection of the broadcast video and broadcast link information (S10207). At that time, the authentication may be authentication in the distribution server (S10207). Information on whether copyright protection is necessary and information on the authentication method for copyright protection are obtained from the broadcast signal (for example, 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 this information is not stored in the broadcast signal, it may be predetermined that the broadcast receiving device 100 will not perform copyright protection processing.

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. Also, the authentications exemplified below may be performed in combination with other authentication processes not exemplified below.

[ID and password authentication]
When the portable information terminal 700 is registered in 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.

[Encryption key usage]
In addition to the authentication using the ID and password described above, 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 a broadcast signal (for example, written in the AIT).

[Use of distribution server]
A method in which an encryption key for decrypting encrypted video data, etc. is issued from a distribution server. The mobile information terminal 700 transmits an ID and a password to the distribution server and obtains the encryption key. In this case, the location information (specifically, URL) of the distribution server is obtained from a broadcast signal (e.g., written in the AIT), and this location information is transmitted from the broadcast receiving device 100 to the mobile information terminal 700, thereby improving security. If the mobile information terminal 700 cannot obtain the encryption key, it cannot decrypt the video data, etc., so the broadcast receiving device 100 may request authentication from the distribution server to authenticate copyright protection, or the mobile information terminal 700 may notify the broadcast receiving device 100 that the encryption key has been obtained, thereby completing the authentication. The distribution server may charge a fee.

[Mutual authentication of encryption keys]
The encryption keys held by the broadcast receiving device 100 and the portable information terminal 700 are mutually authenticated and confirmed to authenticate copyright protection.

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

If terminal linkage is permitted, thereafter, there is no confirmation as to whether the mobile information terminal 700 is present in the same house, and broadcast linkage information is distributed 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 with a set valid time does not have to be performed. The mobile information terminal 700 outside the house acquires broadcast linkage information from the broadcast receiving device 100 or the distribution server using the issued authentication key (S10215). In addition, the broadcast receiving device 100 may incorporate authentication information acquired from the broadcast signal (for example, as described in the AIT) into the authentication key issued, and the distribution server may permit access if the authentication key incorporates authentication information acquired from the broadcast signal, thereby making it possible to more appropriately use outside the house.

Furthermore, in some cases, such as when offering a discount as a premium for viewing a program, it may be better not to allow 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.

Specific procedures in this case are shown in FIG. 18D. Some of the procedures are common to those in FIG. 18C, so the explanation of the overlapping parts will be omitted. First, when the portable information terminal 700 is in the same house as the broadcast receiving device 100, the portable information terminal 700 makes a terminal link request to the broadcast receiving device 100, and the broadcast receiving device 100 confirms that the portable information terminal 700 is in the same house (S10305) and then permits the link. Here, if necessary, authentication may be performed between the portable information terminal 700 and the broadcast receiving device 100 for copyright protection of the broadcast video and broadcast link information (S10307). At that time, the authentication may be authentication in an external distribution server. Information on whether copyright protection is necessary and information on the authentication method for copyright protection are obtained from the broadcast signal (for example, as 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 this information is not stored in the broadcast signal, it may be predetermined that the broadcast receiving device 100 will not perform copyright protection processing.

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. Also, the authentications exemplified below may be performed in combination with other authentication processes not exemplified below.

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

[Use of distribution server]
A method in which an encryption key for decrypting encrypted video data, etc. is issued from a distribution server. The mobile information terminal 700 transmits an ID and a password to the distribution server to obtain the encryption key. In this case, the location information (specifically, URL) of the distribution server is obtained from a broadcast signal (e.g., written in the AIT), and this location information is transmitted from the broadcast receiving device 100 to the mobile information terminal 700, thereby improving security. If the mobile information terminal 700 cannot obtain the encryption key, the video data, etc. cannot be decrypted. Therefore, the broadcast receiving device 100 may request authentication from the distribution server to be used as authentication for copyright protection, or the mobile information terminal 700 may notify the broadcast receiving device 100 that the encryption key has been obtained, thereby completing the authentication. The distribution server may be accessed either inside or outside the home, but if the location information of the distribution server cannot be obtained from the broadcast signal unless a certain point in time is reached in the program, and the handover of the location information to the mobile information terminal 700 is limited to within the same home, a restriction that the user must be within the same home at that time can be imposed, and this can also be used to provide a premium for viewing. It is acceptable for the distribution server to charge a fee.

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

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

The mobile information terminal linking technology according to the present embodiment described above makes it possible to use a mobile information terminal linked to a broadcast receiving device from outside the home while respecting copyright protection.

In actual usage, it is more desirable to easily know whether a program has a terminal link app and which terminal link apps are available. In this embodiment, a method for displaying the availability status of terminal link apps is described. A terminal link app refers to a broadcast link app used in device linkage.

Figure 19A is an example of a launcher screen (173b11) for a broadcast linked app when there is a terminal linked app. The broadcast linked app is displayed as an icon with framed text. Broadcast linked apps (173b12-173b14) for the broadcast receiving device 100 linked to the program being viewed 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 frame indicate the app status. Main app A, B (173b12, 173b13) and terminal app A, B (173b15, 173b16) are available, and main app C (173b14) and terminal app C (173b17) are unavailable. A terminal app unavailable state means that none of the mobile information terminals 700 that are in a state capable of communicating with the broadcast receiving device 100 have the function to execute the app.

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

Mobile terminal 1 (173b22) and mobile terminal 2 (173b23) whose icons have solid borders are in a state where they can communicate with the 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 the broadcast receiving device 100. Additionally, 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.

Also, icons are easier to understand visually if you use pictures, as shown in the following example.

Figure 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 a broadcast receiving device 100, icons 173b34 and 173b35 are icons indicating a smartphone-type mobile information terminal 700, and 173b36 is an icon indicating a head-mounted display-type mobile information terminal 700. Each app is for the device indicated by the icon.

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. Also, 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 makes it possible to prevent unnecessary operation of proceeding with the launcher procedure even though the app is already running. In the case of the mobile information terminal 700, it is also possible to display a mark indicating that the app is running when the app is running on all devices that are capable of communicating with the broadcast receiving device and can run the app.

Figure 19D shows the screen (173b41) after selecting app C (173b34) in Figure 19C. The state of the mobile information terminal 700 of a type corresponding to app C is shown. In this screen, if the mobile information terminal 700 does not have the function to execute a broadcast-linked app, if it is not in a state where it can communicate with the broadcast receiving device 100, or if the broadcast-linked app is already running, a mark representing that is displayed superimposed on the icon. In this example, if it does not have the execution function, a circle with a line (173b44, 173b46) is displayed, if it is not in a state where it can communicate, an exclamation point in a triangle (173b45, 173b46) is displayed, and if the app is already running, a circle with a dot (173b43) is displayed.

Furthermore, it would be desirable to have a display method that would let users know that a broadcast-linked app exists when the situation changes, without the need 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 even during a program, when there is a change in the broadcast-linked app, when there is a change in the communication state between the broadcast receiving device 100 and the mobile information terminal 700, or when the execution status of the app changes, an icon would be displayed for a predetermined period of time to show the status at that time.

Figure 19E shows an example of this case. When an icon showing 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.

Figure 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 which broadcast linkage app can be used with which broadcast receiving device 100 in a list. An example of the list is shown in Figure 19F (10402). This table shows which broadcast receiving devices 100 in the home can use the broadcast linkage app corresponding to the program to be searched. In addition, if the status of each broadcast receiving device 100 is also displayed, it is more convenient, especially when using it from outside the home. In this example, display examples such as receiving the program, receiving another program, free, and other program reservation (when recording of another program is reserved from the middle of the program) are shown. Note that here, if there are multiple tuners in the broadcast receiving device 100, it is more convenient to display the status for each of the multiple tuners. In table 10202, the sub-numbers indicate the distinction between tuners in the same device. For example, receiving device B-1 and receiving device B-2 are tuners in 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 broadcasts can be used if the tuner in broadcast receiving device 100 can be used, so it is convenient to know the usage status of each tuner.

In order to perform the display described in this embodiment, information must be available 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 the broadcast receiving device 100 and the mobile information terminal 700 to execute the compatible app. This information can be obtained by the broadcast receiving device 100 by recording it in the AIT, for example.

According to the mobile information terminal linkage technology of the present embodiment described above, by displaying information related to the broadcast linkage app, the broadcast receiving device 100, and the mobile information terminal 700, it becomes possible to use a more convenient broadcast linkage service.

The following describes Example 6 of the present invention. Note that the configuration and effects of this example are the same as those of Example 1 unless otherwise specified. For this reason, the following mainly describes the differences between this example and Example 1, and explanations of common points are omitted as much as possible to avoid duplication.

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 case. This case refers to a case where the broadcast linked app is a broadcast managed application, and the information on the PMT and information such as the application control code 903 and launch priority 907 of the AIT (Figure 6) specify and instruct that the broadcast managed application, which is the broadcast linked app, should be automatically launched with priority. Note that hereinafter, the broadcast managed application may be referred to as the "broadcast managed application."

The broadcast receiving device 100 of Example 6 has a function of controlling the startup process of a broadcast linked app for which the automatic startup is specified in a digital broadcasting service in accordance with a user selection. When there is a provision or instruction for the automatic startup, the broadcast receiving device 100 of Example 6 controls the broadcast linked app to automatically start only when the following conditions (1) to (3) are met, rather than automatically starting the broadcast linked app unconditionally. (1) When automatic startup is set to allow in the user settings of the broadcast receiving device. (2) When a user who owns a specific terminal linked to the broadcast receiving device is watching, in other words, when automatic startup is set to allow in the user settings of the linked terminal. (3) When a confirmation of startup is performed with the user each time, and the confirmation is positive.

Figure 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 the 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.

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. This is not limited to the above, and one user may use multiple mobile information terminals 700.

The broadcast receiving device 100 of Example 6 has an app launch control means 2000 including a user selection means 2001. The user selection means 2001 is a means for selecting whether or not to permit launch and execution of a broadcast linked app based on the operation of the user of the broadcast receiving device 100 and the mobile information terminal 700. The user selection means 2001 is composed of, 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 the broadcast linked app is instructed by the AIT, the app launch control means 2000 controls the launch of the broadcast linked app in accordance with the selection by the user and the user selection means 2001 of whether or not to permit launch and execution of the broadcast linked app.

[For automatic launch of broadcast managed apps]
In the sixth embodiment, when it is specified that the broadcast managed application is to be automatically started first with priority, the operation sequence in which the broadcast receiving device 100 appropriately checks information such as the PMT and the 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 of the AIT is checked to confirm whether the target broadcast managed application can be executed in the broadcast receiving device 100 (S105). If the execution is confirmed, the broadcast managed application is always automatically started regardless of the selection of the user of the broadcast receiving device 100.

However, it should also be considered that the user of the broadcast receiving device 100 may not want the broadcast managed app to be automatically started, for example, because they want to concentrate on watching a broadcast program. The broadcast receiving device 100 of Example 6 has an app start control means 2000 as a control function that takes this possibility into account. That is, even when there is an instruction to automatically start the broadcast managed app with priority based on information such as the PMT and AIT, and when it is confirmed that the broadcast managed app can be executed based on information such as the AIT, the broadcast receiving device 100 of Example 6 controls the start of the app depending on whether or not the user selects whether or not to start the app. Below, an example of controlling whether or not to automatically start a broadcast managed app will be described.

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

In Fig. 21, the broadcast receiving device 100 acquires a TS by selecting a channel desired by the user using the tuner/demodulator unit 131 in Fig. 2A. Next, the broadcast receiving device 100 acquires the PMT data string separated by the first separation unit 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.

After confirming the above, the broadcast receiving device 100 acquires the AIT data string separated by the first separation unit 132 by 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 processing of S1103 and S1104, that is, if automatic start of the broadcast linked app is specified, the broadcast receiving device 100 further checks the application profile 904 of the acquired AIT data string (S1105).

In S1105, the broadcast receiving device 100 checks the information in the application profile 904 to confirm that the broadcast linked app specified in the AIT can be executed on the broadcast receiving device 100. If the execution is confirmed to be possible, 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 checks whether the automatic startup of the broadcast linked app is permitted in the user settings of the broadcast receiving device 100 (S1106).

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 of the broadcast receiving device 100 or the like. The broadcast receiving device 100 provides the user with a function setting menu on a screen or the like as a 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 as an operation setting value in the memory within the broadcast receiving device 100.

If the broadcast receiving device 100 confirms in the processing of S1106 that automatic startup of the broadcast linked app is not permitted ("No"), i.e., that the user does not want the broadcast linked app to be automatically started (S1107-No), it ends this processing of FIG. 21. In other words, the application control unit 161 does not acquire or start the broadcast linked app specified in the AIT.

On the other hand, if the broadcast receiving device 100 confirms in the processing of S1106 that automatic startup of the broadcast linked app is permitted ("Yes"), i.e., that the user wishes for automatic startup of the broadcast linked 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 sends a distribution request for the broadcast linked app to a specified 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.

The service provider server 400, which has received the broadcast-linked app distribution request of S1108, performs authentication processing of the broadcast receiving device 100 as necessary based on the control of the application management/distribution execution unit 4103 in FIG. 4, and then distributes the specified broadcast-linked app stored in the application memory area 4013 via the LAN communication unit 421 (S1109). Note that a publicly known method may be used for this authentication processing, and detailed explanation will be omitted.

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 based on the control of the application control unit 161 and distributed from the service provider server 400 (S1110). This causes the broadcast-linked app to be executed and the execution screen of the app to be displayed.

As a modified example, the processes of S1106 to S1107 may be performed after acquiring the broadcast-linked app in the processes of S1108 to S1109.

As in the first configuration example of FIG. 21 described above, in Example 6, the broadcast linked app can be launched if it is confirmed in the user settings of the broadcast receiving device 100 that automatic launch is permitted.

[Operation sequence when broadcast managed application is launched (2)]
Fig. 22 shows 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 preferentially as a second configuration example and processing example of the broadcast receiving device 100 of Example 6. Fig. 22 shows an example of checking whether or not the broadcast-linked app can be automatically started by referring to the operation setting value, i.e., the user setting information, stored in the mobile information terminal 700 that performs the linked operation with the broadcast receiving device 100, i.e., the above-mentioned terminal linkage. In the second configuration example, the user setting in the mobile information terminal 700 is used as the user selection means 2000. The user selects and sets whether or not to allow the automatic start of the broadcast-linked app for the mobile information terminal 700.

In FIG. 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 linked app specified in the AIT is executable by checking the application profile 904, then it performs the process of S1206. In S1206, the broadcast receiving device 100 transmits a user setting confirmation request to the mobile information terminal 700 with which it is operating in a linked manner via the application control unit 161. Here, it is assumed that the mobile information terminal 700 which is operating in a linked manner or capable of terminal linkage is, for example, terminal A in FIG. 20.

In response to the user setting confirmation request received by the cooperative control execution unit 7102 in 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 in 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 can be started by the cooperative control execution unit 7102 to the broadcast receiving device 100 via the LAN communication unit 721 as a user setting confirmation result (S1208).

The operation setting value of 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, in a state in which the broadcast receiving device 100 and the mobile information terminal 700 are in a linked operation state, the user can select and set according to his/her 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 or the like. 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 as an operation setting value in the memory of the mobile information terminal 700.

If the broadcast receiving device 100 confirms through the above processing of S1206 to S1208 that automatic startup of the broadcast linked app is not permitted, i.e., that the user who owns the mobile information terminal 700 does not want the broadcast linked app to be automatically started on the broadcast receiving device 100 (S1209-No), it terminates this processing of FIG. 22. In other words, the application control unit 161 does not acquire or start the broadcast linked app specified in the AIT.

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

At S1210, the broadcast receiving device 100 transmits a broadcast linked app distribution request to a specific 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.

The service provider server 400, which has received the broadcast-linked app distribution request of S1210 above, 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).

Next, the broadcast receiving device 100 launches a specific broadcast-linked app 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).

As in the second configuration example of FIG. 22 described above, in Example 6, when a mobile information terminal 700 linked to the broadcast receiving device 100 exists and automatic start-up is permitted in the user settings of the mobile information terminal 700, the broadcast linked app can be started.

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.

As a modified example, an embodiment in which control is performed to select the Yes side in S1209 or an embodiment in which control is performed to select the No side in S1209 is possible in the following cases. In this case, there is no mobile information terminal 700 to which the user setting confirmation request is sent in S1206, there is no response to the request, the user setting confirmation result cannot be correctly acquired in S1208, etc. In this case, there is a situation in which there is no mobile information terminal 700 that can be terminal-linked at that time, or a situation in which communication is temporarily not possible between the broadcast receiving device 100 and the mobile information terminal 700, etc. In the former embodiment, the broadcast linking app is started even though permission for start-up by the user setting could not be confirmed. In the latter embodiment, the broadcast linking app is not started because permission for start-up by the user setting could not be confirmed. In the above modified example, which control operation is adopted is specified in the specifications of the broadcast receiving device 100, or the user can select and set it.

As a variant, the processes of S1206 to S1209 may be performed after acquiring the broadcast-linked app in the processes of S1210 to S1211.

[Operation sequence when broadcast managed application is launched (3)]
Fig. 23 shows an example of an operation sequence when a broadcast-managed application, which is a broadcast-managed application, is started up as a third configuration example and processing example of the broadcast receiving device 100 of Example 6. Fig. 23 shows an example of a sequence of operations when a broadcast-managed application is started up as a broadcast-managed application, as a broadcast-managed application, is started up as a broadcast-managed application, as a third configuration example and processing example of the broadcast receiving device 100 of Example 6. Fig. 23 shows an example of confirming with the user in real time each time whether or not the broadcast-managed application can be started up by a message or the like on the screen. 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.

In FIG. 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 can be executed 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 that allows the user to select whether or not to allow the broadcast-linked app to be started.

The user selects whether or not to launch the broadcast-linked app on the launch confirmation screen displayed in S1306 using an operating means such as the mobile information terminal 700 or a remote control (S1307). The broadcast receiving device 100 receives the selection information as an instruction input.

If the broadcast-linked app is not selected to be launched based on the result of the user's selection of whether or not to launch in S1307, i.e., if the user does not allow the launch at this point (S1308-No), the broadcast receiving device 100 ends the process in FIG. 23. In other words, the application control unit 161 does not acquire or launch the broadcast-linked app specified in the AIT.

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 sends a distribution request for the broadcast-linked app to a specified service provider server 400 via the LAN communication unit 121 based on the information described in the application acquisition destination information 905.

The service provider server 400, which receives the distribution request for the above-mentioned broadcast-linked app, 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).

Next, the broadcast receiving device 100 launches a specific broadcast-linked app 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).

As a variant, the processes of S1306 to S1308 may be performed after acquiring the broadcast-linked app in the processes of S1309 to S1310.

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 launch the broadcast-linked app, and if it is confirmed that the app is acceptable, the broadcast-linked app can be launched.

In the example of FIG. 23, the mobile information terminal 700 functions as an operating means for the broadcast receiving device 100 through terminal linkage to select whether or not to start the device. This is not limited to this, and an embodiment is also possible in which the selection of whether or not to start the device is made using a remote control or the like provided on the main body of the broadcast receiving device 100.

[Start confirmation screen]
FIG. 24 shows an example of a start-up confirmation screen of the broadcast receiving device 100 displayed by the processing of S1306 in FIG. 23. In this embodiment, a message box 173f1 is displayed as a start-up confirmation screen on the screen of the video display unit 173 in FIG. 24. The message box 173f1 includes a message that a specific broadcast-linked application is available, and a display of "Yes" and "No" buttons for selecting whether or not to start the broadcast-linked application. An example of the message is "Broadcast-linked application XXX is available. Do you want to start broadcast-linked application XXX?" Another example of the message is "The start-up of broadcast-linked application XXX has been specified and is available, but do you want to allow the start-up?".

When the message box 173f1 shown in Fig. 24 is displayed, the user uses the above-mentioned operating means to select whether or not to launch the app (S1307). For example, the user uses the cursor keys 741ac and the enter key 741ad, etc. to select "Yes" or "No" on the basic screen 741a of the linkage control app of the mobile information terminal 700 in Fig. 10A. This allows the user to select whether or not to allow the launch of the broadcast linkage app presented in the message box 173f1 on the broadcast receiving device 100, depending on their own convenience and situation at the time.

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 above, or other marks or images, 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 starts up a specific broadcast interlocking application. Also, if the interlocking application key 741a9 corresponding to the selection of the icon 173b0 is not pressed for a specific period of time or longer, the display of the icon 173b0 may be erased.

[Effects, etc.]
As described above, according to each configuration example of the broadcast receiving device 100 of Example 6, even if there are provisions and instructions for automatic startup with priority given to a broadcast managed application by the PMT and AIT and it is confirmed that the broadcast managed application can be executed by the AIT, the startup of the broadcast managed application can be appropriately controlled according to the user's selection. In other words, according to the broadcast receiving device 100 of this embodiment, it is possible to execute functions with higher added value.

Which of the above first to third configuration examples or various modified examples is to be adopted is specified as a specification of the broadcast receiving device 100 or the like, or the user can select and set the broadcast receiving device 100 or the like. For example, in the configuration examples of FIG. 21 and FIG. 22, the user can select from two values, (a) "Allow the launch of the broadcast managed application (Yes)" and (b) "Do not allow the launch of the broadcast managed application (No)", as the operation setting value by the user setting. This is not limited to this, and as a modified example, the user may select from multiple values including values such as (c) "Ask the terminal" and (d) "Check on the screen each time" in addition to the above (a) and (b). The broadcast receiving device 100 of this modified example performs a control operation according to the first to third configuration examples in response to the setting value selected by the user. In the case of the setting of (c), the process of the second configuration example is performed, and in the case of the setting of (d), the process of the third configuration example is performed.

In particular, in the first configuration example of FIG. 21, 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 appropriate according to their own convenience and use the broadcast-linked app.

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

In particular, in the second configuration example of FIG. 22, it is possible to set whether or not to automatically start the broadcast managed app on a per-user basis who owns a mobile information terminal 700, and further, it is also possible to select whether or not to automatically start the broadcast managed app depending on the presence or absence of a mobile information terminal 700 that performs a linked operation.

An example of the above settings and usage will be described with reference to FIG. 20. As user settings on the mobile information terminal 700, the terminal A of user A has setting A, and the terminal B of user B has a different setting B. For example, setting A allows automatic startup of the broadcast linked app, and setting B allows automatic startup of the broadcast linked app. At the time of processing S1206 to S1209 in FIG. 22, for example, if only the terminal A of user A is operating in a linked state, the terminal A is checked and startup is permitted. If only the terminal B of user B is operating in a linked state, 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 linked mobile information terminal 700 in the situation at that time.

As a variant, control operations are possible that take into account 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, both an embodiment in which the contents of the user settings in the mobile information terminal 700 are prioritized over the user settings in the broadcast receiving device 100 and an embodiment in which the contents of the user settings in the broadcast receiving device 100 are prioritized over the user settings in the mobile information terminal 700 are possible.

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

In particular, in the third configuration example of FIG. 23, it is possible to control whether or not to launch each broadcast managed app prepared for each broadcast program. The user can view the broadcast managed app and confirmation information presented on the screen, and can allow the app to be launched if they wish to launch the app at that time, or can disallow the app from being launched if they do not wish to launch the app at that time.

In addition, in the third configuration example, the user may be allowed to set whether or not to check on the screen each time the broadcast-linked app is 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.

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

Furthermore, if the setting value of the application control code 903 is the above (5) "Forced Start" or if the value of the above "Forced Start Setting" item is "Enabled", the broadcast receiving device 100 performs control as follows. That is, even if the above operation setting value is set to (b) No, the broadcast receiving device 100 controls to forcefully start the broadcast managed application. In other words, the control of this embodiment provides forced start as an item that is higher in rank and has priority than the user-selected item regarding the automatic start described above. In an embodiment that provides the above-mentioned forced start option, applications that need to be displayed and provided with a high degree of necessity, such as an application for displaying emergency information from the broadcasting station or an application required for the production of a specific commercial, can be suitably displayed and provided to the user.

As another embodiment, if a broadcast-linked app is pre-installed inside the broadcast receiving device 100, processing such as obtaining the broadcast-linked app from the service provider server 400 described above (e.g., S1108 to S1110 in FIG. 21) becomes unnecessary.

The information contained in the broadcast waves for controlling the broadcast-linked app is not limited to 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 waves, or may be provided in a form separate from the broadcast waves. The control information may be set in advance within the device.

The following describes Example 7 of the present invention. Note that the configuration and effects of this example are the same as those of Example 1 unless otherwise specified. For this reason, the following mainly describes the differences between this example and Example 1, and explanations of common points are omitted as much as possible to avoid duplication.

The broadcast linkage app, which is an application used in the broadcast communication linkage system of this embodiment, is composed of an HTML document, and can therefore be linked to other HTML documents on the network. The broadcast managed app's operations such as launching/terminating are controlled based on the AIT application control code 903 etc. contained in the broadcast signal of the broadcast waves. The operations such as launching/terminating of non-broadcast managed applications and general applications are not controlled by the above-mentioned broadcast signals. Note that hereinafter, non-broadcast managed applications may be referred to as "non-broadcast applications" and general applications as "general applications".

Because links are possible in the HTML documents constituting the above-mentioned broadcast linked app, in Example 7, it is possible to transition from the broadcast managed app to a non-broadcast app or a general app. In addition, in Example 7, it is also possible to directly launch the non-broadcast app or general app in response to a user's instruction operation from the above-mentioned broadcast linked app launcher screen, etc. For example, a broadcast station, service provider, etc., includes information instructing a transition to other HTML documents 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, a transition from the above-mentioned broadcast managed app to a non-broadcast app, etc. may occur.

Because the above non-broadcast applications and general applications are not controlled by broadcast signals for their start/stop operations, a user may execute non-broadcast applications and general applications while watching a broadcast program. When a user is executing a non-broadcast application while watching a broadcast program, a broadcast managed application linked to the broadcast program may also be requested to be started. Such a request may be, for example, an instruction to start the application by application control code 903 of the AIT included in the broadcast signal. That is, in this case, it is requested that the non-broadcast application or general application and the broadcast managed application be executed in parallel, or that one of them be selected. Although it is technically possible to execute multiple different types of applications in parallel in this way, it may be undesirable in terms of control, and may be inconvenient for the user.

Therefore, the broadcast receiving device 100 of Example 7 has a function of controlling the overlapping or parallel launch of the apps or the launch and termination of each app so that it can deal with the above situation appropriately. When a request is made to launch and execute a second app while a first app is being executed, this function controls the operations including the launch and termination of those apps according to the user's selection. In particular, when a request is made to launch a broadcast-managed app while a non-broadcast app or the like is being executed, this function controls the termination of the non-broadcast app or the launch of the broadcast-managed app according to the user's instruction input, settings, etc. In Example 7, an example of the control operation of the broadcast receiving device 100 in the above cases and situations will be described.

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

The means of 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 situation in which a request has been made 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 operation of inputting a selection instruction on the screen. In accordance with the user's selection, the function executes the control content selected, for example, from (1) to (3) above. (b) The above function accepts the operation of user settings made in advance by the user. When the above request is received, the function executes the control content selected, for example, from (1) to (3) above in accordance with the confirmation of the user setting information.

Figure 26 shows a system configuration and a usage example including a broadcast receiving device 100 of Example 7. The broadcast receiving device 100 receives broadcast waves from the 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 application, which is a broadcast linked application, from the service provider server 400 or the like as appropriate based on information such as the AIT. The broadcast receiving device 100 also acquires non-broadcast applications and general applications from the service provider server 400 or other application servers 500 as appropriate. There may also be a mobile information terminal 700 that performs terminal linkage with the broadcast receiving device 100, and various applications may be acquired and executed between the broadcast receiving device 100 and the mobile information terminal 700 in a terminal linkage state.

The broadcast receiving device 100 of Example 7 has a multiple app 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 apps, parallel execution, etc., based on the operations of the 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 accepts 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 accepts and processes user settings.

For example, when a broadcast program is being watched and a non-broadcast app or a general app is being executed and a broadcast-managed app is instructed to be launched by the AIT of the broadcast waves, the multiple app execution control means 2600 controls the termination of the non-broadcast app, the launch of the broadcast-managed app, etc., depending on the control operation selected by the user and the user selection means 2601 corresponding to the case.

[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 the video of a broadcast program, information such as the AIT, and information such as the 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 control of the launch, termination, etc. of the application. For example, a broadcast managed application 2011 is launched by the AIT information included in the broadcast wave 2010.

In Example 7, the broadcast-linked apps are broadly categorized into (a) broadcast-managed apps, (b) non-broadcast apps, and (c) general apps. Broadcast-managed apps operate in a broadcast reception state based on a control signal included in the broadcast signal, and are permitted to access broadcast resources. Non-broadcast apps 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 apps operate independently of the broadcast signal, and are not permitted to access broadcast resources.

In FIG. 27, App1, which is the broadcast managed application 2011, is composed of, for example, four documents, HTML11 to HTML14. App2, which is the non-broadcast application 2012, is composed of, for example, two documents, HTML21 to HTML22. App3, which is the general application 2013, is composed of, for example, two documents, HTML31 to HTML32. Transitions can be made between each HTML document by links indicated by solid arrows. For example, transitions can be made from HTML13 in App1 to HTML21 in App2 or HTML31 in App3. The dashed arrows show examples of transitions between HTML documents.

In FIG. 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, and App3, which is a general application 2013, can be launched. App2 is executed, for example, by loading HTML21, and App3 is executed, for example, by loading HTML31.

An example of the execution of each app independently while a broadcast program (e.g., broadcast program A) is being played back via the broadcast waves 2010 is as follows. (a1) The AIT instructs the launch of App1, which is a broadcast managed app 2011, and App1 is launched and executed. App1 is permitted to access broadcast program A. Then, when the same AIT instructs the end of App1, App1 is ended.

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

[Operation sequence when broadcast managed app is launched]
Fig. 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 started by the AIT of the broadcast signal while a non-broadcast application is being executed during viewing of a broadcast program. Note that the following description is for a non-broadcast application, but the same is also possible for a general application. In Fig. 28, it is assumed that the broadcast managed application is prioritized for startup and is specified and instructed by information on the PMT and information such as the application control code 903 and startup priority 907 of the AIT.

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 an instruction to start the non-broadcast application is given. Then, the broadcast receiving device 100 displays, for example, an execution screen of the non-broadcast application superimposed on the broadcast program screen (S1401). When the broadcast program is switched in the S1401 state, the contents of information such as PMT and AIT in the broadcast signal are updated. Even if the update is made, the non-broadcast application continues to be executed because its operations such as start/stop are not controlled by the broadcast signal.

Next, the broadcast receiving device 100 acquires the PMT data string separated by the first separation unit 132 by 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 is high, for example. Then, the broadcast receiving device 100 acquires the AIT data string separated by the first separation unit 132 by the application control unit 161 (S1404) and checks the application control code 903 of the acquired AIT data string (S1405). In the process of S1405, if the application control code 903 is "automatic startup", the broadcast receiving device 100 further checks the application profile 904 of the AIT data string (S1406). In S1406, the broadcast receiving device 100 checks whether the broadcast managed application specified in the AIT can be executed.

If it is confirmed that the above can be executed, the broadcast receiving device 100 causes the application control unit 161 to display a launch selection screen (such as FIG. 30 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 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 Example 7, as a selection of the above control operations, the launch selection screen allows the user to select whether to continue or terminate the execution of the non-broadcast application, whether to launch the broadcast managed application, etc. 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, etc.

On the launch selection screen displayed in S1407, the user uses his/her operating means, such as the mobile information terminal 700 or the remote control of the broadcast receiving device 100, to select a control operation related to launching or terminating the multiple types of apps (S1408). The broadcast receiving device 100 receives the user's selection as an instruction input. If the launch of the broadcast managed app is not selected according to the user's selection in S1408 (S1409-No), the broadcast receiving device 100 ends this process in FIG. 28. That is, the application control unit 161 does not acquire or launch the broadcast managed app specified in the AIT. The non-broadcast app continues to run.

On the other hand, if launching of the broadcast managed app 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 app that is currently running.

Next, the transmitting/receiving device 100 transmits a broadcast managed application distribution request to the specified 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 receives 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 specified broadcast managed application stored in the application memory area 4013 via the LAN communication unit 421 (S1412). The broadcast receiving device 100 then starts the broadcast managed application received via the LAN communication unit 121 based on the control of the application control unit 161 by the application engine 162 (S1413).

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

As a modified example, the above-mentioned processes of S1407 to S1410, such as checking the start of the application and terminating the non-broadcast application, may be performed after the broadcast-managed application is acquired in S1411 to S1412.

[Control example]
FIG. 29 shows an example of control of the reproduction and execution of a broadcast program and a plurality of types of applications corresponding to the process of FIG. 28 of the seventh embodiment. The horizontal axis indicates time. The vertical direction indicates the reproduction of the video of the broadcast program by the broadcast signal of the broadcast wave and the control instruction by the AIT, and (A) the first control, (B) the second control, and (C) the third control in association with each other. (A) The first control indicates (A1) the execution of App2, which is a non-broadcast application, and (A2) the execution of App1, which is a broadcast managed application. Similarly, (B) The second control indicates (B1) the execution of App2 and (B2) the execution of App1. (C) The third control indicates (C1) the execution of App2 and (C2) the execution of App1. As described above, the start priority of App1, which is a broadcast managed application, is higher than that of App2, which is a non-broadcast application.

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 issues an instruction to launch App1, a broadcast managed app linked to broadcast program B.

(A) In the case of the first control, for example, App2, which is a non-broadcast application, is launched by user operation at time t2 as in (A1), and is 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 continuation of App2 and launch of App1 as a user selection from t3 to t4. The multiple application execution control means 2600 of the broadcast receiving device 100 launches App1 at t4 as in (A2) while continuing the execution of App2 in accordance with the user selection, 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 user operation or the like. Execution of App1 continues from t5 to t6, and at t6, in accordance with an instruction to terminate App1 by the AIT, App1 is terminated.

(B) In the case of the second control, App2 is executed from t2 to t3 as 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, the broadcast receiving device 100 ends the execution of App2 and starts App1 at t4 as in (B2). Thereafter, App1 is executed from t4 to t6.

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

[Startup selection screen]
30 shows an example of a start selection screen displayed by the process of S1407 in FIG. 28 in the seventh embodiment. This screen displays a message box 173g1. The message box 173g1 includes a display of a message indicating that a non-broadcast application is currently being executed, that a broadcast managed application has been instructed to be started and is in a state where the start can be performed, and that the user is asked to confirm and select whether or not to start the application. The message box 173g1 in this example includes "Yes" and "No" buttons for allowing the user to select whether or not to start the application.

With message box 173g1 displayed, the user selects "Yes" or "No", for example, using cursor keys 741ac and decision key 741ad on the basic screen 741a of the collaborative control app. That is, the user selects "Yes" if he or she wishes to launch a broadcast managed app at that time, or selects "No" if he or she wishes to continue running a non-broadcast app. This screen allows the user to easily select whether or not to launch a new broadcast managed app on a broadcast receiving device 100 that is currently running any desired non-broadcast app, depending on his or her own convenience and desires at the time. The above control is also possible for general apps.

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

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

When message box 173g2 is displayed, the user selects from the above options using, for example, color key 741ae on basic screen 741a of the collaborative control app. For example, blue corresponds to control (1), red corresponds to control (2), and yellow corresponds to control (3). Using the above screen, the user can easily select whether to end or start each app depending on the situation at the time.

The above-mentioned start-up selection screen is not limited to a form displayed when a request is made, but can also be a form displayed when the 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 in FIG. 25, and displays control options such as (1) to (3) above in the menu, allowing the user to set the selection. When a request is made, the broadcast receiving device 100 executes control according to this user setting information.

[Multiple apps execution screen]
In the case of controlling to terminate the non-broadcast application and to start and execute 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 the above-mentioned example. That is, the broadcast receiving device 100 terminates, for example, the execution screen of the non-broadcast application that was displayed in an area on the screen of the video display unit 173 separate from the screen of the broadcast program or in an area that overlaps with a part of the screen of the broadcast program, and newly displays the execution screen of the broadcast managed application.

In addition, when the broadcast receiving device 100 launches the broadcast managed app while continuing to execute the non-broadcast app, i.e., when controlling to execute both apps in parallel, the broadcast receiving device 100 may control the display on the screen of the video display unit 173 as follows. For example, the broadcast receiving device 100 appropriately adjusts the size and display position of the execution screen of both or one of the apps so that the execution screen of the non-broadcast app and the execution screen of the broadcast managed app do not overlap overall. Also, adjustments may be made so that both execution screens overlap in some areas.

The broadcast receiving device 100 may, for example, perform a process of reducing the size of the execution screen of the non-broadcast app that is currently being executed so as not to interfere with the display of the execution screen of the newly launched broadcast managed app. Conversely, the size of the execution screen of the newly launched broadcast managed app may be reduced so as not to interfere with the display of the execution screen of the currently executed non-broadcast app. In addition, the non-broadcast app may be temporarily turned into an icon, 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. In addition, both apps may be turned into icons, and the execution screen may be displayed in response to the user's selection of the icon.

The broadcast receiving device 100 may, for example, display a broadcast program playback screen within the screen of the video display unit 173, overlay an execution screen of a non-broadcast app on a partial area of the broadcast program playback screen, and further overlay an execution screen of a broadcast managed app, etc. on a partial area of the execution screen of the non-broadcast app. 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 apps in parallel.

Figure 32 shows an example screen of the video display unit 173 corresponding to the above-mentioned control example of the parallel execution of multiple apps. In the screen of Figure 32, the execution screen of the newly launched broadcast managed app is superimposed on a portion of area 173g3 on the screen 173g displaying the broadcast program. At the same time, the execution screen of the running non-broadcast app is displayed in a reduced size or as an icon, etc. in a portion of area 173g4 within area 173g3. When 173g4 is selected and operated by the user, the execution screen of the non-broadcast app is displayed in an enlarged size in area 173g3, and conversely, the execution screen of the broadcast managed app is displayed in a reduced size or as an icon, etc. in area 173g4. A mark or message indicating that there is an instruction to launch the broadcast managed app may be displayed in area 173g4.

A screen like the one in the example above allows users to easily understand and recognize the status of broadcast programs and the execution of multiple types of apps.

Figure 33 shows another example screen of the video display unit 173 corresponding to the above-mentioned control example of parallel execution of multiple apps. The screen in Figure 33 is divided into multiple areas, in which a broadcast program screen 173g, a non-broadcast app execution screen 173g5, a newly launched broadcast managed app execution screen 173g6, and an area 173g7 displaying information for launch selection and the like are displayed in parallel. Area 173g7 may display a mark or message indicating that there is an instruction to launch a broadcast managed app, or may display information on a list of apps such as the broadcast linked app launcher in Figure 12B. Furthermore, when there are two or more non-broadcast apps, general apps, or two or more broadcast managed apps, this screen may display the execution screens of each app in parallel.

[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 start and end of various applications can be appropriately controlled according to the user's selection. That is, according to the broadcast receiving device 100 of the present embodiment, it is possible to execute a function with higher added value. The user can select and use a non-broadcast application or a broadcast managed application according to the situation or convenience at the time the request is issued.

Which of the controls, variants, screen display control methods, etc. in Example 7 should be adopted will be stipulated in the specifications of the broadcast receiving device 100, etc., or the user will be able to select and set the broadcast receiving device 100, etc.

The following are possible variations of Example 7. As a first variation, after the processing up to S1406 in FIG. 28, the non-broadcast 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 managed application may be automatically started while the non-broadcast application is continued, without confirming the user's selection. Similarly, while the non-broadcast application or the general application is being executed, the broadcast managed application may not be automatically started without confirming the user's selection. In this variation, the user does not have to perform many operations.

As a second modified example, instead of confirming the user's selection instruction input on the start 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 above-mentioned sixth embodiment. For example, the user can select and set, according to preference, whether or not to start a broadcast managed app while a non-broadcast app or a general app is being executed, using user setting information from the above-mentioned function setting menu, etc. The broadcast receiving device 100 stores the setting value in the storage unit 110. When a request is made to start a broadcast managed app while a non-broadcast app or the like is being executed, 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 S1407 to S1409 above. The broadcast receiving device 100 judges and decides on the control of the above-mentioned start, etc., according to the contents. In this modified example, the user can change the user setting as appropriate according to his or her convenience, etc., and use multiple types of broadcast linked apps.

The same can be achieved when 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 the presence or absence of a linked mobile information terminal 700 or the user settings of each linked mobile information terminal 700.

As another variation, as a control example related to the second control (B) in FIG. 29 above, the broadcast receiving device 100 may display information that the non-broadcast app has been terminated midway and a broadcast managed app has been launched, and after terminating the broadcast managed app, may automatically or by a specified user operation re-launch and execute the non-broadcast app that was midway terminated. In this variation, the user can easily return to using the non-broadcast app.

As another modified example, as 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 puts the broadcast managed app on hold instead of launching it in accordance with a user selection, and continues the non-broadcast app that is currently running. After that, the broadcast receiving device 100 launches the broadcast managed app that was on hold, for example, after the non-broadcast app is terminated. As an example of screen display control in this case, a message or mark indicating that there is a request to launch the broadcast managed app or that the launch is on hold is displayed in a corner of the execution screen of the non-broadcast app. This prompts the user to terminate the non-broadcast app and launch the broadcast managed app. In this modified example, the user can move on to using the broadcast managed app at a convenient time.

The following describes Example 8 of the present invention. Note that the configuration and effects of this example are the same as those of Example 1 unless otherwise specified. For this reason, the following mainly describes the differences between this example and Example 1, and explanations of common points are omitted as much as possible to avoid duplication.

The broadcast receiving device 100 of Example 8 has a function of appropriately controlling the restart of an app that has been terminated in accordance with a user's selection when the app is restarted. Although automatic restart of a broadcast-linked app is technically possible, there are cases where this is undesirable from a control standpoint or where it is inconvenient for the user. In contrast, the broadcast receiving device 100 of Example 8 allows the broadcast-linked app to be restarted, and then controls the restart in accordance with the user's selection of whether or not to allow the restart. This makes it possible to respond to cases such as when the app is terminated due to a user mistake by restarting the app in accordance with the user's selection.

In Example 8, the broadcast receiving device 100 performs the following control when an app that has been instructed to be started preferentially and automatically by the AIT or the like is terminated by a user operation or the like, and the instruction to start the app by the AIT is still in effect. That is, (1) the broadcast receiving device 100 controls restart in response to a user selection, i.e., in response to an instruction input or confirmation of a user setting. (2) The broadcast receiving device 100 displays information, such as an icon on the screen, for allowing 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.

Figure 34 shows a system configuration including a broadcast receiving device 100 of Example 8. The broadcast receiving device 100 has 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 regarding 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 Example 6, etc.

The application restart control means 3400 stores information related to 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 related to 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, depending on the user selection by the user selection means 3401. When restarting the application, the application restart control means 3400 uses the application execution information 3411.

Figure 35 shows examples of broadcast program playback by broadcast signals, instructions by the AIT, execution and control of broadcast managed applications, and user operations and selections in Example 8, all related on a time axis.

A broadcast managed app, which is a type of broadcast linked app used in the broadcast communication linked system of this embodiment, has its operations such as start/stop controlled based on information such as the AIT application control code 903 included in the broadcast signal. Of course, the operation of the broadcast managed app may be controlled based on user instructions, etc.

When the above-mentioned AIT or the like is used to control the operation of launching a broadcast managed app linked to a broadcast program, information such as the AIT application control code 903 for instructing the launch is included in the broadcast signal at least at the start of the broadcast program. Furthermore, the information needs to be included in the broadcast signal not only at the start of the broadcast program but continuously while the broadcast program is being aired. The reason for this is that users do not always watch a broadcast program from the beginning, but may start watching it from the middle of the program. When playing a broadcast program from the middle, if the above-mentioned information is not included in the broadcast signal, the broadcast managed app cannot be launched.

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 makes it possible to control the launch of a broadcast managed app even when a user starts watching a broadcast program partway through.

On the other hand, information such as application control code 903 for instructing the termination of execution of a broadcast-managed app can 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. Also, if the broadcast-managed app is to be terminated at any timing during the broadcast of a broadcast program, for example, at a time specified by the broadcast station, termination instruction information can be included in the broadcast signal at that timing. When the broadcast receiving device 100 receives the termination instruction, it terminates execution of the broadcast-managed app.

In addition, 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 mentioned. For example, the broadcast receiving device 100 terminates the execution of the broadcast managed app based on the user using the mobile information terminal 700 or a remote control to change the frequency channel, i.e., to select the channel or program to be played, or to issue an instruction to terminate the app.

The example of AIT in FIG. 35 shows an example of the case where instruction information is continuously and periodically included during the airing of a broadcast program as described above. For example, there is a broadcast managed app M1 linked to broadcast program A. During the period from time t1 to t3 during the airing of broadcast program A, 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 app M1. The last AIT at t3 includes at least an instruction to automatically end the broadcast managed app M1. As a result, as shown in (a), the broadcast managed app M1 is automatically executed during the period from t1 to t3. During the period from t1 to t3, an AIT is distributed in the same manner as at t2. The same applies to broadcast program B and broadcast managed app M2.

The broadcast-managed app may be terminated based on a user instruction during the broadcast of the broadcast program. Even in this case, the PMT, AIT, etc. included in the broadcast signal may continue to instruct automatic startup with priority given to the app while the broadcast program is continuing.

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

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 once terminated, the AIT is checked periodically immediately, and the app is automatically restarted according to the AIT's instruction to automatically start up. From the user's perspective, the app is restarted immediately despite the user's instruction to terminate the app. Therefore, a configuration can be considered that makes it impossible to automatically restart the same broadcast managed app as described above.

On the other hand, the possibility that the instruction to terminate the broadcast-managed app may be an erroneous operation by the user must also be taken into consideration. In light of this possibility, it is not desirable to completely prohibit the automatic restart of the same broadcast-managed app described above. From the user's perspective, it is inconvenient because if the app is terminated by mistake, it cannot be immediately restarted or restored.

The broadcast receiving device 100 of Example 8 has a function of performing control that takes into account the restart of the above-mentioned app. Example 8 describes an example of control of restart of the broadcast managed app of the broadcast receiving device 100 in a case where execution of the broadcast managed app is terminated based on a user's instruction operation or the like at any timing during a broadcast program, and the same app continues to be instructed to be automatically started with priority based on information such as the AIT included in the broadcast wave.

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

(e) to (g) in FIG. 35 show examples of control by the broadcast receiving device 100 of Example 8. In Example 8, in a case such as (d), confirmation of user selection is made in (e). In response to this, in the first control of (f), broadcast managed app M2 is prevented from being restarted and re-executed. In addition, in the second control of (g), control is exercised so that broadcast managed app M2 is restarted and re-executed. The user selection in (e) is input of an instruction on the screen, confirmation of user setting information, etc.

[Operation sequence when restarting the broadcast managed app]
FIG. 36 shows an example of a control operation sequence including a process of restarting a broadcast managed application 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 the broadcast managed application is to be started with priority. The broadcast receiving device 100 terminates the broadcast managed application 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's instruction operation. Furthermore, the broadcast receiving device 100 appropriately checks the PMT and AIT, and controls whether or not to restart the broadcast managed application that was once terminated, in response to a user's selection.

In FIG. 36, the broadcast receiving device 100 acquires a TS by selecting a frequency channel desired by the user using the tuner/demodulator unit 131. Then, in 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 of the AIT, checks the executable state from the application profile, and appropriately acquires a broadcast managed application, which is a specified broadcast-linked application, from a carrier server or the like. The broadcast receiving device 100 launches the broadcast managed application using the application engine 162 based on the control of the application control unit 161.

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

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

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

When the broadcast managed application is terminated in S1511, the broadcast receiving device 100 again acquires the PMT data sequence by the main control unit 101 (S1512), and acquires the AIT data sequence 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 a process of instantly acquiring and referencing the information. Note that the PMT includes information indicating the AIT, and here both the PMT and the AIT are referenced and acquired.

Next, in the process of S1514, the broadcast receiving device 100 checks whether the AIT information of S1513 above indicates the start of the same application as when it was temporarily stored in S1509, for example, automatic start with priority given to the broadcast managed application. In other words, in S1514, it is checked whether the 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 at the time of temporary storage in S1509, that is, if the start of the same application and the execution of the same document are instructed and the display content has not been updated (Yes), proceed 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 the start of a different application or the execution of a different document has been instructed and the display content has been updated (No), proceed to S1515.

Note that, for example, while a broadcast program is being aired, 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 among multiple HTML documents that make up the same broadcast-linked app is changed. 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 app. In S1514, the presence or absence of such changes is also determined.

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 specified broadcast managed application or updating the display content again in the same manner as the processing of S101 to S108 in FIG. 7A, based on the information content of the changed PMT and AIT acquired in S1512 and S1513. Then, the main processing of FIG. 36 ends.

Figure 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 Figure 37 at S1515 above. The screen in Figure 37 displays a predetermined mark 173h1 or a message indicating that restart of the broadcast managed app has been prevented on the 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.

On the other hand, if the process proceeds to S1516, the broadcast receiving device 100 performs control to restart the broadcast managed app 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 app that was terminated in S1511 in response to a user selection operation.

Figure 38 shows a restart confirmation screen, which is an example of a screen displayed in S1516 above. 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 or the like. The broadcast receiving device 100 accepts a user selection operation for the information on this screen, in other words, an instruction input operation for selecting whether or not to restart. The message box 173h2 includes a message for confirming whether or not 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.

Icon 173h3 is an icon indicating a specific broadcast managed application. The broadcast receiving device 100 restarts the application by selecting the icon 173h3. The icon 173h3 may be the same as the icon 173b0 that makes the user aware of a broadcast linked application that can be started, as shown in FIG. 12A described above. In addition, the broadcast receiving device 100 automatically erases the display of the message box 173h2 or the icon 173h3 after a predetermined time has elapsed since displaying the message box 173h2 or the icon 173h3, and in this case, restart is not performed. Since the display of the confirmation information continues for a predetermined time, the user can restart the application by selecting the icon 173h3 remaining on the screen. The user can easily select whether or not to restart the application from the above screen according to his or her convenience at the time.

In S1517, the screen of S1516 in FIG. 36 is operated by the user using an operating means such as the mobile information terminal 700 or a remote control to select the restart icon 173h3 or the like. 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 restart of the broadcast managed app that was terminated in S1511.

When restarting a broadcast managed app, the broadcast receiving device 100 first, in S1518, reads out the data of the HTML document constituting the app in the app execution information 3411 that was temporarily stored in S1509, using the application control unit 161. Then, in S1519, the broadcast receiving device 100 executes the HTML document using the application engine 162 under the control of the application control unit 161. This restarts the broadcast managed app that was terminated in S1511.

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 mentioned above, etc. This causes the broadcast receiving device 100 to not internally generate an instruction to restart, and also erases the display of the restart confirmation screen.

As described above, according to the broadcast receiving device 100 of Example 8, even when a broadcast managed app is terminated by user operation during a broadcast program and the same app continues to be instructed to be automatically started with priority 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 immediately restart the app even in the case of an incorrect operation, which is highly convenient. In other words, according to the broadcast receiving device 100 of this example, it is possible to execute functions with higher added value.

As a variation of the eighth embodiment, the process of restarting the app 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 or not restarting the app is permitted, and stores a setting value based on a user operation in the storage unit 110 (storage unit 710 in the case of the mobile information terminal 700) in advance. Instead of the restart confirmation screen in step S1516, the broadcast receiving device 100 checks by referring to the setting value in the broadcast receiving device 100 or the mobile information terminal 700. If restart is permitted with the setting value, the broadcast receiving device 100 restarts the app.

As a modified example 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 the process of terminating the broadcast managed app in S1511. The display of the broadcast managed app when it is executed is set to transparency = 0%, and the display of the broadcast managed app when it is terminated is set to transparency = 100%. When the broadcast receiving device 100 terminates the app in S1511, it does not terminate the app as a computer process but maintains it, and changes the transparency of the display of the execution screen of the app on the screen to 100% to make it invisible to the user. In addition, when the broadcast receiving device 100 restarts the app in S1516 to S1517, it makes it visible to the user by restoring the transparency of the display of the app on the screen to the original state of 0%. In the case of this modified example, when the processes of S1518 to S1519 are performed, there is no need to read and execute the HTML document of the app execution information 3411 in the temporary storage area, and the processing load is low. The above transmittance may be a value other than 0% or 100%.

The following describes Example 9 of the present invention. Note that the configuration and effects of this example are the same as those of Example 8 unless otherwise specified. For this reason, the following mainly describes the differences between this example and Example 8, and explanations of common points are omitted as much as possible to avoid duplication.

The broadcast managed application used in the broadcast communication cooperation system of Example 9 is not only controlled for its operation such as start/stop based on information such as AIT included in the broadcast signal, but also allows event operation control such as page update by event messages appropriately included in the broadcast signal. In this embodiment, a page update means a change in part or all of the information such as characters and images constituting the 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 as a transition between applications and between HTML documents in the above-mentioned FIG. 27. An HTML document corresponds to a page. An update corresponds to a change in the HTML document constituting the application.

When AIT or other information included in the broadcast waves continues to instruct the broadcast-managed app to automatically start with priority, event messages for controlling the event operation of the app will also continue to be included in the broadcast waves as necessary. Even if the user terminates the broadcast-managed app of their own volition, page updates and other operations may be performed based on event messages or other information in the broadcast waves. In this case, the execution and display content of the app will change due to page updates before and after termination.

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 the page information that is newly provided by the page update. The broadcast receiving device 100 of Example 9 has a function to appropriately control the restart of the app, taking into consideration the above-mentioned cases and circumstances of page updates, etc.

[Operation sequence when restarting the broadcast managed app]
Fig. 39 shows an example of an operation sequence of control for restarting a broadcast managed application in the broadcast receiving device 100 of Example 9 when the broadcast managed application is instructed to be started with priority. In Fig. 39, the broadcast receiving device 100 terminates the broadcast managed application that was automatically started when viewing of a broadcast program is started, in response to a user's instruction. Furthermore, the broadcast receiving device 100 appropriately checks the AIT and the like, and in the case where the information content has not been updated, controls whether or not to restart the terminated broadcast managed application in response to an event message newly acquired from the broadcast wave and in response to the user's selection.

In FIG. 39, the processing of S1600 to S1615 is the same as the processing of S1500 to S1515 in FIG. 36. An event message is appropriately included in the broadcast wave. In S1600, the broadcast receiving device 100 launches a specified broadcast managed application by performing processing similar to S101 to S108 in FIG. 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.

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

In S1610, the user instructs the broadcast managed app to be terminated during the broadcast program. In S1611, the broadcast receiving device 100 terminates the execution of the broadcast managed app. In S1612, the broadcast receiving device 100 acquires the PMT data sequence again, and in S1613, acquires the AIT data sequence.

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 specified broadcast managed application is performed again using the updated PMT and AIT acquired in S1612 and S1613.

On the other hand, if the AIT information acquired in S1613 is the same as the AIT information content of the application execution information 3411 temporarily stored in S1609 (Yes), the process proceeds to S1616, and control is performed to restart the broadcast managed application terminated in S1611. After S1616, the broadcast receiving device 100 of the ninth embodiment monitors and acquires the event message contained in the broadcast wave until the frequency channel is changed or the information such as PMT and AIT contained in the broadcast wave is updated. Note that when the frequency channel is changed or the information such as PMT and AIT contained in the broadcast wave is updated, the broadcast receiving device 100 shifts the process to the above 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.

As an example, in S1616, a page update due to an event instructs transition to and display of the fourth page (HTML14 of App1 in FIG. 27) and subsequent pages of the broadcast managed app. The user has not yet viewed the fourth page and subsequent pages.

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 judges 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. At S1617, if the event is not an instruction for a page update or the like (No), this process in FIG. 39 is terminated. In other words, the broadcast managed app that was terminated at S1611 is not restarted.

On the other hand, if the event is an instruction for page update or the like (Yes) in S1617, the process proceeds to S1618, where control is performed to restart the broadcast managed application that was terminated in S1611. In S1618, the broadcast receiving device 100 reads out the HTML document of the application execution information 3411 that was temporarily stored in S1609. This document is 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 out in S1618 under the control of the application control unit 161. When processing S1619, the broadcast receiving device 100 applies the instruction content of the event message in S1616 to the HTML document to reflect the page update. This restarts the broadcast managed application that was terminated in S1611. The display content of the application screen after the restart is the state after the page update.

As an example, the display content on the screen of the broadcast managed app after the above-mentioned restart will be the fourth page and subsequent pages. After restarting, the user can view the fourth page and subsequent pages that were not viewed before the shutdown.

When the device is restarted, the broadcast receiving device 100 may be controlled so that the new page (e.g., the fourth page) after the page update is automatically displayed. At this time, the broadcast receiving device 100 may display a message on the screen indicating that a page update has occurred or that a new page has been displayed. In this case, the user does not have to go through the trouble of performing operations such as page transitions.

Furthermore, at the time of the restart, the broadcast receiving device 100 may control the display so as to restore the page before the page update (e.g., page 3), 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 (e.g., page 4). In this case, the user can easily recognize the status of the page update.

Figure 40 shows an update confirmation screen, which is an example of a screen for confirming with the user about restarting in the case of a page update and restarting according to the user's selection. The broadcast receiving device 100 displays a screen such as that shown in Figure 40 when the event in S1617 is a page update, for example. This screen displays a message box 173h4. The message box 173h4 includes a message to the effect 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.

As described above, the broadcast receiving device 100 of the ninth embodiment can appropriately 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 obtained from the broadcast wave, and in response to a user selection. In other words, the broadcast receiving device 100 of this embodiment can execute functions with higher added value.

As a variation of the ninth embodiment, the broadcast receiving device 100 may execute the above-mentioned 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 settings regarding whether or not restarting the above-mentioned app is permitted and restarting in the event of a page update due to an event, and stores setting values based on user operations. When obtaining the event message in S1616, the broadcast receiving device 100 checks the above-mentioned setting values and decides whether or not to restart the app.

Although the embodiment of the present invention has been described above using Examples 1 to 9, the configuration for realizing the technology of the present invention is not limited to the above examples and can be modified in various ways. For example, a part of the configuration of one example can be replaced with the configuration of another example, and the configuration of another example can be added to the configuration of one example. All of these belong to the scope of the present invention. Furthermore, the numerical values and messages appearing in the text and figures are merely examples, and the effect of the present invention is not impaired even if different ones are used. The functions of the present invention described above may be realized in part or in whole by hardware, for example, by designing an integrated circuit, or by software, such as by a microprocessor unit interpreting and executing an operating program that realizes each function, or 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 show all the control lines and information lines on the product, and in reality, it may be considered that almost all the configurations are connected to each other.

The above-mentioned software for controlling the broadcast receiving device 100 may be stored in the ROM 103 or storage unit 110 of the broadcast receiving device 100 at the time of product shipment. It may be acquired from other application servers 500 on the Internet 200 via the LAN communication unit 121 after product shipment. Software stored in a memory card or optical disk may be acquired via the extended interface unit 124. Similarly, the software for controlling the mobile information terminal 700 may be stored in the ROM 703 or storage unit 710 of the mobile information terminal 700 at the time of product shipment. It may be acquired from other application servers 500 on the Internet 200 via the LAN communication unit 721 or mobile telephone network communication unit 722 after product shipment. Software stored in a memory card or optical disk may be acquired via the extended interface unit 724.

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 broadcast reception processing unit, 142: Data broadcast 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 linkage control unit, 300: broadcasting station server, 400: service provider server, 500: other application servers, 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 (1)

1. An application startup method for starting an application for accessing a broadcast resource in a broadcast receiving device, comprising:
The application for accessing the broadcast resource includes a broadcast managed application activated by application control information included in the broadcast signal, and a non-broadcast managed application activated by a method 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 launch 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 starting step of starting the non-broadcast managed application based on a start request by a user operation via the external mobile terminal received in the communication step;
Equipped with
The first application startup step includes, when the application control information includes information indicating automatic startup of the broadcast managed application, confirming whether the broadcast managed application is executable, and, if executable, acquiring and starting the broadcast managed application.
How to launch the application.

Images