Server management device

Abstract

The server management device suitably performs a process of associating an identifier of the receiver with an identifier of the terminal. The server management device is capable of information transmission and reception with a plurality of server devices that store information that associates an identifier of a broadcast receiving device, an authentication code, an identifier of a content providing device, and a first token, acquires an authentication request including the authentication code, the identifier of the content providing device, and an identifier of the server device from the terminal device that has acquired the authentication code, acquires a notification of an association instruction from the terminal, acquires the first token corresponding to the authentication code from the server device corresponding to the authentication request after the notification of the association instruction has been acquired, acquires a second token corresponding to the 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.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to two Japanese patent applications filed on October 14, 2021, with application number 2021-168837 entitled "Server Management Device" and on April 7, 2022, with application number 2022-063747 entitled "Server Management Device", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to server management devices. Background Technology

[0004] In recent years, there have been technologies that enable receivers and terminals to cooperate in sending and receiving information. For example, a receiver can send information received from a website to a terminal.

[0005] Prior art literature

[0006] Patent documents

[0007] Patent Document 1: Japanese Patent No. 5898431 Summary of the Invention

[0008] As described above, in order for the receiver, the terminal, and the content providing device that provides content such as a website to cooperate in sending and receiving information, it is necessary to coordinate the identifier of the user of the terminal with the identifier of the receiver in advance, and it is desirable to perform appropriate cooperation processing.

[0009] Therefore, the technical problem to be solved by this application is to provide a server management device capable of appropriately performing processing that causes the identifier of the receiver to cooperate with the identifier of the terminal.

[0010] The server management device of the embodiment is capable of sending and receiving information with multiple server devices, which store information that associates the identifier of the broadcast receiving device, the authentication code, the identifier of the content providing device, and a first token. The server management device includes: a storage unit that stores promotion information that promotes the association of the identifier of the broadcast receiving device with the identifier of a user's terminal device; a promotion information sending unit that sends the promotion information to the broadcast receiving device; an authentication code sending unit that sends an authentication code to the broadcast receiving device based on a request from the promotion information received by the broadcast receiving device; and an authentication request acquisition unit that acquires an authentication request including the authentication code, the identifier of the content providing device, and the identifier of the server devices from the terminal device that has acquired the authentication code. The system comprises: a cooperation instruction acquisition unit, which acquires a cooperation instruction notification from the terminal device for the identifier of the broadcast receiving device and the user identifier of the terminal device; a first token acquisition unit, which, after acquiring the cooperation instruction notification, acquires a first token corresponding to the authentication code from the server device corresponding to the authentication request; a second token acquisition unit, which acquires a second token corresponding to the user identifier of the terminal device from the content providing device corresponding to the authentication request; a broadcast receiving device identifier acquisition unit, which acquires the identifier of the broadcast receiving device corresponding to the first token from the server device; a user identifier acquisition unit, which acquires the user identifier of the terminal device corresponding to the second token from the content providing device; and a registration unit, which 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. Attached Figure Description

[0011] Figure 1 This is a diagram showing an outline of the overall configuration example of the information collaboration system of the first embodiment;

[0012] Figure 2 This is a block diagram showing an example of the overall configuration of the television device according to the first embodiment;

[0013] Figure 3 This is a block diagram showing a partial configuration example of the television device according to the first embodiment;

[0014] Figure 4 This is a block diagram illustrating an example of the overall configuration of the push publishing server according to the first embodiment;

[0015] Figure 5 This is a block diagram illustrating a partial configuration example of the push publishing server according to the first embodiment;

[0016] Figure 6 This is a diagram illustrating the data structure of the data stored by the push publishing server in the first embodiment;

[0017] Figure 7This is a flowchart illustrating the overall processing in the information collaboration system of the first embodiment;

[0018] Figure 8 This is a diagram showing an outline of the overall configuration example of the information collaboration system according to the second embodiment;

[0019] Figure 9 This is a block diagram illustrating an example of the overall configuration of the common acceptance server in the second embodiment;

[0020] Figure 10 This is a block diagram illustrating a partial configuration example of the common acceptance server of the second embodiment;

[0021] Figure 11 This is a flowchart illustrating the overall processing in the information collaboration system of the second embodiment;

[0022] Figure 12 This is a flowchart illustrating the overall processing in the information collaboration system of the third embodiment;

[0023] Figure 13 This is a flowchart illustrating the overall processing in the information collaboration system of the fourth embodiment;

[0024] Figure 14-1 This is a diagram illustrating an example of promotional information in the information collaboration system of the fifth embodiment;

[0025] Figure 14-2 This is a diagram illustrating another example of information facilitation in the information collaboration system of the fifth embodiment;

[0026] Figure 15 This is a diagram used to illustrate advertising information in the fifth embodiment;

[0027] Figure 16-1 This is a flowchart illustrating the display processing of facilitating information in the information collaboration system of the fifth embodiment;

[0028] Figure 16-2 This is a flowchart illustrating another information display processing step in the information collaboration system of the fifth embodiment;

[0029] Figure 17 This is a flowchart illustrating the collaborative processing sequence in the information collaboration system of the fifth embodiment;

[0030] Figure 18 This is a flowchart illustrating the collaboration cancellation process in the information collaboration system of the fifth embodiment;

[0031] Figure 19 This is a flowchart illustrating the processing sequence of canceling collaboration via user terminal operation in the information collaboration system of the fifth embodiment;

[0032] Figure 20 This is a diagram illustrating an example of clickable advertising information in the information collaboration system of the fifth embodiment;

[0033] Figure 21 This is a flowchart illustrating the collaborative processing sequence in a modified information collaboration system.

[0034] Explanation of reference numerals in the attached figures

[0035] 1…Smartphone, 2…TV device, 3…TV cloud, 4…content provider server, 5…TV gateway, 6…measuring server, S…information collaboration system. Detailed Implementation

[0036] Hereinafter, the implementation methods (first embodiment and second embodiment) of the server device, broadcast receiving device, server management device, information collaboration system and program of this application will be described in detail with reference to the accompanying drawings.

[0037] (First Embodiment)

[0038] First, refer to Figure 1 The overall configuration example of the information collaboration system S in the first embodiment is described below. Figure 1 This diagram illustrates a general configuration example of the information collaboration system S according to the first embodiment. The information collaboration system S includes a smartphone 1 (terminal), a television device 2 (broadcast receiving device), a TV cloud 3 (server device), and a content providing server 4, which serves as a content providing device such as an EC (Electronic Commerce) website server. The TV cloud 3 can communicate with the television device 2 and the content providing server 4 via public communication lines such as the Internet. Furthermore, the smartphone 1 can wirelessly communicate with the content providing server 4 and the TV cloud 3 via a base station.

[0039] Smartphone 1 is an example of an information terminal owned by a user of television device 2. Smartphone 1 includes a communication I / F (Interface), a voice input unit (microphone), a sensor array, a display unit, a graphics controller, a touch panel controller, a CPU (Central Processing Unit), memory, a camera, and a speaker. In the first embodiment, it is envisioned that a user uses smartphone 1 to shop online.

[0040] TV Cloud 3 is a server device capable of sending and receiving data with TV device 2 via a network; it is a so-called cloud server. TV Cloud 3 can also be a server device used by the manufacturer of TV device 2, for example. Based on the viewing information (viewing information) collected from TV device 2, TV Cloud 3 provides TV device 2 with various services via the network, such as program viewing recommendations, program reservation recommendations, and product recommendations based on the viewed program content.

[0041] Content provider server 4 is a computer device used to operate an e-commerce website (online store) on the Internet. Content provider server 4 is, for example, a server device for an e-commerce platform. Content provider server 4 is a platform used to facilitate the purchase of goods and services via the network based on user (consumer) operations on terminal devices (such as smartphones 1). Alternatively, content provider server 4 can also be a video platform providing content such as animated images. For example, content provider server 4 sends product images to smartphone 1 based on operations performed on smartphone 1. Content provider server 4 pre-registers the redirect_uri in TV Cloud 3.

[0042] The following is for reference Figure 2 The following figures will illustrate the details of the components in the information collaboration system S. Figure 2 This is a block diagram showing an example of the overall configuration of the television device 2 according to the first embodiment. The television device 2 performs display control on a video display unit 233 that is larger than the display unit of the smartphone 1 (described in detail later).

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

[0044] 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 then supplied to the tuners 203a to 203g via the input terminal 202.

[0045] Tuners 203a to 203g are tuners for terrestrial digital broadcasting. They select the broadcast signal of the channel indicated by the control unit 216 (described later) from the terrestrial digital broadcast signal supplied by the input terminal 202.

[0046] However, the television device 2 may also have an input terminal for receiving satellite digital broadcast signals received by the BS / CS digital broadcast receiving antenna. The satellite digital broadcast signals are supplied to the tuner for satellite digital broadcasting via this input terminal.

[0047] The signal processing unit 207 demodulates the broadcast signal, which includes digital video signals and voice signals, from the broadcast signal supplied by tuners 203a to 203g. Furthermore, the signal processing unit 207 selectively performs prescribed digital signal processing on the video signals included in the digital broadcast signal and outputs the result to the graphics processing unit 208. Additionally, the signal processing unit 207 selectively performs desired digital signal processing on the voice signals included in the digital broadcast signal and outputs the result to the voice processing unit 209.

[0048] Multiple external input terminals 214a to 214d are connected to the signal processing unit 207. These external input terminals 214a to 214d can receive analog video and audio signals from devices such as DVD (Digital Versatile Disk) recorders. The signal processing unit 207 digitizes the analog video and audio signals input from the external input terminals 214a to 214d. Furthermore, the signal processing unit 207 performs prescribed digital signal processing on the digitized video signals and outputs them to the graphics processing unit 208. Additionally, the signal processing unit 207 performs prescribed digital signal processing on the digitized audio signals and outputs them to the audio processing unit 209.

[0049] The graphics processing unit 208 superimposes the OSD signal generated in the OSD signal generation unit 210 onto the digital video signal supplied from the signal processing unit 207 and outputs it to the video processing unit 211. The graphics processing unit 208 may also output either the digital video signal supplied from the signal processing unit 207 or the OSD signal generated in the OSD signal generation unit 210 to the video processing unit 211.

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

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

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

[0053] The control unit 216 centrally controls various operations of the television device 2, such as the reception of broadcast signals including terrestrial digital broadcast signals and satellite digital broadcast signals. Furthermore, the control unit 216 controls various parts of the television device 2 according to operation information from the operation unit 222 or operation information input from the remote control 238 via the light receiver 223.

[0054] CPU 216a controls the overall operation of the television device 2 by executing the program stored in ROM 216b. ROM 216b mainly stores the program executed by CPU 216a. RAM 216c provides a working partition when CPU 216a executes the program. Non-volatile memory 216d stores various setting information and control information of the television device 2.

[0055] The control unit 216 is connected to the card slot 217 via card I / F 225, which allows the memory card 234 to be installed and removed. Thus, the control unit 216 can send and receive various information with the memory card 234 installed in the card slot 217 via card I / F 225.

[0056] The control unit 216 is connected to the LAN terminal 226 via communication I / F 218. Therefore, the control unit 216 can send and receive various information with external devices such as the aforementioned repeater 400 and LAN-compatible HDD (Hard Disk Drive) connected to the LAN terminal 226 via communication I / F 218. However, communication I / F 218 can also be configured to connect wirelessly with external devices such as the repeater 400.

[0057] The control unit 216 is connected to the HDMI terminal 227 via the HDMI (High-Definition Multimedia Interface) I / F 221. Thus, the control unit 216 can send and receive various information with external devices connected to the HDMI terminal 227 via the HDMI I / F 221.

[0058] The control unit 216 is connected to the USB terminal 228 via the USB (Universal Serial Bus) I / F 219. Thus, the control unit 216 can send and receive various information with a storage device 237, such as a USB HDD, connected to the USB terminal 228, via the USB I / F 219.

[0059] Storage device 237 may include, for example, HDD or SSD (Solid State Drive), configured to record digital signals received by television device 2 as video recording data. However, storage device 237 may also be built into television device 2.

