CN116803086A - Server management device - Google Patents

Abstract

The server management apparatus appropriately performs processing of making the identifier of the receiver cooperate with the identifier of the terminal. The server management device is capable of transmitting and receiving information to and from a plurality of server devices, the plurality of server devices store information associating an identifier of a broadcast receiving device, an authentication code, an identifier of a content providing device, and a 1 st token, acquire an authentication request including the authentication code, the identifier of the content providing device, and the identifier of the server device from the terminal device having acquired the authentication code, acquire notification of a collaboration instruction from the terminal, acquire the 1 st token corresponding to the authentication code from the server device corresponding to the authentication request after the notification of the collaboration instruction is acquired, acquire the 2 nd token corresponding to the user identifier of the terminal from the content providing device corresponding to the authentication request, acquire the identifier of the broadcast receiving device corresponding to the 1 st token from the server device, and acquire the user identifier of the terminal device corresponding to the 2 nd token from the content providing device.

Description

Server management device

Cross-references to related applications

This application is required to be submitted to the Japan Patent Office on October 14, 2021, with application number 2021-168837, and the invention title is "Server Management Device"; and on April 7, 2022, it is submitted to the Japan Patent Office, with application number 2022-063747, invention Priority is granted to a Japanese patent application entitled "Server Management Apparatus", the entire contents of which are incorporated herein by reference.

Technical field

This application relates to a server management device.

Background technique

In recent years, there has been technology in which a receiver and a terminal cooperate to transmit and receive information. For example, the receiver transmits information received from a website to the terminal.

Prior technical documents

patent documents

Patent Document 1: Japanese Patent No. 5898431

Contents of the invention

As described above, in order for a receiver, a terminal, and a content providing device that provides content such as a website to cooperate in transmitting and receiving information, it is necessary to coordinate the identifier of the user of the terminal with the identifier of the receiver in advance, and it is desired to perform coordination processing appropriately.

Therefore, a technical problem to be solved by the present application is to provide a server management device that can appropriately execute a process of cooperating the identifier of the receiver with the identifier of the terminal.

The server management device of the embodiment is capable of exchanging information with a plurality of server devices that store information associating the identifier of the broadcast receiving device, the authentication code, the identifier of the content providing device, and the first token, where , the server management device includes: a storage unit that stores promotion information that promotes association of the identifier of the broadcast receiving device with the identifier of the user's terminal device of the content providing device; and a promotion information transmitting unit that promotes The information is transmitted to the broadcast receiving device; the authentication code transmitting unit transmits the authentication code to the broadcast receiving device based on the request based on the promotion information from the broadcast receiving device; and the authentication request acquisition unit obtains the authentication code from the terminal device , acquiring an authentication request including the authentication code, the identifier of the content providing device, and the identifier of the server device; and a collaboration instruction acquisition unit that acquires the collaboration instruction of the identifier of the broadcast receiving device and the user identifier of the terminal device from the terminal device. Notification; the first token acquisition unit, after acquiring the notification of the cooperation instruction, acquires the first token corresponding to the authentication code from the server device corresponding to the authentication request; the second token acquisition unit, which acquires the first token corresponding to the authentication code from the server device corresponding to the authentication request; The corresponding content providing device acquires the second token corresponding to the user identifier of the terminal device; a broadcast receiving device identifier acquisition unit acquires the identifier of the broadcast receiving device corresponding to the first token from the server device; the user identifier an acquisition unit that acquires the user identifier of the terminal device corresponding to the second token from the content providing device; and a registration unit that compares the identifier of the broadcast receiving device corresponding to the first token with the terminal device corresponding to the second token The user identifier of the device is registered in association with it.

Description of the drawings

FIG. 1 is a diagram schematically showing an example of the overall configuration of the information collaboration system according to the first embodiment;

FIG. 2 is a block diagram showing an example of the overall configuration of the television device according to the first embodiment;

3 is a block diagram showing a partial configuration example of the television device according to the first embodiment;

FIG. 4 is a block diagram showing an example of the overall configuration of the push distribution server according to the first embodiment;

FIG. 5 is a block diagram showing a partial configuration example of the push distribution server according to the first embodiment;

FIG. 6 is a diagram showing the data structure of data stored in the push distribution server according to the first embodiment;

7 is a flowchart showing the overall processing in the information collaboration system according to the first embodiment;

8 is a diagram schematically showing an example of the overall configuration of the information collaboration system according to the second embodiment;

Fig. 9 is a block diagram showing an example of the overall configuration of the common acceptance server according to the second embodiment;

Fig. 10 is a block diagram showing a partial configuration example of the common acceptance server according to the second embodiment;

FIG. 11 is a flowchart showing the overall processing in the information collaboration system according to the second embodiment;

FIG. 12 is a flowchart showing the overall processing in the information collaboration system according to the third embodiment;

13 is a flowchart showing the overall processing in the information collaboration system according to the fourth embodiment;

FIG. 14-1 is a diagram showing an example of promotion information in the information collaboration system according to the fifth embodiment;

FIG. 14-2 is a diagram showing another example of promotion information in the information collaboration system according to the fifth embodiment;

Fig. 15 is a diagram for explaining advertising information according to the fifth embodiment;

FIG. 16-1 is a flowchart showing promotion information display processing in the information collaboration system according to the fifth embodiment;

FIG. 16-2 is a flowchart illustrating another display process of promotion information in the information collaboration system according to the fifth embodiment;

FIG. 17 is a flowchart showing the collaboration processing procedure in the information collaboration system according to the fifth embodiment;

18 is a flowchart showing collaboration cancellation processing in the information collaboration system according to the fifth embodiment;

19 is a flowchart illustrating a processing procedure for canceling collaboration through an operation of a user terminal in the information collaboration system according to the fifth embodiment;

FIG. 20 is a diagram showing an example of clickable advertisement information in the information collaboration system according to the fifth embodiment;

FIG. 21 is a flowchart showing the collaboration processing procedure in the information collaboration system according to the modification.

Explanation of reference signs

1…smartphone, 2…TV device, 3…TV cloud, 4…content providing server, 5…TV gateway, 6…measurement server, S…information collaboration system.

Detailed ways

Hereinafter, embodiments (first embodiment, second embodiment) of the server device, broadcast receiving device, server management device, information collaboration system, and program of the present application will be described in detail with reference to the drawings.

(1st Embodiment)

First, an overall configuration example of the information collaboration system S according to the first embodiment will be described with reference to FIG. 1 . FIG. 1 is a diagram schematically showing an example of the overall configuration of the information collaboration system S according to the first embodiment. The information collaboration system S includes a smartphone 1 (terminal), a television device 2 (broadcast receiving device), a TV cloud 3 (server device), and a content providing server 4 which is a content providing device such as an EC (Electronic Commerce: Electronic Commerce) website server. . The TV cloud 3 can communicate with the television device 2 and the content providing server 4 via a public communication line such as the Internet. In addition, the smartphone 1 can perform wireless communication with the content providing server 4 and the TV cloud 3 via the base station.

The smartphone 1 is an example of an information terminal owned by the user of the television device 2 . The smartphone 1 includes a communication I/F (InterFace: interface), a voice input unit (microphone), a sensor group, a display unit, a graphics controller, a touch panel controller, a CPU (Central Processing Unit: central processing unit), a memory, and a camera , speakers, etc. In the first embodiment, it is assumed that the user uses the smartphone 1 to perform Internet shopping.

The TV cloud 3 is a server device capable of transmitting and receiving with the television device 2 via a network, and is a so-called cloud server. The TV cloud 3 may be, for example, a server device operated by the manufacturer of the television device 2 . Based on the results of collecting viewing-related information (viewing information) from the television device 2 , the TV cloud 3 provides various services such as recommended information on programs to watch, reservations for programs, and product recommendation information based on the content of the programs viewed, to the television device 2 via the network.

The content providing server 4 is a computer device for operating an EC website (online store) on the Internet. The content providing server 4 is, for example, a server device of an EC platform. The content providing server 4 is a platform for purchasing goods and services via the network based on a user's (consumer's) operation of a terminal device (smartphone 1, etc.). In addition, the content providing server 4 may be a video platform that provides content such as moving images. For example, the content providing server 4 transmits an image of a product to the smartphone 1 based on an operation performed on the smartphone 1 . The content providing server 4 registers redirect_uri in the TV cloud 3 in advance.

Hereinafter, the details of each structure in the information collaboration system S will be described with reference to the drawings following FIG. 2 . FIG. 2 is a block diagram showing an example of the overall configuration of the television device 2 according to the first embodiment. The television device 2 performs display control on the video display unit 233 that is larger than the display unit included in the smartphone 1 (details will be described later).

As shown in FIG. 2 , the television device 2 includes an input terminal 202, tuners 203a to 203g, a signal processing unit 207, a graphics processing unit 208, a voice processing unit 209, an OSD (On Screen Display) signal generation unit 210, and video processing unit 211.

The terrestrial digital broadcast signal received by the terrestrial broadcast receiving antenna 213 is input to the input terminal 202 . The terrestrial digital broadcast signal is supplied to the tuners 203a to 203g via the input terminal 202.

The tuners 203a to 203g are tuners for terrestrial digital broadcasting, and select a broadcast signal of a channel instructed by a control unit 216 to be described later from the terrestrial digital broadcasting signal supplied from the input terminal 202.

However, the television device 2 may have an input terminal for inputting a satellite digital broadcast signal received by a BS/CS digital broadcast receiving antenna. The satellite digital broadcast signal is supplied to the tuner for satellite digital broadcast via this input terminal.

The signal processing unit 207 demodulates a broadcast signal including a digital video signal and an audio signal from the broadcast signal supplied from the tuners 203a to 203g. In addition, the signal processing unit 207 selectively performs predetermined digital signal processing on the video signal included in the digital broadcast signal, and outputs the processed signal to the graphics processing unit 208 . In addition, the signal processing unit 207 selectively performs desired digital signal processing on the speech signal included in the digital broadcast signal, and outputs it to the speech processing unit 209 .

The signal processing unit 207 is connected to a plurality of external input terminals 214a to 214d. These external input terminals 214a to 214d can input analog video signals and audio signals from a DVD (Digital Versatile Disk) video recorder, which is an example of an external device. The signal processing unit 207 digitizes analog video signals and audio signals input from the external input terminals 214a to 214d. In addition, the signal processing unit 207 performs predetermined digital signal processing on the digitized video signal and outputs it to the graphics processing unit 208 . In addition, the signal processing unit 207 performs predetermined digital signal processing on the digitized voice signal and outputs it to the voice processing unit 209 .

The graphics processing unit 208 superimposes the OSD signal generated by the OSD signal generation unit 210 on the digital video signal supplied from the signal processing unit 207, and outputs the superimposed OSD signal to the video processing unit 211. The graphics processing unit 208 can also output either the digital video signal supplied from the signal processing unit 207 or the OSD signal generated by the OSD signal generation unit 210 to the video processing unit 211 .

The video processing unit 211 converts the digital video signal or OSD signal input from the graphics processing unit 208 into an analog video signal or OSD signal in a format that can be displayed on the display screen of the video display unit 233, and outputs the signal. to the video display unit 233. The video display unit 233 is, for example, an LCD or an OLED display.

The voice processing unit 209 converts the digital voice signal input from the signal processing unit 207 into an analog voice signal in a format that can be played back by the speaker 215 , and outputs the converted voice signal to the speaker 215 .

The television device 2 further includes a control unit 216, a deck 217, various interfaces 218 to 221, and a brightness sensor 230. The control unit 216 includes a CPU 216a, a ROM 216b, a RAM 216c, and a nonvolatile memory 216d.

The control unit 216 centrally controls various operations of the television device 2 such as reception operations of broadcast signals such as terrestrial digital broadcast signals and satellite digital broadcast signals. In addition, the control unit 216 controls each unit of the television device 2 in accordance with the operation information from the operation unit 222 or the operation information input from the remote controller 238 via the light receiving unit 223 .

The CPU 216a controls the overall operation of the television device 2 by executing the program stored in the ROM 216b. ROM 216b mainly stores programs executed by CPU 216a. RAM 216c provides a working partition while CPU 216a executes programs. The nonvolatile memory 216d stores various setting information, control information, and the like of the television device 2 .

The control unit 216 is connected to the card holder 217 via the card I/F 225, and the card holder 217 is capable of attaching and detaching the memory card 234. Thereby, the control unit 216 can transmit and receive various information to and from the memory card 234 installed in the card holder 217 via the card I/F 225 .

