JP7513785B2 - program - Google Patents

Description

The present invention relates to a program.

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

Patent No. 5898431

However, such devices often do not have a large enough screen, making it difficult for users to visualize the size of the images displayed on the device.

The problem that this invention aims to solve is to provide a program that can display an image displayed on a terminal on a device that can display a screen larger than the terminal itself.

The program of the embodiment causes a computer, which is a broadcast receiving device, to execute the following steps: an image providing device information sending step of sending information about an image providing device that provides an image to a server device; an access information acquiring step of acquiring access information including an access destination for the image providing device and an authentication code; an access information output step of outputting the access information to a display unit; a display target image information acquiring step of acquiring from the server device an access destination for an image to be displayed based on a request from a terminal that reads the access information displayed on the display unit; an image acquiring step of acquiring from the image providing device an image based on the access destination of the image to be displayed acquired in the display target image information acquiring step; a display control step of displaying the image acquired in the image acquiring step on the display unit; a command receiving step of receiving an operation command on the screen of the broadcast receiving device by the terminal; and a control step of controlling the image displayed on the display unit based on the operation command .

FIG. 1 is a diagram showing an outline of an example of the overall configuration of an information linking system according to the first embodiment. FIG. 2 is a block diagram showing an example of the overall configuration of the television device according to the first embodiment. FIG. 3 is a block diagram showing an example of a partial configuration of the television device according to the first embodiment. FIG. 4 is a block diagram showing an example of the overall configuration of the push distribution server according to the first embodiment. FIG. 5 is a block diagram showing an example of a partial configuration of the push distribution server of the first embodiment. FIG. 6 is a diagram showing the data structure of data stored in the push distribution server of the first embodiment. FIG. 7 is a flowchart showing the overall processing in the information link system of the first embodiment. FIG. 8 is a diagram illustrating an overview of an example of the overall configuration of an information linking system according to the second embodiment. FIG. 9 is a block diagram showing an example of the overall configuration of a common reception server according to the second embodiment. FIG. 10 is a block diagram showing an example of a partial configuration of a common reception server according to the second embodiment. FIG. 11 is a flowchart showing the overall processing in the information link system according to the second embodiment.

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

First Embodiment
First, an example of the overall configuration of the information linkage system S of the first embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an overview of an example of the overall configuration of the information linkage system S of the first embodiment. The information linkage system S includes a smartphone 1 (terminal), a television device 2 (broadcast receiving device), a push distribution server 3 (server device), and an EC (Electronic Commerce) site server 4. The push distribution server 3 can communicate with the television device 2 and the EC site server 4 via a public communication line such as the Internet. In addition, the smartphone 1 can wirelessly communicate with the EC site server 4 and the push distribution server 3 via a base station.

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

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

The EC site server 4 is a computer device for operating an EC site (online shop) on the Internet. The EC site server 4 is, for example, a server device of an EC platformer. The EC site server 4 serves as a platform for purchasing products and services via a network in response to the operation of a terminal device (smartphone 1, etc.) by a user (consumer). The EC site server 4 transmits images of products to the smartphone 1 in response to, for example, an operation on the smartphone 1. The EC site server 4 registers the redirect_uri in advance in the push distribution server 3.

The components of the information linkage system S will be described in detail below with reference to FIG. 2 and subsequent figures. FIG. 2 is a block diagram showing an example of the overall configuration of a television device 2 according to a 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 (details will be described later).

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

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

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

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

The signal processing unit 207 demodulates the broadcast signal supplied from the tuners 203a to 203g to a broadcast signal including a digital video signal and audio signal. The signal processing unit 207 also selectively applies a predetermined digital signal processing to the video signal included in the digital broadcast signal and outputs the result to the graphics processing unit 208. The signal processing unit 207 also selectively applies a desired digital signal processing to the audio signal included in the digital broadcast signal and outputs the result to the audio processing unit 209.

A number of 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 an external device such as a DVD (Digital Versatile Disk) recorder. The signal processing unit 207 digitizes the analog video and audio signals input from the external input terminals 214a to 214d. The signal processing unit 207 also performs a predetermined digital signal processing on the digitized video signal and outputs it to the graphics processing unit 208. The signal processing unit 207 also performs a predetermined digital signal processing on the digitized audio signal and outputs it to the audio processing unit 209.

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

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

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

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

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

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

