JP6826865B2 - Terminal devices and programs - Google Patents

Description

The present invention relates to terminal devices and programs.

In recent years, research and development on systems for realizing broadcast communication cooperation services have been actively carried out. Hybridcast is one of Japan's representative broadcasting and communication cooperation services, and its technical specifications have been established (see, for example, Non-Patent Documents 1 and 2). In accordance with the standard of this technical specification, the hybrid cast service has been started in 2013. For example, a service by a broadcast managed application described using HTML (Hypertext Markup Language) 5 is provided by a plurality of broadcasting stations. "Application" is an abbreviation for an application program, and is also referred to as "application" below. A broadcast managed application is an application in which a life cycle such as activation, termination, and forced termination is controlled by using a control signal of a broadcasting service transmitted from a broadcasting transmitting side.

In hybrid cast, it is possible to use a function in which a receiving device such as a television and a terminal device such as a smartphone or tablet are linked. In the following, the terminal device linked with the receiving device is also described as a linked terminal. As a specific example of the cooperation function, it is possible to send and receive text messages between a broadcast managed application executed on a TV and a Web (web) application running on a companion application installed on a terminal device. it can.

"IPTV Regulations Broadcast Communication Cooperation System Specification IPTVFJ STD-0010 2.1 Edition", IPTV Forum, March 7, 2016 "IPTV Regulations HTML5 Browser Specification IPTVFJ STD-0011 2.2 Edition", IPTV Forum, March 7, 2016

In the current hybrid cast standard, an application that displays the web application of the URL (Universal Resource Locator) specified from the broadcast managed application on the TV side on the companion application of the terminal device and presents it on both the TV and the terminal device. Works together. When performing this cooperative operation, it has been desired to use information on the cooperative operation performed in the past.

The present invention has been made in consideration of such circumstances, and collects a log related to a cooperative operation in a terminal device that cooperates with an application executed in a broadcast receiving device to provide a broadcast communication cooperation service. Provide terminal devices and programs capable of

One aspect of the present invention is an individual communication unit that communicates with a receiving device that performs a process of outputting content data included in a broadcast signal and a process of executing an application that provides a plurality of services by operating in cooperation with the broadcast signal. A service application, which is an application that provides the service of the above, is executed by a plurality of service execution units that execute the received message, a service execution management unit that operates the plurality of service execution units in parallel, and the reception device. A process of outputting a message issued from the application and received by the communication unit to the service execution unit of the destination, and outputting a message issued from the service execution unit to the receiving device or other service execution units. It is a terminal device including a message control unit that performs at least one of processing, and a log management unit that acquires log data related to the message that is the target of processing in the message control unit.

Further, one aspect of the present invention is the terminal device described above, and the log management unit acquires information about a broadcasting service being received by the receiving device, which is obtained from the message received by the communication unit. , Characterized by.

Further, one aspect of the present invention is the terminal device described above, further comprising a sensor unit for detecting information on the state of the terminal device or the environment of the terminal device, and the log management unit detects by the sensor unit. It is characterized by acquiring log data related to the result.

Further, one aspect of the present invention is the terminal device described above, wherein the log management unit acquires log data relating to a connection state with the receiving device.

Further, one aspect of the present invention is the terminal device described above, wherein the log management unit acquires log data relating to an execution state of the service application by the service execution unit.

Further, one aspect of the present invention is the terminal device described above, wherein the log management unit acquires log data relating to a history of access made by the service execution unit by executing the service application. It is a feature.

Further, one aspect of the present invention is the terminal device described above, further comprising a remote control unit that outputs a control signal to the receiving device via the communication unit according to a user operation, and the log management unit is the remote controller. It is characterized in that log data relating to the user operation performed in the unit is acquired.

Further, one aspect of the present invention is the terminal device described above, wherein the log management unit acquires log data related to a broadcasting service instructed to receive by the user operation.

Further, one aspect of the present invention is the terminal device described above, wherein the log management unit stores the acquired log data in a log storage unit included in the terminal device, and a log for accumulating log data. It is characterized in that at least one of the processing of transmitting to an external device provided with a storage unit via the communication unit is performed.

Further, one aspect of the present invention is the terminal device described above, wherein the log management unit is provided with an external log storage unit that adds user identification information to the acquired log data and stores the log data. It is characterized in that it is transmitted to the device via the communication unit.

Further, one aspect of the present invention is the terminal device described above, further comprising a log access control unit that reads log data instructed to be acquired from the service execution unit from the log storage unit and returns the log data. And.

Further, one aspect of the present invention is to operate a computer, a plurality of service execution means for executing a service application, which is an application for providing individual services, using a received message, and a plurality of the service execution means in parallel. Issued by the service execution management means, the application executed in the receiving device that performs the process of outputting the content data included in the broadcast signal and the process of executing the application that provides a plurality of services by the operation linked with the broadcast signal. A message control means that performs at least one of a process of outputting the message to the destination service execution means and a process of outputting the message issued from the service execution means to the receiving device or the other service execution means. , A program that functions as a terminal device including a log management means for acquiring log data related to the message that is the target of processing in the message control means.

According to the present invention, it is possible to collect a log related to a cooperative operation in a terminal device that cooperates with an application executed in a broadcast receiving device to provide a broadcast communication cooperation service.

It is an overall block diagram of the broadcasting communication cooperation system by one Embodiment of this invention. It is a stack figure of the receiving device and the cooperation terminal by the same embodiment. It is a functional block diagram which shows the internal structure of the receiving device by this embodiment. It is a functional block diagram which shows the detailed structure of the application execution part by the same embodiment. It is a functional block diagram which shows the structure of the cooperation terminal by the same embodiment. It is a functional block diagram which shows the detailed structure of the log management part by the same embodiment. It is a figure which shows the example of the broadcaster determination database by the same embodiment. It is a figure which shows the example of the user policy setting information by the same embodiment. It is a figure which shows the example of the business operator policy setting information by the same embodiment. It is a functional block diagram which shows the detailed structure of the message control part by the same embodiment. It is a figure which shows the description example of the broadcast managed application by the same embodiment. It is a figure which shows the setting example of the message by the same embodiment. It is a figure which shows the processing flow of the message control part by the same embodiment. It is a figure which shows the processing flow of the message control part by the same embodiment. It is a sequence diagram in the case of transmitting a message between a receiving device and a cooperation terminal by the same embodiment. It is a sequence diagram in the case of transmitting a message between web services by the same embodiment. It is a figure which shows the setting example of the message by the same embodiment. It is a sequence diagram in the case of transmitting a message based on a session identifier between a receiving device and a linked terminal according to the same embodiment. It is a sequence diagram in the case of transmitting a message based on a session identifier between a receiving device and a linked terminal according to the same embodiment. It is a figure which shows the setting example of the message by the same embodiment. It is a sequence diagram in the case of transmitting a message based on a session identifier between the web applications of the linked terminal according to the same embodiment. It is a sequence diagram in the case of transmitting a message based on a session identifier between the web applications of the linked terminal according to the same embodiment.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Hereinafter, the "application program" is also referred to as an "application" or an "app". Further, in the following description, executing the process specified by the instruction described in the application may be simply referred to as "execution of the application" or "execution of the application".

FIG. 1 is an overall configuration diagram of a broadcast communication cooperation system 1 according to an embodiment of the present embodiment. The broadcast communication cooperation system 1 includes a broadcast transmission device 2, a service server 3, a reception device 4, a cooperation terminal 5, and a log server 6. The broadcast transmission device 2, the service server 3, and the log server 6 are devices on the transmission side, and the reception device 4 and the cooperation terminal 5 are devices on the reception side.

The broadcast transmission device 2 transmits a broadcast signal. The service server 3 distributes the application body and the content data used by the application to the device on the receiving side via the Internet. The application body is an application program. The receiving device 4 is, for example, a hybrid cast compatible television. The cooperation terminal 5 is, for example, a terminal device such as a smartphone or a tablet terminal. The receiving device 4 and the cooperation terminal 5 can communicate with each other with the service server 3 via the Internet. Further, the receiving device 4 and the cooperation terminal 5 are connected via a local network such as a wireless LAN (Local Area Network). The log server 6 stores the log data collected by the cooperation terminal 5. When the log data is stored only in the cooperation terminal 5, the broadcasting communication cooperation system 1 does not have to include the log server 6.

There are a plurality of forms of the broadcast communication cooperation service, but in the broadcast communication cooperation system 1 of the present embodiment, the digital broadcasting service and the Internet service are provided in the receiving device 4 based on the hybrid cast technical specifications (Non-Patent Documents 1 and 2). Is assumed to work together. When the receiving device 4 executes an application distributed by broadcasting or the Internet, the content on the Internet can be acquired, and the user can use the broadcasting communication cooperation service. Further, according to the hybrid cast technical specifications, the receiving device 4 and the terminal-side cooperation application installed in the cooperation terminal 5 operate in cooperation with each other.

In the present embodiment, the application that operates in the receiving device 4 is a broadcast managed application distributed by the broadcaster. The broadcast managed application controls the life cycle such as activation, termination, and forced termination based on the control signal of the broadcasting service transmitted from the broadcasting transmission device 2.

The terminal-side cooperation application implemented in the cooperation terminal 5 is a companion application that operates in cooperation with the reception device 4 which is another device connected by communication. The terminal-side cooperation application executes one or more service applications that operate in cooperation with the broadcast managed application executed by the receiving device 4.

