JP5695971B2 - Terminal linkage system and receiver - Google Patents

Description

The present invention relates to a terminal cooperation system having a receiver having a function of coordinating between broadcasting and communication and a terminal device capable of cooperating with the receiver.
Moreover, this invention relates to the receiver which comprises the said terminal cooperation system.

In recent years, with the progress of digitalization of broadcasting and broadbandization of communication, research and development for realizing a broadcasting / communication cooperation service has been performed.
In the broadcasting / communication cooperation service, it is assumed that a plurality of contents are distributed using different transmission paths of broadcasting and communication, and the plurality of distributed contents are integrated and presented in a receiver such as a digital television.

  In recent years, with the spread of terminal devices such as mobile phones, a terminal cooperation system in which a receiver and a terminal device cooperate with each other has been proposed (for example, see Non-Patent Document 1).

Hisato Kato, “Toward Hybridcast”, NHK R & D, No. 123, September 2010, P56-63

In the terminal cooperation system disclosed in Non-Patent Document 1, it is shown that the terminal device can cooperate using the function of the receiver to realize an additional service in the terminal device.
Here, in the terminal cooperation system disclosed in Non-Patent Document 1, the access permission level for the resources in the receiver is not set for each user who uses the terminal apparatus.

When the broadcasting / communication cooperation service is realized, it is predicted that the receiver is used not only for broadcast reception but also as an apparatus that uses communication.
As a result, resources such as personal information of the user and information necessary for payment using communication are accumulated in the receiver.

Under such circumstances, in a terminal cooperation system in which a receiver and a terminal device cooperate, a mechanism that can control access from the terminal device to resources accumulated in the receiver is desired.
That is, in the terminal cooperation system, a mechanism for controlling access from the terminal device to the resources in the receiver is required.

The present invention is a terminal cooperation system including a receiver and a terminal device, and is a terminal capable of controlling access from a terminal device to resources in the receiver by limiting the use of API (application program information) in the receiver. The purpose is to provide a linkage system.
An object of this invention is to provide the receiver which comprises the said terminal cooperation system.

  The present invention receives a program content signal formed by multiplexing program content and a plurality of pieces of information via broadcasting or communication, can output a token, and can cooperate with the receiver. A terminal cooperation system having a terminal device that requests the receiver to use a predetermined application program interface, the terminal device via a terminal device side communication unit and the terminal device side communication unit, Via the token receiving unit capable of receiving the token output from the receiver and the terminal device side communication unit, API usage request information including at least API identification information for identifying a predetermined application program interface is output to the receiver. If the token acceptance unit accepts a token, the predetermined API An API usage request output unit that outputs API usage request information including other information and the token to the receiver, the receiver via the receiver side communication unit and the receiver side communication unit, An API usage request receiving unit that receives API usage request information output from the API usage request output unit, an authority level management unit that stores at least authority level information and a token in association with each other, and one or a plurality of API identification information; An API usage level management unit that stores the usage level information set in each of the one or more API identification information in association with each other, and determines whether or not a token is included in the API usage request information. If it is determined that the token is included in the usage request information, whether or not the valid token is stored in the authority level management unit A determination unit for determining whether or not an API can be used, and when determining that the API use request information includes a token and determining that the valid token is stored in the authority level management unit; Based on the authority level information associated with the token in the management unit and the usage level information associated with the API identification information included in the API usage request information in the API usage level management unit, specified by the API identification information It is related with a terminal cooperation system provided with the API use availability judgment part which judges the availability of the application program interface used.

  In the terminal cooperation system, the terminal device includes a cooperation request output unit that outputs cooperation request information including user identification information for identifying the user or the terminal device to the receiver via the terminal device side communication unit. The receiver includes a cooperation request reception unit that receives the cooperation request information output from the cooperation request output unit via the receiver-side communication unit, and each of one or a plurality of user identification information. An authority level can be set, and an account management unit that stores one or a plurality of user identification information and the authority level information set for each of the user identification information, and the cooperation request information from the account management unit A token is issued via an authority level information acquisition unit that acquires authority level information associated with the user identification information included in the receiver and the receiver-side communication unit. A token output unit, and the authority level management unit stores the authority level information acquired by the authority level information acquisition unit in association with the token, and the token output unit stores the authority level management unit. Preferably, the token stored in association with the authority level information is output.

  In the terminal cooperation system, the authority level management unit stores guest authority level information that is not associated with a token, and the API availability determination unit determines that a token is not included in the API usage request information. If it is determined that the API use request information includes a token and it is determined that the valid token is not stored in the authority level management unit, the guest stored in the authority level management unit Whether or not the application program interface specified by the API identification information can be used based on the authority level information and the usage level information associated with the API identification information included in the API usage request information in the API usage level management unit Is preferably determined.

  In the terminal cooperation system, the terminal device includes a cooperation request output unit that outputs cooperation request information including user identification information for identifying the user or the terminal device to the receiver via the terminal device side communication unit. The receiver includes a cooperation request reception unit that receives the cooperation request information output from the cooperation request output unit via the receiver-side communication unit, and each of one or a plurality of user identification information. An authority level can be set, and an account management unit that stores one or a plurality of user identification information and the authority level information set for each of the user identification information, and the cooperation request information from the account management unit A token is issued via an authority level information acquisition unit that acquires authority level information associated with the user identification information included in the receiver and the receiver-side communication unit. A token output unit, and the authority level management unit stores the authority level information acquired by the authority level information acquisition unit in association with the token, and the token output unit stores the authority level management unit. Preferably, the token stored in association with the authority level information is output.

  In the terminal cooperation system, when the API availability determination unit determines that the API usage request information includes a token and determines that the valid token is stored in the authority level management unit The application specified by the API identification information based on the authority level information associated with the token in the authority level management unit and the usage level information associated with the API identification information in the API usage level management unit When it is determined that the use of the program interface is not permitted, it is preferable that information indicating that the specified application program interface cannot be used is output to the terminal device via the receiver-side communication unit.

  In addition, in the terminal cooperation system, when the API use permission determination unit determines that the API use request information does not include a token, the API use request determination unit determines that the API use request information includes a token and is effective. If it is determined that the token is not stored in the authority level management unit, the guest authority level information stored in the authority level management unit and the usage associated with the API identification information in the API usage level management unit When it is determined that the use of the specified application program interface is not permitted based on the level information, information indicating that the specified application program interface cannot be used via the receiver-side communication unit; Cooperation information output requesting output of the cooperation request information It is preferable to output the determined information, to the terminal device.

  The present invention receives a program content signal formed by multiplexing program content and a plurality of pieces of information via broadcasting or communication, can output a token, and can cooperate with the receiver. A receiver used in a terminal cooperation system having a terminal device that requests the receiver to use a predetermined application program interface, via the receiver-side communication unit and the receiver-side communication unit, An authority level management that stores at least authority level information and a token in association with each other, API usage request reception unit that receives API usage request information including API identification information for identifying at least a predetermined application program interface, output from the terminal device Part, one or more API identification information, and the one or more APIs An API usage level management unit that stores the usage level information set for each of the different information in association with each other, determines whether or not a token is included in the API usage request information, and includes a token in the API usage request information. An API availability determination unit that determines whether or not a valid token is stored in the authority level management unit when it is determined that the token is included in the API usage request information. And when it is determined that the token is stored in the authority level management unit, authority level information associated with the valid token in the authority level management unit, and the API usage level management unit Based on the usage level information associated with the API identification information included in the API usage request information. It relates to a receiver; and a determining API usage allowability determining unit availability of an application program interface that is specified by.

ADVANTAGE OF THE INVENTION According to this invention, it is a terminal cooperation system containing a receiver and a terminal device, Comprising: Access from the terminal device with respect to the resource in a receiver is controllable by restrict | limiting use of API (application program information) in a receiver. Terminal cooperation system can be provided.
Moreover, according to this invention, the receiver which comprises the said terminal cooperation system can be provided.