The control unit 216 is connected to a card holder 217 to which a memory card 234 can be attached and detached via a card I/F 225. This allows the control unit 216 to send and receive various information to and from the memory card 234 attached to the card holder 217 via the card I/F 225.

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

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

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

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

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

The transmitting unit 242 transmits various information to an external device. The acquiring unit 243 acquires various information from an external device and reads out various information stored in the memory unit 241.

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

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

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

The storage device 305 includes, for example, an HDD or SSD, and stores various information. The CPU 303 executes various programs to control each component of the push distribution server 3. The memory 304 includes, for example, a ROM or RAM, and stores various programs and data used in various arithmetic processing by the CPU 303.

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

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

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

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

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

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

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

The acquisition unit 243 of the television device 2 acquires the QR code from the push distribution server 3. In this way, the acquisition unit 243 of the television device 2 acquires the QR code, which is access information based on the authentication code and the URL that is the access destination of the EC site. The display control unit 244 of the television device 2 causes the QR code to be displayed on the video display unit 233. In this way, the display control unit 244 displays and outputs the QR code.

In step S3, the smartphone 1 reads the QR code displayed on the video display unit 233 using a QR code reading function implemented by an imaging means or the like. As a result, the smartphone 1 obtains the URL and authentication code of the EC site. In step S4, upon obtaining the URL and authentication code of the EC site, the smartphone 1 accesses the EC site server 4 based on the URL and transmits the authentication code.

When the EC site server 4 acquires the authentication code from the smartphone 1, in step S5, it transmits the authentication code to the push distribution server 3 together with information identifying the EC site server 4, and makes an authentication request. In addition, the acquisition unit 312 of the push distribution server 3 acquires the authentication code together with information identifying the EC site server 4. In this way, the acquisition unit 312 of the push distribution server 3 acquires the authentication code transmitted from the EC site server 4.

The generation unit 314 of the push distribution server 3 performs authentication by referring to the DB of the storage unit 311 and determining whether there is information corresponding to the information identifying the EC site server 4 and the authentication code acquired by the acquisition unit 312. The generation unit 314 refers to the DB of the storage unit 311, and if there is information corresponding to the information identifying the EC site server 4 and the authentication code acquired by the acquisition unit 312, generates a token using publicly known technology. The generation unit 314 also associates the token with the information identifying the EC site server 4 and the information having the authentication code acquired by the acquisition unit 312 in the DB. The information further associating the token with the information identifying the EC site server 4 and the information having the authentication code acquired by the acquisition unit 312 includes the TVID of the television device 2 that made the request.

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

In step S6, the transmission unit 313 of the push distribution server 3 transmits the token generated by the generation unit 314 to the EC site server 4. In this manner, the transmission unit 313 transmits a token based on the authentication code to the EC site server 4. The EC site server 4 retains information that associates the token with the user ID of the smartphone 1 that transmitted the authentication code.

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

In step S9, the EC site server 4 transmits the token corresponding to the requesting smartphone 1 and the URL of the image to be displayed to the push distribution server 3, and requests display. The acquisition unit 312 of the push distribution server 3 acquires the token and URL transmitted by the EC site server 4. In this way, the acquisition unit 312 acquires the token transmitted by the EC site server 4 and the URL of the access destination of the image to be displayed based on the request from the smartphone 1.

In step S10, the push distribution server 3 refers to the DB in the storage unit 311 and identifies the TVID corresponding to the token acquired by the acquisition unit 312. The transmission unit 313 of the push distribution server 3 then transmits the URL of the access destination of the image to be displayed to the television device 2 corresponding to the TVID.

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

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

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

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

Here, an example of the overall configuration of the information linkage system S of the second embodiment will be described. FIG. 8 is a diagram showing an overview of an example of the overall configuration of the information linkage system S of the second embodiment. Note that the same components as those in the first embodiment are given the same reference numerals and will not be described. As shown in FIG. 8, the information linkage system S has multiple push distribution servers 3 (push distribution server 3a, push distribution server 3b). The push distribution server 3b can be connected to a television device 2, which is a television (not shown) made by a manufacturer associated with the push distribution server 3b.

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

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

In addition, a random secret to be set in the x-api-key between the push distribution server 3 and the common reception server 5 is determined in advance. The x-api-key passed between the common reception server 5 and the EC site server 4 becomes a pass-key.