The control unit 216 is connected to the LAN terminal 226 via the communication I/F 218 . This allows the control unit 216 to transmit and receive various information via the communication I/F 218 with external devices such as the relay device 400 described above and a LAN-compatible HDD (Hard Disk Drive) connected to the LAN terminal 226 . However, the communication I/F 218 may be configured to be wirelessly connected to an external device such as the relay device 400 .

The control unit 216 is connected to the HDMI terminal 227 via an HDMI (registered trademark) (High-Definition Multimedia Interface) I/F 221 . Thereby, the control unit 216 can transmit and receive various information with the external device connected to the HDMI terminal 227 via the HDMI I/F 221 .

The control unit 216 is connected to the USB terminal 228 via a USB (Universal Serial Bus: Universal Serial Interface) I/F 219 . Thereby, the control unit 216 can transmit and receive various information to and from the storage device 237 including a USB HDD or the like connected to the USB terminal 228 via the USB I/F 219 .

The storage device 237 includes, for example, an HDD, an SSD (Solid State Drive), or the like, and is configured to record the digital signal received by the television device 2 as recording data. However, the storage device 237 may be built into the television device 2 .

FIG. 3 is a block diagram showing a partial configuration example of the television device 2 according to the first embodiment. The television device 2 includes a storage unit 241 (ROM 216b, RAM 216c, nonvolatile memory 216d, and storage device 237 in FIG. 2), and a function module that is a function module generated as a result of execution of the program stored in the storage unit 241 by the CPU 216a. unit 242, acquisition unit 243, and display control unit 244.

The transmitting unit 242 transmits various information to external devices. The acquisition unit 243 acquires various information from an external device or reads various information stored in the storage unit 241 .

The display control unit 244 executes display processing for displaying various information on the video display unit 233 . The display control unit 244 causes the video display unit 233 to display an image based on, for example, an image display request from the smartphone 1 (details will be described later).

FIG. 4 is a block diagram showing an example of the overall configuration of the TV cloud 3 according to the first embodiment. As shown in FIG. 4 , the TV cloud 3 includes a communication I/F 301, an operation unit 302, a CPU 303, a memory 304, and a storage device 305.

The communication I/F 301 is an interface for communicating with external devices. The operation unit 302 has input devices such as a keyboard and a mouse, and display devices such as a monitor.

The storage device 305 includes, for example, HDD, SSD, etc., and stores various information. The CPU 303 controls each component of the TV cloud 3 by executing various programs. The memory 304 includes a ROM, a RAM, etc., and stores various programs, various data, etc. used in various calculation processes performed by the CPU 303 .

FIG. 5 is a block diagram showing a partial configuration example of the TV cloud 3 according to the first embodiment. The TV cloud 3 includes a storage unit 311 (memory 304, storage device 305), and an acquisition unit 312, a transmission unit 313, and a generation unit 314, which are functional modules generated as a result of execution of the program stored in the storage unit 311 by the CPU 303.

The storage unit 311 stores programs executed by the CPU 303 and a DB (Data Base: database). Here, an example of the data structure of the DB will be described using FIG. 6 . As shown in Figure 6, in the DB, information including TVID, authentication code, EC server ID and token is stored. In addition, the DB may include, together with the TVID, attribute information of the television device 2 (model of the television, etc.) corresponding to the TVID.

TVID is information for identifying the television device 2 . The authentication code is a code required to obtain a token described later. The EC server ID is information for identifying the content providing server 4 . That is, it is the ID of the EC website server, etc. The token is the information used for authentication. Returning to FIG. 5 , the acquisition unit 312 acquires various information from external devices. The transmitting unit 313 transmits various information to external devices. The generation unit 314 executes an information generation operation on the DB.

Next, the processing flow of each component in the information collaboration system S will be described. FIG. 7 is a flowchart showing the overall processing in the information collaboration system S according to the first embodiment. Here, it is assumed that the user operates the remote control or the like of the television device 2 and starts specifying an EC website with which the smartphone 1 wants to cooperate on a so-called portal screen (a screen for cooperation with an EC website or the like). In addition, the processing of the smartphone 1 shown in FIG. 7 may also be executed by an application program installed in the smartphone 1 .

As described above, in the television device 2, when the user specifies an EC website, in step S1, the transmitter 242 of the television device 2 transmits the information of the EC website (for example, the ID of the EC website, the URL of the EC website, etc.) , and the identifier TVID of the television device 2 is sent to the TV cloud 3 . In this way, the transmitting unit 242 transmits the information regarding the content providing server 4 which is an image providing device that provides images on the EC website to the TV cloud 3 .

The acquisition unit 312 of the TV cloud 3 acquires the EC website information and the TVID from the television device 2 . The generation unit 314 of the TV cloud 3 generates an authentication code, and stores information including the TVID, the EC server ID, which is information identifying the content providing server 4 of the EC website, and the authentication code in the DB of the storage unit 311 . In addition, the generation unit 314 generates a QR code (registered trademark) that is a two-dimensional code based on the authentication code and the URL, which is the access address of the EC website. In addition, the QR code is an example, and other displayed information may also be used. That is, it may also be other forms of display information that can convey the authentication code and the access address information of the EC website. The authentication code may include a part for identifying the manufacturer and a part for identifying the television device 2 .

In step S2, the transmitting unit 313 of the TV cloud 3 transmits the QR code to the television device 2 as the request source. In response to a request from the television device 2, a QR code including a URL as an access address to the EC website and an authentication code is sent.

The acquisition unit 243 of the television device 2 acquires the QR code from the TV cloud 3 . In this way, the acquisition unit 243 of the television device 2 acquires the QR code, which is the access information based on the authentication code and the URL which is the access address of the EC website. The display control unit 244 of the television device 2 displays the QR code on the video display unit 233. In this way, the display control unit 244 displays and outputs the QR code.

In step S3, the smartphone 1 reads the QR code displayed on the video display unit 233 using a QR code reading function implemented by a camera mechanism or the like. As a result, smartphone 1 obtains the URL and authentication code of the EC website. In step S4, if the smartphone 1 obtains the URL and authentication code of the EC website, it accesses the content providing server 4 based on the URL and sends the authentication code.

If the content providing server 4 obtains the authentication code from the smartphone 1, in step S5, it sends the authentication code together with the information identifying the content providing server 4 to the TV cloud 3 to request authentication. In addition, the acquisition unit 312 of the TV cloud 3 acquires the authentication code together with the information identifying the content providing server 4 . In this way, the acquisition unit 312 of the TV cloud 3 acquires the authentication code sent from the content providing server 4 .

The generation unit 314 of the TV cloud 3 refers to the DB of the storage unit 311 and determines whether there is information corresponding to the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312, thereby performing authentication. The generation unit 314 refers to the DB of the storage unit 311, and when there is information corresponding to the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312, generates a token using a known technology. In addition, the generation unit 314 further associates the token with information in the DB that includes the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312 . The information including the information identifying the content providing server 4 and the authentication code acquired by the acquiring unit 312 and further associated with the token also includes the TVID of the requesting television device 2 .

Therefore, the generation unit 314 generates correspondence information that associates the television device 2 corresponding to the above-mentioned authentication code with the token based on the authentication code.

In step S6 , the transmitting unit 313 of the TV cloud 3 transmits the token generated by the generating unit 314 to the content providing server 4 . In this way, the transmitting unit 313 transmits the token based on the authentication code to the content providing server 4 . The content providing server 4 stores information in which the token is associated with the user ID of the smartphone 1 that sent the authentication code.

In step S7, the smartphone 1 logs in to the content providing server 4 and accesses the EC website. As a result, the smartphone 1 displays the EC website screen. Here, the user of the smartphone 1 selects an instruction indicating a television display request for a predetermined link destination on the EC website screen. In step S8, based on the selection, the smartphone 1 transmits the URL of the link destination to the content providing server 4, thereby making a television display request (TV display request). The content providing server 4 acquires the TV display request and the URL of the image display object together from the smartphone 1 .

In step S9, the content providing server 4 sends the token corresponding to the request source smartphone 1 and the URL of the image display object to the TV cloud 3, and makes a display request. The acquisition unit 312 of the TV cloud 3 acquires the token and URL sent by the content providing server 4 . In this way, the acquisition unit 312 acquires the token sent by the content providing server 4 and the URL of the access address of the image to be displayed based on the request from the smartphone 1 .

In step S10 , the TV cloud 3 refers to the DB of the storage unit 311 and determines the TVID corresponding to the token acquired by the acquisition unit 312 . Then, the transmitting unit 313 of the TV cloud 3 transmits the URL of the access address of the image to be displayed to the television device 2 corresponding to the TVID.

The acquisition unit 243 of the television device 2 acquires the URL of the access address of the image to be displayed. In addition, the transmitting unit 242 of the television device 2 accesses the content providing server 4 based on the URL, and the acquiring unit 243 acquires an image based on the access address of the image to be displayed from the content providing server 4 . Then, the display control unit 244 of the television device 2 displays the image acquired by the acquisition unit 243 on the video display unit 233 .

The TV cloud 3 of the first embodiment generates correspondence information that associates the TV device 2 corresponding to the authentication code with the token based on the authentication code. If the token is obtained from the content providing server 4 and the token is obtained from the smart If the access address of the image to be displayed is requested by the mobile phone 1, the access address of the image is notified to the television device 2, so that the television device 2 can display the image corresponding to the request of the smartphone 1. Thereby, the TV cloud 3 can cause the television device 2 capable of displaying a screen larger than the screen of the smartphone 1 to display the image requested by the smartphone 1 .

In addition, the television device 2 outputs access information including an access address and an authentication code to the content providing server 4, acquires the access address of the image to be displayed based on the request from the smartphone 1 from the TV cloud 3, and causes the image to be displayed. on the video display unit 233. Thereby, the television device 2 can display the image requested by the smartphone 1 on the video display unit 233 that is larger than the screen of the smartphone 1 .

(Second Embodiment)

The information collaboration system S of the second embodiment is different from the first embodiment in that the TV cloud 3 differs for each manufacturer of the television device 2 . That is, the information cooperation system S of the second embodiment includes a plurality of TV clouds 3 .

Here, an example of the overall configuration of the information collaboration system S according to the second embodiment will be described. FIG. 8 is a diagram schematically showing an example of the overall configuration of the information collaboration system S according to the second embodiment. In addition, the same structures as those in the first embodiment are denoted by the same reference numerals, and description thereof is omitted. As shown in FIG. 8 , the information collaboration system S has a plurality of TV clouds 3 (TV cloud 3a, TV cloud 3b). The TV cloud 3b can be connected to the television device 2 which is a television set (not shown) of a manufacturer associated with the TV cloud 3b.

Reference numeral 2 is a television. Reference numeral 3 is the TV cloud as a so-called push distribution server. The TV cloud 3 is a television manufacturer that manufactures the television device 2 and provides various services such as viewing programs, reservation program recommendations, and product recommendations based on the content of the viewed programs to the television device 2 via the network based on the results of collecting viewing information from the television device 2 provider's server.

In addition, reference numeral 5 is a television gateway as a common acceptance server. The TV gateway 5 is a server for a manufacturer common website of manufacturers of TV devices that integrates the TV clouds 3 of multiple TV manufacturers and is connected to E-commerce (EC). The information collaboration system S includes a television gateway 5 (server management device) capable of transmitting and receiving information to and from the plurality of TV clouds 3 via a network. In addition, the television gateway 5 is also capable of transmitting and receiving information via the network to and from the measurement server 6 that performs measurement processing for tallying the results of advertisement display. This TV gateway 5 is a cloud server that unites various manufacturers. That is, the TV gateway 5 is a server that integrates the TV clouds 3 of multiple TV manufacturers and connects them to the content providing server 4 . The television gateway 5 issues a client certificate (client_id, client_secret) to the content providing server 4.

In addition, a random key set in x-api-key is predetermined between the TV cloud 3 and the TV gateway 5 . The x-api-key transferred between the television gateway 5 and the content providing server 4 becomes a common key (pass-key).

Reference numeral 4 is a content providing server such as an EC website server. The content providing server 4 is a server of the EC platform. The server that serves as a platform for users, that is, consumers, to purchase goods and services is the content providing server 4 . In addition, the content providing server 4 registers redirect_uri in the television gateway 5 in advance.

Reference numeral 1050 is a user terminal. The user terminal 1050 is a terminal including an application program for connecting the television device 2 and the user terminal 1050 and an optical reading device such as a camera. An example of the user terminal 1050 is the smartphone 1 . In the first embodiment, the user terminal 1050 is explained assuming that the smartphone 1 is used, but the user terminal 1050 is not limited to the smartphone. The user terminal 1050 may be a PC, a tablet terminal, etc., as long as it meets the conditions of the situation. In addition, these terminals can replace the smartphone shown in the first embodiment.

