JP2011166441A - Digital broadcast receiver, terminal device and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To install software for providing a function cooperated with a data broadcast application in equipment on a home network inexpensively and without requiring any user operation. <P>SOLUTION: A digital broadcast receiver 10 is connected with a terminal device 50 over a home network, and is equipped with: a broadcast receiving section for acquiring, from a received broadcast signal, terminal device software and a data broadcast application for registering the terminal device software in the terminal device 50; a data broadcast execution section for executing the data broadcast application and instructing transmission of the terminal device software to be registered to the terminal device 50; and a file providing section for transmitting the terminal device software to the terminal device 50 in response to the instruction. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a digital broadcast receiver that manages software distributed by broadcasting, a terminal device, and a computer program thereof.

  BS (Broadcasting Satellite) digital broadcasting and terrestrial digital broadcasting have already been started, and televisions and receivers compatible with digital broadcasting are widely spread. Digital broadcasting also provides various character information such as news and weather called data broadcasting, and interactive services. A data broadcasting application (also referred to as “data broadcasting content”) is a DSM-CC (Digital Storage Media Command and Control) data carousel method defined in ISO (International Organization for Standardization) / IEC (International Electrotechnical Commission) 13818-6. Is multiplexed into a digital broadcast signal. Also, currently broadcast data broadcasting applications are described in the BML (Broadcast Markup Language) system defined by ARIB (Association of Radio Industries and Broadcast) STD-B24.

  The current BML system is a presentation engine type execution environment in which BML content encoded by an XML (extensible markup language) based description language is presented by a browser. On the other hand, an execution environment in which a data broadcasting application is transmitted as a computer program and the transmitted computer program is executed by a receiver is called an application execution engine. The application execution engine type data broadcasting system is defined as a so-called ARIB-J system by ARIB STD-B23 (see Non-Patent Document 1).

The ARIB-J system realizes various applications by using a Java (registered trademark) -based API (Application Program Interface). In the ARIB-J system, since a data broadcast application is created as a Java (registered trademark) program, it is also expected to provide a higher level of service than the conventional BML system.
For example, it becomes possible to produce an ARIB-J data broadcasting application corresponding to a network by using a network API possessed by Java (registered trademark). Furthermore, in the ARIB-J system, various functions of other devices connected to a home network such as an IP (Internet Protocol) network and software operating on the devices are discovered, and the functions are linked and used. “Network device use API” is provided. In some cases, services that cannot be performed by the receiver alone due to problems with the functions and processing capabilities of the receiver can be realized by borrowing the functions of other devices using the network device usage API. It becomes possible.

  The functions to be linked on the home network can be configured as dedicated hardware if communication corresponding to a protocol determined by the operation of the ARIB-J method, for example, UPnP (Universal Plug and Play), is possible. You may implement | achieve with the software installed in the personal computer (henceforth "a personal computer") which is a general purpose apparatus. When the functions to be linked are realized as software on a personal computer, new functions can be linked by acquiring and installing various applications in advance, which can be introduced at low cost for the user. There are benefits.

  For example, two personal computers A and B are connected on a LAN (Local Area Network), and AV (Audio Visual) content is broadcast to the personal computer A from MPEG (Moving Picture Experts Group) -2 format. Consider a case in which software having a transcoding function for converting to -4 format is installed, and software having a function for displaying content encoded in the MPEG-4 format is installed in the personal computer B. At this time, if the ARIB-J data broadcast application transmitted by broadcasting has a function of using network equipment, and the transcoding function and the display function exist in the home, the transmitted ARIB-J data broadcast application Link the functions. In other words, the transcode function converts the content transmitted by broadcasting from the MPEG-2 format to the MPEG-4 format, and reproduces the format-converted content by the display function on the personal computer B capable of displaying MPEG-4. can do. As in this example, when various functions are linked from the ARIB-J data broadcasting application, the software to be linked must be installed in the personal computer in advance.

Application Execution Environment in Digital Broadcasting Standard ARIB STD-B23 1.2 Edition, [online], Japan Radio Industry Association (ARIB), [Searched on December 20, 2009], Internet <http: //www.arib .or.jp / english / html / overview / doc / 2-STD-B23v1_2.pdf>

  In a conventional data broadcasting execution device such as a TV set compatible with the ARIB-J system, as described above, the ARIB-J data broadcasting application uses a network device use API to link software functions installed on a personal computer to provide services. There are the following problems in providing

  As a first problem, there is a method for obtaining software to be installed in a personal computer. The software installed on the personal computer is provided by a broadcaster who provides the service. Therefore, it is possible to download and install necessary software from a server such as a broadcasting station by using the Internet. However, not all users have an Internet connection environment, and it may be necessary to pay an additional fee for Internet connection. Although it is conceivable to distribute software using a removable medium such as a CD-ROM or DVD-ROM, it is still expensive to distribute to a huge number of users.

  On the other hand, it is possible to multiplex software installed on a personal computer and broadcast it to a broadcast receiver by using the DSM-CC data carousel method. According to this, software downloaded to the broadcast receiver by the user himself can be extracted by some method and installed in the personal computer. However, this has a second problem described below.

  That is, the second problem is that a user needs to install software on a personal computer. In the above service examples, examples of the transcoding function and the display function are shown, but various functions to be linked are assumed depending on the service. It is a heavy burden on the user to acquire and install software necessary for using various services each time.

  The present invention has been made in view of the above-described problems, and an object of the present invention is to provide software that provides functions linked to a data broadcasting application at low cost and without requiring user operation. To provide a digital broadcast receiver, a terminal device, and a computer program thereof that can be installed in a terminal device that is a device on a home network.

[1] According to one aspect of the present invention, a storage unit that stores a program for a terminal device that operates in cooperation with a broadcast application program, a digital broadcast signal is received, and the terminal device program and a network are received from the digital broadcast signal. A registration program for registering the terminal device program in an external terminal device connected via the terminal based on the information multiplexed on the digital broadcast signal, the terminal device program and identification information, And a data broadcast execution unit that outputs a transmission instruction in which identification information of the terminal device program to be registered in the terminal device is set by executing the registration program. And the terminal device corresponding to the identification information included in the transmission instruction output from the data broadcast execution unit A digital broadcast receiver, comprising: a file providing unit that reads a program for storage from the storage unit and transmits the program to the terminal device.
According to the present invention, a terminal device program that operates in cooperation with a broadcast application program and a registration program for adding the terminal device program to the terminal device are distributed by broadcasting, and the registration program in the digital broadcast receiver Is executed, the terminal device program is transmitted to the terminal device connected to the home network, and the terminal device registers the terminal device program received from the digital broadcast receiver.
As a result, it is possible to reduce the cost for distributing the program for the terminal device that operates in cooperation with the data broadcast application executed in the digital broadcast receiver, and to distribute by broadcasting without requiring any user operation. The terminal device program thus installed can be installed in a device on the home network.

[2] One aspect of the present invention is the digital broadcast receiver described above, further including a list acquisition unit that acquires information on a terminal device program registered in the terminal device from the terminal device, and the program execution The unit outputs the transmission instruction in which the identification information of the unregistered terminal device program is set based on the information of the terminal device program acquired by the list acquisition unit.
According to the present invention, the terminal device program to be registered is acquired only when it is determined that the terminal device program already registered is acquired from the terminal device and the terminal device program to be registered is not registered. Send to terminal device.
As a result, when the terminal device program to be registered is already installed in the terminal device, it is possible to prevent the installation.

[3] One aspect of the present invention is the digital broadcast receiver described above, wherein the registered terminal device program information acquired by the list acquisition unit includes function information of the terminal device program. It is characterized by.
According to the present invention, when the function information of the terminal device program already registered is acquired from the terminal device, and it is determined that the terminal device program having the same function as the terminal device program to be registered is not registered. Only the terminal device program to be registered is transmitted to the terminal device.
Thus, if a terminal device program having the same function as the registration target terminal device program is already installed in the terminal device, the registration target terminal device program may not be installed. It becomes possible.

[4] One aspect of the present invention is the above-described digital broadcast receiver, wherein the broadcast receiving unit acquires function information of the terminal device program from the signal, and the function information and the terminal device. The program information is written in the storage unit, and the data broadcast execution unit acquires the terminal device program identification information from the terminal device as the registered terminal device program information. When it is determined that the function of the program for the terminal device to be registered is not registered in the terminal device based on the information of the function read from the storage unit corresponding to the identification information, the transmission instruction is output. It is characterized by that.
According to the present invention, the terminal device program identification information already registered from the terminal device is received, and the function of the terminal device program specified from the identification information has the same function as the terminal device program to be registered. Only when it is determined that the terminal device program is not registered, the terminal device program to be registered is transmitted to the terminal device.
Thus, if a terminal device program having the same function as the registration target terminal device program is already installed in the terminal device, the registration target terminal device program may not be installed. It becomes possible.