EC site server 4 is a server of the EC platform provider. For users, i.e., consumers, the server that serves as a platform for purchasing products and services is the EC site server 4. In addition, the EC site server 4 pre-registers the redirect_uri in the common reception server 5.

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

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

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

The storage device 505 includes, for example, an HDD or SSD, and stores various information. The CPU 503 executes various programs to control each component of the common reception server 5. The memory 504 includes, for example, a ROM or RAM, and stores various programs and data used in various arithmetic processing by the CPU 503.

Fig. 10 is a block diagram showing an example of a partial configuration of the common reception server 5 of the second embodiment. The common reception server 5 includes a memory unit 511 (memory 504, storage device 505), and an acquisition unit 512, a transmission unit 513, and a generation unit 514 as functional modules generated as a result of the program stored in the memory unit 511 being executed by the CPU 503.

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

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

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

Also, step S21 in FIG. 11 is similar to step S1 in FIG. 7, so a description thereof will be omitted. In step S22, a URL authentication code is sent from the push distribution server 3 to the television device 2. The URL authentication code 2010 is information including URL information for identifying the EC site server 4 and an authentication code for performing authentication between the EC site server 4 and the push distribution server 3. The authentication code may include a portion for identifying the manufacturer of the television device 2 and a portion for identifying the television device 2. Furthermore, the portion included in the authentication code for identifying the television device 2 is a random value. Furthermore, the push distribution server 3 may associate the time when this value is sent to the television device 2 as information in the DB of the memory unit 311.

An example of the information of the URL authentication code 2010 is as follows:
https://XXXXXXYYYYYYYY
The X portion contains the URL of the EC site server 4, and the Y portion contains the OAuth2 authorization code. The authorization code portion contains information that can identify the manufacturer and the television. Either one of the information that can identify the manufacturer and the television device 2 may be used. The URL authentication code 2010 may be sent in any format as long as it contains the above information.

When the acquisition unit 243 of the television device 2 acquires the URL authentication code 2010 from the push distribution server 3, the display control unit 244 optically displays and outputs the contents of the URL authentication code 2010 as an image or video on the video display unit 233. Note that the display form in the display control unit 244 may be a QR code, a barcode, text, or the like, as long as it is possible to optically display and output the information contained in the URL authentication code 2010 as an image or video. Also, although a QR code is described in the first embodiment, it is not limited to a QR code as in this embodiment.

7, in step S23, the user terminal 1050 reads the information of the URL authentication code 2011 optically displayed on the video display unit 233 from the image information optically captured by the imaging means using the URL authentication code reading function. As a result, the user terminal 1050 obtains the URL and authentication code of the EC site. The authentication code portion is a time-limited authentication code and is configured as follows:
"code": <authorization code>,
"state" : <string> // Random number

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

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

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

In step S26, the transmission unit 313 of the common reception server 5 refers to the acquired authentication code 2021, and refers to the information identifying the manufacturer contained in the authentication code 2021 to identify the push distribution server 3 to which the message is to be sent. Specifically, the transmission unit 313 of the common reception server 5 checks the authorization code, i.e., the authentication code, and determines which push distribution server 3 the message is to be sent to.

Then, in step S27, the transmitting unit 313 of the common reception server 5 makes an authentication request by transmitting an authentication request 2022 to the push distribution server 3 of the transmission destination.
In this way, the transmitting unit 513 of the common reception server 5 transmits the authentication request 2022 to the push distribution server 3 of the destination identified based on the Authorization_code (authentication code) of the authentication code 2021. The information of the authentication request 2022 transmitted by the transmitting unit 313 of the common reception server 5 is the same as the information of the authentication code 2021 acquired from the EC site server 4. Other examples of the information of the authentication request 2022 include the following.
GET https://each-maker. Example. com/common/devices/id
Authorization: "Bearer" + <access_token>
The acquisition unit 312 of the push distribution server 3 acquires the authentication code written in the URL authentication code 2010 together with the information for identifying the EC site server 4 .

The generation unit 314 of the push distribution server 3 performs authentication by referring to the DB of the storage unit 311 and determining whether there is information corresponding to the information identifying the EC site server 4 and the authentication code acquired by the acquisition unit 312. The generation unit 314 refers to the DB of the storage unit 311, and generates a token 2030 if there is information corresponding to the information identifying the EC site server 4 and the authentication code acquired by the acquisition unit 312. The generation unit 314 further associates the token 2030 with information having the information identifying the EC site server 4 and the authentication code acquired by the acquisition unit 312 in the above DB.