FIG. 9 is a block diagram showing an example of the overall configuration of the television gateway 5 according to the second embodiment. As shown in Fig. 9 , the television gateway 5 includes a communication I/F 501, an operation unit 502, a CPU 503, a memory 504, and a storage device 505.

Communication I/F501 is an interface used for communication between external devices. The operation unit 502 has input devices such as a keyboard and a mouse, and display devices such as a monitor.

The storage device 505 includes, for example, HDD, SSD, etc., and stores various information. The CPU 503 controls each component of the television gateway 5 by executing various programs. The memory 504 includes a ROM, a RAM, etc., and stores various programs, various data, etc. used in various calculation processes performed by the CPU 503 .

FIG. 10 is a block diagram showing a partial configuration example of the television gateway 5 according to the second embodiment. The television gateway 5 includes a storage unit 511 (memory 504, storage device 505), and an acquisition unit 512, a transmission unit 513, and a generation unit 514, which are functional modules generated as a result of execution of the program stored in the storage unit 511 by the CPU 503.

The storage unit 511 stores programs executed by the CPU 503 and a DB (Data Base: database).

The acquisition unit 512 acquires various information from external devices. The transmitting unit 513 transmits various information to external devices. The generation unit 514 performs an information generation operation on the DB.

Next, the processing flow of each component in the information collaboration system S of the second embodiment will be described. FIG. 11 is a flowchart showing the overall processing in the information collaboration system S according to the second embodiment. The flowchart shown in FIG. 11 also assumes a scenario in which the user operates the remote control of the television device 2 and the like, and starts specifying an EC website with which the smartphone 1 wants to cooperate on a so-called portal screen. In addition, it is assumed that the authentication code and token generated by TV Cloud 3 contain information identifying the manufacturer. That is, it is assumed that the TV cloud 3 includes information for identifying its own device in the authentication code and the token.

In addition, since step S21 in FIG. 11 is the same as step S1 in FIG. 7 , description thereof will be omitted. In step S22, the URL authentication code is sent from the TV cloud 3 to the television device 2. The URL authentication code 2010 is information including URL information that identifies the content providing server 4 and an authentication code used for authentication between the content providing server 4 and the TV cloud 3 . The authentication code may include a part for identifying the manufacturer of the television device 2 and a part for identifying the television device 2 . In addition, the part used for identifying the television device 2 included in the authentication code is a random value. In addition, the TV cloud 3 may associate the time when the value is transmitted to the television device 2 as the information in the DB of the storage unit 311 .

Examples of information for URL authentication code 2010 are as follows.

https://XXXXXXX YYYYYYYYY

The X part contains the URL of the content provider server 4, and the Y part contains the OAuth2 authorization code. In the authorization code section there is information that identifies the manufacturer and the television. The information that can identify the manufacturer and the television device 2 may be either one of them. The sending form of the URL authentication code 2010 can also be in any form, as long as it contains the above information.

When the acquisition unit 243 of the television device 2 acquires the URL authentication code 2010 from the TV cloud 3 , the display control unit 244 optically displays and outputs the content of the URL authentication code 2010 as an image or video on the video display unit 233 . In addition, the display form in the display control unit 244 may be a QR code, a barcode, a text, or the like, as long as the information included in the URL authentication code 2010 can be optically displayed and output as an image or video. In addition, in the first embodiment, the description is made using a QR code. However, like this embodiment, it is not limited to a QR code.

In addition, similar to step S3 in FIG. 7 , in step S23 , the user terminal 1050 uses the URL authentication code reading function to read the URL on the video display unit 233 from the image information optically captured by the camera mechanism. Optically displays URL authentication code 2011 information. As a result, the user terminal 1050 obtains the URL and authentication code of the EC website. The authentication code part is a time-limited authentication code and is composed as follows.

"code"：＜authorization code＞，

"state"：＜string＞//Random number

In step S24, if the user terminal 1050 obtains the URL and authentication code of the EC website, it accesses the content providing server 4 based on the URL and sends the authentication code 2020.

The authentication code 2020 is the authentication code part (<authorization code>) of the URL authentication code 2010 and the URL authentication code 2011. The certification code 2021 is as described below.

"code"：＜authorization code＞，

"state"：＜string＞//Random number

In addition, the authentication code 2020 may include URL information of the content providing server 4 in addition to the above content.

In step S25, if the content providing server 4 receives the authentication code 2020, it sends the authentication code 2021 to the television gateway 5 and makes an authentication request. The content providing server 4 sends the authentication request information to the OAuth2 token endpoint (Token Endpoint) of the television gateway 5 , for example. The information of the authentication code 2021 is composed of the following.

Authorization："Basic"+Base64(＜client_id＞+"："+＜client_secret＞)

Content-type: application/x-www-form-urlencoded

·grant_type: "authorization_code"

·code:＜authorization code＞(authentication code)

·redirect_uri: The entry for returning to the EC website of the content providing server 4 and the address registered in advance in the TV gateway 5 .

·client_id: An identifier assigned to each EC website of the content providing server 4. An identifier registered in advance in the television gateway 5 .

The client_secret is allocated by the TV gateway 5 to each website of the content providing server 4 based on the client_id. The TV Gateway 5 website observes the manufacturer extension of the code and redirects.

In step S26, the transmitting unit 313 of the TV gateway 5 refers to the acquired authentication code 2021 and the information identifying the manufacturer included in the authentication code 2021 to determine the TV cloud 3 of the transmission destination. Specifically, the transmitting unit 313 of the television gateway 5 confirms an authorization code, that is, an authentication code, and determines which TV cloud 3 it is.

Then, in step S27, the transmission unit 313 of the television gateway 5 performs an authentication request by sending the authentication request 2022 to the TV cloud 3 of the transmission destination. In this way, the transmission unit 513 of the television gateway 5 transmits the authentication request 2022 to the TV cloud 3 of the transmission destination specified based on the Authorization_code (authentication code) of the authentication code 2021. The information of the authentication request 2022 sent by the transmitting unit 313 of the television gateway 5 is the same as the information of the authentication code 2021 acquired from the content providing server 4 . As examples of other information required for certification 2022, there are the following examples.

GET https://each-maker.example.com/common/devices/id

Authorization："Bearer"+＜access_token＞

The acquisition unit 312 of the TV cloud 3 acquires the authentication code described in the URL authentication code 2010 together with the information identifying the content providing server 4 .

The generation unit 314 of the TV cloud 3 performs authentication by referring to the DB of the storage unit 311 and determining whether there is information corresponding to the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312. The generation unit 314 refers to the DB of the storage unit 311, and generates the token 2030 when there is information corresponding to the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312. In addition, the generation unit 314 further associates the token 2030 with information including the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312 in the above-mentioned DB.

In step S28, the sending unit 313 of the TV cloud 3 sends the token 2030 generated by the generating unit 314 to the TV gateway 5.

Specifically, the transmitting unit 313 of the TV cloud 3 transmits the token response (Token Response) of OAuth2 as the token 2030 to the TV gateway 5 . The OAuth2 access token response (Access Token Response) of this response is composed as follows.

{"access_token": <access token>,

"token_type"："Bearer"，

"expires_in": 3600,

"refresh_token"：＜refresh token＞}

TV cloud 3 brings access_token when accessing TV gateway 5. expires_in is the validity period (seconds) of the access_token. When the access_token is received, it is stored together with the time when it becomes invalid. The access_token is reused until then. The refresh_token is secretly kept by the content providing server 4. This is because, in terms of security, simply placing it in local storage is not good. When each manufacturer issues an access_token or a refresh_token, the television manufacturer can be identified by adding an identifier for identifying the television manufacturer at the beginning.

The acquisition unit 512 of the television gateway 5 acquires the token 2030 . Then, in step S29, the television gateway 5 sends the token 2030 to the content providing server 4 as the token 2031, and the content providing server 4 acquires the token 2031. In addition, the sending unit 313 of the TV cloud 3 may directly send the token to the content providing server 4 .

The content providing server 4 stores information that associates the token 2031 with the user ID of the user terminal 1050 that sent the authentication code.

Then, in step S30, the content providing server 4 sends the token 2031 and the user ID 2040 to the television gateway 5 in response. Thereby, the content providing server 4 can transmit the user ID of the user of the user terminal 1050 to the television gateway 5 .

The structure of the information of token + user ID 2040 sent by the content providing server 4 is as follows.

POST https://tv-common.example.com/common/users/id

Authorization："Basic"+Base64(＜client_id＞+"："+＜client_secret＞)

Content-type: application/x-www-form-urlencoded

{grant_type："access_token"，

access_token: <access token> (information issued as the access token in step S28),

client_id: An identifier assigned to each website of the content providing server 4. Register in advance on the manufacturer's common website,

user_id: User ID in the website of content providing server 4,

Preference: ＜Current user attributes (current user attributes: user’s date of birth, gender, zip code, purchase history, etc.)＞}

The acquisition unit 512 of the television gateway 5 acquires the token + user ID 2040 from the content providing server 4 . In step S31, the transmission unit 513 of the TV gateway 5 determines the TV cloud 3 of the transmission destination based on the token + user ID 2040, and transmits the device ID request 2041 (TVID) to the TV cloud 3 of the transmission destination. In addition, when transmitting the device ID request 2041, the transmitting unit 513 of the television gateway 5 may transmit a token.

The device ID request 2041 is a request for the TV gateway 5 to inquire the device_id (TVID) of the TV from each manufacturer (TV cloud 3) using the access_token of OAuth2, and is, for example, the following request.

GET https://each-maker.example.com/common/devices/id

·Authorization："Bearer"+＜access＿token＞

·x-api-key: <Random key specified by the manufacturer's common website and each manufacturer>

·Content-type: application/json

·client_id: An identifier assigned to each manufacturer's common website

The TV cloud 3 refers to the DB of the storage unit 311 and acquires the TVID corresponding to the acquired token. In addition, the TV cloud 3 may also acquire the information of the device corresponding to the acquired TVID (the attribute information of the television device 2 of the TVID). In step S32, the transmitting unit 313 of the TV cloud 3 transmits information such as TVID to the television gateway 5 as the device ID response 2050. As an example of device ID response 2050, there is the following example

·"device_id": <id> (TVID assigned to TV device 2 by TV cloud 3)

·"model": <model name> (The model of the television device 2 is the display screen inch, pixel number information such as 2K, 4K, 8K, etc.)

In step S33 , the generation unit 514 of the television gateway 5 adds the information binding information obtained by associating the acquired TVID (device ID), the user ID, and the model information (model) of the television device 2 to the DB as information. The storage unit 511 registers.

In addition, the generation unit 514 of the television gateway 5 generates a pass key 2051. In addition, in step S34, the transmitting unit 513 transmits the common key to the content providing server 4. The universal key contains the following information.

·"pass_key": <pass_key>, (This pass_key is used as the ID during the operation from the operation command 2090 to the operation command 2093 after step S44)

·"expires_in": 86400, (expires_in is in the initial access, even if the preference cannot be prepared, the return will be delayed for 10 days.)

·"model": <model name> (It is information about the model that the device ID responds to. The model of the TV device 2 is information on the number of pixels such as display screen inches, 2K, 4K, 8K, etc.)

In addition, in step S35, the generation unit 514 of the television gateway 5 stores the generated common key in the storage unit 511.

When the content providing server 4 acquires the universal key from the television gateway 5, it stores the information included in the universal key. Specifically, the following information is stored for each user ID of the EC website.

·access_token

·refresh_token

·pass＿key

·model//TV model information for collaboration

In step S36, the user terminal 1050 logs in to the service provided by the content providing server 4 by activating the application program. As a result, the smartphone 1 displays the EC website screen. The EC website screen output by this application also outputs a button for connecting to the television device 2 . Furthermore, in step S37, the content providing server 4 sends the device information 2070 to the user terminal 1050 based on the login in step S36. The device information 2070 mentioned here is any one, two or three combinations of the device ID, user ID, and model name included in the common key 2051.

The user of the smartphone 1 selects a button for connecting to the television device 2 as a link destination on the EC website screen. In step S38, the user terminal 1050 transmits the URL of the link destination to the content providing server 4 based on the selection, thereby transmitting a TV display request (TV display request 2071).

When the content providing server 4 receives the TV display request 2071 from the user terminal 1050 , in step S39 , the content providing server 4 sends the display request 2072 including the token, the common key, and the URL of the link destination to the TV gateway 5 . The television device 2 makes a display request. The information of the display request 2072 is structured as follows.