1 is an overall configuration diagram of a broadcasting / communication cooperation system. It is a figure which shows the stack | stuck of the transmission protocol of the broadcast signal which concerns on digital broadcasting. It is a block diagram which shows the function structure of a receiver. It is a figure which shows an example of AIT described in the XML format. It is a block diagram which shows the function structure of the receiver side cooperation management part in a terminal cooperation system, and a terminal device side cooperation management part. It is a figure which shows the user identification information-authority level information table memorize | stored in an account management part. It is a figure which shows the authority level information management table memorize | stored in an authority level management part. It is a figure which shows the API utilization level management table memorize | stored in an API utilization level management part. It is a figure for demonstrating an example of the availability of starting API in a user resource management application in a receiver, a display API, and a change API. It is a flowchart explaining operation | movement of a terminal device and a receiver in case a terminal device cooperates with a receiver. It is a flowchart explaining operation | movement of a terminal device and a receiver when utilization of starting API, display API, and change API in a user resource management application in a receiver is requested | required from the linked terminal device. It is a flowchart explaining operation | movement of a terminal device and a receiver when utilization of starting API, display API, and change API in a user resource management application in a receiver is requested | required from the unlinked terminal device.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is an overall configuration diagram of a broadcasting / communication cooperation system 100 according to an embodiment of the present invention. The broadcasting / communication cooperation system 100 includes a broadcasting station 1, a broadcasting antenna 2, a service server 3 (distribution server), and a receiver 4. In the broadcasting / communication cooperation system 100, a receiver 4 uses a broadcasting service provided from a broadcasting station 1 by an ISDB (Integrated Services Digital Broadcasting) system and a communication network N configured by the Internet or the like. The communication service provided from the service server 3 is linked to provide the user of the receiver 4 as a broadcasting / communication cooperation service.
In addition, the broadcasting / communication cooperation system 100 in this embodiment includes a terminal device 40 that cooperates with the receiver 4.
Here, the receiver 4 and the terminal device 40 cooperate with each other to configure the terminal cooperation system 200.

The broadcasting station 1 includes a general digital broadcasting broadcasting facility (not shown) configured to include a program organization facility, a program transmission facility, and a transmission facility.
The broadcasting station 1 produces contents, event information (Event Information Table: EIT), application management information (Application Information Table: AIT), and the like, using broadcasting equipment. Then, the broadcasting station 1 multiplexes these contents, event information, AIT, and the like into a broadcast signal by using broadcasting equipment. The broadcast station 1 modulates the broadcast signal into a broadcast wave by the broadcast facility, and broadcasts the broadcast wave via the broadcast antenna 2.

  The content included in the broadcast wave broadcast from the broadcast station 1 includes program content that is broadcast according to the broadcast schedule and includes video and audio, and earthquake early warnings that occur asynchronously with the program content. This includes emergency content that is content.

The event information includes meta information related to the content such as the name of the program content, the broadcast date and time of the program content, and the description of the program content. Hereinafter, the event information is referred to as EIT.
The AIT is management information for managing one or a plurality of application programs (hereinafter referred to as applications) that can provide the receiver 4 with content linked to program content. The AIT includes one or more pieces of individual management information corresponding to one or more applications and managing each of the one or more applications. The individual management information includes an application ID for identifying the application, life cycle control information for controlling the life cycle of the application, and location information indicating the location of the application (see FIG. 4).

  The content provided by the application includes content linked to the program content and content not linked to the program content. Hereinafter, content provided by an application is referred to as application content.

  The broadcast signal is the same as the broadcast signal of the conventional digital broadcast, and is defined by ARIB (registered trademark) (Association of Radio Industries and Broadcast) standard.

  FIG. 2 is a diagram illustrating a stack of broadcast signal transmission protocols related to digital broadcasting. As shown in FIG. 2, various types of data such as video and audio provided by digital broadcasting are stored in TS packets (transport stream packets) defined by the international standard MPEG-2 Systems and multiplexed in a time division manner. Is transmitted.

  In the TS packet, as shown in FIG. 2, PSI (Program Specific Information) / SI (Service Information) is defined for the section. PSI / SI includes information indicating the type of data stored in the TS packet and information indicating the type of content. The above-mentioned EIT is included in SI.

  Data transmission using TS packets is classified into a method of transmitting data using sections and a method of transmitting data using PES (Packetized Elementary Stream) packets (data stream transmission method).

  Methods for transmitting data using sections include a data carousel transmission method and an event message transmission method.

  The data carousel transmission method is a transmission method in which one or a plurality of data is repeatedly transmitted at a fixed period. Each piece of data (module) transmitted by this transmission method has identification information for identifying individual data. It is attached. The data carousel transmission system is used for the purpose of causing the receiver 4 to acquire individual data at an arbitrary timing.

  The event message transmission method is a method for sending a trigger signal from the broadcast station 1 to the receiver 4. The event message transmission method is used when a message with a small amount of data is transmitted from the broadcasting station 1 to the receiver 4.

  The data stream transmission method is a transmission method in which data to be transmitted is accommodated in a PES packet and transmitted as a stream. The data stream transmission method is used for transmitting real-time data such as video, audio, and caption data, and data that needs to be synchronized with other streams.

Here, AIT can be transmitted by various methods using TS packets.
That is, the AIT can be transmitted by describing the EIT included in the SI of the TS packet.

  The AIT can be transmitted by a data carousel transmission system using sections. When the AIT is transmitted by the data carousel transmission method, identification information is attached to the module so that the receiver 4 can recognize the AIT.

  The AIT can be transmitted as PES multiplexed with content video and audio.

The AIT can be described in binary representation or text representation by XML (Extensible Markup Language) and stored in the TS packet.
In this embodiment, the AIT transmission method is defined in advance in at least one of the above transmission methods.

  Multimedia coding language (BML) is based on xHTML defined by W3C (registered trademark) (World Wide Web Consortium), and procedural language is based on JavaScript (registered trademark). This is a standard defined in consideration of consistency with international standards.

  Although not shown, the service server 3 is a content distribution server that distributes program content and content (application content) distributed to applications, and an application distribution server that distributes various applications that operate on the receiver 4. With.

The service server 3 is communicably connected to the equipment of the broadcast station 1 and receives program content and program content metadata from the broadcast station 1.
The service server 3 transmits the program content to the receiver 4 in response to receiving the program content acquisition request from the receiver 4.

  Further, the service server 3 transmits the application to the receiver 4 in response to receiving the application acquisition request from the receiver 4. Furthermore, the service server 3 transmits video data, audio data, and the like of application content to the receiver 4 when an application is being executed in the receiver 4.

  Further, the service server 3 multiplexes the AIT with the program content and transmits it to the receiver 4. Further, the service server 3 transmits an AIT to the receiver 4 in response to receiving an AIT acquisition request from the receiver 4.

  The receiver 4 synchronizes and outputs the video data and audio data of the program content by performing predetermined processing on the program content received from the broadcast station 1 or through communication with the service server 3. . The receiver 4 acquires an application based on the AIT, and executes the acquired application. Subsequently, the receiver 4 acquires the video data and audio data of the application content from the service server 3 by the application being executed, and outputs the video data and audio data of the program content in cooperation with each other. Hereinafter, functions of the receiver 4 will be described in detail.

FIG. 3 is a block diagram illustrating a functional configuration of the receiver 4.
The receiver 4 includes a broadcast wave reception unit 11, a first separation unit 12, a broadcast AIT acquisition unit 13, a receiver-side communication unit 14, a second separation unit 15, a communication AIT acquisition unit 16, and application execution. Control unit 17, voice control unit 18, display control unit 19, speaker 20, display 21, memory 22, AIT storage unit 23, application storage unit 24, receiver side cooperation management unit 70, An API utilization unit 91 and a resource management unit 95 are provided.

  The broadcast wave receiving unit 11 receives a broadcast wave broadcast from the broadcast station 1 via the broadcast antenna 2.

  The first separation unit 12 demodulates the broadcast wave received by the broadcast wave reception unit 11 and extracts a broadcast signal, that is, a TS packet from the broadcast wave. Then, the first separation unit 12 refers to the PSI / SI of the TS packet, determines the type of data included in the TS packet, and extracts various data such as video, audio, and EIT. In addition, the first separation unit 12 extracts the AIT by referring to the section and the PES according to a predetermined AIT transmission method.

  Subsequently, when the data included in the PES of the TS packet is audio data, the first separation unit 12 outputs the audio data to the audio control unit 18. In addition, when the data included in the PES of the TS packet is video data, the first separation unit 12 outputs the video data to the display control unit 19.

  Further, the first separation unit 12 stores the extracted EIT and other various data in the memory 22. Further, when the first separation unit 12 extracts the AIT, the first separation unit 12 outputs the extracted AIT to the broadcast AIT acquisition unit 13.

  The broadcast AIT acquisition unit 13 acquires the AIT output from the first separation unit 12 and stores it in the AIT storage unit 23.