In step S28, the transmission unit 313 of the push distribution server 3 transmits the token 2030 generated by the generation unit 314 to the common reception server 5.

Specifically, the transmitting unit 313 of the push distribution server 3 sends an OAuth2 Token Response to the common reception server 5 as a token 2030. This response, the OAuth2 Access Token Response, has the following structure.
{"access_token": <access token>,
"token_type": "Bearer",
"expires_in": 3600,
"refresh_token": <refresh token>}
When the push distribution server 3 accesses the common reception server 5, it attaches the access_token. expires_in is the validity period (seconds) of the access_token, and is stored when the access_token is received together with the time at which it becomes invalid, and until then, the access_token is used repeatedly. The refresh_token is stored secretly by the EC site server 4. For security reasons, it is not good to simply store it in local storage. When the access_token and refresh_token are issued by each manufacturer, the television manufacturer can be identified by attaching an identifier that identifies the television manufacturer to the beginning of the token.

The acquisition unit 512 of the common reception server 5 acquires the token 2030. Then, in step S29, the common reception server 5 transmits the token 2030 to the EC site server 4 as the token 2031, and the EC site server 4 acquires the token 2031. Note that the transmission unit 313 of the push distribution server 3 may transmit the token directly to the EC site server 4.

The EC site server 4 stores information associating the token 2031 with the user ID of the user terminal 1050 that sent the authentication code.

Then, in step S30, the EC site server 4 sends the token 2031 and the user ID as a response, i.e., the token + user ID 2040, to the common reception server 5. This allows the EC site server 4 to send the user ID of the user of the user terminal 1050 to the common reception server 5.

