JP7769068B2 - Server management device, method and program - Google Patents

Description

The present invention relates to a server management device , method, and program .

In recent years, technology has emerged that allows a receiver and a terminal to work together to send and receive information. For example, a receiver can send information received from a website to a terminal.

Patent No. 5898431

As described above, in order for the receiver, terminal, and content provider device that provides content such as websites to link together and send and receive information, it is necessary to link the terminal user's identifier with the receiver's identifier in advance, and it is desirable to perform the linking process appropriately.

Therefore, the problem to be solved by the present invention is to provide a server management device , method, and program that can appropriately execute processing for linking a receiver identifier and a terminal identifier.

A server management device according to an embodiment is a server management device capable of transmitting and receiving information to and from a plurality of server devices that store information associating an identifier of a broadcast receiving device, an authentication code, an identifier of a content providing device, and a first token, and includes: an acquisition unit that accepts a request to acquire program guide information via the server device in response to a request to acquire program guide information from the broadcast receiving device, and acquires program configuration information from the content providing device; a storage unit that stores promotion information that promotes associating the identifier of the broadcast receiving device with a user identifier of a terminal device of a user of the content providing device; and a transmission unit that transmits the program configuration information and the promotion information to the broadcast receiving device, and the acquisition unit receives the authentication code and the promotion information from the terminal device that has acquired the authentication code sent by the server device to the broadcast receiving device in response to a request based on the promotion information from the broadcast receiving device. and a generation unit that acquires an authentication request including an identifier of a content providing device and an identifier of a server device, acquires from the terminal device a notification of an instruction to link between the identifier of a broadcast receiving device and the user identifier of the terminal device, and after acquiring the notification of the instruction to link, acquires a first token corresponding to the authentication code from the server device corresponding to the authentication request, acquires a second token corresponding to the user identifier of the terminal device from the content providing device corresponding to the authentication request, acquires an identifier of the broadcast receiving device corresponding to the first token from the server device, acquires a user identifier of the terminal device corresponding to the second token from the content providing device, and associates the identifier of the broadcast receiving device corresponding to the first token acquired by the acquisition unit with the user identifier of the terminal device corresponding to the second token and registers them in a recording unit.

FIG. 1 is a diagram illustrating an overview of an example of the overall configuration of an information linkage system according to the first embodiment. FIG. 2 is a block diagram showing an example of the overall configuration of the television device of the first embodiment. FIG. 3 is a block diagram showing an example of a partial configuration of the television device of 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 an example of a partial configuration 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 of the first embodiment. FIG. 7 is a flowchart showing the overall processing in the information linkage system of the first embodiment. FIG. 8 is a diagram illustrating an outline of an example of the overall configuration of an information linkage system according to the second embodiment. FIG. 9 is a block diagram showing an example of the overall configuration of a common reception server according to the second embodiment. FIG. 10 is a block diagram showing an example of the partial configuration of a common reception server according to the second embodiment. FIG. 11 is a flowchart showing the overall processing in the information linkage system of the second embodiment. FIG. 12 is a flowchart showing the overall processing in the information linkage system of the third embodiment. FIG. 13 is a flowchart showing the overall processing in the information linkage system of the fourth embodiment. FIG. 14 is a diagram illustrating an example of promotion information in the information link system according to the fifth embodiment. FIG. 15 is a flowchart showing a display process of promotion information in the information link system according to the fifth embodiment. FIG. 16 is a flowchart showing the procedure of a linkage process in the information linkage system according to the fifth embodiment. FIG. 17 is a flowchart showing a linkage cancellation process in the information linkage system according to the fifth embodiment. FIG. 18 is a flowchart showing a processing procedure for canceling cooperation via an operation of a user terminal in the information cooperation system according to the fifth embodiment. FIG. 19 is a diagram illustrating an example of information on a clickable advertisement in the information linking system according to the fifth embodiment. FIG. 20 is a flowchart showing a linkage processing procedure in the information linkage system of the modified example.

The following describes in detail embodiments (first and second embodiments) of the server device, broadcast receiving device, server management device, information linkage system, and program of the present invention, with reference to the drawings.

(First embodiment)
First, an example of the overall configuration of an information linkage system S according to a first embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram illustrating an overview of an example of the overall configuration of the information linkage system S according to the first embodiment. The information linkage 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) site server. The TV cloud 3 is capable of communicating with the television device 2 and the content providing server 4 via a public communication line such as the Internet. Furthermore, the smartphone 1 is capable of wireless communication with the content providing server 4 and the TV cloud 3 via a base station.

Smartphone 1 is an example of an information terminal owned by a user of television device 2. Smartphone 1 includes a communication I/F (Interface), an audio input unit (microphone), a group of sensors, a display unit, a graphics controller, a touch panel controller, a CPU (Central Processing Unit), memory, a camera, a speaker, and the like. In the first embodiment, it is assumed that a user uses smartphone 1 to do internet shopping.

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

The content providing server 4 is a computer device for operating an e-commerce site (online shop) on the Internet. The content providing server 4 is, for example, a server device of an e-commerce platform provider. The content providing server 4 serves as a platform for purchasing products and services over a network in response to operations of a terminal device (smartphone 1, etc.) by a user (consumer). The content providing server 4 may also be a video platform that provides content such as videos. For example, the content providing server 4 sends product images to the smartphone 1 in response to operations on the smartphone 1. The content providing server 4 registers the redirect_uri in advance in the TV cloud 3.

The components of the information linkage system S will be described in detail below with reference to Figure 2 and subsequent figures. Figure 2 is a block diagram showing an example of the overall configuration of the television device 2 of the first embodiment. The television device 2 performs display control on the video display unit 233, which is larger than the display unit provided on the smartphone 1 (details will be described later).

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

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

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

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

Signal processing unit 207 demodulates the broadcast signals supplied from tuners 203a-203g into broadcast signals containing digital video and audio signals. Furthermore, signal processing unit 207 selectively performs predetermined digital signal processing on the video signals contained in the digital broadcast signals and outputs the result to graphics processing unit 208. Furthermore, signal processing unit 207 selectively performs desired digital signal processing on the audio signals contained in the digital broadcast signals and outputs the result to audio processing unit 209.

Signal processing unit 207 is connected to multiple external input terminals 214a-214d. These external input terminals 214a-214d can receive analog video and audio signals from external devices such as a DVD (Digital Versatile Disk) recorder. Signal processing unit 207 digitizes the analog video and audio signals received from external input terminals 214a-214d. Signal processing unit 207 then performs predetermined digital signal processing on the digitized video signals and outputs the resulting signal to graphics processing unit 208. Signal processing unit 207 also performs predetermined digital signal processing on the digitized audio signals and outputs the resulting signal to audio processing unit 209.

The graphics processing unit 208 superimposes an OSD signal generated by the OSD signal generation unit 210 onto the digital video signal supplied from the signal processing unit 207 and outputs the superimposed 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 it to the video display unit 233. The video display unit 233 is, for example, an LCD or organic EL display.

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

The television device 2 further includes a control unit 216, a card holder 217, various interfaces 218-221, and a brightness sensor 230. The control unit 216 includes a CPU 216a, a ROM 216b, a RAM 216c, and a non-volatile memory 216d.

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

The CPU 216a controls the overall operation of the television device 2 by executing programs stored in the ROM 216b. The ROM 216b mainly stores the programs executed by the CPU 216a. The RAM 216c provides a working area when the CPU 216a executes the programs. The non-volatile memory 216d stores various setting information, control information, etc. for the television device 2.

The control unit 216 is connected to a card holder 217, to which a memory card 234 can be attached and detached, via a card I/F 225. This allows the control unit 216 to send and receive various information to and from the memory card 234 attached to 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 send and receive various information via the communication I/F 218 to external devices such as the relay device 400 and LAN-compatible HDDs (Hard Disk Drives) connected to the LAN terminal 226. However, the communication I/F 218 may also be configured to be able to connect wirelessly to external devices such as the relay device 400.

The control unit 216 is connected to the HDMI (registered trademark) (High-Definition Multimedia Interface) terminal 227 via an HDMI I/F 221. This allows the control unit 216 to send and receive various information to and from external devices connected to the HDMI terminal 227 via the HDMI I/F 221.

The control unit 216 is connected to a USB terminal 228 via a USB (Universal Serial Bus) I/F 219. This allows the control unit 216 to send and receive various information via the USB I/F 219 to and from a storage device 237, such as a USB HDD, connected to the USB terminal 228.

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

Figure 3 is a block diagram showing an example of the partial configuration of a television device 2 according to the first embodiment. The television device 2 includes a storage unit 241 (ROM 216b, RAM 216c, non-volatile memory 216d, and storage device 237 in Figure 2), and functional modules generated as a result of the CPU 216a executing a program stored in the storage unit 241, including a transmission unit 242, an acquisition unit 243, and a display control unit 244.

The transmission unit 242 transmits various information to external devices. The acquisition unit 243 acquires various information from external devices and reads various information stored in the memory unit 241.

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

Figure 4 is a block diagram showing an example of the overall configuration of the TV cloud 3 of the first embodiment. As shown in Figure 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 used for communication with external devices. The operation unit 302 has input devices such as a keyboard and mouse, and a display device such as a display.

The storage device 305 includes, for example, an HDD or SSD, and stores various information. The CPU 303 controls each component of the TV cloud 3 by executing various programs. The memory 304 includes, for example, ROM and RAM, and stores various programs and data used for various arithmetic processing by the CPU 303.

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

The storage unit 311 stores programs executed by the CPU 303 and a DB (DataBase). An example of the data structure of the DB will now be described with reference to FIG. 6. As shown in FIG. 6, the DB stores information including a TV ID, an authentication code, an EC server ID, and a token. Note that the DB may also store attribute information (such as the TV model) of the television device 2 corresponding to the TV ID along with the TV ID.