[5] Further, one aspect of the present invention is the above-described digital broadcast receiver, wherein the broadcast reception unit acquires function information of the terminal device program from the signal and writes the function information to the storage unit. The data broadcast execution unit outputs the transmission instruction when it is determined that function information of the terminal device program to be registered is stored in the storage unit.
According to the present invention, before transmitting the registration target terminal device software to the terminal device, it is determined whether the registration target terminal device software by the registration program has already been accumulated in the storage unit.
As a result, when the terminal device program cannot be received for some reason, it is possible to stop the additional operation of the terminal device program.

[6] Moreover, one aspect of the present invention is the above-described digital broadcast receiver, which receives the transmission instruction from the data broadcast execution unit and transmits an instruction to add the terminal device program to be registered. The file providing unit further includes a software addition instruction unit for transmitting to the terminal device corresponding to the identification information included in the transmission instruction in response to the acquisition request for the terminal device program received from the terminal device. A program is read from the storage unit and transmitted to the terminal device.
According to the present invention, a terminal device program addition instruction is transmitted to the terminal device, and when there is an access from the terminal device side, the registration target terminal device program is returned.
As a result, the terminal device can be installed only when it is determined that the terminal device program can be installed.

[7] One embodiment of the present invention is the above-described digital broadcast receiver, wherein the broadcast reception unit acquires a broadcast application program that cooperates with the terminal device program from the received digital broadcast signal. The data broadcast execution unit instructs the terminal device to execute the terminal device program by executing the acquired broadcast application program.
According to this invention, the program for terminal devices installed in the terminal device can be executed by executing the broadcast application program.
Accordingly, it is possible to provide a service in which a data broadcast application executed in the digital broadcast receiver and a terminal device program added to the terminal device are linked.

[8] Further, according to one aspect of the present invention, there is provided a storage unit that stores information on a program for a terminal device that operates in cooperation with a broadcast application program, and a digital broadcast receiver connected via a network. Receiving the program and the terminal device program information, registering the received terminal device program and writing the received terminal device program information to the storage unit; and receiving the digital broadcast A terminal device comprising: an added software list notifying unit that receives a terminal device program list transmission request from a machine, reads out information on the terminal device program from the storage unit, and returns the information.
According to the present invention, a digital broadcast receiver receives a terminal device program that operates in cooperation with a broadcast application program, and the terminal device receives the terminal device program received by the digital broadcast receiver over a network. Via and register. The terminal device stores information on the terminal device program received together with the terminal device program, and returns the information when an inquiry is received from the digital broadcast receiver.
As a result, it is possible to reduce the cost for distributing the program for the terminal device that operates in cooperation with the data broadcast application executed in the digital broadcast receiver, and to distribute by broadcasting without requiring any user operation. The terminal device program thus installed can be installed in the terminal device connected to the digital broadcast receiver via the home network. In addition, since the terminal device can notify the digital broadcast receiver of information about the already-added terminal device program, it is possible not to install the already installed terminal device program again. .

[9] Further, one aspect of the present invention is the terminal device described above, wherein the information on the terminal device program includes information on a function of the terminal device program or identification information on the terminal device program. It is at least one of them.
According to the present invention, the terminal device receives and stores at least one of the function of the terminal device program or the identification information together with the terminal device program, and when there is an inquiry from the digital broadcast receiver, Return the stored information.
As a result, when a terminal device program having a function equivalent to that of the registration target terminal device program is already installed in the terminal device, it is possible to prevent the terminal device program from being installed.

[10] Further, according to one embodiment of the present invention, a computer used for a digital broadcast receiver receives a digital broadcast signal, a storage unit that stores a program for a terminal device that operates in cooperation with a broadcast application program, Based on information multiplexed on the digital broadcast signal, the program for the terminal device from the digital broadcast signal and a registration program for registering the program for the terminal device to an external terminal device connected via a network A broadcast receiving unit that acquires and writes the terminal device program and identification information in association with each other into the storage unit, and the terminal device program identification information to be registered in the terminal device by executing the registration program A data broadcast execution unit that outputs a transmission instruction that is set, and an output from the data broadcast execution unit It said a computer program for causing to function as a file providing unit, to be transmitted to the terminal device said terminal device program corresponding read from the storage unit the identification information included in the transmission instruction.

[11] Further, according to one embodiment of the present invention, a computer used for a terminal device is a digital unit connected via a network to a storage unit that stores information about a program for a terminal device that operates in cooperation with a broadcast application program. Software that receives the terminal device program and the terminal device program information from a broadcast receiver, registers the received terminal device program, and writes the received terminal device program information into the storage unit Functioning as an adding unit and an added software list notifying unit that receives a terminal apparatus program list transmission request from the digital broadcast receiver, reads out information on the terminal apparatus program from the storage unit, and returns the information. It is a computer program characterized.

  According to the present invention, a terminal device program that provides a function in cooperation with a data broadcast application executed in a digital broadcast receiver, and a registration program that is a data broadcast application that registers the terminal device program in the terminal device, Can be installed in a device connected to the digital broadcast receiver via the home network by executing the registration program in the digital broadcast receiver that has received the broadcast and received the broadcast. As a result, the cost for distributing the terminal device program can be reduced, and the terminal device program can be installed in a device on the home network without requiring any user operation.

1 is a connection configuration diagram of a digital broadcast receiving system according to a first embodiment of the present invention. It is a functional block diagram of the digital broadcast receiver by the same embodiment. It is an example of the descriptor contained in the digital broadcast signal by the same embodiment. It is an example of data memorize | stored in the memory | storage part of the digital broadcast receiver by the same embodiment. It is a functional block diagram of the terminal device by the embodiment. It is an example of data memorize | stored in the memory | storage part of the terminal device by the embodiment. It is a figure which shows the processing flow of the digital broadcast receiving system by the embodiment. It is an example of API (Application Program Interface) provided by the terminal device software list acquisition unit of the digital broadcast receiver according to the embodiment. It is an example of API which the software list acquisition part for terminal devices of the digital broadcast receiver by the same embodiment provides. It is an example of API which provides the various information of the software for each PC acquired from the software list acquisition part for terminal devices of the digital broadcast receiver by the embodiment. It is an example of API which the software management function control part of the digital broadcast receiver by the same embodiment provides. It is an example of API which the file provision part of the digital broadcast receiver by the same embodiment provides. It is an example of API which the file provision part of the digital broadcast receiver by the same embodiment provides. It is an example of an SCPD (Service Control Protocol Declaration) file that defines the functions of a UPnP (Universal Plug and Play) service provided by the terminal device according to the embodiment. It is an example of the SCPD file which defines the function of the UPnP service provided by the terminal device according to the embodiment. It is a figure which shows the processing sequence of the digital broadcast receiving system by the embodiment. It is a figure which shows the processing sequence of the digital broadcast receiving system by the embodiment. It is a figure which shows the processing sequence of the digital broadcast receiving system by the embodiment. It is a functional block diagram of the terminal device by 2nd Embodiment. It is a figure which shows the example of addition of the difference with FIG.14 and FIG.15 of the SCPD file which defines the function of the UPnP service which the terminal device by the same embodiment provides. It is a figure which shows the processing flow of the digital broadcast receiving system by the embodiment.