The broadcast managed application and the service application operate in cooperation with each other to execute the service provided to the user. The service is to output the image, video, and sound of the result of the operation according to the operation performed by the user to the cooperation terminal 5 to the cooperation terminal 5, or to the receiving device 4 and the cooperation terminal 5. Information acquired from the receiver function of the receiving device 4 or the like is used to execute the service. The receiver function is a series of functions that receive a broadcast signal, acquire content data such as program video and audio of a channel selected by the user from the broadcast signal, decode it, and output it. The services provided to users are optional, but examples include providing information such as SNS (social network services), weather forecasts and news, providing foreign language subtitles, and presenting images from different angles than TV images. is there.

In the present embodiment, a case where the service application executed in the terminal-side cooperation application is a web application will be described as an example. A web app is an app that is run by a web browser. The web application is implemented on the cooperation terminal 5 by any means. For example, the web application may be an application instructed to be acquired from the broadcast managed application, an application acquired by user operation, or an application pre-installed in the cooperation terminal 5. Broadcast managed application and web application programs are described, for example, in HTML (Hypertext Markup Language).

FIG. 2 is a stack diagram of the receiving device 4 and the cooperation terminal 5. The receiving device 4 is composed of four layers: hardware, an OS (Operation System), a resident, and an application execution unit. The application execution unit is, for example, an HTML5 browser, and executes a broadcast managed application. The resident executed on the OS is equipped with a broadcast receiver function by software resident in the memory. The broadcast managed application executed by the application execution unit can access the receiver function of the resident through the extended API (Application Program Interface) defined by Non-Patent Document 1. The hardware includes a CPU (central processing unit), various memories, a tuner, a decoder, a communication device, a display device, an input device, and the like.

The cooperative terminal 5 is composed of three layers: hardware, an OS, and a native application execution unit. The native application execution unit executes an application provided by the OS of the terminal such as iOS (registered trademark) and Android (registered trademark). In the native application execution unit, multiple native applications can be operated. A native application is a program that can be executed on a specific OS or platform. The terminal-side cooperation application in this embodiment is a native application, and operates in the native application execution unit. The terminal-side cooperation application does not have to be a native application. For example, the terminal-side cooperation application may call a browser other than the native application from the native application and execute the web application by the browser. The hardware includes a CPU, various memories, a communication device, a display device, an input device, and the like.

The terminal cooperation function in the hybrid cast is realized between the broadcast managed application that operates in the application execution unit of the receiving device 4 and the web application that operates inside the terminal side cooperation application that is executed by the native application execution unit of the cooperation terminal 5. To. A text message is transmitted between the broadcast managed application and the web application using the extended API specified in Non-Patent Document 1. Any message content can be described in the text message. For example, the message content may be various execution commands to the application, additional information used when the application operates, or the like.

FIG. 3 is a block diagram showing an internal configuration of the receiving device 4, and only functional blocks related to the present embodiment are extracted and shown. The receiving device 4 shown in the figure includes a broadcast receiving unit 401, a separation unit 402, a video decoding unit 403, an audio decoding unit 404, a data broadcasting execution unit 405, a communication input / output unit 406, a remote control input control unit 407, and a power supply control unit 408. , App execution unit 409, application control unit 410, broadcast communication cooperation unit 411, terminal cooperation unit 412, video synthesis unit 413, video display unit 414, voice synthesis unit 415, and audio output unit 416.

The broadcast receiving unit 401 is a tuner, and receives and demodulates the broadcast signal transmitted from the broadcast transmitting device 2. The separation unit 402 separates the broadcast signal received and demodulated by the broadcast reception unit 401 into content data such as video data and audio data, and data other than the content data. Data other than content includes, for example, data broadcasting, receiving channels, SI (Service Information) in which program information is described, event messages, and the like. The video decoding unit 403 decodes the video data. The voice decoding unit 404 decodes the voice data. The data broadcasting execution unit 405 is a BML (Broadcast Markup Language) browser and executes data broadcasting.

The communication input / output unit 406 is an interface for connecting to a communication network. The communication input / output unit 406 connects to the service server 3 such as the application market, the account management server, and the application distribution server via the Internet or the like. Further, the communication input / output unit 406 connects to the cooperation terminal 5 via a local network such as a wireless LAN. The remote controller input control unit 407 receives data indicating an operation performed by the user on the remote controller from the remote controller (remote controller). The power supply control unit 408 controls the power supply of the receiving device 4.

The application execution unit 409 is a web (Web) browser that executes a broadcast managed application. Broadcast managed apps provide the functionality of one or more services. The application control unit 410 controls the start and end of the broadcast managed application based on the information contained in the data separated from the broadcast signal. For example, the application control unit 410 controls the broadcast managed application of the currently selected broadcaster (channel) based on the information set in the AIT separated from the broadcast signal. The application control unit 410 notifies the terminal cooperation unit 412 of the identification information of the started broadcast managed application.

The broadcast communication cooperation unit 411 provides the application execution unit 409 with a function defined by the extended API in order to cooperate and operate the contents acquired by broadcasting or communication in the broadcast managed application. Specifically, the broadcast communication cooperation unit 411 provides a means for accessing information such as SI and event messages included in the broadcast signal being received, functions provided by the receiving device 4, and the like. The terminal cooperation unit 412 performs a pairing process with the cooperation terminal 5 and a process of mediating communication between the broadcast managed application of the receiving device 4 and the web application of the cooperation terminal 5. The terminal cooperation unit 412 operates as a pair with the terminal cooperation unit 531 of the cooperation terminal 5 shown in FIG. 5, which will be described later. The terminal cooperation unit 412 notifies the cooperation terminal 5 of the identification information of the started broadcast managed application.

The video synthesis unit 413 synthesizes the video data of the broadcast program decoded by the video decoding unit 403 and the video data output based on the processing results of the data broadcasting execution unit 405 and the application execution unit 409, and displays the video data in the video display unit 414. Output. The video display unit 414 is a general display, and displays a video of video data synthesized by the video synthesis unit 413.

The voice synthesis unit 415 synthesizes the voice data of the broadcast program decoded by the voice decoding unit 404 and the voice data output based on the processing results of the data broadcast execution unit 405 and the application execution unit 409, and causes the voice output unit 416 to combine the voice data. Output. The voice output unit 416 is a general speaker, and outputs the voice data synthesized by the voice synthesis unit 415 by voice.

FIG. 4 is a functional block diagram showing a detailed configuration of the application execution unit 409. The application execution unit 409 has a service execution unit 421, a service execution management unit 422, and a message control unit 423. The application execution unit 409 may include a plurality of service execution units 421, but only one broadcast managed application operates at the same time. In the figure, a plurality of service execution units 421 included in the application execution unit 409 are described as service execution units 421-1, 421-2, 421-3, ..., Respectively.

The service execution unit 421 executes the service function included in the broadcast managed application based on the control by the application control unit 410. The service execution management unit 422 controls the start and end of each service execution unit 421 and manages the state, and causes a plurality of service execution units 421 to be executed in parallel.

The message control unit 423 controls for appropriately transmitting and receiving a message between the service function of the broadcast managed application executed by the service execution unit 421 and the web application executed by the cooperation terminal 5. The message control unit 423 includes a service identification management unit 4231, a message reception unit 4232, a message determination unit 4233, a message distribution unit 4234, and a source service setting unit 4235.

The service identification management unit 4231 manages a correspondence table between the identifier of the service execution unit 421 and the identifier of the service executed by the service execution unit 421, for example, in a list format. The service identifier is predetermined. In addition, each broadcast managed application adds a predetermined identifier for each service as a destination address by adding a prefix or the like to a part of the message to send and receive.

The message receiving unit 4232 receives the message from the cooperation terminal 5 and the message from the service executing unit 421. The message receiving unit 4232 transmits the received message to the message determination unit 4233 and the message distribution unit 4234. The message receiving unit 4232 may transmit only the information necessary for determining the destination to the message determination unit 4233.

The message determination unit 4233 collates the service identifier added to the message received from the message reception unit 4232 with the correspondence table stored in the service identification management unit 4231 to determine the message transmission destination, and determines the message distribution unit. Notify 4234. If the identifier of the source service and the identifier of the destination service added to the message are the same, the message determination unit 4233 uses the cooperation terminal 5 as the destination, and if they are different, the service execution unit 421 is the destination. .. Further, the message determination unit 4233 issues an identifier for establishing a communication channel between services and determines a message transmission destination based on the identifier, depending on the embodiment.

The message distribution unit 4234 transmits the message received from the message reception unit 4232 to the destination determined by the message determination unit 4233. The source service setting unit 4235 adds the identifier of the service of the broadcast managed application being executed by the service execution unit 421 to the message transmitted by the service execution unit 421 to the cooperation terminal 5 or another service execution unit 421. ..

FIG. 5 is a functional block diagram showing the configuration of the cooperative terminal 5, and only the functional blocks related to the present embodiment are extracted and shown. In the figure, the functional configuration centering on the terminal-side cooperation application is shown. The cooperation terminal 5 has a hardware unit 51, an OS unit 52, a cooperation application execution control unit 53, and another application execution control unit 54.