POST https://tv-common.example.com/common/devices/control

Authorization："Bearer"+＜access_token＞x-api-key：＜pass＿key＞

Content-type: application/jison

{"command_type"："keycode"

"keycode": "<common key code>"}

{"command_type"："webview"，

"site": "<Website URL>",

"Template"："full"}

The acquisition unit 512 of the television gateway 5 receives the information of the display request 2072 including the token, the common key, and the URL of the link destination from the content providing server 4 . Then, the acquisition unit 512 retrieves pass_key from the header of x-api-key.

In step S40, the acquisition unit 512 uses the common key (pass_key) and the information stored in the storage unit 511 to determine the access address and the access source. In step S41, the transmitting unit 513 transmits the information including the token and the URL to the TV cloud 3 based on the discrimination result, and performs a display request. In this way, the transmission unit 513 transmits the token and the access address of the image to be displayed to the TV cloud 3 of the transmission destination. In addition, the television gateway 5 measures the number of accesses for each access source and manufacturer.

The display request 2073 sent by the sending unit 513 to the TV cloud 3 includes the token, client ID, URL, and message. Examples of this information are described below.

POST https://each-maker.example.com/common/devices/control

Authorization: "Bearer"+＜access_token＞x-api-key:＜Random key specified by the manufacturer's common website and each manufacturer＞

Content-type: application/json

{"command_type"："keycode"，

"keycode"：＜common key code＞，

"client_id"：<client_id>，

"messageid：＜message ID＞}

{"command_type"："webview"，

"site": <Website URL> (Website URL for TV),

"template": "full",

"client_id"：<client_id>，

"message id"：＜message ID＞}

The acquisition unit 312 of the TV cloud 3 receives the display request 2073 from the television gateway 5 . The acquisition unit 312 extracts the access_token from the Authorization header of the display request 2073 and identifies the television device 2 . In step S42, the transmitting unit 313 of the TV cloud 3 outputs a display request 2074 to the television device 2 based on the determination result. In addition, the display request can also be replaced with the manufacturer's own display request instruction. In addition, if necessary, TV Cloud 3 can also count the visits of each client_id and make requirements for the TV.

In step S43, the television device 2 activates the browser in response to the display request, executes javascript (registered trademark) through onLoad, onClick events, etc., and displays and outputs the image of the URL destination to be displayed. In addition, the television device 2 notifies the measurement server 6 of a display operation result notification 2080 identifying the service provider, the user, the TV manufacturer, and the advertisement to be displayed. The measurement server 6 counts the results of the TV cloud 3 displaying advertisements on the plurality of television devices 2 . Based on the statistical results, the manufacturer or the owner of the television gateway 5 or the measurement server 6 requests advertising fees from the E-commerce platform holding the content providing server 4 .

The application program of the user terminal 1050 can operate the screen of the television device 2 based on the operation instruction 2090 in step S44. The operation instruction 2090 is sent to the content providing server 4 according to the operation from the user terminal 1050.

In step S45, the content providing server 4 sends the operation instruction 2091 including the common key code to the television gateway 5 based on the operation instruction 2090 sent in step S44. The common key code is a command configured to correspond to the operation button of the television operation remote control. Features numbers, cross cursor, volume/channel/power, color keys, function keys, media controls, manufacturer-specific commands. The manufacturer-specific instructions refer to instructions used by each manufacturer to operate independently. That is, the manufacturer-specific instruction refers to an operation instruction set by each manufacturer and unique to the manufacturer. A common key code is a key code used to perform common operations between manufacturers in addition to instructions specific to the manufacturer.

Numeric instructions are "11", "12", "0", "1", "2", "3", "4", "5", "6", "7", "8", "9" , ".".

The cross cursor commands are "up", "down", "left", "right", "page up", "page down", "page left", "page right", "enter" , "Exit", "Return".

The volume/channel/power commands are "power", "power off", "power on", "volume up", "volume down", "channel selection forward", "channel selection backward".

The color keys are "blue", "red", "green", and "yellow".

The function key commands are "Electronic Program Guide", "Initial Configuration", "Select Broadcast Type", "Input Selection", "Display Information", "Mute", "Content Menu", "Closed Subtitles".

The media control instructions are "play", "stop", "pause", "replay", "fast forward", "rewind", "skip forward", "skip backward", and "record".

If the TV gateway 5 receives the operation instruction 2091 in step S45, it sends the operation instruction 2092 to the TV cloud 3 in step S46. Operation instruction 2092 is the same instruction as operation instruction 2091. In step S47, the television gateway 5 sends the response message ID 2094 to the content providing server 4 as a response message. The message ID has the following composition.

{message id：＜message ID＞}

When the TV cloud 3 receives the operation command 2092 from the TV gateway 5, it sends the operation command 2093 to the television device 2 in step S48. The operation command 2093 is the same or equivalent information as the operation command 2092 and is a manufacturer's own command to operate the display screen of the television device 2 . The TV cloud 3 replaces the operation command 2092 with an operation command 2093 that is a company key code for operating the television device 2 . When the standardization of operation commands of the television device 2 has been advanced, the operation command 2092 can be directly used as the operation command 2093 without converting it.

The television device 2 operates the image displayed on the video display unit 233 of the television device 2 based on the operation command 2093 . In addition, in step S49, the television device 2 notifies the measurement server 6 of the operation result notification 2081 identifying the operation command.

The flowchart shown in FIG. 11 is a comprehensive description of the process of multiple manufacturers accessing the content providing server 4 of the platform. However, like the TV cloud 3 of the first embodiment, manufacturers can also access the content providing server individually. 4. In this case, TV Cloud 3 combines the actions of TV Gateway 5 . At this time, the exchange of information between the TV cloud 3 and the TV gateway 5 is omitted.

The TV gateway 5 obtains the authentication code from the content providing server 4, sends the authentication code to the TV cloud 3 of the transmission destination determined based on the authentication code, obtains the token and the access address of the image of the display object from the content providing server 4, and sends the authentication code to the TV cloud 3. The TV cloud 3 of the destination sends the token and the access address of the image of the display object. This makes it possible to process the content without having to determine which of the plurality of TV clouds 3 the content should be transmitted to on the content providing server 4 side.

In addition, the program executed in each device (user terminal 1050, television device 2, TV cloud 3, content providing server 4, television gateway 5, measurement server 6) of this embodiment can be in an installable form or in an installable form. Files in the form of execution are recorded in CD (Compact Disc: Compact Disc) - ROM (Read Only Memory: Read Only Memory), Floppy Disk (FD), CD-R (Recordable: Writable Disk), DVD (Digital Versatile Disk: Digital Versatile disk), etc. are provided in a storage medium readable by a computer device. In addition, the program can also be provided or distributed via a network such as the Internet.

(Third Embodiment)

The information collaboration system S of the third embodiment has the same overall configuration as the information collaboration system S of the second embodiment. In the information cooperation system S of the third embodiment, the television gateway 5 acquires tokens not only from the TV cloud 3 but also from the content providing server 4, and uses these tokens to match the ID of the television device 2 with the ID of the user terminal 1050. User ID collaboration.

In addition, the structure of the data stored in the TV cloud 3 shown in FIG. 6 is different. Specifically, TV Cloud 3 stores HA-ID instead of TVID shown in FIG. 6 . In addition, PF-ID is stored instead of the EC website server ID shown in FIG. 6 . HA-ID is identification information including TC-ID, which is the company ID of the television manufacturer, and TV-ID, which is the device ID of the television device 2 . PF-ID is the company ID of the video platform. TC-ID becomes the identifier for identifying TV Cloud 3. In addition, PF-ID is an identifier for identifying the content providing server 4 .

Next, the processing flow of each component in the information collaboration system S of the third embodiment will be described. FIG. 12 is a flowchart showing the overall processing in the information collaboration system S according to the third embodiment. The flowchart shown in FIG. 12 also assumes a scenario in which the user operates the remote control of the television device 2 and the like, and starts from a so-called portal screen to specify an EC website (for example, a server that accepts content provision) with which the smartphone 1 wants to cooperate. . In addition, it is assumed that the authentication code and token generated by TV Cloud 3 contain information identifying the manufacturer. That is, it is assumed that the TV cloud 3 includes information for identifying its own device in the authentication code and the token.

In addition, step S61 in FIG. 12 is the same as step S1 in FIG. 7 and step S12 in FIG. 11 . Furthermore, in step S61, the television device 2 transmits the PF-ID corresponding to the EC website (video platform) specified by the user to the TV cloud 3.

In step S62, the TV cloud 3 responds by sending the QR code including the URL of the TV gateway 5 and the URL authentication code to the TV device 2. This QR code includes the URL of the television gateway 5 and the following time-limited authentication code.

{"code"：＜authorization code＞(authentication code),

"state":HEX(JSON.stringify({"tcid";<TC-ID>,"pfid";<PF-ID>,"salt";<random string>})+hash)(status information)}

The URL authentication code is information including URL information identifying the TV gateway 5, an authentication code used for authentication between the content providing server 4 and the TV cloud 3, and state information. The authentication code may include a part for identifying the manufacturer of the television device 2 and a part for identifying the television device 2 . In addition, the part used for identifying the television device 2 included in the authentication code is a random value. In addition, the TV cloud 3 may associate the time when the value is transmitted to the television device 2 as the information in the DB of the storage unit 311 . The status information may also include information encoding the manufacturer's TC-ID and the video platform's PF-ID.

Examples of URL authentication code information are as follows.

https://XXXXXXX YYYYYYYYY

The X part contains the URL of the TV gateway 5, and the Y part contains the OAuth2 authorization code. The authorization code section contains information that can identify the manufacturer and the television. The information that can identify the manufacturer and the television device 2 may be either one of them. The sending form of the URL authentication code can also be in any form, as long as it contains the above information. In addition, the Y part can also contain status information.

When the acquisition unit 243 of the television device 2 acquires the URL authentication code from the TV cloud 3 , the display control unit 244 optically displays and outputs the content of the URL authentication code as an image or video on the video display unit 233 . In addition, the display form in the display control unit 244 may be a QR code, a barcode, a text, or the like, as long as the information included in the URL authentication code can be optically displayed and output as an image or video. In addition, in the first embodiment and the second embodiment, the QR code was used in the description. However, like the present embodiment, it is not limited to the QR code.

In addition, similar to step S3 in FIG. 7 and step S23 in FIG. 11 , in step S63 , the user terminal 1050 uses the URL authentication code reading function to read the image information optically captured by the camera mechanism. The information of the URL authentication code is optically displayed on the display unit 233 . Thereby, the user terminal 1050 acquires the URL, authentication code, etc. of the television gateway 5 . The authentication code part is a time-limited authentication code and is composed as follows.

"code"：＜authorization code＞，

"state"：＜string＞//Random number

In step S64, if the user terminal 1050 obtains the URL, authentication code, and status information of the TV gateway 5, it accesses the TV gateway 5 based on the URL, sends the authentication code and status information, and performs an authentication request. In addition, the status information includes TC-ID and PF-ID as mentioned above.

The information sent when authentication is requested is as follows.

"code"：＜authorization code＞，

"state"：＜string＞//Random number

In step S65, if the acquisition unit 512 of the television gateway 5 receives the authentication code and the status information, the transmission unit 513 of the television gateway 5 transmits a screen in HTML format including a collaboration button indicating a collaboration instruction to the user terminal 1050. The HTML can also include the URL and parameters for accessing PF-ID's OAuth2 authorization endpoint (Authorization Endpoint).

The user terminal 1050 acquires the above-mentioned screen in HTML format. Then, when the collaboration button is pressed by the user operation of the user terminal 1050 (step S66), an approval request is made to the content providing server 4 as the video platform. In addition, the content providing server 4 receives the approval request and sends information on the purpose of the response to the user terminal 1050 (step S67).

The information sent when the above-mentioned authorization request is made has the following structure, for example.

Authorization："Basic"+Base64(＜client_id＞+"："+＜client_secret＞)Request

{

"response_type"："code"

"code": <authorization code> (authentication code)

"redirect_uri": <TGW Endpoint> (the end point of TV gateway 5)

"client_id": <TG-ID> (ID of TV gateway 5)

"scope": <VPF provided> (authentication scope of the token)

"state": HEX(JSON.stringify({"tcid"; <TC-ID>, "pfid"; <PF-ID>, "salt"; <random string>})+hash) (status information)

}

When the user information is not registered in the content providing server 4, user registration processing is performed between the user terminal 1050 and the content providing server 4 (step S68). Here, the user registration process refers to a process of registering a user ID and password, which are information used to log in to the content providing server 4, or registering the user's attribute information.

Next, the user terminal 1050 makes a login request to the content providing server 4, and the content providing server 4 responds in accordance with the login request (step S69). As an example of this response, the following information (authorization code) is output.

Response

{"code"：＜authorization code＞，

"state"：＜state＞}

When the user terminal 1050 receives the above response, it redirects the cooperation instruction to the television gateway 5 (step S70). In addition, the user terminal 1050 may also send the above-mentioned approval code to the television gateway 5 .

If the acquisition unit 512 of the television gateway 5 receives the redirection indicating the cooperation instruction, the television gateway 5 determines the manufacturer based on the TC-ID included in the status information acquired from the user terminal 1050 . That is, the television gateway 5 assigns the manufacturer (step S71).

Then, in step S72, the transmission unit 513 of the television gateway 5 performs a token request by transmitting the authentication code to the TV cloud 3 of the transmission destination (step S72).

The information sent when requesting the token has the following structure, for example.

Authorization："Basic"+Base64(TG－ID+"："+＜client_secret＞)

Request Parameters

{

grant_type: "authorization_code",

code: <authorization code> (authentication code),

state: <string> (status information),

redirect_uri：＜redirect_uri＞，

client_id：＜TG－ID＞}

The generation unit 314 of the TV cloud 3 determines whether there is information corresponding to the information identifying the content providing server 4 (for example, information included in the status information) and the authentication code acquired by the acquisition unit 312 by referring to the DB of the storage unit 311, thereby authenticating. The generation unit 314 refers to the DB of the storage unit 311, and generates a token (first token) when there is information corresponding to the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312. In addition, the generation unit 314 further associates the first token with information including the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312 in the DB.

In step S73, the transmitting unit 313 of the TV cloud 3 transmits the first token generated by the generating unit 314 to the television gateway 5.

Specifically, the transmitting unit 313 of the TV Cloud 3 transmits the OAuth2 token response (Token Response) as a token to the TV gateway 5 . The OAuth2 access token response (Access token Response) of this response is composed as follows.

Response

{"access_token": <access token>,

"token_type"："Bearer"，

"expires_in": 3600,

"refresh_token"：＜refresh token＞}

TV cloud 3 brings access_token when accessing TV gateway 5. expires_in is the validity period (seconds) of the access_token. When the access_token is received, it is stored together with the time when it becomes invalid. The access_token is reused until then. The refresh_token is secretly kept by the content providing server 4. This is because, in terms of security, simply placing it in local storage is not good. When each manufacturer issues an access_token or a refresh_token, the television manufacturer can be identified by adding an identifier for identifying the television manufacturer at the beginning.

When the acquisition unit 512 of the television gateway 5 acquires the first token, the transmission unit 513 of the television gateway 5 transmits the information including the authorization code and makes a token request to the content providing server 4 (step S74).

The information sent when requesting the token has the following structure, for example.

Authorization："Basic"+Base64(TG－ID+"："+＜client_secret＞)

Request

{grant_type: "authorization_code",

code: <code> (approval code),

state: <string> (status information),

redirect_uri：＜TGW Endpoint＞，

client_id：＜TG－ID＞

}

The content providing server 4 determines the user ID corresponding to the authorization code based on the authorization code obtained from the television gateway 5 . Then, the content providing server 4 generates a token based on the user ID, that is, a second token.

In step S75, the content providing server 4 sends the generated second token to the television gateway 5. In addition, the content providing server 4 may store the second token, the user ID, and the user attribute information in association with each other.

Specifically, the content providing server 4 sends the OAuth2 token response (Token Response) as a token to the television gateway 5 . The OAuth2 access token response (Access token Response) of this response is composed as follows.

{"access_token": <access token>,

"token_type"："Bearer"，

"expires_in": 3600,

"refresh_token"：＜refresh token＞}

The acquisition unit 512 of the television gateway 5 acquires the second token from the content providing server 4 . Then, the transmitting unit 513 of the television gateway 5 transmits the second token to the content providing server 4 and makes a user information request to the content providing server 4 (step S76).

The information sent when requesting user information has the following structure, for example.

Authorization: "Bearer"+<access token>)