The receiver-side communication unit 14 is a communication interface for transmitting and receiving data and the like to and from the service server 3 and the terminal device 40 using one or more communication methods.
The communication method is not particularly limited, and examples thereof include communication (wired and wireless), infrared communication, and Bluetooth communication via a communication network N such as a public network or a LAN (Local Area Network).
In the present embodiment, the receiver-side communication unit 14 has a communication interface function for transmitting and receiving data and the like with the service server 3 via the communication network N.
In the present embodiment, the receiver-side communication unit 14 has a communication interface function for transmitting and receiving data and the like with the terminal device 40 using infrared communication, Bluetooth communication, or the like.

  The second separation unit 15 determines the type of data received by the receiver side communication unit 14. When the second separation unit 15 determines that the received data is an AIT, the second separation unit 15 outputs the AIT to the communication AIT acquisition unit 16. When the second separation unit 15 determines that the received data is an application, the second separation unit 15 outputs the application to the application execution control unit 17.

  The second separation unit 15 outputs this AIT to the communication AIT acquisition unit 16 when the AIT is extracted, and outputs this data to the application execution control unit 17 when data other than the AIT is extracted.

  The communication AIT acquisition unit 16 acquires the AIT output from the second separation unit 15 and stores it in the AIT storage unit 23.

  The application execution control unit 17 acquires an application based on a user execution instruction via an AIT or a remote controller (not shown), and controls execution of the acquired application. Then, the application execution control unit 17 outputs the audio data of the application content acquired from the service server 3 by executing the application to the audio control unit 18, and the video data of the application content acquired from the service server 3. The data is output to the display control unit 19.

FIG. 4 is a diagram illustrating an example of the AIT described in the XML format. As described above, the AIT includes one or more pieces of individual management information corresponding to one or more applications and managing each of the one or more applications.
Specifically, the codes described from the <mhp: Application> tag to the </ mhp: Application> tag shown in FIG. 4 correspond to the individual management information related to one application. In the AIT, a plurality of pieces of individual management information can be described by newly describing individual management information of other applications after the </ mhp: Application> tag.

  Of the codes corresponding to the individual management information, for example, the code corresponding to the <mhp: appId> tag indicates the application ID (identification information). The code corresponding to the <mhp: controlCode mhp: type = “ARIB-J”> tag indicates the life cycle control information of this application, and “AUTOSTART” shown in FIG. Is life cycle control information for automatically executing A code corresponding to the <mhp: location> tag indicates location information indicating the location of the application. As shown in FIG. 4, the location information describes the address of the service server 3 as the location of the application. In the location information, the receiver 4 can be designated as the location of the application.

  The application execution control unit 17 monitors the AIT storage unit 23 and refers to control information related to the life cycle described in the AIT when a new AIT is stored. Then, when the control information related to the life cycle indicates “automatic execution”, the application execution control unit 17 uses the location information described in the AIT as the application acquisition destination, The application is acquired from the service server 3 via the 2 separation unit 15 and the acquired application is executed. In this case, the application is automatically executed without receiving an explicit operation instruction from the user of the receiver 4.

  The application execution control unit 17 receives an application execution instruction from the user of the receiver 4 via the remote controller. For example, the remote control is provided with a Hybridcast (registered trademark) button, and the application execution control unit 17 receives a selection of an application to be executed in response to the user pressing the Hybridcast button by the user of the receiver 4. The execution instruction of the menu screen is accepted. In response to receiving the menu screen execution instruction, the application execution control unit 17 refers to the AIT storage unit 23 and identifies the AIT of the executable application. Then, the application execution control unit 17 outputs video data constituting a menu screen from which an application corresponding to the identified AIT can be selected to the display control unit 19 and causes the display 21 to display this menu screen. In this case, for example, an icon corresponding to the application is displayed on the display 21 at a position and a region corresponding to a predetermined display priority. When an application selection operation is received from the user of the receiver 4 via the remote control, the application execution control unit 17 refers to the location information of the application described in the AIT, acquires the application, and executes the application.

  The application causes the application execution control unit 17 to acquire video data and audio data of the application content from the service server 3. Then, the application execution control unit 17 outputs the audio data of the application content acquired by the application to the audio control unit 18 and outputs the video data of the application content acquired by the application to the display control unit 19. Here, when the application is an application that provides application content linked to the program content, the video data and audio data of the application content are displayed on the display 21 in conjunction with the video data and audio data of the program content. .

Further, the application execution control unit 17 monitors the AIT storage unit 23, and when the AIT describing the individual management information corresponding to the application being executed is newly stored in the AIT storage unit 23, it is included in the individual management information. The running application is controlled based on the life cycle control information. For example, when the life cycle control information of the application indicates “end”, the application is ended.

The application execution control unit 17 includes an API 17a.
The API 17a includes a plurality of APIs. Each of the plurality of APIs included in the API 17a is called by the API availability determination unit 79 when the API availability determination unit 79 determines that the API 17a can be used. The called API sends a predetermined notification to the API using unit 91. The called API is used by the API using unit 91.

  The audio control unit 18 outputs the audio data output from the first separation unit 12 to the speaker 20 while synchronizing with the video data whose display is controlled by the display control unit 19. Further, when the audio data output from the application execution control unit 17 can be synchronized with the video data whose display is controlled by the display control unit 19, the audio control unit 18 transmits the audio data to the speaker while synchronizing with the video data. 20 is output.

  The display control unit 19 displays the video data output from the first separation unit 12 on the display 21 in synchronization with the audio data output-controlled by the audio control unit 18. In addition, when the video data output from the application execution control unit 17 can be synchronized with the audio data output-controlled by the audio control unit 18, the display control unit 19 displays the video data while synchronizing with the audio data. 21 is displayed.

The memory 22 stores meta information of program content such as EIT and various other information.
The AIT storage unit 23 stores the AIT acquired by the broadcast AIT acquisition unit 13 and the communication AIT acquisition unit 16.

The application storage unit 24 stores an application.
The application storage unit 24 stores an application acquired by the receiver 4 in addition to an application installed in advance.
Specifically, the application storage unit 24 stores the application acquired by the application execution control unit 17 based on the AIT.

  The receiver side cooperation management unit 70 manages cooperation with the terminal device 40. The receiver side cooperation management unit 70 performs transmission / reception of data and the like with the terminal device side cooperation management unit 50 described later to form a terminal cooperation system 200. The receiver side cooperation management unit 70 will be described in detail later.

The API using unit 91 can use one or a plurality of APIs. For example, the API using unit 91 uses a predetermined API in response to a request from a predetermined application.
In this embodiment, the API using unit 91
A predetermined API which is determined to be usable by the API availability determination unit 79 and called is used. The API using unit 91 receives a predetermined notification from the called API. The API using unit 91 uses the API.

The resource management unit 95 manages receiver resources.
The resource management unit 95 manages, for example, in-receiver user resources (user information and the like), authentication resources such as authentication information, program resources such as image data and audio data used for program content, and the like.

The terminal device 40 constitutes the terminal cooperation system 200 together with the receiver 4.
The terminal device 40 is configured to be able to cooperate with the receiver 4. Specifically, the terminal device 40 includes a terminal device side cooperation management unit 50 for cooperation with the receiver 4.
The terminal device 40 will be described in detail later.