[0060] Figure 3 This 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 ( Figure 2 The ROM 216b, RAM 216c, non-volatile memory 216d, storage device 237), and functional modules generated by the CPU 216a as a result of executing the program stored in the storage unit 241, namely the sending unit 242, the acquiring unit 243, and the display control unit 244.

[0061] The transmitting unit 242 transmits various information to external devices. The acquiring unit 243 acquires various information from external devices or reads various information stored in the storage unit 241.

[0062] The display control unit 244 performs display processing to display various information on the video display unit 233. For example, the display control unit 244 causes the video display unit 233 to display an image based on an image display request from the smartphone 1 (described in detail later).

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

[0064] Communication I / F 301 is an interface for communicating with external devices. Operation unit 302 includes input devices such as a keyboard and mouse, and display devices such as a monitor.

[0065] Storage device 305 includes, for example, HDD or SSD, for storing various information. CPU 303 controls the various components of TV Cloud 3 by executing various programs. Memory 304 includes ROM, RAM, etc., for storing various programs and data used in the various calculations performed by CPU 303.

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

[0067] Storage unit 311 stores programs executed by CPU 303 and a database (DB). Here, an example of the data structure of the DB is provided. Figure 6 To illustrate. For example Figure 6As shown, the database stores information including the TVID, authentication code, EC server ID, and token. Additionally, the database may also contain attribute information (such as the TV model) of the television device 2 corresponding to that TVID, along with the TVID.

[0068] TVID is information that identifies television device 2. The authentication code is a code needed to obtain the token described later. EC Server ID is information that identifies content provider server 4. That is, it is the ID of the EC website server, etc. The token is information used for authentication. Back Figure 5 The acquisition unit 312 acquires various information from external devices. The transmission unit 313 transmits various information to external devices. The generation unit 314 performs information generation operations on the database.

[0069] Next, the processing flow of each component in the information collaboration system S will be explained. Figure 7 This is a flowchart illustrating the overall processing in the information collaboration system S of the first embodiment. Here, we envision a scenario where a user operates a remote control or similar device such as a television device 2, and in a so-called entry screen (a screen for collaborating with EC websites, etc.), the user begins specifying an EC website they wish to collaborate with on their smartphone 1. Furthermore, Figure 7 The processing of the smartphone 1 shown can also be performed by an application installed on the smartphone 1.

[0070] As described above, in the television device 2, if the user specifies an EC website, in step S1, the transmitting unit 242 of the television device 2 sends the information of the EC website (such as the EC website ID, the EC website URL, etc.) and the identifier of the television device 2, i.e., the TVID, to the TV cloud 3. In this way, the transmitting unit 242 sends information related to the image providing device, i.e., the content providing server 4, that provides images from the EC website to the TV cloud 3.

[0071] The acquisition unit 312 of TV Cloud 3 acquires information about the EC website and the TVID from the television device 2. The generation unit 314 of TV Cloud 3 generates an authentication code and stores the information, including the TVID, the EC server ID (identifying the content provider server 4 of the EC website), and the authentication code, in the database of the storage unit 311. Additionally, the generation unit 314 generates a QR code (registered trademark) based on the authentication code and the access address (URL) of the EC website. Furthermore, the QR code is just one example; other display information may also be used. That is, other forms of display information capable of transmitting the authentication code and the access address information of the EC website may also be used. The authentication code may also include parts for identifying the manufacturer and parts for identifying the television device 2.

[0072] In step S2, the sending unit 313 of TV Cloud 3 sends the QR code to the requesting television device 2. Based on the request from the television device 2, a QR code containing a URL serving as the access address to the EC website and an authentication code is sent.

[0073] The acquisition unit 243 of the television device 2 acquires a QR code from the TV cloud 3. Thus, the acquisition unit 243 of the television device 2 acquires access information, i.e., a QR code, based on an authentication code and a URL serving as the access address of the aforementioned EC website. The display control unit 244 of the television device 2 displays the QR code on the video display unit 233. Thus, the display control unit 244 displays and outputs the QR code.

[0074] In step S3, smartphone 1 reads the QR code displayed on video display unit 233 using a QR code reading function implemented by a camera or similar device. Thus, smartphone 1 obtains the URL and authentication code of the EC website. In step S4, if smartphone 1 has obtained the URL and authentication code of the EC website, it accesses content providing server 4 based on the URL and sends the authentication code.

[0075] If the content provider server 4 obtains the authentication code from the smartphone 1, in step S5, it sends the authentication code along with information identifying the content provider server 4 to the TV cloud 3 to request authentication. Additionally, the acquisition unit 312 of the TV cloud 3 acquires the authentication code along with information identifying the content provider server 4. Thus, the acquisition unit 312 of the TV cloud 3 acquires the authentication code sent from the content provider server 4.

[0076] The generation unit 314 of TV Cloud 3 determines, by referring to the database of storage unit 311, whether information corresponding to the information and authentication code of the content providing server 4 obtained by acquisition unit 312 exists, and performs authentication accordingly. If information corresponding to the information and authentication code of the content providing server 4 obtained by acquisition unit 312 exists, the generation unit 314 generates a token using known technology. Furthermore, the generation unit 314 establishes a correspondence between the token and the information in the database containing the information and authentication code of the content providing server 4 obtained by acquisition unit 312. The information further includes the TVID of the requesting television device 2.

[0077] Therefore, the generation unit 314 generates corresponding information that establishes a correspondence between the television device 2 corresponding to the authentication code and the token based on the authentication code.

[0078] In step S6, the sending unit 313 of TV Cloud 3 sends the token generated by the generation unit 314 to the content providing server 4. Thus, the sending unit 313 sends the token based on the authentication code to the content providing server 4. The content providing server 4 stores information that establishes a correspondence between the token and the user ID of the smartphone 1 from which the authentication code was sent.

[0079] In step S7, smartphone 1 logs into content provider server 4 and accesses the EC website. As a result, smartphone 1 displays the EC website screen. Here, the user of smartphone 1 selects an instruction indicating a television display request for the specified link destination on the EC website screen. In step S8, smartphone 1, based on this selection, sends the URL of the link destination to content provider server 4, thereby making a television display request (TV display request). Content provider server 4 obtains both the television display request and the URL of the image display object from smartphone 1.

[0080] In step S9, the content providing server 4 sends a token corresponding to the requesting smartphone 1 and the URL of the image display object to the TV cloud 3, and makes a display request. The acquisition unit 312 of the TV cloud 3 acquires the token and URL sent by the content providing server 4. Thus, the acquisition unit 312 acquires the token sent by the content providing server 4 and the URL of the access address of the image of the display object requested from the smartphone 1.

[0081] In step S10, TV Cloud 3 refers to the DB of storage unit 311 to determine the TVID corresponding to the token obtained by acquisition unit 312. Then, the sending unit 313 of TV Cloud 3 sends the URL of the access address of the image of the display object to the television device 2 corresponding to the TVID.

[0082] The acquisition unit 243 of the television device 2 acquires the URL of the access address of the image of the display object. Furthermore, the transmission unit 242 of the television device 2 accesses the content providing server 4 based on this URL, thereby the acquisition unit 243 acquires the image based on the access address of the image of the display object from the content providing server 4. Then, the display control unit 244 of the television device 2 displays the image acquired by the acquisition unit 243 on the video display unit 233.

[0083] In the first embodiment, TV Cloud 3 generates corresponding information between the television device 2 corresponding to the authentication code and the token based on the authentication code. If it obtains the token and the access address of the image of the display object requested from the smartphone 1 from the content provider server 4, it notifies the television device 2 of the access address of the image, thereby enabling the television device 2 to display the image corresponding to the request from the smartphone 1. Thus, TV Cloud 3 enables the television device 2, which displays a larger screen than the smartphone 1, to display the image requested by the smartphone 1.

[0084] Furthermore, the television device 2 outputs access information including the access address and authentication code to the content providing server 4, obtains the access address of the image of the display object requested from the smartphone 1 from the TV cloud 3, and displays the image on the video display unit 233. Thus, the television device 2 enables the video display unit 233, which displays a larger image than the smartphone 1, to display the image requested by the smartphone 1.

[0085] (Second Implementation)

[0086] The information collaboration system S of the second embodiment differs from that of the first embodiment in that the TV cloud 3 varies for each manufacturer of the television device 2. That is, the information collaboration system S of the second embodiment has multiple TV clouds 3.

[0087] Here, an example of the overall configuration of the information collaboration system S in the second embodiment will be described. Figure 8 This is a diagram showing a summary of the overall configuration of the information collaboration system S according to the second embodiment. Furthermore, for configurations identical to those in the first embodiment, the same reference numerals are used, and descriptions are omitted. Figure 8 As shown, the information collaboration system S has multiple TV clouds 3 (TV cloud 3a, TV cloud 3b). TV cloud 3b can connect to a television set (not shown) of a manufacturer associated with the TV cloud 3b, i.e., a television device 2.

[0088] Reference numeral 2 in the attached figure represents a television set. Reference numeral 3 represents a TV cloud, which acts as a so-called push and distribution server. The TV cloud 3 is a server belonging to the television set manufacturer that produces the television set 2 and provides various services such as program viewing, program reservation recommendations, and product recommendations based on the viewed program content to the television set 2 via the network, based on the viewing information collected from the television set 2.

[0089] Additionally, reference numeral 5 in the attached diagram refers to the TV gateway, which serves as a common receiving server. The TV gateway 5 is a server for a common website of TV device manufacturers, used to integrate the TV clouds 3 of multiple TV manufacturers and connect them to E-commerce (EC). The information collaboration system S has a TV gateway 5 (server management device) capable of sending and receiving information with these multiple TV clouds 3 via a network. Furthermore, the TV gateway 5 can also send and receive information with a measurement server 6 via a network, which performs measurement processing for statistical advertising display results. The TV gateway 5 is a cloud server that unites the various manufacturers. That is, the TV gateway 5 is a server used to integrate the TV clouds 3 of multiple TV manufacturers and connect them to a content provider server 4. The TV gateway 5 issues client certificates (client_id, client_secret) to the content provider server 4.

[0090] In addition, a random key is pre-defined between TV Cloud 3 and TV Gateway 5 and is set in x-api-key. The x-api-key exchanged between TV Gateway 5 and Content Provider Server 4 becomes the universal key (pass-key).

[0091] In the attached diagram, reference numeral 4 indicates a content provider server, such as an EC website server. Content provider server 4 is the server for the EC platform. For users, i.e., consumers, it serves as the platform for purchasing goods and services. Furthermore, content provider server 4 pre-registers the redirect_uri in the TV gateway 5.

[0092] Reference numeral 1050 in the attached drawing refers to a user terminal. User terminal 1050 is a terminal having an application for connecting the television device 2 to user terminal 1050, and an optical reading device such as a camera. As an example of user terminal 1050, a smartphone 1 is used. In the first embodiment, user terminal 1050 is described as smartphone 1, but it is not limited to smartphones. User terminal 1050 can be a PC, tablet computer, or any terminal that meets the conditions. Furthermore, these terminals can replace the smartphone shown in the first embodiment.

[0093] Figure 9 This is a block diagram illustrating an example of the overall configuration of the television gateway 5 according to the second embodiment. (As shown...) Figure 9 As shown, the TV gateway 5 includes a communication I / F 501, an operation unit 502, a CPU 503, a memory 504, and a storage device 505.

[0094] Communication I / F 501 is the interface used for communication between external devices. Operation unit 502 includes input devices such as a keyboard and mouse, and display devices such as a monitor.

[0095] Storage device 505 includes, for example, HDD or SSD, for storing various information. CPU 503 controls various components of TV gateway 5 by executing various programs. Memory 504 includes ROM, RAM, etc., for storing various programs and data used in various operations performed by CPU 503.

[0096] Figure 10 This 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 functional modules generated as a result of the CPU 503 executing a program stored in the storage unit 511, namely an acquisition unit 512, a transmission unit 513, and a generation unit 514.

[0097] Storage unit 511 stores programs executed by CPU 503 and DB (Data Base).