The content providing server 4 searches for the user ID and the user's attribute information corresponding to the second token acquired from the television gateway 5, and sends these information to the television gateway 5 as a response (step S77). Thereby, the acquisition unit 512 of the television gateway 5 acquires the user ID and the user's attribute information. The response information is composed as follows.

Response

{"user_id": <UR-ID> (user ID in the website of content providing server 4),

"Preference": <Current user attributes> (User's date of birth, gender, zip code, purchase history, etc.)}

In step S78, the content providing server 4 sends the PF-ID and performs a device information request. The information sent in this device information request has the following structure, for example.

Authorization："Basic"+Base64(PF－ID+"："+＜client_secret＞)

When the acquisition unit 512 of the TV gateway 5 receives the device information request from the content providing server 4, the sending unit 513 of the TV gateway 5 sends the first token corresponding to the second token sent in step S74 to the TV cloud 3 , and perform a device information request (step S79). The information sent in this device information request has the following structure, for example.

Authorization: "Bearer"+<access token>)

When the acquisition unit 312 of the TV cloud 3 acquires the first token, it acquires the HA-ID corresponding to the first token and the information of the device corresponding to the HA-ID (the television device corresponding to the HA-ID 2 attribute information).

In step S80, the transmitting unit 313 of the TV cloud 3 sends the HA-ID and other information to the television gateway 5 as a response. The acquisition unit 512 of the television gateway 5 acquires the HA-ID and information about the device corresponding to the HA-ID. Examples of this response include the following.

Response

{

·"device_id"：＜HA-ID＞(HA-ID)

·"model": <model name> (The model of the television device 2 is the display screen inch, pixel number information such as 2K, 4K, 8K, etc.)}

In step S81 , the generation unit 514 of the television gateway 5 associates the acquired HA-ID, the user ID, the model information (model) which is the attribute information of the television device 2 , and the PF-ID as a DB. The information is registered in the storage unit 511. In addition, the generation unit 514 of the television gateway 5 may further include the user's attribute information in the binding information.

In addition, the generation unit 514 of the television gateway 5 generates a common key. In addition, in step S82, the transmitting unit 513 transmits the common key to the content providing server 4. The universal key contains the following information.

·"pass_key": <pass_key>, (use this pass_key as ID when operating the command)

·"expires_in": 86400, (expires_in is in the initial access, even if the preference cannot be prepared, the return will be delayed for 10 days.)

·"model": <model name> (It is information about the model that the device ID responds to. The model of the TV device 2 is information on the number of pixels such as display screen inches, 2K, 4K, 8K, etc.)

In addition, the generation unit 514 of the television gateway 5 stores the generated common key in the storage unit 511 .

When the content providing server 4 acquires the universal key from the television gateway 5, it stores the information included in the universal key. Specifically, the content providing server 4 stores the following information for each user ID of the EC website.

·access_token

·refresh_token

·pass＿key

·model//Collaborated TV model information

The TV gateway 5 acquires the authentication code from the user terminal 1050, sends the authentication code to the TV cloud 3 of the transmission destination determined based on the authentication code, acquires the first token from the TV cloud 3, and acquires the second token from the content providing server 4. . Then, the television gateway 5 transmits the second token to the content providing server 4 to obtain the user ID, and transmits the first token to the TV cloud 3 to obtain the ID (for example, HA-ID) of the television device 2 . In this way, the television gateway 5 acquires the user ID from the content providing server 4 and acquires the ID of the television device 2 from the TV cloud 3 , thereby being able to associate the user ID with the ID of the television device 2 .

In this case, since the television gateway 5 stores the user ID in association with the ID of the television device 2 , the TV cloud 3 does not need to manage the user ID, and the information management burden of the TV cloud 3 can be reduced. In addition, since the television gateway 5 acquires the authentication code from the user terminal 1050, it is not necessary to send the authentication code from the content providing server 4 to the television gateway 5, and the processing load on the content providing server 4 can also be reduced. That is, the television gateway 5 can appropriately execute the process of cooperating the identifier of the receiver (the ID of the television device 2) and the identifier of the terminal (the user ID of the user terminal 1050).

(4th Embodiment)

The information collaboration system S of the fourth embodiment has the same overall configuration as the information collaboration system S of the second embodiment. In the second embodiment, the case where the authentication code is also included in the QR code has been described. However, in the information collaboration system S of the fourth embodiment, the authentication code is separately displayed as a personal identification code (pin code).

Next, the processing flow of each component in the information collaboration system S of the fourth embodiment will be described. Step S21 in FIG. 13 is the same as step S21 in FIG. 11 and step S1 in FIG. 7 , so the description is omitted.

In step S91, the TV cloud 3 sends the QR code including the URL to the television device 2. In addition, the TV cloud 3 transmits the personal identification code corresponding to the authentication code to the television device 2 .

Examples of URL information included in the QR code are as follows.

https://XXXXXXX

In the section of X, there is the URL of the content providing server 4. The URL of the QR code can be sent in any form, as long as it contains the above information.

When the acquisition unit 243 of the television device 2 acquires the QR code and the personal identification code from the TV cloud 3 , the display control unit 244 optically displays and outputs the QR code as an image or video on the video display unit 233 . In addition, the display control unit 244 displays and outputs the personal identification code.

In step S92, the user terminal 1050 uses the reading function to read the information of the URL optically displayed on the video display unit 233 from the image information optically photographed by the camera mechanism.

In step S93, the user terminal 1050 starts the application program (APP) so as to be in a state in which input of the personal identification code can be received.

In step S94, if the PIN code is input through user operation, the user terminal 1050 obtains the PIN code as the authentication code. Steps S24 to S35 are respectively the same as steps S24 to S35 in FIG. 11 .

The TV cloud 3 of the fourth embodiment sends the personal identification code corresponding to the authentication code to the television device 2, and the television device 2 displays the personal identification code. Then, the user of the user terminal 1050 performs an input operation based on the personal identification code, and the user terminal 1050 sends the personal identification code to the content providing server 4 as an authentication code.

In this case, even if the authentication code cannot be included in the QR code together with the URL, the authentication code can be transmitted from the user terminal 1050 to the content providing server 4 .

(fifth embodiment)

The information collaboration system S of the fifth embodiment has the same overall configuration as the information collaboration system S of the third embodiment. In the information cooperation system S of the fifth embodiment, the television gateway 5 transmits campaign information to the television device 2 as promotion information for promoting the use of the television in the information cooperation system S of the third embodiment. Processing in which the ID of the device 2 cooperates with the user ID of the user terminal 1050 . In the information cooperation system S, when the television device 2 is instructed to cooperate with the ID of the television device 2 and the user ID of the user terminal 1050 based on the promotion information, the television device 2 executes the process of making the ID of the television device 2 and the user ID of the user terminal 1050 cooperate. Collaborative processing.

In the information cooperation system S, when the television device 2 makes a request to obtain program guide information, the television gateway 5 receives the request to obtain the program table information via the TV cloud 3 . The TV gateway 5 acquires the program table composition information from the content providing server 4 and sends the program table composition information to the TV cloud 3 . The TV cloud 3 acquires the program guide composition information, and sends the acquired program guide composition information to the television device 2 . The program table composition information includes enterprise information, channel information, program information, CM information, and VOD information.

Alternatively, in the information cooperation system S, if the television device 2 makes a request to obtain program guide information, the television gateway 5 receives the request to obtain the program guide information. The television gateway 5 acquires the program guide configuration information and sends the program guide configuration information to the television device 2 . The program table composition information includes enterprise information, channel information, program information, CM information, and VOD information. It should be noted that the file server that implements the television gateway 5 stores program table composition information. That is, the television gateway 5 stores the program guide composition information, and transmits the stored program guide composition information to the television device 2 in response to a request to obtain the program guide information from the television device 2 .

The television gateway 5 stores promotional information and transmits the promotional information in response to a request from the television device 2 when transmitting the program guide configuration information.

Here, Figure 14-1 is used to illustrate the content of promotional information. FIG. 14-1 is a diagram showing an example of promotion information. The promotional information has a normal collaboration data part 330 and a promotional collaboration data part 340 .

The normal collaboration data section 330 includes: information indicating an object (Object) of ID collaboration data (idbind); information indicating a base URL in which a URL of an image file is stored (img_base_url); and information indicating an image explaining the collaboration method (explanation_img). ; and information indicating an image explaining the collaboration cancellation method (explanation_img).

The publicity cooperation data part 340 includes: information indicating an Array of the object of the publicity information (idbind_campaign); information indicating the TV manufacturer of the publicity target (tv); and information indicating a base URL in which the URL of the image file is stored (img_base_url). ); Information indicating an image that explains the contents of the promotion (campaign_img); Information indicating an image that is displayed when collaboration is nearly completed (hasbound_img); Information indicating an image that explains the collaboration method (explanation_img); Information indicating that the recommended license is based on IFA -The information of the tracking image of the ID (recommend_tracking_img); the information indicating the promotion start date and time (start); and the information indicating the promotion end date and time (end).