Next, the terminal cooperation system 200 will be described with reference to FIGS.
FIG. 5 is a block diagram illustrating functional configurations of the receiver side cooperation management unit 70 and the terminal device side cooperation management unit 50 in the terminal cooperation system 200. FIG. 6 is a diagram showing a user identification information-authority level information table 300 stored in the account management unit 73. FIG. 7 is a diagram showing an authority level information management table 310 stored in the authority level management unit 75. FIG. 8 is a diagram showing an API usage level management table 320 stored in the API usage level management unit 78.

  Here, the terminal cooperation system 200 receives a program content signal formed by multiplexing program content and a plurality of pieces of information via broadcasting or communication, and can output a token, and a receiver 4. And a terminal device 40 that requests the receiver 4 to use a predetermined API.

As illustrated in FIG. 5, the terminal cooperation system 200 includes a terminal device 40 and a receiver 4.
First, the terminal device 40 will be described.
The terminal device 40 includes a terminal device side communication unit 41, an operation input unit 42, and a terminal device side cooperation management unit 50.

Similarly to the receiver-side communication unit 14, the terminal device-side communication unit 41 is a communication interface for transmitting and receiving data and the like with the service server 3, the receiver 4, and the like using one or more communication methods. Similarly to the receiver-side communication unit 14, the communication method is not particularly limited. For example, communication (wired, wireless), infrared communication, Bluetooth via a communication network N such as a public network or a LAN (Local Area Network). (Bluetooth) communication can be illustrated.
In this embodiment, the terminal device side communication unit 41 has a communication interface function for transmitting / receiving data and the like to / from the service server 3 via the communication network N. Further, in the present embodiment, the terminal device side communication unit 41 has a communication interface function for transmitting and receiving data and the like with the receiver 4 using, for example, infrared communication or Bluetooth communication.

  The terminal device side communication unit 41 is configured to be able to output cooperation request information including user identification information, which will be described later, and API use request information, to the receiver 4 (receiver side communication unit 14). Further, the terminal device side communication unit 41 outputs a token output from the receiver 4 (receiver side communication unit 14), information indicating that the specific API cannot be used (error information), and cooperation request information. It is configured to be able to receive cooperation information output request information requesting that.

The operation input unit 42 includes a plurality of keys arranged on the surface of the terminal device 40, a touch sensor arranged on the surface of the terminal side display unit, and the like.
The operation input unit 42 receives an operation input from the user. Specifically, the operation input unit 42 receives an operation input for requesting cooperation with the receiver 4.
The operation input unit 42 may receive an operation input requesting selection of a predetermined application in the receiver 4, use of the predetermined application, or use of a predetermined function in the predetermined application.
The operation input unit 42 outputs a signal (information) corresponding to the received operation input to the cooperation request output unit 52 and the API use request output unit 54.

The terminal device side cooperation management unit 50 includes a user identification information management unit 51, a cooperation request output unit 52, a token reception unit 53, and an API use request output unit 54.
The terminal device side cooperation management unit 50 manages cooperation with the receiver 4. The terminal device side cooperation management unit 50 exchanges data and the like with the receiver side cooperation management unit 70 to form a terminal cooperation system 200.

The user identification information management unit 51 manages user identification information for identifying a user or the terminal device.
Examples of the user identification information include a user name, a user ID, identification information of a decision card owned by the user, a terminal device ID, and communication address information of the terminal device (for example, Bluetooth address information).
The user identification information management unit 51 is configured to be able to output user identification information to the cooperation request output unit 52.

The cooperation request output unit 52 outputs cooperation request information including user identification information to the receiver 4 via the terminal device side communication unit 41. In addition to the user identification information, the cooperation request information includes, for example, information requesting cooperation and receiver identification information identifying a receiver requesting cooperation.
The cooperation request output unit 52 outputs cooperation request information including the user identification information acquired from the user identification information management unit 51 to the receiver 4.
Specifically, the cooperation request output unit 52 acquires user identification information from the user identification information management unit 51 when receiving a signal indicating that the operation input of the cooperation request has been received from the operation input unit 42. Then, the cooperation request output unit 52 outputs the cooperation request information including the acquired user identification information to the receiver 4 via the terminal device side communication unit 41.
In addition, the cooperation request output unit 52 may output cooperation request information including user identification information directly input from the operation input unit 42 to the receiver 4.

The token accepting unit 53 is configured to accept a token output from the receiver 4 via the terminal device side communication unit 41. The token reception unit 53 receives a token output from a token output unit 76 described later via the terminal device side communication unit 41 and the receiver side communication unit 14.
Specifically, the token accepting unit 53 accepts a token issued to the cooperation request information (user identification information) output by the cooperation request output unit 52 and output from the token output unit 76.
The token reception unit 53 outputs the received token to the API use request output unit 54.
The token reception unit 53 may be configured to be able to store the received token for a predetermined period.

The API use request output unit 54 is configured to be able to output API use request information including at least API identification information for identifying a predetermined API to the receiver 4 via the terminal device side communication unit 41.
In addition to the API identification information, the API use request information includes, for example, information requesting use of an API specified by the API identification information, a token received by the token receiving unit, and the like.

  The API use request output unit 54 analyzes information related to the request received via the operation input unit 42 and specifies an API used to execute the request. Then, the API usage request output unit 54 outputs API usage request information including API identification information for identifying the specified API.

When the token receiving unit 53 receives a token, the API use request output unit 54 outputs API use request information including predetermined API identification information and a token to the receiver 4.
The API usage request output unit 54 acquires a token from the token reception unit 53 and outputs API usage request information including API identification information and the acquired token to the receiver 4.
Specifically, when an execution of a predetermined function is requested via the operation input unit 42, the API use request output unit 54 specifies an API used for executing the predetermined function. Further, the API use request output unit 54 acquires a token from the token reception unit 53. Then, the API usage request output unit 54 outputs API identification information of the identified API and usage request information including the acquired token to the receiver 4.

When the token reception unit 53 has not received a token, the API usage request output unit 54 outputs API usage request information that includes predetermined API identification information and does not include a token to the receiver 4.
Specifically, when an execution of a predetermined function is requested via the operation input unit 42, the API use request output unit 54 specifies an API used for executing the predetermined function. The API use request output unit 54 requests the token reception unit 53 to output a token. When the API usage request output unit 54 cannot acquire a token from the token reception unit 53, the API usage request output unit 54 outputs usage request information that does not include a token, including API identification information of the specified API, to the receiver 4.

Next, the receiver 4 will be described.
The receiver 4 includes a receiver-side communication unit 14 and a receiver-side cooperation management unit 70.

As described above, the receiver-side communication unit 14 is a communication interface for transmitting and receiving data and the like to and from the service server 3 and the terminal device 40 using one or more communication methods.
In the present embodiment, the receiver-side communication unit 14 has a communication interface function for transmitting and receiving data and the like with the terminal device 40 using, for example, infrared communication or Bluetooth.

  The receiver-side communication unit 14 sends to the terminal device 40 (terminal device-side communication unit 41) information (error information) indicating that the token or the specific API cannot be used, or cooperation information output request information described later. It is configured to allow output. Moreover, the terminal device side communication part 41 is comprised so that the cooperation request information output from the terminal device 40 (terminal device side communication part 41) and API utilization request information can be received.

The receiver-side cooperation management unit 70 includes a cooperation request reception unit 71, an authority level information acquisition unit 72, an account management unit 73, a token generation unit 74, an authority level management unit 75, a token output unit 76, and an API. The usage request reception unit 77, the API usage level management unit 78, and the API usage availability determination unit 79 are included.
As described above, the receiver side cooperation management unit 70 manages the cooperation with the terminal device 40. The receiver side cooperation management unit 70 performs transmission / reception of data and the like with the terminal device side cooperation management unit 50 described later to form a terminal cooperation system 200.

The cooperation request reception unit 71 receives the cooperation request information output from the cooperation request output unit 52 via the receiver-side communication unit 14.
The cooperation request reception unit 71 outputs the received cooperation request information or user identification information included in the received cooperation request information to the authority level information acquisition unit 72.