[0098] The acquisition unit 512 acquires various information from external devices. The transmission unit 513 transmits various information to external devices. The generation unit 514 performs information generation operations on the database.

[0099] Next, the processing flow of each component in the information collaboration system S of the second embodiment will be described. Figure 11 This is a flowchart illustrating the overall processing in the information collaboration system S of the second embodiment. Figure 11 The flowchart shown also envisions a scenario where a user operates a remote control for the television device 2, and in the so-called entry screen, the user begins to specify the EC website they wish to collaborate with on the smartphone 1. Furthermore, it is assumed that the authentication code and token generated by TV Cloud 3 contain information identifying the manufacturer. That is, it is assumed that TV Cloud 3 includes information identifying the device itself in the authentication code and token.

[0100] in addition, Figure 11 Step S21 due to Figure 7 Step S1 is the same, so the explanation is omitted. In step S22, the URL authentication code is sent from TV Cloud 3 to TV device 2. The URL authentication code 2010 contains information including the URL information for determining the content provider server 4, and an authentication code for authenticating between the content provider server 4 and TV Cloud 3. The authentication code may also include a part for identifying the manufacturer of TV device 2, and a part for identifying TV device 2. In addition, the part of the authentication code for identifying TV device 2 is a random value. Furthermore, TV Cloud 3 may also establish a correspondence by using the time when this value was sent to TV device 2 as information in the DB of storage unit 311.

[0101] An example of URL Authentication Code 2010 information is shown below.

[0102] https: / / XXXXXXX YYYYYYYYY

[0103] The X section contains the URL of content provider server 4, and the Y section contains the OAuth2 authorization code. The authorization code contains information that identifies the manufacturer and television set. This information could be either the manufacturer or the television set 2. The URL authentication code 2010 can be sent in any format, as long as it contains the aforementioned information.

[0104] If 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 displays the content of the URL authentication code 2010 on the video display unit 233 in an optical manner as an image or video. Furthermore, the display format in the display control unit 244 can be a QR code, barcode, text, etc., as long as it can display the information contained in the URL authentication code 2010 in an optical manner as an image or video. In addition, while the first embodiment described the information using a QR code, it is not limited to a QR code, as is the case in this embodiment.

[0105] In addition, with Figure 7 Similarly, in step S23, the user terminal 1050 reads the information of the URL authentication code 2011, which is optically displayed on the video display unit 233, from the image information optically captured by the camera using the URL authentication code reading function. Thus, the user terminal 1050 obtains the URL and authentication code of the EC website. This authentication code is a time-limited authentication code, configured as follows.

[0106] "code":<authorization code>,

[0107] "state": <string> / / Random number

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

[0109] Authentication code 2020 is the authentication code portion (<authorizationcode>) of URL authentication code 2010 and URL authentication code 2011. Authentication code 2021 is described below.

[0110] "code":<authorization code>,

[0111] "state": <string> / / Random number

[0112] In addition to the above, the Authentication Code 2020 may also include the URL information of Content Provider Server 4.

[0113] In step S25, if the content provider server 4 receives authentication code 2020, it sends authentication code 2021 to the TV gateway 5 and requests authentication. For example, the content provider server 4 sends the authentication request information to the OAuth2 token endpoint of the TV gateway 5. The information in authentication code 2021 is as follows.

[0114] Authorization:"Basic"+Base64(<client_id>+":"+<client_secret>)

[0115] Content-type: application / x-www-form-urlencoded

[0116] ·grant_type: "authorization_code"

[0117] • code: <authorization code> (authentication code)

[0118] • redirect_uri: The entry point for returning to the EC website of content provider server 4, and the address pre-registered in TV gateway 5.

[0119] • client_id: An identifier assigned to each EC website of content provider server 4. This identifier is pre-registered in TV gateway 5.

[0120] The client_secret is assigned by TV Gateway 5 to each website of Content Provider Server 4 based on client_id. TV Gateway 5 redirects websites based on the manufacturer's extension of the website code.

[0121] In step S26, the transmitting unit 313 of the TV gateway 5 refers to the obtained authentication code 2021 and the information identifying the manufacturer contained in the authentication code 2021 to determine the TV cloud 3 as the destination for transmission. Specifically, the transmitting unit 313 of the TV gateway 5 confirms the authorization code, i.e., the authentication code, to determine which TV cloud 3 it is.

[0122] Then, in step S27, the transmitting unit 313 of the TV gateway 5 performs authentication by sending an authentication request 2022 to the TV cloud 3, the destination of the transmission. In this way, the transmitting unit 513 of the TV gateway 5 sends the authentication request 2022 to the TV cloud 3, the destination of the transmission, which is determined based on the Authorization_code (authentication code) of the authentication code 2021. The information in the authentication request 2022 sent by the transmitting unit 313 of the TV gateway 5 is the same as the information in the authentication code 2021 obtained from the content provider server 4. Examples of other authentication request 2022 information include the following.

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

[0124] Authorization:"Bearer"+<access_token>

[0125] TV Cloud 3's acquisition unit 312 acquires the authentication code recorded in URL authentication code 2010 along with the information of the identification content providing server 4.

[0126] The generation unit 314 of TV Cloud 3 determines, by referring to the database of the storage unit 311, whether information corresponding to the information and authentication code of the identification content providing server 4 obtained by the acquisition unit 312 exists, and then performs authentication. If information corresponding to the information and authentication code of the identification content providing server 4 obtained by the acquisition unit 312 exists, the generation unit 314 generates a token 2030. Furthermore, the generation unit 314 establishes a correspondence between the token 2030 and the information in the aforementioned database containing the information and authentication code of the identification content providing server 4 obtained by the acquisition unit 312.

[0127] In step S28, the sending unit 313 of TV Cloud 3 sends the token 2030 generated by the generating unit 314 to TV Gateway 5.

[0128] Specifically, TV Cloud 3's sending unit 313 sends the OAuth2 token response as token 2030 to TV gateway 5. The OAuth2 access token response is structured as follows.

[0129] {"access_token": <access token>,

[0130] "token_type": "Bearer"

[0131] "expires_in": 3600,

[0132] "refresh_token":<refresh token>}

[0133] TV Cloud 3 includes the access token when accessing TV Gateway 5. `expires_in` is the validity period (in seconds) of the access token, stored along with the time it becomes invalid upon receipt, and reused until that time. The refresh token is secretly stored by the content provider server 4. This is because, from a security perspective, simply storing it in local storage is inadequate. When manufacturers issue access tokens and refresh tokens, they add an identifier that identifies the TV manufacturer, thus allowing for the identification of the TV manufacturer.

[0134] The acquisition unit 512 of the TV gateway 5 acquires token 2030. Then, in step S29, the TV gateway 5 sends token 2030 as token 2031 to the content provider server 4, and the content provider server 4 acquires token 2031. Alternatively, the sending unit 313 of the TV cloud 3 can also directly send the token to the content provider server 4.

[0135] Content provider server 4 stores information that establishes a correspondence between token 2031 and the user ID of the user terminal 1050, the source of the authentication code.

[0136] Then, in step S30, the content providing server 4 sends a token + user ID 2040 to the TV gateway 5 in response to the token 2031 and the user ID. Thus, the content providing server 4 is able to send the user ID of the user terminal 1050 to the TV gateway 5.

[0137] The information provided by the content provider server 4, consisting of the token and user ID 2040, is as follows.

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

[0139] Authorization:"Basic"+Base64(<client_id>+":"+<client_secret>)

[0140] Content-type: application / x-www-form-urlencoded