The information indicating the image in the publicity collaboration data section 340 may be set differently for each TV manufacturer using a macro or the like. This makes it possible to distribute different promotional images to a plurality of TV manufacturers with a simple configuration.

In addition, the content of another promotional information will be described using Figure 14-2. FIG. 14-2 is a diagram showing another example of promotion information. The promotional information has a general collaboration data part 330, a promotional collaboration data part 340, and one or more advertisement information parts 350.

The normal collaboration data part 330 includes: information indicating an object (Object) of ID collaboration data (idbind); information indicating a base URL in which a URL of an image file is stored (img_base_url); and information indicating an image describing the collaboration method (bind). explanation_img); and information indicating an image explaining the collaboration cancellation method (explanation_img of unbind).

The publicity cooperation data part 340 includes: information indicating an Array of the object of the publicity information (idbind_campaign); information indicating the TV manufacturer of the publicity target (tv); and information indicating a base URL in which the URL of the image file is stored (img_base_url). ); Information indicating an image that explains the contents of the promotion (campaign_img); Information indicating an image that is displayed when collaboration is nearly completed (hasbound_img); Information indicating an image that explains the collaboration method (explanation_img); Information indicating that the recommended license is based on IFA -The information of the tracking image of the ID (recommend_tracking_img); the information indicating the promotion start date and time (start); and the information indicating the promotion end date and time (end).

The information indicating the image in the publicity collaboration data section 340 may be set differently for each TV manufacturer using a macro or the like. This makes it possible to distribute different promotional images to a plurality of TV manufacturers with a simple configuration.

The advertisement information section 350 includes: arrangement information (tv) indicating the TV manufacturer to be displayed; an ad_info unique identifier (id); advertisement information (ad_info) including information indicating the display type of the advertisement and the content of the advertisement; and the display start date. Time (start); displays the end date and time (end).

In addition, as shown in Figures 14-2 and 15, the advertisement information includes: information indicating the display type of the advertisement (type); information indicating the ID of the displayed screen (place); when the display type of the advertisement is text The displayed text message (message); the URL of the display image (image) displayed when the display type of the advertisement is image; the URL (movie) of the dynamic image displayed when the display type of the advertisement is movie; and the expression Information about the display period of the advertisement (period). The above-mentioned text message, the URL of the display image, and the URL of the dynamic image are examples of information indicating the content of the advertisement.

The promotional information shown in Figure 14-2 includes: an advertisement information part 350a whose advertisement type is text; an advertisement information part 350b whose advertisement type is image; and an advertisement information part 350c whose advertisement display type is movie. When the television device 2 receives the promotional information shown in FIG. 14-2 , it displays an advertisement for text messages, an advertisement for displaying pictures, and an advertisement for displaying dynamic images.

Next, the procedure of collaborative processing based on promotional information will be described using FIG. 16-1. FIG. 16-1 is a flowchart showing the display process of promotional information.

Based on the user's operation, the television device 2 makes a request to obtain the program list configuration information (program list) of the EC website designated by the user with respect to the TV cloud 3 . If the television device 2 makes a request to obtain the program list information, the TV gateway 5 receives the request to obtain the program list information via the TV cloud 3 . The TV gateway 5 acquires the program table composition information from the content providing server 4 and sends the program table composition information to the TV cloud 3 . The TV cloud 3 acquires the program guide composition information, and sends the acquired program guide composition information to the television device 2 . The television device 2 displays the program guide composition information (step S101). The program table composition information includes enterprise information, channel information, program information, CM information, and VOD information.

The television device 2 makes a request to obtain promotional information from the television gateway 5 . When the television device 2 fails to acquire the promotional information from the television gateway 5 via the TV cloud 3 (step S102: No), the process ends.

The television device 2 makes a request to obtain promotional information from the television gateway 5 . When the television device 2 acquires the promotional information from the TV gateway 5 via the TV cloud 3 (step S102: Yes), and if the cooperation with the content providing server 4 is not completed (step S103: yes), the television device 2 combines the promotional information with the The program guide composition information is displayed together (step S104). As a method of determining whether collaboration with the content providing server 4 has been completed, there is a method in which the television device 2 retains a log of the presence or absence of past collaboration processing requests in advance and performs the determination based on the log.

In the publicity information, when a selection is made to apply for publicity, the television device 2 displays the survey information (step S105). This survey is a survey that receives input of the user's attributes (gender, address, etc.). In addition, the survey information can also be displayed at other times.

After inputting the survey, the television device 2 makes a collaboration instruction request (step S106).

Next, the sequence of displaying advertisements based on another promotional information will be described using FIG. 16-2. FIG. 16-2 is a flowchart illustrating display processing of an advertisement of another promotional information.

The process shown in FIG. 16-2 is a process executed by the television device 2 in the program list display process. In response to the user's operation, the television device 2 makes a request to the television gateway 5 to acquire the program table configuration information (program table) of the EC website specified by the user. When the television device 2 makes a request to obtain the program table information, the television gateway 5 receives the request to obtain the program table information. The television gateway 5 transmits the program table configuration information to the television device 2 . The television device 2 displays program guide composition information. The program table composition information includes enterprise information, channel information, program information, CM information, and VOD information.

As described above, when the program guide configuration information is displayed, the television device 2 makes a request to obtain the promotional information from the television gateway 5 . When the television device 2 does not acquire the promotional information from the television gateway 5 (step S101: No), the television device 2 ends the process.

When the television device 2 acquires the promotional information from the television gateway 5 (step S101: Yes), it refers to the promotional information and determines whether there is advertising information within the valid period based on the display start date and time and the display end date and time (step S102 ). When there is no advertisement information within the valid period (step S102: No), the television device 2 ends the process.

When there is advertisement information within the validity period (step S102: Yes), the television device 2 extracts the information to be displayed from the promotional information (step S103). Then, the television device 2 displays all the extracted information or executes the loop process of step S104 until the program list display is terminated by user operation.

In the loop process of step S104, the television device 2 displays the advertisement according to the type of advertisement (step S105).

In addition, when the user selects the meaning of applying for recruitment promotion while the advertisement is being displayed (for example, during the loop process of step S104), the television device 2 displays the consultation information, receives the input of the consultation information, and cooperates. Instruction request. This consultation is a consultation that receives input of the user's attributes (gender, address, etc.).

It should be noted that the television device 2 may refer to the promotional information, first display a screen where the advertised application can be selected, and then execute the process of the flowchart shown in FIG. 16-2 . That is, the television device 2 may independently execute the processing related to advertisement display and the processing related to ID cooperation.

Next, the cooperation processing sequence will be described using FIG. 17 . FIG. 17 is a flowchart showing the cooperation processing procedure. It is assumed that the authentication code and token generated by TV Cloud 3 contain information identifying the manufacturer. That is, it is assumed that the TV cloud 3 includes information for identifying its own device in the authentication code and the token.

Before executing the process of the flowchart shown in FIG. 16-1 or 16-2, the television device 2 generates an IFA-ID using a random number and notifies the TV cloud 3 (step S111). The IFA-ID is a numerical value with enough digits to ensure that it is unique. In addition, the television device 2 may transmit the TV model name of the television device 2 . In addition, bearer authentication may also be performed in steps S111 and S112.

The TV cloud 3 sends the IFA-ID to the TV gateway 5 (step S112). Then, in step S113, the process of the flowchart shown in FIG. 16-1 or 16-2 is executed. In step S113, if the cooperation instruction is issued, the television device 2 performs a QR code request (step S114).

In addition, step S114 in FIG. 17 is the same as step S1 in FIG. 7 , step S12 in FIG. 11 , and step S61 in FIG. 12 . Furthermore, in step S114, the television device 2 transmits the PF-ID corresponding to the EC website (video platform) specified by the user to the TV cloud 3.

In step S115, the TV cloud 3 responds by sending a QR code including the URL of the TV gateway 5 and the URL authentication code to the TV device 2. This QR code includes the URL of the television gateway 5 and the following time-limited authentication code.

{"code"：＜authorization code＞(authentication code),

"state":HEX(JSON.stringify({"tcid";<TC-ID>,"pfid";<PF-ID>,"salt";<random string>})+hash)(status information)}

The URL authentication code is information including URL information identifying the TV gateway 5, an authentication code used for authentication between the content providing server 4 and the TV cloud 3, and status information. The authentication code may include a part for identifying the manufacturer of the television device 2 and a part for identifying the television device 2 . In addition, the part used for identifying the television device 2 included in the authentication code is a random value. In addition, the TV cloud 3 may associate the time when the value is transmitted to the television device 2 as the information in the DB of the storage unit 311 . The status information may also include information encoding the manufacturer's TC-ID and the video platform's PF-ID.

Examples of URL authentication code information are as follows.

https://XXXXXXX YYYYYYYYY

The X part contains the URL of the TV gateway 5, and the Y part contains the OAuth2 authorization code. The authorization code section contains information that can identify the manufacturer and the television. The information that can identify the manufacturer and the television device 2 may be either one of them. The sending form of the URL authentication code can also be in any form, as long as it contains the above information. In addition, the Y part can also contain status information.

When the acquisition unit 243 of the television device 2 acquires the URL authentication code from the TV cloud 3 , the display control unit 244 optically displays and outputs the content of the URL authentication code as an image or video on the video display unit 233 . In addition, the display form in the display control unit 244 may be a QR code, a barcode, a text, or the like, as long as the information included in the URL authentication code can be optically displayed and output as an image or video. In addition, in the first embodiment and the second embodiment, the QR code was used in the description. However, like the present embodiment, it is not limited to the QR code.

In addition, similarly to step S3 in FIG. 7 , step S23 in FIG. 11 , and step S63 in FIG. 12 , in step S116 , the user terminal 1050 reads the URL authentication code from the image information optically captured by the camera mechanism. The function reads the information of the URL authentication code optically displayed on the video display unit 233. Thereby, the user terminal 1050 acquires the URL, authentication code, etc. of the television gateway 5 . The authentication code part is a time-limited authentication code and is composed as follows.

"code"：＜authorization code＞，

"state"：＜string＞//Random number

In step S117, if the user terminal 1050 obtains the URL, authentication code and status information of the TV gateway 5, it accesses the TV gateway 5 based on the URL, sends the authentication code and status information, and performs an authentication request. In addition, the status information includes TC-ID and PF-ID as mentioned above.

The information sent when authentication is requested is as follows.

"code"：＜authorization code＞，

"state"：＜string＞//Random number

In step S118, if the acquisition unit 512 of the television gateway 5 receives the authentication code and the status information, the transmission unit 513 of the television gateway 5 transmits a screen in HTML format including a collaboration button indicating a collaboration instruction to the user terminal 1050. The HTML can also include the URL and parameters for accessing PF-ID's OAuth2 authorization endpoint (Authorization Endpoint).

The user terminal 1050 acquires the above-mentioned screen in HTML format. Then, when the collaboration button is pressed by the user operation of the user terminal 1050 (step S119), an approval request is made to the content providing server 4 as the video platform. In addition, the content providing server 4 receives the approval request and sends information on the purpose of the response to the user terminal 1050 (step S120).

The information sent when the above-mentioned authorization request is made has the following structure, for example.

Authorization："Basic"+Base64(＜client_id＞+"："+＜client_secret＞)Request

{

"response_type"："code"

"code": <authorization code> (authentication code)

"redirect_uri": <TGW Endpoint> (the end point of TV gateway 5)

"client_id": <TG-ID> (ID of TV gateway 5)

"scope": <VPF provided> (authentication scope of the token)

"state": HEX(JSON.stringify({"tcid"; <TC-ID>, "pfid"; <PF-ID>, "salt"; <random string>})+hash) (status information)

}

Furthermore, when the television device 2 requests the television gateway 5 to confirm the cooperation status via the TV cloud 3 at the time point of step S119 (steps S151 and S152), the television gateway 5 transmits information to the effect that the cooperation is not completed. Send to the television device 2 (step S153, step S154).

When the user information is not registered in the content providing server 4, user registration processing is performed between the user terminal 1050 and the content providing server 4 (step S121). Here, the user registration process refers to a process of registering a user ID and password, which are information used to log in to the content providing server 4, or registering the user's attribute information.