The authority level information acquisition unit 72 acquires authority level information associated with user identification information included in the cooperation request information from an account management unit 73 described later. Here, the authority level information acquisition unit 72 may authenticate the terminal device 40 by requesting input such as a password or a PIN code, and may acquire authority level information associated with the authenticated user identification information. .
When the authority level information acquisition unit 72 acquires the authority level information associated with the user identification information included in the cooperation request information, the authority level information acquisition unit 72 instructs the token generation unit 74 (to be described later) to generate a token. At least the acquired authority level information is output to the management unit 75.
Here, the authority level information acquisition unit 72 can output user identification information and the like to the authority level management unit 75 in addition to the authority level information.

The account management unit 73 can set the authority level for each of the one or more user identification information, and stores the one or more user identification information in association with the authority level information set for each. To do.
The account management unit 73 stores one or more pieces of user identification information in association with authority level information set for each. The account management unit 73 may also store a password and a PIN code for authenticating user identification information.
For example, the account management unit 73 stores a user identification information-authority level information table 300.

As shown in FIG. 6, the user identification information-authority level information table 300 stores a user name, user ID information as user identification information, and authority level information in association with each other.
In the user identification information-authority level information table 300, the authority level stored in association with the user identification information (ID: A) of the user A is “0”. Further, the authority level stored in association with the user identification information (ID: B) of the user B is “1”. The authority level stored in association with the user identification information (ID: C) of the user C is “1”. The authority level stored in association with the user identification information (ID: D) of the user D is “1”. The authority level stored in association with the user identification information (ID: E) of the user E is “2”. The authority level stored in association with the user identification information (ID: F) of the user F is “2”.

The account management unit 73 is configured to be able to set user identification information and to set an authority level for each user identification information.
For example, the account management unit 73 can set information received from a user via a remote controller as user identification information. Further, the account management unit 73 detects a terminal device that can be linked in a method defined in UPnP (Universal Plug and Play) or DLNA (Digital Living Network Alliance), and identifies the detected terminal device The information may be configured to be automatically set as user identification information.

The account management unit 73 is configured to be able to set an authority level for each set user identification information.
For example, the account management unit 73 accepts authority level settings and changes from the user via a remote controller, and changes authority levels in response to the accepted settings and changes.
Further, the account management unit 73 may set an authority level to a predetermined authority level (for example, the lowest authority level “0”) as an initial setting.

The token generation unit 74 generates a token. The token generation unit 74 generates a token in response to an instruction from the authority level information acquisition unit 72. For example, the token generation unit 74 generates a pseudo-random number of a predetermined digit as a token.
The token generation unit 74 outputs the generated token to the authority level management unit 75.
Further, the token generation unit 74 outputs the generated token to the token output unit 76.

The authority level management unit 75 stores at least authority level information and a token in association with each other. The authority level management unit 75 stores the authority level information acquired by the authority level information acquisition unit 72 and the token acquired from the token generation unit 74 in association with each other.
In the present embodiment, the authority level management unit 75 may store authority level information and tokens in association with user identification information corresponding thereto.
Further, the authority level management unit 75 stores guest authority level information that is not associated with a token.
Further, the authority level management unit 75 is configured to be able to set an expiration date for each token.
Further, the authority level management unit 75 may be configured to automatically delete the expired token, or may manage the valid / invalid state of each token.
The authority level management unit 75 stores, for example, an authority level information management table 310.

As shown in FIG. 7, the authority level information management table 310 associates user names, user ID information as user identification information, authority level information, tokens, expiration dates, and valid / invalid information. Store.
In the authority level information management table 310, the authority level associated with the token “abcd” is “0”, the expiration date is “20aa / bb / cc”, and the status is “valid”. Further, the authority level associated with the token “ehgh” is “0”, the expiration date is “20aa / bb / dd”, and the state is “invalid”. Further, the authority level associated with the token “ijk” is “1”, the expiration date is “20aa / bb / ee”, and the status is “valid”. Further, the authority level associated with the token “lmno” is “1”, the expiration date is “20aa / bb / ff”, and the state is “invalid”. Further, the authority level associated with the token “pqrs” is “2”, the expiration date is “20aa / bb / gg”, and the state is “valid”. Further, the authority level associated with the token “tuvw” is “2”, the expiration date is “20aa / bb / hh”, and the status is “invalid”. Further, in the case of the token “-(none)”, it is treated as a guest terminal device, the authority level is “0”, no expiration date is set, and the state is always “valid”.

  In addition, the authority level management unit 75 outputs predetermined authority level information in response to a request from an API availability determination unit 79 described later.

The token output unit 76 outputs a token via the receiver side communication unit 14. The token output unit 76 receives a token from the token generation unit 74 and outputs the received token to the terminal device 40 via the receiver-side communication unit 14.
The token output unit 76 outputs the token stored in the authority level management unit 75 in association with the authority level information.

The API use request receiving unit 77 receives the API use request information output from the API use request output unit 54 via the receiver side communication unit 14.
The API use request receiving unit 77 outputs the received API use request information to the API use availability determination unit 79.

The API usage level management unit 78 stores one or more API identification information and the usage level information set for each of the one or more API identification information in association with each other.
The API usage level management unit 78 stores an API usage level management table 320, for example.

As shown in FIG. 8, the API usage level management table 320 stores API identification information and usage level information in association with each other.
In the API usage level management table 320, the usage level stored in association with the API identification information (API-1) is “0”. The usage level stored in association with the API identification information (API-2) is “1”. The usage level stored in association with the API identification information (API-3) is “2”. The usage level stored in association with the API identification information (API-4) is “0”. The usage level stored in association with the API identification information (API-5) is “2”.

  The API usage level management unit 78 outputs usage level information associated with the API identification information included in the API usage request information to an API usage determination unit 79 described later.

The API availability determination unit 79 determines whether the API specified by the API identification information can be used.
Specifically, the API availability determination unit 79 first determines whether a token is included in the API usage request information.
If it is determined that the API use request information includes a token, the API use permission determination unit 79 determines whether a valid token is stored in the authority level management unit 75.
In other words, when the API use permission determination unit 79 determines that the token is included in the API use request information, the API use request determination unit 79 checks whether the valid token is stored in the authority level management unit 75 and checks whether the token is valid. It is determined whether the token is stored in the authority level management unit 75.

Specifically, first, when it is determined that the API usage request information does not include a token, the API usage permission determination unit 79 stores the guest authority level information stored in the authority level management unit 75 and the API usage level management unit. Based on the usage level information associated with the API identification information included in the API usage request information at 78, it is determined whether or not the API specified by the API identification information can be used.
The API availability determination unit 79 acquires usage level information associated with the API identification information included in the API usage request information from the API usage level management unit 78.
Then, the API availability determination unit 79 acquires guest authority level information, which is authority level information not associated with the token, from the authority level management unit 75, and determines whether or not the API can be used.
Here, in the present embodiment, the API availability determination unit 79 determines that the use of the specified API is permitted when the authority level is equal to or higher than the usage level, and when the authority level is lower than the usage level. The use of the specified API is determined not to be permitted.

Further, when the API availability determination unit 79 determines that the API usage request information includes a token and determines that the token is stored in the authority level management unit 75 in a valid state, the authority level management unit 79 Based on the authority level information associated with the token in 75 and the utilization level information associated with the API identification information included in the API utilization request information in the API utilization level management unit 78, it is specified by the API identification information. It is determined whether or not API can be used.
The API availability determination unit 79 acquires authority level information corresponding to the token from the authority level management unit 75, and determines whether the API can be used.

Further, when the API availability determination unit 79 determines that a token is included in the API usage request information and determines that the token is stored in the authority level management unit 75 in an invalid state, the authority level management unit 79 75 based on the guest authority level information stored in 75 and the usage level information associated with the API identification information included in the API usage request information in the API usage level management unit 78. Judgment of availability.
The API availability determination unit 79 is in an invalid state although the token corresponding to the authority level management unit 75 is managed (is present), so the guest authority level information is acquired from the authority level management unit 75 to use the API. Determine whether or not.