The hardware unit 51 includes various hardware such as a CPU, various memories, a communication device, a display (display device), and an input device (input device) for inputting user operations. When the display is a touch panel, the input device is a touch sensor arranged on the touch panel. The hardware unit 51 includes a communication input / output unit 511 realized by a communication device and various sensors 512. In the figure, n sensors (n is a natural number) are described as sensors 521-1 to 512-n.

The communication input / output unit 511 is an interface for connecting to a communication network. The communication input / output unit 511 connects to the service server 3 and the log server 6 via the Internet or the like. Further, the communication input / output unit 511 connects to the receiving device 4 via a local network such as a wireless LAN. The sensor 512 detects information about the state of the cooperation terminal 5 and the environment in which the cooperation terminal 5 exists. The sensor 512 is, for example, a GPS (Global Positioning System), an acceleration sensor, a temperature sensor, a magnetic sensor, a brightness sensor, a proximity sensor, and the like, but is not limited thereto.

The OS unit 52 is realized by the OS, controls the entire terminal, and provides the linked application execution control unit 53 and the other application execution control unit 54 with an interface to the hardware unit 51.

The linked application execution control unit 53 is realized by the CPU reading and executing the terminal-side linked application stored in the memory. The linked application execution control unit 53 includes a terminal cooperation unit 531, a service execution unit 532, a service execution management unit 533, a message control unit 534, an ID management unit 551, a connection status management unit 552, a remote control unit 553, a log management unit 554, and a log. It has an access control unit 555, a user policy setting unit 556, and a business operator policy setting unit 557. The plurality of service execution units 532 are described as service execution units 532-1, 532-2, 532-3, ..., Respectively.

The terminal cooperation unit 531 performs a pairing process with the receiving device 4 and a process of mediating communication between the broadcast managed application of the receiving device 4 and the web application of the cooperation terminal 5. The terminal cooperation unit 531 operates as a pair with the terminal cooperation unit 412 of the receiving device 4.

The service execution unit 532 executes a web application for providing individual services. Examples of the implementation method of the service execution unit 532 include WebView on an Android (registered trademark) -equipped terminal and UIWebView on an iOS-equipped terminal. It is premised that there are a plurality of service execution units 532, and each service execution unit 532 is assigned a unique identifier and is also used as a service identifier. Each service execution unit 532 executes the following web application.

(1) A web application linked with the broadcast managed application of the receiving device 4 for which the service is actually provided. It is one service execution unit 532 that executes this web application.
(2) A web application that can be used in common by linking with a broadcast managed application distributed by multiple broadcasting stations.
(3) A web application that does not work with the receiver 4.

The service execution management unit 533 controls the start and end of each service execution unit 532 and manages the state, and causes a plurality of service execution units 532 to be executed in parallel. The service execution management unit 533 controls the start and end of the web application executed on the service execution unit 532 or the service execution unit 532 based on the instruction from the receiving device 4 or the user operation, and operates in the foreground. Or change the state such as operation in the background. In addition, the service execution management unit 533 manages one or both of the identification information of the provider of the running web application and the identification information of the web application. As the identification information of the provider of the web application, for example, the domain name from which the web application is acquired can be used.

The ID management unit 551 issues and manages individual user IDs. The user ID is, for example, identification information that uniquely identifies the user of the cooperation terminal 5, the terminal-side cooperation application mounted on the cooperation terminal 5, or the cooperation terminal 5. The user ID may be input by the user, or may be generated by the ID management unit 551 in cooperation with an external device.

The connection state management unit 552 detects whether or not the cooperation terminal 5 is in a connection state with the receiving device 4, and manages the state. The remote control unit 553 corresponds to the software remote control of the receiving device 4. Specifically, the remote control unit 553 has user interfaces such as channel buttons, color buttons, d buttons, up / down / left / right buttons, enter buttons, back buttons, volume buttons, and power buttons, and when the user operates them, the remote control unit 553 has a user interface. It has a function of issuing a command according to the operation and transmitting it to the receiving device 4 via the terminal cooperation unit 531 and the communication input / output unit 511.

The log management unit 554 manages a plurality of types of log data that can be acquired when the user uses the terminal-side cooperation application in an integrated manner. The log data includes information on the time when the log was obtained. The log access control unit 555 controls access to whether or not to allow the web application running in the service execution unit 532 to access various log data managed by the log management unit 554. The log access control unit 555 performs this access control based on the conditions set as the user policy in the user policy setting unit 556 and the conditions set as the business operator policy in the business operator policy setting unit 557.

The user policy setting unit 556 determines whether or not the log management unit 554 is authorized to manage various log data, and whether or not to authorize access to various log data from the web application. Has a function to set as. The user policy setting unit 556 writes the user policy data indicating the policy set by the user to the internal user policy storage unit 5651. The user policy storage unit 5651 may be provided outside the user policy setting unit 556. If the log storage unit that stores log data is installed in both the log management unit 554 of the linked terminal 5 and the cloud server such as the log server 6 connected via the Internet, which one is used. It is also possible to further set the policy to be set in the user policy setting unit 556. The log management unit 554 writes the acquired log data to the log storage unit 5542 in the log management unit 554 shown in FIG. 6 to be described later, or transmits the acquired log data to the log server 6 according to the policy stored in the user policy storage unit 5651. .. It is assumed that the function for the user to set the user policy is provided as a screen by the terminal-side cooperation application, and the user sets it via the graphical user interface (GUI) of the cooperation terminal 5.

The operator policy setting unit 557 has a function in which the broadcaster sets as a policy whether or not to approve access to the log data managed by the log management unit 554 from the web application. The approval or disapproval of access may be set for each business operator that provides the web application, or may be set for each web application or service. The operator policy setting unit 557 writes the operator policy data indicating the policy set by the broadcaster into the operator policy storage unit 5571 provided internally. This business operator policy data is updated by updating the terminal-side cooperation application or by transmitting data related to the business operator's policy from the service server 3 on the Internet to the cooperation terminal 5. Alternatively, the business operator policy setting unit 557 receives the business operator policy data acquired from the broadcast signal by the receiving device 4 via the communication input / output unit 511 and the terminal cooperation unit 531 and stores it in the business operator policy storage unit 5571. Business policy data may be updated. The business operator policy storage unit 5571 may be provided outside the business operator policy setting unit 557.

Log management in the linked terminal 5 will be described.
FIG. 6 is a diagram showing a detailed configuration of the log management unit 554. The log management unit 554 includes a log database unit 5541, a broadcast service determination unit 5543, a log access API providing unit 5544, and an external management interface unit 5545.

The log database unit 5541 is a database that acquires log data from each functional unit of the terminal-side cooperation application and manages the acquired log data. The log database unit 5541 has a log writing process for writing log data acquired from other functional units to the log storage unit 5542, and a log reading process for reading log data stored in the log storage unit 5542 and outputting it to other functional units. Perform processing. The log server 6 may be provided with a functional unit that operates as a log database unit 5541. The functional unit in which the log database unit 5541 acquires the log data and the log data specifically acquired from the functional unit are shown below.

(1) The log database unit 5541 acquires log data indicating the state of which service execution unit 532 or the web application is being executed from the service execution management unit 533. There are two possible state acquisition methods: a case where the service execution management unit 533 periodically transmits the state, and a case where the state is transmitted only when the state changes.

(2) The log database unit 5541 acquires connection information indicating the state of whether or not the cooperation terminal 5 is connected to the receiving device 4 as log data from the connection state management unit 552. There are two possible state acquisition methods: a case where the connection state management unit 552 periodically transmits the state, and a case where the state is transmitted only when the state changes. This log data is used to determine whether the cooperation terminal 5 can cooperate with the receiving device 4.

(3) The log database unit 5541 acquires the operation history of the user by the user interface provided by the remote controller unit 553 as log data from the remote controller unit 553. For example, the broadcast channel was selected by pressing the number keys, the hybrid cast or data broadcasting was activated by pressing the d button, and the reception was received by pressing the power button. It is used to detect that the power supply of the device 4 has been turned on / off. Here, the remote control unit 553 notifies the log database unit 5541 of log data indicating the event (button operation by the user) when an event that the button is pressed is issued.

(4) The log database unit 5541 may send and receive messages from the message control unit 534 between the broadcast managed application of the receiving device 4 and the web service of the linked terminal 5 or between the web services of the linked terminal 5, and the receiving device 4 and the linked terminal. A command to be transmitted / received between the message control units 423 of 5 is acquired, and the acquired message or information related to the command is used as log data. For example, the log data includes at least a part of information that identifies the source of the message or command, information that identifies the destination of the message or command, and information about the content of the message or command. The information regarding the content of the message or command is information obtained by performing arbitrary data processing on all or part of the content of the message or command, or all or part of the content of the message or command. For example, in order to acquire the value of setURLForCompanionDevice sent from the broadcast managed application of the receiving device 4 to the terminal cooperation unit 531 in order to start the web application of the cooperation terminal 5 from the command, and to detect which broadcasting station the service is. Can be used for. The value of setURLForCompanionDevice specifically indicates the URL (Universal Resource Locator) of the web application to be started. Specific examples of messages will be described later.

(5) The log database unit 5541 acquires log data indicating the detection result of the sensor 512 from various sensors 512 such as GPS, an acceleration sensor, and a brightness sensor mounted on the hardware of the cooperation terminal 5.

(6) The log database unit 5541 is executed by the service execution unit 532, the execution status of the web application, the history of access to the service server 3 performed by the web application executed by the service execution unit 532, and the service execution unit 532. The operation history data performed by the user while providing the web application to be executed is acquired as log data. The operation history data is, for example, a history of screen operations such as tapping and swiping.