Next, the user terminal 1050 makes a login request to the content providing server 4, and the content providing server 4 responds in accordance with the login request (step S122). As an example of this response, the following information (authorization code) is output.

Response

{"code"：＜authorization code＞，

"state"：＜state＞}

When the user terminal 1050 receives the above response, it redirects the cooperation instruction to the television gateway 5 (step S123). In addition, the user terminal 1050 may also send the above-mentioned approval code to the television gateway 5 .

If the acquisition unit 512 of the television gateway 5 receives the redirection indicating the cooperation instruction, the television gateway 5 determines the manufacturer based on the TC-ID included in the status information acquired from the user terminal 1050 . That is, the television gateway 5 assigns the manufacturer (step S124).

Then, in step S125, the transmission unit 513 of the television gateway 5 performs a token request by transmitting the authentication code to the TV cloud 3 of the transmission destination (step S125).

The information sent when requesting the token has the following structure, for example.

Authorization："Basic"+Base64(TG－ID+"："+＜client_secret＞)

Request Parameters

{

grant_type: "authorization_code",

code: <authorization code> (authentication code),

state: <string> (status information),

redirect_uri：＜redirect_uri＞，

client_id：＜TG－ID＞

}

The generation unit 314 of the TV cloud 3 determines whether there is information corresponding to the information identifying the content providing server 4 (for example, information included in the status information) and the authentication code acquired by the acquisition unit 312 by referring to the DB of the storage unit 311, thereby authenticating. The generation unit 314 refers to the DB of the storage unit 311, and generates a token (first token) when there is information corresponding to the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312. In addition, the generation unit 314 further associates the first token with information including the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312 in the DB.

In step S126, the transmitting unit 313 of the TV cloud 3 transmits the first token generated by the generating unit 314 to the television gateway 5.

Specifically, the transmitting unit 313 of the TV Cloud 3 transmits the OAuth2 token response (Token Response) as a token to the TV gateway 5 . The OAuth2 access token response (Access token Response) of this response is composed as follows.

Response

{"access_token": <access token>,

"token_type"："Bearer"，

"expires_in": 3600,

"refresh_token"：＜refresh token＞}

TV cloud 3 brings access_token when accessing TV gateway 5. expires_in is the validity period (seconds) of the access_token. When the access_token is received, it is stored together with the time when it becomes invalid. The access_token is reused until then. The refresh_token is secretly kept by the content providing server 4. This is because, in terms of security, simply placing it in local storage is not good. When each manufacturer issues an access_token or a refresh_token, the television manufacturer can be identified by adding an identifier for identifying the television manufacturer at the beginning.

When the acquisition unit 512 of the television gateway 5 acquires the first token, the transmission unit 513 of the television gateway 5 transmits information including the authorization code and makes a token request to the content providing server 4 (step S127).

The information sent when requesting the token has the following structure, for example.

Authorization："Basic"+Base64(TG－ID+"："+＜client_secret＞)

Request

{

grant_type: "authorization_code",

code: <code> (approval code),

state: <string> (status information),

redirect_uri：＜TGW Endpoint＞，

client_id：＜TG－ID＞}

The content providing server 4 determines the user ID corresponding to the authorization code based on the authorization code obtained from the television gateway 5 . Then, the content providing server 4 generates a token based on the user ID, that is, a second token.

In step S128, the content providing server 4 sends the generated second token to the television gateway 5. In addition, the content providing server 4 may store the second token, the user ID, and the user attribute information in association with each other.

Specifically, the content providing server 4 sends the OAuth2 token response (Token Response) as a token to the television gateway 5 . The OAuth2 access token response (Access token Response) of this response is composed as follows.

{"access_token": <access token>,

"token_type"："Bearer"，

"expires_in": 3600,

"refresh_token"：＜refresh token＞}

The acquisition unit 512 of the television gateway 5 acquires the second token from the content providing server 4 . Then, the transmitting unit 513 of the television gateway 5 transmits the second token to the content providing server 4 and makes a user information request to the content providing server 4 (step S129).

The information sent when requesting user information has the following structure, for example.

Authorization: "Bearer"+<access token>)

The content providing server 4 searches for the user ID and the user's attribute information corresponding to the second token acquired from the television gateway 5, and sends these information to the television gateway 5 as a response (step S130). Thereby, the acquisition unit 512 of the television gateway 5 acquires the user ID and the user's attribute information. The response information is composed as follows.

Response

{"user_id": <UR-ID> (user ID in the website of content providing server 4),

"Preference": <Current user attributes> (User's date of birth, gender, zip code, purchase history, etc.)}

In step S131, the content providing server 4 sends the PF-ID and performs a device information request. The information sent in this device information request has the following structure, for example.

Authorization："Basic"+Base64(PF－ID+"："+＜client_secret＞)

When the acquisition unit 512 of the TV gateway 5 receives the device information request from the content providing server 4, the sending unit 513 of the TV gateway 5 sends the first token corresponding to the second token sent in step S127 to the TV cloud 3 , and perform a device information request (step S132). The information sent in this device information request has the following structure, for example.

Authorization: "Bearer"+<access token>)

When the acquisition unit 312 of the TV cloud 3 acquires the first token, it acquires the HA-ID corresponding to the first token and the information of the device corresponding to the HA-ID (the television device corresponding to the HA-ID 2 attribute information).

In step S133, the transmitting unit 313 of the TV cloud 3 sends the HA-ID and other information as a response to the television gateway 5. The acquisition unit 512 of the television gateway 5 acquires the HA-ID and information about the device corresponding to the HA-ID. Examples of this response include the following.

Response

{

·"device_id"：＜HA-ID＞(HA-ID)

·"model": <model name> (The model of the television device 2 is the display screen inch, pixel number information such as 2K, 4K, 8K, etc.)

}

In step S134, the generation unit 514 of the television gateway 5 associates the acquired HA-ID, the user ID, the model information (model) which is the attribute information of the television device 2, and the PF-ID as a DB. The information is registered in the storage unit 511. In addition, the generation unit 514 of the television gateway 5 may further include the user's attribute information in the binding information.

In step S135, the television gateway 5 responds to the user terminal 1050 together with the above-mentioned authorization code (step S135).

After step S134, when the television device 2 requests the television gateway 5 to confirm the cooperation status via the TV cloud 3 (steps S136 and S137), the television gateway 5 transmits information indicating that the cooperation has been completed (identification that the cooperation has been completed). (information on the cooperating content providing server 4, etc.) is sent to the television device 2 (steps S138 and S139). In addition, the television gateway 5 notifies the content providing server 4 of the IFA-ID (step S140).

In addition, when the IFA-ID is updated in the television device 2, the updated IFA-ID is notified to the TV cloud 3 (step S141). TV cloud 3 sends the updated IFA-ID to TV gateway 5. The television gateway 5 sends the updated IFA-ID to the content providing server 4 (step S143).

Next, the cooperation cancellation process will be described using the flowchart shown in FIG. 18 . FIG. 18 is a flowchart showing collaboration cancellation processing. Based on the user's operation, the television device 2 makes a collaboration cancellation request to the TV cloud 3 (step S161). Based on the cancellation request from the television device 2, the TV cloud 3 makes a cooperation cancellation request to the television gateway 5 (step S162). In addition, in steps S161 and S162, the television device 2 or the TV cloud 3 may also send the IFA-ID together with the collaboration cancellation request.

The television gateway 5 notifies the content providing server 4 of the cooperation cancellation request (step S163). The content providing server 4 deletes the generated second token. The TV gateway 5 deletes the binding information and notifies the TV cloud 3 of the deletion (step S164). The TV cloud 3 notifies the television device 2 that the binding information has been deleted (step S165). In addition, TV Cloud 3 can also delete the 1st token. In addition, the content providing server 4 notifies the television gateway 5 of the cancellation of the cooperation (step S166), and the television gateway 5 notifies the TV cloud 3 of the cancellation of the cooperation (step S167).

Next, a processing sequence for canceling collaboration via an operation of the user terminal 1050 will be described using FIG. 19 . FIG. 19 is a flowchart showing the processing sequence of canceling cooperation via the operation of the user terminal 1050.

It is assumed that the user operates the remote control of the television device 2 and the like, and the user specifies that he or she wants to cancel the content providing server 4 that cooperates with the smartphone 1 on a so-called portal screen.

Step S180 in FIG. 19 is the same as step S1 in FIG. 7 and step S12 in FIG. 11 . Furthermore, in step S180 , the television device 2 transmits the PF-ID corresponding to the content providing server 4 specified by the user to the TV cloud 3 .

In step S181, the TV cloud 3 responds by sending the QR code including the URL of the TV gateway 5 and the URL authentication code to the TV device 2. This QR code includes the URL of the television gateway 5 and the following time-limited authentication code.

{"code"：＜authorization code＞(authentication code),

"state":HEX(JSON.stringify({"tcid";<TC-ID>,"pfid";<PF-ID>,"salt";<random string>})+hash)(status information)}

The URL authentication code is information including URL information identifying the TV gateway 5, an authentication code used for authentication between the content providing server 4 and the TV cloud 3, and status information. The authentication code may include a part for identifying the manufacturer of the television device 2 and a part for identifying the television device 2 . In addition, the part used for identifying the television device 2 included in the authentication code is a random value. In addition, the TV cloud 3 may associate the time when the value is transmitted to the television device 2 as the information in the DB of the storage unit 311 . The status information may also include information encoding the manufacturer's TC-ID and the video platform's PF-ID.

Examples of URL authentication code information are as follows.

https://XXXXXXX YYYYYYYYY

The X part contains the URL of the TV gateway 5, and the Y part contains the OAuth2 authorization code. The authorization code section contains information that can identify the manufacturer and the television. The information that can identify the manufacturer and the television device 2 may be either one of them. The sending form of the URL authentication code can also be in any form, as long as it contains the above information. In addition, the Y part can also contain status information.

When the acquisition unit 243 of the television device 2 acquires the URL authentication code from the TV cloud 3 , the display control unit 244 optically displays and outputs the content of the URL authentication code as an image or video on the video display unit 233 . In addition, the display form in the display control unit 244 may be a QR code, a barcode, a text, or the like, as long as the information included in the URL authentication code can be optically displayed and output as an image or video. In addition, in the first embodiment and the second embodiment, the QR code was used in the description. However, like the present embodiment, it is not limited to the QR code.

In addition, similarly to step S3 in FIG. 7 and step S23 in FIG. 11 , in step S182 , the user terminal 1050 uses the URL authentication code reading function to read the image information in view from the image information optically captured by the camera mechanism. The information of the URL authentication code is optically displayed on the image display unit 233. Thereby, the user terminal 1050 acquires the URL, authentication code, etc. of the television gateway 5 . The authentication code part is a time-limited authentication code and is composed as follows.

"code"：＜authorization code＞，

"state"：＜string＞//Random number

In step S183, if the user terminal 1050 obtains the URL, authentication code and status information of the TV gateway 5, it accesses the TV gateway 5 based on the URL, sends the authentication code and status information, and performs an authentication request. In addition, the status information includes TC-ID and PF-ID as mentioned above.

The information sent when authentication is requested is as follows.

"code"：＜authorization code＞，

"state"：＜string＞//Random number

In step S184, if the acquisition unit 512 of the television gateway 5 receives the authentication code and the status information, the transmission unit 513 of the television gateway 5 transmits a screen in HTML format including a collaboration cancel button indicating a collaboration cancellation instruction to the user terminal 1050 send. The HTML can also include the URL and parameters for accessing PF-ID's OAuth2 authorization endpoint (Authorization Endpoint).

The user terminal 1050 acquires the above-mentioned screen in HTML format. Then, when the collaboration cancel button is pressed by the user operation of the user terminal 1050 (step S185), an approval request is made to the content providing server 4 as the video platform. In addition, the content providing server 4 receives the approval request and sends information on the purpose of the response to the user terminal 1050 (step S186).

The information sent when the above-mentioned authorization request is made has the following structure, for example.

Authorization："Basic"+Base64(＜client_id＞+"："+＜client_secret＞)Request

{

"response_type"："code"

"code": <authorization code> (authentication code)

"redirect_uri": <TGW Endpoint> (the end point of TV gateway 5)

"client_id": <TG-ID> (ID of TV gateway 5)

"scope": <VPF provided> (authentication scope of the token)

"state":HEX(JSON.stringify({"tcid";<TC-ID>,"pfid";<PF-ID>,"salt";<random string>})+hash)(status information)}

In addition, when the television device 2 requests the television gateway 5 to confirm the cooperation status via the TV cloud 3 at the time point of step S185 (steps S251 and S252), the television gateway 5 sends information on the purpose of the cooperation to The television device 2 transmits (step S253, step S254).

Next, the user terminal 1050 makes a login request to the content providing server 4, and the content providing server 4 responds in accordance with the login request (step S188). As an example of this response, the following information (authorization code) is output.

Response

{"code"：＜authorization code＞，

"state"：＜state＞}

When the user terminal 1050 receives the above response, it redirects the cooperation instruction to the television gateway 5 (step S189). In addition, the user terminal 1050 may also send the above-mentioned approval code to the television gateway 5 .

Then, in step S72, the transmission unit 513 of the television gateway 5 performs a token request by transmitting the authentication code to the TV cloud 3 of the transmission destination (step S190).

The information sent when requesting the token has the following structure, for example.

Authorization："Basic"+Base64(TG－ID+"："+＜client_secret＞)

Request Parameters

{grant_type: "authorization_code",

code: <authorization code> (authentication code),

state: <string> (status information),

redirect_uri：＜redirect_uri＞，

client_id：＜TG－ID＞

}

The generation unit 314 of the TV cloud 3 determines whether there is information corresponding to the information identifying the content providing server 4 (for example, information included in the status information) and the authentication code acquired by the acquisition unit 312 by referring to the DB of the storage unit 311, thereby authenticating. When the generation unit 314 refers to the DB of the storage unit 311 and there is information corresponding to the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312, the transmission unit 313 of the TV cloud 3 sends the first token to The television gateway 5 sends (step S191).

Specifically, the transmitting unit 313 of the TV Cloud 3 transmits the OAuth2 token response (Token Response) as a token to the TV gateway 5 . The OAuth2 access token response (Access token Response) of this response is composed as follows.

Response

{"access_token": <access token>,

"token_type"："Bearer"，

"expires_in": 3600,

"refresh_token"：＜refresh token＞}

TV cloud 3 brings access_token when accessing TV gateway 5. expires_in is the validity period (seconds) of the access_token. When the access_token is received, it is stored together with the time when it becomes invalid. The access_token is reused until then. The refresh_token is secretly kept by the content providing server 4. This is because, in terms of security, simply placing it in local storage is not good. When each manufacturer issues an access_token or a refresh_token, the television manufacturer can be identified by adding an identifier for identifying the television manufacturer at the beginning.

When the acquisition unit 512 of the television gateway 5 acquires the first token, the transmission unit 513 of the television gateway 5 transmits the information including the authorization code and makes a token request to the content providing server 4 (step S192).

The information sent when requesting the token has the following structure, for example.

Authorization："Basic"+Base64(TG－ID+"："+＜client_secret＞)

Request

{

grant_type: "authorization_code",

code: <code> (approval code),

state: <string> (status information),

redirect_uri：＜TGW Endpoint＞，

client_id：＜TG－ID＞

}

In step S193, the content providing server 4 sends the generated second token to the television gateway 5.

Specifically, the content providing server 4 sends the OAuth2 token response (Token Response) as a token to the television gateway 5 . The OAuth2 access token response (Access token Response) of this response is composed as follows.

{"access_token": <access token>,

"token_type"："Bearer"，

"expires_in": 3600,

"refresh_token"：＜refresh token＞}

The acquisition unit 512 of the television gateway 5 acquires the second token from the content providing server 4 . Then, the transmitting unit 513 of the television gateway 5 transmits the second token to the content providing server 4 and makes a user information request to the content providing server 4 (step S194).

The information sent when requesting user information has the following structure, for example.

Authorization: "Bearer"+<access token>)