The TVID is information that identifies the television device 2. The authentication code is a code required to acquire a token, which will be described later. The EC server ID is information that identifies the content providing server 4. In other words, it is the ID of the EC site server, etc. The token is information used for authentication. Returning to FIG. 5, the acquisition unit 312 acquires various information from an external device. The transmission unit 313 transmits various information to the external device. The generation unit 314 performs an information generation operation for the DB.

Next, the processing flow of each component in the information linkage system S will be described. Figure 7 is a flowchart showing the overall processing in the information linkage system S of the first embodiment. Here, the process starts when the user operates the remote control of the television device 2 or the like to specify the EC site with which the user wants to link the smartphone 1 on a so-called portal screen (a screen for linking with EC sites, etc.). Note that the processing of the smartphone 1 shown in Figure 7 may be executed by an application program installed on the smartphone 1.

When an EC site is specified by the user as described above, in step S1, the transmission unit 242 of the television device 2 transmits information about the EC site (e.g., the EC site ID, the EC site URL, etc.) and a TVID, which is an identifier for the television device 2, to the TV cloud 3. In this way, the transmission unit 242 transmits information about the content providing server 4, which is an image providing device that provides images on the EC site, to the TV cloud 3.

The acquisition unit 312 of the TV cloud 3 acquires EC site information and the TV ID from the television device 2. The generation unit 314 of the TV cloud 3 generates an authentication code and stores information including the TV ID, an EC server ID that identifies the content provider server 4 of the EC site, and the authentication code in the DB of the storage unit 311. The generation unit 314 also generates a QR code (registered trademark), which is a two-dimensional code based on the authentication code and the URL that is the access destination of the EC site. Note that the QR code is just one example, and other display information may be used. In other words, other forms of display information that can convey the authentication code and EC site access destination information may be used. The authentication code may include a portion for identifying the manufacturer and a portion for identifying the television device 2.

In step S2, the transmission unit 313 of the TV cloud 3 transmits the QR code to the television device 2 that made the request. In response to the request from the television device 2, the transmission unit 313 transmits a QR code including a URL to access the EC site and an authentication code.

The acquisition unit 243 of the television device 2 acquires a QR code from the TV cloud 3. In this way, the acquisition unit 243 of the television device 2 acquires a QR code that serves as access information based on the authentication code and the URL of the EC site to be accessed. 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 an imaging means or the like. As a result, the smartphone 1 obtains the URL and authentication code of the EC site. In step S4, after obtaining the URL and authentication code of the EC site, the smartphone 1 accesses the content providing server 4 based on the URL and transmits the authentication code.

When the content providing server 4 acquires the authentication code from the smartphone 1, in step S5 it sends the authentication code to the TV cloud 3 along with information identifying the content providing server 4, and makes an authentication request. The acquisition unit 312 of the TV cloud 3 also acquires the authentication code along with 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 performs authentication by referencing the DB in 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 references the DB in the storage unit 311, and if 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 publicly known technology. The generation unit 314 also associates the token with information in the DB that contains the information identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312. The information that further associates the token with the information identifying the content providing server 4 and the information containing the authentication code acquired by the acquisition unit 312 also includes the TVID of the television device 2 that made the request.

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

In step S6, the transmission unit 313 of the TV cloud 3 transmits the token generated by the generation unit 314 to the content providing server 4. In this way, the transmission unit 313 transmits a token based on the authentication code to the content providing server 4. The content providing server 4 stores information associating the token with the user ID of the smartphone 1 that transmitted the authentication code.

In step S7, the smartphone 1 logs in to the content providing server 4 and accesses the EC site. This causes the smartphone 1 to display the EC site screen. Here, the user of the smartphone 1 selects an instruction indicating a television display request for a specific link destination on the EC site screen. In step S8, in response to this selection, the smartphone 1 makes a television display request (TV display request) by sending the URL of the link destination to the content providing server 4. The content providing server 4 obtains the television display request from the smartphone 1, along with the URL of the image to be displayed.

In step S9, the content providing server 4 sends a token corresponding to the requesting smartphone 1 and the URL of the image to be displayed to the TV cloud 3, requesting display. 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 destination of the image to be displayed based on the request from the smartphone 1.

In step S10, the TV cloud 3 references the DB in the storage unit 311 and identifies the TV ID corresponding to the token acquired by the acquisition unit 312. The transmission unit 313 of the TV cloud 3 then transmits the URL of the access destination for the image to be displayed to the television device 2 corresponding to the TV ID.

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

The TV cloud 3 according to the first embodiment generates correspondence information that associates a television device 2 corresponding to an authentication code with a token based on the authentication code, and upon obtaining the token and the access destination of the image to be displayed based on a request from the smartphone 1 from the content providing server 4, notifies the television device 2 of the access destination of the image, thereby causing the television device 2 to display the image in response to the request from the smartphone 1. This allows the TV cloud 3 to display the image based on the request from the smartphone 1 on the television device 2, which can display an image on a screen larger than that of the smartphone 1.

The television device 2 also outputs access information including the access destination of the content providing server 4 and an authentication code, obtains the access destination of the image to be displayed based on the request from the smartphone 1 from the TV cloud 3, and displays the image on the video display unit 233. This allows the television device 2 to display the image based on the request from the smartphone 1 on the video display unit 233, which can display an image larger than the screen of the smartphone 1.

Second Embodiment
The information linkage system S according to the second embodiment differs from the first embodiment in that the TV cloud 3 differs for each manufacturer of the television device 2. That is, the information linkage system S according to the second embodiment has a plurality of TV clouds 3.

Here, an example of the overall configuration of the information linkage system S of the second embodiment will be described. Figure 8 is a diagram showing an overview of an example of the overall configuration of the information linkage system S of the second embodiment. Note that the same components as in the first embodiment are given the same reference numerals and their description will be omitted. As shown in Figure 8, the information linkage system S has multiple TV clouds 3 (TV cloud 3a, TV cloud 3b). TV cloud 3b can be connected to a television device 2, which is a television (not shown) made by a manufacturer related to that TV cloud 3b.

Number two is television.
A TV cloud 3 is a so-called push distribution server. The TV cloud 3 is a server of a television manufacturer that manufactures the television device 2 and provides various services to the television device 2 via a network based on viewing information collected from the television device 2, such as recommendations for programs to be viewed or reserved, and product recommendations based on the content of the programs viewed.

5 is a TV gateway, which is a common reception server. The TV gateway 5 is a server at the common manufacturer site of television device manufacturers that integrates the TV clouds 3 of multiple television manufacturers and connects to e-commerce (EC). The information linkage system S has a TV gateway 5 (server management device) that can send and receive information with the multiple TV clouds 3 via a network. The TV gateway 5 can also send and receive information via a network with a measurement server 6 that performs measurement processing to tally the results of advertisement display. This TV gateway 5 is a cloud server that integrates each manufacturer. In other words, the TV gateway 5 is a server that integrates the TV clouds 3 of multiple television manufacturers and connects them to the content providing server 4. The TV gateway 5 issues client credentials (client_id, client_secret) to the content providing server 4.

In addition, a random secret is set in the x-api-key between the TV cloud 3 and the TV gateway 5 in advance. The x-api-key exchanged between the TV gateway 5 and the content providing server 4 becomes a pass-key.

4 is a content providing server such as an EC site server. The content providing server 4 is a server of an EC platform provider. For users, i.e., consumers, the content providing server 4 is a server that serves as a platform for purchasing products and services. The content providing server 4 also pre-registers the redirect_uri in the TV gateway 5.

1050 is a user terminal. The user terminal 1050 is a terminal that has 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 a smartphone 1. In the first embodiment, the user terminal 1050 is described as being a smartphone 1, but is not limited to a smartphone. The user terminal 1050 may be a PC, tablet terminal, or the like that meets the conditions of the situation. Furthermore, these terminals can replace the smartphone shown in the first embodiment.

Figure 9 is a block diagram showing an example of the overall configuration of a television gateway 5 according to the second embodiment. As shown in Figure 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.

The communication I/F 501 is an interface used for communication with external devices. The operation unit 502 has input devices such as a keyboard and mouse, and a display device such as a display.

The storage device 505 includes, for example, an HDD or SSD, and stores various information. The CPU 503 controls each component of the TV gateway 5 by executing various programs. The memory 504 includes, for example, ROM and RAM, and stores various programs and data used for various arithmetic processing by the CPU 503.

Figure 10 is a block diagram showing an example of the partial configuration of the TV gateway 5 of the second embodiment. The TV gateway 5 includes a storage unit 511 (memory 504, storage device 505), and functional modules generated as a result of the CPU 503 executing a program stored in the storage unit 511: an acquisition unit 512, a transmission unit 513, and a generation unit 514.

The memory unit 511 stores programs executed by the CPU 503 and a database (DB).

The acquisition unit 512 acquires various information from external devices. The transmission unit 513 transmits various information to external devices. The generation unit 514 performs information generation operations for the DB.

Next, the processing flow of each component in the information linkage system S of the second embodiment will be described. Figure 11 is a flowchart showing the overall processing in the information linkage system S of the second embodiment. The flowchart shown in Figure 11 also starts when the user operates the remote control of the television device 2 or the like to specify, on a so-called portal screen, the EC site that the user wants to link with the smartphone 1. Note that the authentication code and token generated by the TV cloud 3 include information that identifies the manufacturer. In other words, the TV cloud 3 includes information that identifies its own device in the authentication code and token.

Furthermore, step S21 in FIG. 11 is similar to step S1 in FIG. 7, and therefore description thereof will be omitted. In step S22, a 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 identifying the content providing server 4 and an authentication code for performing authentication between the content providing server 4 and the TV cloud 3. The authentication code may include a portion for identifying the manufacturer of the television device 2 and a portion for identifying the television device 2. Furthermore, the portion of the authentication code for identifying the television device 2 is a random value. Furthermore, the TV cloud 3 may associate the time when this value is sent to the television device 2 as information in the DB of the memory unit 311.

