JP6018797B2 - Receiving machine - Google Patents

Description

  The present invention relates to a receiver.

  Conventionally, a broadcasting / communication cooperation system in which broadcasting and communication are linked is known (for example, see Non-Patent Document 1).

“Application Execution Environment for Digital Broadcasting Standards APPLICATION EXECUTION ENGINE PLATFORM FOR DIGITAL BROADCASTING”, The Japan Radio Industry Association, ARIB STD-B23 1.2 Edition, July 29, 2009

  In the broadcasting / communication cooperation system, since the receiver can store and execute an application acquired via a network, there is a problem that it is desired to accurately manage an application stored therein.

  The present invention has been made in view of such circumstances, and provides a receiver capable of accurately managing an application stored therein.

[1] According to one aspect of the present invention, an application storage unit that stores information related to an application program, an application execution unit that executes an application program read from the application storage unit, and the application execution unit that executes the application program wherein the method receiving unit that receives the requested Rume Sod, based on the inquiry method in cache in an application where the method accepting unit accepts, searches the application storage section, whether specified application exists a cache search unit returns to the application execution unit, based on the saving method to the method accepting unit accepts the application in the cache, requests the Save method application To obtain information about different other application programs and tio emission program, a receiver, characterized in that it comprises, an application acquisition unit for writing into the application storage unit. When the application program specified by the inquiry method does not exist in the application storage unit, the application execution unit requests the storage method specifying the application, and the application acquisition unit specifies the specified application program May be acquired and written to the application storage unit.

[2] One aspect of the present invention is the above-described receiver, wherein the method reception unit receives an application list information acquisition method in cache requested from the application execution unit by executing the application program, and the cache The internal search unit reads out the list information related to the application stored in the application storage unit based on the cached application list information acquisition method received by the method reception unit, and returns it to the application execution unit. Features.

  According to the present invention, it is possible to accurately manage an application stored therein.

It is a functional block diagram which shows the internal structure of the receiver by one Embodiment of this invention. It is a figure which shows the person using the broadcast communication cooperation system to which this invention is applied, and its relationship. It is a figure which shows the whole structure of a broadcast communication cooperation system. It is a figure which shows the terminal cooperation model of a broadcast communication cooperation system. The conceptual diagram of the service classification of a broadcast communication cooperation system is shown. It is a figure which shows the example of the text expression of AIT used for a broadcast communication cooperation system. It is a figure which shows the life cycle of the application in a broadcast communication cooperation system. It is a figure which shows the data flow between providers in a broadcast communication cooperation system. It is a figure which shows the flow of the data in the whole broadcast communication cooperation system. It is a figure which shows the sequence of the recommendation service in a broadcast communication cooperation system. It is a figure which shows the transfer protocol stack in a broadcast communication cooperation system. It is a figure which shows the application management model in a broadcast communication cooperation system. The functional model of the secure manager in the broadcasting / communication cooperation system is shown. It is a figure which shows the concept of the screen presentation control system in a broadcast communication cooperation system. It is a figure which shows the basic operation | movement model of the screen presentation control in a broadcast communication cooperation system. The example of the screen presentation control according to the policy level in a broadcast communication cooperation system is shown. The example of the presentation control at the time of the earthquake early warning reception in a broadcast communication cooperation system is shown. 1 is an overall configuration diagram of a broadcasting / communication cooperation system according to an embodiment of the present invention. It is a functional block diagram which shows the internal structure of the receiver by the embodiment. It is a block diagram which shows the detailed structure of the application execution control part by the embodiment. It is a block diagram which shows the detailed structure of the presentation control part by the embodiment. FIG. 22 shows a configuration and data example of information stored in the application storage unit shown in FIG. 3 is a flowchart illustrating an example of operation of the receiver illustrated in FIG. 1.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a functional block diagram showing an internal configuration of a receiver according to an embodiment of the present invention. As shown in FIG. 1, the receiver 4 according to an embodiment of the present invention includes a communication input / output unit 411 and an application execution control unit 412. The application execution control unit 412 includes an application control unit 434, an application storage unit 431, and an application execution unit 435. The application control unit 434 includes a method reception unit 501, an application acquisition unit 520, and a cache search unit 570.

[Description of Broadcast and Communication Cooperation System to which the Present Invention is Applied]
Here, a broadcasting / communication cooperation system to which the present invention is applied will be described. The broadcast communication cooperation system (broadcast communication integration system, broadcast communication system, transmission / reception system) to which the present invention is applied is, for example, a Hybridcast (registered trademark) (hybrid cast) system, and a broadcast communication cooperation service (Hybridcast (registered trademark)). Service, broadcasting / communication integration service, broadcasting / communication service). The broadcasting / communication cooperation service realized by the broadcasting / communication cooperation system to which the present invention is applied links a digital broadcasting service and a communication service using the Internet or the like. For example, in a broadcasting / communication cooperation service, a receiver such as a digital television, a personal computer, or a portable terminal displays a display screen (hereinafter, “program display screen”) of a broadcast program (hereinafter also referred to as “program”) transmitted by broadcasting. (Also referred to as a “broadcast screen”), and a display screen of services and contents acquired by communication by the application installed in the receiver (hereinafter referred to as “application screen” and “application display screen”). ) And display simultaneously.

[1. System model]
[1.1 Users of the broadcasting / communication cooperation system]
FIG. 2 is a diagram showing a person who uses the broadcasting / communication cooperation system and its relationship.
A broadcasting station that sends a program accompanied by organization distributes the program to viewers by broadcast radio waves or a communication network. Broadcasting stations provide service providers with metadata related to programs in order to enhance broadcast communication cooperation services.

  A service provider that provides a broadcasting / communication cooperation service produces and distributes content and an application (hereinafter also referred to as “app”) for providing the viewer with a broadcasting / communication cooperation service. Hereinafter, when simply described as “application”, it refers to an application for providing a broadcasting / communication cooperation service (an application of the broadcasting / communication cooperation service). The content or application producer and distributor need not be the same service provider. A broadcasting station may also serve as a service provider. The service provider can also provide link information to other service providers. The service provider can apply for registration of the application and obtain approval from the system administrator in order to indicate that the application to be provided is official. Approved applications are not restricted in operation on the receiver. On the other hand, a screen displayed by an unapproved application cannot overlap the program display screen and sound, but the application display screen can be reduced and displayed outside the broadcast program screen. An approved application is called an A (Authorized) application, and an unapproved application is called a general application. The A application is also referred to as an official application, a registered application, an authenticated application, an authorized application, an authorized application, an authorized application, or an A (Authorized) type application. The general application is also referred to as an unofficial application, an unauthenticated application, an unauthorized application, an unauthorized application, a U (Unauthorized) type application, or a U application.

  The system administrator is an organization that certifies that the application (receiver application) provided to the viewer is the A application (official). The system administrator's decision as to whether or not to approve the applied application depends on the commission from the broadcasting station.

  An application for performing various settings may be installed in the receiver. At this time, the display screen of the application in the receiver may overlap the display screen (video) of the program.

A viewer who views a program broadcast by a broadcasting station enjoys a broadcasting / communication cooperation service.
The viewer can download or start the application according to his / her will. Further, the viewer can overlap the display screen of the application with the display screen (video) of the program according to his / her intention.

[1.2 System configuration of broadcasting / communication cooperation system]
FIG. 3 is a diagram illustrating the overall configuration of the broadcast communication cooperation system. The broadcasting / communication cooperation system is configured by functionally adding a “broadcasting station server group”, a “service provider server group”, and a “receiver” to the current broadcasting station equipment using radio waves.

  The broadcasting station has broadcasting station facilities. Further, the broadcasting station configures and manages both the broadcasting station server group and the service provider server group. The service provider configures and manages a service provider server group. The system administrator manages and operates the repository server. The receiver manufacturer manufactures and sells the receiver. The viewer has a receiver and enjoys a broadcasting / communication cooperation service.

A receiver (Hybridcast (registered trademark) receiver, broadcast receiving communication device) is equipped with a standardized common API (Application Program Interface). Further, the receiver receives broadcasts of the current system such as terrestrial digital broadcast and BS (broadcasting satellite) digital broadcast.
The broadcasting station equipment multiplexes a signal for starting a broadcasting / communication cooperation service into a broadcasting wave. The multiplexing method will be described later.

[1.3 Configuration example of broadcast station server group]
The broadcasting station server group manages and distributes content and metadata held by broadcasting stations.
For example, the broadcast station server group includes various servers, a data storage unit (DB (database)), and an API, and the broadcast station server group includes a content management server, a viewer management server, a content distribution server, a broadcast A station service server is included.

  A content management server that manages content manages programs and metadata that are broadcast content. The content management server includes a program management server that manages a broadcast program or a broadcast program, and a metadata management server that manages metadata related to the program. The metadata indicates, for example, a program title, a program ID, a program summary, performers, staff, broadcast date and time, script, captions, and commentary.

  The viewer management server manages viewers (users), and the content distribution server distributes content data by communication. The broadcast station service server is a server for the broadcast station to provide a service to a service provider. Services provided by the broadcast station service server include, for example, a social network service operated by a broadcast station and a web log (blog) for each broadcast program.

  The data storage unit of the broadcast station server group includes a part for storing contents and metadata held by the broadcast station and a database. The stored data can be accessed only by the service provider that is managing it, and is restricted so that it cannot be accessed by others.

  The API of the broadcasting station server group is an API for providing data in response to a request from the service provider server group. The API is a program that an application calls to receive a service and its execution unit.

[1.4 Service provider server group configuration example]
A service server group managed and operated by a service provider manages and provides applications and contents. The service server group includes a receiver application server, a service server, a content distribution server, a data storage unit (DB (database)), and an API.

The receiver application server is a server that manages an application of the broadcasting / communication cooperation service. The service provider stores, manages, and distributes applications that operate on the receiver.
Service providers are composed of groups or individuals. In response to a request from the receiver, the receiver application server notifies the receiver of the storage location of the application file (the application file will be described later) and distributes the application file.

  The service server is a server that provides a service in response to a request from an application operating on the receiver. Examples of the service server include a multilingual subtitle server, a speech speed conversion voice server, a social TV server, a recommendation server, a program review server, and a bookmark server.

  The content distribution server is a server that provides content in response to a request from an application running on the receiver. Examples of the content distribution server include a VOD (Video On Demand) distribution server, a caption distribution server, and a multi-view distribution server.

  The data storage unit of the service provider server group is a place for storing content data, metadata, data created by the service provider, viewer data, and application files. The data stored in the data storage unit can be accessed only by the service provider that is managing it, and cannot be accessed by others.

  The API of the service server group is an API for providing application files, contents, and services in response to a request from an application running on the receiver.

[1.5 Receiver]
The receiver receives and displays the broadcast of the current system, and executes a broadcasting / communication cooperation service. Current broadcasting is satellite broadcasting such as terrestrial digital broadcasting and BS digital broadcasting, and data broadcasting. The receiver is connected to the Internet.