[First embodiment]
FIG. 1 is a diagram showing a connection configuration of a digital broadcast receiving system according to a first embodiment of the present invention. In the figure, the digital broadcast receiving system is configured by connecting a digital broadcast receiver 10 and a terminal device 50 via a network 90 which is a home network such as a LAN (Local Area Network). The digital broadcast receiver 10 is a digital broadcast receiver and is connected to an output device 30 having a display and a speaker. The output device 30 outputs the video and audio output from the digital broadcast receiver 10 through a display or a speaker. The terminal device 50 is a computer device capable of executing general-purpose software, and is a personal computer (hereinafter referred to as “PC”), for example. A plurality of terminal devices 50 may be connected to the network 90.

  In the figure, a digital broadcast receiver 10 receives a digital broadcast signal and plays a video or audio of a broadcast program, and in addition to a data broadcast application program (hereinafter simply referred to as “data broadcast application”) multiplexed on the broadcast program. And the processing results of various data broadcast applications are displayed on the television screen of the broadcast program displayed by the output device 30 by the output from the digital broadcast receiver 10. The data broadcasting application is a Java (registered trademark) program corresponding to the ARIB (Association of Radio Industries and Broadcast) -J system.

  The digital broadcast receiver 10 compatible with the ARIB-J system has a network device use function that can control and use functions executed by devices connected on the network over the network. Therefore, a Java (executed on the digital broadcast receiver 10) is installed on the terminal device 50 connected to the network 90 by installing a function that can be controlled by the ARIB-J method as terminal device software (terminal device program). The registered data) data broadcasting application and the terminal device software executed on the terminal device 50 communicate via the network 90, and the Java (registered trademark) data broadcasting application and the software function executed on the terminal device 50 are It is possible to provide a service that links the two.

  A plurality of terminal device software can be installed in the terminal device 50. Therefore, when there are a plurality of ARIB-J compatible terminal device software, it is possible to use the terminal device software for each function requested by the service provided by the data broadcasting application. In this embodiment, an example in which the data broadcast application is a Java (registered trademark) program corresponding to the ARIB-J system is shown. However, the execution environment of the data broadcast application of the digital broadcast receiver 10 is a BML (Broadcast Markup Language) system. Or other program execution environments.

  In the present embodiment, the terminal device 50 is a PC, PC software that is software for the terminal device operating on the PC, and data broadcasting that is a program for performing control for adding the PC software to the terminal device 50. An application (program for registration) is multiplexed with a digital broadcast program and transmitted by a digital broadcast signal. The digital broadcast receiver 10 extracts PC software from the broadcast signal, and adds new PC software while operating in cooperation with the terminal device 50 by a data broadcast application that is a registration program. A function for this purpose is added to the conventional digital broadcast receiver 10, and a software management function for managing addition / deletion of PC software is installed in the terminal device 50.

  FIG. 2 is a block diagram showing the functional configuration of the digital broadcast receiver 10, and only functional blocks related to the present invention are extracted and shown. In the figure, a digital broadcast receiver 10 includes a broadcast receiving unit 11, a storage unit 12, a data broadcast executing unit 13, a terminal device software list obtaining unit 14, a software management function control unit 15, a file providing unit 16, and network control information. A transmission / reception unit 17 and an output unit 18 are included.

  The broadcast receiving unit 11 receives a digital broadcast signal such as BS (Broadcasting Satellite) digital broadcast or terrestrial digital broadcast as an aerial wave or via a cable, and broadcasts video, audio, etc. multiplexed on the received digital broadcast signal. It has a function of extracting data other than broadcast programs such as programs and data broadcast applications, and outputting the extracted data to other functional units. When the PC software and related information are multiplexed and sent to the digital broadcast signal, the broadcast receiving unit 11 extracts them, outputs them to the storage unit 12, and stores them. Similarly, an ARIB-J data broadcast application for performing control for adding PC software to the terminal device 50 is also multiplexed and broadcast on the digital broadcast signal, and the broadcast receiving unit 11 is multiplexed on the digital broadcast signal. The ARIB-J data broadcast application is extracted and output to the data broadcast execution unit 13. If the digital broadcast signal and the digital broadcast receiver 10 are compatible with ARIB STB-B23, it can be detected that the ARIB-J data broadcast application is multiplexed.

  The broadcast receiving unit 11 identifies that the PC software and the ARIB-J data broadcast application are multiplexed based on the information multiplexed on the digital broadcast signal. Information for indicating that the PC software is multiplexed with the broadcast signal is added as a descriptor to module_info_byte of DII (DownloadInfoIndication) information of the data carousel method, for example.

  FIG. 3 is a diagram illustrating an example of a descriptor added to module_info_byte. In the module_info_byte descriptor_tag shown in the figure, a value indicating that this is a descriptor for PC software is set, and in descriptor_length, the data length of this descriptor is set. organization_id, external_application_id, and version are a series of identifiers for specifying PC software. Hereinafter, a set of two identifiers of organization_id and external_application_id is referred to as an application identifier (AppID).

  The PC software is an executable file in Java (registered trademark) jar format, and the PC software data can be identified by a series of ids (identifiers) of <original_network_id>, <transport_stream_id>, and <service_id>, for example. A broadcast signal of a certain broadcast channel is transmitted as an elementary stream of component tag 0x [aa], a module of module identification 0x [bbbb], and a resource name [cccc] [dddd] [ee] .jar. When the arib-dc: name space (arib-dc: // name space) defined by ARIB STB-B24 is used, the URL (Universal Resource Locator) that is the position of the resource in the broadcast signal is “arib- dc: // <original_network_id>. <transport_stream_id>. <service_id> / [aa] / [bbbb] / [cccc] [dddd] [ee] .jar ”.

  arib-dc: By designating the name space, the digital broadcast receiver 10 can extract the target data from the broadcast signal, so that the PC software can be extracted by the digital broadcast receiver 10. Needs to notify the digital broadcast receiver 10 of the ari-dc: name space of the PC software. Therefore, the PC software descriptor is similarly transmitted as the elementary stream of the component tag 0x [aa] and the module_info_byte of the module of the module identification 0x [bb], and the contents of the descriptor are organization_id = 0x [cccc], external_application_id By describing = 0x [dddd] and version = 0x [ee], it is possible to know all the identification information in the above example of the arib-dc: namespace. Thereby, the broadcast receiving unit 11 detects that the PC software is transmitted by the descriptor, and a URL (arib-dc: namespace) indicating the location where the resource of the PC software is transmitted in the broadcast signal. ) In this way, by adding a descriptor for PC software, the arib-dc: name space is indirectly specified, and the channels, components, and modules that contain the PC software, and the PC software resources. The name is specified.

  In addition, when information about a name and a function is defined as information about PC software in module_info_byte shown in FIG. 3, the broadcast receiving unit 11 extracts them and outputs them to the storage unit 12. It is memorized as information. The function type that is the function information of the PC software can be set in func_type_text_char of module_info_byte, and related information such as the name other than the function type can be set in reserved of module_info_byte, for example.

  The storage unit 12 is realized by a hard disk device, a semiconductor memory, or the like, and has a function of receiving various data transmitted by a digital broadcast signal from the broadcast receiving unit 11 and temporarily or permanently storing the data. As described above, the file of data transmitted by the digital broadcast signal is identified by the arib-dc: name space defined by ARIB STB-B24. The storage unit 12 uses the arb-dc: name space URL when transmitted by a digital broadcast signal, or an application identifier (AppID), which is an identifier specified by a descriptor, as PC software specifying information, and for PC The information is stored in the storage unit 12 in association with the software. As a result, the PC software and related information transmitted by the digital broadcast signal are accumulated in the storage unit 12 via the broadcast receiving unit 11, and arb-dc: name space, which is PC software specifying information, or It is specified by an application identifier (AppID) and used later. In other words, the other functions in the digital broadcast receiver 10 specify the arib-dc: name space used at the time of broadcasting by the digital broadcasting signal, or specify the application identifier (AppID) assigned at the time of broadcasting. The data stored in the storage unit 12 is read.

  For example, by the following arib-dc: namespace "arib-dc: // <original_network_id>. <Transport_stream_id>. <Service_id> / [aa] / [bbbb] / [cccc] [dddd] [ee] .jar" The sent PC software is stored in the storage unit 12 as “/ [some_directory] / [some_name]”. Further, the storage unit 12 associates the PC software identification information that is arib-dc: name space (or application identifier AppID) with “/ [some_directory] / [some_name]” indicating the storage location of the PC software. In addition, the arib-dc: name space (or application identifier AppID) and related information indicating the function type and name of the PC software are stored in association with each other.

The data broadcast execution unit 13 executes a data broadcast application transmitted by a digital broadcast signal. The data broadcast execution unit 13 includes an application execution unit 131 and a network device use unit 132.
In the case of an ARIB-J data broadcasting signal, the application execution unit 131 implements an execution environment for a data broadcasting application described by Java (registered trademark). In the Java (registered trademark) execution environment implemented by the application execution unit 131, a Java (registered trademark) virtual environment for the Java (registered trademark) and the Java (registered trademark) execution environment for the digital broadcast receiver 10 should be provided. (Registered Trademark) Basic API (Application Program Interface) is implemented.

  The network device using unit 132 includes an implementation of an API for ARIB-J that has been added according to the ARIB-J standard for use in data broadcasting. The API for ARIB-J implemented in the network device using unit 132 is provided as a Java (registered trademark) class library that operates on a Java (registered trademark) virtual machine, and a manufacturer or the like that provides the digital broadcast receiver 10 digitally It can be used by being incorporated in the broadcast receiver 10 in advance or added to the digital broadcast receiver 10 later by some method. The API for ARIB-J includes various APIs stipulated in the ARIB-J standard (standard ARIB STD-B23), and is a network device use API (ARIB STD-B23) that supports cooperation with functions on the network 90. 1.2 class second part 11.16 class groups and APIs provided by them) are also included.

  The terminal device software list acquisition unit 14 operates as an additional function of the data broadcast execution unit 13. The terminal device software list acquisition unit 14 acquires a list of currently available PC software according to an instruction output from the application execution unit 131 when the data broadcast application is executed, and the application program execution unit 131 operates the data broadcast. Has a function to notify the application. That is, the terminal device software list acquisition unit 14 acquires a list of PC software identification information of the PC software stored in the storage unit 12 and information such as the function type, name, and storage position of each PC software. The application execution unit 131 notifies the data broadcasting application that is operating. When a data broadcast signal according to the ARIB-J system is used, the terminal device software list acquisition unit 14 provides an API for performing control by a Java (registered trademark) data broadcast application.