An example of the information in the URL authentication code 2010 is as follows:
https://XXXXXXXX YYYYYYYYY
The X part contains the URL of the content providing server 4, and the Y part contains the OAuth2 authorization code. The authorization code part contains information that can identify the manufacturer and the television. Either one of the information that can identify the manufacturer or the television device 2 may be used. The URL authentication code 2010 may be sent in any format 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 contents of the URL authentication code 2010 as an image or video on the video display unit 233. The display format of the display control unit 244 may be a QR code, barcode, text, or the like, as long as it can optically display and output the information contained in the URL authentication code 2010 as an image or video. Also, although the first embodiment uses a QR code for explanation, it is not limited to a QR code, as in this embodiment.

7, in step S23, the user terminal 1050 uses its URL authentication code reading function to read the URL authentication code 2011 optically displayed on the video display unit 233 from image information optically captured by the imaging unit. This allows the user terminal 1050 to obtain the URL and authentication code of the EC site. The authentication code portion is a time-limited authentication code configured as follows:
“code”: <authorization code>,
"state": <string> // Random number

In step S24, after the user terminal 1050 acquires the URL and authentication code of the EC site, it accesses the content providing server 4 based on the URL and transmits the authentication code 2020.

The authentication code 2020 is the authentication code portion (<authorization code>) of the URL authentication code 2010 and the URL authentication code 2011. The authentication code 2021 is as follows.
“code”: <authorization code>,
"state": <string> // random number Note that the authentication code 2020 may also include URL information of the content providing server 4 in addition to the above.

In step S25, upon receiving the authentication code 2020, the content providing server 4 transmits an authentication code 2021 to the television gateway 5 and makes an authentication request. The content providing server 4 sends information of the authentication request to, for example, the OAuth2 Token Endpoint of the television gateway 5. The information of the authentication code 2021 has the following configuration.
Authorization: “Basic” + Base64 (<client_id> + “:” + <client_secret>)
Content-type: application/x-www-form-urlencoded
・grant_type: “authorization_code”
・code ：＜authorization code＞ (Authorization code)
redirect_uri: an entrance for returning to the EC site of the content providing server 4, which is pre-registered in the television gateway 5.
client_id: an identifier assigned to each EC site of the content providing server 4, which is pre-registered in the TV gateway 5.
The client_secret is assigned by the TV gateway 5 based on the client_id for each site of the content providing server 4. The site of the TV gateway 5 checks the manufacturer extension of the code and performs redirection.

In step S26, the transmission unit 313 of the TV gateway 5 references the acquired authentication code 2021 and the information identifying the manufacturer contained in the authentication code 2021 to identify the destination TV cloud 3. Specifically, the transmission unit 313 of the TV gateway 5 checks the authorization code, i.e., the authentication code, and determines which TV cloud 3 it is.

Then, in step S27, the transmission unit 313 of the television gateway 5 makes an authentication request by transmitting an authentication request 2022 to the TV cloud 3 as the transmission destination.
In this way, the transmission unit 513 of the TV gateway 5 transmits the authentication request 2022 to the destination TV cloud 3 identified based on the Authorization_code (authentication code) of the authentication code 2021. The information of the authentication request 2022 transmitted by the transmission unit 313 of the TV gateway 5 is the same as the information of the authentication code 2021 acquired from the content providing server 4. Other examples of the information of the authentication request 2022 include the following.
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 written in the URL authentication code 2010 together with the information for identifying the content providing server 4 .

The generation unit 314 of the TV cloud 3 performs authentication by referencing 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 references the DB of the storage unit 311, and if 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 2030. The generation unit 314 also associates the token 2030 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.

In step S28, the transmission unit 313 of the TV cloud 3 transmits the token 2030 generated by the generation unit 314 to the TV gateway 5.

Specifically, the transmission unit 313 of the TV cloud 3 sends the OAuth2 Token Response to the TV gateway 5 as the token 2030. This response, the OAuth2 Access Token Response, has the following configuration.
{“access_token”: <access token>,
“token_type”: “Bearer”,
“expires_in”: 3600,
“refresh_token”: <refresh token>}
When the TV cloud 3 accesses the TV gateway 5, it attaches an access_token. expires_in is the validity period (seconds) of the access_token, and is stored when the access_token is received along with the time at which it becomes invalid, and the access_token is used repeatedly until then. The refresh_token is stored secretly by the content providing server 4. For security reasons, it is not advisable to simply store it in local storage. When the access_token and refresh_token are issued by each manufacturer, the TV manufacturer can be identified by attaching an identifier that identifies the TV manufacturer to the beginning.

The acquisition unit 512 of the TV gateway 5 acquires the token 2030. Then, in step S29, the TV gateway 5 transmits the token 2030 to the content providing server 4 as token 2031, and the content providing server 4 acquires the token 2031. Note that the transmission unit 313 of the TV cloud 3 may transmit the token directly to the content providing server 4.

The content providing server 4 stores information associating 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 as a response, i.e., the token + user ID 2040, to the television gateway 5. This allows the content providing server 4 to send the user ID of the user of the user terminal 1050 to the television gateway 5.

The information structure of the token+user ID 2040 transmitted 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 site of the content providing server 4. Pre-registered on the manufacturer's common site.
user_id: user ID at the site of the content providing server 4,
Preference: <Current user attributes (current user attributes: user's date of birth, gender, postal code, purchase history, etc.)>}

The acquisition unit 512 of the TV 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 identifies the destination TV cloud 3 from the token+user ID 2040 and transmits a device ID request 2041 (TVID) to the destination TV cloud 3. Note that the transmission unit 513 of the TV gateway 5 may also transmit the token when transmitting the device ID request 2041.

The device ID request 2041 is a request for the TV gateway 5 to inquire about the device_id (TVID) of the TV from each manufacturer (TV cloud 3) using the access_token of OAuth2, and is, for example, as follows:
GET https://each-maker. example. com/common/devices/id
・Authorization: “Bearer” + <access_token>
・x-api-key: <Random secret determined by the manufacturer's common site and each manufacturer>
・Content-type: application/json
client_id: Identifier assigned to each manufacturer's common site

The TV cloud 3 refers to the DB of the storage unit 311 and acquires the TV ID corresponding to the acquired token. The TV cloud 3 may also acquire device information corresponding to the acquired TV ID (attribute information of the television device 2 of the TV ID). In step S32, the transmission unit 313 of the TV cloud 3 transmits information such as the TV ID as a device ID response 2050 to the television gateway 5. Examples of the device ID response 2050 include the following:
"device_id": <id> (TVID assigned to the television device 2 by the TV cloud 3)
"model":<model name> (model of the television device 2, i.e., display screen size, pixel count information such as 2K, 4K, 8K, etc.)

In step S33, the generation unit 514 of the television gateway 5 registers information binding information that associates the acquired TVID (device ID), user ID, and model information (model) of the television device 2 as DB information in the storage unit 511.

Furthermore, the generation unit 514 of the television gateway 5 generates a pass key 2051. Furthermore, in step S34, the transmission unit 513 transmits the pass key to the content providing server 4. The pass key includes the following information:
"pass_key": <pass_key> (this pass_key is used as an ID when the operation commands 2090 to 2093 are executed from step S44 onwards)
"expires_in": 86400 (expires_in is returned with a grace period of 10 days or so even if preference cannot be prepared at the first access.)
"model":<model name> (model information in the device ID response, such as the model of the television device 2, i.e., display screen size, pixel count information such as 2K, 4K, 8K, etc.)

Also, in step S35, the generation unit 514 of the TV gateway 5 stores the generated pass key in the storage unit 511.

When the content providing server 4 acquires the pass key from the television gateway 5, it stores the information included in the pass key. Specifically, the following information is stored for each user ID of the EC site:
・access_token
・refresh_token
・pass_key
・model // Linked TV model information

In step S36, the user terminal 1050 starts the application and logs in to the service provided by the content providing server 4. This causes the smartphone 1 to display an EC site screen. The EC site screen output by the application also displays a button for connecting to the television device 2. In step S37, the content providing server 4 transmits device information 2070 to the user terminal 1050 in response to the login in step S36. The device information 2070 here refers to a combination of one, two, or three of the device ID, user ID, and model name included in the pass key 2051.

The user of the smartphone 1 selects a button for connecting to the television device 2 from the link destination on the EC site screen. In step S38, the user terminal 1050, in response to the selection, sends a television display request (TV display request 2071) by sending the URL of the link destination to the content providing server 4.

Upon receiving the TV display request 2071 from the user terminal 1050, the content providing server 4 transmits, in step S39, a display request 2072 including the token, pass key, and URL of the link destination to the television gateway 5, thereby making a display request to the television device 2. The information configuration of the display request 2072 is 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 TV gateway 5 receives information about the display request 2072, including the token, pass key, and link destination URL, from the content providing server 4. The acquisition unit 512 then extracts the pass_key from the x-api-key header.

In step S40, the acquisition unit 512 uses the pass key (pass_key) and information stored in the memory unit 511 to determine the access destination and access source. In step S41, the transmission unit 513 transmits information including the token URL to the TV cloud 3 based on the determination result, and requests display. In this way, the transmission unit 513 transmits the token and the access destination of the image to be displayed to the destination TV cloud 3. The TV gateway 5 measures the number of accesses by access source and manufacturer.

The display request 2073 that the transmission unit 513 transmits to the TV cloud 3 includes a token, a client ID, a URL, and a message. Examples of this information are as follows:
POST https://each-maker. example. com/common/devices/control
Authorization: “Bearer” + <access_token>
x-api-key: <Random secret determined by the manufacturer's common site 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> (TV website URL),
“template”: “full”,
“client_id”:<client_id>,
“messageid”:<message ID>}

The acquisition unit 312 of the TV cloud 3 receives a 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 transmission unit 313 of the TV cloud 3 outputs a display request 2074 to the television device 2 based on the identification result. Note that this display request may be replaced with a manufacturer-specific display request command. Furthermore, if necessary, the TV cloud 3 may aggregate accesses for each client_id and send a request to the television.

