Processing method for server management device

Abstract

To allow a process for associating the identifier of a receiver with the identifier of a terminal to be appropriately executed.SOLUTION: A server management device of an embodiment is 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 acquires an authentication request including the authentication code, the identifier of the content providing device, and an identifier of a server device from a terminal device that has acquired the authentication code, acquires a notification of an association instruction from the terminal, and after acquiring the notification of the association instruction, acquires the first token corresponding to the authentication code from the server device corresponding to the authentication request, acquires a second token corresponding to a user identifier of the terminal from the content providing device corresponding to the authentication request, acquires the identifier of the broadcast receiving device corresponding to the first token from the server device, and acquires the user identifier of the terminal device corresponding to the second token from the content providing device.SELECTED DRAWING: Figure 17

Description

Technical Field

[0001] The present invention relates to a server management device.

Background Art

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

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] As described above, in order for the receiver, the terminal, and the content providing device that provides content such as a website to cooperate to transmit and receive information, it is necessary to previously associate the identifier of the user of the terminal and the identifier of the receiver, and it is desirable to perform the association process appropriately.

[0005] Therefore, the problem to be solved by the present invention is to provide a server management device that can appropriately execute the process of associating the identifier of the receiver and the identifier of the terminal.

Means for Solving the Problems

[0006] The server management device according to the embodiment is a server management device capable of transmitting and receiving data with 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. The server management device includes a storage unit that stores promotion information for promoting the association of an identifier of a broadcast receiving device with an identifier of a terminal device of a user of a content providing device, a promotion information transmission unit that transmits the promotion information to the broadcast receiving device, an authentication code transmission unit that transmits an authentication code to the broadcast receiving device in response to a request based on the promotion information from the broadcast receiving device, an authentication request acquisition unit that acquires an authentication request including the authentication code, an identifier of the content providing device, and an identifier of the server device from a terminal device that has acquired the authentication code, a cooperation instruction acquisition unit that acquires a notification of a cooperation instruction between an identifier of the broadcast receiving device and a user identifier of the terminal device from the terminal device, a first token acquisition unit that acquires a first token corresponding to the authentication code from a server device corresponding to the authentication request after acquiring the notification of the cooperation instruction, a second token acquisition unit that acquires a second token corresponding to the user identifier of the terminal device from a content providing device corresponding to the authentication request, a broadcast receiving device identifier acquisition unit that acquires an identifier of the broadcast receiving device corresponding to the first token from the server device, a user identifier acquisition unit that acquires a user identifier of the terminal device corresponding to the second token from the content providing device, and a registration unit that registers the identifier of the broadcast receiving device corresponding to the first token and the user identifier of the terminal device corresponding to the second token in association with each other. The promotion information includes advertisement information including information indicating a display type of an advertisement and information indicating advertisement content.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Embodiments for Carrying Out the Invention

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

[0009] (First Embodiment) First, with reference to FIG. 1, an overall configuration example of the information cooperation system S according to the first embodiment will be described. FIG. 1 is a diagram showing an outline of the overall configuration example of the information cooperation system S according to the first embodiment. The information cooperation 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 can communicate with the television device 2 and the content providing server 4 via a public communication line such as the Internet. Also, the smartphone 1 can communicate wirelessly with the content providing server 4 and the TV cloud 3 via a base station.

[0010] The smartphone 1 is an example of an information terminal owned by the user of the television device 2. The smartphone 1 includes a communication I / F (Interface), a voice input unit (microphone), a sensor group, a display unit, a graphic controller, a touch panel controller, a CPU (Central Processing Unit), a memory, a camera, a speaker, etc. In the first embodiment, it is assumed that the user performs Internet shopping using the smartphone 1.

[0011] The TV cloud 3 is a server device that can communicate with the television device 2 via a network, and is a so-called cloud server. The TV cloud 3 may be, for example, a server device operated by the manufacturer of the television device 2. The TV cloud 3 provides various services such as viewing programs, recommended information for reserved programs, and product recommendation information based on the content of the viewed program to the television device 2 via the network based on the result of collecting information related to viewing (viewing information) from the television device 2.

[0012] The content providing server 4 is a computer device for operating an EC site (online store) on the Internet. The content providing server 4 is, for example, a server device of an EC platform. The content providing server 4 serves as a platform for purchasing goods and services via the network in response to operations of a terminal device (such as the smartphone 1) by a user (consumer). Further, the content providing server 4 may be a video platform that provides content such as videos. The content providing server 4 transmits an image of a product to the smartphone 1, for example, in response to an operation on the smartphone 1. The content providing server 4 registers the redirect_uri in advance with the TV cloud 3.

[0013] Hereinafter, with reference to FIG. 2 and subsequent figures, the details of each component in the information cooperation system S will be described. FIG. 2 is a block diagram showing an overall configuration example of the television device 2 according to the first embodiment. The television device 2 executes display control for the video display unit 233 that is larger than the display unit provided in the smartphone 1 (details will be described later).

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

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

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

[0017] However, the television apparatus 2 may 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 tuner for satellite digital broadcasts via such an input terminal.

[0018] The signal processing unit 207 demodulates a broadcast signal including a digital video signal and an audio signal from the broadcast signals supplied from the tuners 203a to 203g. Further, the signal processing unit 207 selectively performs predetermined digital signal processing on the video signal included in the digital broadcast signal and outputs it to the graphic processing unit 208. Further, the signal processing unit 207 selectively performs desired digital signal processing on the audio signal included in the digital broadcast signal and outputs it to the audio processing unit 209.

[0019] A plurality of external input terminals 214a to 214d are connected to the signal processing unit 207. Analog video signals and audio signals can be input to these external input terminals 214a to 214d from, for example, a DVD (Digital Versatile Disk) recorder as an external device. The signal processing unit 207 digitizes the analog video signals and audio signals input from the external input terminals 214a to 214d. Further, the signal processing unit 207 performs predetermined digital signal processing on the digitized video signal and outputs it to the graphic processing unit 208. Further, the signal processing unit 207 performs predetermined digital signal processing on the digitized audio signal and outputs it to the audio processing unit 209.

[0020] The graphic processing unit 208 superimposes the OSD signal generated by the OSD signal generation unit 210 on the digital video signal supplied from the signal processing unit 207 and outputs it to the video processing unit 211. The graphic 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.

[0021] The video processing unit 211 converts the digital video signal or OSD signal input from the graphic 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 an organic EL display.

[0022] 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 reproduced by the speaker 215 and outputs it to the speaker 215.

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

[0024] The control unit 216 comprehensively controls various operations of the television apparatus 2, such as the reception operation of broadcast signals such as terrestrial digital broadcast signals and satellite digital broadcast signals. Further, the control unit 216 controls each part of the television apparatus 2 according to the operation information from the operation unit 222 or the operation information input from the remote controller 238 via the light receiving unit 223.

[0025] The CPU 216a controls the operation of the entire television apparatus 2 by executing the programs stored in the ROM 216b. The ROM 216b mainly stores the programs executed by the CPU 216a. The RAM 216c provides a work area when the CPU 216a executes programs. The non-volatile memory 216d stores various setting information and control information of the television apparatus 2 and the like.

[0026] The control unit 216 is connected to a card holder 217 to which a memory card 234 is detachable via a card I / F 225. Thereby, the control unit 216 can transmit and receive various information to and from the memory card 234 mounted on the card holder 217 via the card I / F 225.

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

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

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

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

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

[0032] The transmission unit 242 transmits various information to an external device. The acquisition unit 243 acquires various information from an external device or reads out various information stored in the storage unit 241.

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

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

[0035] The communication I / F 301 is an interface used for communication with an external device. The operation unit 302 includes input devices such as a keyboard and a mouse, and a display device such as a display.

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

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

[0038] The storage unit 311 stores programs and a DB (DataBase) executed by the CPU 303. Here, a data configuration example of the DB will be described with reference to FIG. 6. As shown in FIG. 6, the DB stores information including a TVID, an authentication code, an EC server ID, and a token. Note that the DB may have attribute information (such as a TV model) of the television device 2 corresponding to the TVID together with the TVID.

[0039] The TVID is information for identifying the television device 2. The authentication code is a code required for obtaining a token described later. The EC server ID is information for identifying the content providing server 4. That is, it is an ID such as an EC site server. 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 an external device. The generation unit 314 executes an information generation operation on the DB.

[0040] Next, the processing flow of each component in the information sharing system S will be described. FIG. 7 is a flowchart showing the overall processing in the information sharing system S of the first embodiment. Here, it starts with a scenario where a user operates a remote control or the like of the television apparatus 2 to specify an EC site that the user wants to link with the smartphone 1 on a so-called portal screen (a screen for linking with an EC site or the like). Note that the processing of the smartphone 1 shown in FIG. 7 may be executed by an application program installed in the smartphone 1.

[0041] As described above, when an EC site is specified by the user, in step S1, the transmission unit 242 of the television apparatus 2 transmits information on the EC site (for example, the ID of the EC site, the URL of the EC site, etc.) and the TVID which is an identifier of the television apparatus 2 to the TV cloud 3. In this way, the transmission unit 242 transmits information regarding the content providing server 4 which is an image providing apparatus that provides an image in the EC site to the TV cloud 3.

[0042] The acquisition unit 312 of the TV cloud 3 acquires the information on the EC site and the TVID from the television apparatus 2. The generation unit 314 of the TV cloud 3 generates an authentication code, and stores information including the TVID, the EC server ID which is information for identifying the content providing server 4 of the EC site, and the authentication code in the DB of the storage unit 311. Further, the generation unit 314 generates a QR code (registered trademark) which is a two-dimensional code based on the authentication code and the URL which is the access destination of the EC site. Note that the QR code is an example, and other display information may be used. That is, other forms of display information capable of transmitting the authentication code and the access destination information of the EC site may be used. The authentication code may include a part for discriminating the manufacturer and a part for discriminating the television apparatus 2.