Further, when the API use permission determination unit 79 determines that a token is included in the API use request information and determines that the token is not included in the authority level management unit 75, the API use request determination unit 79 stores the token in the authority level management unit 75. Availability of the API specified by the API identification information based on the guest authority level information and the usage level information associated with the API identification information included in the API usage request information in the API usage level management unit 78 Determine.
The API availability determination unit 79 does not manage the token corresponding to the authority level management unit 75 (there is no), so acquires the guest authority level information from the authority level management unit 75 and determines whether the API can be used. .

  When the API availability determination unit 79 determines that the specific API is available, it calls the specific API included in the application execution control unit 17. The specific API called by the API availability determination unit 79 is used by the API usage unit 91. In addition, when the API availability determination unit 79 determines that the specified API is unusable, information indicating that the specified API cannot be used via the receiver-side communication unit 14, or cooperation request information Is output to the terminal device 40.

  Specifically, when the API usage permission determination unit 79 determines that the token is included in the API usage request information and determines that the token is stored in a valid state in the authority level management unit, Based on the authority level information associated with the token in the authority level management unit 75 and the usage level information associated with the API identification information in the API usage level management unit 78, it is determined that the use of the specified API is not permitted. Then, information (error information) indicating that the specified API cannot be used is output to the terminal device 40 via the receiver-side communication unit 14.

  In addition, when the API use permission determination unit 79 determines that the API use request information does not include a token, the API use request information determines that the API use request information includes a token, and the token uses the authority level management. When it is determined that the token is included in the API usage request information and when it is determined that the token is stored in an invalid state in the authority level management unit, When it is determined that the use of the specified API is not permitted based on the guest authority level information stored in the authority level management unit 75 and the usage level information associated with the API identification information in the API usage level management unit Information indicating that the specified API cannot be used (error information) and cooperation request information are output via the machine-side communication unit 14 Outputs and a linkage information output request information that requests the terminal apparatus 40.

Next, operations of the terminal device 40 and the receiver 4 constituting the terminal cooperation system 200 will be described with reference to FIGS. 9 to 12.
FIG. 9 is a diagram for explaining an example of availability of the activation API, display API, and change API in the user resource management application in the receiver. FIG. 10 is a flowchart for explaining operations of the terminal device and the receiver when the terminal device cooperates with the receiver. FIG. 11 is a flowchart for explaining operations of the terminal device and the receiver when the use of the activation API, the display API, and the change API in the user resource management application in the receiver is requested from the linked terminal device. FIG. 12 is a flowchart for explaining operations of the terminal device and the receiver when the use of the activation API, the display API, and the change API in the receiver user resource management application is requested from an uncoordinated terminal device.

First, operations of the terminal device 40 and the receiver 4 when the terminal device 40 cooperates with the receiver 4 will be described with reference to FIG.
As shown in FIG. 10, first, in step ST101, the terminal device 40 (cooperation request output unit 52) receives an operation input for requesting cooperation with the receiver 4 via the operation input unit 42. Cooperation request information including user identification information is output to the machine 4.

  Next, in step ST102, the receiver 4 (cooperation request reception unit 71) receives the cooperation request information output from the terminal device 40 (cooperation request output unit 52). Then, the cooperation request reception unit 71 outputs the cooperation request information to the authority level information acquisition unit 72.

  Subsequently, in step ST103, the authority level information acquisition unit 72 acquires authority level information associated with the user identification information included in the cooperation request information in the account management unit 73. The authority level information acquisition unit 72 may acquire the authority level information by performing identity authentication using a password or a PIN code. Then, when the authority level information acquisition unit 72 acquires the authority level information, the authority level information acquisition unit 72 instructs the token generation unit 74 to generate a token and outputs the acquired authority level information to the authority level management unit 75.

  Subsequently, in step ST104, the token generation unit 74 generates a token. Then, the token generation unit 74 outputs the generated token to the token output unit 76 and the authority level management unit 75.

  Subsequently, in step ST105, the authority level management unit 75 stores the authority level information output from the authority level information acquisition unit 72 and the token output from the token generation unit 74 in association with each other.

  Subsequently, in step ST106, the receiver 4 (token output unit 76) outputs a token to the terminal device 40 (token receiving unit 53).

In step ST107, the terminal device 40 (token accepting unit 53) accepts the token output from the receiver 4 (token output unit 76).
Thereby, the terminal device 40 is in a state of being linked with the receiver 4.

Next, the operation of the terminal device and the receiver when the use of the activation API, the display API, and the change API in the receiver user resource management application is requested from the linked terminal device will be described with reference to FIG.
First, in step ST201, the terminal device 40 (API use request output unit 54) receives a request for browsing and changing the user resource in the receiver via the operation input unit 42.
Specifically, the API use request output unit 54 receives an activation request, a browse request, and a change request for the in-receiver user resource management application from the operation input unit 42.
Then, the API use request output unit 54 analyzes the input operation content and, as an API necessary for executing the above request, a start API for starting the in-receiver user resource management application, and for browsing A display API and a change API for changing are specified.

Next, in step ST202, the API use request output unit 54 receives the API use request information including the API identification information of the activation API, the display API, and the change API of the in-receiver user resource management application, and the token. Output to (API usage request receiving unit).
Specifically, the API use request output unit 54 acquires a token from the token reception unit 53. Then, the API use request output unit 54 receives the API use request information including the API identification information and the token of the identified start-up API, display API, and change API of the identified in-receiver user resource management application, and the receiver 4 (API To the usage request reception unit).

  Subsequently, in step ST203, the receiver 4 (API usage request receiving unit 77) receives the API usage request information output from the terminal device 40 (API usage request output unit 54). Then, the API use request receiving unit 77 outputs the API use request information to the API use availability determination unit 79.

Subsequently, in step ST204, the API availability determination unit 79 determines whether or not each of the in-receiver user resource management application activation API, the display API, and the change API can be used based on the authority level information and the API usage level information. To do.
Specifically, the API availability determination unit 79 acquires authority level information associated with the token included in the API usage request information from the authority level management unit 75.
The API availability determination unit 79 is associated with the API identification information of each of the activation API, display API, and change API of the user resource management application in the receiver included in the API usage request information from the API usage level management unit 78. Get usage level information.
Then, the API availability determination unit 79 includes the authority level information acquired from the authority level management unit 75, the activation API, display API, and change API of the in-receiver user resource management application acquired from the API usage level management unit 78. Based on the usage level information associated with each of the API identification information, whether or not the activation API, the display API, and the change API are available is determined.

Here, as shown in FIG. 9, the activation API in the in-receiver user resource management application has a usage level of “0”, so that all users including guest users are permitted to use.
That is, since the authority level associated with the token managed in the valid state is “0”, “1”, and “2” in the authority level management unit 75, the corresponding users A, C, and E have the activation API. Usage is permitted.
Moreover, since the authority level is “0”, the so-called guest user can use the activation API in the same manner.
Here, since the authority level of the guest user is applied to a token that is not managed by the authority level management unit 75 and a token that is managed in an invalid state by the authority level management unit 75, the same as for the guest user. In addition, an activation API can be used.
That is, in this example, all users can start the user resource management application in the receiver.

Also, as shown in FIG. 9, the usage level of the display API in the in-receiver user resource management application is permitted only to users C and E because the usage level is “1”.
The authority level management unit 75 manages the token in a valid state, and the users C and E whose authority levels associated with the token are “1” and “2” are permitted to use the display API.
That is, in this example, the users C and E can browse the user resources in the receiver.

Further, as shown in FIG. 9, the change API in the in-receiver user resource management application is permitted to use only for the user E because the use level is “2”.
In the authority level management unit 75, the token is managed in a valid state, and the user E whose authority level associated with the token is “2” is permitted to use the change API.
That is, in this example, the user E can change the user resource in the receiver.

  When the API availability determination unit 79 determines that the API is available, it calls a specific API included in the application execution control unit 17. If the API availability determination unit 79 determines that the API cannot be used, the API availability determination unit 79 outputs information indicating that the API cannot be used (error information) to the terminal device 40.