The log database unit 5541 writes the collected log data in the log storage unit 5542 in association with the user ID acquired from the ID management unit 551 in addition to the time information. The user ID is a user ID, a device ID, a terminal-side cooperation application ID, or the like. Further, the log database unit 5541 adds a log ID for identifying each log data and a log type indicating the type of the log data to the log data, and writes the log data to the log storage unit 5542. An example of the log type will be described with reference to FIG. 8 described later.

The broadcast service determination unit 5543 provides a function of determining the broadcast service being received by the receiving device 4 based on the operation history data acquired from the remote controller unit 553 and the value of setURLForCompanionDevice () acquired from the message control unit 534. To do. The details of the method for determining the broadcasting service will be described later. The log access API providing unit 5544 provides an API for the web application executed by the service execution unit 532 to access the log database unit 5541.

The external management interface unit 5545 controls communication with the log server 6 when the log data is stored in the log server 6. FIG. 6 shows a case where the cooperation terminal 5 implements the log database unit 5541, but a case where the same function as the log database unit 5541 is implemented in the log server 6 on the cloud connected to the communication network is considered. Be done. When the log server 6 implements the same function as the log database unit 5541, the external management interface unit 5545 periodically or logs the log data collected by the log database unit 5541 and stored in the log storage unit 5542. Each time data is generated, it is read out and transmitted to the log server 6. Alternatively, the cooperation terminal 5 may not provide the log database unit 5541, and the external management interface unit 5545 may directly transmit the log data acquired from each functional unit including the connection state management unit 552 to the log server 6.

Next, a method in which the broadcast service determination unit 5543 determines the broadcast service being received by the receiving device 4 will be described. The following three data can be mentioned as the data used for the determination.

(1) The operation history data received from the remote controller unit 553 is used. When the user selects the broadcast service of the receiving device 4 by using the cooperation terminal 5, it is conceivable that the remote control unit 553 operates a number key or the like displayed on the display. The data of the number keys pressed by this operation is transmitted from the remote controller unit 553 to the broadcast service determination unit 5543. The broadcast service determination unit 5543 determines the broadcaster or channel based on the number keys. When the operation history indicating that the number keys have been operated is output from the remote control unit 5543, the broadcast service determination unit 5543 sets the information of the broadcaster or channel determined based on the number keys, and the log data of the viewing history. Is generated and output to the log database unit 5541.

(2) The value of the URL received from the receiving device 4 is used. If the broadcast managed application is running on the receiving device 4 and the terminal cooperation service is provided, use the setURLForCompanionDevice () function from the broadcast managed application to the terminal side cooperation application on the terminal side cooperation application. It is conceivable to send the URL of the web application to be operated by the command. When the message control unit 534 receives the command, the message control unit 534 transmits the URL value acquired from the received command to the broadcast service determination unit 5543. The broadcast service determination unit 5543 determines the broadcaster based on the information included in the URL, such as the domain name. The broadcast service determination unit 5543 generates log data of the viewing history in which the information of the determined broadcaster is set and outputs the log data to the log database unit 5541.

(3) The viewing history data received from the receiving device 4 is used. The broadcast managed application of the receiving device 4 acquires the values of the service_id and event_id of the broadcasting service being received as viewing history data, and transmits them to the linked terminal 5 using the sendTextToCompanionDevice () function. In this case, when the message control unit 534 receives the service_id or event_id by the message transmitted from the broadcast managed application, the message control unit 534 transmits the value to the broadcast service determination unit 5543. The broadcast service determination unit 5543 determines the broadcaster based on the value of service_id and the value of event_id obtained from the content of the message. The broadcast service determination unit 5543 generates log data of the viewing history in which the information of the determined broadcaster is set and outputs the log data to the log database unit 5541.

FIG. 7 is a diagram showing an example of a broadcaster determination database implemented by the broadcast service determination unit 5543. The broadcast service determination unit 5543 determines the broadcaster of the channel being received by the receiving device 4 with reference to the broadcaster determination database. A unique operator ID is assigned to all broadcasters in advance. In broadcasting, the channel number input by the remote controller, that is, the broadcasting company assigned to the number keys differs depending on the region. Therefore, a broadcaster judgment table will be set up for each region. Each broadcaster judgment table uses the broadcaster's operator ID as the primary key, and supports the broadcaster name, service_id, domain name of the URL sent from the broadcast managed application using the setURLForCompanionDevice () function, and number keys. Attach and store in the record. There may be multiple domain names and service_ids corresponding to one business ID.

In advance, the user sets in the cooperation terminal 5 which area the receiving device 4 is used in. Alternatively, the broadcast service determination unit 5543 may acquire regional information based on the GPS output included in the cooperative terminal 5. The broadcasting service determination unit 5543 determines a table to be referred to among the broadcasting operator determination tables constituting the broadcasting operator determination database based on the information of the area. When the numerical key, the value of the URL from the receiving device 4, and the viewing history data from the receiving device 4 are input, the broadcasting service determination unit 5543 provides the broadcasting service with reference to the determined broadcaster determination table. The broadcaster is identified and notified to the log database department 5541.

Next, the relationship between the log management unit 554 and the log access control unit 555 will be described. When the web application being executed by the service execution unit 532 uses the log data stored in the log database unit 5541, it calls the API for log access. When this API provided by the log access API provider 5544 is called, or when the log data read from the log database section 5541 by the log access API provider 5544 is passed to the service execution section 532 as the result of the API call. In addition, the log access control unit 555 refers to the user policy setting information and the business operator policy setting information to determine whether or not to provide the log data to the web application, and executes the access control.

FIG. 8 is a diagram showing an example of user policy setting information stored in the user policy storage unit 5651. The user policy setting information uses the information of the item indicating the log type as a key, and corresponds to each item, whether or not to authorize the log management and whether or not to authorize the access from the web application, respectively. Consists of the indicated records. The information of the item used as the key is indicated by the log type that identifies the item of the log and the item name. In the figure, approval is “1” and denial is “0”. If the log management is "0", the log access is also set to "0". An example of each item is shown below. The user policy setting information set here is notified to the log access control unit 555, and the log access control unit 555 executes access control for each API as follows according to the user policy setting information.

(1) The item "service usage history" is log data indicating information on which service was used, and is obtained from the service execution management unit 533.
(2) The item "Web browsing history" is log data indicating information on the URL of the acquisition destination when the service execution unit 532 accesses the web page provided by the service server 3, and is obtained from the service execution unit 532. ..
(3) The item "screen operation history" is log data indicating the operation history of the web application, and is obtained from the service execution unit 532.
(4) The item "connection state with the television" is log data indicating the connection state with the cooperation terminal 5, and is obtained from the connection state management unit 552.
(5) The item "remote control operation history" is log data indicating the operation history of the user with respect to the remote control unit 553, and is obtained from the remote control unit 553.
(6) The item "viewing history" is log data indicating the history of the broadcasting service received by the receiving device 4, and is obtained from the broadcasting service determination unit 5543.
(7) The item "GPS" corresponds to log data obtained from GPS, which is one of the sensors 512.
(8) The item "acceleration sensor" corresponds to the log data obtained from the acceleration sensor which is one of the sensors 512.

The log database unit 5541 discards the log data of the item for which "0" is set in the log management of the user policy setting information without writing it in the log storage unit 5542, and "1" is set in the log management. The log data of the item is written in the log storage unit 5542. Further, the log access control unit 555 does not approve the access from the service execution unit 532 for the log data of the item for which "0" is set in the log access of the user policy setting information.

The log access control unit 555 authorizes the use of the log data of the item for which "1" is set in the log access of the user policy setting information from the service execution unit 532. However, among the log data managed by the log database unit 5541 of the log management unit 554, the log access control unit 555 is a business operator for the log data of the viewing history recorded via the broadcast service determination unit 5543. Access control from the web application is performed according to the setting information of the policy setting unit 557. The viewing history includes the time from the start to the end of reception of each broadcasting service.

FIG. 9 is a diagram showing an example of the business policy setting information stored in the business policy storage unit 5571. The business policy setting information is composed of a business policy setting table for each region. The operator policy setting table for each region uses information indicating a broadcaster similar to the broadcaster determination table for that region as shown in FIG. 7 as a key. That is, the operator policy setting table shown in FIG. 9 uses the operator ID, the broadcaster name, the broadcaster domain (own station domain), and the number keys as keys to access the viewing history of each broadcaster. The domain of the web application to be authorized is described.

The business operator policy setting unit 557 reads the business operator policy setting table corresponding to the area set in the cooperation terminal 5 from the business operator policy storage unit 5571 and notifies the log access control unit 555. The log access control unit 555 executes access control to the log data from the service execution unit 532 according to the setting of the notified business operator policy setting table. In the following, the application acquired from the service server 3 with the URL including the domain "XXX" as the acquisition destination will be described as the application of the domain "XXX".

For example, the broadcaster "AAA Tokyo" can view the viewing history of its broadcast from its own domain "aaa.co.jp" web application and the third party domain "xyz.co.jp" web application. Authorize access to the indicated log data. In addition, the broadcaster "CCC" authorizes access to log data showing the viewing history of its own broadcast from web applications of all domains.