The receiver makes an application download request to the service provider server based on the information multiplexed on the received broadcast wave. When the receiver executes an application program included in the downloaded application file, the application operates on the receiver. An application operating on the receiver accesses the service provider server and acquires content.
Further, the receiver has a broadcasting / communication cooperation function which is a function necessary for executing a broadcasting / communication cooperation service such as a synchronization function and an application control function. Since the API for the broadcasting / communication cooperation function is shared, it is easy to create an application and the application does not depend on the receiver.
The broadcasting / communication cooperation service also incorporates functions for cooperation with devices such as personal computers and portable terminals.

  The broadcasting / communication cooperation function includes a broadcasting / communication cooperation basic function and an optional function to be implemented as necessary. The receiver manufacturer implements the broadcasting / communication cooperation basic function in all receivers. The application uses the broadcasting / communication cooperation function through the API. The broadcasting / communication cooperation function operates based on an API described later.

  The API implemented by the receiver is defined so that the operation of the application is the same without depending on the receiver. Since all applications process the receiver through the API, the application cannot access functions specific to the receiver without going through the API.

[1.6 Terminal linkage model]
FIG. 4 is a diagram illustrating a terminal cooperation model of the broadcasting / communication cooperation system.
The receiver can provide a service in cooperation with a terminal such as a portable terminal. Examples of terminals to be linked include a personal computer, a mobile phone, a tablet, a smartphone, and a PDA (Personal Digital Assistant). The receiver provides, as an API, a function that can be used by other terminals as a receiver function. An API that provides a function that can be used by other terminals is called a terminal cooperation API. For example, an application running on a mobile terminal can access a broadcasting resource such as acquisition of program information or call a receiver function such as reproduction control by using the terminal cooperation API.

[1.6.1 Terminal cooperation API]
The terminal cooperation API is an API for using functions of the receiver by other terminals and applications operating on the terminals. The terminals that cooperate with each other target terminals on a home network (LAN) and terminals that are accessed through the Internet. The definition of the API that provides various operations will be described later.

[1.6.2 Terminal cooperation API provision process]
The terminal cooperation API providing process operating on the receiver operates the terminal cooperation API. The terminal cooperation API providing process operates like a kind of daemon process that operates residently.

[1.6.3 Protocol for calling API]
For example, RESTful (REST: Representational State Transfer), UPnP (Universal Plug and Play), XMPP (eXtensible Messaging and Presence Protocol), or the like is used as a protocol for calling the terminal cooperation API.

[1.6.4 Push Notification Function]
The receiver also supports a Notification function in which a server on the Internet notifies the receiver of information by pushing. The receiver receives information notified by a push from a server or the like. Some receiver operations may be controlled by the Notification function, and the Notification function is also defined as part of the terminal cooperation API specification.

[2. Broadcast communication application]
[2.1 Service and application model]
The application model of the broadcasting / communication cooperation system is a model added or changed based on the concept of the application model of DVB-GEM1.2.

[2.1.1 Broadcast / communication cooperation application]
The operation of the application of the broadcasting / communication cooperation service is classified into two patterns: an operation linked to AV (Audio Visual) content (linked) and an operation of the application alone (not linked). AV content is broadcast content (program) or communication content (VoD, etc.).

In the case of linkage, application life cycle control such as activation is performed in conjunction with broadcast or communication content. The application is activated based on an AIT (Application Information Table) (application information table, application activation information) distributed together with the AV content. In this case, in addition to startup and termination operations by the viewer, a provider of AV content such as a broadcaster can also control a life cycle such as automatic startup and termination of an application.
On the other hand, in the case of non-linkage, the application is started and terminated without being linked to broadcasting or communication content. In this case, the life cycle of the application such as the start and end of the application is controlled only by the viewer.

[2.1.2 Service]
Conventionally, a service means a series of programs that can be broadcasted as part of a schedule organized by a broadcaster, but this concept has been expanded in a broadcasting / communication cooperation system to provide stream-dependent and independent services. Two service types are defined.

FIG. 5 shows a conceptual diagram of service types.
In the receiver, a related application is started by pseudo-tuning the stream dependent service and the independent service.
The stream dependent service is an extension of the service concept in the conventional sense, and is configured by adding an application (or a plurality of applications) operating in conjunction with an AV stream transmitted by broadcasting or communication. An application can be started in conjunction with selection / playback of an AV stream (channel selection in the case of broadcasting).
On the other hand, the independent service does not include a video / audio stream, and is configured only by an application (a plurality of applications). When the viewer selects the stand-alone service, the application is activated.

[2.1.3 Launching apps acquired on the fly and launching installed apps]
There are two methods for starting an application: a method of starting an application file acquired on the fly, and a method of starting an application file stored (installed) in a receiver in advance. On-the-fly is a method of acquiring an application file by communication when an application is executed, and is also referred to as a non-install type or a direct execution type.

  The receiver activates an application program of an application file in the local file system based on the well-known application by AIT described later. When the receiver acquires and installs an application file by communication, it rewrites the information in the location hierarchy set in the related AIT (see section 2.5.1) to the location on the local file system. Accordingly, an operation for generating a value for identifying a stand-alone service (required for each AIT unit of the stand-alone service) is required.

[2.2 Application well-known method (signaling)]
[2.2.1 Application startup information (AIT)]
The application included in the service is made known by application activation information notified when the service is selected. AIT defined by ARIB STD-B23 (hereinafter referred to as ARIB-J) is used as application activation information. In each of the stream dependent service and the independent service, the AIT for the service is known. Details of how to send AIT in each service are shown below.

FIG. 6 is a diagram showing an example of a text expression of AIT used in the broadcasting / communication cooperation system.
The AIT used in the broadcasting / communication cooperation system is based on the AIT defined by ARIB-J. In AIT, there are binary representation for transmission in SI (Service Information) table and text representation (AIT File) in XML (extensible markup language) format. In the figure, an example of text representation is shown. Yes. In the AIT, an application ID (applicationIdentifier) for identifying an application, a control code (controlCode) for controlling an application state, location information (location) indicating a storage location (storage location) of an application file, and the like are described.

[2.2.2 Dissemination of applications linked to AV contents]
Known applications that are linked to AV content are sometimes multiplexed with AIT on AV content transmitted by MPEG (Moving Picture Experts Group) -2 TS (Transport Stream), or sent separately with AIT information. . By transmitting AIT in conjunction with AV content, life cycle control such as activation of an application that is linked to a broadcast program or dynamic application that is linked to the progress of the program can be performed at the receiver.
Well-known methods include, for example, (1) AIT ES (Elementary Stream) addition, (2) Descriptor addition to EIT (Event Information Table), (3) Carousel transmission, ( 4) Acquisition of AIT file by communication, (5) Dynamic transmission of AIT file by communication, etc.

(1) When an ES for AIT is added, the AIT ES is multiplexed on the broadcast TS in the same manner as in ARIB-J.

(2) In the case of adding a descriptor to the EIT, a descriptor to the EIT (p / f) is added and the same information as the information transmitted by the AIT is transmitted as in the presentation control described later.

(3) In the case of transmission by carousel, AIT is transmitted by DSM-CC (Digital Storage Media Command and Control) data carousel. For example, an AIT file is transmitted by a specific module. By transmitting in the carousel, an acquisition time overhead is assumed, but there is no need to change the current broadcast signal.
As an example of operation in the carousel, the component tag and module of the broadcast communication cooperative activation file transmission carousel are fixed. For example, “AA” is set in the component tag, “0000” is set in the module ID, and a type indicating AIT is set in the Type descriptor of the module. The receiver monitors the update of the module, and when the update is detected, rereads the AIT, and executes the control specified by the AIT (application life cycle control).

(4) When acquiring an AIT file by communication, an AIT file prepared separately is acquired simultaneously with the selection of AV content. For example, the AV content to be reproduced (content ID) and the information describing application activation information (AIT) are acquired as starting points. It is possible to use the concept of usage unit contents and entry components of server type broadcasting (ARIB TR-B27).

  (5) In the case of dynamic AIT transmission by communication, control for starting a new application or ending an active application during reproduction of AV content is performed by the AIT transmitted by communication. When control is performed at a timing that is not assumed in advance, notification by push through communication is performed.

[2.2.3 Dissemination of applications that operate independently]
The receiver acquires an AIT including activation information of an application that operates independently by communication. Independent applications are obtained from known application repositories. The procedure for obtaining the startup information of each independent application is shown below.

(1) Set the application repository location in the receiver. It may be set in advance at the time of shipment, or a plurality of repositories may be added later by some method.
(2) When the application menu is opened, the receiver acquires a list of applications (including an AIT location description of each application) from the application repository, and displays the applications on the menu.
(3) The AIT of the application selected by the viewer is acquired from communication.

  The above procedure is executed using a WEB (Web) API provided by the repository. In addition, since an application that operates independently does not operate in conjunction with AV content, dynamic life cycle control is not performed at a predetermined timing. Control (such as termination) at a timing not specified in advance is performed by notification (notification) by push through communication.

[2.3 Application startup and termination]
[2.3.1 Application life cycle]
[2.3.1.1 Lifecycle]
FIG. 7 is a diagram illustrating a life cycle of an application.
The application status is “Not Loaded”, “Loaded”, “Paused”, “Started”, “Destroyed” (destroyed) according to the application status in ARIB-J. ) ". In these five states, a series of processes from when an application is loaded and executed until the application is finished is called an application life cycle, and control of transition between the states is called life cycle control.

[2.3.1.2 Basic life cycle control of applications linked to AV contents]
The life cycle control of an application linked to AV content is basically performed through selection of a stream dependent service.
The selection of the stream dependent service is made by the viewer. A service is a set of a series of contents including AV contents and applications, and a life cycle such as activation and termination is controlled by a control code included in an AIT sent together with the application. A single service may include a plurality of applications that operate simultaneously.

  Selection of a service that triggers application activation includes control from an application through a receiver API, control from a navigator as a resident application of a receiver, and control of a remote control button in the case of a broadcast service. . At the time of service switching, presentation of content (AV content or application) included in the service before and after switching is switched. When the applications included in the service before and after the switching are different, the application that was activated before the switching is terminated by the service switching, and a different application can be activated after the switching. Details of these operations will be described later in section 2.4.

[2.3.2 Application startup]
[2.3.2.1 Startup by AIT]
When a service (stream dependent service or independent service) is selected at the receiver, an application for which “auto-start” is specified in the control code included in the AIT provided together with the service is explicitly received from the viewer. Automatically starts with service selection without any action. During service selection, the life cycle is controlled by application signaling for that service. For example, in the case of a broadcast service, the receiver always monitors the AIT transmitted together with the broadcast and responds to the change. As described above, by application signaling such as AIT transmission, a new application can be controlled to be automatically started (auto-start) in the middle of the receiver.

  An application for which “auto-start” is not designated in the application activation information by AIT is not automatically activated, and requires explicit activation by the viewer. This explicit activation is performed by the application launcher of the resident application of the receiver. For example, when a broadcast service is selected, a broadcast communication cooperation service button on the remote control is pressed to open an application activation menu in the receiver, and a list of applications linked to the current broadcast (communication) service is displayed. Here, the viewer performs an operation of selecting and starting an application to be started on the receiver.

[2.3.2.2 Start from broadcasting / communication cooperation application]
Since a plurality of applications can be started in the service, another application included in the same service may be started from the started application. In the ARIB-J application execution environment, an API for starting another application by specifying an application ID is defined. In other execution environments, an API having the same function is defined.

[2.3.2.3 Startup from BML (Broadcast Markup Language)]
Since the receiver includes the current BML data broadcast execution environment in addition to the broadcast communication cooperation application execution environment, an API for controlling the start of the broadcast communication cooperation application is added as a BML API. BML is a multimedia coding system defined in ARIB STD B24, and is adopted as a data broadcasting system in the current Japanese terrestrial / BS / CS digital broadcasting.