[0043] In step S2, the transmission unit 313 of the TV cloud 3 transmits the above QR code to the requesting television device 2. In response to the request from the television device 2, it transmits a QR code including the URL that is the access destination to the EC site and the authentication code.

[0044] The acquisition unit 243 of the television device 2 acquires the QR code from the TV cloud 3. In this way, the acquisition unit 243 of the television device 2 acquires a QR code that is access information based on the authentication code and the URL that is the access destination of the above EC site. The display control unit 244 of the television device 2 causes the video display unit 233 to display the QR code. In this way, the display control unit 244 outputs the QR code for display.

[0045] In step S3, the smartphone 1 reads the QR code displayed on the video display unit 233 by means of a QR code reading function realized by an imaging means or the like. Thereby, the smartphone 1 acquires the URL of the EC site and the authentication code. In step S4, when the smartphone 1 acquires the URL of the EC site and the authentication code, it accesses the content providing server 4 based on the URL and transmits the authentication code.

[0046] When the content providing server 4 acquires the authentication code from the smartphone 1, in step S5, it transmits the authentication code together with the information for identifying the content providing server 4 to the TV cloud 3 and makes an authentication request. Also, the acquisition unit 312 of the TV cloud 3 acquires the authentication code together with the information for identifying the content providing server 4. In this way, the acquisition unit 312 of the TV cloud 3 acquires the authentication code transmitted from the content providing server 4.

[0047] The generation unit 314 of the TV cloud 3 refers to the DB in the storage unit 311, and authenticates by determining whether there is information for identifying the content providing server 4 acquired by the acquisition unit 312 and information corresponding to the authentication code. When there is information for identifying the content providing server 4 acquired by the acquisition unit 312 and information corresponding to the authentication code in the DB of the storage unit 311, the generation unit 314 generates a token by a known technique. Further, the generation unit 314 further associates the token with the information having the information for identifying the content providing server 4 acquired by the acquisition unit 312 and the authentication code in the above DB. The information further associated with the token in the information having the information for identifying the content providing server 4 acquired by the acquisition unit 312 and the authentication code also includes the TV ID of the requesting television device 2.

[0048] Therefore, the generation unit 314 generates correspondence information associating the television device 2 corresponding to the authentication code with the token based on the authentication code.

[0049] 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 the token based on the authentication code to the content providing server 4. The content providing server 4 holds information associating the token with the user ID of the smartphone 1 that is the transmission source of the authentication code.

[0050] In step S7, the smartphone 1 logs in to the content providing server 4 and accesses the EC site. Thereby, the smartphone 1 displays the EC site screen. Here, the user of the smartphone 1 selects an instruction indicating a television display request for a predetermined link destination on the EC site screen. In step S8, the smartphone 1 makes a television display request (TV display request) by transmitting the URL of the link destination to the content providing server 4 in response to the selection. The content providing server 4 acquires the URL of the image display target together with the television display request from the smartphone 1.

[0051] In step S9, the content providing server 4 transmits the token corresponding to the requesting smartphone 1 and the URL of the image to be displayed to the TV cloud 3 and requests the display. The acquisition unit 312 of the TV cloud 3 acquires the token and the URL transmitted by the content providing server 4. Thus, the acquisition unit 312 acquires the token transmitted 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.

[0052] In step S10, the TV cloud 3 refers to the DB in the storage unit 311 and specifies the TV ID corresponding to the token acquired by the acquisition unit 312. Then, the transmission unit 313 of the TV cloud 3 transmits the URL of the access destination of the image to be displayed to the television device 2 corresponding to the TV ID.

[0053] The acquisition unit 243 of the television device 2 acquires the URL of the access destination of the image to be displayed. Further, by the transmission unit 242 of the television device 2 accessing the content providing server 4 based on the URL, the acquisition unit 243 acquires the image based on the access destination of the image to be displayed from the content providing server 4. Then, the display control unit 244 of the television device 2 causes the video display unit 233 to display the image acquired by the acquisition unit 243.

[0054] The TV cloud 3 according to the first embodiment generates correspondence information associating the television device 2 corresponding to the authentication code and the token based on the authentication code. When acquiring the token from the content providing server 4 and the access destination of the image to be displayed based on the request from the smartphone 1, the TV cloud 3 notifies the television device 2 of the access destination of the image, so that the television device 2 can display the image corresponding to the request of the smartphone 1. Thereby, the TV cloud 3 can display the image based on the request of the smartphone 1 on the television device 2 that can be displayed larger than the screen of the smartphone 1.

[0055] In addition, the television apparatus 2 outputs access information including an access destination to the content providing server 4 and an authentication code, acquires an access destination of an image to be displayed based on a request from the smartphone 1 from the TV cloud 3, and causes the video display unit 233 to display the image. As a result, the television apparatus 2 can display an image based on a request from the smartphone 1 on the video display unit 233 that can be displayed larger than the screen of the smartphone 1.

[0056] (Second Embodiment) Unlike the first embodiment, the information sharing system S according to the second embodiment has different TV clouds 3 for each manufacturer of the television apparatus 2. That is, the information sharing system S according to the second embodiment has a plurality of TV clouds 3.

[0057] Here, an overall configuration example of the information sharing system S of the second embodiment will be described. FIG. 8 is a diagram showing an outline of an overall configuration example of the information sharing system S of the second embodiment. Note that the same reference numerals are given to the same configurations as those in the first embodiment, and the description thereof is omitted. As shown in FIG. 8, the information sharing system S has a plurality of TV clouds 3 (TV cloud 3a, TV cloud 3b). The TV cloud 3b can be connected to a television apparatus 2, which is a television (not shown) of the manufacturer related to the TV cloud 3b.

[0058] 2 is a television. 3 is a TV cloud, which is a so-called push distribution server. The TV cloud 3 is a server of a TV manufacturer that manufactures the television apparatus 2 and further provides various services such as recommended viewing programs, recommended reserved programs, and product recommendations based on the content of the viewed programs to the television apparatus 2 via a network from the result of collecting visual information from the television apparatus 2.

[0059] Also, 5 is a TV gateway which is a common reception server. The TV gateway 5 is a server of a maker common site of a television device manufacturer for integrating the TV clouds 3 of a plurality of TV makers and connecting to e-commerce (EC). The information sharing system S has a TV gateway 5 (server management device) capable of transmitting and receiving information to and from the plurality of TV clouds 3 via a network. Also, the TV gateway 5 can transmit and receive information to and from a measurement server 6 for performing measurement processing for aggregating the results of advertisement display via a network. This TV gateway 5 is a cloud server that unites each maker. That is, the TV gateway 5 is a server for integrating the TV clouds 3 of a plurality of TV makers and connecting to the content providing server 4. The TV gateway 5 issues client credentials (client_id, client_secret) to the content providing server 4.

[0060] Also, a random secret installed in the x-api-key is predetermined between the TV cloud 3 and the TV gateway 5. The x-api-key passed between the TV gateway 5 and the content providing server 4 becomes a pass-key.

[0061] 4 is a content providing server such as an EC site server. The content providing server 4 is a server of an EC platform. For the user, i.e., the consumer, the content providing server 4 is a server that serves as a platform for purchasing goods and services. Also, the content providing server 4 causes the TV gateway 5 to pre-register a redirect_uri.

[0062] 1050 is a user terminal. The user terminal 1050 is a terminal having an application program for connecting the television device 2 and the user terminal 1050, and an optical reading device such as a camera. As an example of the user terminal 1050, the smartphone 1 corresponds. In the first embodiment, although the user terminal 1050 is described as being the smartphone 1, it is not limited to the smartphone. The user terminal 1050 may be a PC, a tablet terminal, or the like as long as it satisfies the conditions of the situation. Also, these terminals can replace the smartphone shown in the first embodiment.

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

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

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

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

[0067] The storage unit 511 stores programs executed by the CPU 503 and a DB (DataBase).

[0068] The acquisition unit 512 acquires various information from an external device. The transmission unit 513 transmits various information to the external device. The generation unit 514 executes an information generation operation on the DB.

[0069] Next, the processing flow of each component in the information cooperation system S of the second embodiment will be described. FIG. 11 is a flowchart showing the overall processing in the information cooperation system S of the second embodiment. The flowchart shown in FIG. 11 also starts with a scene where the user operates a remote control or the like of the television device 2 to specify an EC site that the user wants to cooperate with the smartphone 1 on a so-called portal screen. Note that the authentication code and token generated by the TV cloud 3 include information for identifying the manufacturer. That is, the TV cloud 3 includes information for identifying its own device in the authentication code and token.

[0070] Also, since step S21 in FIG. 11 is the same as step S1 in FIG. 7, the description thereof is omitted. In step S22, the URL authentication code is sent from the TV cloud 3 to the television device 2. The URL authentication code 2010 is information including URL information for specifying 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 part for discriminating the manufacturer of the television device 2 and a part for discriminating the television device 2. Also, the part for discriminating the television device 2 included in the authentication code is a random value. Also, the TV cloud 3 may associate the time when this value is transmitted to the television device 2 as information in the DB of the storage unit 311.

[0071] An example of the information of the URL authentication code 2010 is as follows. https: / / XXXXXXX YYYYYYYYY The URL of the content providing server 4 is in the part of X, and the OAuth2 authorization code is in the part of Y. Information for identifying the manufacturer and the TV is included in the authorization code part. Either one of the information for identifying the manufacturer and the television device 2 is sufficient. The sending format of the URL authentication code 2010 may be in any format as long as the above information is included.