[0141] {grant_type:"access_token",

[0142] access_token: <access token> (information issued as an access token in step S28)

[0143] client_id: An identifier assigned to each website on content provider server 4. It is pre-registered on the manufacturer's common website.

[0144] user_id: The user ID in the website of content provider server 4.

[0145] Preference: <Current user attributes (Current user attributes: user's date of birth, gender, postal code, purchase history, etc.)>}

[0146] The acquisition unit 512 of the TV gateway 5 obtains a token and user ID 2040 from the content provider server 4. In step S31, the sending unit 513 of the TV gateway 5 determines the TV cloud 3 as the destination based on the token and user ID 2040, and sends a device ID request 2041 (TVID) to the TV cloud 3 as the destination. Furthermore, the sending unit 513 of the TV gateway 5 may also send a token when sending the device ID request 2041.

[0147] Device ID Request 2041 is a request made by TV Gateway 5 using OAuth2 access token to query the device ID (TVID) of TV from each manufacturer (TV Cloud 3), for example, the following request.

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

[0149] ·Authorization:"Bearer"+<access_token>

[0150] • x-api-key: <A random key specified by the manufacturer's common website and each manufacturer>

[0151] ·Content-type: application / json

[0152] client_id: An identifier assigned to each manufacturer's common website.

[0153] TV Cloud 3 refers to the DB of storage unit 311 to obtain the TVID corresponding to the obtained token. Additionally, TV Cloud 3 can also obtain information about the device corresponding to the obtained TVID (attribute information of the television device 2 associated with that TVID). In step S32, the sending unit 313 of TV Cloud 3 sends the TVID and other information as a device ID response 2050 to the television gateway 5. An example of the device ID response 2050 is as follows:

[0154] • "device_id": <id> (TVID assigned to TV device 2 by TV Cloud 3)

[0155] • "model": <model name> (The model of TV device 2, i.e., information such as the number of pixels, such as the screen size in inches, 2K, 4K, 8K, etc.)

[0156] In step S33, the generation unit 514 of the TV gateway 5 registers the information binding information, which is associated with the obtained TVID (device ID), user ID, and model information of the TV device 2, as DB information to the storage unit 511.

[0157] Additionally, the generation unit 514 of the TV gateway 5 generates a pass key 2051. Furthermore, in step S34, the sending unit 513 sends this pass key to the content providing server 4. This pass key contains the following information.

[0158] • "pass_key": <pass_key>, (This pass_key is used as the ID during the operation from step S44 onwards, from operation instruction 2090 to operation instruction 2093)

[0159] • "expires_in": 86400, (expires_in is a 10-day delay for returning a preference even if it cannot be prepared during the initial access.)

[0160] • "model": <model name> (This is the model information in the device ID response. For example, the model of TV device 2 includes information such as the number of pixels in the display screen (inches, 2K, 4K, 8K, etc.)

[0161] In addition, in step S35, the generation unit 514 of the TV gateway 5 stores the generated universal key in the storage unit 511.

[0162] If content provider server 4 obtains the universal key from TV gateway 5, it stores the information contained in the universal key. Specifically, it stores the following information for each user ID of the EC website.

[0163] access_token

[0164] refresh_token

[0165] ·pass_key

[0166] ·model / / TV model information for collaboration

[0167] In step S36, the user terminal 1050 logs in to the services provided by the content provider server 4 by launching the application. As a result, the smartphone 1 displays the EC website screen. The EC website screen output by the application also displays a button for connecting to the television device 2. Furthermore, in step S37, the content provider server 4 sends device information 2070 to the user terminal 1050 based on the login in step S36. The device information 2070 referred to here is any combination of one, two, or three of the device ID, user ID, and model name contained in the general key 2051.

[0168] The user of smartphone 1 selects a button to connect to television device 2 for the link destination on the EC website screen. In step S38, user terminal 1050 sends a television display request (TV display request 2071) by sending the URL of the link destination to content provider server 4 according to the selection.

[0169] If the content provider server 4 receives a TV display request 2071 from the user terminal 1050, then in step S39, it sends a display request 2072, which includes a token, a general key, and a URL of the link destination, to the TV gateway 5, thereby requesting a display from the TV device 2. The information in the display request 2072 is as described below.

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

[0171] Authorization:"Bearer"+<access_token>x-api-key:<pass_key>

[0172] Content-type: application / jison

[0173] {"command_type":"keycode"}

[0174] "keycode": "<common key code>"}

[0175] {"command_type":"webview",

[0176] "site": "<Website URL>",

[0177] "Template": "full"}

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

[0179] In step S40, the acquisition unit 512 uses the common key (pass_key) and information stored in the storage unit 511 to determine the access address and access source. In step S41, the sending unit 513 sends information containing a token and a URL to the TV cloud 3 based on the determined result, and makes a display request. Thus, the sending unit 513 sends the token and the access address of the image to be displayed to the TV cloud 3, the destination. Furthermore, the TV gateway 5 counts the number of accesses according to the access source and manufacturer.

[0180] The display request 2073 sent by the sending unit 513 to TV Cloud 3 includes a token, customer ID, URL, and message. An example of this information is described below.

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

[0182] Authorization: "Bearer" + <access_token> x-api-key: <random key specified by the manufacturer's common website and each manufacturer>

[0183] Content-type: application / json

[0184] {"command_type":"keycode",

[0185] "keycode":<common key code>,

[0186] "client_id":<client_id>,

[0187] "messageid:<message ID>}

[0188] {"command_type":"webview",

[0189] "site": <Website URL> (Website URL for television).

[0190] "template": "full"

[0191] "client_id":<client_id>,

[0192] "message id":<message ID>}

[0193] 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 TV device 2. In step S42, the sending unit 313 of TV Cloud 3 outputs a display request 2074 to the TV device 2 based on the identified result. Furthermore, this display request can also be replaced with a manufacturer-specific display request instruction. Additionally, TV Cloud 3 can, as needed, count the accesses of each client_id and make requests to the TV.

[0194] In step S43, the television device 2 launches its browser based on the display request, and executes JavaScript (registered trademark) through events such as onLoad and onClick to display the image at the URL destination of the display object. Additionally, the television device 2 notifies the measurement server 6 of the display operation results, identifying the service provider, user, TV manufacturer, and displayed advertisements, via notification 2080. The measurement server 6 compiles statistics on the results of advertisement displays performed by the TV cloud 3 on multiple television devices 2. Based on these statistics, the manufacturer or the owner of the TV gateway 5, or the measurement server 6, requests advertising fees from the E-commerce platform holding the content providing server 4.

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

[0196] In step S45, the content providing server 4 sends operation instructions 2091, including common key codes, to the television gateway 5 based on the operation instructions 2090 sent in step S44. Common key codes are instructions constructed in a manner corresponding to the operation buttons on the television remote control. They include numbers, crosshair cursors, volume / channel / power, color keys, function keys, media controls, and manufacturer-specific instructions. Manufacturer-specific instructions refer to instructions used independently by each manufacturer. In other words, manufacturer-specific instructions are instructions set by each manufacturer for operation unique to that manufacturer. Common key codes are key codes, in addition to manufacturer-specific instructions, used for common operations between manufacturers.

[0197] The numerical instructions are "11", "12", "0", "1", "2", "3", "4", "5", "6", "7", "8", "9", and ".".

[0198] The crosshair cursor commands are "Up", "Down", "Left", "Right", "Page Up", "Page Down", "Page Left", "Page Right", "Enter", "Exit", and "Return".

[0199] The volume / channel / power commands are "Power", "Power Off", "Power On", "Increase Volume", "Decrease Volume", "Select Channel Forward", and "Select Channel Backward".

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

[0201] The function key commands are "Electronic Program Wizard", "Initial Configuration", "Select Broadcast Type", "Input Selection", "Display Information", "Mute", "Content Menu", and "Hidden Captions".

[0202] The media control commands are "Play", "Stop", "Pause", "Replay", "Fast Forward", "Rewind", "Skip Forward", "Skip Backward", and "Record".

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

[0204] {message id:<message ID>}

[0205] If TV Cloud 3 receives operation instruction 2092 from TV gateway 5, it sends operation instruction 2093 to TV device 2 in step S48. Operation instruction 2093 is the same as or equivalent to operation instruction 2092, and is a manufacturer-specific instruction for operating the display screen of TV device 2. TV Cloud 3 replaces operation instruction 2092 with the key codes of various companies used to operate TV device 2, i.e., operation instruction 2093. Given the standardization of operation instructions for TV device 2, operation instruction 2092 can be directly used as operation instruction 2093 without conversion.

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

[0207] Figure 11 The flowchart shown illustrates the process of multiple manufacturers accessing the content provider server 4 of the platform. However, as in the TV cloud 3 of the first embodiment, manufacturers can also access the content provider server 4 individually. In this case, the TV cloud 3 combines the actions of the TV gateway 5. At this time, the information exchange between the TV cloud 3 and the TV gateway 5 is omitted.

[0208] TV gateway 5 obtains an authentication code from content provider server 4, sends the authentication code to TV cloud 3 (the destination determined by the authentication code), obtains a token and the access address of the displayed object's image from content provider server 4, and sends the token and the access address of the displayed object's image to TV cloud 3. Therefore, it can process the request without requiring content provider server 4 to determine which of the multiple TV clouds 3 to send to.

[0209] Furthermore, the programs executed in the various devices of this embodiment (user terminal 1050, television device 2, TV cloud 3, content providing server 4, television gateway 5, and measurement server 6) can be provided as installable or executable files on storage media readable by computer devices, such as CD (Compact Disc)-ROM (Read Only Memory), floppy disk (FD), CD-R (Recordable), and DVD (Digital Versatile Disk). Alternatively, the program can also be provided or distributed via a network such as the Internet.

[0210] (Third Implementation)

[0211] The information collaboration system S of the third embodiment has the same overall configuration as the information collaboration system S of the second embodiment. In the information collaboration system S of the third embodiment, the television gateway 5 obtains tokens not only from the TV cloud 3, but also from the content provider server 4, and uses these tokens to make the ID of the television device 2 collaborate with the user ID of the user terminal 1050.

[0212] also, Figure 6 The data structure stored in TV Cloud 3 is different from that shown. Specifically, TV Cloud 3 replaces... Figure 6 The TVID shown is used, while the HA-ID is stored. Additionally, instead of... Figure 6 The EC website server ID is shown, while the PF-ID is stored. HA-ID contains identification information including the company ID of the television manufacturer (TC-ID) and the device ID of the television device 2 (TV-ID). PF-ID is the company ID of the video platform. TC-ID serves as the identifier for TV Cloud 3. Additionally, PF-ID serves as the identifier for content provider server 4.

[0213] Next, the processing flow of each component in the information collaboration system S of the third embodiment will be described. Figure 12 This is a flowchart illustrating the overall processing in the information collaboration system S of the third embodiment. Figure 12 The flowchart shown also envisions a scenario where a user operates a remote control or similar device on the television device 2, and in the so-called entry screen, the user begins by specifying an EC website (e.g., a server that accepts content) that they wish to collaborate with their smartphone 1. Furthermore, it is assumed that the authentication code and token generated by TV Cloud 3 contain information identifying the manufacturer. That is, it is assumed that TV Cloud 3 includes information identifying the device itself in the authentication code and token.

[0214] in addition, Figure 12 Step S61 and Figure 7 Step S1 Figure 11 Step S12 is the same. Furthermore, in step S61, the television device 2 sends the PF-ID corresponding to the user-specified EC website (video platform) to the TV cloud 3.

[0215] In step S62, TV Cloud 3, in response, sends a QR code containing the URL of TV Gateway 5 and a URL authentication code to TV Device 2. This QR code contains the URL of TV Gateway 5 and the time-limited authentication code described below.

[0216] {"code": <authorization code> (authentication code)}

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

[0218] The URL authentication code contains information including the URL of the TV gateway 5, an authentication code for authentication between the content provider server 4 and the TV cloud 3, and state information. The authentication code may also include a portion for identifying the manufacturer of the TV device 2, and a portion for identifying the TV device 2 itself. Furthermore, the portion of the authentication code used to identify the TV device 2 is a random value. Additionally, the TV cloud 3 may establish a database (DB) in its storage unit 311 with the time when this value was sent to the TV device 2 as information. The state information may also include information encoded with the manufacturer's TC-ID and the video platform's PF-ID.

[0219] Examples of URL authentication code information are described below.

[0220] https: / / XXXXXXX YYYYYYYYY

[0221] Part X contains the URL of TV gateway 5, and part Y contains the OAuth2 authorization code. The authorization code section contains information that identifies the manufacturer and the television set. This information could be either the manufacturer or the television device 2. The URL authentication code can be sent in any format, as long as it contains the aforementioned information. Furthermore, part Y may also contain status information.

[0222] If the acquisition unit 243 of the television device 2 acquires the URL authentication code from the TV cloud 3, the display control unit 244 displays the content of the URL authentication code as an image or video in the video display unit 233 using optical means. Furthermore, the display format in the display control unit 244 can be a QR code, barcode, text, etc., as long as it can display the information contained in the URL authentication code as an image or video using optical means. In addition, while the first and second embodiments were described using QR codes, this embodiment is not limited to QR codes.

[0223] In addition, with Figure 7 Step S3 Figure 11Similarly, in step S63, the user terminal 1050 reads the URL authentication code information optically displayed on the video display unit 233 from the image information optically captured by the camera using the URL authentication code reading function. Thus, the user terminal 1050 obtains the URL and authentication code of the television gateway 5. This authentication code is a time-limited authentication code, configured as follows.

[0224] "code":<authorization code>,

[0225] "state": <string> / / Random number

[0226] In step S64, if the user terminal 1050 obtains the URL, authentication code, and status information of the TV gateway 5, it accesses the TV gateway 5 based on the URL, sends the authentication code and status information, and performs authentication. Furthermore, as described above, the status information includes TC-ID and PF-ID.

[0227] The information sent during the authentication request is as follows.

[0228] "code":<authorization code>,

[0229] "state": <string> / / Random number

[0230] In step S65, if the acquisition unit 512 of the TV gateway 5 receives the authentication code and status information, the transmission unit 513 of the TV gateway 5 sends an HTML-formatted screen, including a collaboration button indicating a collaboration instruction, to the user terminal 1050. This HTML may also include the URL of the OAuth2 Authorization Endpoint for accessing the PF-ID, and parameters.

[0231] User terminal 1050 acquires the aforementioned HTML-formatted screen. Then, if a user presses the collaboration button via user operation on user terminal 1050 (step S66), a request for approval is sent to content provider server 4, which is the video platform. Content provider server 4 receives this approval request and sends information regarding its response to user terminal 1050 (step S67).

[0232] The information sent when the above-mentioned approval requirements are required may be composed of the following components.

[0233] Authorization:"Basic"+Base64(<client_id>+":"+<client_secret>)Request

[0234] {

[0235] "response_type": "code"

[0236] "code": <authorization code> (authentication code)

[0237] "redirect_uri": <TGW Endpoint> (The endpoint of TV Gateway 5)

[0238] "client_id": <TG-ID> (ID of TV Gateway 5)

[0239] "scope": <provided by VPF> (the authentication scope of the token)

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

[0241] }

[0242] If user information is not registered in the content provider server 4, user registration processing is performed between the user terminal 1050 and the content provider server 4 (step S68). Here, user registration processing refers to the process of registering the information used to log in to the content provider server 4, namely the user ID and password, or registering the user's attribute information.

[0243] Next, user terminal 1050 sends a login request to content provider server 4, and content provider server 4 responds accordingly to the login request (step S69). As an example of this response, the following information (acknowledgment code) is output.

[0244] Response

[0245] {"code":<authorization code>,

[0246] "state": <state>}

[0247] If the user terminal 1050 receives the above response, it redirects the data to the television gateway 5 to indicate a cooperation instruction (step S70). Alternatively, the user terminal 1050 may also send the above-mentioned approval code to the television gateway 5.

[0248] If the acquisition unit 512 of the TV gateway 5 receives a redirection indicating a cooperation instruction, the TV gateway 5 determines the manufacturer based on the TC-ID contained in the status information obtained from the user terminal 1050. That is, the TV gateway 5 assigns a manufacturer (step S71).

[0249] Then, in step S72, the sending unit 513 of the TV gateway 5 makes a token request by sending an authentication code to the TV cloud 3 at the sending destination (step S72).

[0250] The information sent during the token request may be, for example, as follows.

[0251] Authorization:"Basic"+Base64(TG-ID+":"+<client_secret>)

[0252] Request Parameters

[0253] {

[0254] grant_type: "authorization_code",

[0255] code: <authorization code>

[0256] state: <string> (state information)

[0257] redirect_uri:<redirect_uri>,

[0258] client_id: <TG-ID>

[0259] The generation unit 314 of TV Cloud 3 determines, by referring to the database of the storage unit 311, whether there exists information corresponding to the information of the identification content providing server 4 obtained by the acquisition unit 312 (e.g., information contained in the status information) and the authentication code, and performs authentication accordingly. If the database of the storage unit 311 contains information corresponding to the information of the identification content providing server 4 obtained by the acquisition unit 312 and the authentication code, the generation unit 314 generates a token (first token). Furthermore, the generation unit 314 establishes a correspondence between the first token and the information in the database containing the information of the identification content providing server 4 obtained by the acquisition unit 312 and the authentication code.

[0260] In step S73, the sending unit 313 of TV Cloud 3 sends the first token generated by the generating unit 314 to TV Gateway 5.

[0261] Specifically, the sending unit 313 of TV Cloud 3 sends the OAuth2 token response as a token to TV gateway 5. The OAuth2 access token response is structured as follows.

[0262] Response

[0263] {"access_token": <access token>,

[0264] "token_type": "Bearer"

[0265] "expires_in": 3600,

[0266] "refresh_token":<refresh token>}

[0267] TV Cloud 3 includes the access token when accessing TV Gateway 5. `expires_in` is the validity period (in seconds) of the access token, stored along with the time it becomes invalid upon receipt, and reused until that time. The refresh token is secretly stored by the content provider server 4. This is because, from a security perspective, simply storing it in local storage is inadequate. When manufacturers issue access tokens and refresh tokens, they add an identifier that identifies the TV manufacturer, thus allowing for the identification of the TV manufacturer.

[0268] If the acquisition unit 512 of the TV gateway 5 acquires the first token, the sending unit 513 of the TV gateway 5 sends information containing the approval code and makes a token request to the content provider server 4 (step S74).

[0269] The information sent during the token request may be, for example, as follows.

[0270] Authorization:"Basic"+Base64(TG-ID+":"+<client_secret>)

[0271] Request

[0272] {grant_type: "authorization_code",

[0273] code: <code> (accreditation code)

[0274] state: <string> (state information)

[0275] redirect_uri:<TGW Endpoint>,

[0276] client_id: <TG-ID>

[0277] }

[0278] Content provider server 4 determines the user ID corresponding to the authentication code obtained from TV gateway 5. Then, content provider server 4 generates a token based on that user ID, namely the second token.

[0279] In step S75, the content providing server 4 sends the generated second token to the television gateway 5. Furthermore, the content providing server 4 may also establish a corresponding storage for the second token, the user ID, and the user attribute information.

[0280] Specifically, content provider server 4 sends an OAuth2 token response as a token to TV gateway 5. This OAuth2 access token response is structured as follows.

[0281] {"access_token": <access token>,

[0282] "token_type": "Bearer"

[0283] "expires_in": 3600,

[0284] "refresh_token":<refresh token>}

[0285] The acquisition unit 512 of the TV gateway 5 obtains the second token from the content provider server 4. Then, the sending unit 513 of the TV gateway 5 sends the second token to the content provider server 4 and makes a user information request to the content provider server 4 (step S76).

[0286] The information sent when requesting user information may be composed of, for example, the following.

[0287] Authorization: "Bearer"+<access token>)

[0288] Content provider server 4 retrieves the user ID and user attribute information corresponding to the second token obtained from TV gateway 5, and sends this information as a response to TV gateway 5 (step S77). Thus, the acquisition unit 512 of TV gateway 5 acquires the user ID and user attribute information. The response information is configured as follows.

[0289] Response

[0290] {"user_id": <UR-ID> (User ID in the website of content provider server 4),

[0291] "Preference": <Current user attributes> (user's date of birth, gender, postal code, purchase history, etc.)

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

[0293] Authorization:"Basic"+Base64(PF-ID+":"+<client_secret>)

[0294] If the acquisition unit 512 of the TV gateway 5 receives a device information request from the content provider server 4, the sending unit 513 of the TV gateway 5 sends the first token corresponding to the second token sent in step S74 to the TV cloud 3, and performs a device information request (step S79). The information sent during the device information request has the following composition, for example.

[0295] Authorization: "Bearer"+<access token>)

[0296] If the acquisition unit 312 of 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 TV device 2 corresponding to the HA-ID).

[0297] In step S80, the transmitting unit 313 of TV Cloud 3 sends HA-ID and other information to TV Gateway 5 as a response. The acquiring unit 512 of TV Gateway 5 acquires the HA-ID and information about the device corresponding to that HA-ID. An example of this response is as follows.

[0298] Response

[0299] {

[0300] ·"device_id":<HA-ID>(HA-ID)

[0301] • "model": <model name> (The model of TV device 2, i.e., information such as the number of pixels (inches, 2K, 4K, 8K, etc.))

[0302] In step S81, the generation unit 514 of the TV gateway 5 registers the binding information, which associates the acquired HA-ID, user ID, attribute information of the TV device 2 (i.e., model information), and PF-ID, as DB information to the storage unit 511. Furthermore, the generation unit 514 of the TV gateway 5 may further include user attribute information in the binding information.

[0303] Additionally, the generation unit 514 of the TV gateway 5 generates a universal key. Furthermore, in step S82, the sending unit 513 sends this universal key to the content providing server 4. This universal key contains the following information.

[0304] • "pass_key": <pass_key>, (this pass_key is used as an ID when performing an operation command)

[0305] • "expires_in": 86400, (expires_in is a 10-day delay for returning a preference even if it cannot be prepared during the initial access.)

[0306] • "model": <model name> (This is the model information in the device ID response. For example, the model of TV device 2 includes information such as the number of pixels in the display screen (inches, 2K, 4K, 8K, etc.)

[0307] In addition, the generation unit 514 of the TV gateway 5 stores the generated general key in the storage unit 511.

[0308] If content provider server 4 obtains the universal key from TV gateway 5, it stores the information contained in the universal key. Specifically, content provider server 4 stores the following information for each user ID of the EC website.

[0309] access_token

[0310] refresh_token

[0311] ·pass_key

[0312] ·model / / Collaborative TV model information

[0313] TV gateway 5 obtains an authentication code from user terminal 1050, sends the authentication code to TV cloud 3 (the destination determined by the authentication code), obtains a first token from TV cloud 3, and obtains a second token from content provider server 4. Then, TV gateway 5 obtains the user ID by sending the second token to content provider server 4, and obtains the ID (e.g., HA-ID) of TV device 2 by sending the first token to TV cloud 3. In this way, TV gateway 5 can establish a correspondence between the user ID and the ID of TV device 2 by obtaining the user ID from content provider server 4 and the ID of TV device 2 from TV cloud 3.

[0314] In this scenario, because TV gateway 5 stores the user ID in a corresponding manner with the ID of TV device 2, TV cloud 3 does not need to manage the user ID, thus reducing its information management burden. Furthermore, since TV gateway 5 obtains the authentication code from user terminal 1050, it is not necessary to send the authentication code from content provider server 4 to TV gateway 5, further reducing the processing burden on content provider server 4. In other words, TV gateway 5 can appropriately perform the processing that coordinates the receiver's identifier (ID of TV device 2) with the terminal's identifier (user ID of user terminal 1050).

[0315] (Fourth implementation)

[0316] The information collaboration system S of the fourth embodiment has the same overall structure as the information collaboration system S of the second embodiment. In the second embodiment, the case where the authentication code is also included in the QR code is described; however, in the information collaboration system S of the fourth embodiment, the authentication code is displayed separately as a personal identification code (PIN code).

[0317] Next, the processing flow of each component in the information collaboration system S of the fourth embodiment will be explained. Figure 13 Step S21 because of... Figure 11 Step S21 and Figure 7 Step S1 is the same, so the explanation is omitted.

[0318] In step S91, TV Cloud 3 sends a QR code containing the URL to TV device 2. Additionally, TV Cloud 3 sends a personal identification code corresponding to the authentication code to TV device 2.

[0319] Examples of URL information contained in QR codes are described below.

[0320] https: / / XXXXXXX

[0321] In section X, there is the URL for content provider server 4. The URL for sending the QR code can be in any format, as long as it contains the information described above.

[0322] If the acquisition unit 243 of the television device 2 acquires the QR code and personal identification code from the TV cloud 3, the display control unit 244 displays the QR code as an image or video on the video display unit 233 in an optical manner. Additionally, the display control unit 244 displays the personal identification code.

[0323] In step S92, the user terminal 1050 reads the URL information that is optically displayed on the video display unit 233 from the image information optically captured by the camera using the reading function.

[0324] In step S93, the user terminal 1050 starts the application (APP) and makes it capable of receiving personal identification code input.

[0325] In step S94, if a PIN code is entered through user operation, the user terminal 1050 obtains the PIN code as an authentication code. Steps S24 to S35 are respectively related to... Figure 11 Steps S24 to S35 are the same.

[0326] In the fourth embodiment, TV Cloud 3 sends a personal identification code corresponding to the authentication code to TV device 2, which displays the personal identification code. Then, the user of user terminal 1050 performs an input operation based on the personal identification code, and user terminal 1050 sends the personal identification code as an authentication code to content provider server 4.

[0327] In this case, even if the authentication code cannot be included in the QR code along with the URL, it is still possible to send the authentication code from the user terminal 1050 to the content provider server 4.

[0328] (Fifth Embodiment)

[0329] The information collaboration system S of the fifth embodiment has the same overall configuration as the information collaboration system S of the third embodiment. In the information collaboration system S of the fifth embodiment, the television gateway 5 sends campaign information as promotional information to the television device 2. This promotional information is used to promote the processing that enables the ID of the television device 2 to collaborate with the user ID of the user terminal 1050 in the information collaboration system S of the third embodiment. In the information collaboration system S, when the promotional information instructs the television device 2 to collaborate with the user ID of the user terminal 1050, the television device 2 executes the processing that enables the ID of the television device 2 to collaborate with the user ID of the user terminal 1050.

[0330] In the information collaboration system S, if television device 2 requests program schedule information, television gateway 5 receives the request via TV cloud 3. Television gateway 5 obtains program schedule composition information from content provider server 4 and sends this information to TV cloud 3. TV cloud 3 obtains the program schedule composition information and sends it back to television device 2. The program schedule composition information includes company information, channel information, program information, CM information, and VOD information.

[0331] Alternatively, in the information collaboration system S, if television device 2 requests program schedule information, television gateway 5 receives the request. Television gateway 5 obtains the program schedule structure information and sends it to television device 2. The program schedule structure information includes company information, channel information, program information, CM information, and VOD information. It should be noted that the file server implementing television gateway 5 stores the program schedule structure information. That is, television gateway 5 stores the program schedule structure information and sends the stored program schedule structure information to television device 2 according to the request for program schedule information from television device 2.

[0332] The TV gateway 5 stores promotional information and sends the promotional information according to the request from the TV device 2 when sending program schedule information.

[0333] Here, use Figure 14-1 Explain the content of the promotional information. Figure 14-1 This is a diagram illustrating an example of promotional information. The promotional information includes a typical collaborative data section 330 and a promotional collaborative data section 340.

[0334] Typically, the collaboration data section 330 includes: information (idbind) representing the object (Object) for ID collaboration data; information (img_base_url) representing the base URL that stores the URL of the image file; information (explanation_img) representing the image that describes the collaboration method; and information (explanation_img) representing the image that describes the collaboration release method.

[0335] The promotional collaboration data section 340 includes: information about the array representing the promotional information (idbind_campaign); information about the TV manufacturer representing the promotional object (tv); information about the base URL representing the URL storing the image file (img_base_url); information about the image representing the content of the promotion (campaign_img); information about the image displayed when collaboration is nearing completion (hasbound_img); information about the image representing the collaboration method (explanation_img); information about the image representing the recommended license based on IFA-ID tracking (recommend_tracking_img); information about the start date and time of the promotion (start); and information about the end date and time of the promotion (end).

[0336] Macros can also be used to set the information of the promotional collaboration data section 340 to represent images differently for each TV manufacturer. This allows for the distribution of different promotional images to multiple TV manufacturers with a simple configuration.

[0337] Additionally, using Figure 14-2 Explain the content of another promotional message. Figure 14-2 This is a diagram illustrating another example of promotional information. The promotional information includes a typical collaboration data section 330, a promotional collaboration data section 340, and one or more advertising information sections 350.

[0338] Typically, the collaboration data section 330 includes: information (idbind) representing the object (Object) for ID collaboration data; information (img_base_url) representing the base URL that stores the URL of the image file; information (explanation_img) representing the image that describes the collaboration method; and information (explanation_img) representing the image that describes the collaboration unbinding method.

[0339] The promotional collaboration data section 340 includes: information about the array representing the promotional information (idbind_campaign); information about the TV manufacturer representing the promotional object (tv); information about the base URL representing the URL storing the image file (img_base_url); information about the image representing the content of the promotion (campaign_img); information about the image displayed when collaboration is nearing completion (hasbound_img); information about the image representing the collaboration method (explanation_img); information about the image representing the recommended license based on IFA-ID tracking (recommend_tracking_img); information about the start date and time of the promotion (start); and information about the end date and time of the promotion (end).

[0340] Macros can also be used to set the information of the promotional collaboration data section 340 to represent images differently for each TV manufacturer. This allows for the distribution of different promotional images to multiple TV manufacturers with a simple configuration.

[0341] The advertising information section 350 includes: TV manufacturer arrangement information (tv) indicating the display object; ad_info unique identifier (id); advertising information (ad_info) containing information indicating the display type and content of the advertisement; display start date and time (start); and display end date and time (end).

[0342] In addition, such as Figure 14-2 and Figure 15 As shown, the advertising information includes: information indicating the type of advertisement (type); information indicating the ID of the displayed screen (place); a text message displayed when the advertisement's display type is text; a URL of the displayed image (image) displayed when the advertisement's display type is image; a URL of the animated image displayed when the advertisement's display type is movie (movie); and information indicating the duration of the advertisement's display (period). The text message, the URL of the displayed image, and the URL of the animated image mentioned above are examples of information indicating the content of the advertisement.

[0343] Figure 14-2 The promotional information shown includes: text-based advertising information section 350a; image-based advertising information section 350b; and movie-based advertising information section 350c. Television device 2 receives... Figure 14-2In the case of the promotional information shown, advertisements that display text messages, advertisements that display images, and advertisements that display animated images.

[0344] Next, use Figure 16-1 Explain the order of collaborative processing based on promotional information. Figure 16-1 This is a flowchart illustrating the display process of promotional information.

[0345] Based on the user's operation, television device 2 requests the program schedule structure information (program schedule) of the EC website specified by the user to TV Cloud 3. If television device 2 makes a request to obtain program schedule information, television gateway 5 receives the request via TV Cloud 3. Television gateway 5 obtains the program schedule structure information from content provider server 4 and sends the program schedule structure information to TV Cloud 3. TV Cloud 3 obtains the program schedule structure information and sends the obtained program schedule structure information to television device 2. Television device 2 displays the program schedule structure information (step S101). The program schedule structure information includes enterprise information, channel information, program information, CM information, and VOD information.

[0346] Television device 2 requests advertising information from television gateway 5. If television device 2 fails to obtain advertising information from television gateway 5 via TV cloud 3 (step S102: No), the process ends.

[0347] Television device 2 requests advertising information from television gateway 5. If television device 2 obtains the advertising information from television gateway 5 via TV cloud 3 (step S102: Yes), but has not completed cooperation with content provider server 4 (step S103: Yes), then television device 2 displays the advertising information along with program schedule information (step S104). As a method for determining whether cooperation with content provider server 4 has been completed, the following method exists: television device 2 maintains a log of past cooperation processing requests and makes the determination based on this log.

[0348] In the promotional information, after selecting the main theme of the recruitment advertisement, the television device 2 displays survey information (step S105). This survey receives input from users regarding their attributes (gender, address, etc.). Alternatively, this survey information can also be displayed at other times.

[0349] After inputting the survey data, the television device 2 makes a cooperation instruction request (step S106).

[0350] Next, use Figure 16-2 Explain the order in which advertisements are displayed based on another promotional message. Figure 16-2 This is a flowchart of the display process for an advertisement that represents another promotional message.

[0351] Figure 16-2 The process shown is the process performed by television device 2 in the program list display process. Based on the user's operation, television device 2 requests the television gateway 5 to obtain the program list structure information (program list) of the EC website specified by the user. If television device 2 makes a request to obtain program list information, television gateway 5 receives the request. Television gateway 5 sends the program list structure information to television device 2. Television device 2 displays the program list structure information. The program list structure information includes company information, channel information, program information, CM information, and VOD information.

[0352] As shown above, when the television device 2 displays program schedule information, it requests advertising information from the television gateway 5. If the television device 2 does not obtain advertising information from the television gateway 5 (step S101: No), the process ends.

[0353] If the television device 2 receives advertising information from the television gateway 5 (step S101: Yes), it determines, with reference to the advertising information, whether there is advertising information within a valid period based on the display start date and display end date (step S102). If there is no advertising information within the valid period (step S102: No), the television device 2 terminates the process.

[0354] If there is advertising information within the valid period (step S102: Yes), the television device 2 extracts the information to be displayed from the advertising information (step S103). Then, the television device 2 either displays all the extracted information or performs the loop processing of step S104 until the program schedule display is ended by user operation.

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

[0356] Additionally, when the television device 2 is displaying an advertisement (e.g., during the loop processing of step S104), if the user has selected their intention to participate in the recruitment campaign, it displays a request for feedback, receives input of the feedback information, and makes a cooperation instruction request. This feedback is based on input of the user's attributes (gender, address, etc.).

[0357] It should be noted that, alternatively, television device 2, referring to the promotional information, first displays a screen where applicants can select which advertisements to promote, and then executes... Figure 16-2 The flowchart shown illustrates the processing. That is, the television device 2 can also independently perform the processing related to advertising display and the processing related to ID collaboration, respectively.

[0358] Next, use Figure 17Explain the collaborative processing order. Figure 17 This is a flowchart illustrating the collaborative processing sequence. It is assumed that the authentication code and token generated by TV Cloud 3 contain information identifying the manufacturer. That is, it is assumed that TV Cloud 3 includes information identifying the device in the authentication code and token.

[0359] In execution Figure 16-1 or Figure 16-2 Before the processing in the flowchart shown, television device 2 generates an IFA-ID using a random number and notifies the TV cloud 3 (step S111). This IFA-ID is a numerical value with a number of bits that guarantees uniqueness. Additionally, television device 2 can also send its TV model name. Furthermore, bearer authentication can also be performed in steps S111 and S112.

[0360] TV Cloud 3 sends the IFA-ID to TV Gateway 5 (step S112). Then, in step S113, the following steps are executed: Figure 16-1 or Figure 16-2 The flowchart shown illustrates the processing. In step S113, if a cooperation instruction is given, the television device 2 requests a QR code (step S114).

[0361] in addition, Figure 17 Step S114 and Figure 7 Step S1 Figure 11 Step S12 and Figure 12 Step S61 is the same. Furthermore, in step S114, the television device 2 sends the PF-ID corresponding to the user-specified EC website (video platform) to the TV cloud 3.

[0362] In step S115, TV Cloud 3, in response, sends a QR code containing the URL of TV Gateway 5 and a URL authentication code to TV Device 2. This QR code contains the URL of TV Gateway 5 and the time-limited authentication code described below.

[0363] {"code": <authorization code> (authentication code)}

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

[0365] The URL authentication code contains information including the URL information for identifying the TV gateway 5, an authentication code for authentication between the content provider server 4 and the TV cloud 3, and status information. The authentication code may also include a portion for identifying the manufacturer of the TV device 2, and a portion for identifying the TV device 2 itself. Furthermore, the portion of the authentication code used to identify the TV device 2 is a random value. Additionally, the TV cloud 3 may establish a corresponding database in its storage unit 311 based on the time when this value was sent to the TV device 2. The status information may also include information encoded from the manufacturer's TC-ID and the video platform's PF-ID.

[0366] Examples of URL authentication code information are described below.

[0367] https: / / XXXXXXX YYYYYYYYY

[0368] Part X contains the URL of TV gateway 5, and part Y contains the OAuth2 authorization code. The authorization code section contains information that identifies the manufacturer and the television set. This information could be either the manufacturer or the television device 2. The URL authentication code can be sent in any format, as long as it contains the aforementioned information. Furthermore, part Y may also contain status information.

[0369] If the acquisition unit 243 of the television device 2 acquires the URL authentication code from the TV cloud 3, the display control unit 244 displays the content of the URL authentication code on the video display unit 233 as an image or video in an optical manner. Furthermore, the display format in the display control unit 244 can be a QR code, barcode, text, etc., as long as it can display the information contained in the URL authentication code as an image or video in an optical manner. In addition, while the first and second embodiments were described using QR codes, this embodiment is not limited to QR codes.

[0370] In addition, with Figure 7 Step S3 Figure 11 Step S23 Figure 12 Similarly, in step S116, the user terminal 1050 reads the URL authentication code information optically displayed on the video display unit 233 from the image information optically captured by the camera using the URL authentication code reading function. Thus, the user terminal 1050 obtains the URL and authentication code of the television gateway 5. This authentication code is a time-limited authentication code, configured as follows.

[0371] "code":<authorization code>,

[0372] "state": <string> / / Random number

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

[0374] The information sent during the authentication request is as follows.

[0375] "code":<authorization code>,

[0376] "state": <string> / / Random number

[0377] In step S118, if the acquisition unit 512 of the TV gateway 5 receives the authentication code and status information, the transmission unit 513 of the TV gateway 5 sends an HTML-formatted screen, including a collaboration button indicating a collaboration instruction, to the user terminal 1050. This HTML may also include the URL of the OAuth2 Authorization Endpoint for accessing the PF-ID, and parameters.

[0378] User terminal 1050 acquires the aforementioned HTML-formatted screen. Then, if a user presses the collaboration button via user operation on user terminal 1050 (step S119), a request for approval is sent to content provider server 4, which is the video platform. Content provider server 4 receives this approval request and sends information regarding its response to user terminal 1050 (step S120).

[0379] The information sent when the above-mentioned approval requirements are required may be composed of the following components.

[0380] Authorization:"Basic"+Base64(<client_id>+":"+<client_secret>)Request

[0381] {

[0382] "response_type": "code"

[0383] "code": <authorization code> (authentication code)

[0384] "redirect_uri": <TGW Endpoint> (The endpoint of TV Gateway 5)

[0385] "client_id": <TG-ID> (ID of TV Gateway 5)

[0386] "scope": <provided by VPF> (the authentication scope of the token)

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

[0388] }

[0389] Furthermore, when the TV device 2 makes a confirmation request for the cooperation status to the TV gateway 5 via the TV cloud 3 at the time point of step S119 (steps S151 and S152), the TV gateway 5 sends information about the incomplete cooperation to the TV device 2 (steps S153 and S154).

[0390] If user information is not registered in the content provider server 4, user registration processing is performed between the user terminal 1050 and the content provider server 4 (step S121). Here, user registration processing refers to the process of registering the information used to log in to the content provider server 4, namely the user ID and password, or registering the user's attribute information.

[0391] Next, user terminal 1050 sends a login request to content provider server 4, and content provider server 4 responds accordingly to the login request (step S122). As an example of this response, the following information (acknowledgment code) is output.

[0392] Response

[0393] {"code":<authorization code>,

[0394] "state": <state>}

[0395] If the user terminal 1050 receives the above response, it redirects the TV gateway 5 to indicate a cooperation instruction (step S123). Alternatively, the user terminal 1050 may also send the above approval code to the TV gateway 5.

[0396] If the acquisition unit 512 of the TV gateway 5 receives a redirection indicating a cooperation instruction, the TV gateway 5 determines the manufacturer based on the TC-ID contained in the status information obtained from the user terminal 1050. That is, the TV gateway 5 assigns a manufacturer (step S124).

[0397] Then, in step S125, the sending unit 513 of the TV gateway 5 sends an authentication code to the TV cloud 3 at the sending destination to make a token request (step S125).

[0398] The information sent during the token request may be, for example, as follows.

[0399] Authorization:"Basic"+Base64(TG-ID+":"+<client_secret>)

[0400] Request Parameters

[0401] {

[0402] grant_type: "authorization_code",

[0403] code: <authorization code>

[0404] state: <string> (state information)

[0405] redirect_uri:<redirect_uri>,

[0406] client_id: <TG-ID>

[0407] }

[0408] The generation unit 314 of TV Cloud 3 determines, by referring to the database of the storage unit 311, whether there exists information corresponding to the information of the identification content providing server 4 obtained by the acquisition unit 312 (e.g., information contained in the status information) and the authentication code, and performs authentication accordingly. If the database of the storage unit 311 contains information corresponding to the information of the identification content providing server 4 obtained by the acquisition unit 312 and the authentication code, the generation unit 314 generates a token (first token). Furthermore, the generation unit 314 establishes a correspondence between the first token and the information in the database containing the information of the identification content providing server 4 obtained by the acquisition unit 312 and the authentication code.

[0409] In step S126, the sending unit 313 of TV Cloud 3 sends the first token generated by the generating unit 314 to TV Gateway 5.

[0410] Specifically, the sending unit 313 of TV Cloud 3 sends the OAuth2 token response as a token to TV gateway 5. The OAuth2 access token response is structured as follows.

[0411] Response

[0412] {"access_token": <access token>,

[0413] "token_type": "Bearer"

[0414] "expires_in": 3600,

[0415] "refresh_token":<refresh token>}

[0416] TV Cloud 3 includes the access token when accessing TV Gateway 5. `expires_in` is the validity period (in seconds) of the access token, stored along with the time it becomes invalid upon receipt, and reused until that time. The refresh token is secretly stored by the content provider server 4. This is because, from a security perspective, simply storing it in local storage is inadequate. When manufacturers issue access tokens and refresh tokens, they add an identifier that identifies the TV manufacturer, thus allowing for the identification of the TV manufacturer.

[0417] If the acquisition unit 512 of the TV gateway 5 acquires the first token, the sending unit 513 of the TV gateway 5 sends information containing the approval code and makes a token request to the content provider server 4 (step S127).

[0418] The information sent during the token request may be, for example, as follows.

[0419] Authorization:"Basic"+Base64(TG-ID+":"+<client_secret>)

[0420] Request

[0421] {

[0422] grant_type: "authorization_code",

[0423] code: <code> (accreditation code)

[0424] state: <string> (state information)

[0425] redirect_uri:<TGW Endpoint>,

[0426] client_id: <TG-ID>

[0427] Content provider server 4 determines the user ID corresponding to the authentication code obtained from TV gateway 5. Then, content provider server 4 generates a token based on that user ID, namely the second token.

[0428] In step S128, the content providing server 4 sends the generated second token to the television gateway 5. Furthermore, the content providing server 4 may also establish a corresponding storage for the second token, user ID, and user attribute information.

[0429] Specifically, content provider server 4 sends an OAuth2 token response as a token to TV gateway 5. This OAuth2 access token response is structured as follows.

[0430] {"access_token": <access token>,

[0431] "token_type": "Bearer"

[0432] "expires_in": 3600,

[0433] "refresh_token":<refresh token>}

[0434] The acquisition unit 512 of the TV gateway 5 obtains the second token from the content provider server 4. Then, the sending unit 513 of the TV gateway 5 sends the second token to the content provider server 4 and makes a user information request to the content provider server 4 (step S129).

[0435] The information sent when requesting user information may be composed of, for example, the following.

[0436] Authorization: "Bearer"+<access token>)

[0437] Content provider server 4 retrieves the user ID and user attribute information corresponding to the second token obtained from TV gateway 5, and sends this information as a response to TV gateway 5 (step S130). Thus, the acquisition unit 512 of TV gateway 5 acquires the user ID and user attribute information. The response information is configured as follows.

[0438] Response

[0439] {"user_id": <UR-ID> (User ID in the website of content provider server 4),

[0440] "Preference": <Current user attributes> (user's date of birth, gender, postal code, purchase history, etc.)

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

[0442] Authorization:"Basic"+Base64(PF-ID+":"+<client_secret>)

[0443] If the acquisition unit 512 of the TV gateway 5 receives a device information request from the content provider server 4, the sending unit 513 of the TV gateway 5 sends the first token corresponding to the second token sent in step S127 to the TV cloud 3, and performs a device information request (step S132). The information sent during the device information request has the following composition, for example.

[0444] Authorization: "Bearer"+<access token>)

[0445] If the acquisition unit 312 of 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 TV device 2 corresponding to the HA-ID).

[0446] In step S133, the transmitting unit 313 of TV Cloud 3 sends HA-ID and other information to TV Gateway 5 as a response. The acquiring unit 512 of TV Gateway 5 acquires the HA-ID and information about the device corresponding to that HA-ID. An example of this response is as follows.

[0447] Response

[0448] {

[0449] ·"device_id":<HA-ID>(HA-ID)

[0450] • "model": <model name> (The model of TV device 2, i.e., information such as the number of pixels, such as the screen size in inches, 2K, 4K, 8K, etc.)

[0451] }

[0452] In step S134, the generation unit 514 of the TV gateway 5 registers the binding information, which associates the acquired HA-ID, user ID, attribute information of the TV device 2 (i.e., model information), and PF-ID, as DB information to the storage unit 511. Furthermore, the generation unit 514 of the TV gateway 5 may further include user attribute information in the binding information.

[0453] In step S135, the TV gateway 5 responds to the user terminal 1050 along with the aforementioned authentication code (step S135).

[0454] After step S134, when the television device 2 requests confirmation of the cooperation status from the television gateway 5 via the TV cloud 3 (steps S136 and S137), the television gateway 5 sends information about the completion of cooperation (such as information identifying the content provider server 4 that has cooperated) to the television device 2 (steps S138 and S139). Additionally, the television gateway 5 notifies the content provider server 4 of its IFA-ID (step S140).

[0455] Additionally, in television device 2, if the IFA-ID is updated, the updated IFA-ID is notified to TV cloud 3 (step S141). TV cloud 3 sends the updated IFA-ID to television gateway 5. Television gateway 5 sends the updated IFA-ID to content providing server 4 (step S143).

[0456] Next, use Figure 18 The flowchart shown illustrates the collaboration cancellation process. Figure 18 This is a flowchart illustrating the collaboration cancellation process. Based on the user's action, TV device 2 sends a collaboration cancellation request to TV cloud 3 (step S161). TV cloud 3, based on the cancellation request from TV device 2, sends a collaboration cancellation request to TV gateway 5 (step S162). Furthermore, in steps S161 and S162, either TV device 2 or TV cloud 3 may also send the IFA-ID along with the collaboration cancellation request.

[0457] TV gateway 5 notifies content provider server 4 of the collaboration cancellation request (step S163). Content provider server 4 deletes the generated second token. TV gateway 5 deletes the binding information and notifies TV cloud 3 of the deletion (step S164). TV cloud 3 notifies TV device 2 that the binding information has been deleted (step S165). Alternatively, TV cloud 3 can also delete the first token. Furthermore, content provider server 4 notifies TV gateway 5 of the cancellation of collaboration (step S166), and TV gateway 5 notifies TV cloud 3 of the cancellation of collaboration (step S167).

[0458] Next, use Figure 19 This explains how to cancel the collaboration process via operations on user terminal 1050. Figure 19 This is a flowchart illustrating the processing sequence for canceling collaboration via operation of user terminal 1050.

[0459] Imagine a scenario where a user operates a remote control or similar device on a television device 2, and in what is called an entry screen, the user begins to specify that they want to cancel the content delivery server 4 that is cooperating with their smartphone 1.

[0460] Figure 19 Step S180 and Figure 7 Step S1 Figure 11 Step S12 is the same. Furthermore, in step S180, the television device 2 sends the PF-ID corresponding to the user-specified content providing server 4 to the TV cloud 3.

[0461] In step S181, TV Cloud 3, in response, sends a QR code containing the URL of TV Gateway 5 and a URL authentication code to TV Device 2. This QR code contains the URL of TV Gateway 5 and the time-limited authentication code described below.

[0462] {"code": <authorization code> (authentication code)}

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

[0464] The URL authentication code contains information including the URL information for identifying the TV gateway 5, an authentication code for authentication between the content provider server 4 and the TV cloud 3, and status information. The authentication code may also include a portion for identifying the manufacturer of the TV device 2, and a portion for identifying the TV device 2 itself. Furthermore, the portion of the authentication code used to identify the TV device 2 is a random value. Additionally, the TV cloud 3 may establish a corresponding database in its storage unit 311 based on the time when this value was sent to the TV device 2. The status information may also include information encoded from the manufacturer's TC-ID and the video platform's PF-ID.

[0465] Examples of URL authentication code information are described below.

[0466] https: / / XXXXXXX YYYYYYYYY

[0467] Part X contains the URL of TV gateway 5, and part Y contains the OAuth2 authorization code. The authorization code section contains information that identifies the manufacturer and the television set. This information could be either the manufacturer or the television device 2. The URL authentication code can be sent in any format, as long as it contains the aforementioned information. Furthermore, part Y may also contain status information.

[0468] If the acquisition unit 243 of the television device 2 acquires the URL authentication code from the TV cloud 3, the display control unit 244 displays the content of the URL authentication code on the video display unit 233 as an image or video in an optical manner. Furthermore, the display format in the display control unit 244 can be a QR code, barcode, text, etc., as long as it can display the information contained in the URL authentication code as an image or video in an optical manner. In addition, while the first and second embodiments were described using QR codes, this embodiment is not limited to QR codes.

[0469] In addition, with Figure 7 Step S3 Figure 11 Similarly, in step S182, the user terminal 1050 reads the URL authentication code information optically displayed on the video display unit 233 from the image information optically captured by the camera using the URL authentication code reading function. Thus, the user terminal 1050 obtains the URL and authentication code of the television gateway 5. This authentication code is a time-limited authentication code, configured as follows.

[0470] "code":<authorization code>,

[0471] "state": <string> / / Random number

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

[0473] The information sent during the authentication request is as follows.

[0474] "code":<authorization code>,

[0475] "state": <string> / / Random number

[0476] In step S184, if the acquisition unit 512 of the TV gateway 5 receives the authentication code and status information, the transmission unit 513 of the TV gateway 5 sends an HTML-formatted screen, including a collaboration cancellation button indicating a collaboration cancellation instruction, to the user terminal 1050. This HTML may also include the URL of the OAuth2 Authorization Endpoint for accessing the PF-ID, and parameters.

[0477] User terminal 1050 acquires the aforementioned HTML-formatted screen. Then, if the user presses the collaboration cancellation button via user operation on user terminal 1050 (step S185), a confirmation request is sent to content provider server 4, which is the video platform. Furthermore, content provider server 4 receives this confirmation request and sends information regarding its response to user terminal 1050 (step S186).

[0478] The information sent when the above-mentioned approval requirements are required may be composed of the following components.

[0479] Authorization:"Basic"+Base64(<client_id>+":"+<client_secret>)Request

[0480] {

[0481] "response_type": "code"

[0482] "code": <authorization code> (authentication code)

[0483] "redirect_uri": <TGW Endpoint> (The endpoint of TV Gateway 5)

[0484] "client_id": <TG-ID> (ID of TV Gateway 5)

[0485] "scope": <provided by VPF> (the authentication scope of the token)

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

[0487] Furthermore, when the TV device 2 makes a confirmation request for the cooperation status to the TV gateway 5 via the TV cloud 3 at the time point of step S185 (steps S251 and S252), the TV gateway 5 sends the information of the subject of cooperation to the TV device 2 (steps S253 and S254).

[0488] Next, user terminal 1050 sends a login request to content provider server 4, and content provider server 4 responds accordingly to the login request (step S188). As an example of this response, the following information (acknowledgment code) is output.

[0489] Response

[0490] {"code":<authorization code>,

[0491] "state": <state>}

[0492] If the user terminal 1050 receives the above response, it redirects the TV gateway 5 to indicate a cooperation instruction (step S189). Alternatively, the user terminal 1050 may also send the above approval code to the TV gateway 5.

[0493] Then, in step S72, the sending unit 513 of the TV gateway 5 makes a token request by sending an authentication code to the TV cloud 3 at the sending destination (step S190).

[0494] The information sent during the token request may be, for example, as follows.

[0495] Authorization:"Basic"+Base64(TG-ID+":"+<client_secret>)

[0496] Request Parameters

[0497] {grant_type: "authorization_code",

[0498] code: <authorization code>

[0499] state: <string> (state information)

[0500] redirect_uri:<redirect_uri>,

[0501] client_id: <TG-ID>

[0502] }

[0503] The generation unit 314 of TV Cloud 3 determines, by referring to the database of storage unit 311, whether there is information corresponding to the information of the identification content providing server 4 obtained by acquisition unit 312 (e.g., information contained in status information) and the authentication code, and performs authentication. If the generation unit 314 finds information corresponding to the information of the identification content providing server 4 obtained by acquisition unit 312 and the authentication code in the database of storage unit 311, the sending unit 313 of TV Cloud 3 sends the first token to TV gateway 5 (step S191).

[0504] Specifically, the sending unit 313 of TV Cloud 3 sends the OAuth2 token response as a token to TV gateway 5. The OAuth2 access token response is structured as follows.

[0505] Response

[0506] {"access_token": <access token>,

[0507] "token_type": "Bearer"

[0508] "expires_in": 3600,

[0509] "refresh_token":<refresh token>}

[0510] TV Cloud 3 includes the access token when accessing TV Gateway 5. `expires_in` is the validity period (in seconds) of the access token, stored along with the time it becomes invalid upon receipt, and reused until that time. The refresh token is secretly stored by the content provider server 4. This is because, from a security perspective, simply storing it in local storage is inadequate. When manufacturers issue access tokens and refresh tokens, they add an identifier that identifies the TV manufacturer, thus allowing for the identification of the TV manufacturer.

[0511] If the acquisition unit 512 of the TV gateway 5 acquires the first token, the sending unit 513 of the TV gateway 5 sends information containing the approval code and makes a token request to the content provider server 4 (step S192).

[0512] The information sent during the token request may be, for example, as follows.

[0513] Authorization:"Basic"+Base64(TG-ID+":"+<client_secret>)

[0514] Request

[0515] {

[0516] grant_type: "authorization_code",

[0517] code: <code> (accreditation code)

[0518] state: <string> (state information)

[0519] redirect_uri:<TGW Endpoint>,

[0520] client_id: <TG-ID>

[0521] }

[0522] In step S193, the content providing server 4 sends the generated second token to the TV gateway 5.

[0523] Specifically, content provider server 4 sends an OAuth2 token response as a token to TV gateway 5. This OAuth2 access token response is structured as follows.

[0524] {"access_token": <access token>,

[0525] "token_type": "Bearer"

[0526] "expires_in": 3600,

[0527] "refresh_token":<refresh token>}

[0528] The acquisition unit 512 of the TV gateway 5 obtains the second token from the content provider server 4. Then, the sending unit 513 of the TV gateway 5 sends the second token to the content provider server 4 and makes a user information request to the content provider server 4 (step S194).

[0529] The information sent when requesting user information may be composed of, for example, the following.

[0530] Authorization: "Bearer"+<access token>)

[0531] Content provider server 4 retrieves the user ID and user attribute information corresponding to the second token obtained from TV gateway 5, and sends this information as a response to TV gateway 5 (step S195). Thus, the acquisition unit 512 of TV gateway 5 acquires the user ID and user attribute information. The response information is configured as follows.

[0532] Response

[0533] {"user_id": <UR-ID> (User ID in the website of content provider server 4),

[0534] "Preference": <Current user attributes> (user's date of birth, gender, postal code, purchase history, etc.)

[0535] The sending unit 513 of the TV gateway 5 sends the first token to the TV cloud 3 and makes a device information request (step S196). The information sent during the device information request has the following structure, for example.

[0536] Authorization: "Bearer"+<access token>)

[0537] If the acquisition unit 312 of 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 TV device 2 corresponding to the HA-ID).

[0538] In step S197, the transmitting unit 313 of TV Cloud 3 sends HA-ID and other information to TV Gateway 5 as a response. The acquiring unit 512 of TV Gateway 5 acquires the HA-ID and information about the device corresponding to that HA-ID. An example of this response is as follows.

[0539] Response

[0540] {

[0541] ·"device_id":<HA-ID>(HA-ID)

[0542] • "model": <model name> (The model of TV device 2, i.e., information such as the number of pixels (inches, 2K, 4K, 8K, etc.))

[0543] TV gateway 5 deletes the binding information and provides a notification of the deletion to server 4 (step S198). Additionally, TV gateway 5 can also notify TV cloud 3 of the deletion of the binding information.

[0544] After step S198, if TV device 2 requests confirmation of cooperation status from TV cloud 3 to TV gateway 5 (steps S199 and S200), TV gateway 5 will send information indicating that no cooperation has been performed to TV device 2 (steps S201 and S202).

[0545] In the above embodiments, the display of promotional information is described when the program schedule is displayed. However, promotional information may also be displayed when advertisements are displayed on the screen at a specified time during a program broadcast (a program with linearly published dynamic image content) via the network.

[0546] For example, it can also be used Figure 20 Clickable ads, as shown, are used to display promotional information. Figure 20 This is an example of clickable ad information. The ad information includes: information about an array of objects representing the ad information (ad_list); information about the ad type (ad_type); and information about the URL of the ad image (img_url), etc.

[0547] In the above embodiments, in Figure 17 The flowchart shown illustrates the process where the TV gateway 5 requests user information from the content provider server 4 and obtains the UR-ID from the content provider server 4; however, it is not limited to this. For example, in... Figure 21 The middle shows Figure 17A variation of the flowchart. For example, with... Figure 17 The same processing described in the text is omitted. It is also possible that it is not included in... Figure 21 Instead of the content provider server 4 providing the UR-ID in step S128 or S130, the TV gateway 5 issues a temporary UR-ID in step S118 and includes this parameter in the value of "state" contained in the HTML code. In this case, the user terminal 1050 sends this value to the content provider server 4 in step S120. Alternatively, it is also possible to... Figure 12 As also described in the flowchart, TV gateway 5 issues a temporary UR-ID.

[0548] In this embodiment, the television gateway 5 pre-stores promotional information and sends the promotional information to the television device 2 at predetermined times, such as when the television device 2 displays the program schedule. The promotional information includes an advertising information section 350, which contains information indicating the type of advertisement to be displayed and information indicating the content of the advertisement.

[0549] Additionally, TV gateway 5 obtains an authentication code from user terminal 1050, sends the authentication code to TV cloud 3 (the destination determined by the authentication code), obtains a first token from TV cloud 3, and obtains a second token from content provider server 4. Then, TV gateway 5 obtains the user ID by sending the second token to content provider server 4, and obtains the ID (e.g., HA-ID) of TV device 2 by sending the first token to TV cloud 3. In this way, TV gateway 5 can establish a correspondence between the user ID and the ID of TV device 2 by obtaining the user ID from content provider server 4 and the ID of TV device 2 from TV cloud 3.

[0550] In this scenario, because TV gateway 5 stores the user ID corresponding to the ID of TV device 2, TV cloud 3 does not need to manage the user ID, thus reducing its information management burden. Furthermore, since TV gateway 5 obtains the authentication code from user terminal 1050, it is not necessary to send the authentication code from content provider server 4 to TV gateway 5, further reducing the processing burden on content provider server 4. In other words, TV gateway 5 can appropriately perform the processing that coordinates the receiver's identifier (TV device 2's ID) with the terminal's identifier (user ID of user terminal 1050). Additionally, TV gateway 5 can facilitate the processing that coordinates the ID of TV device 2 with the user ID of user terminal 1050 by outputting promotional information.

[0551] Furthermore, the TV gateway 5 includes advertising information in its promotional materials. This advertising information includes information indicating the type of advertisement to be displayed and information indicating the content of the advertisement. Therefore, the TV device 2 switches its display mode according to the type of advertisement to output the advertising information, thereby further facilitating the processing of user ID collaboration with the user terminal 1050. Additionally, the TV gateway 5 contains multiple advertising messages in its promotional materials, allowing the TV device 2 to output multiple advertisements sequentially.

[0552] Furthermore, after the TV gateway 5 coordinates the ID of the TV device 2 with the user ID of the user terminal 1050, it sends the IFA-ID to the content provider server 4. Thus, the TV gateway 5 can provide information that identifies the TV device 2 without revealing the ID of the TV device 2 to the content provider server 4.

[0553] While several embodiments of this application have been described, these embodiments are merely illustrative and not intended to limit the scope of the application. For example, the television device in the above embodiments could also be an electronic device, such as a set-top box or video recorder, that does not have a display mechanism but has the function of receiving video signals output to an external display device. Furthermore, these new embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the application. These embodiments and their variations are included in the scope and spirit of the application, and are included within the scope of the invention described in the claims and its equivalents.

[0554] For example, for image icons displayed on a user terminal that can be magnified on a television device, a button indicating magnification can be provided on or near the image icon. Additionally, the color, shape, and display format of the magnifiable image icon can be changed to distinguish it from other non-magnifiable image icons. Furthermore, when the user terminal instructs the television device to magnify the image, or during display processing on the television device, a voice notification can be given via the user terminal or the television device.

Claims

1. A server management device capable of sending and receiving information with multiple server devices, wherein the multiple server devices store information establishing a correspondence between an identifier of a broadcast receiving device, an authentication code, an identifier of a content providing device, and a first token, wherein... The server management device includes: The storage unit stores promotion information that facilitates establishing a correspondence between the identifier of the broadcast receiving device and the identifier of the terminal device of the user of the content providing device. The promotion information sending unit sends the promotion information to the broadcast receiving device; An authentication code sending unit sends the authentication code to the broadcast receiving device based on a request for promotional information from the broadcast receiving device. The authentication request acquisition unit acquires authentication requests from the terminal device that has acquired the authentication code, including the authentication code, the identifier of the content providing device, and the identifier of the server device. The cooperation instruction acquisition unit acquires a notification from the terminal device of a cooperation instruction between the identifier of the broadcast receiving device and the user identifier of the terminal device; The first token acquisition unit, after receiving the notification of the cooperation instruction, acquires the first token corresponding to the authentication code from the server device corresponding to the authentication requirement; The second token acquisition unit acquires a second token corresponding to the user identifier of the terminal device from the content providing device corresponding to the authentication requirement; The broadcast receiving device identifier acquisition unit acquires the identifier of the broadcast receiving device corresponding to the first token from the server device; The user identifier acquisition unit acquires the user identifier of the terminal device corresponding to the second token from the content providing device; as well as The registration department establishes a corresponding registration for 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.

2. The server management device according to claim 1, wherein, The server management device also includes: The second identifier acquisition unit acquires the second identifier of the broadcast receiving device generated by the broadcast receiving device; and The second identifier sending unit sends the second identifier of the broadcast receiving device corresponding to the first token to the content providing device of the acquisition source of the second token after the registration unit establishes a corresponding registration 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 sending unit sends the promotion information together with the program schedule information.

4. The server management device according to claim 1, wherein, The promotional information sending unit sends the promotional information by including it in selectable advertising information.

5. The server management device according to any one of claims 1 to 4, wherein, The promotional information includes advertising information, which contains information indicating the type of advertisement to be displayed and information indicating the content of the advertisement.

6. The server management device according to claim 5, wherein, The promotional information includes multiple advertising messages.

Images