The configuration of the token+user ID 2040 information transmitted by the EC site server 4 is as follows:
POST https://tv-common. Example. com/common/users/id
Authorization: "Basic" + Base64 (<client_id> + ":" + <client_secret>)
Content-type: application/x-www-form-urlencoded
{grant_type: "access_token",
access_token: <access token> (information issued as the access token in step S28),
client_id: An identifier assigned to each site of the EC site server 4. Pre-registered on the manufacturer's common site.
user_id: User ID on the site of the EC site server 4,
Preference: <Current user attributes (current user attributes: user's date of birth, gender, zip code, purchase history, etc.)>}

The acquisition unit 512 of the common reception server 5 acquires the token+user ID 2040 from the EC site server 4. In step S31, the transmission unit 513 of the common reception server 5 identifies the destination push distribution server 3 from the token+user ID 2040, and transmits a device ID request 2041 (TVID) to the destination push distribution server 3. Note that the transmission unit 513 of the common reception server 5 may transmit the token when transmitting the device ID request 2041.

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

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

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

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

In addition, in step S35, the generation unit 514 of the common reception server 5 stores the generated pass key in the memory unit 511.

When the EC site server 4 acquires the pass key from the common reception server 5, it stores the information contained in the pass key. Specifically, the following information is stored for each EC site user ID:
・access_token
・refresh_token
・pass_key
・model // Related TV model information

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

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

When the EC site server 4 receives the TV display request 2071 from the user terminal 1050, in step S39, it transmits a display request 2072 including the token, pass key, and URL of the link destination to the common reception server 5, thereby making a display request to the television device 2. The information of the display request 2072 has the following configuration.
POST https://tv-common. Example. com/common/devices/control
Authorization: "Bearer" + <access_token>
x-api-key:<pass_key>
Content-type: application/jison
{"command_type":"keycode"
"keycode": "<common key code>"}
{"command_type":"webview",
"site": "<Website URL>",
"Template": "full"}

The acquisition unit 512 of the common reception server 5 receives information about the display request 2072, including the token, pass key, and the URL of the link destination, from the EC site server 4. The acquisition unit 512 then extracts the pass_key from the x-api-key header.

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

The display request 2073 that the sending unit 513 sends to the push distribution server 3 includes a token, a client ID, a URL, and a message. Examples of this information are as follows:
POST https://each-maker. Example. com/common/devices/control
Authorization: "Bearer" + <access_token>
x-api-key: <Random secret determined by the manufacturer's common site and each manufacturer>
Content-type: application/json
{"command_type":"keycode",
"keycode": <common key code>,
"client_id":<client_id>,
"messageid:<message ID>}
{"command_type":"webview",
"site": <Website URL> (TV website URL),
"template": "full",
"client_id":<client_id>,
"messageid":<message ID>}

The acquisition unit 312 of the push distribution server 3 receives the display request 2073 from the common reception server 5. The acquisition unit 312 extracts the access_token from the Authorization header of the display request 2073 and identifies the television device 2. In step S42, the transmission unit 313 of the push distribution server 3 outputs a display request 2074 to the television device 2 based on the identification result. Note that the display request may be replaced with a display request command unique to the manufacturer. In addition, if necessary, the push distribution server 3 may also aggregate accesses for each client_id and make a request to the television.

In step S43, the television device 2 starts a browser in response to the display request, executes Javascript (registered trademark) using an onLoad or onClick event, etc., and displays and outputs the image at the URL destination of the display target. The television device 2 also notifies the measurement server 6 of a display operation result notification 2080 that identifies the servicer, user, TV manufacturer, and the displayed advertisement. The measurement server 6 tally up the results of the advertisements displayed by the push distribution server 3 on multiple television devices 2. Based on the tally up results, the manufacturer or common reception server 5, or the owner of the measurement server 6, requests advertising and promotion fees from the e-commerce platformer that owns the EC site server 4.

The application on the user terminal 1050 can operate the screen of the television device 2 based on the operation command 2090 in step S44. The application sends the operation command 2090 to the EC site server 4 in response to the operation from the user terminal 1050.

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

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

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

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

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

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

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

Upon receiving the operation command 2091 in step S45, the common reception server 5 sends an operation command 2092 to the push distribution server 3 in step S46. The operation command 2092 is the same command as the operation command 2091.
In step S47, the common reception server 5 transmits a response message ID 2094 as a response message to the EC site server 4. The message ID has the following structure.
{messageid: <message ID>}

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

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

The flowchart shown in FIG. 11 explains the process of integrating multiple manufacturers to access the platform provider's EC site server 4, but a manufacturer can also access the EC site server 4 independently, as in the case of the push distribution server 3 in the first embodiment. In this case, the push distribution server 3 incorporates the operations of the common reception server 5. In this case, the exchange of information between the push distribution server 3 and the common reception server 5 is omitted.

The common reception server 5 acquires an authentication code from the EC site server 4, transmits the authentication code to the destination push distribution server 3 identified based on the authentication code, acquires a token and an access destination for the image to be displayed from the EC site server 4, and transmits the token and the access destination for the image to be displayed to the destination push distribution server 3. This allows processing to be performed without the EC site server 4 having to determine which of the multiple push distribution servers 3 to transmit to.

The programs executed by each device (user terminal 1050, television device 2, push distribution server 3, EC site server 4, common reception server 5, measurement server 6) in this embodiment can be provided by recording them in an installable or executable format on a recording medium that can be read by a computer device, such as a CD (Compact Disc)-ROM (Read Only Memory), a flexible disk (FD), a CD-R (Recordable), or a DVD (Digital Versatile Disk). The programs may also be provided or distributed via a network such as the Internet.

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

1...smartphone, 2...television device, 3...push distribution server, 4...e-commerce site server, 5...common reception server, 6...measurement server, S...information linkage system

Claims (2)

A computer that is a broadcast receiving device
an image providing device information transmitting step of transmitting information about an image providing device that provides an image to a server device;
an access information acquisition step of acquiring access information including an access destination and an authentication code for the image providing device;
an access information output step of outputting the access information to a display unit;
a display target image information acquisition step of acquiring, from the server device, an access destination of an image to be displayed based on a request from a terminal that has read the access information displayed on the display unit ;
an image acquisition step of acquiring, from the image providing device, an image based on an access destination of the image to be displayed acquired in the display target image information acquisition step;
a display control step of displaying the image acquired in the image acquisition step on the display unit; and a command receiving step of receiving an operation command on a screen of the broadcast receiving device by the terminal.
a control step of controlling an image displayed on the display unit based on the operation command;
A program for executing the above. a notification step of transmitting an operation result notification identifying the operation command to a measurement server;
The program according to claim 1 , further causing the computer to execute the steps of:

Images