[0072] When the acquisition unit 243 of the television device 2 acquires the URL authentication code 2010 from the TV cloud 3, the display control unit 244 optically displays and outputs the content of the URL authentication code 2010 as an image or video on the video display unit 233. Note that the display form by the display control unit 244 may be a QR code, a bar code, text, etc., as long as the information included in the URL authentication code 2010 can be optically displayed and output as an image or video. Also, in the first embodiment, it is described with a QR code, but it is not limited to the QR code in the same manner as this embodiment.

[0073] Also, similar to step S3 in FIG. 7, in step S23, the user terminal 1050 reads the information of the URL authentication code 2011 optically displayed on the video display unit 233 by the URL authentication code reading function from the image information optically captured by the imaging means. Thereby, the user terminal 1050 acquires the URL of the EC site and the authentication code. The authentication code part is configured as a time-limited authentication code as follows. “code” : <authorization code>, “state” : <string> / / Random number

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

[0075] The authentication code 2020 is the authentication code part (<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 In addition to the above, the authentication code 2020 may also include the URL information of the content providing server 4.

[0076] In step S25, when receiving the authentication code 2020, the content providing server 4 sends the authentication code 2021 to the TV gateway 5 and makes an authentication request. For example, the content providing server 4 sends the information of the authentication request to the Token Endpoint of OAuth2 of the TV 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> (authentication code) ·redirect_uri: The entrance when returning to the EC site of the content providing server 4, pre-registered with the TV gateway 5. ·client_id: The identifier assigned for each EC site of the content providing server 4. Pre-registered with 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 redirects by looking at the maker extension of the code.

[0077] In step S26, the transmission unit 313 of the TV gateway 5 refers to the acquired authentication code 2021, refers to the information for identifying the maker included in the authentication code 2021, and specifies the destination TV cloud 3. Specifically, the transmission unit 313 of the TV gateway 5 confirms the authorization code, that is, the authentication code, and determines which TV cloud 3 it is.

[0078] Then, in step S27, the transmitter 313 of the TV gateway 5 sends an authentication request by sending an authentication request 2022 to the destination TV cloud 3. In this way, the transmitter 513 of the TV gateway 5 sends an authentication request 2022 to the destination TV cloud 3 specified based on the Authorization_code (authentication code) of the authentication code 2021. The information of the authentication request 2022 sent by the transmitter 313 of the TV gateway 5 is the same as the information of the authentication code 2021 obtained from the content providing server 4. Examples of other information of the authentication request 2022 are as follows. GET https: / / each-maker.example.com / common / devices / id Authorization: "Bearer ” + <access_token> The acquisition unit 312 of the TV cloud 3 acquires the authentication code described in the URL authentication code 2010 together with the information for identifying the content providing server 4.

[0079] The generation unit 314 of the TV cloud 3 refers to the DB in the storage unit 311 and authenticates by determining whether there is information for identifying the content providing server 4 and information corresponding to the authentication code acquired by the acquisition unit 312. When there is information for identifying the content providing server 4 and information corresponding to the authentication code acquired by the acquisition unit 312 in the DB of the storage unit 311, the generation unit 314 generates a token 2030. In addition, the generation unit 314 further associates the token 2030 with the information having the information for identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312 in the above DB.

[0080] In step S28, the transmitter 313 of the TV cloud 3 sends the token 2030 generated by the generation unit 314 to the TV gateway 5.

[0081] Specifically, the transmission unit 313 of the TV cloud 3 sends the OAuth2 Token Response as the token 2030 to the TV gateway 5. The OAuth2 Access Token Response of this response is configured as follows. {"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 the access_token. expires_in is the valid period (in seconds) of the access_token. When receiving the access_token, it is memorized together with the time when it becomes invalid. Until then, this access_token is used repeatedly. The refresh_token is secretly stored by the content providing server 4. For security reasons, it is not good to simply place it in local storage. When issuing the access_token and refresh_token for each manufacturer, the TV manufacturer can be identified by attaching an identifier for identifying the TV manufacturer at the beginning.

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

[0083] The content providing server 4 holds information in which the token 2031 is associated with the user ID of the user terminal 1050 that is the sender of the authentication code.

[0084] Then, in step S30, the content providing server 4 transmits the token 2031 and the user ID as a response to the token + user ID 2040 to the TV gateway 5. As a result, the content providing server 4 can transmit the user ID of the user of the user terminal 1050 to the TV gateway 5.

[0085] The configuration of the information 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 an access token in step S28), client_id: Identifier assigned for each site of the content providing server 4. Pre-registered on the manufacturer common site, user_id: User ID on 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.)}

[0086] 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 transmit the token when transmitting the device ID request 2041.

[0087] The device ID request 2041 is a request for the TV gateway 5 to inquire about the TV's device ID (TVID) from each manufacturer (TV cloud 3) using the OAuth2 access token. For example, it is as follows. GET https: / / each-maker.example.com / common / devices / id ·Authorization: "Bearer ” + <access_token> ·x-api-key: <random secret defined by the manufacturer common site and each manufacturer> ·Content-type: application / json ·client_id: identifier assigned for each manufacturer common site

[0088] The TV cloud 3 refers to the DB in the storage unit 311 and acquires the TVID corresponding to the obtained token. Also, the TV cloud 3 may acquire information on the device corresponding to the obtained TVID (attribute information of the television device 2 with the TVID). In step S32, the transmitter 313 of the TV cloud 3 transmits information such as the TVID to the TV gateway 5 as the device ID response 2050. Examples of the device ID response 2050 are as follows. · "device_id”: <id>(TVID given to the television device 2 by the TV cloud 3) · "model": <model name> (Model of the television device 2, i.e., information such as the display screen size in inches and pixel count information such as 2K, 4K, 8K, etc.)

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

[0090] Also, the generation unit 514 of the TV gateway 5 generates a pass key 2051. Further, 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 during the operations of operation commands 2090 to 2093 after step S44.) · "expires_in": 86400, (expires_in is returned with a grace period of, for example, 10 days even when preferences cannot be prepared at the first access.) · "model": <model name> (Model information of the device ID response, i.e., model of the television device 2, i.e., information such as the display screen size in inches and pixel count information such as 2K, 4K, 8K, etc.)

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

[0092] When the content providing server 4 acquires the pass key from the TV 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 / / Associated TV model information

[0093] In step S36, the user terminal 1050 logs in to the service provided by the content providing server 4 by starting the application. As a result, the smartphone 1 displays the EC site screen. The EC site screen output by the application also outputs a button for connecting to the television device 2. In step S37, the content providing server 4 transmits the device information 2070 to the user terminal 1050 in response to the login in step S36. The device information 2070 here refers to any one or two or three combinations of the device ID, user ID, and model name included in the pass key 2051.

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

[0095] When the content providing server 4 receives the TV display request 2071 from the user terminal 1050, in step S39, it requests the television device 2 to display by transmitting a display request 2072 including a token, a pass key, and the URL of the link destination to the TV gateway 5. The configuration of the information 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"}

[0096] The acquisition unit 512 of the TV gateway 5 receives information of a display request 2072 including a token, a pass key, and a link destination URL from the content providing server 4. Then, the acquisition unit 512 extracts the pass key from the header of x-api-key.

[0097] In step S40, the acquisition unit 512 discriminates the access destination and the access source using the pass key (pass_key) and the information stored in the storage unit 511. In step S41, the transmission unit 513 transmits information including a token URL to the TV cloud 3 based on the discriminated result and makes a display request. In this way, the transmission unit 513 transmits a token and an access destination of an image to be displayed to the TV cloud 3 of the transmission destination. Note that the TV gateway 5 measures the number of accesses by access source and by manufacturer.

[0098] The display request 2073 transmitted by the transmission unit 513 to the TV cloud 3 includes a token, a client ID, a URL, and a message. Examples of the information are as follows. POST https: / / each-maker.example.com / common / devices / control Authorization: "Bearer " + <access_token> x-api-key: <random secret defined by the common site of manufacturers 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-specific Website URL), "template”: "full”, "client_id”: <client_id>, "messageid”: <message ID>}

[0099] The acquisition unit 312 of TV Cloud 3 receives a display request 2073 from the TV 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 TV Cloud 3 outputs a display request 2074 to the television device 2 based on the identified result. Note that the display request may be replaced with a manufacturer-specific display request command. Also, if necessary, TV Cloud 3 may aggregate accesses for each client_id and make a request to the TV.

[0100] In step S43, the television device 2 activates the browser in response to the display request, executes javascript (registered trademark) with events such as onLoad and onClick, and displays and outputs the image at the URL destination of the display target. Also, the television device 2 notifies the measurement server 6 of a display operation result notification 2080 for identifying the service provider, user, TV manufacturer, and displayed advertisement. The measurement server 6 aggregates the results of the advertisement displays by TV Cloud 3 to multiple television devices 2. Based on the aggregated results, the manufacturer, TV gateway 5, or the owner of the measurement server 6 requests an advertising fee from the e-commerce platform that owns the content provider server 4.

[0101] 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.

[0102] In step S45, the content providing server 4 sends an operation command 2091 including a common key code to the TV gateway 5 based on the operation command 2090 sent in step S44. The common key code is a command configured to correspond to the operation buttons of the TV operation remote control. There are numbers, cross cursors, volume / channel / power, color keys, function keys, media controls, and manufacturer-specific commands. This manufacturer-specific command is a command for each manufacturer to operate independently. That is, the manufacturer-specific command is a manufacturer-specific operation command set by each manufacturer. The common key code is a key code for performing common operations among manufacturers excluding the manufacturer-specific commands.

[0103] The number commands are "11", "12", "0", "1", "2", "3", "4", "5", "6", "7", "8", "9", ".".

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

[0105] The volume / channel / power commands are "power", "power off", "power on", "volume up", "volume down", "channel up", "channel down".