The software management function control unit 15 operates as an additional function to the network device use function of the data broadcast execution unit 13. The software management function control unit 15 provides an interface (API) for controlling a software management function (detailed functions will be described later) existing on the network by a data broadcasting application.
Thereby, the application execution unit 131 executing the ARIB-J data broadcasting application uses the network device use function of the network device use unit 132 to provide software provided by the terminal device 50 connected via the network 90. The management function is discovered, and the discovered software management function can be controlled using the software management function control unit 15. Therefore, in data broadcasting by the ARIB-J system, the software management function control unit 15 provides an API for performing control by a Java (registered trademark) data broadcasting application.
In addition, the software management function of the terminal device 50 can be controlled by supporting a protocol used by a network device using function such as UPnP (Universal Plug and Play) in order to enable control via the network 90. Therefore, the software management function control unit 15 converts control using the API by the data broadcasting application into control corresponding to a device cooperation protocol such as UPnP that is supported by the software management function of the terminal device 50.

  The software management function control unit 15 includes a list acquisition unit 151 and a software addition instruction unit 152. The list acquisition unit 151 transmits a search signal to the network 90 in order to search for the terminal device 50 that provides the software management function. The software addition instruction unit 152 instructs the terminal device 50 that provides the software management function to install PC software.

  The file providing unit 16 operates as an additional function of the data broadcast execution unit 13. The file providing unit 16, in accordance with an instruction output from the data broadcast execution unit 13 by execution of the data broadcast application, transmits a file transmitted multiplexed with a broadcast program using a digital broadcast signal to the terminal device 50 or the like via the network 90. Make it available from other devices. This file includes PC software. For example, when the network 90 uses IP (Internet Protocol) or the like, a function as an HTTP (Hypertext Transfer Protocol) server or an ftp (File Transfer Protocol) server is provided.

  In the case of data broadcasting by the ARIB-J system, the file providing unit 16 provides a file providing API for performing control from a Java (registered trademark) data broadcasting application. In the API for newly adding a file provision, in order to provide a resource that is transmitted in a data carousel system by a digital broadcast signal defined by ARIB STD-B24, an arb-dc: A name space is designated as one of the arguments, and a URL used to acquire a resource by HTTP or FTP from the terminal device 50 on the network 90 is used as another argument. For example, “http: //...” Or “ftp: //...” Is used as a URL when acquiring a resource by HTTP or FTP. By using such an additional API, a file included in the broadcast signal can be provided to the terminal device 50 on the network.

  The network control information transmission / reception unit 17 uses a network interface provided in the digital broadcast receiver 10 to perform various types of control performed on the functions on the network 90 from the data broadcast application using the network device utilization function of the network device utilization unit 132. It has a function to transmit and receive via. For example, the network control information transmission / reception unit 17 uses a search packet for searching for a function that can be used in a device connected to the network 90, or a control packet used when the discovered function is controlled by the network device use function. Send and receive. Further, the network control information transmission / reception unit 17 transmits / receives a transmission packet or the like of the PC software when adding the PC software received by broadcasting to the terminal device 50 connected via the network 90.

  The output unit 18 outputs video and audio included in the digital broadcast signal to the output device 30. Further, the data broadcast application execution result by the application execution unit 131 is output to the output device 30.

  FIG. 4 is a diagram illustrating an example of data stored in the storage unit 12 of the digital broadcast receiver 10. As shown in the figure, the storage unit 12 stores PC software identification information, a storage location of PC software, and related information in association with each other. The PC software identification information is an arib-dc: name space, an application identifier (AppID), or a unique identifier assigned by the digital broadcast receiver 10. A UUID (Universally Unique IDentifier) is used as a unique identifier assigned in the digital broadcast receiver 10. The related information includes the function type and name of the PC software. The related information may be a PC software descriptor itself.

  FIG. 5 is a block diagram illustrating a functional configuration of the terminal device 50. As shown in the figure, the terminal device 50 includes a software management function unit 51 that implements a software management function. The software management function unit 51 is controlled via the network 90 by a data broadcast application that operates in the digital broadcast receiver 10.

  There are a plurality of technologies such as UPnP (Universal Plug & Play), Jini (Genie), and CORBA (Common Object Request Broker Architecture) as technologies for controlling the functions of other devices via a network. Now, an example using UPnP is shown. When UPnP is used, the software management function unit 51 can be realized as a certain UPnP service, for example. Hereinafter, this UPnP service is referred to as an ExAppManager service. In UPnP, SPCD (Service Control Protocol Declaration) in which the functions of the UPnP service that can be provided are described in an XML document is disclosed to other devices.

  The software management function unit 51 includes a network control information transmission / reception unit 52, a software management function announcement unit 53, an added software list notification unit 54, a storage unit 55, and a software addition / deletion unit 56.

The software management function announcement unit 53 searches for a software management function received via the network 90 in order to inform other devices connected to the network 90 of a series of functions provided by the software management function unit 51. Has a function to respond. The software management function announcement unit 53 has a function of sending announcement information indicating its presence to the network 90 when the software management function unit 51 in the terminal device 50 is activated and at predetermined intervals after activation.
When the software management function unit 51 supports UPnP, the function of the software management function announcement unit 53 is realized by an announcement function of the UPnP protocol. The software management function announcement unit 53 notifies a UPnP announcement indicating that it is a software management function. The UPnP announcement indicating the software management function includes a UPnP device type URN and a UPnP service type URN.

  The software adding / deleting unit 56 has a function of installing new PC software in the terminal device 50 and a function of uninstalling installed PC software. The software addition / deletion unit 56 operates based on an instruction from a data broadcast application executed in the digital broadcast receiver 10 connected via the network 90. When UPnP is used, the software addition / deletion unit 56 can be realized as a UPnP action of the ExAppManager service.

  Upon receiving the URL for acquiring the PC software to be added, the UUID that is a unique ID of the PC software, and the function type, the software adding / deleting unit 56 acquires the PC software from the URL. And installed in the terminal device 50. The software addition / deletion unit 56 manages the added PC software using the received UUID. The software addition / deletion unit 56 writes the UUID and function type of the PC software added by installation in the storage unit 55. If the name of the added PC software and other information can be acquired, the information is also written in the storage unit 55.