[2.3.2.4 Launching an independently running application]
An independent service is a virtual service that includes only an application, and by selecting an independent application, the application is started by acquiring an AIT by the same mechanism as the activation by AIT in Section 2.3.2.1. . However, in the stand-alone service, at least one auto-start application is started. The stand-alone service is selected from, for example, an application launcher.

[2.3.3 Termination of application]
[2.3.3.1 End by AIT]
The life cycle of the activated application is controlled by application signaling for the service. For example, in the case of broadcast, the receiver always monitors the AIT transmitted together with the broadcast and designates the control code destroy for the active application, thereby terminating the application. Even when the AIT is multiplexed in the stream dependent service transmitted by communication, the termination control of the linked application can be performed.

[2.3.3.2 Termination by application itself]
The application itself terminates itself using the termination API.

[2.3.3.3 Termination by other applications]
Using the application termination API executed by the application, other running applications are terminated. In this case, an appropriate security policy for terminating other applications is necessary.

[2.3.3.4 Termination when switching to another service]
At the time of switching to another service at the receiver, among the applications included in the stream dependent service, the application included in the service before the switching is terminated, and the application signaled by the new service is started. If the same application is included in the services before and after switching, the operation can be continued. This is controlled by a flag in the AIT. Details of the service bound application, which is an application included in the stream dependent service, will be described later in section 4.2.

[2.3.3.5 End by receiver]
The receiver terminates the designated application by the receiver function. For example, a list of applications that are activated by the receiver is displayed, and the designated application is terminated by the viewer's selection.

[2.3.3.6 Dynamic application termination]
In order to dynamically control the end of the application, an AIT file instructing the end of the application is transmitted to the receiver. In this case, push notification (Notification) of AIT is performed.

[2.3.4 Launching multiple applications]
[2.3.4.1 Application signaled within the same service]
The receiver can simultaneously execute applications listed in the AIT in the same service.

[2.3.4.2 Simultaneous activation of applications that operate independently of applications linked to AV content]
An application linked to AV content is activated only within the stream dependent service. On the other hand, an application that operates independently can be activated at the same time as an application that works with AV content or another application that operates independently.

[2.3.4.3 Resource management when starting multiple applications]
When multiple applications are launched, they may require the same receiver resources (eg, displays). The receiver is equipped with a mechanism such as a resource manager, and performs operations such as appropriately allocating resources and stopping execution of applications when resources are not available.

[2.4 Application boundary]
[2.4.1 Basic handling of bound / unbound]
There are two types of applications: bound applications associated (associated) with the composition service and unbound applications not associated (unassociated). The composition service to which the bound application is associated is determined by the composition service from which the AIT including the activation information of the application is obtained.

  The bound application is in an executable state when receiving the associated organization service. That is, when the composition service is started by the AIT and the reception of the composition service is finished (when the composition channel being received is changed), the execution is finished. Another application started from the bound application is also handled as a bound application. When the first activated application that is the main book of a series of related bound applications is terminated, the other applications activated thereby are also terminated.

  Since the unbound application is not linked to the composition service, the execution of the application is continued even if the received composition service is changed. Since the AIT for starting the application cannot be obtained from the composition service, the start information is obtained by other means (for example, obtaining an AIT File (file) linked to the application using an application launcher or the like). It is given to the receiver and activated. Another application started from the unbound application is also handled as an unbound application. The application is basically terminated explicitly by the operation of the viewer, but is terminated also when an instruction (KILLALL) for terminating all applications is given by the AIT from the receiving service.

[2.4.2 Handling specific to unbound applications]
An unbound application is not associated with a composition service, but as shown in Section 2.3.2.4, a bound application is associated with a virtual composition service (generated in the receiver when the receiver is started). The same startup processing mechanism can be applied.

  The method of generating the virtual composition service depends on the implementation of the receiver, and what identification value is given to the composition service differs depending on the implementation of the receiver. However, if application files are stored in the receiver and can be started from the application launcher at an arbitrary timing, an ID for identifying a virtual organization service or an application file acquisition destination (service provider server or Since the server is described as the acquisition destination in the AIT acquired from the repository, it is necessary to change it so that it is acquired from the storage area in the receiver). Need to be updated.

[2.5 Application acquisition method]
[2.5.1 Acquisition based on AIT]
As described above, the activation information of all applications is given by the AIT.
Acquisition of the application file is instructed by the location information of the application included in the AIT. For example, in the example of FIG. 3, the location information is described in a hierarchy of “/ ApplicationList / Application / applicationSpecificDescriptor / dvbjDescriptor / location” (XML is described as the contents of the location element). The description of the location information is, for example, “http://192.168.11.37/demo.jar”.
The above is an example of acquiring demo.jar (Java (registered trademark) application archive) using the HTTP (Hypertext Transfer Protocol) protocol. The transport protocol to be used and the package format of the application will be described later.

[2.5.2 Application package format]
The package format of the application depends on the application format (Java (registered trademark) or HTML5). The receiver acquires a series of files (such as a program main body and an image file) necessary for starting the application by acquiring a group of files or entry files. This series of files is an application file. For example, the application file includes a compressed series of files (such as a zip file), a Jar file (Java (registered trademark) execution environment), an entry HTML file (in the case of the HTML5 execution environment), and an entry file defined uniquely. Format is used.

[2.5.3 Application transmission method]
The transmission method used when acquiring the application file via the network includes acquisition using the HTTP protocol and acquisition using the FILE protocol.
In the case of acquisition using the HTTP protocol, acquisition is performed using the GET method. The designation of the location of the AIT is “http: // ˜”.
On the other hand, in the case of acquisition using the FILE protocol, when specifying an application file (application program) stored (installed) locally on the receiver, the location of the AIT is specified as “file: /// ˜”.

[3. Interface conditions]
[3.1 Broadcast wave communication communication service control signal]
The broadcast wave needs a mechanism for sending the application activation information described in Section 2.2.2. Furthermore, in order to forcibly terminate all applications in the event of an emergency warning broadcast, the AIT application control code (application_control_code) defined in ARIB STD-B23 Part 2 Section 10.16.3.2 is set to “ Add “KILLALL”. Table 1 shows the meaning of the control code “KILLALL” to be added.

  Also, descriptors are added to EIT and AIT in order to control application presentation from the relationship between the application and AV content. Details will be described later in section 4.3.

[3.2 Broadcasting Station Server Group API]
FIG. 8 is a diagram illustrating a data flow between business operators in the broadcast communication cooperation system, and FIG. 9 is a diagram illustrating a data flow in the entire broadcast communication cooperation system.
Here, as shown in FIG. 8, between the broadcast station server group and the server for each service of the service provider server group, between the broadcast station server group and the broadcast communication cooperation infrastructure server, and between the broadcast communication cooperation infrastructure server and the service A description will be given of the API definition between the server for each service of the provider server group, the API between the receiver control and the broadcasting / communication cooperation base server, the metadata and the server for each service shown in FIG.

[3.2.1 API]
Communication between the broadcast station server, which is each server constituting the broadcast station server group, and the service provider server, which is each server constituting the service provider server group, is in the REST format. Also, since it is expected that the directory structure of the server differs between the broadcasting station server and the service provider server depending on the service to be provided, the API is negotiated between the two. Examples of URLs of the broadcast station server and service provider server are shown below.

http://hybridcast.org/{Broadcaster name} / {Server name} / {Content ID} / {Data to be managed} / {Sort method} / {First item}, {Number} /? {Parameter} = { value}/

[3.2.2 Recommendation service]
FIG. 10 is a diagram illustrating a sequence of a recommendation service. Methods used between the service provider server group and the interface unit of the broadcast station server are “GET”, “POST”, “PUT”, and “DELETE”. An example of the command format is shown below.

(1) http://hybridcast.or.jp/{broadcast station name} / (server name) / {content ID} / {data to be managed} / {sort method} / {first item}, {number} /
(2) http://hybridcast.or.jp/{broadcast station name} / (server name) / {viewer ID} / {data to be managed} / {sort method} / {first item}, {number} /
(3) http://hybridcast.or.jp/{Broadcasting station name} / (Server name) / {Review ID} / {Data to be managed} / {Sort method} / {First item}, {Number} /

  Parameters include {broadcast station name}, {server name}, {content ID}, {viewer ID}, {review ID}, {data to be managed}, {sort method}, {first item}, { Number} etc.

[3.2.3 Data to be managed]
Data to be managed includes content information, user information, user generated content information, device information, and authentication information.
Content information includes title, summary, genre, broadcast date / time, broadcast time (scale), video mode, audio mode, caption data, script, performer, music, producer, production company, work, recommended program, video URI, playback It includes data indicating the number of times, CM, time stamp information, and the like. The user information indicates the user's (viewer) name, age, gender, region, number of reviews written, number of comments written, favorites, friend list, playback location (time), playback end location (time), program viewing history, etc. Contains data. The user generated content information includes data indicating a content ID, a user ID, a review content, a review writing time, a review evaluation, and the like. The device information includes a device ID. The authentication information includes an authentication ID.

[3. Transport format]
[3.3.1 Video / audio handled by communication]
Video and audio handled by communications conform to the Digital TV Network Functional Specification, Streaming Functional Specification, Protocol Version V1.1 (Digital Television Information Society).

[3.3.1.1 Relationship to Video / Audio Monomedia Format]
MPEG-2 Video or H.264 For multiplexing video encoded with H.264 / MPEG-4 AVC (Advanced Video Coding), audio encoded with MPEG-1 Audio Layer II, MPEG-2 Audio AAC, subtitles, etc. Use the Transport Stream format. However, MPEG2-TS, MMT (MPEG Media Transport), MP4, etc. can also be used.

[3.3.1.2 Transfer protocol]
FIG. 11 is a diagram illustrating a transfer protocol stack.
Stream transmission uses RTP (Real-Time Transport Protocol) / UDP (User Datagram Protocol) and HTTP / TCP (Transmission Control Protocol). When RTP / UDP is used, error correction information may be transmitted as an option. In addition, when HTTP / TCP is used, stream control is performed using HTTP connections, methods, and headers. When transmission is performed by RTP (Real-time Transport Protocol), RTSP (Real Time Streaming Protocol) is used as stream control information.

[3.3.2 Subtitles]
Multilingual subtitles comply with Timed Text Markup Language (W3C (World Wide Web Consortium)). Note that synchronization is performed separately at the application level. Each corresponding font is downloaded from the server as necessary. For example, a font file is placed on the HTTP payload. In this case, Web Dynamic Fonts and PFR (PortableFont Resource) are used.
The font capacity is preferably about 5-35 MB (megabytes).

[3.4 Monomedia format]
The monomedia encoding in the broadcasting / communication cooperation service uses the one defined below.

[3.4.1 Video]
For the moving images, the MPEG-2 Video system defined in ARIB STD-B32 2.4 edition, Part 1, section 3.1 and the MPEG4-AVC system defined in section 3.2 are used. The restrictions of the encoding parameters of the television service specified in section are applied.

[3.4.2 Voice]
MPEG-2 Audio and PCM (Pulse Code Modulation) (AIFF-C (Audio Interchange File Format Compression)) are used for audio.
In the case of MPEG-2 Audio, the MPEG-2 AAC system defined in ARIB STD-B32 2.4 Edition, Part 2, Section 3.1 is used, and the encoding parameter constraints defined in Chapter 5 are Applied.
In the case of PCM, the system defined in ARIB STD-B24 5.4 version 1st part 2 section 6.2 is used.
For the additional sound, the system defined in ARIB STD-B24 5.4 version 1st part 2 section 6.4 is used.