[0106] The color keys are "blue", "red", "green", "yellow".

[0107] The function key commands are "electronic program guide", "initial configuration", "select broadcast type", "input select", "display information", "mute", "contents menu", "closed caption".

[0108] The media control commands are "Play", "stop", "pause", "rewind ", "forward", "backward", "skip forward", "skip backward", "record".

[0109] When the TV gateway 5 receives the operation command 2091 in step S45, it sends the 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 TV gateway 5 sends the response message ID 2094 to the content providing server 4 as a response message. The message ID has the following configuration. {messageid: <message ID>}

[0110] When the TV cloud 3 receives the operation command 2092 from the TV 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 the key code of each company for operating the television device 2. When the standardization of the operation commands of the television device 2 progresses, the operation command 2092 can be used as the operation command 2093 without conversion.

[0111] The television apparatus 2 operates on the image displayed on the video display unit 233 of the television apparatus 2 based on the operation command 2093. Also, in step S49, the television apparatus 2 notifies the measurement server 6 of an operation result notification 2081 for identifying the operation command.

[0112] The flowchart shown in FIG. 11 explains the process of accessing the content providing server 4 of the platform by integrating multiple manufacturers. However, like the TV cloud 3 of the first embodiment, a manufacturer can also access the content providing server 4 alone. In this case, the TV cloud 3 combines the operations of the TV gateway 5. At this time, the exchange of information between the TV cloud 3 and the TV gateway 5 is omitted.

[0113] The TV gateway 5 acquires an authentication code from the content providing server 4, transmits the authentication code to the TV cloud 3 of the specified destination 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 TV cloud 3 of the destination. Thereby, the content providing server 4 side can process without determining to which of the plurality of TV clouds 3 to transmit.

[0114] Note that the programs executed by each device (user terminal 1050, television apparatus 2, TV cloud 3, content providing server 4, TV gateway 5, measurement server 6) of the present embodiment can be recorded and provided on a recording medium readable by a computer device such as a CD (Compact Disc)-ROM (Read Only Memory), flexible disk (FD), CD-R (Recordable), DVD (Digital Versatile Disk) in an installable format or an executable format file. Also, the program may be provided or distributed via a network such as the Internet.

[0115] (Third Embodiment) The information cooperation system S according to the third embodiment is the same as the overall configuration of the information cooperation system S of the second embodiment. In the information cooperation system S according to the third embodiment, the TV gateway 5 acquires tokens not only from the TV cloud 3 but also from the content providing server 4, and uses these tokens to associate the ID of the television device 2 with the user ID of the user terminal 1050.

[0116] Note that the structure of the data stored in the TV cloud 3 shown in FIG. 6 is different. Specifically, the TV cloud 3 stores an HA-ID instead of the TVID shown in FIG. 6. Also, instead of the EC site server ID shown in FIG. 6, the TV cloud 3 stores a PF-ID. The HA-ID is identification information including the TC-ID which is the company ID of the TV manufacturer and the 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 for identifying the TV cloud 3. Also, the PF-ID is an identifier for identifying the content providing server 4.

[0117] Next, the processing flow of each component in the information cooperation system S of the third embodiment will be described. FIG. 12 is a flowchart showing the overall processing in the information cooperation system S of the third embodiment. The flowchart shown in FIG. 12 also starts with a scenario where the user operates a remote control or the like of the television device 2 to specify an EC site (for example, a server that receives content) that the user wants to cooperate with the smartphone 1 in a so-called portal screen. Note that the authentication code and token generated by the TV cloud 3 include information for identifying the manufacturer. That is, the TV cloud 3 includes information for identifying its own device in the authentication code and token.

[0118] Also, step S61 in FIG. 12 is the same as step S1 in FIG. 7 and step S12 in FIG. 11. Note that 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.

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

[0120] {"code”:<authorization code> (authentication code), "state”:HEX(JSON.stringify({"tcid”; <tc-id>,"pfid”; <pf-id>,"salt”;<random string>})+hash)(state information)}

[0121] The URL authentication code is information including the URL information identifying the TV gateway 5, the authentication code for authentication between the content providing server 4 and the TV cloud 3, and the state information. The authentication code may include a part for discriminating the manufacturer of the television apparatus 2 and a part for discriminating the television apparatus 2. Also, the part for discriminating the television apparatus 2 included in the authentication code is a random value. Further, the TV cloud 3 may associate the time when this value is transmitted to the television apparatus 2 as information in the DB of the storage unit 311. The state information may include information in which the manufacturer's TC-ID and the PF-ID of the video platform are encoded.

[0122] An example of the information of the URL authentication code is as follows. https: / / XXXXXXX YYYYYYYYY In the X part, the URL of the TV gateway 5 is included, and in the Y part, the OAuth2 authorization code is included. In the authorization code part, information for identifying the manufacturer and the TV is included. Either one of the information for identifying the manufacturer and the television apparatus 2 may be used. The sending format of the URL authentication code may be in any format as long as the above information is included. Note that the state information may be included in the Y part.

[0123] When the acquisition unit 243 of the television apparatus 2 acquires the URL authentication code from the TV cloud 3, the display control unit 244 optically displays and outputs the content of the URL authentication code as an image or video on the video display unit 233. Note that the display form by the display control unit 244 may be a QR code, a bar code, text, etc., as long as the information included in the URL authentication code can be optically displayed and output as an image or video. Also, in the first embodiment and the second embodiment, the QR code is described, but it is not limited to the QR code in the same manner as in this embodiment.

[0124] Also, similar to step S3 in FIG. 7 and step S23 in FIG. 11, in step S63, the user terminal 1050 reads the information of the URL authentication code optically displayed on the video display unit 233 from the image information optically captured by the imaging means by means of the URL authentication code reading function. As a result, the user terminal 1050 acquires the URL of the TV gateway 5, the authentication code, and the like. The authentication code part is configured as a time-limited authentication code as follows. "code” : <authorization code>, "state” : <string> / / Random number

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

[0126] The information transmitted at the time of the authentication request is as follows. "code” : <authorization code>, "state” : <string> / / Random number

[0127] 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-formatted screen including a cooperation button indicating a cooperation instruction to the user terminal 1050. The HTML may include a URL and parameters for accessing the OAuth2 Authorization Endpoint of the PF-ID.

[0128] The user terminal 1050 acquires the above HTML-formatted screen. Then, when the cooperation button is pressed by a user operation on the user terminal 1050 (step S66), an authorization request is made to the content providing server 4 which is a video platform. Also, the content providing server 4 receives the authorization request and transmits information to the effect of responding thereto to the user terminal 1050 (step S67).

[0129] The information transmitted at the time of the above authorization request has, for example, the following configuration. Authorization: "Basic ” + Base64(<client_id> + ":” + <client_secret>)Request { "response_type”:"code” "code”:<authorization code> (authentication code) "redirect_uri”:<TGW Endpoint>(endpoint of the TV gateway 5) "client_id”: <tg-id>(ID of the TV gateway 5) "scope”: <VPF provided> (Token authentication scope) "state”: HEX(JSON.stringify({"tcid”; <tc-id>,"pfid”; <pf-id>,"salt”;<random string>})+hash)(state information) [[ID=2}}

[0130] When user information is not registered in the content providing server 4, a user registration process is performed between the user terminal 1050 and the content providing server 4 (step S68). Here, the user registration process is a process of registering a user ID and a password, which are information for logging in to the content providing server 4, or registering user attribute information.

[0131] Subsequently, the user terminal 1050 makes a login request to the content providing server 4, and the content providing server 4 responds 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>}

[0132] When the user terminal 1050 receives the above response, it makes a redirect indicating a cooperation instruction to the TV gateway 5 (step S70). Note that the user terminal 1050 may transmit the above authorization code to the TV gateway 5.

[0133] When the acquisition unit 512 of the TV gateway 5 receives a redirect indicating a cooperation instruction, the TV gateway 5 identifies the manufacturer based on the TC-ID included in the state information acquired from the user terminal 1050. That is, the TV gateway 5 allocates the manufacturer (step S71).

[0134] Then, in step S72, the transmission unit 513 of the TV gateway 5 makes a token request by transmitting an authorization code to the destination TV cloud 3 (step S72).

[0135] The information transmitted at the time of the token request is, for example, configured as follows. 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> }

[0136] The generation unit 314 of the TV cloud 3 refers to the DB in the storage unit 311, and authenticates by determining whether there is information for identifying the content providing server 4 (for example, information included in the state information) and information corresponding to the authentication code obtained by the acquisition unit 312. When there is information for identifying the content providing server 4 and information corresponding to the authentication code obtained by the acquisition unit 312 in the DB of the storage unit 311, the generation unit 314 generates a token (first token). Further, the generation unit 314 further associates the first token with the information having the information for identifying the content providing server 4 and the authentication code obtained by the acquisition unit 312 in the above DB.

[0137] 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.