Subsequently, in step ST205, the terminal device 40 receives information indicating that the API cannot be used (error information) and causes the terminal-side display unit (not shown) to display that the specific API cannot be used.
For example, the terminal device 40 displays “display not permitted” indicating that the use of the display API is not permitted or “change not permitted” indicating that the use of the change API is not permitted on the terminal side display unit. Display.

Subsequently, in step ST206, the API using unit 91 uses the specific API called by the API use availability determination unit 79.
For example, the API using unit 91 uses a display API or a change API.

  Subsequently, in step ST207, the receiver 4 displays the contents of the user resource in the receiver using the display API. Further, the receiver 4 accepts a change in the content of the user resource in the receiver using the change API.

The operation of the terminal device and the receiver when the use of the activation API, display API, and change API in the in-receiver user resource management application is requested from an uncoordinated terminal device will be described with reference to FIG.
First, in step ST301, the terminal device 40 (API use request output unit 54) receives a request for viewing and changing the user resource in the receiver via the operation input unit 42.
Specifically, the API use request output unit 54 receives an activation request, a browse request, and a change request for the in-receiver user resource management application from the operation input unit 42.
Then, the API use request output unit 54 analyzes the input operation content and, as an API necessary for executing the above request, a start API for starting the in-receiver user resource management application, and for browsing A display API and a change API for changing are specified.

  Next, in step ST302, the API use request output unit 54 receives the API use request information including the API identification information of the activation API, the display API, and the change API of the receiver user resource management application in the receiver 4 (API use request). To the reception unit).

  Subsequently, in step ST303, the receiver 4 (API usage request receiving unit 77) receives the API usage request information output from the terminal device 40 (API usage request output unit 54). Then, the API use request receiving unit 77 outputs the API use request information to the API use availability determination unit 79.

  Subsequently, in step ST304, the API availability determination unit 79 determines whether each of the in-receiver user resource management application activation API, the display API, and the change API can be used based on the guest authority level information and the API usage level information. judge.

  Here, if the API usage determination unit 79 determines that a token is not included in the API usage request information, the API usage request information determines that the API usage request information includes a token and the token is an authority level management unit 75. If it is determined that the token is included in the API use request information and it is determined that the token is stored in the authority level management unit 75 in an invalid state, the authority level Guest authority level information is acquired from the management unit 75 as authority level information.

Then, the API availability determination unit 79 includes the guest authority level information acquired from the authority level management unit 75, the in-receiver user resource management application startup API, the display API, and the change API acquired from the API usage level management unit 78. Based on the usage level information associated with each API identification information, whether or not the activation API, the display API, and the change API are available is determined.
Here, since the guest authority level is less than the usage level of the display API and the change API, the API availability determination unit 79 determines that the usage in the display API and the change API is impossible.
Then, the API availability determination unit 79 provides the terminal device 40 with information indicating that the display API and the change API cannot be used (error information) and linkage information output request information requesting that the linkage request information be output. Output.

Subsequently, in step ST305, the terminal device 40 receives information indicating that the display API and the change API cannot be performed (error information), and cooperation information output request information requesting to output the cooperation request information. Upon receiving the information, the terminal device 40 displays “display not permitted” or “change not permitted” on the terminal side display (not shown), and prompts the receiver 4 to make a cooperation request. A cooperation request display (menu etc.) is displayed.
Thereby, a user who uses the terminal device 40 inputs a cooperation request to the receiver 4 via the operation input unit 42.
When the terminal device 40 (cooperation request output unit 52) receives an operation input requesting cooperation with the receiver 4 via the operation input unit 42, the terminal device 40 (cooperation request output unit 52) includes the user identification information for the receiver 4. Output request information.

  Subsequently, in step ST306, the receiver 4 (cooperation request reception unit 71) receives the cooperation request information output from the terminal device 40 (cooperation request output unit 52). Then, the cooperation request reception unit 71 outputs the cooperation request information to the authority level information acquisition unit 72.

  Subsequently, in step ST307, the authority level information acquisition unit 72 acquires authority level information associated with the user identification information included in the cooperation request information in the account management unit 73. Then, when the authority level information acquisition unit 72 acquires the authority level information, the authority level information acquisition unit 72 instructs the token generation unit 74 to generate a token and outputs the acquired authority level information to the authority level management unit 75.

  Subsequently, in step ST308, the token generation unit 74 generates a token. Then, the token generation unit 74 outputs the generated token to the token output unit 76 and the authority level management unit 75.

  Subsequently, in step ST309, the authority level management unit 75 stores the authority level information output from the authority level information acquisition unit 72 and the token output from the token generation unit 74 in association with each other.

  Subsequently, in step ST310, the receiver 4 (token output unit 76) outputs a token to the terminal device 40 (token receiving unit 53).

Subsequently, in step ST311, the terminal device 40 (token reception unit 53) receives the token output from the receiver 4 (token output unit 76).
Thereby, the terminal device 40 is in a state of being linked with the receiver 4.

  In step ST312, the terminal device 40 (API use request output unit 54) receives a request to view and change the user resource in the receiver via the operation input unit 42 again.

  Subsequently, in step ST313, the receiver 4 (API usage request receiving unit 77) receives the API usage request information output from the terminal device 40 (API usage request output unit 54). Then, the API use request receiving unit 77 outputs the API use request information to the API use availability determination unit 79.

Subsequently, in step ST314, the API availability determination unit 79 determines whether or not each of the in-receiver user resource management application activation API, the display API, and the change API can be used based on the authority level information and the API usage level information. To do.
Specifically, the API availability determination unit 79 acquires authority level information associated with the token included in the API usage request information from the authority level management unit 75.
The API availability determination unit 79 is associated with the API identification information of each of the activation API, display API, and change API of the user resource management application in the receiver included in the API usage request information from the API usage level management unit 78. Get usage level information.
Then, the API availability determination unit 79 includes the authority level information acquired from the authority level management unit 75, the activation API, display API, and change API of the in-receiver user resource management application acquired from the API usage level management unit 78. Based on the usage level information associated with each of the API identification information, whether or not the activation API, the display API, and the change API are available is determined.

When the API availability determination unit 79 determines that the API is available, it calls a specific API included in the API 17a. The called specific API notifies the API using unit 91 of a predetermined notification.
If the API availability determination unit 79 determines that the API cannot be used, the API availability determination unit 79 outputs information indicating that the API cannot be used (error information) to the terminal device 40.

  Subsequently, in step ST315, when receiving information (error information) indicating that the API cannot be used, the terminal device 40 displays “display not permitted” and “change not permitted” on the terminal side display unit.

Subsequently, in step ST316, the API using unit 91 uses the specific API called by the API use availability determination unit 79. The API using unit 91 receives a predetermined notification from the called specific API and uses the specific API.
For example, the API using unit 91 uses a display API or a change API.

  Subsequently, in step ST317, the receiver 4 displays the contents of the user resource in the receiver using the display API. Further, the receiver 4 accepts a change in the content of the user resource in the receiver using the change API.

  According to this embodiment, it is a terminal cooperation system including a receiver and a terminal device, and controls access from the terminal device to resources in the receiver by restricting the use of API (application program information) in the receiver. A possible terminal cooperation system can be provided.

  Further, according to the present embodiment, the terminal cooperation system determines whether or not the API can be used based on the authority level of the user and the API usage level. You can set the access level to resources.

  Further, according to the present embodiment, since the terminal cooperation system is configured to specify the authority level in the terminal device (user) using the token, the correct authority level information is provided for each user in response to the API use request. Provided. The terminal cooperation system can control access to resources in the receiver for each user with high accuracy.

  Further, according to the present embodiment, in the terminal cooperation system, even when a token is not included in the API use request information, the API use availability determination unit determines whether the API can be used based on the guest authority level information. Thus, a minimum API usage can be allowed for a terminal device that is not linked.

  Further, according to the present embodiment, the terminal cooperation system is in a disabled state when the token included in the API use request information is an invalid token (if it is not managed by the authority level management unit, it is managed). In other cases, the API availability determination unit is configured to determine the availability of the API based on the guest authority level information. Can be tolerated.