[3.4.3 Still image]
In the case of JPEG (Joint Photographic Experts Group), ARIB STD-B24
The encoding method defined in Section 5.4 of the 5.4 edition, Volume 1, Part 2 is used.
In the case of PNG (Portable Network Graphics), a method defined in ISO / IEC 15948: 2003 is used. This is the same content as W3C Recommendation Portable Network Graphics (PNG) Specification (Second Edition)

[3.4.4 characters]
For character encoding, an internationally encoded character set defined in ARIB STD-B24 5.4 Edition, Volume 1, Part 2, Section 7.2 is used.
For the character code set, the BMP (Basic Multilingual Plane) set defined in section 7.2.1.1.3 is used, and Table 7-20 is applied. Also, ISO / IEC 10646: 2003 supplement 5 and supplement 6 are applied.
The external characters are defined in the ARIB STD-B24 5.4 edition, Part 1, Part 2 Section 1.2.1.2, or in the ARIB STD-B23 Part 1 section 5.2.1.2. The method is applied.
As control codes, only APR (CR) and APD (LF) are used among the C0 control codes defined in ARIB STD-B24 5.4 version 1 Part 2 Section 7.2.2.1. . Other C0 control codes and C1 control codes are not used.
The conversion of the character code is in accordance with ARIB STD-B24 5.4 Edition, Part 1, Part 2, Appendix E.

  When information is encoded by a method other than the character encoding method defined above, the information is converted into the character encoding method and processed in an appropriate process in the transmission or receiver. That is, the character code by another encoding method is not directly handled by the application.

[3.5 Application format]
Describes how to describe applications that can be executed on the receiver. The connection between the execution environment for executing the application created by this description method and the secure manager is shown in Chapter 4.

[3.5.1 Application format executable by receiver]
As a description method of an application executable by the receiver, BML (ARIB STD-B24), ARIB-J (ARIB STD-B23), HTML5 (W3C HTML5
Working draft-2011 / Jan / 13).

[3.5.2 BML]
The receiver has a function of presenting a BML document that conforms to the terrestrial digital broadcast operation regulations (ARIB TR-B14) or the BS digital broadcast operation regulations (ARIB TR-B15).
The receiver must be able to present data broadcasting services provided by terrestrial digital broadcasting or BS digital broadcasting in accordance with existing standards. However, the receiver is required only to present BML content distributed by broadcasting by the data carousel method, and BML content provided by the HTTP protocol by communication (TR-B14 Volume 3, Part 2, Section 5.14, TR -B15 Part 1, Part 3, Section 8.14) is not mandatory.

  Also, starting from the data broadcast content (BML), browser.startHybridcastApp () and getAITInfo () are defined as broadcast extended APIs for starting the communication application defined below.

  Table 2 shows the definition of browser.startHybridcastApp (). browser.startHybridcastApp () is an API for starting a broadcasting / communication cooperation application.

  Table 3 shows the definition of getAITInfo (). getAITInfo () is an API for acquiring the latest AIT information included in the service being received.

[3.5.3 HTML5]
[3.5.3.1 Description method]
The receiver supports HTML5 as a description method of a presentation engine type application provided from communication. The following are supported as JavaScript API. Of the following APIs, those being studied by W3C include Working Draft (WD) or Editor's Draft (ED). However, the API related to the data carousel transmitted by the broadcast wave is not essential.

(1) System Information API (W3C Working Draft 02 Feb. 2010) (2) WebSocket API (W3C Editor's Draft 28 Feb. 2011) (3) File API (W3C Working Draft 26 Oct. 2010) (4) Permission for File API , System Information API (Permissions for Device API Access, W3C Working Draft 05 Oct. 2010) (5) Device Description Repository Simple API (W3C Recommendation 05 Dec. 2008) (6) API for Media Resource 1.0 (W3C Working Draft 08 June 2010 (7) Web Storage (W3C Working Draft 08 Feb. 2011) (8) Server-Sent Events (W3C Editor's Draft 28 Feb. 2011) (9) Indexed Database API (W3C Working Draft 19 Aug. 2010) (10) SI Access API
(11) Tuning API
(12) Print (13) Reservations