[0138] Specifically, the transmission unit 313 of the TV cloud 3 sends the OAuth2 Token Response as a token to the TV gateway 5. The OAuth2 Access Token Response of this response is configured as follows. Response {"access_token”: <access token>, "token_type”: "Bearer”, "expires_in”: 3600, "refresh_token”: <refresh token>}

[0139] When the TV cloud 3 accesses the TV gateway 5, an access_token should be attached. expires_in is the expiration period (in seconds) of the access_token. When receiving the access_token, remember the time when it becomes invalid, and repeatedly use this access_token until then. The refresh_token is secretly stored by the content providing server 4. This is because, for security reasons, simply storing it in local storage is not good. When issuing the access_token and refresh_token by each manufacturer, the TV manufacturer can be identified by attaching an identifier for identifying the TV manufacturer at the beginning.

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

[0141] The information transmitted during the token request is, for example, configured as follows. Authorization: "Basic” + Base64(TG-ID + ":” + <client_secret>) Request { grant_type: "authorization_code”, code : <code>(Approval code), state : <string>(state information), redirect_uri: <TGW Endpoint>, client_id: <tg-id> }

[0142] Based on the authorization code obtained from the TV gateway 5, the content providing server 4 identifies the user ID corresponding to the authorization code. Then, the content providing server 4 generates a second token, which is a token based on the user ID.

[0143] In step S75, the content providing server 4 sends the generated second token to the TV gateway 5. Note that the content providing server 4 may store the second token, the user ID, and the user attribute information in association with each other.

[0144] Specifically, the content providing server 4 sends the OAuth2 Token Response as a token to the TV gateway 5. The OAuth2 Access Token Response of this response is configured as follows. {"access_token”: <access token>, "token_type”: "Bearer”, "expires_in”: 3600, "refresh_token”: <refresh token>}

[0145] The acquisition unit 512 of the TV gateway 5 acquires the second token from the content providing server 4. Then, the transmission unit 513 of the TV gateway 5 sends the second token to the content providing server 4 and requests user information from the content providing server 4 (step S76).

[0146] The information sent at the time of the user information request is, for example, configured as follows. Authorization: "Bearer” + <access token>)

[0147] The content providing server 4 searches for the user ID and the user's attribute information corresponding to the second token acquired from the TV gateway 5, and transmits this information as a response to the TV gateway 5 (step S77). Thereby, the acquisition unit 512 of the TV gateway 5 acquires the user ID and the user's attribute information. The information of the response is configured as follows. Response {"user_id”: <ur-id>(User ID on the site of the content providing server 4), "Preference”: <Current user attributes> (user's date of birth, gender, postal code, purchase history, etc.)}

[0148] In step S78, the content providing server 4 transmits the PF-ID and requests device information. The information transmitted at the time of the device information request has, for example, the following configuration. Authorization: "Basic” + Base64(PF-ID + ":" + <client_secret>)

[0149] When the acquisition unit 512 of the TV gateway 5 receives a device information request from the content providing server 4, the transmission unit 513 of the TV gateway 5 transmits the first token corresponding to the second token transmitted in step S74 to the TV cloud 3 and requests device information (step S79). The information transmitted at the time of the device information request has, for example, the following configuration. Authorization: "Bearer” + <access token>)

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

[0151] 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 the information of the device corresponding to the HA-ID. Examples of the response are as follows. Response { · "device_id”: <ha-id>(HA-ID) · "model": <model name> (Model of the television device 2, i.e., information such as the inch of the display screen and the number of pixels such as 2K, 4K, 8K, etc.) }

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

[0153] Also, the generation unit 514 of the television gateway 5 generates a pass key. Also, in step S82, 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 during the operation of the operation command) · "expires_in": 86400, (expires_in is returned with a grace period of 10 days or so even if preferences cannot be prepared at the first access.) · "model": <model name> (Model information of the device ID response, i.e., model of the television device 2, i.e., information such as the inch of the display screen and the number of pixels such as 2K, 4K, 8K, etc.)

[0154] Also, the generation unit 514 of the television gateway 5 stores the generated pass key in the storage unit 511.

[0155] 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 content providing server 4 stores the following information for each user ID of the EC site. · access_token · refresh_token · pass_key ·model / / Associated TV model information

[0156] The TV gateway 5 obtains an authentication code from the user terminal 1050, transmits the authentication code to the TV cloud 3 of the specified destination based on the authentication code, obtains a first token from the TV cloud 3, and obtains a second token from the content providing server 4. Then, the TV gateway 5 transmits the second token to the content providing server 4 to obtain the user ID, and transmits the first token to the TV cloud 3 to obtain the ID (for example, HA-ID) of the television apparatus 2. In this way, the TV gateway 5 can associate the user ID with the ID of the television apparatus 2 by obtaining the user ID from the content providing server 4 and obtaining the ID of the television apparatus 2 from the TV cloud 3.

[0157] In this case, since the TV gateway 5 associates and stores the user ID with the ID of the television apparatus 2, the TV cloud 3 does not need to manage the user ID, and the information management burden on the TV cloud 3 can be reduced. Further, since the TV gateway 5 obtains the authentication code from the user terminal 1050, the content providing server 4 does not need to transmit the authentication code to the TV gateway 5, and the processing burden on the content providing server 4 can also be reduced. That is, the TV gateway 5 can appropriately execute the process of linking the identifier of the receiver (the ID of the television apparatus 2) and the identifier of the terminal (the user ID of the user terminal 1050).

[0158] (Fourth Embodiment) The information cooperation system S according to the fourth embodiment has the same overall configuration as the information cooperation system S of the second embodiment. In the second embodiment, the case where the authentication code is also included in the QR code was described, but in the information cooperation system S according to the fourth embodiment, the authentication code is separately displayed with a pin code.

[0159] Next, the processing flow of each component in the information sharing system S of the fourth embodiment will be described. Since step S21 in FIG. 13 is the same as step S21 in FIG. 11 and step S1 in FIG. 7, the description thereof will be omitted.

[0160] In step S91, the TV cloud 3 transmits a QR code including a URL to the television device 2. Also, the TV cloud 3 transmits a pin code corresponding to the authentication code to the television device 2.

[0161] Examples of the information of the URL included in the QR code are as follows. https: / / XXXXXXX The URL of the content providing server 4 is entered in the X part. The transmission format of the URL of the QR code may be in any format as long as the above information is included.

[0162] When the acquisition unit 243 of the television device 2 acquires the QR code and the 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. Also, the display control unit 244 displays and outputs the pin code.

[0163] In step S92, the user terminal 1050 reads the information of the URL optically displayed on the video display unit 233 by a reading function from the image information optically captured by the imaging means.

[0164] In step S93, the user terminal 1050 starts an application (app) and makes it possible to accept the input of the pin code.

[0165] In step S94, when a PIN code is input by a 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 FIG. 11, respectively.

[0166] The TV cloud 3 according to the fourth embodiment transmits a pin code corresponding to the authentication code to the television device 2, and the television device 2 displays the pin code. Then, the user of the user terminal 1050 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 the authentication code.

[0167] In this case, even when the authentication code cannot be included in the two-dimensional code together with the URL, the authentication code can be transmitted from the user terminal 1050 to the content providing server 4.

[0168] (Fifth Embodiment) The information cooperation system S according to the fifth embodiment has the same overall configuration as the information cooperation system S of the third embodiment. In the information cooperation system S according to the fifth embodiment, the television gateway 5 transmits campaign information as promotion information for promoting the process of linking the ID of the television device 2 and the user ID of the user terminal 1050 in the information cooperation system S according to the third embodiment to the television device 2. In the information cooperation system S, when the television device 2 instructs the process of linking the ID of the television device 2 and the user ID of the user terminal 1050 based on the promotion information, the information cooperation system S executes the process of linking the ID of the television device 2 and the user ID of the user terminal 1050.

[0169] In the information cooperation 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. The television gateway 5 acquires program guide configuration information and transmits the program guide configuration information to the television device 2. The program guide configuration information includes broadcaster information, channel information, program information, CM information, and VOD information. Note that a file server that realizes the television gateway 5 stores the program guide configuration information. That is, the television gateway 5 stores the program configuration information and transmits the stored program configuration information to the television device 2 in response to a request to acquire program guide information from the television device 2.

[0170] The TV gateway 5 stores campaign information and transmits the campaign information in response to a request from the television apparatus 2 when transmitting the program guide configuration information.

[0171] Here, the content of the campaign information will be described with reference to FIG. 14. FIG. 14 is a diagram showing an example of promotion information. The campaign information includes a normal cooperation data part 330, a campaign cooperation data part 340, and one or more advertisement information parts 350.

[0172] The normal cooperation data part 330 includes information (idbind) indicating an object of ID cooperation data, information (img_base_url) indicating a base URL of a URL where an image file is stored, information (bind's explanation_img) indicating an image explaining a cooperation method, and information (unbind's explanation_img) indicating an image explaining a cooperation cancellation method.

[0173] The campaign cooperation data part 340 includes information (idbind_campaign) indicating an array of objects of campaign information, information (tv) indicating a TV manufacturer targeted by the campaign, information (img_base_url) indicating a base URL of a URL where an image file is stored, information (campaign_img) indicating an image explaining the content of the campaign, information (hasbound_img) indicating an image to be displayed when already cooperated, information (explanation_img) indicating an image explaining a cooperation method, information (recommend_tracking_img) indicating an image recommending to permit tracking by IFA-ID, information (start) indicating a campaign start date and time, and information (end) indicating a campaign end date and time.

[0174] The information indicating an image in the campaign cooperation data part 340 may be set to be different for each TV manufacturer by a macro or the like. Thereby, different campaign images can be assigned to each of a plurality of TV manufacturers with a simple configuration.

[0175] The advertisement information part 350 includes array information (tv) indicating the TV manufacturer to be displayed, an ad_info unique identifier (id), advertisement information (ad_info) including information indicating the display type of the advertisement and the content of the advertisement, a display start date and time (start), and a display end date and time (end).

[0176] Also, as shown in FIGS. 14 and 15, the advertisement information includes information (type) indicating the display type of the advertisement, information (place) indicating the ID of the screen to be displayed, a text message (message) to be displayed when the display type of the advertisement is text, a URL (image) of the display image to be displayed when the display type of the advertisement is image, a URL (movie) of the video to be displayed when the display type of the advertisement is movie, and information (period) indicating the display period of the advertisement. The above text message, URL of the display image, and URL of the video are examples of information indicating the content of the advertisement.

[0177] The campaign information shown in FIG. 14 includes an advertisement information part 350a where the advertisement type is text, an advertisement information part 350b where the advertisement type is image, and an advertisement information part 350c where the display type of the advertisement is movie. When the television device 2 receives the campaign information shown in FIG. 14, it displays an advertisement with a text message, an advertisement with a display image, and an advertisement with a video.

[0178] Subsequently, the procedure for displaying an advertisement based on the campaign information will be described with reference to FIG. 16. FIG. 16 is a flowchart showing the advertisement display process of the campaign information.

[0179] The process shown in FIG. 16 is a process executed by the television apparatus 2 in the program guide display process. The television apparatus 2 makes a request to the television gateway 5 for acquisition of program guide configuration information (program guide) of an EC site designated by the user in response to a user operation. When the television apparatus 2 makes a request for acquisition of program guide information, the television gateway 5 receives the request for acquisition of program guide information. The television gateway 5 transmits the program guide configuration information to the television apparatus 2. The television apparatus 2 displays the program guide configuration information. The program guide configuration information includes broadcaster information, channel information, program information, CM information, and VOD information.

[0180] As described above, when the television apparatus 2 displays the program guide configuration information, it makes a request to the television gateway 5 for acquisition of campaign information. If the television apparatus 2 fails to acquire campaign information from the television gateway 5 (step S101: No), the process ends.

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

[0182] If there is advertisement information within the valid period (step S102: Yes), the television apparatus 2 extracts the information to be displayed from the campaign information (step S103). Then, the television apparatus 2 executes the loop process of step S104 until it displays all the extracted information or ends the program guide display by a user operation.

[0183] In the loop process of step S104, the television apparatus 2 displays an advertisement according to the type of the advertisement (step S105).

[0184] In addition, when the television device 2 is displaying an advertisement (for example, during the loop process of step S104), if the user selects to apply for a campaign, the television device 2 may display questionnaire information, accept the input of the questionnaire information, and request a linkage instruction. This questionnaire is a questionnaire that accepts the input of the user's attributes (such as gender, address, etc.).

[0185] Note that the television device 2 may refer to the campaign information, first display a screen on which the user can select to apply for the campaign, and then execute the processing of the flowchart shown in FIG. 16. That is, the television device 2 may execute the processing related to advertisement display and the processing related to ID linkage separately and independently.

[0186] Subsequently, the linkage processing procedure will be described with reference to FIG. 17. FIG. 17 is a flowchart showing the linkage processing procedure. It is assumed that the authentication code and token generated by the TV cloud 3 include information for identifying the manufacturer. That is, the TV cloud 3 includes the information for identifying its own device in the authentication code and token.

[0187] Before executing the processing of the flowchart shown in FIG. 16, the television device 2 generates an IFA-ID by a random number and notifies the TV cloud 3 (step S111). This IFA-ID is a numerical value having a number of digits that can guarantee uniqueness. Note that the television device 2 may transmit the TV model name of the television device 2. Also, in step S111 and step S112, bearer authentication may be performed.

[0188] The TV cloud 3 transmits the IFA-ID to the TV gateway 5 (step S112). Thereafter, in step S113, the processing of the flowchart shown in FIG. 16 is executed. When a linkage instruction is given in step S113, the television device 2 requests a QR code (step S114).

[0189] Also, step S114 in FIG. 17 is the same as step S1 in FIG. 7, step S12 in FIG. 11, and step S61 in FIG. 12. 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.

[0190] In step S115, the TV cloud 3 sends a QR code including the URL of the TV gateway 5 and the 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.

[0191] {"code”:<authorization code> (authentication code), "state”:HEX(JSON.stringify({"tcid”; <tc-id>,"pfid”; <pf-id>,"salt”;<random string>})+hash)(state information)}

[0192] The URL authentication code is information including the URL information for specifying the TV gateway 5, the authentication code for performing authentication between the content providing server 4 and the TV cloud 3, and the state information. The authentication code may include a part for discriminating the manufacturer of the television apparatus 2 and a part for discriminating the television apparatus 2. Also, the part for discriminating the television apparatus 2 included in the authentication code is a random value. Further, the TV cloud 3 may associate the time when this value is transmitted to the television apparatus 2 with the information in the DB of the storage unit 311. The state information may include information in which the manufacturer's TC-ID and the PF-ID of the video platform are encoded.

[0193] An example of the information of the URL authentication code is as follows. https: / / XXXXXXX YYYYYYYYY In the X part, the URL of the TV gateway 5 is included, and in the Y part, the OAuth2 authorization code is included. In the authorization code part, information for specifying the manufacturer and the TV is included. Either one of the information for specifying the manufacturer and the television apparatus 2 may be used. The sending format of the URL authentication code may be in any format as long as the above information is included. Note that the state information may be included in the Y part.

[0194] When the acquisition unit 243 of the television apparatus 2 acquires the URL authentication code from the TV cloud 3, the display control unit 244 optically displays and outputs the content of the URL authentication code as an image or video on the video display unit 233. The display form by the display control unit 244 may be a QR code, a barcode, text, etc., as long as the information included in the URL authentication code can be optically displayed and output as an image or video. Also, in the first embodiment and the second embodiment, the QR code is described, but it is not limited to the QR code in the same manner as this embodiment.

[0195] Also, similar to step S3 in FIG. 7, step S23 in FIG. 11, and step S63 in FIG. 12, in step S116, the user terminal 1050 reads the information of the URL authentication code optically displayed on the video display unit 233 from the image information optically captured by the imaging means by the URL authentication code reading function. Thereby, the user terminal 1050 acquires the URL of the TV gateway 5, the authentication code, and the like. The authentication code part is configured as a time-limited authentication code as follows. "code” : <authorization code>, "state” : <string> / / Random number

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

[0197] The information transmitted at the time of the authentication request is as follows. "code” : <authorization code>, "state” : <string> / / Random number

[0198] 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-formatted screen including a cooperation button indicating a cooperation instruction to the user terminal 1050. The HTML may include a URL and parameters for accessing the OAuth2 Authorization Endpoint of the PF-ID.

[0199] The user terminal 1050 acquires the above HTML-formatted screen. Then, when the cooperation button is pressed by a user operation on the user terminal 1050 (step S119), an authorization request is made to the content providing server 4 which is a video platform. Also, the content providing server 4 receives the authorization request and transmits information to the effect of responding thereto to the user terminal 1050 (step S120).

[0200] The information transmitted at the time of the above authorization request has, for example, the following configuration. Authorization: "Basic ” + Base64(<client_id> + ":” + <client_secret>)Request { "response_type”:"code” "code”:<authorization code> (authentication code) "redirect_uri”:<TGW Endpoint>(endpoint of the TV gateway 5) "client_id”: <tg-id>(ID of the TV gateway 5) "scope”: <VPF provided> (Token authentication scope) "state”: HEX(JSON.stringify({"tcid”; <tc-id>,"pfid”; <pf-id>,"salt”;<random string>})+hash)(state information) }

[0201] In addition, when the television device 2 requests confirmation of the linked state from the television gateway 5 via the TV cloud 3 at the time of step S119 (steps S151 and S152), the television gateway 5 transmits information indicating that the linkage is not completed to the television device 2 (steps S153 and S154).

[0202] When user information is not registered in the content providing server 4, user registration processing is performed between the user terminal 1050 and the content providing server 4 (step S121). Here, the user registration processing is processing for registering a user ID and a password, which are information for logging in to the content providing server 4, or registering user attribute information.

[0203] Subsequently, the user terminal 1050 requests login to the content providing server 4, and the content providing server 4 responds 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>}

[0204] When the user terminal 1050 receives the above response, it makes a redirect indicating a cooperation instruction to the TV gateway 5 (step S123). Note that the user terminal 1050 may transmit the above authorization code to the TV gateway 5.

[0205] When the acquisition unit 512 of the TV gateway 5 receives a redirect indicating a cooperation instruction, the TV gateway 5 identifies the manufacturer based on the TC-ID included in the state information acquired from the user terminal 1050. That is, the TV gateway 5 assigns a manufacturer (step S124).

[0206] Then, in step S125, the transmission unit 513 of the TV gateway 5 makes a token request by transmitting an authorization code to the destination TV cloud 3 (step S125).

[0207] The information transmitted at the time of the token request is, for example, configured as follows. 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> }

[0208] The generation unit 314 of the TV cloud 3 refers to the DB in the storage unit 311, and authenticates by determining whether there is information for identifying the content providing server 4 (for example, information included in the state information) and information corresponding to the authentication code acquired by the acquisition unit 312. When there is information for identifying the content providing server 4 and information corresponding to the authentication code acquired by the acquisition unit 312 in the DB of the storage unit 311, the generation unit 314 generates a token (first token). Further, the generation unit 314 further associates the first token with the information having the information for identifying the content providing server 4 and the authentication code acquired by the acquisition unit 312 in the above DB.

[0209] 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.

[0210] Specifically, the transmission unit 313 of the TV cloud 3 sends the OAuth2 Token Response as a token to the TV gateway 5. The OAuth2 Access Token Response of this response is configured as follows. Response {"access_token”: <access token>, "token_type”: "Bearer”, "expires_in”: 3600, "refresh_token”: <refresh token>}

[0211] When the TV cloud 3 accesses the TV gateway 5, an access_token shall be attached. expires_in is the expiration period (in seconds) of the access_token. It shall be memorized together with the time when it becomes invalid upon receiving the access_token, and this access_token shall be used repeatedly until then. The refresh_token shall be secretly stored by the content providing server 4. This is because, for security reasons, simply placing it in local storage is not good. When issuing the access_token and refresh_token by each manufacturer, the TV manufacturer can be identified by attaching an identifier for identifying the TV manufacturer at the beginning.

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

[0213] The information transmitted at the time of the token request has, for example, the following configuration. Authorization: "Basic” + Base64(TG-ID + ":” + <client_secret>) Request { grant_type: "authorization_code”, code : <code>(Approval Code), state : <string>(state information), redirect_uri: <TGW Endpoint>, client_id: <tg-id> }

[0214] Based on the authorization code obtained from the TV game gateway 5, the content providing server 4 identifies the user ID corresponding to the authorization code. Then, the content providing server 4 generates a second token, which is a token based on the user ID.

[0215] In step S128, the content providing server 4 sends the generated second token to the TV game gateway 5. Note that the content providing server 4 may store the second token, the user ID, and the user attribute information in association with each other.

[0216] Specifically, the content providing server 4 sends the OAuth2 Token Response as a token to the TV game gateway 5. The OAuth2 Access Token Response of this response is configured as follows. {"access_token”: <access token>, "token_type”: "Bearer”, "expires_in”: 3600, "refresh_token”: <refresh token>}

[0217] The acquisition unit 512 of the TV game gateway 5 acquires the second token from the content providing server 4. Then, the transmission unit 513 of the TV game gateway 5 sends the second token to the content providing server 4 and requests user information from the content providing server 4 (step S129).

[0218] The information transmitted at the time of the user information request has, for example, the following configuration. Authorization: "Bearer” + <access token>)

[0219] The content providing server 4 searches for the user ID and the user's attribute information corresponding to the second token acquired from the TV gateway 5, and transmits this information as a response to the TV gateway 5 (step S130). Thereby, the acquisition unit 512 of the TV gateway 5 acquires the user ID and the user's attribute information. The information of the response is configured as follows. Response {"user_id”: <ur-id>(User ID on the site of the content providing server 4), "Preference”: <Current user attributes> (user's date of birth, gender, postal code, purchase history, etc.)}

[0220] In step S131, the content providing server 4 transmits the PF-ID and requests device information. The information transmitted at the time of the device information request has, for example, the following configuration. Authorization: "Basic” + Base64(PF-ID + ":” + <client_secret>)

[0221] When the acquisition unit 512 of the TV gateway 5 receives a device information request from the content providing server 4, the transmission unit 513 of the TV gateway 5 transmits the first token corresponding to the second token transmitted in step S127 to the TV cloud 3 and requests device information (step S132). The information transmitted at the time of the device information request has, for example, the following configuration. Authorization: "Bearer” + <access token>)

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

[0223] 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 the information of the device corresponding to the HA-ID. Examples of the response are as follows. Response { ·"device_id”: <ha-id>(HA-ID) · "model": <model name> (Model of the television device 2, i.e., information such as the inch of the display screen and pixel count information such as 2K, 4K, 8K, etc.) [[ID=4}}

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

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

[0226] After step S134, when the television device 2 requests to confirm the cooperation state with the television gateway 5 via the TV cloud 3 (steps S136, S137), the television gateway 5 transmits information indicating that the cooperation is completed (information for identifying the content providing server 4 that has been cooperated, etc.) to the television device 2 (steps S138, S139). Also, the television gateway 5 notifies the IFA-ID to the content providing server 4 (step S140).

[0227] Also, when the IFA-ID is updated in 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).

[0228] Next, the disconnection process will be described using the flowchart shown in FIG. 18. FIG. 18 is a flowchart showing the disconnection process. The television apparatus 2 makes a disconnection request to the TV cloud 3 in response to a user operation (step S161). The TV cloud 3 makes a disconnection request to the TV gateway 5 in response to the disconnection request from the television apparatus 2 (step S162). In steps S161 and S162, the television apparatus 2 or the TV cloud 3 may transmit the IFA-ID together with the disconnection request.

[0229] The TV gateway 5 notifies the content providing server 4 of the disconnection request (step S163). The content providing server 4 deletes the generated second token. The TV gateway 5 deletes the binding information and notifies the TV cloud 3 that the deletion has been performed (step S164). The TV cloud 3 notifies the television apparatus 2 that the binding information has been deleted (step S165). Also, the TV cloud 3 may delete the first token. Further, the content providing server 4 notifies the TV gateway 5 that the connection has been cancelled (step S166), and the TV gateway 5 notifies the TV cloud 3 that the connection has been cancelled (step S167).

[0230] Next, the procedure for cancelling the connection via the operation of the user terminal 1050 will be described with reference to FIG. 19. FIG. 19 is a flowchart showing the procedure for cancelling the connection via the operation of the user terminal 1050.

[0231] The process starts with a scenario where the user operates a remote control or the like of the television apparatus 2 and designates the content providing server 4 with which the user wants to cancel the connection with the smartphone 1 on a so-called portal screen.

[0232] Step S180 in FIG. 19 is the same as Step S1 in FIG. 7 and Step S12 in FIG. 11. In Step S180, the television apparatus 2 transmits the PF-ID corresponding to the content providing server 4 designated by the user to the TV cloud 3.

[0233] In Step S181, the TV cloud 3 sends, as a response, a QR code including the URL of the television gateway 5 and a URL authentication code to the television apparatus 2. The QR code includes the URL of the television gateway 5 and the following time-limited authentication code.

[0234] {"code”:<authorization code> (authentication code), "state”:HEX(JSON.stringify({"tcid”; <tc-id>,"pfid”; <pf-id>,"salt”;<random string>})+hash)(state information)}

[0235] The URL authentication code is information that includes URL information for identifying the TV 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 part for discriminating the manufacturer of the television apparatus 2 and a part for discriminating the television apparatus 2. Further, the part for discriminating the television apparatus 2 included in the authentication code is a random value. Also, the TV cloud 3 may associate the time when this value was transmitted to the television apparatus 2 as information in the DB of the storage unit 311. The state information may include information in which the manufacturer's TC-ID and the PF-ID of the video platform are encoded.

[0236] An example of the information of the URL authentication code is as follows. https: / / XXXXXXX YYYYYYYYY In the X part, the URL of the TV gateway 5 is included, and in the Y part, the OAuth2 authorization code is included. In the authorization code part, information that can identify the manufacturer and the TV is included. Either one of the information that can identify the manufacturer and the television apparatus 2 may be used. The transmission format of the URL authentication code may be in any format as long as the above information is included. Note that the state information may be included in the Y part.

[0237] When the acquisition unit 243 of the television apparatus 2 acquires the URL authentication code from the TV cloud 3, the display control unit 244 optically displays and outputs the content of the URL authentication code as an image or video on the video display unit 233. Note that the display form by the display control unit 244 may be a QR code, a barcode, text, etc., as long as the information included in the URL authentication code can be optically displayed and output as an image or video. Also, in the first embodiment and the second embodiment, a QR code is described, but it is not limited to the QR code in the same manner as in this embodiment.

[0238] Also, similar to step S3 in FIG. 7 and step S23 in FIG. 11, in step S182, the user terminal 1050 reads the information of the URL authentication code optically displayed on the video display unit 233 from the image information optically captured by the imaging means by the URL authentication code reading function. Thereby, the user terminal 1050 acquires the URL of the TV gateway 5, the authentication code, and the like. The authentication code portion is configured as a time-limited authentication code as follows. "code” : <authorization code>, "state” : <string> / / Random number

[0239] In step S183, when 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 make an authentication request. Note that the state information includes the TC-ID and PF-ID as described above.

[0240] The information transmitted at the time of the authentication request is as follows. "code” : <authorization code>, "state” : <string> / / Random number

[0241] 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-formatted screen including a cooperation cancellation button indicating a cooperation cancellation instruction to the user terminal 1050. The HTML may include a URL and parameters for accessing the OAuth2 Authorization Endpoint of the PF-ID.

[0242] The user terminal 1050 acquires the above HTML-formatted screen. Then, when the cooperation cancellation button is pressed by a user operation on the user terminal 1050 (step S185), an authorization request is made to the content providing server 4 which is a video platform. Also, the content providing server 4 receives the authorization request and transmits information to the effect of responding thereto to the user terminal 1050 (step S186).

[0243] The information transmitted at the time of the above authorization request has, for example, the following configuration. Authorization: "Basic ” + Base64(<client_id> + ":” + <client_secret>)Request { "response_type”:"code” "code”:<authorization code> (authentication code) "redirect_uri”:<TGW Endpoint>(endpoint of the TV gateway 5) "client_id”: <tg-id>(ID of the TV gateway 5) "scope”: <VPF provided> (Token authentication scope) "state”: HEX(JSON.stringify({"tcid”; <tc-id>,"pfid”; <pf-id>,"salt”;<random string>})+hash)(state information) }

[0244] In addition, when the television device 2 requests confirmation of the linked state from the television gateway 5 via the TV cloud 3 at the time of step S185 (steps S251 and S252), the television gateway 5 transmits information indicating that they are linked to the television device 2 (steps S253 and S254).

[0245] Subsequently, the user terminal 1050 requests to log in to the content providing server 4, and the content providing server 4 responds 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>}

[0246] When the user terminal 1050 receives the above response, it makes a redirect indicating a cooperation instruction to the TV gateway 5 (step S189). Note that the user terminal 1050 may transmit the above authorization code to the TV gateway 5.

[0247] Then, in step S72, the transmission unit 513 of the TV gateway 5 makes a token request by transmitting an authorization code to the destination TV cloud 3 (step S190).

[0248] The information transmitted at the time of the token request is, for example, configured as follows. 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> }

[0249] The generation unit 314 of the TV cloud 3 refers to the DB of the storage unit 311 and authenticates by determining whether there is information for identifying the content providing server 4 (for example, information included in the state information) and information corresponding to the authentication code acquired by the acquisition unit 312. When the generation unit 314 refers to the DB of the storage unit 311 and there is information for identifying the content providing server 4 and information corresponding to the 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).

[0250] Specifically, the transmission unit 313 of the TV cloud 3 sends the OAuth2 Token Response as a token to the TV gateway 5. The OAuth2 Access Token Response of this response is configured as follows. Response {"access_token”: <access token>, "token_type”: "Bearer”, "expires_in”: 3600, "refresh_token”: <refresh token>}

[0251] When the TV cloud 3 accesses the TV gateway 5, it attaches the access_token. The expires_in is the valid period (seconds) of the access_token. When receiving the access_token, it stores the time when it becomes invalid together, and repeatedly uses this access_token until then. The refresh_token is secretly stored by the content providing server 4. This is because it is not good to simply place it in local storage for security reasons. When issuing the access_token and the refresh_token by each manufacturer, the TV manufacturer can be identified by attaching an identifier for identifying the TV manufacturer at the beginning.

[0252] 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 an authorization code and requests a token from the content providing server 4 (step S192).

[0253] The information transmitted at the time of the token request has, for example, the following configuration. Authorization: "Basic” + Base64(TG-ID + ":” + <client_secret>) Request { grant_type: "authorization_code”, code : <code>(Approval Code), state : <string>(state information), redirect_uri: <TGW Endpoint>, client_id: <tg-id> }

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

[0255] Specifically, the content providing server 4 sends the OAuth2 Token Response as a token to the television gateway 5. The OAuth2 Access Token Response of this response is configured as follows. {"access_token”: <access token>, "token_type”: "Bearer”, "expires_in”: 3600, "refresh_token”: <refresh token>}

[0256] 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).

[0257] The information transmitted at the time of the user information request is, for example, configured as follows. Authorization: "Bearer” + <access token>)

[0258] 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 information of this response is configured as follows. Response {"user_id”: <ur-id>(User ID on the site of the content providing server 4), "Preference”: <Current user attributes> (user's date of birth, gender, postal code, purchase history, etc.)}

[0259] The transmission unit 513 of the TV gateway 5 transmits the first token to the TV cloud 3 and requests device information (step S196). The information transmitted at the time of the device information request has, for example, the following configuration. Authorization: "Bearer” + <access token>)

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

[0261] 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 the information of the device corresponding to the HA-ID. Examples of the response are as follows. Response { ·"device_id”: <ha-id>(HA-ID) · "model": <model name> (model of the television device 2, i.e., information such as the number of inches of the display screen and pixel count information such as 2K, 4K, 8K, etc.) [[ID=4}}

[0262] The TV gateway 5 deletes the binding information and notifies the content providing server 4 of the deletion (step S198). Note that the TV gateway 5 may notify the TV cloud 3 of the deletion of the binding information.

[0263] When the television device 2 requests confirmation of the cooperation status from the TV gateway 5 via the TV cloud 3 after step S198 (steps S199, S200), the TV gateway 5 transmits information indicating that they are not in cooperation to the television device 2 (steps S201, S202).

[0264] In the above embodiment, the case of displaying campaign information when displaying the program guide has been described. However, when displaying an advertisement on the screen at a specified timing during program broadcasting via the network (a program with linear delivery of video content), campaign information may be displayed.

[0265] For example, campaign information may be displayed using a clickable advertisement as shown in FIG. 20. FIG. 20 is an example of clickable advertisement information. This advertisement information includes information indicating an array of Objects of the advertisement information (ad_list), information indicating the advertisement type (ad_type), information indicating the URL of the advertisement image (img_url), etc.

[0266] In the above-described embodiment, in the process of the flowchart shown in FIG. 17, the case where the TV gateway 5 requests user information from the content providing server 4 and obtains a UR-ID from the content providing server 4 has been described, but it is not limited to this. For example, FIG. 21 shows a modified example of the flowchart of FIG. 17. Descriptions of parts similar to the process described in FIG. 17 are omitted. Instead of the content providing server 4 providing a UR-ID in step S128 or S130 shown in FIG. 21, the TV gateway 5 may issue a temporary UR-ID in step S118 and include the parameter in the value of "state" included in the HTML-formatted code. In this case, in step S120, the user terminal 1050 transmits this value to the content providing server 4. Also, in the flowchart of FIG. 12, as described above, the TV gateway 5 may issue a temporary UR-ID.

[0267] The TV gateway 5 according to the present embodiment stores campaign information and transmits the campaign information to the television apparatus 2 at a predetermined timing such as the timing when the television apparatus 2 displays a program guide. The campaign information has an advertisement information part 350 including information indicating the type of advertisement display and information indicating the advertisement content.

[0268] Also, the TV gateway 5 obtains an authentication code from the user terminal 1050, transmits the authentication code to the TV cloud 3 of the transmission destination specified based on the authentication code, obtains a first token from the TV cloud 3, and obtains a second token from the content providing server 4. Then, the TV gateway 5 transmits the second token to the content providing server 4 to obtain a user ID, and transmits the first token to the TV cloud 3 to obtain the ID of the television apparatus 2 (for example, HA-ID). In this way, the TV gateway 5 can associate the user ID with the ID of the television apparatus 2 by obtaining the user ID from the content providing server 4 and obtaining the ID of the television apparatus 2 from the TV cloud 3.

[0269] In this case, since the TV gateway 5 stores the user ID and the ID of the television device 2 in association with each other, the TV cloud 3 does not need to manage the user ID, and the information management burden on the TV cloud 3 can be reduced. Also, since the TV 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 TV gateway 5, and the processing burden on the content providing server 4 can also be reduced. That is, the TV gateway 5 can appropriately execute the process of associating the identifier of the receiver (the ID of the television device 2) with the identifier of the terminal (the user ID of the user terminal 1050). Also, the TV gateway 5 can promote the process of associating the ID of the television device 2 with the user ID of the user terminal 1050 by outputting the campaign information. Also, since the TV gateway 5 has advertisement information including information indicating the type of advertisement display and information indicating the advertisement content in the campaign information, the television device 2 can further promote the process of associating with the user ID of the user terminal 1050 by switching the display mode according to the type of advertisement display and outputting the advertisement information. Also, the TV gateway 5 can include a plurality of pieces of advertisement information in the campaign information, so that the television device 2 can sequentially output a plurality of advertisements.

[0270] Also, after the TV gateway 5 associates the ID of the television device 2 with the user ID of the user terminal 1050, it transmits the IFA-ID to the content providing server 4. Thereby, the TV gateway 5 can provide information that can identify the television device 2 without disclosing the ID of the television device 2 to the content providing server 4.

[0271] Although some embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. For example, the television apparatus in the above embodiment may be an electronic apparatus that does not include a display means, such as a set-top box or a recorder, and has a receiving function of outputting a video signal to an external display device. Further, these novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalent scope thereof. For example, among the image icons displayed on the user terminal, for the image icons that can be enlarged and displayed on the television apparatus, a button for instructing the enlarged display on the television apparatus may be provided on or near the image icon, or the color, shape, and display form for visually recognizing the image icon that can be enlarged and displayed may be changed so as to be distinguishable from other image icons that cannot be enlarged and displayed. Further, when an instruction for enlarged display is given from the user terminal to the television apparatus, or during the display process on the television apparatus, an audio notification may be made via the user terminal or the television apparatus.

Description of Reference Numerals

[0272] 1…Smartphone, 2…Television apparatus, 3…TV cloud, 4…Content providing server, 5…Television gateway, 6…Measurement server, S…Information cooperation system < / string> < / code> < / string> < / state> < / string> < / string> < / string> < / code> < / string> < / state> < / string> < / string> It should be noted that there seems to be an error in the original text at "HEX(JSON.stringify({"tcid”;". It's an incomplete or incorrect JSON expression. This translation is based on the best understanding of the provided text. < / string> < / code> < / string> < / state> < / string> < / string> < / id> < / string> < / string>

Claims

1. 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: a storage unit that stores promotion information that promotes association of an identifier of the broadcast receiving device with an identifier of a terminal device of a user of the content providing device; a promotion information transmitting unit that transmits the promotion information to the broadcast receiving device; an authentication code transmission unit that transmits the authentication code to the broadcast receiving device in response to a request based on the promotion information from the broadcast receiving device; an authentication request acquisition unit that acquires, from the terminal device that has acquired the authentication code, an authentication request including the authentication code, an identifier of a content providing device, and an identifier of the server device; a link instruction acquisition unit that acquires, from the terminal device, a notification of a link instruction between an identifier of the broadcast receiving device and a user identifier of the terminal device; a first token acquisition unit that acquires a first token corresponding to the authentication code from a server device corresponding to the authentication request after acquiring the notification of the link instruction; a second token acquisition unit that acquires a second token corresponding to a user identifier of the terminal device from a content providing device corresponding to the authentication request; a broadcast receiving device identifier acquisition unit that acquires an identifier of a broadcast receiving device corresponding to the first token from the server device; a user identifier acquisition unit that acquires a user identifier of a terminal device corresponding to the second token from the content providing device; a registration unit that registers an identifier of a broadcast receiving device corresponding to the first token and a user identifier of a terminal device corresponding to the second token in association with each other; Equipped with The promotion information includes advertisement information including information indicating an advertisement display type and information indicating advertisement content. Server management device.

2. a second identifier acquisition unit that acquires a second identifier of the broadcast receiving device generated by the broadcast receiving device; The server management device of claim 1, further comprising a second identifier transmission unit that transmits the second identifier of the broadcast receiving device corresponding to the first token to a content providing device from which the second token was obtained, after the registration unit has registered in association with the identifier of the broadcast receiving device corresponding to the first token and the user identifier of the terminal device corresponding to the second token.

3. The server management device according to claim 1 , wherein the promotion information transmission unit transmits the promotion information together with program guide information.

4. The server management device according to claim 1 , wherein the promotion information transmission unit transmits the promotion information together with selectable advertising information.

5. The server management device according to claim 1 , wherein the promotion information includes a plurality of pieces of advertisement information.

Images