Further, the log access control unit 555 may control access to not only the viewing history but also the log data related to the web application or service of each business operator by using the business operator policy setting information. For example, in the case of the operator policy setting information shown in FIG. 9, the broadcaster "AAA Tokyo" has a web application of its own domain "aaa.co.jp" and a third party domain "xyz.co.jp". Authorize access to log data about web apps in your domain from your web app. In addition, the broadcaster "CCC" authorizes access to log data related to the web application of its own domain from the web application of all domains. The log data related to the web application is, for example, log data such as a service used, a web browsing history, and a screen operation history. Therefore, the log data related to the web application includes information such as the ID of the service provided by the web application, the URL of the acquisition destination of the web application, or the identification of the business operator (for example, domain or business operator ID) obtained from the URL. Is included or added.

In the operator policy setting information shown in FIG. 9, the information of the domain that authorizes the use of the viewing history is set for each broadcaster, but the information of the domain that does not authorize the use of the viewing history is set. You may. In addition, in the above, the domain that permits or does not approve the use of viewing history is set for each broadcaster in the operator policy setting information, but the operator or web application that permits or does not approve the use of viewing history. , The service may be set for each broadcaster. When each business operator further controls access to the use of log data related to the web application or service provided by the company, the business operator policy setting information permits the use of log data for each business operator's web application or service. Or set information on domains, businesses, web apps, and services that are not authorized. As a result, the log access control unit 555 calls the API for log access to approve or reject access to log data related to all or part of the web applications or services provided by a certain broadcaster according to the operator policy setting information. Control based on the web application, the domain of the web application, the business operator that provides the web application, or the service provided by the web application.

Next, transmission and reception of messages between the receiving device 4 and the cooperation terminal 5 will be described.
In the hybrid cast, an API for transmitting and receiving a text message between the receiving device 4 and the cooperation terminal 5 is defined. The message control unit 534 appropriately transmits and receives messages between the broadcast managed application executed by the receiving device 4 and the web application executed by each service execution unit 532 of the cooperation terminal 5 and between the service execution unit 532. To control. The details of the message control unit 534 will be described with reference to FIG.

FIG. 10 is a functional block diagram showing a detailed configuration of the message control unit 534. The message control unit 534 includes a service identification management unit 5341, a message reception unit 5342, a message determination unit 5343, a message distribution unit 5344, and a source service setting unit 5345.

The service identification management unit 5341 manages a correspondence table between the identifier of the service execution unit 532 and the identifier of the web service which is a service provided by the web application executed by the service execution unit 532, for example, in a list format. The identifier of the web service is predetermined. In addition, each web service sends and receives by adding a predetermined identifier for each web service as a destination address to a part of the message by adding a prefix or the like.

The message receiving unit 5342 receives the message from the receiving device 4 and the message from each service executing unit 532. The message receiving unit 5342 transmits the received message to the message determination unit 5343 and the message distribution unit 5344. The message receiving unit 5342 may transmit only the information necessary for determining the destination to the message determination unit 5343.

The message determination unit 5343 collates the service identifier added to the message received from the message reception unit 5342 with the correspondence table stored in the service identification management unit 5341 to determine the message transmission destination, and determines the message distribution unit. Notify 5344. The message determination unit 5343 uses the receiving device 4 as the transmission destination when the identifier of the source service and the identifier of the destination service added to the message are the same, and sets the service execution unit 532 as the transmission destination when they are different. .. Further, depending on the embodiment, the message determination unit 5343 issues an identifier for establishing a communication channel between services and determines a message transmission destination based on the identifier.

The message distribution unit 5344 transmits the message received from the message reception unit 5342 to the destination determined by the message determination unit 5343. The source service setting unit 5345 adds the identifier of the source service execution unit 532 to the message transmitted by the service execution unit 532 to the receiving device 4 or another service execution unit 532.

As described above, there is only one broadcast managed application executed by the receiving device 4. Therefore, in order to execute a plurality of services with one broadcast managed application, a program for executing each of the plurality of services is described in one HTML document (application program). For example, in addition to the service A in the current broadcast managed application provided by the broadcasting station A, it is assumed that the service X commonly provided by the broadcasting station A and the broadcasting station B is operated at the same time. At this time, the function of the service X is described in JavaScript (registered trademark) or the like in the HTML document of the service A provided by the broadcasting station A and in the HTML document of the service B of the broadcasting managed application provided by the broadcasting station B. Further, since a plurality of services individually send and receive messages between devices, the function of the service execution management unit 422 having the same function as the service execution management unit 533 of the cooperation terminal 5 and the same as the message control unit 534 of the cooperation terminal 5 The function of the message control unit 423 having the function of is described in the HTML document of both the services of the service A and the service B in the same manner as the function of the service X. The functions of the service execution management unit 422 include control of starting and ending of the service execution unit 421, and control of whether or not to display on the screen for each service.

FIG. 11 is a diagram showing a description example of a broadcast managed application. The figure is an example in which the broadcast managed application of broadcasting station A is described as an HTML document. As shown in the figure, the elements to be displayed for service A and service X are grouped in the div, and the id is specified (serviceA, common_serviceX). The function of each service executed by the service execution unit 421 is described in JavaScript (registered trademark) and included in the head part (serviceA.js, common_serviceX). Further, the service execution management unit 422 controls functions such as starting and terminating the service execution unit 421 (common_appcontrol.js), the message control unit 423 function (common_messaging.js), and the service execution management unit 422 displays each service. The control function (common_viewcontrol.js) of is also included. When the application execution unit 409 executes the broadcast managed application described as the HTML document in this way, the application execution unit 409 operates as the service execution unit 421, the service execution management unit 422, and the message control unit 423. As a result, the same functions are introduced into both the broadcast managed application on the receiving device 4 and the companion application on the linked terminal 5, so that a plurality of services can be used on the pair of receiving devices 4 and the linked terminal 5. Become.
The function unit that operates as the service execution management unit 422, the message control unit 423, and the service execution unit 421 may be mounted in advance in the application execution unit 409 of the receiving device 4.

The service execution management unit 533 of the cooperation terminal 5 starts or stops the web application by the service execution unit 532 according to the instruction from the receiving device 4 or the instruction input by the user to the cooperation terminal 5. Specifically, when a service start instruction is output from the broadcast managed application executed by the application execution unit 409 of the receiving device 4, the terminal cooperation unit 412 sets the cooperation terminal 5 as the transmission destination and sets the communication input / output unit 406 as the transmission destination. Send a service start instruction via. The service start instruction includes information that identifies the web application to be started. As a service start instruction, for example, a command by the setURLForCompanionDevice () function is used. The terminal cooperation unit 531 of the cooperation terminal 5 outputs the service start instruction received via the communication input / output unit 511 to the service execution management unit 533. The service execution management unit 533 starts the web application instructed to start by the received service start instruction. Alternatively, when the user inputs the information of the web application to be activated by the input device of the cooperation terminal 5, the service execution management unit 533 activates the web application to be activated. As a result, the service execution unit 532 operates in the cooperation application execution control unit 53.

FIG. 12 shows an example of a message.
FIG. 12A shows a service in which the service execution unit 421 executing the function of the service P of the broadcast managed application in the receiving device 4 executes the web application of the service P in the terminal-side cooperation application of the cooperation terminal 5. Indicates the message M11 transmitted to the execution unit 532. FIG. 12B shows the service execution from the service execution unit 532, which is executing the web application of service P in the terminal-side cooperation application of the cooperation terminal 5, to execute the web application of service Q in the terminal-side cooperation application. The message M21 transmitted to the unit 532 is shown. The message M11 is a message described by the service execution unit 421 executing the function of the service P of the broadcast managed application, and the message M12 is described by the service execution unit 532 executing the web application of the service P. Message. In the messages M11 and M21, the identifier (dst: ServiceP, dst: ServiceQ) of the destination service and the message body (message) are described.

The message M12 shown in FIG. 12C and the message M22 shown in FIG. 12D are messages received by the message receiving unit 5342 of the cooperation terminal 5. The message M12 is the message M11 with the identifier of the source service P (src: ServiceP) added, and the message M22 is the message M21 with the identifier of the source service P (src: ServiceP) added. It is a thing.

Specifically, the source service setting unit 4235 of the receiving device 4 adds the identifier of the source service P to the message M11 to become the message M12. In the case of the message M12, the identifier of the source service is set by the function of the source service setting unit 4235 (common_messaging.js in FIG. 11) of the message control unit 423 generated by executing the broadcast managed application. To. On the other hand, in the case of the message M22, the source service setting unit 5345 of the cooperation terminal 5 adds the identifier of the source service P to the message M21.

The message format is not limited to these description examples. Further, in the present embodiment, only the identifier of the service of the transmission source and the identifier of the service of the transmission destination are described, but the receiving device 4 or the cooperation terminal 5 may be described as the transmission destination.

13 and 14 are processing flows showing the operations of the message control unit 423 and the message control unit 534. In the following, the message control unit 534 will be described as an example, but the message control unit 423 also operates in the same manner.

FIG. 13 shows a processing flow at the time of receiving a message. The terminal cooperation unit 531 of the cooperation terminal 5 outputs a message received from the reception device 4 via the communication input / output unit 511 to the message reception unit 5342. The message receiving unit 5342 receives a message from the terminal cooperation unit 531 (step S105). The message receiving unit 5342 detects the identifier of the destination service and the identifier of the source service from the received message (step S110). The message receiving unit 5342 notifies the message determination unit 5343 of the identifier of the destination service read by the message and the identifier of the source service, and notifies the message distribution unit 5344 of the entire message (step S115).