[3.5.3.2 Browser]
The HTML5 browser of the receiver has the functions of JavaScript processing system, Web Workers (W3C Working Draft 08 Feb. 2011), Widget Interface (W3C Working Draft 3 Feb. 2011), HTML Canvas2D Context (W3C Editor's Draft 28 Feb. 2011) Implement. Web Workers supports multitasking, Widget Interface supports independent applications, and HTML Canvas 2D Context is necessary to support 2D vector graphics.

[3.5.4 ARIB-J]
The receiver supports ARIB-J as a description method of an application execution engine type application provided from communication. Further, DVB Bluebook A153 (GEM Media Synchronization API) is used as a synchronization API between a plurality of streams.

[3.6 Receiver API]
Hereinafter, receiver APIs usable in HTML5 and ARIB-J will be described.

[3.6.1 Namespace]
The name space is a character string description rule for specifying the positions of various resources such as video / audio contents, applications, monomedia files, and the like that are handled on the server or in the receiver. Namespace notation for referring to various resources used in section 3.5.2 and after is specified for each classification. The resources include resources on the Internet server, resources on the application cache, and broadcasting resources. The resources on the Internet server include stream resources such as VOD contents, and file resources such as applications and other resources referred to by applications. Broadcast resources include stream resources such as programs being broadcast, past and future programs, and carousel resources such as modules and event messages.

[3.6.2 Broadcasting / communication cooperation interface]
The broadcasting / communication cooperation interface includes the following interfaces.

(1) getRunningApplications (): Acquires information on applications being executed. The return value of getRunningApplications includes apps [] and application_id and running_level for each application. In apps [], a list of running applications is set. In application_id, an application ID is set, and is null when the application is a general application (unofficial application). In running_level, an execution level (authentication result and viewer setting state) is set.
From a security point of view, information that can be acquired for other applications should be restricted.

(2) queryApplicationInfo (): Acquires information about the specified application.
(3) getProgramInfo (): Acquires information on the broadcast being received. Return values are tuner_state, network_id, ts_id, orig_ts_id, service_id, event_id, and content_id. In tuner_state, a value indicating the reception state is set.
(4) getEPGInfo (): Acquires various information in the EIT (+ SDT) of the broadcast being received.
(5) saveApplicationToCache (): Saves the application file on the server in the cache.

(6) queryApplicationInCache (): Search for an application file (application program) in the cache. The arguments of queryApplicationInCache () are application_id, getDSMCCModule (), addBroadcastSignalListener (), and getListFromHybridcastMenu (). In application_id, an application ID issued from the certification authority is set. getDSMCCModule () acquires the specified module from the broadcast wave. addBroadcastSignalListener () registers a listener that monitors updates of SI, emergency information, carousel, and event messages. getListFromHybridcastMenu () acquires a list of top menu applications. The return values of queryApplicationInCache () are user_apps [], broadcaster_apps [], and vendor_apps [].

(7) addApplicationToHybridcastMenu (): Adds an application to the top menu.
(8) getKeyFromBroadcast (): Acquires key information for limited server access from broadcasting.
(9) querySupportedFunction (): Queries the application browser function. This is used for the purpose of checking whether the function / API is available.

[3.6.3 BroadacastSignalListener interface]
The BroadacastSignalListener interface is a listener interface for monitoring SI, emergency information, carousel, and event messages acquired from broadcasting. This interface event also occurs when the associated organization service is changed during bound application execution.

[3.6.4 LocalDatabase interface]
The LocalDatabase interface is an interface for holding and managing viewer information in the receiver. The viewer information is information that should not be output to the server side such as personal information, and is minimum information such as a viewer ID and a receiver ID.

[3.6.5 Synchronization API]
An API similar to DVB Bluebook A153 (GEM Stream Synchronization API) is introduced as the SynchronizationManager interface. Further, the following interface is added as an API.

(1) getCurrentSTC (): Acquires the current STC (System Time Clock) value. In the MPEG 2 Systems standard, the system clock (STC) on the receiver side is multiplexed and distributed as a PCR (Program Clock Reference) signal in the MPEG2 transport stream so that the system clock (STC) inside the receiver is transmitted on the transmission side. To be synchronized with the STC.
(2) getCurrentPositionInProgram (): Acquires the elapsed time from the start of the program.
(3) delayStreamPresentation (): Starts delay presentation of the broadcast stream being presented.
(4) getCurrentDelay (): Acquires the delay time amount (from the original presentation time) of the broadcast stream being presented.

[3.6.6 SecurityException interface]
An interface for exceptions that occur when an application makes function calls and property operations that are prohibited at the current execution level. The ecurityException interface is generated by calling each of the above APIs or by various operations on an object (<video> for HTML5 or OO Controller for ARIB-J) that references a broadcast.

[3.7 Receiver function]
The receiver of the broadcasting / communication cooperation system includes an application launcher as a receiver function. The application launcher is used to start an application stored in the receiver, to select an independent application from a known repository, and to select an application whose control code is “PRESENT” among applications whose start instructions are described by the AIT.

[4. Security]
[4.1 Management of broadcasting / communication cooperation application]
In order to disseminate and activate the broadcasting / communication cooperation service while satisfying the requirements of broadcasting companies, a framework that allows not only broadcasting companies and their related parties but also a wide range of service companies and individuals to participate is necessary. In this broadcasting / communication cooperation system, applications are classified into “A application” and “general application” from the viewpoint of security, and both applications can be executed in the receiver.

FIG. 12 shows an application management model in the broadcasting / communication cooperation system. By performing pre-registration with a registration manager (a third party organization), the “A application” is assured of the operation expected in the specifications of the broadcast communication cooperation system. The “A application” is given an ID and signature at the time of registration, and the signature is verified by the secure manager defined in section 2.2 at the receiver, allowing access to all APIs, and program linkage using broadcast resources Service can be performed. In addition, the AIT transmitted from the broadcaster enables fine presentation control according to the broadcaster's requirements.
On the other hand, the “general application” does not need to be registered in advance, but the operation expected in the specifications of the broadcasting / communication cooperation system is not guaranteed, and the broadcasting-related API cannot be handled from the application. Since “general application” is not assigned an ID and signature, it is difficult to specify individual applications, but it is possible to execute the application with presentation restrictions based on the requirements of the broadcaster.

[4.2 Secure Manager Functional Model]
FIG. 13 shows a functional model of the secure manager. The secure manager is a function that comprehensively manages security in the receiver.

[4.2.1 Application monitoring / control functions]
As described above, applications that run on the receiver are roughly classified into two types, “A application” and “general application”, depending on the distribution form of application files. “A application” and “general application” are distinguished according to the presence or absence of an ID and signature as shown in section 4.1, and the API access range in the receiver and the control range from the broadcaster are different. The operation contents of are different. The purpose of the application monitoring / control function is to identify the difference between the types of the A application and the general application, and to reliably control the operation at the time of executing the application.

(1) Application authentication: The receiver identifies either an A application or a general application for all applications to be executed, and further identifies an ID for an A application. The A application or the general application is distinguished by confirming the presence or absence of a signature attached to the application file (application program). If the application is an A application, the receiver further acquires an application ID described in the signature. Application identification is performed when an application is acquired or activated.
(2) Screen presentation control: described later in section 4.3.
(3) Resource access control: The receiver performs access control to APIs such as broadcast resources of the application being executed. When an application tries to access an API, if the application is a general application, the access is restricted by the type of API.
Further, when the application accesses the screen display API on the display, screen presentation control is executed based on the type of the A application or the general application and the presentation policy of the selected broadcaster. Details will be described later in section 4.3.
(4) Revocation: An application revocation function is provided.

[4.2.2 Receiver protection]
The receiver has protection functions such as viewer information protection and virus countermeasures.

[4.3 Application screen presentation control]
[4.3.1 Overview of screen presentation control]
In the broadcasting / communication cooperation service, the convenience of the broadcasting service can be expanded by presenting a related communication application simultaneously with the broadcasting program. On the other hand, it is assumed that a broadcast program and a communication application are mixedly presented on the receiver screen by using the communication service. Depending on the presentation method, the screen of the communication application overlaps with the broadcast program, which not only impairs the uniqueness and workability of the broadcast program, but also makes it impossible to accurately convey emergency information such as earthquake early warnings to viewers. There is. By the screen presentation control, application presentation control based on the intention of the broadcaster is performed in the broadcasting / communication cooperation service.

  FIG. 14 is a diagram illustrating the concept of the screen presentation control method. The screen presentation control method is intended to reflect the broadcaster's presentation policy on how to display the communication application on the screen for each broadcast program on the receiver. This is called control. In the content presentation control, presentation control in units of programs according to composition, presentation control for events occurring in a program such as an earthquake early warning, and presentation control in units of applications are realized.

[4.3.2 Basic operation of screen presentation control]
FIG. 15 is a diagram illustrating a basic operation model of screen presentation control. In order to reflect the broadcaster's presentation policy to the receiver, the method of presenting the communication content for the broadcast program, which is assumed in advance by the broadcaster, is managed as a presentation rule by the receiver. Specifically, as a method for presenting communication content, levels are classified according to the order of superposition and the difference in arrangement, and a table of presentation levels (policy levels) and presentation methods is held in the receiver as presentation rules. The broadcaster multiplexes and transmits the designated presentation level to the broadcast wave, and the receiver collates the presentation level with the presentation rules to determine the presentation method. Thereby, presentation control based on the presentation policy of the broadcaster can be realized.

[4.3.3 Transmission and multiplexing of control information]
With respect to the format of the control information for transmitting the broadcaster's presentation policy, three specific examples will be given as a method using program arrangement information used in digital broadcasting. As a screen presentation control in units of programs, there are a method using an existing EIT (Event Information Table) and a method using an extended EIT (EIT +). As a screen presentation control in service (channel) units, there is a method in which the AIT of a broadcast signal is extended and used. Further, as a screen presentation control in units of events that occur in real time during a program, there is a method using information transmitted from a broadcasting station other than program arrangement information. Details of the four methods will be described below.

(1) EIT program genre (EIT): The policy level is determined from the program genre described in the existing EIT content descriptor. For this purpose, the receiver manages a correspondence table between program genres and policy levels. The relationship with the ARIB standard is ARIB STD-B10.
Part 2 6.2.4, Appendix H.

  Table 4 is a table showing a specific example of the relationship between the program genre and the policy level. The program genre (program_genre) is composed of two stages of “content_nibble_level1” (0x0 to 0xF) representing the major classification and “content_nibble_level2” (0x0 to 0xF) representing the middle classification. The table managed by the receiver covers the genre of the middle category, and defines a policy level value.

(2) New descriptor added to EIT (EIT +): A new descriptor is added to the event information section of EIT, and policy information is described. The receiver interprets this descriptor and executes a desired process, thereby realizing control according to the policy level for each program. The relationship with the ARIB standard is ARIB TR-B14 (second volume) Part 3 31.3, ARIB STD-B10 Volume 2 5.2.7.

  Table 5 is a table showing the structure of the event security descriptor. In the case of EIT +, the event security descriptor shown in the figure is newly defined, and this event security descriptor is stored in the descriptor area in the EIT and transmitted. In the event security descriptor, a policy level (policy_level), an application ID (application_identifier), a control code (application_control_code), a priority (application_priority), a protocol identification (protocol_id), and a program related flag (associated_application_flag) are set.

policy_level represents a policy level in units of programs. The policy level is a value from 1 to 4.
application_identifier () is an identifier for identifying an application. Table 6 shows the structure of application_identifier ().

organization_id represents the organization that created the application and takes a value of 0x00000063 or later. application_id represents a number for identifying an application. application_id is uniquely assigned within the organization identification.

  application_control_code specifies a control code for controlling the application state. Table 7 shows the definition of the control code.

  application_priority indicates a policy level for each application. The policy level for each application indicates the relative priority among the applications announced in the service. The priority is a value from 1 to 4.

  protocol_id indicates a protocol for transmitting the application file. Table 8 shows the protocol_id specification.

  associated_application_flag indicates whether the application is linked to the program. Table 9 shows the protocol_id specification.

(3) AIT table definition and addition of new descriptor (AIT +): AIT is extended to transmit policy information. The receiver interprets this table and executes a desired process, thereby realizing control corresponding to a policy level for an event that occurs at any time. The association with the ARIB standard is ARIB STD-B23 Part 2 10.16.

Table 10 shows the data structure of AIT. The AIT shown in Table 10 is an extension of the AIT data structure defined by ARIB STD-B23. AIT describes a policy level, an application ID, and a control code. The AIT is transmitted in the section format, and is always transmitted while the event is continuing. The application ID is described in application_identifier (), and the control code is described in application_control_code.
These details are the same as those described in (2) EIT extension.
Further, in order to describe the policy level, a new security policy descriptor is defined and stored in the AIT common descriptor loop for transmission.

  Table 11 shows the structure of a newly defined security policy descriptor.

(4) Emergency warning broadcasting and emergency earthquake warning (EWS / EEW): The policy level is determined using emergency information transmitted from a broadcasting station. In the receiver, correspondence between emergency information and policy level is assumed in advance. If it is emergency warning broadcast, the emergency flag broadcast start flag of TMCC is monitored. The occurrence and termination of emergency information is detected, and the policy level at that time can be determined. The relationship with the ARIB standard is ARIB STD-B31 3.15 and ARIB STD-B24 Volume 1 Part 3 Chapter 9.

  Each of the above methods (1) to (4) can be sent simultaneously in parallel. Therefore, it is necessary to determine which method is used to prioritize what is sent and determine the policy level. The priority order is as follows.

EWS / EEW> AIT +> EIT +> EIT

  Based on this priority, the receiver determines the policy level, thereby enabling screen presentation control that prioritizes an emergency event based on the intention of the broadcaster.

[4.3.4 Example of screen presentation control]
FIG. 16 shows an example of screen presentation control according to the policy level.
When the policy level of the program is “1”, both the application screen of the application screen of the A application and the application screen of the general application are permitted to be superimposed on the broadcast screen.
When the policy level of the program is “2”, only the A application is permitted to be superimposed on the broadcast screen, and the application screen of the general application is prohibited from being superimposed on the broadcast screen. Only display of is allowed.
When the policy level of the program is “3”, the display of both the application screen of the A application and the application screen of the general application is permitted, but superimposition on the broadcast screen is prohibited for all application screens. Only display outside the screen is allowed.
When the policy level is “4”, only the full screen display of the broadcast screen is permitted.

  FIG. 17 shows an example of presentation control at the time of receiving the earthquake early warning. When the program policy level of program A is “1”, in the broadcast time zone of program A, the application screen of application A and the application screen of general application are displayed superimposed on the broadcast screen. However, the receiver determines that the policy level in the time zone in which the earthquake early warning is generated in the broadcast time zone of program A is the policy level “4” of the emergency earthquake early warning. Therefore, even if the receiver is in the broadcast time zone of program A, the application screen of the A application and the application screen of the general application are superimposed on the broadcast screen in the time zone where the earthquake early warning is occurring. Prohibit alignment.

[Description of an embodiment of the present invention to which the above-described broadcast communication cooperation system is applied]
Next, an embodiment of the present invention shown in FIG. 1 will be described.
FIG. 18 is an overall configuration diagram of a broadcasting / communication cooperation system according to an embodiment of the present invention. As shown in the figure, the broadcasting / communication cooperation system of the present embodiment includes a broadcaster apparatus 1 owned by a broadcasting station, a service provider server group 2 held by a service provider, and a repository server 3 held by a system administrator. And a receiver 4 held by the viewer. Although only one receiver 4 is shown in the figure, a plurality of receivers 4 are actually provided.

The broadcast provider apparatus 1 includes a broadcast transmission apparatus 11 and a broadcast station server group 12.
The broadcast sending apparatus 11 corresponds to the broadcasting station equipment shown in FIG. 3, and is a broadcasting equipment for digital broadcasting composed of a program organization equipment, a program sending equipment, a transmission equipment, and the like.

The broadcast transmission apparatus 11 includes a broadcast-related data management unit 111, a signal setting unit 112, and a broadcast transmission unit 113.
The broadcast-related data management unit 111 manages program security policy data for each program, application security policy data for the A application, other policy data, and the like.
The program security policy data includes policy level data indicating a policy level of the program, an application ID of an application bound to the program, a control code for the application bound to the program, and the like.
The application security policy data includes information for identifying a program to which the application is bound, application protocol identification, location information, and the like. The location information indicates the storage location (storage location) of the application, and is, for example, the URL of the receiver application server 21 or the repository server 3 that can download the application. The protocol identification indicates whether the application is transmitted by broadcast or communication.
Only the A application is bound to the program.

The policy data includes presentation rule data and a policy level table.
The presentation rule data is data describing a presentation method for each policy level. The presentation method includes a screen display method and an audio output method. As the screen display method, for example, only the broadcast screen (video of the program) is displayed. For both the A application and the general application, the application screen (video of the application) is displayed on the broadcast screen or outside the broadcast screen. There are methods such as displaying only the application screen superimposed on the broadcast screen, and displaying the application screen of the general application outside the broadcast screen. Examples of the audio output method include a method of outputting only the sound of the broadcast program, and outputting the sound of the broadcast program and the sound of the A application or the general application independently or in combination.
The policy level table is data describing the policy level corresponding to the genre of the program and the policy level of each event. An event is the content of a broadcast that does not necessarily occur in conjunction with a program, such as an emergency warning signal or an earthquake early warning.

The signal setting unit 112 sets various data in the broadcast signal transmitted by the broadcast sending unit 113.
The signal setting unit 112 sets AIT and program policy level data for a broadcast signal based on program security policy data and application security policy data managed by the broadcast-related data management unit 111. The signal setting unit 112 multiplexes the AIT of the application bound to the program as an independent ES on the broadcast signal (broadcast TS) or sets it in the data carousel. Alternatively, the signal setting unit 112 sets information equivalent to the AIT of the application bound to the program in the EIT. Further, the signal setting unit 112 sets the policy level data of the program to EIT (Table 5) or AIT (Table 11). Note that when the policy level corresponding to the genre of the program is used, the policy level data need not be set in the broadcast signal. Further, the signal setting unit 112 sets the application file to a data carousel or the like. In addition, the signal setting unit 112 sets the policy data managed by the broadcast-related data management unit 111 to a broadcast signal in a section format, or to an engineering service or a data carousel.
The broadcast sending unit 113 transmits a broadcast signal for digital broadcasting. The broadcast signal includes information set by the signal setting unit 112.

The broadcast station server group 12 corresponds to the broadcast station server group shown in FIG. 3, and includes a content management server 13, a content distribution server 16, a broadcast station service server 17, and a notification server 18.
The content management server 13 includes a program management server 14 and a metadata management server 15. The program management server 14 manages already broadcasted programs and broadcasted programs. The metadata management server 15 manages metadata regarding each program. The metadata includes, for example, program title, program ID, program outline, performer, broadcast date and time, script, caption, and commentary data.

The content distribution server 16 is connected to the receiver 4 via the communication network 9 such as the Internet, and distributes content data of the content requested from the receiver 4.
The broadcast station service server 17 transmits the content data of the broadcast station service to the service provider server group 2. Examples of broadcasting station services include social network services and blog services.

  The notification server 18 is connected to the receiver 4 via the communication network 9 and is bound to the program based on the program security policy data and the application security policy data acquired from the broadcast-related data management unit 111 of the broadcast transmission device 11. The application AIT (FIG. 6) and the policy level data of the program are distributed to the receiver 4. In addition, the notification server 18 distributes the policy data acquired from the broadcast-related data management unit 111 of the broadcast transmission device 11 to the receiver 4. Note that all or part of the information may not be distributed from the notification server 18 and may be transmitted by the broadcast sending unit 113 of the broadcast sending device 11 using only the broadcast signal.

  The service provider server group 2 corresponds to the service provider server group shown in FIG. 3 and includes a receiver application server 21, a service server 22, a content distribution server 23, and a notification server 24. The receiver application server 21, service server 22, content distribution server 23, and notification server 24 are connected to the receiver 4 via the communication network 9.

The receiver application server 21 manages each application and distributes application files to the receiver 4.
The service server 22 is, for example, a multilingual subtitle server, a speech speed conversion voice server, a social TV server, a recommendation server, a bookmark server, and the like, and distributes content data of a service requested from the receiver 4.
The content distribution server 23 is, for example, a VOD distribution server, a caption distribution server, or a multi-view distribution server, and distributes content data of content requested from the receiver 4.
The notification server 24 transmits the application AIT (FIG. 6) to the receiver 4. In the case of the A application, the notification server 24 may transmit AIT (FIG. 6) based on the program security policy data and application security policy data acquired from the broadcast related data management unit 111 of the broadcast transmission device 11.

The repository server 3 corresponds to the repository shown in FIG. 3 and is connected to the receiver 4 via the communication network 9. The repository server 3 performs an electronic signature on an application file (application program) generated by the service provider, and transmits data necessary for authenticating the electronic signature of the application file (application program) to the receiver 4. Further, the repository server 3 transmits data indicating a list of A applications and location information of the A applications to the receiver 4. The repository server 3 may transmit the application file of the A application that is digitally signed to the receiver 4, and the receiver application server 21 receives and receives the application file of the A application that is digitally signed from the repository server 3. You may transmit to the machine 4. Further, the repository server 3 may transmit the AIT of the A application to the receiver 4.
Further, the repository server 3 receives the AIT (FIG. 6) of the A application bound to the program based on the program security policy data and the application security policy data received from the broadcast related data management unit 111 of the broadcast transmission device 11. 4 may be transmitted.

  The receiver 4 corresponds to the receiver shown in FIG. 3 and is, for example, a device such as a television receiver, a set top box, a personal computer, or a portable terminal.

  FIG. 19 is a functional block diagram showing the internal configuration of the receiver 4. As shown in the figure, the receiver 4 includes a broadcast receiving unit 401, a separating unit 402, a clock 403, a first synchronization buffer 404-1, a second synchronization buffer 404-2, a first decoder 405-1, 2 decoder 405-2, data broadcast execution unit 406, video control unit 407, video display unit 408, audio control unit 409, audio output unit 410, communication input / output unit 411, application execution control unit 412, presentation control unit 413, operation An input unit 414, a channel selection unit 415, a local information storage unit 416, and an external I / F unit 417 are configured.

The broadcast receiving unit 401 is a tuner that receives a broadcast signal. The broadcast signal is either a wireless broadcast signal or a wired broadcast signal. A radio broadcast signal is a signal obtained by receiving a broadcast radio wave (ground wave) transmitted by a transmission antenna on the broadcast station side or a satellite wave relayed by a satellite with a reception antenna. The wired broadcast signal is a signal transmitted from the broadcast station side via an optical cable, a coaxial cable, or the like. The broadcast receiving unit 401 receives a broadcast signal, demodulates it, and outputs a broadcast stream (TS).
The demultiplexing unit 402 is a demultiplexer, which converts a broadcast stream supplied from the broadcast receiving unit 401 into PCR (Program Clock Reference), video data, audio data, subtitle data, data broadcast, PSI (Program Specific Information) / SI (SI). Service Information) and AIT transmitted in an independent elementary stream (ES). The AIT may be included in the data broadcast, or the same content as the AIT may be set in the EIT constituting the SI. Further, the separation unit 402 may separate and output the application file from the broadcast signal.

  The communication input / output unit 411 inputs and outputs data through communication via the communication network 9. The communication input / output unit 411 outputs the AIT and application file transmitted via the communication network 9 to the application execution control unit 412. Further, the communication input / output unit 411 outputs the policy level data and policy data of the program transmitted via the communication network 9 to the presentation control unit 413. The communication input / output unit 411 communicates content data distributed from the content distribution server 16 and the content distribution server 23 and content data distributed from the service server 22 in accordance with an instruction of an application executed by the application execution control unit 412. The data is received via the network 9 and output to the second synchronization buffer 404-2.