As described above, since the added PC software is managed by the UUID, the PC software to be deleted is also specified by the UUID. When the software adding / deleting unit 56 receives the UUID of the PC software to be deleted, it deletes the PC software specified by the UUID. The software addition / deletion unit 56 deletes information such as the UUID and function type of the deleted PC software from the storage unit 55.
Note that the software adding / deleting unit 56 may be realized by another UPnP action for realizing an equivalent function, such as adding or deleting PC software in association with information other than the UUID.

  The storage unit 55 stores information such as UUID, function type, and name of the installed PC software that is managed by the software management function unit 51. Accordingly, the storage unit 55 provides various information such as a list of PC software managed by the software management function unit 51 and UUID and name of each PC software.

  The added software list notification unit 54 obtains a list of UUIDs and function types of PC software managed by the software management function unit 51 from the storage unit 55 and receives digital broadcasts connected via the network 90. In response to a request from a data broadcasting application being executed in the device 10, it has a function of notifying the acquired list.

  The network control information transmission / reception unit 52 has a function of transmitting / receiving various controls using a network device utilization function by a data broadcast application operating on the digital broadcast receiver 10 via a network interface provided in the terminal device 50. For example, transmission / reception of control packets for controlling the added software list notification unit 54 and software addition / deletion unit 56, transmission / reception of search packets and response packets handled by the software management function announcement unit 53, and existence of software management functions Announcement information packet indicating that is transmitted.

  Since the software management function unit 51 described above is provided as a function on the terminal device 50, the software management function unit 51 is implemented by software that can be installed in the terminal device 50 later or software that is preinstalled in the terminal device 50. .

  FIG. 6 is an example of installed PC software information stored in the storage unit 55 of the terminal device 50. As shown in the figure, the installed PC software information stores the UUID of the PC software installed in the terminal device 50 and information such as the function type and name of the PC software in association with each other. .

  Next, operations of the digital broadcast receiver 10 and the terminal device 50 of the above-described embodiment will be described. The software management function unit 51 of the digital broadcast receiver 10 and the terminal device 50 communicates with each other via the network 90, and the digital broadcast receiver 10 newly adds the PC software extracted from the broadcast signal to the terminal device 50. Add as new PC software.

  FIG. 7 shows that a digital broadcast receiver 10 receives a broadcast program in which PC software and a data broadcast application for controlling the addition of PC software (hereinafter also referred to as “registration data broadcast application”) are multiplexed. 3 is a flowchart showing a series of procedures from when the registration data broadcasting application is executed until the PC software is installed in the terminal device 50. In this procedure, the digital broadcast receiver 10 and the software management function unit 51 of the terminal device 50 operate by communicating with each other via the network 90. In FIG. 7, control requests and responses communicated between the digital broadcast receiver 10 and the terminal device 50 are indicated by broken line arrows. The operation procedure shown in FIG.

  Step S105: The broadcast receiving unit 11 of the digital broadcast receiver 10 multiplexes the PC software providing the function X and the registration data broadcasting application for adding the PC software having the function X to the PC on the network. Broadcast programs are received by digital broadcast signals. When the broadcast receiving unit 11 acquires the PC software and the descriptor from the received digital broadcast signal, the broadcast receiving unit 11 outputs the PC software and the arb-dc: name space and accompanying information of the PC software to the storage unit 12. The accompanying information includes the function type and name of the PC software acquired from the descriptor. Further, the broadcast receiving unit 11 acquires a registration data broadcast application from the received digital broadcast signal and outputs the registration data broadcast application to the data broadcast execution unit 13.

  Step S110: The storage unit 12 of the digital broadcast receiver 10 stores the PC software output from the broadcast reception unit 11, the specific information of the PC software, the storage position, and the accompanying information in the storage unit 12.

  Step S115: The application execution unit 131 of the digital broadcast receiver 10 activates and executes the registration data broadcast application output from the broadcast reception unit 11. The application execution unit 131 performs the following operations by executing the registration data broadcast application program.

  Step S120: The application execution unit 131 uses the home network device use function of the network device use unit 132 to search for a software management function on the network 90. The network device using unit 132 transmits a search packet (M1) for the software management function to the network 90 for searching.

  Step S125: The software management function announcement unit 53 provided in the software management function unit 51 of the terminal device 50 receives the search packet transmitted by the search in step S120 and knows that the software management function is being searched. The software management function announcement unit 53 returns a response (M2) to the search to the digital broadcast receiver 10.

  Step S130: If the network device utilization unit 132 has not received a response to the search packet (M1), the process proceeds to step S185 (step S130: NO), and if the response (M2) is received, the process proceeds to step S135. (Step S130: YES).

  Step S135: Upon receiving the response (M2) to the search packet (M1) transmitted in step S120, the application execution unit 131 requests the terminal device software list acquisition unit 14 for a list of PC software that can be currently provided. . The terminal device software list acquisition unit 14 reads a list of PC software function types, PC software identification information, and the like from the storage unit 12 and returns the list to the application execution unit 131. When the application execution unit 131 determines that the read list includes the function type indicating the function X, the software management function acquires the list of installed PC software from the discovered terminal device 50. The controller 15 is instructed. The list acquisition unit 151 of the software management function control unit 15 currently manages the software management function unit 51 of the terminal device 50 that is the transmission source of the response (M2) by the software management function, and uses the network device. A PC software information list acquisition request (M3) is transmitted in order to acquire PC software information that can be linked by function.

  Step S140: The added software list notifying unit 54 provided in the software management function unit 51 of the terminal device 50 receives the list acquisition request (M3) transmitted by the digital broadcast receiver 10 in Step S135 and is stored in the storage unit 55. Based on the installed PC software information, the added PC software list (M4) is returned to the terminal device 50 as a response. This PC software list includes the UUID and function type information acquired from the installed PC software information.

  Step S145: Upon obtaining the list (M4), the terminal device software list acquisition unit 14 of the digital broadcast receiver 10 outputs the list (M4) to the application execution unit 131. The application execution unit 131 checks whether or not the PC software having the function X already exists depending on whether or not the function type representing the function X is included in the received list. If it is determined that it already exists, the process proceeds to step S185 (step S145: YES), and if it is determined that it does not exist yet, the process proceeds to step S150 (step S145: NO).

  Step S150: As a result of Step S145, when there is no software having the function X in the software managed by the software management function unit 51 of the terminal device 50, the application execution unit 131 specifies the PC software corresponding to the function X. The information and the URL for acquisition (“http: //...” Or “ftp: //...”) Are output to the file providing unit 16, and the other device functions X via the network 90. It is instructed to be able to acquire PC software having The file providing unit 16 uses, as a resource, an execution file of the PC software having the function X by using the arib-dc: name space described in the received PC software identification information or an identifier specified at the time of separate storage. Read from the storage unit 12. For example, when the file providing unit 16 starts functioning as an http server or an ftp server and receives a PC software acquisition request via the network 90, the file providing unit 16 loads the PC software that is a resource read from the storage unit 12. Prepare so that it can be sent to the sender of the acquisition request.

  Step S155: The application execution unit 131 controls the software management function provided by the terminal device 50 connected to the network 90 by the software addition instruction unit 152 included in the software management function control unit 15. That is, the software addition instruction unit 152 transmits a new PC software addition request (M5) having the function X to the software management function unit 51 of the terminal device 50. The addition request transmitted to the software management function unit 51 of the terminal device 50 includes information for acquiring PC software to be added, a UUID that is a unique ID of the PC software to be added, and a function type Contains information. The information for acquiring the PC software is link information for acquiring the PC software provided by the file providing unit 16, and “http: //” and the information received from the application execution unit 131 in step S150. URL information represented by “ftp: //” is used. Information such as the name of the PC software may be included in the addition request, and the terminal device 50 may issue and manage the UUID itself without including the UUID in the addition request.

  Step S160: The software addition / deletion unit 56 included in the software management function unit 51 of the terminal device 50 receives the software addition request (M5). The software addition / deletion unit 56 executes an operation for adding PC software according to the addition request (M5). First, when the software adding / deleting unit 56 reads the URL of the PC software to be added from the received addition request, the software adding / deleting unit 56 uses this URL to access the digital broadcast receiver 10 and acquire the PC software. An acquisition request (M6) is transmitted.

  Step S165: When the file providing unit 16 of the digital broadcast receiver 10 receives the PC software acquisition request (M6) destined for the URL specified by the addition request (M5) from the software management function unit 51 of the terminal device 50. The PC software prepared for provision in step S150 is transmitted as an execution file (M7) via the network 90.

  Step S170: The software addition / deletion unit 56 of the terminal device 50 transmits the PC software (M7) having the function X from the digital broadcast receiver 10 as a result of transmitting the execution file acquisition request (M6) transmitted in Step S160. If received, the received PC software is installed in the terminal device 50.

  Step S175: The storage unit 55 included in the software management function unit 51 of the terminal device 50 accumulates information on the newly added PC software as installed PC software information. The installed PC software information includes at least the UUID and function type information of the PC software received in step S155. Note that the name of the PC software received in step S155 may be set as the installed PC software information. If no UUID is received in step S155, the terminal device 50 issues a unique UUID. And may be accumulated.

  Step S180: The software addition / deletion unit 56 included in the software management function unit 51 of the terminal device 50 responds to the addition request (M5) in order to notify the digital broadcast receiver 10 that the new PC software has been correctly added. A success response (M8) is returned.

  Step S185: The application execution unit 131 of the digital broadcast receiver 10 ends the execution of the data broadcast application. When the application execution unit 131 receives the success response (M8) for software addition from the software management function unit 51 of the terminal device 50, or when the operation is not normally terminated due to some error, You may complete | finish, after displaying on the television screen which the output device 30 is displaying.

In the above procedure, the function type of the PC software is transmitted to the terminal device 50 together with the link information in step S155. In step S165, the function type of the PC software is transmitted to the terminal device 50 together with the execution file of the PC software. You may send it.
In step S140, the added software list notifying unit 54 of the terminal device 50 may return only the UUID of the PC software to the added PC software list (M4). By associating and storing the UUID and the function type in the digital broadcast receiver 10, in step S145, the application execution unit 131 corresponds to the UUID described in the received PC software list (M4). The function type is read from the storage unit 12, and it can be determined whether or not PC software having the function X exists.
Further, when the PC software added in the terminal device 50 is activated, the function type may be written in the installed PC software information in the storage unit 55 by a process executed by the PC software.

  After the PC software added to the terminal device 50 by the above procedure is added, the application execution unit 131 of the digital broadcast receiver 10 receives and executes the data broadcast application linked with the PC software by the digital broadcast signal. By doing so, the data broadcasting application and the PC software added to the terminal device 50 operate in cooperation.

  Next, a specific example of a Java (registered trademark) class for enabling each functional unit to be used when the digital broadcast receiver 10 is compatible with the ARIB-J system will be described. A class defines methods and attributes. When a class is instantiated, an object is generated, a memory is allocated, and each method is executed.

  FIG. 8 and FIG. 9 are diagrams showing an outline of the function of the ExAppsDatabase class, which is a Java (registered trademark) class for making it possible to use the terminal device software list acquisition unit 14 from a data broadcasting application in Javadoc format. . The ExAppsDatabase class is a PC software list management class for managing currently available PC software, and includes the following methods as APIs as shown in FIG.

getAppsDatabase () is an extended application database instance return method that returns a single instance of the ExAppsDatabase object.
getExAppAttibutes () is a software information list acquisition method for acquiring information about PC software that can be currently provided as an enumeration of ExAppAttributes. With this method, the function type of the PC software is acquired and returned.
getExAppAttributes (org.dvb.application.AppID key) is a specified software information acquisition method, and acquires a class in which information about PC software having an identifier specified as (org.dvb.application.AppID) is held. . AppID is used for this identifier.
getExAppIDs () is a software identifier acquisition method for acquiring identifiers of PC software that can be currently provided as an AppID enumeration.
reload () is a reload method that reloads information and brings it to the latest state.
size () is a software number acquisition method that returns the number of PC software that can be currently provided.

  In the ExAppsDatabase class described above, an interface of a class called ExAppAttributes is used internally in order to acquire information about PC software. This class acquires data included in digital broadcasting. That is, information stored as PC software identification information and related information in the storage unit 12 is acquired from a digital broadcast signal by a method of this ExAppsDatabase class.

FIG. 10 is a diagram illustrating an example of the ExAppAttributes class. As shown in the figure, the ExAppAttributes class includes the following methods as APIs.
getIdentifier () is a software acquisition method for acquiring the identifier of the PC software as an AppID composed of the descriptor organization_id and external_application_id shown in FIG.
getJarURL () is a JAR software storage location acquisition method for acquiring the URL of a Jar file when the PC software is distributed in the Jar execution format.
getJnlpURL () is a JNLP software storage location acquisition method for acquiring the URL of a JNLP (Java Network Launching Protocol) file when installing PC software using the Java (registered trademark) Web Start mechanism.
getName () is a PC software name acquisition method for acquiring the name of the PC software from the descriptor shown in FIG.
getVendor () is a vendor acquisition method for acquiring information about the vendor that created the PC software from the descriptor shown in FIG.
getFunction () is a function acquisition method for acquiring the function type of the PC software from the descriptor shown in FIG.

  FIG. 11 shows a Java (registered trademark) interface implemented by the software management function control unit 15 so that the software management function provided by the software management function unit 51 of the terminal device 50 on the network can be controlled from the data broadcasting application. An outline of the function of a certain ExAppManagerProxy is shown in Javadoc format.

Control by the API of the ExAppManagerProxy interface is converted into a device cooperation protocol such as UPnP via the network. Therefore, the API of the ExAppManagerProxy interface has a function equivalent to the UPnP action included in the software management function unit 51 of the terminal device 50.
As shown in FIG. 11, the ExAppManagerProxy class is a control class that controls the software management function on the home network via the network 90, and includes the following methods as APIs.

delete (java.lang.String uuid) specifies a UUID that is an ID uniquely assigned to the PC software, and uses a software management function provided by the terminal device 50 to implement the PC installed in the terminal device 50 This is a software deletion method that deletes software. If successful, a return value of 0 is returned.
deploy (ExAppAttributes attributs, java.lang.String uuid) is a software addition method for adding new PC software to the terminal device 50 using the software management function provided by the software management function unit 51 of the terminal device 50. . As new PC software, information of ExAppAttributes (a class that holds information about PC software) and a UUID that is a unique ID in the String format are specified and added. If successful, a return value of 0 is returned.
getAppList () is a software list acquisition method that returns a list of PC software currently managed by the software management function provided by the terminal device 50. The return value is a String format in which a set of UUIDs and function types of a plurality of software is separated by a delimiter such as “;”.

  getAppList () implements a list acquisition unit 151, and delete (java.lang.String uuid) and deploy (ExAppAttributes attributs, java.lang.String uuid) implement a software addition instruction unit 152.

  FIG. 12 and FIG. 13 show an outline of the function of the LocalWebServer (local web server) class, which is a Java (registered trademark) class, for enabling the file providing unit 16 to be used from the data broadcasting application in the Javadoc format. As shown in the figure, the LocalWebServer class is a file providing class that provides a local web server function in the digital broadcast receiver 10, and includes the following methods as an API.

addResource (org.davic.net.Locator source_loc, java.lang.String get_url) is a resource addition method for adding a new resource to the web server. The resource in the source broadcast stream is specified by Locator, and the URL published on the local web server is specified by String as a relative path from the path of the web server root. Returns 0 if the resource was added successfully.
getLocalWebServer () is a local web server instance acquisition method that returns a single instance of the LocalWebServer object.
removeAllResources () is an all resource deletion method that deletes all resources from the web server, and returns 0 if the resource is successfully deleted.
removeResource (java.lang.String get_url) is a resource removal method that removes the specified resource from the web server, and removes the resource specified by the relative path from the web server root path. If the resource is deleted normally, 0 is returned.
run () is a web server start method for starting the operation of the web server.
stop () is a stop method for stopping the operation of the web server.

  By using the WebServer class, the Java (registered trademark) data broadcast application constructs a local HTTP server in the digital broadcast receiver 10 and provides specified resources by the HTTP protocol.

  The ExAppsDatabase class, the ExAppManagerProxy interface, and the LocalWebServer class described above are merely examples of implementation methods of the terminal device software list acquisition unit 14, the software management function control unit 15, and the file provision unit 16, and realize equivalent functions. Another class configuration can be used.

  14 and 15 are diagrams illustrating an example of an SCPD (Service Control Protocol Declaration) file when the software management function unit 51 of the terminal device 50 is realized by UPnP. In the SCPD file, a UPnP action that is a function called from a remote device by UPnP, an input argument thereof, and a return value are defined. In the figure, UPnP actions shown for realizing the added software list notifying unit 54 and the software adding / deleting unit 56 shown in FIG. 5 are described.

Among the functions of the software addition / deletion unit 56, the function of installing new PC software in the terminal device 50 is the Deploy action shown in FIG. 14, and the function of uninstalling installed PC software is shown in FIG. Implemented as the Delete action shown.
In the Deploy action, a URL (Url) for acquiring the PC software to be added, a UUID (Uuid) that is a unique ID of the PC software, and a function type (Function) are specified, and the specified URL Obtain and install the PC software executable from If the Deploy action can be executed normally, for example, “0” is returned as Result. The storage unit 55 holds the Id of the PC software added by the Deploy action.
In the Delete action, the UUID (Uuid) of the software to be deleted is specified, and the software specified by the specified UUID (Uuid) is deleted. If the Delete action can be executed normally, for example, “0” is returned as Result.

  The added software list notification unit 54 is realized as a GetAppList action shown in FIG. The GetAppList action is called without an argument, and the return value AppList returns a list of combinations of the UUID (Uuid) and function type of the PC software managed by the software management function unit 51 as a character string, and the return value Num Return the number of PC software returned in the list.

  The UPnP action described above is merely an example, and may be another UPnP action for realizing an equivalent function.

  FIG. 16 to FIG. 18 show, as a specific example of the procedure of FIG. 7, each function unit of the digital broadcast receiver 10 as the native function and Java (registered trademark) class of the digital broadcast receiver 10 by the ARIB-J data broadcast application. When implemented, an operation sequence when the software management function unit 51 of the terminal device 50 is further implemented as a UPnP service provided in the UPnP device is shown. FIGS. 16 to 18 actually use the APIs and UPnP actions of the Java (registered trademark) classes of FIGS. 8 to 13 and the UPnP service definition examples of FIGS. 14 and 15. An example of the operation is shown.

  The receiver native function and DeviceManager are functions implemented in the existing digital broadcast receiver 10. The receiver native function is realized by the broadcast receiving unit 11 and the storage unit 12. The ARIB-J data broadcast application is executed by the application execution unit 131. DeviceManager, which is an ARIB-J network device usage class, is realized by the network device usage unit 132 and manages various devices. The API of DeviceManager is defined by ARIB-J. The UPnP ExAppManager service, which is a software management function, is realized by the software management function unit 51 of the terminal device 50.

  Step S205: In FIG. 16, the receiver native function of the digital broadcast receiver 10 receives the digital broadcast signal broadcast from the broadcast station. The digital broadcast signal includes a PC software descriptor, a PC software execution file, and a registration application which is a registration ARIB-J data broadcast application for adding PC software. The registration application may be transmitted by digital signals broadcast at different times.

  Step S210: When the receiver native function of the digital broadcast receiver 10 acquires the PC software and the descriptor from the digital broadcast signal, the PC software arib-dc that can be solved by the descriptor: name space, PC software, storage The storage position and descriptor of the PC software in the unit 12 are associated and written to the storage unit 12. The descriptor is used as related information, and includes the function type and name of the PC software, an application identifier, and the like.

Step S215: The receiver native function of the digital broadcast receiver 10 acquires and activates a registration application from the digital broadcast signal.
Step S220: The activated registration application calls getDeviceManager () to request acquisition of an instance of the network device usage class.
Step S225: The DeviceManager returns the instance to the registration application as a return value of getDeviceManager (). As a result, the registration application can use the DeviceManager object.

Step S230: The registration application calls searchDevice () of DeviceManager and requests UPnP ExAppManager to search for the software management function.
Step S235: The DeviceManager transmits UPnP M-search which is a UPnP search packet in order to search the network 90 for the UPnP ExAppManager service.
Step S240: Upon receiving the UPnP search packet, the UPnP ExAppManager service implemented as the software management function unit 51 of the terminal device 50 returns SSDP Alive and notifies its existence.

Step S245: Upon receiving SSDP Alive, the DeviceManager determines that an available UPnP ExAppManager service exists on the network 90, and calls new ExAppManagerProxy to generate a control class in order to prepare for control of the software management function. .
Step S250: The ExAppManagerProxy generates an instance and returns it to the DeviceManager. As a result, the registration application can use the ExAppManagerProxy object.
Step S255: DeviceManager returns deviceAdded (ExAppManagerProxy) to the registration application and notifies that the software management function has been found.

Step S260: In order to confirm whether the PC software to be registered can be actually registered, the registration application first calls getAppsDatabase () of ExAppsDatabase and requests acquisition of the PC software list management class.
Step S265: ExAppsDatabase returns a single instance to the registration application as a return value. As a result, the registration application can use ExAppsDatabase, which is a PC software list management class.
Step S270: The registration application executes getExAppAttributes () of ExAppsDatabase to request acquisition of a list of PC software that can be provided.
Step S275: ExAppsDatabase reads all the descriptors stored in the storage unit 12.
Step S280: The ExAppsDatabase returns, as a return value, an Enumeration that is a list in which each descriptor read in Step S275 is enumerated as ExAppAttributes.

Step S305: In FIG. 17, when the registration application determines from the returned list that the function X of the PC software to be registered is included, it executes getAppList () of ExAppManagerProxy, and the software management function Requests acquisition of a list of PC software managed by. It is described in advance in the registration application that the function X is a function of the PC software to be added.
Step S310: The ExAppManagerProxy executes GetAppList () and calls a UPnP action for acquiring the PC software list.
Step S315: When the UPnP ExAppManager service implemented by the software management function unit 51 of the terminal device 50 is called a UPnP action for acquiring a PC software list, the UUID is determined from the installed PC software information stored in the storage unit 55. And a combination of function types as a list, and a return value in which the character string of the read list and the number of elements that are the number of UUIDs and function types included in the list are set is returned.
Step S320: Upon receiving the return value from the UPnP ExAppManager service, the ExAppManagerProxy returns the list character string (String) included in the return value to the registration application as the return value of getAppList.

Step S325: The registration application determines whether a function type indicating the function X of the PC software to be added is included in the returned list.
Step S330: The registration application executes deploy (attributes, uuid_X) of ExAppManagerProxy and specifies the addition of PC software by specifying the UUID (uuid_X) of the PC software to be registered. The UUID is assigned in the registration application. The attributes is a class ExAppAtttibutes that holds various types of information about the PC software for the function X, and includes information that the function type is the function X.

Step S335: The ExAppManagerProxy reads a path indicating the storage location of the PC software stored in the storage unit 12 corresponding to the AppID included in attributes (ExAppAttributes class) as source_loc.
Step S340: ExAppManagerProxy calls getLocalWebServer () of LocalWebServer and requests acquisition of a file providing class.
Step S345: The LocalWebServer returns a single instance as a return value. As a result, ExAppManagerProxy can use LocalWebServer.

Step S350: The ExAppManagerProxy calls addResource (source_loc, get_url) of LocalWebServer and requests the LocalWebServer to add a resource for the PC software. source_loc is an arib-dc: namespace locator acquired in step S335. Get_url is a URL provided by LocalWebServer determined by ExAppManagerProxy.
Step S355: When addResource (source_loc, get_url) is called, LocalWebServer returns a return value indicating a successful response.

Step S405: In FIG. 18, the ExAppManagerProxy executes the UPnP action Deploy (get_url, uuid, function) and calls the software addition UPnP action. get_url is the value specified in step S350, and uuid is the value specified in step S330. Further, function can be acquired by attributes.getFunction () in the attributes (ExAppAttributes class) specified in step S330.
Step S410: When the UPnP ExAppManager service implemented by the software management function unit 51 of the terminal device 50 is called Deploy (get_url, uuid, function), HTTP is sent to the LocalWebServer of the digital broadcast receiver 10 using the get_url argument as an access destination. Send GET.

Step S415: The LocalWebServer reads PC software, which is an execution file, from the storage unit 12 using source_loc corresponding to the specified get_url.
Step S420: LocalWebServer returns HTTP 200 OK and the PC software read in step S350 to the UPnP ExAppManager service.
Step S425: The UPnP ExAppManager service installs the received PC software on the terminal device 50.
Step S430: Further, the UPnP ExAppManager service writes the installed software information including the UUID and function type of the installed PC software in the storage unit 55.
Step S435: The UPnP ExAppManager service returns success of Deploy () when the installation is completed.

Step S440: Upon receiving success of Deploy (), ExAppManagerProxy calls LocalWebServer's Stop () to stop LocalWebServer.
Step S445: The ExAppManagerProxy returns a return value indicating a Deploy success response to the registration application as a return value of deploy (attributes, uuid_X) called in Step S310.
Steps S450 to S460: Upon receiving a Deploy success response, the registration application executes storyXlet (), and ends the execution of ExAppManagerProxy, DeviceManager, and the registration application.

[Second Embodiment]
In the second embodiment of the present invention, the function of the software management function unit 51 of the terminal device 50 shown in FIG. 5 of the first embodiment is expanded, and a function for starting software is added. Therefore, the procedure in which the digital broadcast receiver 10 receives the PC software by broadcasting and adds it as new software to the terminal device 50 is the same as in the first embodiment. Hereinafter, a difference function and procedure from the first embodiment will be described.

  FIG. 19 is a block diagram illustrating a functional configuration of the software management function unit 51a included in the terminal device 50 according to the second embodiment. In this figure, the same parts as those of the software management function unit 51 shown in FIG. 5 of the first embodiment are denoted by the same reference numerals, and the description thereof is omitted. The software management function unit 51a shown in this figure is different from the software management function unit 51 of the first embodiment in that a software activation unit 57 is provided.

  The software activation unit 57 has a function of activating the PC software managed by the software management function unit 51a. As an execution format of PC software that operates on the terminal device 50, for example, in the case of an exe format that is a native application that operates on a Windows (registered trademark) personal computer, a class file format executed by JavaVM, a jar execution format, Although there are cases, it corresponds to the execution format of the PC software transmitted by the digital broadcast signal.

  FIG. 20 shows the definition of the UPnP action that is the difference from FIGS. 14 and 13 when the software management function unit 51a according to the present embodiment shown in FIG. 19 is realized by UPnP. The Launch action shown in the figure is an interface for specifying the UUID of the PC software and starting the PC software. This example of action is merely an example of the realization means, and may be another UPnP action that realizes an equivalent function for specifying and starting up the PC software by another designation method other than the UUID.

  With the above configuration, the digital broadcast receiver 10 and the software management function unit 51a of the terminal device 50 communicate with each other via the network 90, and the digital broadcast receiver 10 stores the PC software extracted from the broadcast signal in the terminal device 50. In addition, the PC software is automatically activated under the control of the data broadcasting application. The procedure is shown in FIG.

  FIG. 21 shows that after the digital broadcast receiver 10 receives a broadcast program in which the PC software and the registration data broadcast application are multiplexed, the PC software is installed in the terminal device 50 under the control of the registration data broadcast application. FIG. 6 is a flowchart showing a series of procedures from when the PC software is automatically activated under the control of the registration data broadcast application until the registration data broadcast application and the PC software operate in cooperation with each other. In the figure, control requests and responses communicated between the digital broadcast receiver 10 and the terminal device 50 are indicated by broken line arrows. Hereinafter, the operation procedure shown in FIG. 21 will be described focusing on the difference from the operation procedure shown in FIG.

  The registration data broadcast application in this operation procedure not only controls the addition of PC software as in the registration data broadcast application described in the first embodiment, but also has a function X by a network device utilization function. By linking with software, some services can be executed at the same time. If the PC software having the function X already exists, the cooperative operation is performed. If the PC software having the function X does not exist, the PC software having the function X is newly obtained using the software management function. The software is added to the device 50, and the added software is automatically activated to perform a cooperative operation.

  Steps S505 to S515: The same as steps S105 to S115 of the first embodiment shown in FIG.

Step S520: The home network device use function of the network device use unit 132 of the digital broadcast receiver 10 is used to search whether the PC software having the function X to be linked exists on the home network. For example, the network device using unit 132 transmits a function X search packet (M9) to the network 90 for search. When the PC software having the function X is not installed, the added software list notifying unit 54 of the terminal device 50 does not return a response.

  Step S525: When receiving a response to the function X search packet (M9), the data broadcast execution unit 13 proceeds to step S620 (step S525: YES). If no response is received, the process proceeds to step S530 (step S525: NO).

  Steps S530 to S590: When no response to the function X search packet (M9) is received in step S525, the same processing as in steps S120 to S180 of the first embodiment shown in FIG. 7 is performed. The software addition / deletion unit 56 included in the software management function unit 51a of the terminal device 50 returns a response indicating failure in step S590 when the PC software is not correctly added.

  Step S595: The application execution unit 131 of the digital broadcast receiver 10 receives the software addition response (M8) returned from the software management function unit 51a of the terminal device 50. If a response indicating that the addition has failed is received, the process proceeds to step S630 (step S595: NO). If a response indicating that the addition is successful is received, the process proceeds to step S600 (step S595: YES).

  Step S600: The application execution unit 131 uses the software management function control unit 15 to control the software management function unit 51a included in the terminal device 50 connected to the network 90. The software management function control unit 15 transmits a PC software activation request (M10) having the function X to the software management function unit 51a of the terminal device 50. The activation request (M10) includes at least the UUID of the PC software to be activated. For example, the activation request (M10) is a unique ID transmitted together with the function type by the PC software addition request (M5) transmitted in step S465. A UUID_X is set. After transmitting the PC software activation request, the software management function control unit 15 transitions again to step S520 after a predetermined time has elapsed.

  Step S605: When the software activation unit 57 included in the software management function unit 51a of the terminal device 50 receives the software activation request (M10), it is installed in the terminal device 50 in order to activate the specified UUID_X PC software. The activation control of the PC software is performed.

  Step S610: The software activation unit 57 included in the software management function unit 51a of the terminal device 50 activates the PC software whose UUID is UUID_X. The PC software has a function X, and provides a function that can be controlled via the network 90 by the network device cooperation function of the digital broadcast receiver 10.

  Step S615: After step S600, the digital broadcast receiver 10 executes step S620 again, and the terminal device 50 receives the function X search packet (M9) from the digital broadcast receiver 10. The software activation unit 57 returns a response (M11) because the PC software that has been linked with the data broadcasting application and has the function X has already been activated by the procedure of Steps S600 to S610 described above. The digital broadcast receiver 10 receives the response (M11) (step S525: YES), and transitions to step S520.

  Step S620: The network device utilization unit 132 of the digital broadcast receiver 10 links the registration data broadcast application executed in the application execution unit 131 and the PC software activated in the terminal device 50 via the network 90. To do. That is, according to an instruction from the application execution unit 131, the network device utilization unit 132 requests the terminal device 50 to execute the function X (M12), and in some cases, receives the execution result (M13). This process is repeated as necessary. When all the processes are completed, or when the user gives an instruction to end the registration data broadcasting application, the process proceeds to step S630.

  Step S625: In response to the request (M12) output from the network device using unit 132 of the digital broadcast receiver 10, the PC software performs the operation of the function X and returns a response (M13) as necessary. The operation performed by the function X is not limited to one, and M12 and M13 are different for each requested operation.

  Step S630: The data broadcast execution unit 13 of the digital broadcast receiver 10 ends the execution of the registration data broadcast application. It should be noted that the registration data broadcast application receives a response to the successful addition of the software from the software management function (step S595: NO), or when the operation is not normally terminated due to some error, on the TV screen. You may end after displaying the result to that.

  The digital broadcast receiver 10 and the terminal device 50 described above have a computer system inside. The data broadcast execution unit 13 of the digital broadcast receiver 10, the terminal device software list acquisition unit 14, the software management function control unit 15, the file providing unit 16, the network control information transmission / reception unit 17, and the terminal device 50 The operation process of the software management function announcement unit 53, added software list notification unit 54, software addition / deletion unit 56, and software activation unit 57 is stored in a computer-readable recording medium in the form of a program. Is read out and executed by the computer system to perform the above processing. The computer system here includes a CPU, various memories, an OS, and hardware such as peripheral devices.

Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, the “computer-readable recording medium” dynamically holds a program for a short time like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory in a computer system serving as a server or a client in that case, and a program that holds a program for a certain period of time are also included. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

DESCRIPTION OF SYMBOLS 10 ... Digital broadcast receiver 11 ... Broadcast receiving part 12 ... Memory | storage part 13 ... Data broadcast execution part 131 ... Application execution part 132 ... Network equipment utilization part 14 ... Software list acquisition part 15 for terminal devices ... Software management function control part 151 ... List acquisition unit 152 ... software addition instruction unit 16 ... file providing unit 17 ... network control information transmission / reception unit 30 ... output device 50 ... terminal device 51, 51a ... software management function unit 52 ... network control information transmission / reception unit 53 ... software management function announcement Unit 54 ... added software list notification unit 55 ... storage unit 56 ... software addition / deletion unit 57 ... software activation unit 90 ... network

Claims (11)

A storage unit for storing a terminal device program that operates in cooperation with a broadcast application program;
The digital broadcast signal is received from the digital broadcast signal, and the registration program for registering the terminal device program in an external terminal device connected via a network is received from the digital broadcast signal. A broadcast receiving unit that is acquired on the basis of information multiplexed on the terminal device and writes the terminal device program and identification information in the storage unit in association with each other,
A data broadcast execution unit that outputs a transmission instruction that sets identification information of the terminal device program to be registered in the terminal device by executing the registration program;
A file providing unit that reads the terminal device program corresponding to the identification information included in the transmission instruction output from the data broadcast execution unit from the storage unit and transmits the program to the terminal device;
A digital broadcast receiver comprising: A list acquisition unit for acquiring information on the terminal device program registered in the terminal device from the terminal device;
The program execution unit outputs the transmission instruction in which identification information of the unregistered terminal device program is set based on the information of the terminal device program acquired by the list acquisition unit.
The digital broadcast receiver according to claim 1. The digital broadcast receiver according to claim 2, wherein the information on the registered terminal device program acquired by the list acquisition unit includes information on the function of the terminal device program. The broadcast receiving unit obtains function information of the terminal device program from the signal, writes the function information and identification information of the terminal device program in the storage unit,
The data broadcast execution unit acquires the identification information of the terminal device program from the terminal device as information of the registered terminal device program, and reads the function from the storage unit corresponding to the acquired identification information If it is determined that the function of the program for the terminal device to be registered is not registered in the terminal device based on the information, the transmission instruction is output.
The digital broadcast receiver according to claim 2. The broadcast receiving unit acquires information on the function of the terminal device program from the signal and writes the information to the storage unit,
The data broadcast execution unit outputs the transmission instruction when it is determined that the function information of the terminal device program to be registered is stored in the storage unit.
The digital broadcast receiver according to any one of claims 1 to 4, wherein the digital broadcast receiver is provided. A software addition instruction unit that receives the transmission instruction from the data broadcast execution unit and transmits an instruction to add the terminal device program to be registered to the terminal device;
The file providing unit reads the terminal device program corresponding to the identification information included in the transmission instruction from the storage unit in response to an acquisition request for the terminal device program received from the terminal device. Send to
The digital broadcast receiver according to any one of claims 1 to 5, wherein the digital broadcast receiver is provided. The broadcast receiving unit is obtained from the received digital broadcast signal broadcast application program to cooperate with the terminal device program,
The data broadcast execution unit instructs the terminal device to execute the terminal device program by executing the acquired broadcast application program.
The digital broadcast receiver according to claim 1, wherein the digital broadcast receiver is a digital broadcast receiver. A storage unit for storing information of a program for a terminal device operating in cooperation with a broadcast application program;
The terminal device program and the terminal device program information are received from a digital broadcast receiver connected via a network, the received terminal device program is registered, and the received terminal device program A software addition unit for writing information to the storage unit;
Receiving a transmission request of the terminal device program list from the digital broadcast receiver, reading out the information of the terminal device program from the storage unit and returning the information, and an added software list notification unit;
A terminal device comprising: The terminal device program information is at least one of function information of the terminal device program or identification information of the terminal device program.
The terminal device according to claim 8. Computers used in digital broadcast receivers
A storage unit for storing a terminal device program that operates in cooperation with a broadcast application program;
The digital broadcast signal is received from the digital broadcast signal, and the registration program for registering the terminal device program in an external terminal device connected via a network is received from the digital broadcast signal. A broadcast receiving unit that is acquired on the basis of information multiplexed on the terminal device and writes the terminal device program and identification information in the storage unit in association with each other,
A data broadcast execution unit that outputs a transmission instruction that sets identification information of the terminal device program to be registered in the terminal device by executing the registration program;
A file providing unit that reads the terminal device program corresponding to the identification information included in the transmission instruction output from the data broadcast execution unit from the storage unit and transmits the program to the terminal device;
A computer program that functions as a computer program. The computer used for the terminal device
A storage unit for storing information of a program for a terminal device operating in cooperation with a broadcast application program;
The terminal device program and the terminal device program information are received from a digital broadcast receiver connected via a network, the received terminal device program is registered, and the received terminal device program A software addition unit for writing information to the storage unit;
An added software list notification unit that receives a transmission request for the terminal device program list from the digital broadcast receiver, reads out the information of the terminal device program from the storage unit, and returns the information.
A computer program that functions as a computer program.

Images