The message determination unit 5343 requests the service identification management unit 5341 to collate whether or not the service execution unit 532 is executing the service specified by the identifier of the destination service (step S120). The service identification management unit 5341 acquires the identifier of the service execution unit 532 registered in the correspondence table in association with the identifier of the destination service notified from the message determination unit 5343. The service identification management unit 5341 outputs a collation result for setting the identifier when the identifier of the service execution unit 532 can be acquired, and outputs a collation result indicating that the service execution unit 532 does not exist when the identifier cannot be acquired.

When the message determination unit 5343 determines that it has received a collation result indicating that there is a service execution unit 532 that executes the service specified by the identifier of the destination service from the service identification management unit 5341 (step S125: yes). , Step S130 is performed. That is, the message determination unit 5343 notifies the message distribution unit 5344 to notify the service execution unit 532 that is executing the web service specified by the identifier of the destination service described in the message to transmit the message. (Step S130). The message distribution unit 5344 transmits a message to the service execution unit 532 specified by the identifier of the destination service described in the message according to the instruction of the message determination unit 5343 (step S135).

On the other hand, if the message determination unit 5343 determines that the service identification management unit 5341 has received a collation result indicating that there is no service execution unit 532 that executes the service specified by the identifier of the destination service (step S125: No). ), The process of step S140 is performed. That is, the message determination unit 5343 performs predetermined error processing such as returning an error to the source of the message (step S140).

FIG. 14 shows a processing flow at the time of issuing a message. The service execution unit 532 sets a message and notifies the source service setting unit 5345 (step S205). The source service setting unit 5345 adds the identifier of the service being executed by the service execution unit 532 of the message transmission source as the sender identifier to the received message, and notifies the message reception unit 5342 ( Step S210). The message receiving unit 5342 notifies the message determination unit 5343 of the identifier of the destination service read from the message and the identifier of the sending source service, and notifies the message distribution unit 5344 of the entire message (step S215).

The message determination unit 5343 determines whether or not the identifiers of the transmission destination and the transmission source are the same (step S220). When the message determination unit 5343 determines that the identifiers of the transmission destination and the transmission source are the same (step S225: Yes), the message determination unit 5343 transmits a message to the message distribution unit 5344 to the receiving device 4 via the terminal cooperation unit 531. (Step S230). The message distribution unit 5344 outputs a message to the terminal cooperation unit 531 according to the instruction of the message determination unit 5343, and the terminal cooperation unit 531 receives the message received from the message distribution unit 5344 via the communication input / output unit 511. It is transmitted to 4 (step S240).

On the other hand, when the message determination unit 5343 determines that the identifiers of the transmission destination and the transmission source are not the same (step S225: No), the process of step S235 is performed. That is, the message determination unit 5343 reads out the identifier of the service execution unit 532 registered in the correspondence table corresponding to the identifier of the destination service described in the message from the service identification management unit 5341. The message determination unit 5343 transmits a message to the service execution unit 532 specified by the read identifier, that is, the service execution unit 532 executing the web service specified by the identifier of the destination service described in the message. The message distribution unit 5344 is notified to do so (step S235). The message distribution unit 5344 transmits a message to the service execution unit 532 designated as a transmission destination by the message determination unit 5343 (step S240).

FIG. 15 is a sequence diagram between the receiving device 4 and the cooperation terminal 5. The service execution unit 421 of the receiving device 4 issues a message in which the identifier of the service executed by the cooperation terminal 5 is set as the destination (step S305). The source service setting unit 4235 sets the identifier of the source service in the message received from the service execution unit 421 and outputs the identifier to the message receiving unit 4232 (step S310). The message receiving unit 4232 notifies the message determination unit 4233 of the identifier of the source service and the identifier of the destination service acquired from the message (step S315), and notifies the entire message to the message distribution unit 4234 (step S320). .. Since the identifier of the source service and the identifier of the destination service are the same, the message determination unit 4233 notifies the message distribution unit 4234 to transmit the message to the cooperation terminal 5 (step S325). The message distribution unit 4234 outputs a message to the terminal cooperation unit 412 (step S330), and the terminal cooperation unit 412 transmits the message to the cooperation terminal 5 via the communication input / output unit 406.

The communication input / output unit 511 of the cooperation terminal 5 outputs the message received from the receiving device 4 to the terminal cooperation unit 531 (step S335). The message receiving unit 5342 receives a message from the terminal cooperation unit 531 (step S340). The message receiving unit 5342 notifies the message determination unit 5343 of the identifier of the source service and the identifier of the destination service acquired from the message (step S345), and notifies the entire message to the message distribution unit 5344 (step S350). .. When the message determination unit 5343 receives the collation result indicating the existence of the web service specified by the identifier of the destination service from the service identification management unit 5341, the message determination unit 5343 performs the process of step S355. That is, the message determination unit 5343 instructs the message distribution unit 5344 to output a message to the service execution unit 532 executing the web service specified by the identifier of the destination service (step S355). The message distribution unit 5344 outputs a message to the service execution unit 532 instructed by the message determination unit 5343 (step S360).

Although FIG. 15 shows an example of transmitting a message from the receiving device 4 to the cooperation terminal 5, the message transmission from the cooperation terminal 5 to the receiving device 4 can also be executed by the same procedure.

FIG. 16 is a sequence diagram when a message is transmitted between the web applications of the cooperative terminal 5. In the figure, the service execution unit 532-1 is described as the service execution unit (1), and the service execution unit 534-2 is described as the service execution unit (2).

The service execution unit 532-1 issues a message in which the identifier of the service being executed by the service execution unit 534-2 is set as the destination (step S405). The source service setting unit 5345 sets the identifier of the source service in the message received from the service execution unit 532-1 and outputs it to the message reception unit 5342 (step S410). The message receiving unit 5342 notifies the message determination unit 5343 of the identifier of the source service and the identifier of the destination service acquired from the message (step S415), and notifies the entire message to the message distribution unit 5344 (step S420). .. Since the identifier of the source service and the identifier of the destination service are different, the message determination unit 5343 transmits a message to the service execution unit 532-2 that executes the web service specified by the identifier of the destination service. Notify the message distribution unit 5344 to do so (step S425). The message distribution unit 5344 outputs a message to the service execution unit 532-2 instructed by the message determination unit 5343 (step S430).

Although FIG. 16 shows a case where a message is transmitted between the web applications of the cooperative terminal 5, the same procedure can be executed when a message is transmitted between the service execution units 421 of the receiving device 4.

In the above-described examples of FIGS. 12 to 16, the identifier of the source service and the identifier of the destination service are added to all the messages for transmission, but the embodiment in which the identifier of the channel between the services is added. It doesn't matter. In this case, before starting messaging between the service of the broadcast managed application of the receiving device 4 and the web service of the linked terminal 5, or between the web services of the linked terminal 5, a connection process is executed between the services. Establish a channel. After that, the receiving device 4 and the cooperation terminal 5 transmit a message based on the identifier of the session assigned in the established channel without adding the identifiers of the source and the destination until the process of disconnection is executed. To do.

FIG. 17 is a diagram showing an example of setting a message when a message is transmitted between the service of the broadcast managed application of the receiving device 4 and the web service of the cooperation terminal 5 based on the identifier of the session. 17 (a) is a connection registration message M31, FIG. 17 (b) is a connection registration confirmation message M32, FIG. 17 (c) is a connection disconnection message M33, and FIG. 17 (d) is a connection disconnection confirmation message M34. , FIG. 17 (e) shows the message M35 in which the message body is set.

The connection registration message M31, the connection registration confirmation message M32, the connection disconnection message M33, the connection disconnection confirmation message M34, and the message M35 include a type attribute. By this type attribute, it is possible to identify whether the message is registered (publish) / registration confirmation (subscribe) / disconnection (unpublish) / disconnection confirmation (unsubscribe) / message body (body).

Further, in the connection registration message M31, the connection registration confirmation message M32, the connection disconnection message M33, and the connection disconnection confirmation message M34, the identifier of the source service (src) and the identifier of the destination service (dst) are set to connect. The registration confirmation message M32 and the disconnection confirmation message M34 further describe the identifier (subscribe_ID) of the session assigned to the established channel. The source and destination are not set in the message M35 in which the message body (message) is set, and the session identifier (subscribe_ID) and the message content (message) are described.

18 and 19 are sequence diagrams in the case where a message is transmitted between the receiving device 4 and the cooperation terminal 5 based on the session identifier.

FIG. 18 shows a sequence of connection registration processing. The service execution unit 421 of the receiving device 4 issues a connection registration message (step S505). The connection registration message issued by the service execution unit 421 includes a type attribute in which "publish" indicating that the connection registration message is set is set, and a dst attribute in which the identifier of the destination service is set. The source service setting unit 4235 adds a src attribute in which the identifier of the source service is set to this message. The source service setting unit 4235 outputs the connection registration message to which the src attribute is added to the message receiving unit 4232 (step S510).