The operation input unit 414 is an interface that receives an operation by the viewer, and is, for example, a receiving device that receives information input by the viewer from a remote controller, a mobile phone, a tablet terminal, or the like, a keyboard, a mouse, or the like. The operation input unit 414 outputs media (terrestrial / BS) and channel selection instructions input by the viewer to the channel selection unit 415. In addition, the operation input unit 414 outputs instructions for starting and ending the broadcasting / communication cooperation service and instructions for the application to the application execution control unit 412.
The channel selection unit 415 controls media and channels received by the broadcast reception unit 401 in accordance with the operation input to the operation input unit 414.

  The data broadcast execution unit 406 executes the data broadcast application transmitted by the digital broadcast signal, and outputs data broadcast image (graphic) data to the video control unit 407. The data broadcast execution unit 406 includes an API for starting an application of the broadcast communication cooperation service. When the data broadcast execution unit 406 executes the data broadcast application and an API for starting the application of the broadcast communication cooperation service is called, the data broadcast execution unit 406 instructs the application execution control unit 412 to start the application. Further, the data broadcast execution unit 406 acquires the AIT and application file transmitted by the data carousel from the data broadcast and outputs them to the application execution control unit 412. Further, the data broadcast execution unit 406 acquires the policy data transmitted by the data carousel from the data broadcast and outputs it to the presentation control unit 413.

  The application execution control unit 412 executes an application of the broadcasting / communication cooperation service. The application execution control unit 412 instructs the second decoder 405-2 to decode the content data received from the content distribution server 16, the content distribution server 23, or the service server 22 in accordance with the application being executed. The content data includes one or both of video data and audio data. The video data is, for example, a moving image, a still image, text data, or the like. The application execution control unit 412 outputs graphic (video) data and video control instructions to the video control unit 407 and outputs audio data and voice control instructions to the audio control unit 409 according to the application being executed.

The clock 403 outputs a timer counter value. The clock 403 adjusts the frequency of the oscillator according to the timer counter value indicated by the PCR, and synchronizes the time with the broadcast transmission side.
The first synchronization buffer 404-1 stores video data, audio data, and caption data output from the separation unit 402. A PES (Packetized Elementary Stream) generated from an elementary stream (ES) of video data, audio data, and subtitle data is set by being divided into transport packets constituting a broadcast stream (TS). The PES header includes PTS (Presentation Time Stamp). The first synchronization buffer 404-1 outputs the video data, audio data, and caption data output from the separation unit 402 in units of PES packets according to the instruction of the first decoder 405-1.
The second synchronization buffer 404-2 stores content data and service content data received by the communication input / output unit 411. Alternatively, the second synchronization buffer 404-2 stores video data, audio data, and caption data output from the separation unit 402 in accordance with a viewer instruction input by the operation input unit 414. The second synchronization buffer 404-2 outputs the stored content data or video data, audio data, and caption data of the program in units of PES packets according to the instruction of the second decoder 405-2.

The first decoder 405-1 identifies the PES packet in the first synchronization buffer 404-1, in which the PTS corresponding to the time output from the clock 403 is set, and the video data encoded from the identified PES packet Audio data and subtitle data are read, and the read data are decoded and output.
The second decoder 405-2 identifies the content data or the PES packet of the program in the second synchronization buffer 404-2 in which the PTS corresponding to the time output from the clock 403 is set, and from the identified PES packet The encoded video data, audio data, and subtitle data are read, and the read data are decoded and output.

  The presentation control unit 413 determines a presentation method (screen display method and audio output method) according to the policy level of the selected program or the policy level of the event that is occurring and the presentation rule data. The presentation control unit 413 instructs the video control unit 407 to display the broadcast screen, the application screen of the A application, and the application screen of the general application according to the determined screen display method. Further, the presentation control unit 413 instructs the audio control unit 409 to output the sound based on the broadcast sound data, the sound based on the sound data of the A application, and the sound based on the sound data of the general application, according to the determined sound output method. .

  The video control unit 407 includes a broadcast screen based on the video data and caption data of the program output from the first decoder 405-1 and an A application based on the video data of the content data output from the second decoder 405-2, The application screen of the application is displayed on the video display unit 408 according to the screen display method instructed from the presentation control unit 413 or the application execution control unit 412. When graphic (video) data is output from the application execution control unit 412 by executing the application, the video control unit 407 displays the video according to the screen display method instructed from the presentation control unit 413 or the application execution control unit 412. A display screen based on the data is also displayed on the video display unit 408. The second decoder 405-2 may output video data and caption data of other programs.

  The video display unit 408 is a general display, and displays broadcast and application screens. For example, the video display unit 408 displays an application screen such as a moving image, a still image, text of content data received from the communication network 9, a graphic output from the application execution control unit 412 by executing the application, Alternatively, a video that combines broadcast screens of other programs is displayed.

  The audio control unit 409 includes audio based on the audio data of the program output from the first decoder 405-1, audio of A application and general application based on the audio data of the content data output from the second decoder 405-2. The voice based on the voice data output from the application execution control unit 412 by executing the application is output from the voice output unit 410 according to the voice output method instructed by the presentation control unit 413 or the application execution control unit 412. Note that the second decoder 405-2 may output audio data of another program. The audio output unit 410 is a general speaker and outputs broadcast and application audio.

The local information storage unit 416 stores various data such as user information.
An external interface unit (hereinafter referred to as “external I / F unit”) 417 transmits and receives data to and from the device 8 connected to a home network such as a LAN (Local Area Network). The device 8 is a terminal that operates in cooperation with the receiver 4, and is, for example, a personal computer, a mobile phone, a tablet, a smartphone, or a PDA.

  When the receiver 4 is a set top box or the like, the video display unit 408 and the audio output unit 410 are external devices connected to the receiver 4.