Further, according to the present embodiment, the API availability determination unit determines that the token is not included in the API usage request information or the token included in the API usage request information is an invalid token (authority level management). If it is determined that the use of the API is not possible in the case where the API is not available, the cooperation information output request information is output to the terminal device.
As a result, the terminal cooperation system can prompt the user (terminal apparatus) who can use the specific API if cooperation is provided. In addition, the terminal cooperation system can suppress the occurrence of the cooperation operation to the minimum, and can prompt the user (terminal device) to cooperate when cooperation is necessary.

  As mentioned above, although demonstrated using embodiment of this invention, the technical scope of this invention is not limited to the range as described in the said embodiment. Various modifications or improvements can be added to the above embodiment. It is apparent from the scope of the claims that the embodiments added with such changes or improvements can also be included in the technical scope of the present invention.

  For example, the receiver may include an authentication unit that recognizes that the user identification information is correct during the cooperative operation.

  Further, for example, the token generation unit generates a token regardless of the content of the user identification information, but is not limited thereto, and may be configured to limit tokens generated for the same user identification information.

DESCRIPTION OF SYMBOLS 1 Broadcasting station 2 Broadcasting antenna 3 Service server 4 Receiver 11 Broadcast wave receiving part 12 First separation part 13 Broadcast AIT acquisition part 14 Receiver side communication part 15 Second separation part 16 Communication AIT acquisition part 17 Application execution control part 17a API
18 Voice control unit 19 Display control unit 20 Speaker 21 Display 22 Memory 23 AIT storage unit 24 Application storage unit 40 Terminal device 41 Terminal device side communication unit 42 Operation input unit 50 Terminal device side cooperation management unit 51 User identification information management unit 52 Cooperation Request output unit 53 Token reception unit 54 API use request output unit 70 Receiver side cooperation management unit 71 Cooperation request reception unit 72 Authority level information acquisition unit 73 Account management unit 74 Token generation unit 75 Authority level management unit 76 Token output unit 77 API Usage request reception unit 78 API usage level management unit 79 API usage availability determination unit 91 API usage unit 95 Resource management unit 100 Broadcast communication cooperation system 200 Terminal cooperation system 300 Authority level information table 310 Authority level information management table 320 API usage level management Buru

Claims (7)

A receiver that can receive a program content signal configured by multiplexing program content and a plurality of pieces of information via broadcast or communication, and that can output a token, can be linked to the receiver, and can be connected to the receiver. A terminal cooperation system having a terminal device that requests the use of a predetermined application program interface,
The terminal device
A terminal device side communication unit;
A token accepting unit capable of accepting a token output from the receiver via the terminal device side communication unit;
When the API usage request information including API identification information for identifying at least a predetermined application program interface can be output to the receiver via the terminal device side communication unit, and the token receiving unit receives a token, An API usage request output unit that outputs API usage request information including the predetermined API identification information and the token to the receiver;
The receiver
The receiver side communication section,
An API usage request receiving unit that receives the API usage request information output from the API usage request output unit via the receiver side communication unit;
An authority level management unit that stores at least authority level information and a token in association with each other;
An API usage level management unit that stores one or more API identification information and usage level information set in each of the one or more API identification information in association with each other;
It is determined whether or not a token is included in the API usage request information, and when it is determined that a token is included in the API usage request information, the valid token is stored in the authority level management unit. An API availability determination unit that determines whether or not
When it is determined that the API use request information includes a token and the token is stored in the authority level management unit, the authority level associated with the valid token in the authority level management unit Based on the information and the usage level information associated with the API identification information included in the API usage request information in the API usage level management unit, it is determined whether or not the application program interface specified by the API identification information can be used A terminal cooperation system comprising: an API availability determination unit. The terminal device
A cooperation request output unit that outputs cooperation request information including user identification information for identifying a user or the terminal device to the receiver via the terminal device side communication unit;
The receiver
A cooperation request receiving unit that receives the cooperation request information output from the cooperation request output unit via the receiver-side communication unit;
An account management unit capable of setting an authority level for each of one or a plurality of user identification information, and storing one or a plurality of user identification information in association with the authority level information set for each;
An authority level information acquisition unit that acquires authority level information associated with user identification information included in the cooperation request information from the account management unit;
A token output unit that outputs a token via the receiver-side communication unit,
The authority level management unit
Storing the authority level information acquired by the authority level information acquisition unit in association with the token;
The token output unit
The terminal cooperation system according to claim 1, wherein the authority level management unit outputs a token stored in association with the authority level information. The authority level management unit
Remembers guest privilege level information not associated with a token,
The API availability determination unit
When it is determined that no token is included in the API use request information,
When it is determined that the API use request information includes a token and it is determined that the valid token is not stored in the authority level management unit,
Based on the guest authority level information stored in the authority level management unit and the usage level information associated with the API identification information included in the API usage request information in the API usage level management unit, the API identification information The terminal cooperation system according to claim 1, wherein whether or not the application program interface specified by the function is usable is determined. The terminal device
A cooperation request output unit that outputs cooperation request information including user identification information for identifying a user or the terminal device to the receiver via the terminal device side communication unit;
The receiver
A cooperation request receiving unit that receives the cooperation request information output from the cooperation request output unit via the receiver-side communication unit;
An account management unit capable of setting an authority level for each of one or a plurality of user identification information, and storing one or a plurality of user identification information in association with the authority level information set for each;
An authority level information acquisition unit that acquires authority level information associated with user identification information included in the cooperation request information from the account management unit;
A token output unit that outputs a token via the receiver-side communication unit,
The authority level management unit
Storing the authority level information acquired by the authority level information acquisition unit in association with the token;
The token output unit
The terminal cooperation system according to claim 3, wherein the authority level management unit outputs a token stored in association with the authority level information. The API availability determination unit
When it is determined that the API use request information includes a token and it is determined that the valid token is stored in the authority level management unit, the authority level associated with the token in the authority level management unit When it is determined that the use of the application program interface specified by the API identification information is not permitted based on the information and the usage level information associated with the API identification information in the API usage level management unit, the receiver side The terminal cooperation system according to claim 1 or 2, wherein information indicating that the specified application program interface cannot be used is output to the terminal device via a communication unit. The API availability determination unit
When it is determined that no token is included in the API use request information,
When it is determined that the API use request information includes a token and it is determined that the valid token is not stored in the authority level management unit,
Based on the guest authority level information stored in the authority level management unit and the usage level information associated with the API identification information in the API usage level management unit, use of the specified application program interface is prohibited. When it is determined to be permitted, information indicating that the specified application program interface cannot be used via the receiver-side communication unit, cooperation information output request information requesting to output the cooperation request information, The terminal cooperation system according to claim 4 which outputs to a terminal unit. A receiver that can receive a program content signal configured by multiplexing program content and a plurality of pieces of information via broadcast or communication, and that can output a token, can be linked to the receiver, and can be connected to the receiver. A terminal device for requesting the use of a predetermined application program interface, and a receiver used in a terminal cooperation system,
The receiver side communication section,
An API usage request receiving unit that receives API usage request information including API identification information that identifies at least a predetermined application program interface output from the terminal device via the receiver-side communication unit;
An authority level management unit that stores at least authority level information and a token in association with each other;
An API usage level management unit that stores one or more API identification information and usage level information set in each of the one or more API identification information in association with each other;
It is determined whether or not a token is included in the API usage request information, and when it is determined that a token is included in the API usage request information, the valid token is stored in the authority level management unit. An API availability determination unit that determines whether or not
When it is determined that the API use request information includes a token and the token is stored in the authority level management unit, the authority level associated with the valid token in the authority level management unit Based on the information and the usage level information associated with the API identification information included in the API usage request information in the API usage level management unit, it is determined whether or not the application program interface specified by the API identification information can be used An API availability determination unit.

Images