The message receiving unit 4232 notifies the message determination unit 4233 of the identifier of the destination service and the identifier of the source service set in the connection registration message (step S515), and sends the entire connection registration message to the message distribution unit 4234. Notify (step S520). Since the message determination unit 4233 has the same identifier for the service of the transmission destination and the transmission source, the message determination unit 4233 notifies the message distribution unit 4234 to transmit the message to the cooperation terminal 5 (step S525). The message distribution unit 4234 outputs a connection registration message to the terminal cooperation unit 412 (step S530), and the terminal cooperation unit 412 outputs the connection registration message received from the message distribution unit 4234 to the cooperation terminal via the communication input / output unit 406. Send to 5.

The communication input / output unit 511 of the cooperation terminal 5 receives a message from the receiving device 4 and outputs it to the terminal cooperation unit 531 (step S535). The message receiving unit 5342 receives a message from the terminal cooperation unit 531 (step S540). The message receiving unit 5342 outputs the received message to the message determination unit 5343 (step S545). When the message determination unit 5343 determines that the connection registration message is based on the type attribute of the received message, it issues a subscribe_ID and stores it in association with the identifiers of the source and destination services. A new subscribe_ID may be issued each time the connection is disconnected, or a predetermined subscribe_ID may be assigned to the source-destination pair. Further, the message determination unit 5343 generates a connection registration confirmation message. The connection registration confirmation message includes the type attribute in which "subscribe" indicating the connection registration confirmation message is set, the issued subscribe_ID, and the dst attribute and src attribute set in the connection registration confirmation message. The message determination unit 5343 notifies the message distribution unit 5344 of the generated connection registration confirmation message, and instructs the reception device 4 to transmit the message (step S550).

The message distribution unit 5344 outputs the connection registration confirmation message to the terminal cooperation unit 531 (step S555), and the terminal cooperation unit 531 transmits the connection registration confirmation message to the receiving device 4 via the communication input / output unit 511 (step S555). Step S560).

The communication input / output unit 406 of the receiving device 4 outputs the message received from the cooperation terminal 5 to the terminal cooperation unit 412. The message receiving unit 4232 receives a message from the terminal cooperation unit 412 (step S565). The message receiving unit 4232 determines from the type attribute of the received message that it is a connection registration confirmation message. The message receiving unit 4232 outputs the subscribe_ID acquired from the connection registration confirmation message and the identifiers of the source and destination services to the message determination unit 4233 (step S570). The message determination unit 4233 registers the subscribe_ID and the identifiers of the source and destination services in association with each other. Further, the message receiving unit 4232 notifies the service executing unit 421 executing the broadcast managed application specified by the identifier of the destination service of the connection registration confirmation message with the subscribe_ID (step S575).

FIG. 19 shows a sequence of message transmission processing. The service execution unit 421 of the receiving device 4 issues a message in which the message body is set (step S605). The message includes a type attribute in which "body" indicating that it is the message body is set, subscribe_ID according to the destination service, and the message content. The source service setting unit 4235 sets the identifier of the source service in the message received from the service execution unit 421. It is not necessary to set the identifier of the source service. The source service setting unit 4235 outputs a message in which the identifier of the source service is set to the message receiving unit 4232 (step S610).

The message receiving unit 4232 notifies the message determination unit 4233 of the subscribe_ID set in the message (step S615), and notifies the entire message to the message distribution unit 4234 (step S620). Since the message determination unit 4233 has the same identifier of the destination and the source service stored in correspondence with the subscribe_ID, the message distribution unit 4234 notifies the message distribution unit 4234 to transmit the message to the cooperation terminal 5 (step S625). The message distribution unit 4234 outputs a message to the terminal cooperation unit 412 (step S630), and the terminal cooperation unit 412 transmits the message received from the message distribution unit 4234 to the cooperation terminal 5 via the communication input / output unit 406. ..

The communication input / output unit 511 of the cooperation terminal 5 outputs the message received from the receiving device 4 to the terminal cooperation unit 531 (step S635). The message receiving unit 5342 receives a message from the terminal cooperation unit 531 (step S640). When the message receiving unit 5342 determines that the message is the main body based on the type of the received message, the message receiving unit 5342 outputs the subscribe_ID read from the message to the message determining unit 5343 (step S645) and outputs the message to the message distributing unit 5344 (step S650). ). Since the source and destination service identifiers corresponding to subscribe_ID are the same, the message determination unit 5343 outputs a message to the service execution unit 532 that is executing the service specified by the destination service identifier. Message distribution unit 5344 is instructed (step S655). The message distribution unit 5344 outputs a message to the service execution unit 532 instructed by the message determination unit 5343 (step S660).

Although FIGS. 18 and 19 show an example of transmitting a message from the receiving device 4 to the cooperation terminal 5, the message transmission from the cooperation terminal 5 to the receiving device 4 can also be executed by the same procedure.

FIG. 20 is a diagram showing a description example of a message when a message is transmitted between the web applications of the cooperative terminal 5 based on the session identifier. 20 (a) is a connection registration message M41, FIG. 20 (b) is a connection registration confirmation message M42, FIG. 20 (c) is a connection disconnection message M43, and FIG. 20 (d) is a connection disconnection confirmation message M44. , FIG. 20E shows a message M45 in which a message body is set. The attributes included in the messages of M41 to M45 are the same as the messages of M31 to M35 shown in FIG. 17, respectively.

That is, the connection registration message M41, the connection registration confirmation message M42, the connection disconnection message M43, the connection disconnection confirmation message M44, and the message M45 include the type attribute. Further, in the connection registration message M41, the connection registration confirmation message M42, the connection disconnection message M43, and the connection disconnection confirmation message M44, the identifier of the source service (src) and the identifier of the destination service (dst) are set to connect. The registration confirmation message M42 and the disconnection confirmation message M44 further describe the identifier (subscribe_ID) of the session assigned to the established channel. The source and destination are not set in the message M45 in which the message body (message) is set, and the session identifier (subscribe_ID) and the message content (message) are described.

21 and 22 are sequence diagrams in the case of transmitting a message between the web applications of the cooperative terminal 5 based on the session identifier. This sequence has no basic procedure differences from the sequences shown in FIGS. 18 and 19. However, when transmitting a message between the receiving device 4 and the cooperation terminal 5, the cooperation terminal 5 transmits and receives from the message distribution unit 5344 via the terminal cooperation unit 531. However, in the case of between web applications, the message is transmitted. A message is transmitted from the distribution unit 5344 to the message reception unit 5342 in the cooperation terminal 5, and the same processing is subsequently executed.

FIG. 21 shows a sequence of connection registration processing between the web applications of the linked terminal 5. The service execution unit 532-1 of the cooperation terminal 5 issues a connection registration message (step S705). In the connection registration message issued by the service execution unit 532-1, the type attribute in which "publish" indicating that the connection registration message is set is set, and the identifier of the destination service executed by the service execution unit 534-2. Contains the dst attribute with the set. The source service setting unit 5345 adds a src attribute in which the identifier of the source service is set to this message. The source service setting unit 5345 outputs a connection registration message to which the src attribute has been added to the message receiving unit 5342 (step S710).

The message receiving unit 5342 notifies the message determination unit 5343 of the identifier of the destination service and the identifier of the source service set in the connection registration message (step S715), and sends the entire connection registration message to the message distribution unit 5344. Notify (step S720). Since the message determination unit 5343 has different identifiers for the service of the transmission destination and the transmission source, the message determination unit 5343 notifies the message distribution unit 5344 to transmit the message to the message reception unit 5342 (step S725). The message distribution unit 5344 outputs the connection registration message to the message reception unit 5342 (step S730).

The message receiving unit 5342 outputs the received message to the message determination unit 5343 (step S735). When the message determination unit 5343 determines that the connection registration message is based on the type of the received message, it issues a subscribe_ID and stores it in association with the identifiers of the source and destination services. Further, the message determination unit 5343 generates a connection registration confirmation message. The message determination unit 5343 notifies the message distribution unit 5344 of the generated connection registration confirmation message, and instructs the message reception unit 5342 to transmit the message (step S740). The message distribution unit 5344 outputs a connection registration confirmation message to the message reception unit 5342 (step S745).

The message receiving unit 5342 outputs the subscribe_ID acquired from the received connection registration confirmation message and the identifiers of the source and destination services to the message determination unit 5343 (step S750). The message determination unit 5343 registers the subscribe_ID and the identifiers of the source and destination services in association with each other. Further, the message receiving unit 5342 notifies the service executing unit 532-1 executing the web application specified by the identifier of the destination service of the connection registration confirmation message with the subscribe_ID (step S755).

FIG. 22 shows a sequence of message transmission processing between the web applications of the linked terminal 5. The service execution unit 532-1 of the cooperation terminal 5 issues a message in which the message body is set (step S805). The source service setting unit 5345 sets the identifier of the source service in the message received from the service execution unit 532-1. It is not necessary to set the identifier of the source service. The source service setting unit 5345 outputs a message in which the identifier of the source service is set to the message receiving unit 5342 (step S810).

The message receiving unit 5342 notifies the message determination unit 5343 of the subscribe_ID set in the message (step S815), and notifies the entire message to the message distribution unit 5344 (step S820). Since the message determination unit 5343 has different identifiers of the destination and source services stored corresponding to the subscribe_ID, the service execution unit 532-2 that executes the web service specified by the identifier of the destination service. Notifies the message distribution unit 5344 to send a message to (step S825). The message distribution unit 5344 outputs a message to the service execution unit 532-2 instructed by the message determination unit 5343 (step S830).