FIG. 20 is a block diagram illustrating a detailed configuration of the application execution control unit 412.
As shown in the figure, the application execution control unit 412 includes an application storage unit 431, an application authentication unit 432, an application management unit 433, an application control unit 434, an application execution unit 435, a resource access control unit 438, and a resource control unit 439. Prepare.

  The application storage unit 431 is an application file received by the communication input / output unit 411 via the communication network 9, or an application file acquired from the data broadcast by the data broadcast execution unit 406, or separated from the broadcast signal by the separation unit 402. Store application files. The application file may be stored in the application storage unit 431 in advance at the time of shipment. The application storage unit 431 includes a main storage device and an auxiliary storage device such as a disk. For example, an application file is stored on a disk and read to the main storage device at the time of execution. In this case, the application file of the application executed on-the-fly is not stored in the disk but is stored only in the main storage device, and is deleted from the main storage device when the execution is completed.

  The application authentication unit 432 receives data necessary for authentication of the electronic signature from the repository server 3, and verifies the electronic signature added to the application file (application program) using the received data. For example, the application authentication unit 432 uses the public key received from the repository server 3 to decrypt the application file that has been digitally signed. As a result, when a predetermined data string is obtained, the application authentication unit 432 determines that the verification of the electronic signature has succeeded. When the verification of the electronic signature is successful, the application authentication unit 432 determines that the application is an A application. When the verification of the electronic signature is unsuccessful, or when the electronic signature is not added, the application authentication unit 432 determines that the application is a general application. to decide.

  The application management unit 433 manages the activation or stop state of the application by the application execution unit 435 and the output status of the activated application. The output status is information indicating whether an image or sound is output from a running application. In response to the inquiry from the presentation control unit 413, the application management unit 433 returns the output status of the activated application and a response indicating whether the activated application is an A application or a general application.

  The application control unit 434 controls activation and stop of the application in the application execution unit 435 according to the control code for the application bound to the program and the instruction for the application input by the operation input unit 414. In addition, the application control unit 434 instructs the application execution unit 435 to start the application that is instructed to start from the data broadcast execution unit 406. When the channel is changed according to the input from the operation input unit 414, the application control unit 434 terminates the application bound to the program of the channel before the change and the application bound to the program of the channel after the change. The application execution unit 435 is instructed to start. Note that the application control unit 434 is equivalent to the application bound to the program and the control code for the bound application as the independent ES of the broadcast signal or the AIT included in the data broadcast and the AIT obtained from the EIT of the broadcast signal. Or from the AIT received from the notification server 18 or the notification server 24 via the communication input / output unit 411. In addition, the application control unit 434 transmits an application file download request with the location information set in the AIT as a destination. The repository server 3 or the receiver application server 21 that has received the download request from the receiver 4 distributes the application file to the receiver 4.

  The application execution unit 435 includes a receiver API unit 436 and a terminal cooperation API unit 437. In accordance with an instruction from the application control unit 434, the application execution unit 435 reads the application program of the application instructed to start from the application storage unit 431 and executes it. When the application execution unit 435 executes the application program, the application operates on the receiver 4, and the application execution unit 435 requests content from the content distribution server 16 and the content distribution server 23 via the communication network 9. Or request a service from the service server 22. Also, by executing the application program, the application execution unit 435 outputs graphic data and video control instructions to the video control unit 407 and outputs audio data and voice control instructions to the audio control unit 409.

The receiver API unit 436 executes a receiver API that is an API for using each resource in the receiver 4 when the application execution unit 435 executes the application. When the receiver API unit 436 executes the receiver API, the resources in the receiver 4 can be used from the application program executed by the application execution unit 435.
The terminal cooperation API unit 437 is an API that allows the device 8 on the home network that can communicate with the external I / F unit 417 and the device connected via the communication network 9 to use the function of the receiver 4. Execute cooperative API. When the terminal cooperation API unit 437 executes the terminal cooperation API, resources in the receiver 4 can be used from a device 8 connected via the home network or a device connected via the communication network 9.

The resource control unit 439 controls access from the receiver API unit 436 and the terminal cooperation API unit 437 to each functional unit that is a resource in the receiver 4.
The resource access control unit 438 controls whether access from the receiver API unit 436 and the terminal cooperation API unit 437 to each functional unit in the receiver 4 is permitted. The resource access control unit 438 performs this control according to whether the application that is the caller of each API executed by the receiver API unit 436 or the terminal cooperation API unit 437 is an A application or a general application.

  FIG. 21 is a block diagram illustrating a detailed configuration of the presentation control unit 413. As shown in the figure, the presentation control unit 413 includes a policy data management unit 451, a policy data storage unit 452, an event interpretation unit 453, a policy level collation unit 454, an event control unit 455, a program policy storage unit 456, and a policy mediation unit. 457 and a policy level storage unit 458.

  The policy data storage unit 452 stores policy data including presentation rule data and a policy level table. The policy data management unit 451 manages policy data stored in the policy data storage unit 452. The policy data management unit 451 outputs the policy level table read from the policy data storage unit 452 to the policy level verification unit 454, and outputs the presentation rule data read from the policy data storage unit 452 to the policy arbitration unit 457. Further, the policy data management unit 451 receives the policy data transmitted by broadcasting from the separation unit 402 or the data broadcast execution unit 406, and receives the policy data transmitted by communication from the communication input / output unit 411. The policy data management unit 451 updates the policy data stored in the policy data storage unit 452 with the policy data transmitted by broadcasting or communication.

  The event interpreter 453 analyzes the broadcast signal received by the broadcast receiver 401, the data broadcast and subtitle data separated by the separator 402, and detects the occurrence or end of the event. When the event interpretation unit 453 detects (interprets) the occurrence or end of an event, the event interpretation unit 453 outputs the event number of the detected event and status data indicating the occurrence or end to the policy level matching unit 454.