In step S43, the television device 2 launches a browser in response to the display request, executes Javascript (registered trademark) using an onLoad or onClick event, etc., and displays and outputs the image at the URL destination of the display target. The television device 2 also sends a display operation result notification 2080 to the measurement server 6, which identifies the servicer, user, TV manufacturer, and displayed advertisement. The measurement server 6 tallys up the results of advertisements displayed by the TV cloud 3 on multiple television devices 2. Based on the tallying results, the manufacturer, television gateway 5, or the owner of the measurement server 6 requests advertising and promotional expenses from the e-commerce platform that owns the content providing server 4.

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

In step S45, the content providing server 4 transmits an operation command 2091 including a common key code to the television gateway 5 based on the operation command 2090 transmitted in step S44. The common key code is a command configured to correspond to the operation buttons on a television remote control. There are numbers, cross cursor, volume/channel/power, color keys, function keys, media control, and manufacturer-specific commands. These manufacturer-specific commands are commands for operating in a manner unique to each manufacturer. In other words, manufacturer-specific commands are manufacturer-specific operation commands set by each manufacturer. The common key code is a key code for performing operations common to all manufacturers, excluding manufacturer-specific commands.

The numeric commands are "11", "12", "0", "1", "2", "3", "4", "5", "6", "7", "8", "9", and ".".

The cross cursor commands are "up", "down", "left", "right", "page up", "page down", "page left", "page right", "enter", "exit", and "back".

Volume/channel/power commands are "power", "power off", "power on", "volume up", "volume down", "channel up", and "channel down".

The color key is "blue", "red", "green", and "yellow".

Function key commands are "electronic program guide", "initial configuration", "select broadcast type", "input select", "display information", "mute", "contents menu", and "closed caption".

Media control commands are "Play", "stop", "pause", "rewind", "forward", "backward", "skip forward", "skip backward", and "record".

Upon receiving the operation command 2091 in step S45, the television gateway 5 sends an operation command 2092 to the TV cloud 3 in step S46. The operation command 2092 is the same command as the operation command 2091.
In step S47, the television gateway 5 transmits a response message ID 2094 as a response message to the content providing server 4. The message ID has the following structure.
{messageid: <message ID>}

When the TV cloud 3 receives the operation command 2092 from the television gateway 5, in step S48 it sends the operation command 2093 to the television device 2. The operation command 2093 is the same or equivalent information as the operation command 2092 and is a manufacturer-specific command for operating the display screen of the television device 2. The TV cloud 3 replaces the operation command 2092 with the operation command 2093, which is each company's key code for operating the television device 2. When the standardization of the operation commands for the television device 2 progresses, the operation command 2092 can be used as the operation command 2093 without conversion.

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 an operation result notification 2081 that identifies the operation command.

The flowchart shown in Figure 11 explains the process of integrating multiple manufacturers to access the platform provider's content provider server 4, but as with the TV cloud 3 in the first embodiment, a manufacturer can also access the content provider server 4 on its own. In this case, the TV cloud 3 incorporates the operations of the TV gateway 5. In this case, the exchange of information between the TV cloud 3 and the TV gateway 5 is omitted.

The television gateway 5 acquires an authentication code from the content providing server 4, transmits the authentication code to the destination TV cloud 3 identified based on the authentication code, acquires a token and the access destination of the image to be displayed from the content providing server 4, and transmits the token and the access destination of the image to be displayed to the destination TV cloud 3. This allows processing to be performed from the content providing server 4 side without having to determine which of multiple TV clouds 3 to send to.

The programs executed by each device in this embodiment (user terminal 1050, television device 2, TV cloud 3, content providing server 4, television gateway 5, measurement server 6) can be provided as installable or executable files recorded on a recording medium readable by a computer device, such as a CD (Compact Disc)-ROM (Read Only Memory), a flexible disk (FD), a CD-R (Recordable), or a DVD (Digital Versatile Disk). The programs may also be provided or distributed via a network such as the Internet.

(Third embodiment)
The information linkage system S according to the third embodiment has the same overall configuration as the information linkage system S according to the second embodiment. In the information linkage system S according to 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 links the ID of the television device 2 and the user ID of the user terminal 1050 using these tokens.

Note that the data structure stored in the TV cloud 3 shown in Figure 6 is different. Specifically, the TV cloud 3 stores an HA-ID instead of the TVID shown in Figure 6. Also, it stores a PF-ID instead of the EC site server ID shown in Figure 6. The HA-ID is identification information that includes a TC-ID, which is the company ID of the television manufacturer, and a TV-ID, which is the device ID of the television device 2. The PF-ID is the company ID of the video platform. The TC-ID is an identifier that identifies the TV cloud 3. Also, the PF-ID is an identifier that identifies the content providing server 4.

Next, the processing flow of each component in the information linkage system S of the third embodiment will be described. Figure 12 is a flowchart showing the overall processing in the information linkage system S of the third embodiment. The flowchart shown in Figure 12 also starts when the user operates the remote control of the television device 2 or the like to specify, on a so-called portal screen, an EC site (e.g., a server that receives content) that the user wants to link with the smartphone 1. Note that the authentication code and token generated by the TV cloud 3 include information that identifies the manufacturer. In other words, the TV cloud 3 includes information that identifies its own device in the authentication code and token.

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

In step S62, the TV cloud 3 sends a QR code including the URL of the TV gateway 5 and a URL authentication code to the television device 2 as a response. The QR code includes the URL of the TV gateway 5 and the following time-limited authentication code:

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

The URL authentication code is information that includes URL information that identifies the television gateway 5, an authentication code for performing authentication between the content providing server 4 and the TV cloud 3, and state information. The authentication code may include a portion for identifying the manufacturer of the television device 2 and a portion for identifying the television device 2. The portion of the authentication code for identifying the television device 2 is a random value. The TV cloud 3 may also associate the time at which this value is sent to the television device 2 as information in the DB of the memory unit 311. The state information may include information in which the manufacturer's TC-ID and the video platform's PF-ID are encoded.

An example of the URL authentication code information is as follows:
https://XXXXXXXX YYYYYYYYY
The X part contains the URL of the television gateway 5, and the Y part contains the OAuth2 authorization code. The authorization code part contains information that can identify the manufacturer and the television. Either one of the information that can identify the manufacturer and the television device 2 may be used. The URL authentication code may be sent in any format as long as it contains the above information. Note that the Y part may contain state information.

When the acquisition unit 243 of the television device 2 acquires a URL authentication code from the TV cloud 3, the display control unit 244 optically displays and outputs the contents of the URL authentication code as an image or video on the video display unit 233. The display format of the display control unit 244 may be a QR code, barcode, text, or the like, as long as it can optically display and output the information contained in the URL authentication code as an image or video. Furthermore, although the first and second embodiments are described using a QR code, it is not limited to a QR code, as in this embodiment.

7 and step S23 in Fig. 11, in step S63, the user terminal 1050 uses its URL authentication code reading function to read the URL authentication code information optically displayed on the video display unit 233 from the image information optically captured by the imaging means. As a result, the user terminal 1050 acquires the URL and authentication code of the TV gateway 5. The authentication code portion is a time-limited authentication code configured as follows:
“code”: <authorization code>,
"state": <string> // Random number

In step S64, after the user terminal 1050 acquires the URL, authentication code, and state information of the TV gateway 5, it accesses the TV gateway 5 based on the URL and transmits the authentication code and state information to request authentication. Note that the state information includes the TC-ID and PF-ID, as described above.

The information to be sent at the time of authentication request is as follows.
“code”: <authorization code>,
"state": <string> // Random number

In step S65, when the acquisition unit 512 of the TV gateway 5 receives the authentication code and state information, the transmission unit 513 of the TV gateway 5 transmits an HTML screen including a link button indicating a link instruction to the user terminal 1050. The HTML may include a URL and parameters for accessing the OAuth2 Authorization Endpoint of the PF-ID.

The user terminal 1050 acquires the above HTML format screen. Then, when the user presses the link button on the user terminal 1050 (step S66), an authorization request is made to the content providing server 4, which is the video platform. The content providing server 4 receives the authorization request and sends information to the user terminal 1050 in response to it (step S67).

The information sent when making the authorization request has the following configuration, for example:
Authorization: “Basic” + Base64 (<client_id> + “:” + <client_secret>) Request
{
“response_type”: “code”
"code": <authorization code> (authorization code)
“redirect_uri”:<TGW Endpoint> (endpoint of the TV gateway 5)
“client_id”:<TG-ID> (ID of the TV gateway 5)
"scope": <Provided by VPF> (token authentication scope)
“state”: HEX (JSON. stringify ({“tcid”; <TC-ID>, “pfid”; <PF-ID>, “salt”; <random string>}) + hash) (state information)
}

If user information is not registered on 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 processing involves registering a user ID and password, which are information for logging in to the content providing server 4, and registering user attribute information.

Next, the user terminal 1050 makes a login request to the content providing server 4, and the content providing server 4 makes a response in response to the login request (step S69). As an example of the response, the following information (authorization code) is output.
Response
{“code”: <authorization code>,
“state”: <state>}

When the user terminal 1050 receives the response, it redirects the request to the TV gateway 5 to issue a link command (step S70). The user terminal 1050 may also transmit the authorization code to the TV gateway 5.

When the acquisition unit 512 of the TV gateway 5 receives a redirect indicating a link instruction, the TV gateway 5 identifies the manufacturer based on the TC-ID included in the state information acquired from the user terminal 1050. In other words, the TV gateway 5 assigns a manufacturer (step S71).

Then, in step S72, the transmission unit 513 of the TV gateway 5 requests a token by sending an authentication code to the destination TV cloud 3 (step S72).

The information transmitted when requesting a token has the following configuration, for example:
Authorization: “Basic” + Base64 (TG-ID + “:” + <client_secret>)
Request Parameters
{
grant_type: “authorization_code”,
code: <authorization code> (authorization code),
state: <string> (state information),
redirect_uri:<redirect_uri>,
client_id:<TG-ID>
}