The content providing server 4 searches for the user ID and the user's attribute information corresponding to the second token acquired from the television gateway 5, and sends these information to the television gateway 5 as a response (step S195). Thereby, the acquisition unit 512 of the television gateway 5 acquires the user ID and the user's attribute information. The response information is composed as follows.

Response

{"user_id": <UR-ID> (user ID in the website of content providing server 4),

"Preference": <Current user attributes> (User's date of birth, gender, zip code, purchase history, etc.)}

The transmitting unit 513 of the television gateway 5 transmits the first token to the TV cloud 3 and performs a device information request (step S196). The information sent in this device information request has the following structure, for example.

Authorization: "Bearer"+<access token>)

When the acquisition unit 312 of the TV cloud 3 acquires the first token, it acquires the HA-ID corresponding to the first token and the information of the device corresponding to the HA-ID (the television device corresponding to the HA-ID 2 attribute information).

In step S197, the transmitting unit 313 of the TV cloud 3 sends the HA-ID and other information as a response to the television gateway 5. The acquisition unit 512 of the television gateway 5 acquires the HA-ID and information about the device corresponding to the HA-ID. Examples of this response include the following.

Response

{

·"device_id"：＜HA-ID＞(HA-ID)

·"model": <model name> (The model of the television device 2 is the display screen inch, pixel number information such as 2K, 4K, 8K, etc.)}

The television gateway 5 deletes the binding information and notifies the content providing server 4 of the deletion (step S198). In addition, the TV gateway 5 may also notify the TV cloud 3 that the binding information has been deleted.

When the television device 2 requests the television gateway 5 to confirm the cooperation status via the TV cloud 3 after step S198 (steps S199 and S200), the television gateway 5 sends information to the television device 2 indicating that cooperation is not performed. (Step S201, step S202).

In the above-mentioned embodiment, the case where promotional information is displayed when the program list is displayed has been described. However, it may also be possible to display promotional information at a designated time during program broadcast (a program in which moving image content is linearly distributed) via the network. When an advertisement is displayed on the screen, promotional information is displayed.

For example, the promotional information may be displayed using a clickable advertisement as shown in FIG. 20 . FIG. 20 is an example of information of a clickable advertisement. The advertisement information includes: information (ad_list) indicating an Array of advertisement information objects (Object); information indicating an advertisement type (ad_type); information indicating a URL of an advertisement image (img_url), and the like.

In the above-mentioned embodiment, in the process of the flowchart shown in FIG. 17 , the case where the television gateway 5 makes a user information request to the content providing server 4 and acquires the UR-ID from the content providing server 4 has been described. However, the present invention is not limited to this. this. For example, a modification of the flowchart of FIG. 17 is shown in FIG. 21 . Description of the same parts as the processing explained in FIG. 17 is omitted. Instead of providing the UR-ID in steps S128 or S130 shown in FIG. 21, the television gateway 5 may issue a temporary UR-ID and include it in the HTML format code in step S118. This parameter is included in the value of "state". In this case, the user terminal 1050 transmits the value to the content providing server 4 in step S120. In addition, as described above in the flowchart of FIG. 12 , the television gateway 5 may issue a temporary UR-ID.

The television gateway 5 of this embodiment stores promotional information in advance and transmits the promotional information to the television device 2 at a predetermined time such as when the television device 2 displays a program list. The promotional information has an advertisement information part 350 that includes information indicating the display type of the advertisement and information indicating the content of the advertisement.

In addition, the TV gateway 5 acquires the authentication code from the user terminal 1050, sends the authentication code to the TV cloud 3 of the transmission destination determined based on the authentication code, acquires the first token from the TV cloud 3, and acquires the second token from the content providing server 4. Token. Then, the television gateway 5 transmits the second token to the content providing server 4 to obtain the user ID, and transmits the first token to the TV cloud 3 to obtain the ID (for example, HA-ID) of the television device 2 . In this way, the television gateway 5 acquires the user ID from the content providing server 4 and acquires the ID of the television device 2 from the TV cloud 3 , thereby being able to associate the user ID with the ID of the television device 2 .

In this case, since the television gateway 5 stores the user ID in association with the ID of the television device 2 , the TV cloud 3 does not need to manage the user ID, and the information management burden of the TV cloud 3 can be reduced. In addition, since the television gateway 5 acquires the authentication code from the user terminal 1050, it is not necessary to send the authentication code from the content providing server 4 to the television gateway 5, and the processing load on the content providing server 4 can also be reduced. That is, the television gateway 5 can appropriately execute the process of cooperating the identifier of the receiver (the ID of the television device 2) and the identifier of the terminal (the user ID of the user terminal 1050). In addition, the television gateway 5 can facilitate the process of linking the ID of the television device 2 and the user ID of the user terminal 1050 by outputting promotional information.

In addition, the television gateway 5 includes advertisement information in the promotional information, and the advertisement information includes information indicating the display type of the advertisement and information indicating the content of the advertisement. Therefore, the television device 2 switches the display mode according to the display type of the advertisement and outputs the advertisement information. This can further facilitate processing of cooperation with the user ID of the user terminal 1050 . In addition, the television gateway 5 includes a plurality of advertisement information in the publicity information, so that the television device 2 can sequentially output a plurality of advertisements.

In addition, the television gateway 5 coordinates the ID of the television device 2 with the user ID of the user terminal 1050 and then transmits the IFA-ID to the content providing server 4 . This allows the television gateway 5 to provide information that can identify the television device 2 without having to disclose the ID of the television device 2 to the content providing server 4 .

Although several embodiments of the present application have been described, these embodiments are provided as examples only and are not intended to limit the scope of the application. For example, the television device in the above embodiment may be an electronic device that does not have a display mechanism, such as a set-top box or a video recorder, but has a reception function for outputting a video signal to an external display device. In addition, these new embodiments can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the spirit of the application. These embodiments and modifications thereof are included in the scope and gist of the application, and are included in the scope of the invention described in the claims and their equivalents.

For example, among the image icons displayed on the user terminal and which can be enlarged and displayed on the television device, a button instructing the television device to enlarge the display may be provided on or near the image icon. Alternatively, The color, shape, and display form of the image icon that can be displayed in an enlarged manner are changed so that it can be clearly recognized from other image icons that cannot be displayed in an enlarged manner. In addition, when an enlarged display is instructed from the user terminal to the television device, or when display processing is performed on the television device, a voice notification may be made via the user terminal or the television device.

Claims (6)

1. A server management device capable of transmitting and receiving information to and from a plurality of server devices storing information associating an identifier of a broadcast receiving device, an authentication code, an identifier of a content providing device, and a 1 st token,

   the server management device is provided with:

   a storage unit that stores promotion information that promotes associating an identifier of the broadcast receiving apparatus with an identifier of a terminal apparatus of a user of the content providing apparatus;

   a promotion information transmitting unit that transmits the promotion information to the broadcast receiving apparatus;

   An authentication code transmitting unit that transmits the authentication code to the broadcast receiving apparatus in response to a request based on the promotion information from the broadcast receiving apparatus;

   an authentication request acquisition unit that acquires an authentication request including the authentication code, an identifier of a content providing device, and an identifier of the server device from a terminal device that acquired the authentication code;

   a cooperation instruction acquisition unit that acquires, from the terminal device, a notification of a cooperation instruction of an identifier of the broadcast receiving device and a user identifier of the terminal device;

   a 1 st token acquisition unit that acquires a 1 st token corresponding to the authentication code from a server device corresponding to the authentication request after acquiring the notification of the cooperation instruction;

   a 2 nd token acquisition unit that acquires a 2 nd token corresponding to the user identifier of the terminal device from a content providing device corresponding to the authentication request;

   a broadcast receiving apparatus identifier acquisition unit that acquires an identifier of a broadcast receiving apparatus corresponding to the 1 st token from the server apparatus;

   a user identifier acquisition unit that acquires a user identifier of a terminal device corresponding to the 2 nd token from the content providing device; and

   And a registration unit that registers an identifier of the broadcast receiving apparatus corresponding to the 1 st token and a user identifier of the terminal apparatus corresponding to the 2 nd token in association with each other.
2. The server management apparatus according to claim 1, wherein,

   the server management device further includes:

   a 2 nd identifier acquisition unit that acquires a 2 nd identifier of the broadcast receiving apparatus generated by the broadcast receiving apparatus; and

   and a 2 nd identifier transmitting unit that, after the registration unit registers the identifier of the broadcast receiving device corresponding to the 1 st token and the user identifier of the terminal device corresponding to the 2 nd token in association with each other, transmits the 2 nd identifier of the broadcast receiving device corresponding to the 1 st token to the content providing device of the acquisition source of the 2 nd token.
3. The server management apparatus according to claim 1, wherein,

   the promotion information transmitting unit transmits the promotion information together with program table information.
4. The server management apparatus according to claim 1, wherein,

   the promotion information transmitting unit transmits the promotion information by including the promotion information in the selectable advertisement information.
5. The server management apparatus according to any one of claims 1 to 4, wherein,

   The promotion information has advertisement information including information indicating a display type of an advertisement and information indicating advertisement content.
6. The server management apparatus according to claim 5, wherein,

   the promotion information includes a plurality of advertisement information.