Although FIGS. 21 and 22 show a case where a message is transmitted between the web applications of the linked terminal 5, the same procedure is used for transmitting a message between services executed by the broadcast managed application in the receiving device 4. it can.

According to the embodiment described above, the broadcast communication cooperation system 1 has a receiving device 4 and a cooperation terminal 5 (terminal device). The receiving device 4 executes a process of outputting content data included in a broadcast signal and a process of executing an application (broadcast managed application) that provides a plurality of services by operating in cooperation with the broadcast signal. The cooperation terminal 5 includes a communication input / output unit 511 (communication unit), a plurality of service execution units 532, a service execution management unit 533, a message control unit 534, and a log management unit 554. The communication input / output unit 511 communicates with the receiving device 4. Each service execution unit 532 executes a service application (web application), which is an application that provides an individual service, using the received message. The service execution management unit 533 operates a plurality of service execution units 532 in parallel. The message control unit 534 is issued from the application executed in the receiving device 4, and outputs the message received by the communication input / output unit 511 to the destination service execution unit 532, and the message issued from the service execution unit 532. At least one of the processing of outputting the above to the receiving device 4 or another service execution unit 532. The log management unit 554 acquires log data related to the message to be processed by the message control unit 534.

In addition, the log management unit 554 acquires information about the broadcasting service being received by the receiving device 4 obtained from the message received by the communication input / output unit 511. Information about the broadcasting service is, for example, an event, a viewing history, and the like. In addition, the log management unit 554 includes log data related to the detection result of the status of the linked terminal 5 or the environment of the linked terminal 5 by the sensor 512 (sensor unit), log data related to the connection status with the receiving device 4, and service execution unit 532. The log data related to the execution status of the service application and the log data related to the history of access made by the service execution unit 532 by executing the service application are acquired. Further, the cooperative terminal 5 includes a remote control unit 553 that outputs a control signal to the receiving device 4 via the communication input / output unit 511 according to a user operation, and the log management unit 554 is a user performed by the remote control unit 553. Acquire log data related to the operation. In addition, the log management unit 554 acquires log data related to the broadcasting service instructed to receive by the user operation.

The log management unit 554 has a process of accumulating the acquired log data in the log storage unit 5542 included in the cooperation terminal 5, and a communication input / output unit in the log server 6 which is an external device having a log storage unit for accumulating the log data. At least one of the processes of transmitting via 511 is performed. The log management unit 554 adds user identification information to the log data transmitted to the log server 6. The cooperation terminal 5 may further include a log access control unit 555 that reads and returns the log data instructed to be acquired from the service execution unit 532 from the log storage unit 5542 or the log server 6.

According to the embodiment described above, various logs can be acquired and managed in a linked terminal that provides a broadcast communication linked service such as hybrid cast. When linking with the receiving device, the linked terminal uses the broadcast managed application on the receiving device side and the remote control function of the linked terminal to acquire the viewing history such as the broadcasting channel or program identifier being received as a viewing log. be able to. In addition, the linked terminal can acquire the connection status of the receiving device and the data of the sensor of the hardware such as GPS even when the receiving device is not linked. Therefore, the action history of the user of the linked terminal can be acquired regardless of whether or not the linked device is linked. As a result, the behavior history of the user of the cooperative terminal can be permanently used not only when both the web application of the cooperative terminal and the broadcast managed application of the receiving device are operating. Then, it becomes possible to target contents and information related to broadcasting according to the situation of the user obtained from the collected log.

The above-mentioned receiving device 4 and the cooperation terminal 5 have a computer system inside. Then, a part of the operation process of the receiving device 4 and the cooperation terminal 5 is stored in a computer-readable recording medium in the form of a program, and the computer system reads and executes this program to perform the above processing. Will be done. The computer system referred to here includes hardware such as a CPU, various memories, an OS, and peripheral devices.

In addition, the "computer system" includes a homepage providing environment (or display environment) if a WWW system is used.
Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built in a computer system. Further, a "computer-readable recording medium" is a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line, and dynamically holds the program for a short period of time. In that case, it also includes the one that holds the program for a certain period of time, such as the volatile memory inside the computer system that becomes the server or client. Further, the above-mentioned program may be a program for realizing a part of the above-mentioned functions, and may further realize the above-mentioned functions in combination with a program already recorded in the computer system.

1 ... Broadcast communication cooperation system 2 ... Broadcast transmission device 3 ... Service server 4 ... Reception device 5 ... Cooperation terminal 6 ... Log server 51 ... Hardware unit 52 ... OS unit 53 ... Cooperation application execution control unit 54 ... Other application execution control unit 401 ... Broadcast receiving unit 402 ... Separation unit 403 ... Video decoding unit 404 ... Audio decoding unit 405 ... Data broadcasting execution unit 406 ... Communication input / output unit 407 ... Remote control input control unit 408 ... Power control unit 409 ... App execution unit 410 ... App Control unit 411 ... Broadcast communication cooperation unit 412 ... Terminal cooperation unit 413 ... Video synthesis unit 414 ... Video display unit 415 ... Voice synthesis unit 416 ... Audio output unit 421 ... Service execution unit 422 ... Service execution management unit 423 ... Message control unit 511 ... Communication input / output unit 512, 512-1, 512-n ... Sensor 531 ... Terminal cooperation unit 5321 to 532-3 ... Service execution unit 533 ... Service execution management unit 534 ... Message control unit 551 ... ID management unit 552 ... Connection status management unit 553 ... Remote control unit 554 ... Log management unit 555 ... Log access control unit 556 ... User policy setting unit 557 ... Operator policy setting unit 4231 ... Service identification management unit 4232 ... Message receiving unit 4233 ... Message judgment unit 4234 ... Message distribution unit 4235 ... Source service setting unit 5341 ... Service identification management unit 5342 ... Message reception unit 5343 ... Message judgment unit 5344 ... Message distribution unit 5345 ... Source service setting unit 5541 ... Log database unit 5542 ... Log storage unit 5543 ... Broadcast service judgment unit 5544 ... Log access API provision unit 5545 ... External management interface unit 5651 ... User policy storage unit 5571 ... Business operator policy storage unit

Claims (12)

A communication unit that communicates with a receiving device that performs processing to output content data included in a broadcast signal and processing to execute an application that provides a plurality of services by operating in cooperation with the broadcast signal.
Multiple service execution units that execute service applications, which are applications that provide individual services, using received messages, and
A service execution management unit that operates a plurality of the service execution units in parallel,
A process of outputting a message issued from the application executed in the receiving device and received by the communication unit to the service executing unit executing the destination service application, and executing the service application. a process of destination of the messages issued to other applications from the service execution unit determines whether said receiver device or other of the service execution unit, and outputs to the transmission destination is determined the message Message control unit that performs
A log management unit that acquires log data related to the message that is the target of processing in the message control unit, and a log management unit.
A terminal device characterized by comprising. The log management unit acquires information about a broadcasting service being received by the receiving device, which is obtained from the message received by the communication unit.
The terminal device according to claim 1. A sensor unit for detecting information on the state of the terminal device or the environment of the terminal device is further provided.
The log management unit acquires log data related to the detection result by the sensor unit.
The terminal device according to claim 1 or 2, wherein the terminal device is characterized by the above. The log management unit acquires log data related to the connection state with the receiving device.
The terminal device according to any one of claims 1 to 3, wherein the terminal device is characterized by the above. The log management unit acquires log data related to the execution state of the service application by the service execution unit.
The terminal device according to any one of claims 1 to 4, wherein the terminal device is characterized by the above. The log management unit acquires log data related to the history of access made by the service execution unit by executing the service application.
The terminal device according to any one of claims 1 to 5, characterized in that. A remote control unit that outputs a control signal to the receiving device according to a user operation via the communication unit is further provided.
The log management unit acquires log data related to the user operation performed on the remote controller unit.
The terminal device according to any one of claims 1 to 6, wherein the terminal device is characterized by the above. The log management unit acquires log data related to the broadcasting service instructed to receive by the user operation.
The terminal device according to claim 7. The log management unit has a process of accumulating the acquired log data in the log storage unit included in the terminal device and a process of transmitting the acquired log data to an external device including the log storage unit for accumulating the log data via the communication unit. Do at least one with
The terminal device according to any one of claims 1 to 8, wherein the terminal device is characterized by the above. The log management unit adds user identification information to the acquired log data, and transmits the log data to an external device including a log storage unit that stores the log data via the communication unit.
The terminal device according to any one of claims 1 to 8, wherein the terminal device is characterized by the above. It further includes a log access control unit that reads out the log data instructed to be acquired from the service execution unit from the log storage unit and returns the log data.
The terminal device according to claim 9 or 10. Computer,
A plurality of service execution means for executing a service application, which is an application for providing individual services, using received messages, and
A service execution management means for operating a plurality of the service execution means in parallel, and
The destination is a message issued by the application executed in the receiving device that performs the process of outputting the content data included in the broadcast signal and the process of executing the application that provides a plurality of services by the operation linked with the broadcast signal. The process of outputting to the service execution means executing the service application and the destination of the message issued from the service execution means executing the service application to the other application are the receiving device or the other. and message control means for the determining whether the service execution unit, and a process of outputting the message to have been the destination determination,
A log management means for acquiring log data related to the message to be processed by the message control means, and a log management means.
A program that functions as a terminal device equipped with.

Images