The generation unit 314 of the TV cloud 3 performs authentication by referencing the DB of the storage unit 311 and determining whether there is information corresponding to the information identifying the content providing server 4 (e.g., information included in the state information) and authentication code acquired by the acquisition unit 312. The generation unit 314 references the DB of the storage unit 311, and if there is information corresponding to the information identifying the content providing server 4 and authentication code acquired by the acquisition unit 312, generates a token (first token). The generation unit 314 also associates the first token with information in the DB that includes the information identifying the content providing server 4 and authentication code acquired by the acquisition unit 312.

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

Specifically, the transmission unit 313 of the TV cloud 3 sends the OAuth2 Token Response as a token to the TV gateway 5. This response, the OAuth2 Access Token Response, has the following configuration.
Response
{“access_token”: <access token>,
“token_type”: “Bearer”,
“expires_in”: 3600,
“refresh_token”: <refresh token>}

When the TV cloud 3 accesses the TV gateway 5, it attaches an access_token. expires_in is the validity period (seconds) of the access_token, and is stored when the access_token is received along with the time it becomes invalid; until then, the access_token is used repeatedly. The refresh_token is stored secretly by the content providing server 4. For security reasons, it is not advisable to simply store it in local storage. When the access_token and refresh_token are issued by each manufacturer, the TV manufacturer can be identified by adding an identifier that identifies the TV manufacturer to the beginning.

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

The information transmitted when requesting a token has the following configuration, for example:
Authorization: “Basic” + Base64 (TG-ID + “:” + <client_secret>)
Request
{
grant_type: “authorization_code”,
code: <code> (authorization code),
state: <string> (state information),
redirect_uri:<TGW Endpoint>,
client_id:<TG-ID>
}

The content providing server 4 identifies the user ID corresponding to the authorization code obtained from the television gateway 5. The content providing server 4 then generates a second token based on the user ID.

In step S75, the content providing server 4 transmits the generated second token to the television gateway 5. Note that the content providing server 4 may store the second token in association with the user ID and user attribute information.

Specifically, the content providing server 4 sends an OAuth2 Token Response as a token to the television gateway 5. This response, OAuth2 Access Token Response, has the following structure:
{“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 transmission unit 513 of the television gateway 5 transmits the second token to the content providing server 4 and requests user information from the content providing server 4 (step S76).

The information transmitted when the user information is requested has, for example, the following configuration.
Authorization: “Bearer” + <access token>)