The policy level checking unit 454 refers to the policy level table to determine (check) the policy level corresponding to the genre of each program indicated by the EIT and the policy level corresponding to the event specified by the event number. The policy level collating unit 454 includes the broadcast start time and broadcast end time data of the program acquired from the SI input from the separating unit 402 and the policy level of the program (hereinafter referred to as “program policy level”). Output to the event control unit 455. When the program policy level is set to EIT, the policy level verification unit 454 sends the program start level and end time data of the program and the program policy level of the program acquired from the EIT to the event control unit 455. Output.
Further, when the policy level matching unit 454 acquires the program policy level from the AIT, the policy level matching unit 454 outputs the acquired program policy level to the policy mediation unit 457. Further, the policy level matching unit 454 outputs the policy level determined in accordance with the event number (hereinafter referred to as “trigger policy level”) to the policy arbitration unit 457.

  The program policy storage unit 456 stores the program start time and program end time in association with the program policy level. The event control unit 455 writes the program start time and program end time data input from the policy level matching unit 454 and the program policy level in association with each other and writes them in the program policy storage unit 456, and stores them in the program policy storage unit 456. Based on these information, the time for executing the display control is managed. When the event control unit 455 refers to the program start time data stored in the program policy storage unit 456 and detects that the execution time is to be notified, the event control unit 455 corresponds to the execution time and the execution time. The program policy level is output to the policy mediation unit 457.

  The policy level storage unit 458 stores the execution time and program policy level, trigger policy level, and status data input to the policy arbitration unit 457. The policy arbitration unit 457 determines a policy level from the execution time and program policy level input from the event control unit 455 and the trigger policy level input from the policy level collation unit 454. For example, the trigger policy level may be determined as the policy level, and the higher one of the program policy level and the trigger policy level may be determined as the policy level.

  When the program policy level acquired by the AIT is input from the policy level verification unit 454, the policy mediation unit 457 is input from the policy level verification unit 454 rather than the program policy level input from the event control unit 455. Prioritize program policy level. That is, the policy mediation unit 457 determines the policy level from the program policy level obtained from the AIT and the trigger policy level. The policy arbitration unit 457 refers to the presentation rule data, and determines the screen display method and sound based on the determined policy level, information indicating whether the active application acquired from the application management unit 433 is an A application, and the output status. Determine the output method (presentation method). The policy arbitration unit 457 outputs the determined screen display method to the video control unit 407, and outputs the determined audio output method to the audio control unit 409.

  FIG. 22 shows a configuration and data example of information stored in the application storage unit 431 shown in FIG. The application storage unit 431 is an area for storing location information indicating the storage location of the application program (application code) and the application program in association with the application ID. In the example illustrated in FIG. 1, the application storage unit 431 stores the application program in association with the application ID “001”, and the location information “http: //192.168.11. 37 / bbbbbb ”is stored, and location information“ http://192.168.11.37/ccccc ”and an application program are stored in association with the application ID“ 003 ”.

  Returning to the description of FIG. The application execution unit 435 reads an application program from the application storage unit 431 and executes the application.

  Specifically, the application execution unit 435 acquires an application ID and a control code (auto-start) instructing execution of the application from the separation unit 402, and reads an application program associated with the application ID. And run the application. In addition, when the application execution unit 435 obtains an application ID and an application execution instruction from the application activation menu via the operation input unit 414, the application execution unit 435 similarly executes the application.

  The method reception unit 501 receives various method calls requested from the application execution unit 435 that executes an application. In other words, the method receiving unit 501 receives invocations of various methods issued by the application executed by the application execution unit 435.

  Specifically, the method receiving unit 501 receives a method for saving an application to the cache (saveApplicationToCache ()) requested from the application execution unit 435 that executes one application. An application ID for identifying another application is specified as an argument in the method for storing the application in the cache (hereinafter simply referred to as “save method”). When the method reception unit 501 receives a storage method, the method reception unit 501 outputs an application request instruction including an application ID (an application ID of another application) specified as an argument to the application acquisition unit 520.

  In addition, the method reception unit 501 receives an in-cache application query method (queryApplicationInCache ()) requested from the application execution unit 435 that executes one application. An application ID for identifying another application is specified as an argument in the inquiry method for the application in the cache (hereinafter simply referred to as “inquiry method”). When the method reception unit 501 receives an inquiry method, the method reception unit 501 outputs an application search instruction including an application ID (an application ID of another application) specified as an argument to the in-cache search unit 570.

  In addition, the method reception unit 501 receives an in-cache application list information acquisition method (getApplicationsInCache ())) requested from the application execution unit 435 that executes one application. No argument is specified in the cached application list information acquisition method (hereinafter simply referred to as “list information acquisition method”). When receiving the list information acquisition method, the method reception unit 501 outputs an application list information acquisition instruction to the in-cache search unit 570.

  When the method reception unit 501 receives a save method (saveApplicationToCache ()) and outputs an application request instruction to the application acquisition unit 520, the method reception unit 501 acquires response information for the application request instruction from the application acquisition unit 520. Specifically, the method reception unit 501 acquires an acquisition result indicating success or failure of application acquisition from the application acquisition unit 520. The method reception unit 501 outputs the return value of the storage method corresponding to the response information (acquisition result) acquired from the application acquisition unit 520 to the application execution unit 435. Specifically, when the method reception unit 501 acquires an acquisition result indicating success of application acquisition from the application acquisition unit 520, the method reception unit 501 outputs a return value “True” to the application execution unit 435 and acquires an acquisition result indicating failure. Is acquired from the application acquisition unit 520, the return value “False” is output to the application execution unit 435 (the return value is returned to the application that called the method).

  In addition, when the method reception unit 501 receives a query method (queryApplicationInCache ()) and outputs an application search instruction to the application acquisition unit 520, the method reception unit 501 acquires response information for the application search instruction from the in-cache search unit 570. Specifically, the method receiving unit 501 acquires a search result indicating whether or not the queried application ID is stored in the application storage unit 431 from the application acquisition unit 520. The method reception unit 501 outputs the return value of the inquiry method corresponding to the response information (search result) acquired from the in-cache search unit 570 to the application execution unit 435. Specifically, when the method reception unit 501 obtains a search result indicating that the queried application ID is stored in the application storage unit 431 from the cache search unit 570, the method reception unit 501 returns the return value “True” to the application. When the search result output to the execution unit 435 and indicating that it is not stored is acquired from the cache search unit 570, the return value “False” is output to the application execution unit 435 (the return value is the application that called the method). To be returned).

  In addition, when the method reception unit 501 receives a list information acquisition method (getApplicationsInCache ()) and outputs an application list information acquisition instruction to the application acquisition unit 520, response information for the application list information acquisition instruction is stored in the cache. Obtained from the search unit 570. Specifically, the method reception unit 501 acquires the application ID list “001, 002...” Stored in the application storage unit 431 from the application acquisition unit 520. The method reception unit 501 outputs the response information (application ID) acquired from the cache search unit 570 to the application execution unit 435 as a return value of the list information acquisition method. Specifically, when the method reception unit 501 acquires the application ID “001, 002,...” Stored in the application storage unit 431 from the cache search unit 570, the return value “001, 002,. "Is output to the application execution unit 435 (the return value is returned to the application that called the method).

  The application acquisition unit 520 acquires an application request instruction from the method reception unit 501. The application acquisition unit 520 acquires location information indicating the storage location of the application program with the application ID included in the application request instruction from a predetermined repository (external server) via the communication input / output unit 411. The application acquisition unit 520 associates the application ID included in the application request instruction acquired from the method reception unit 501 with the location information acquired via the communication input / output unit 411, and writes it in the application storage unit 431.

  That is, the application acquisition unit 520 acquires location information from a predetermined repository based on the storage method received by the method reception unit 501 and writes the location information in the application storage unit 431.

  Further, the application acquisition unit 520 outputs response information (acquisition result) to the application request instruction to the method reception unit 501.

  The application acquisition unit 520 acquires an application program based on the location information read from the application storage unit 431 and writes it in the application storage unit 431. Specifically, the application acquisition unit 520 displays the location information when the location information corresponding to the application ID included in the application request instruction acquired from the method reception unit 501 is stored in the application storage unit 431. Instead of acquiring and writing to the application storage unit 431, an application program is acquired and written to the application storage unit 431. As a result, the application program cached in the own apparatus can be read and executed.

  The in-cache search unit 570 acquires an application search instruction from the method reception unit 501. The in-cache search unit 570 searches the application storage unit 431 for the application ID included in the application search instruction. The in-cache search unit 570 outputs the search result to the method reception unit 501.

  That is, the cache search unit 570 searches the application storage unit 431 based on the inquiry method received by the method reception unit 501, and responds (returns) to the application whether or not the designated program exists.

  In addition, the cache search unit 570 acquires an application list information acquisition instruction from the method reception unit 501. The cache search unit 570 acquires all application IDs stored in the application storage unit 431 as list information. The cache search unit 570 outputs all application IDs to the method reception unit 501.

  That is, the cache search unit 570 reads the list information related to the application stored in the application storage unit 431 based on the list information acquisition method received by the method reception unit 501 and responds to the application with the read list information. (return).

  When the application ID “001, 002,...” That is the return value of the list information acquisition method is acquired from the method reception unit 501 by the function of the application executed by the application execution unit 435, it is based on the application ID. Program name list information can be generated and output to the presentation control unit 413.

  In addition, the application function executed by the application execution unit 435 can execute an application designated by the user from the list information presented as described above.

  Moreover, when the program ID of one application program is not stored as a result of the query method (queryApplicationInCache ()) by the function of the application executed by the application execution unit 435, the application ID is stored as an argument. A method (saveApplicationToCache ()) can be called.

  Hereinafter, the operation of the receiver illustrated in FIG. 1 will be described with reference to a flowchart. FIG. 23 is a flowchart illustrating an example of the operation of the receiver illustrated in FIG. Note that the flowchart shown in FIG. 23A shows the operation from when the application execution unit 435 outputs (issues) the storage method to the method reception unit 501 until the return value is acquired. The flowchart shown in FIG. 23B shows the operation from when the application execution unit 435 outputs (issues) the inquiry method to the method reception unit 501 until the return value is acquired. The flowchart shown in FIG. 23C shows the operation from when the application execution unit 435 outputs (issues) the list information acquisition method to the method reception unit 501 until the return value is acquired.

  In FIG. 23A, the application execution unit 435 outputs (issues) a storage method based on the application being executed (step S10). The method reception unit 501 outputs an application request instruction including an argument (application ID) of the storage method received from the application execution unit 435 to the application acquisition unit 520.

  The application acquisition unit 520 acquires location information indicating the storage location of the application program with the application ID included in the application request instruction from a predetermined repository (external server) via the communication input / output unit 411 (step S12). ). The application acquisition unit 520 associates the application ID included in the application request instruction acquired in step S10 with the location information acquired in step S12, and writes it in the application storage unit 431 (step S14).

  Further, the application acquisition unit 520 outputs response information (acquisition result) to the application request instruction to the method reception unit 501. The method reception unit 501 outputs the return value of the storage method corresponding to the response information acquired from the application acquisition unit 520 to the application execution unit 435. The application execution unit 435 acquires the return value of the saved method from the method reception unit 501 (step S16). Then, the flowchart of FIG.

  In FIG. 23B, the application execution unit 435 outputs (issues) an inquiry method based on the application being executed (step S20). The method reception unit 501 outputs an application search instruction including an argument (application ID) of the inquiry method received from the application execution unit 435 to the in-cache search unit 570.

  The in-cache search unit 570 searches the application storage unit 431 for the application ID included in the application search instruction (step S22). The in-cache search unit 570 outputs response information (search result) to the application search instruction to the method reception unit 501. The method reception unit 501 outputs the return value of the inquiry method corresponding to the response information acquired from the cache search unit 570 to the application execution unit 435. The application execution unit 435 acquires the return value of the inquiry method from the method reception unit 501 (step S24). Then, the flowchart of FIG. Thereby, it is possible to notify the application through the API whether or not information related to the specific application is stored in the application storage unit 431.

  In FIG.23 (c), the application execution part 435 outputs (issues) a list information acquisition method based on the application in execution (step S10). The method reception unit 501 outputs an application list information acquisition instruction to the cache search unit 570.

  The in-cache search unit 570 acquires all application IDs stored in the application storage unit 431 (step S32). The cache search unit 570 outputs response information (application ID) to the application list information acquisition instruction to the method reception unit 501. The method reception unit 501 outputs the response information acquired from the cache search unit 570 to the application execution unit 435 as a return value of the list information acquisition method (step S34). The application execution unit 435 acquires the return value of the list information acquisition method from the method reception unit 501 (step S34). Then, the flowchart of FIG. Accordingly, a list of information related to the application stored in the application storage unit 431 can be notified to the application through the API through the API. For example, a list of applications for which location information has been acquired from the repository can be displayed.

  The above is an embodiment in which the receiver 4 stores (stores in the application storage unit 431) the location information and the application program (application code). According to this, it is possible to speed up the activation of the application based on the information cached therein (application program or location information). In addition, information cached internally can be displayed as a list.

  As another embodiment, there is an embodiment in which the receiver 4 stores only the location information without storing the application program itself. In the form in which only the location information is stored, the receiver 4 appropriately acquires a desired application program using the location information and executes it without storing it. According to this, it is possible to speed up the activation of the application as compared with the case where the location information is not cached inside. In addition, information cached internally (location information) can be displayed as a list.

  The application execution control unit 412 and the presentation control unit 413 of the receiver 4 described above have a computer system therein. The operation processes of the application execution control unit 412 and the presentation control unit 413 of the receiver 4 are stored in a computer-readable recording medium in the form of a program, and this program is read and executed by the computer system. The above processing is performed. The computer system here includes a CPU, various memories, an OS, and hardware such as peripheral devices.

The “computer-readable recording medium” refers to a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor disk (SSD), a semiconductor memory, and the like.
Alternatively, the computer program may be distributed to the computer by broadcasting or a communication line, and the computer that has received the distribution may execute the program. Further, the program may be for realizing a part of the above processing, and may be capable of realizing the above-described processing in combination with a program already recorded in a computer system.

DESCRIPTION OF SYMBOLS 1 ... Broadcast provider apparatus 11 ... Broadcast transmission apparatus 111 ... Broadcast related data management part 112 ... Signal setting part 113 ... Broadcast transmission part 12 ... Broadcasting station server group 13 ... Content management server 14 ... Program management server 15 ... Metadata management server 16 ... Content distribution server 17 ... Broadcasting station service server 18 ... Notification server 2 ... Service provider server group 21 ... Receiver application server 22 ... Service server 23 ... Content distribution server 24 ... Notification server 3 ... Repository server 4 ... Receiver 401 ... broadcast receiving section 402 ... separating section 403 ... clock 404-1 ... first synchronization buffer 404-2 ... second synchronization buffer 405-1 ... first decoder 405-2 ... second decoder 406 ... data broadcast execution section 407 ... Video control unit 408 ... Video display unit 409 ... Audio control unit 410 ... Audio output unit 411 ... Communication input / output Unit 412 ... Application execution control unit 413 ... Presentation control unit 414 ... Operation input unit 415 ... Channel selection unit 416 ... Local information storage unit 417 ... External I / F unit 431 ... Application storage unit 432 ... Application authentication unit 433 ... Application management unit 434 Application control unit 435 Application execution unit 436 Receiver API unit 437 Terminal cooperation API unit 438 Resource access control unit 439 Resource control unit 451 Policy data management unit 452 Policy data storage unit 453 Event interpretation unit 454 ... Policy level matching unit 455 ... Event control unit 456 ... Program policy storage unit 457 ... Policy mediation unit 458 ... Policy level storage unit 501 ... Method reception unit 520 ... Application acquisition unit 570 ... In-cache search unit 9 Communications network

Claims (3)

An application storage unit for storing information about the application program;
An application execution unit that executes an application program read from the application storage unit;
And methods accepting unit that accepts a Rume Sod requested from the application execution unit by the execution of the application program,
Based on the inquiry method in cache in an application where the method accepting unit accepts, it searches the application storage unit, and the cache search unit returns whether the specified application exists in the application execution unit,
An application acquisition unit that acquires information on another application program different from the application program that requested the storage method based on a storage method in the cache of the application received by the method reception unit, and writes the information to the application storage unit; ,
A receiver comprising:   The application execution unit
  When the application program specified by the inquiry method does not exist in the application storage unit, the storage method specifying the application is requested,
  The application acquisition unit
  The receiver according to claim 1, wherein information related to a specified application program is acquired and written into the application storage unit. The method reception unit
In-cache application list information acquisition method requested from the application execution unit by executing the application program,
The cache search unit
Based on the cached application list information acquisition method received by the method receiving unit, read out list information related to applications stored in the application storage unit, and return to the application execution unit,
The receiver according to claim 1 or 2 , characterized by the above.

Images