The content providing server 4 searches for the user ID and user attribute information corresponding to the second token acquired from the television gateway 5, and transmits this information as a response to the television gateway 5 (step S77). As a result, the acquisition unit 512 of the television gateway 5 acquires the user ID and user attribute information. The response information has the following configuration:
Response
{"user_id": <UR-ID> (user ID at the site of the 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 transmits the PF-ID and requests device information. The information transmitted when requesting device information has the following structure, for example.
Authorization: “Basic” + Base64 (PF-ID + “:” + <client_secret>)

When the acquisition unit 512 of the television gateway 5 receives the device information request from the content providing server 4, the transmission unit 513 of the television gateway 5 transmits the first token corresponding to the second token transmitted in step S74 to the TV cloud 3, and also requests device information (step S79). The information transmitted when requesting device information has, for example, the following configuration:
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 information about the device corresponding to the HA-ID (attribute information about the television device 2 corresponding to the HA-ID).

In step S80, the transmission unit 313 of the TV cloud 3 transmits information such as the HA-ID as a response to the TV gateway 5. The acquisition unit 512 of the TV gateway 5 acquires the HA-ID and information on the device corresponding to the HA-ID. Examples of the response include the following:
Response
{
・“device_id”: <HA-ID> (HA-ID)
"model":<model name> (model of the television device 2, i.e., display screen size, pixel count information such as 2K, 4K, 8K, etc.)
}

In step S81, the generation unit 514 of the television gateway 5 registers binding information that associates the acquired HA-ID, user ID, model information (model) which is attribute information of the television device 2, and PF-ID as DB information in the storage unit 511. Note that the generation unit 514 of the television gateway 5 may also include user attribute information as binding information.

The generating unit 514 of the television gateway 5 generates a pass key. In step S82, the transmitting unit 513 transmits the pass key to the content providing server 4. The pass key includes the following information:
"pass_key": <pass_key> (This pass_key is used as an ID when an operation command is executed)
"expires_in": 86400 (expires_in is returned with a grace period of 10 days or so even if preference cannot be prepared at the first access.)
"model":<model name> (model information in the device ID response, such as the model of the television device 2, i.e., display screen size, pixel count information such as 2K, 4K, 8K, etc.)

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

Upon receiving the pass key from the television gateway 5, the content providing server 4 stores the information included in the pass key. Specifically, the content providing server 4 stores the following information for each user ID of the EC site:
・access_token
・refresh_token
・pass_key
・model // Linked TV model information

The television gateway 5 acquires an authentication code from the user terminal 1050, transmits the authentication code to the destination TV cloud 3 identified based on the authentication code, acquires a first token from the TV cloud 3, and acquires a second token from the content providing server 4. The television gateway 5 then acquires the user ID by transmitting the second token to the content providing server 4, and acquires the ID (e.g., HA-ID) of the television device 2 by transmitting the first token to the TV cloud 3. In this way, the television gateway 5 can associate the user ID with the ID of the television device 2 by acquiring the user ID from the content providing server 4 and the ID of the television device 2 from the TV cloud 3.

In this case, the television gateway 5 stores the user ID in association with the ID of the television device 2, so the TV cloud 3 does not need to manage user IDs, reducing the information management burden on the TV cloud 3. Furthermore, because the television gateway 5 obtains the authentication code from the user terminal 1050, the content providing server 4 does not need to send the authentication code to the television gateway 5, reducing the processing burden on the content providing server 4. In other words, the television gateway 5 can appropriately perform processing to link the receiver identifier (the ID of the television device 2) and the terminal identifier (the user ID of the user terminal 1050).

(Fourth embodiment)
The information linkage system S according to the fourth embodiment has the same overall configuration as the information linkage system S according to the second embodiment. In the second embodiment, the case where the authentication code is also included in the QR code has been described, but in the information linkage system S according to the fourth embodiment, the authentication code is displayed as a separate PIN code.

Next, we will explain the processing flow of each component in the information linkage system S of the fourth embodiment. Step S21 in Figure 13 is similar to step S21 in Figure 11 and step S1 in Figure 7, so its explanation will be omitted.

In step S91, the TV cloud 3 transmits a QR code including a URL to the television device 2. The TV cloud 3 also transmits a PIN code corresponding to the authentication code to the television device 2.

An example of URL information included in the QR code is as follows:
https://XXXXXXXX
The part X contains the URL of the content providing server 4. The sending format of the QR code URL may be any format as long as it contains the above information.

When the acquisition unit 243 of the television device 2 acquires the QR code and PIN 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. The display control unit 244 also displays and outputs the PIN code.

In step S92, the user terminal 1050 uses its reading function to read the URL information optically displayed on the video display unit 233 from the image information optically captured by the imaging means.

In step S93, the user terminal 1050 launches an application (app) and enters a state in which it can accept input of a pin code.

In step S94, when a PIN code is entered by user operation, the user terminal 1050 acquires the PIN code as an authentication code. Steps S24 to S35 are the same as steps S24 to S35 in Figure 11, respectively.

In the fourth embodiment, the TV cloud 3 transmits a pin code corresponding to the authentication code to the television device 2, and the television device 2 displays the pin code. The user of the user terminal 1050 then performs an input operation based on the pin code, and the user terminal 1050 transmits the pin code to the content providing server 4 as an authentication code.

In this case, even if the authentication code cannot be included in the two-dimensional code along with the URL, the authentication code can be sent from the user terminal 1050 to the content providing server 4.

Fifth Embodiment
The information linkage system S according to the fifth embodiment has the same overall configuration as the information linkage system S according to the third embodiment. In the information linkage system S according to the fifth embodiment, the television gateway 5 transmits campaign information to the television device 2 as promotion information for prompting processing to link the ID of the television device 2 with the user ID of the user terminal 1050 in the information linkage system S according to the third embodiment. In the information linkage system S, when the television device 2 instructs processing to link the ID of the television device 2 with the user ID of the user terminal 1050 based on the promotion information, the information linkage system S executes processing to link the ID of the television device 2 with the user ID of the user terminal 1050.

In the information linkage system S, when the television device 2 requests to acquire program guide information, the television gateway 5 accepts the request to acquire program guide information via the TV cloud 3. The television gateway 5 acquires program guide configuration information from the content providing server 4 and transmits the program guide configuration information to the TV cloud 3. The TV cloud 3 acquires the program guide configuration information and transmits the acquired program guide configuration information to the television device 2. The program guide configuration information includes operator information, channel information, program information, commercial information, and VOD information.

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

Here, the contents of the campaign information will be explained using Figure 14. Figure 14 is a diagram showing an example of promotion information. The campaign information has a normal linked data portion 330 and a campaign linked data portion 340.

The normal linking data portion 330 includes information (idbind) indicating the object of the ID linking data, information (img_base_url) indicating the base URL of the URL where the image file is stored, information (explanation_img) indicating an image explaining the linking method, and information (explanation_img) indicating an image explaining how to cancel the linking.

The campaign linkage data portion 340 includes information indicating an array of campaign information objects (idbind_campaign), information indicating the TV manufacturer targeted by the campaign (tv), information indicating the base URL of the URL where the image file is stored (img_base_url), information indicating an image explaining the campaign content (campaign_img), information indicating an image to display if linkage has already been established (hasbound_img), information indicating an image explaining the linkage method (explanation_img), information indicating an image recommending allowing tracking by IFA-ID (recommend_tracking_img), information indicating the campaign start date and time (start), and information indicating the campaign end date and time (end).

The information indicating the image in the campaign linkage data portion 340 may be set differently for each TV manufacturer using a macro, etc. This allows different campaign images to be assigned to each of multiple TV manufacturers with a simple configuration.

Next, the procedure for linking based on campaign information will be explained using Figure 15. Figure 15 is a flowchart showing the campaign information display process.

In response to a user operation, the television device 2 requests the TV cloud 3 to acquire program guide configuration information (program guide) for the e-commerce site specified by the user. When the television device 2 requests to acquire program guide information, the television gateway 5 accepts the request to acquire program guide information via the TV cloud 3. The television gateway 5 acquires the program guide configuration information from the content providing server 4 and transmits the program guide configuration information to the TV cloud 3. The TV cloud 3 acquires the program guide configuration information and transmits the acquired program guide configuration information to the television device 2. The television device 2 displays the program guide configuration information (step S101). The program guide configuration information includes operator information, channel information, program information, commercial information, and VOD information.

The television device 2 requests the television gateway 5 to acquire campaign information. If the television device 2 does not acquire campaign information from the television gateway 5 via the TV cloud 3 (Step S102: No), it terminates processing.

The television device 2 requests the television gateway 5 to acquire campaign information. When the television device 2 acquires the campaign information from the television gateway 5 via the TV cloud 3 (step S102: Yes), if the television device 2 is not already linked to the content providing server 4 (step S103: Yes), the television device 2 displays the campaign information along with the program guide configuration information (step S104). One method for determining whether or not the television device 2 is already linked to the content providing server 4 is for the television device 2 to keep a log of past link processing requests and make a determination based on that log.

If a selection is made in the campaign information to apply for the campaign, the television device 2 displays survey information (step S105). This survey accepts input of the user's attributes (gender, address, etc.). This survey information may also be displayed at other times.

After the questionnaire has been entered, the television device 2 requests a linkage instruction (step S106).

Next, the linking process procedure will be explained using Figure 16. Figure 16 is a flowchart showing the linking process procedure. The authentication code and token generated by TV cloud 3 include information that identifies the manufacturer. In other words, TV cloud 3 includes information that identifies its own device in the authentication code and token.

Before executing the processing of the flowchart shown in FIG. 15, the television device 2 generates an IFA-ID using random numbers and notifies the TV cloud 3 (step S111). This IFA-ID is a number with enough digits to ensure its uniqueness. The television device 2 may also transmit the TV model name of the television device 2. Bearer authentication may also be performed in steps S111 and S112.

The TV cloud 3 transmits the IFA-ID to the television gateway 5 (step S112). Then, in step S113, the process of the flowchart shown in FIG. 14 is executed. When a link instruction is issued in step S113, the television device 2 makes a QR code request (step S114).

Furthermore, step S114 in FIG. 16 is similar to step S1 in FIG. 7, step S12 in FIG. 11, and step S61 in FIG. 12. Note that in step S114, the television device 2 transmits the PF-ID corresponding to the EC site (video platform) specified by the user to the TV cloud 3.

In step S115, the TV cloud 3 sends a QR code including the URL of the TV gateway 5 and a URL authentication code to the television device 2 as a response. The QR code includes the URL of the TV gateway 5 and the following time-limited authentication code:

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

The URL authentication code is information that includes URL information that identifies the television gateway 5, an authentication code for performing authentication between the content providing server 4 and the TV cloud 3, and state information. The authentication code may include a portion for identifying the manufacturer of the television device 2 and a portion for identifying the television device 2. The portion of the authentication code for identifying the television device 2 is a random value. The TV cloud 3 may also associate the time at which this value is sent to the television device 2 as information in the DB of the memory unit 311. The state information may include information in which the manufacturer's TC-ID and the video platform's PF-ID are encoded.

An example of the URL authentication code information is as follows:
https://XXXXXXXX YYYYYYYYY
The X part contains the URL of the television gateway 5, and the Y part contains the OAuth2 authorization code. The authorization code part contains information that can identify the manufacturer and the television. Either one of the information that can identify the manufacturer and the television device 2 may be used. The URL authentication code may be sent in any format as long as it contains the above information. Note that the Y part may contain state information.

When the acquisition unit 243 of the television device 2 acquires a URL authentication code from the TV cloud 3, the display control unit 244 optically displays and outputs the contents of the URL authentication code as an image or video on the video display unit 233. The display format of the display control unit 244 may be a QR code, barcode, text, or the like, as long as it can optically display and output the information contained in the URL authentication code as an image or video. Furthermore, although the first and second embodiments are described using a QR code, it is not limited to a QR code, as in this embodiment.

7, step S23 in Fig. 11, and step S63 in Fig. 12, in step S116, the user terminal 1050 uses its URL authentication code reading function to read the URL authentication code information optically displayed on the video display unit 233 from the image information optically captured by the imaging means. As a result, the user terminal 1050 acquires the URL and authentication code of the TV gateway 5. The authentication code portion is a time-limited authentication code configured as follows:
“code”: <authorization code>,
"state": <string> // Random number

In step S117, after the user terminal 1050 acquires the URL, authentication code, and state information of the TV gateway 5, it accesses the TV gateway 5 based on the URL and transmits the authentication code and state information to request authentication. Note that the state information includes the TC-ID and PF-ID, as described above.

The information to be sent at the time of authentication request is as follows.
“code”: <authorization code>,
"state": <string> // Random number

In step S118, when the acquisition unit 512 of the TV gateway 5 receives the authentication code and state information, the transmission unit 513 of the TV gateway 5 transmits an HTML screen including a link button indicating a link instruction to the user terminal 1050. This HTML may include a URL and parameters for accessing the OAuth2 Authorization Endpoint of the PF-ID.

The user terminal 1050 acquires the above HTML format screen. Then, when the user presses the link button on the user terminal 1050 (step S119), an authorization request is made to the content providing server 4, which is the video platform. The content providing server 4 receives the authorization request and sends information to the user terminal 1050 indicating its response (step S120).

The information sent when making the authorization request has the following configuration, for example:
Authorization: “Basic” + Base64 (<client_id> + “:” + <client_secret>) Request
{
“response_type”: “code”
"code": <authorization code> (authorization code)
“redirect_uri”:<TGW Endpoint> (endpoint of the TV gateway 5)
“client_id”:<TG-ID> (ID of the TV gateway 5)
"scope": <Provided by VPF> (token authentication scope)
“state”: HEX (JSON. stringify ({“tcid”; <TC-ID>, “pfid”; <PF-ID>, “salt”; <random string>}) + hash) (state information)
}

Note that if the television device 2 requests confirmation of the linkage status from the television gateway 5 via the TV cloud 3 at step S119 (steps S151 and S152), the television gateway 5 sends information to the television device 2 indicating that linkage has not been completed (steps S153 and S154).

If user information is not registered on the content providing server 4, a user registration process is performed between the user terminal 1050 and the content providing server 4 (step S121). Here, the user registration process involves registering a user ID and password, which are information for logging in to the content providing server 4, and registering user attribute information.

Next, the user terminal 1050 makes a login request to the content providing server 4, and the content providing server 4 makes a response in response to the login request (step S122). As an example of the response, the following information (authorization code) is output.
Response
{“code”: <authorization code>,
“state”: <state>}

When the user terminal 1050 receives the response, it redirects the request to the TV gateway 5 to indicate a linking instruction (step S123). Note that the user terminal 1050 may also send the authorization code to the TV gateway 5.

When the acquisition unit 512 of the TV gateway 5 receives a redirect indicating a link instruction, the TV gateway 5 identifies the manufacturer based on the TC-ID included in the state information acquired from the user terminal 1050. In other words, the TV gateway 5 assigns a manufacturer (step S124).

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

The information transmitted when requesting a token has the following configuration, for example:
Authorization: “Basic” + Base64 (TG-ID + “:” + <client_secret>)
Request Parameters
{
grant_type: “authorization_code”,
code: <authorization code> (authorization code),
state: <string> (state information),
redirect_uri:<redirect_uri>,
client_id:<TG-ID>
}

The generation unit 314 of the TV cloud 3 performs authentication by referencing the DB of the storage unit 311 and determining whether there is information corresponding to the information identifying the content providing server 4 (e.g., information included in the state information) and authentication code acquired by the acquisition unit 312. The generation unit 314 references the DB of the storage unit 311, and if there is information corresponding to the information identifying the content providing server 4 and authentication code acquired by the acquisition unit 312, generates a token (first token). The generation unit 314 also associates the first token with information in the DB that includes the information identifying the content providing server 4 and authentication code acquired by the acquisition unit 312.

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

Specifically, the transmission unit 313 of the TV cloud 3 sends the OAuth2 Token Response as a token to the TV gateway 5. This response, the OAuth2 Access Token Response, has the following configuration.
Response
{“access_token”: <access token>,
“token_type”: “Bearer”,
“expires_in”: 3600,
“refresh_token”: <refresh token>}

When the TV cloud 3 accesses the TV gateway 5, it attaches an access_token. expires_in is the validity period (seconds) of the access_token, and is stored when the access_token is received along with the time it becomes invalid; until then, the access_token is used repeatedly. The refresh_token is stored secretly by the content providing server 4. For security reasons, it is not advisable to simply store it in local storage. When the access_token and refresh_token are issued by each manufacturer, the TV manufacturer can be identified by adding an identifier that identifies the TV manufacturer to the beginning.

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

The information transmitted when requesting a token has the following configuration, for example:
Authorization: “Basic” + Base64 (TG-ID + “:” + <client_secret>)
Request
{
grant_type: “authorization_code”,
code: <code> (authorization code),
state: <string> (state information),
redirect_uri:<TGW Endpoint>,
client_id:<TG-ID>
}

The content providing server 4 identifies the user ID corresponding to the authorization code obtained from the television gateway 5. The content providing server 4 then generates a second token based on the user ID.

In step S128, the content providing server 4 transmits the generated second token to the television gateway 5. Note that the content providing server 4 may store the second token in association with the user ID and user attribute information.

Specifically, the content providing server 4 sends an OAuth2 Token Response as a token to the television gateway 5. This response, OAuth2 Access Token Response, has the following structure:
{“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 transmission unit 513 of the television gateway 5 transmits the second token to the content providing server 4 and requests user information from the content providing server 4 (step S129).

The information transmitted when the user information is requested has, for example, the following configuration.
Authorization: “Bearer” + <access token>)

The content providing server 4 searches for the user ID and user attribute information corresponding to the second token acquired from the television gateway 5, and transmits this information as a response to the television gateway 5 (step S130). As a result, the acquisition unit 512 of the television gateway 5 acquires the user ID and user attribute information. The response information has the following configuration:
Response
{"user_id": <UR-ID> (user ID at the site of the 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 transmits the PF-ID and requests device information. The information transmitted when requesting device information has the following structure, for example.
Authorization: “Basic” + Base64 (PF-ID + “:” + <client_secret>)

When the acquisition unit 512 of the television gateway 5 receives the device information request from the content providing server 4, the transmission unit 513 of the television gateway 5 transmits the first token corresponding to the second token transmitted in step S127 to the TV cloud 3, and also requests device information (step S132). The information transmitted when requesting device information has, for example, the following configuration:
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 information about the device corresponding to the HA-ID (attribute information about the television device 2 corresponding to the HA-ID).

In step S133, the transmission unit 313 of the TV cloud 3 transmits information such as the HA-ID as a response to the TV gateway 5. The acquisition unit 512 of the TV gateway 5 acquires the HA-ID and information on the device corresponding to the HA-ID. Examples of the response include the following:
Response
{
・“device_id”: <HA-ID> (HA-ID)
"model":<model name> (model of the television device 2, i.e., display screen size, pixel count information such as 2K, 4K, 8K, etc.)
}

In step S134, the generation unit 514 of the television gateway 5 registers binding information that associates the acquired HA-ID, user ID, model information (model) which is attribute information of the television device 2, and PF-ID as DB information in the storage unit 511. Note that the generation unit 514 of the television gateway 5 may also include user attribute information as binding information.

In step S135, the TV gateway 5 responds to the user terminal 1050 with the authorization code (step S135).

After step S134, if the television device 2 requests confirmation of the linkage status from the television gateway 5 via the TV cloud 3 (steps S136 and S137), the television gateway 5 transmits information indicating that linkage has been completed (such as information identifying the linked content provider server 4) to the television device 2 (steps S138 and S139). The television gateway 5 also notifies the content provider server 4 of the IFA-ID (step S140).

Furthermore, if the IFA-ID is updated on the television device 2, the updated IFA-ID is notified to the TV cloud 3 (step S141). The TV cloud 3 transmits the updated IFA-ID to the television gateway 5. The television gateway 5 transmits the updated IFA-ID to the content providing server 4 (step S143).

Next, the link cancellation process will be described using the flowchart shown in Figure 17. Figure 17 is a flowchart showing the link cancellation process. In response to a user operation, the television device 2 requests the TV cloud 3 to cancel the link (step S161). In response to the cancellation request from the television device 2, the TV cloud 3 requests the television gateway 5 to cancel the link (step S162). Note that in steps S161 and S162, the television device 2 or the TV cloud 3 may also send an IFA-ID along with the link cancellation request.

The TV gateway 5 notifies the content providing server 4 of a request to cancel the link (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). The TV cloud 3 may also delete the first token. The content providing server 4 notifies the TV gateway 5 of the cancellation of the link (step S166), and the TV gateway 5 notifies the TV cloud 3 of the cancellation of the link (step S167).

Next, the processing procedure for canceling collaboration via operation of the user terminal 1050 will be explained using Figure 18. Figure 18 is a flowchart showing the processing procedure for canceling collaboration via operation of the user terminal 1050.

The process starts when the user operates the remote control of the television device 2 and, on a so-called portal screen, specifies the content providing server 4 from which the user wants to cancel the link with the smartphone 1.

Step S180 in Figure 18 is similar to step S1 in Figure 7 and step S12 in Figure 11. 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 sends a QR code including the URL of the TV gateway 5 and a URL authentication code to the television device 2 as a response. The QR code includes the URL of the TV gateway 5 and the following time-limited authentication code:

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

The URL authentication code is information that includes URL information that identifies the television gateway 5, an authentication code for performing authentication between the content providing server 4 and the TV cloud 3, and state information. The authentication code may include a portion for identifying the manufacturer of the television device 2 and a portion for identifying the television device 2. The portion of the authentication code for identifying the television device 2 is a random value. The TV cloud 3 may also associate the time at which this value is sent to the television device 2 as information in the DB of the memory unit 311. The state information may include information in which the manufacturer's TC-ID and the video platform's PF-ID are encoded.

An example of the URL authentication code information is as follows:
https://XXXXXXXX YYYYYYYYY
The X part contains the URL of the television gateway 5, and the Y part contains the OAuth2 authorization code. The authorization code part contains information that can identify the manufacturer and the television. Either one of the information that can identify the manufacturer and the television device 2 may be used. The URL authentication code may be sent in any format as long as it contains the above information. Note that the Y part may contain state information.

When the acquisition unit 243 of the television device 2 acquires a URL authentication code from the TV cloud 3, the display control unit 244 optically displays and outputs the contents of the URL authentication code as an image or video on the video display unit 233. The display format of the display control unit 244 may be a QR code, barcode, text, or the like, as long as it can optically display and output the information contained in the URL authentication code as an image or video. Furthermore, although the first and second embodiments are described using a QR code, it is not limited to a QR code, as in this embodiment.

7 and step S23 in Fig. 11, in step S182, the user terminal 1050 uses its URL authentication code reading function to read the URL authentication code information optically displayed on the video display unit 233 from the image information optically captured by the imaging means. As a result, the user terminal 1050 acquires the URL and authentication code of the TV gateway 5. The authentication code portion is a time-limited authentication code configured as follows:
“code”: <authorization code>,
"state": <string> // Random number

In step S183, after the user terminal 1050 acquires the URL, authentication code, and state information of the TV gateway 5, it accesses the TV gateway 5 based on the URL and transmits the authentication code and state information to request authentication. Note that the state information includes the TC-ID and PF-ID, as described above.

The information to be sent at the time of authentication request is as follows.
“code”: <authorization code>,
"state": <string> // Random number

In step S184, when the acquisition unit 512 of the TV gateway 5 receives the authentication code and state information, the transmission unit 513 of the TV gateway 5 transmits an HTML screen including a link cancellation button indicating a link cancellation instruction to the user terminal 1050. This HTML may include a URL and parameters for accessing the OAuth2 Authorization Endpoint of the PF-ID.

The user terminal 1050 acquires the above HTML format screen. Then, when the user presses the link cancellation button on the user terminal 1050 (step S185), an authorization request is made to the content providing server 4, which is the video platform. The content providing server 4 also receives the authorization request and sends information to the user terminal 1050 indicating its response (step S186).

The information sent when making the authorization request has the following configuration, for example:
Authorization: “Basic” + Base64 (<client_id> + “:” + <client_secret>) Request
{
“response_type”: “code”
"code": <authorization code> (authorization code)
“redirect_uri”:<TGW Endpoint> (endpoint of the TV gateway 5)
“client_id”:<TG-ID> (ID of the TV gateway 5)
"scope": <Provided by VPF> (token authentication scope)
“state”: HEX (JSON. stringify ({“tcid”; <TC-ID>, “pfid”; <PF-ID>, “salt”; <random string>}) + hash) (state information)
}

Note that if the television device 2 requests confirmation of the linkage status from the television gateway 5 via the TV cloud 3 at step S185 (steps S251 and S252), the television gateway 5 transmits information indicating linkage to the television device 2 (steps S253 and S254).

Next, the user terminal 1050 makes a login request to the content providing server 4, and the content providing server 4 makes a response in response to the login request (step S188). As an example of the response, the following information (authorization code) is output.
Response
{“code”: <authorization code>,
“state”: <state>}

When the user terminal 1050 receives the response, it redirects the request to the TV gateway 5 to indicate a linking instruction (step S189). Note that the user terminal 1050 may also send the authorization code to the TV gateway 5.

Then, in step S72, the transmission unit 513 of the TV gateway 5 requests a token by sending an authentication code to the destination TV cloud 3 (step S190).

The information transmitted when requesting a token has the following configuration, for example:
Authorization: “Basic” + Base64 (TG-ID + “:” + <client_secret>)
Request Parameters
{
grant_type: “authorization_code”,
code: <authorization code> (authorization code),
state: <string> (state information),
redirect_uri:<redirect_uri>,
client_id:<TG-ID>
}

The generation unit 314 of the TV cloud 3 performs authentication by referencing the DB of the memory unit 311 and determining whether there is information corresponding to the information identifying the content providing server 4 (e.g., information included in the state information) and authentication code acquired by the acquisition unit 312. The generation unit 314 refers to the DB of the memory unit 311, and if there is information corresponding to the information identifying the content providing server 4 and authentication code acquired by the acquisition unit 312, the transmission unit 313 of the TV cloud 3 transmits the first token to the TV gateway 5 (step S191).

Specifically, the transmission unit 313 of the TV cloud 3 sends the OAuth2 Token Response as a token to the TV gateway 5. This response, the OAuth2 Access Token Response, has the following configuration.
Response
{“access_token”: <access token>,
“token_type”: “Bearer”,
“expires_in”: 3600,
“refresh_token”: <refresh token>}

When the TV cloud 3 accesses the TV gateway 5, it attaches an access_token. expires_in is the validity period (seconds) of the access_token, and is stored when the access_token is received along with the time it becomes invalid; until then, the access_token is used repeatedly. The refresh_token is stored secretly by the content providing server 4. For security reasons, it is not advisable to simply store it in local storage. When the access_token and refresh_token are issued by each manufacturer, the TV manufacturer can be identified by adding an identifier that identifies the TV manufacturer to the beginning.

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

The information transmitted when requesting a token has the following configuration, for example:
Authorization: “Basic” + Base64 (TG-ID + “:” + <client_secret>)
Request
{
grant_type: “authorization_code”,
code: <code> (authorization code),
state: <string> (state information),
redirect_uri:<TGW Endpoint>,
client_id:<TG-ID>
}

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

Specifically, the content providing server 4 sends an OAuth2 Token Response as a token to the television gateway 5. This response, OAuth2 Access Token Response, has the following structure:
{“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 transmission unit 513 of the television gateway 5 transmits the second token to the content providing server 4 and requests user information from the content providing server 4 (step S194).

The information transmitted when the user information is requested has, for example, the following configuration.
Authorization: “Bearer” + <access token>)

The content providing server 4 searches for the user ID and user attribute information corresponding to the second token acquired from the television gateway 5, and transmits this information as a response to the television gateway 5 (step S195). As a result, the acquisition unit 512 of the television gateway 5 acquires the user ID and user attribute information. The response information has the following configuration:
Response
{"user_id": <UR-ID> (user ID at the site of the 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 requests device information (step S196). The information transmitted when requesting device information has, for example, the following configuration.
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 information about the device corresponding to the HA-ID (attribute information about the television device 2 corresponding to the HA-ID).

In step S197, the transmission unit 313 of the TV cloud 3 transmits information such as the HA-ID as a response to the TV gateway 5. The acquisition unit 512 of the TV gateway 5 acquires the HA-ID and information on the device corresponding to the HA-ID. Examples of the response include the following:
Response
{
・“device_id”: <HA-ID> (HA-ID)
"model":<model name> (model of the television device 2, i.e., display screen size, pixel count 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). The television gateway 5 may also notify the TV cloud 3 of the deletion of the binding information.

If the television device 2 requests confirmation of the linkage status from the television gateway 5 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 linkage is not established (steps S201 and S202).

In the above embodiment, campaign information is displayed when the program guide is displayed, but campaign information may also be displayed when an advertisement is displayed on the screen at a specified timing during a program broadcast via a network (a program of linearly distributed video content).

For example, campaign information may be displayed using a clickable advertisement such as that shown in Figure 19. Figure 19 is an example of clickable advertisement information. This advertisement information includes information indicating an array of advertisement information objects (ad_list), information indicating the advertisement type (ad_type), and information indicating the URL of the advertisement image (img_url).

In the above embodiment, the processing of the flowchart shown in FIG. 16 was described as the case where the television gateway 5 requests user information from the content providing server 4 and obtains a UR-ID from the content providing server 4, but this is not limited to this. For example, FIG. 20 shows a modified version of the flowchart of FIG. 16. Description of the same parts of the processing as those described in FIG. 16 will be omitted. Instead of the content providing server 4 providing a UR-ID in step S128 or S130 shown in FIG. 20, the television gateway 5 may issue a temporary UR-ID in step S118 and include this parameter in the value of "state" included in the HTML code. In this case, the user terminal 1050 transmits this value to the content providing server 4 in step S120. Furthermore, in the flowchart of FIG. 12, the television gateway 5 may also issue a temporary UR-ID as described above.

In this embodiment, the television gateway 5 stores campaign information and transmits the campaign information to the television device 2 at predetermined times, such as when the television device 2 displays a program guide.

The television gateway 5 also acquires an authentication code from the user terminal 1050, transmits the authentication code to the destination TV cloud 3 identified based on the authentication code, acquires a first token from the TV cloud 3, and acquires a second token from the content providing server 4. The television gateway 5 then acquires the user ID by transmitting the second token to the content providing server 4, and acquires the ID (e.g., HA-ID) of the television device 2 by transmitting the first token to the TV cloud 3. In this way, the television gateway 5 can associate the user ID with the ID of the television device 2 by acquiring the user ID from the content providing server 4 and the ID of the television device 2 from the TV cloud 3.

In this case, the television gateway 5 stores the user ID and the television device 2 ID in association with each other, so the TV cloud 3 does not need to manage user IDs, reducing the information management burden on the TV cloud 3. Furthermore, because the television gateway 5 obtains the authentication code from the user terminal 1050, the content providing server 4 does not need to send the authentication code to the television gateway 5, reducing the processing burden on the content providing server 4. In other words, the television gateway 5 can appropriately execute processing to link the receiver identifier (the television device 2 ID) and the terminal identifier (the user ID of the user terminal 1050). Furthermore, by outputting campaign information, the television gateway 5 can expedite processing to link the television device 2 ID and the user ID of the user terminal 1050.

Furthermore, the television gateway 5 links 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 disclosing the ID of the television device 2 to the content providing server 4.

Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. For example, the television device in the above embodiments may be an electronic device that does not have a display unit but has a receiving function that outputs a video signal to an external display device, such as a set-top box or a recorder. Furthermore, these novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the invention and its equivalents as defined in the claims.
For example, among image icons displayed on a user terminal, an image icon that can be enlarged on a television device may have a button on or near the image icon that instructs the television device to enlarge the image, and the color, shape, or display format of the enlarged image icon may be changed so that it can be visually distinguished from other image icons that cannot be enlarged. Furthermore, when an instruction to enlarge the image on the television device is given from the user terminal, or during display processing on the television device, a voice notification may be made via the user terminal or the television device.

1...Smartphone, 2...Television device, 3...TV cloud, 4...Content provider server, 5...TV gateway, 6...Measurement server, S...Information sharing system

Claims (4)

A server management device capable of transmitting and receiving information to and from a plurality of server devices, the server management device storing information associating an identifier of a broadcast receiving device, an authentication code, an identifier of a content providing device, and a first token, the server management device comprising:
an acquisition unit that receives a request for program guide information from the broadcast receiving device via the server device and acquires program configuration information from the content providing device;
a storage unit that stores promotion information that promotes associating the identifier of the broadcast receiving device with the user identifier of a terminal device of a user of the content providing device;
a transmitting unit that transmits the program configuration information and the promotion information to the broadcast receiving device,
The acquisition unit
acquires, from the terminal device that has acquired the authentication code sent by the server device to the broadcast receiving device in response to a request based on the promotion information from the broadcast receiving device, an authentication request including the authentication code, an identifier of the content providing device, and an identifier of the server device;
acquiring, from the terminal device, a notification of an instruction to link an identifier of the broadcast receiving device and a user identifier of the terminal device;
After receiving the notification of the link instruction, obtain a first token corresponding to the authentication code from a server device corresponding to the authentication request;
acquiring a second token corresponding to a user identifier of the terminal device from a content providing device corresponding to the authentication request;
acquiring an identifier of a broadcast receiving device corresponding to the first token from the server device;
acquiring a user identifier of a terminal device corresponding to the second token from the content providing device;
a generating unit that associates an identifier of the broadcast receiving device corresponding to the first token acquired by the acquiring unit with a user identifier of the terminal device corresponding to the second token and registers the associated identifier in a recording unit;
A server management device comprising: The promotion information includes a normal linked data portion and a campaign linked data portion;
The information indicating the image in the campaign linked data portion is set to be different for each manufacturer of the broadcast receiving device.
The server management device according to claim 1 . A method executed by a server management device capable of transmitting and receiving information to and from a plurality of server devices, the server management device storing information associating an identifier of a broadcast receiving device, an authentication code, an identifier of a content providing device, and a first token, the method comprising:
an acquisition step of accepting a request for program guide information from the broadcast receiving device via the server device and acquiring program configuration information from the content providing device;
a storage step of storing promotion information that promotes associating the identifier of the broadcast receiving device with the user identifier of a terminal device of the user of the content providing device;
a transmitting step of transmitting the program configuration information and the promotion information to the broadcast receiving device,
The obtaining step includes:
acquires, from the terminal device that has acquired the authentication code sent by the server device to the broadcast receiving device in response to a request based on the promotion information from the broadcast receiving device, an authentication request including the authentication code, an identifier of the content providing device, and an identifier of the server device;
acquiring, from the terminal device, a notification of an instruction to link an identifier of the broadcast receiving device and a user identifier of the terminal device;
After receiving the notification of the link instruction, obtain a first token corresponding to the authentication code from a server device corresponding to the authentication request;
acquiring a second token corresponding to a user identifier of the terminal device from a content providing device corresponding to the authentication request;
acquiring an identifier of a broadcast receiving device corresponding to the first token from the server device;
acquiring a user identifier of a terminal device corresponding to the second token from the content providing device;
a generating step of registering in a recording unit an identifier of the broadcast receiving device corresponding to the first token acquired in the acquiring step and a user identifier of the terminal device corresponding to the second token in association with each other;
A method comprising: a computer serving as a server management device capable of transmitting and receiving information to and from a plurality of server devices, the server management device storing information associating an identifier of a broadcast receiving device, an authentication code, an identifier of a content providing device, and a first token;
an acquisition step of accepting a request for program guide information from the broadcast receiving device via the server device and acquiring program configuration information from the content providing device;
a storage step of storing promotion information that promotes associating the identifier of the broadcast receiving device with the user identifier of a terminal device of the user of the content providing device;
a transmitting step of transmitting the program configuration information and the promotion information to the broadcast receiving device,
The obtaining step includes:
acquires, from the terminal device that has acquired the authentication code sent by the server device to the broadcast receiving device in response to a request based on the promotion information from the broadcast receiving device, an authentication request including the authentication code, an identifier of the content providing device, and an identifier of the server device;
acquiring, from the terminal device, a notification of an instruction to link an identifier of the broadcast receiving device and a user identifier of the terminal device;
After receiving the notification of the link instruction, obtain a first token corresponding to the authentication code from a server device corresponding to the authentication request;
acquiring a second token corresponding to a user identifier of the terminal device from a content providing device corresponding to the authentication request;
acquiring an identifier of a broadcast receiving device corresponding to the first token from the server device;
acquiring a user identifier of a terminal device corresponding to the second token from the content providing device;
a generating step of registering in a recording unit an identifier of the broadcast receiving device corresponding to the first token acquired in the acquiring step and a user identifier of the terminal device corresponding to the second token in association with each other;
A program to execute.