Television receiver and television system

Abstract

To provide a television receiver and a television system capable of avoiding access concentration to a server.SOLUTION: The television receiver which receives content information distributed via a server comprises a load leveling unit which levels loads on the server based on characteristic information of the television receiver.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] The present invention relates to television receivers and television systems. [Background technology]

[0002] In recent years, advances in networks have led to the launch of many video distribution services. In particular, large-screen television receivers can no longer simply receive broadcasts as in the past; they can now connect to networks and play distributed videos, allowing viewers to enjoy higher-quality, more realistic images. This has become possible thanks to faster networks and improved processing capabilities of television receivers, and it is expected that in the future there will be more opportunities to display and operate a variety of content provided by networks on television receivers.

[0003] Video distribution services have become more sophisticated and go beyond simply watching videos. They now offer interactive services that link video with web information, such as directing users from video content to e-commerce sites to purchase products and allowing them to check details about web information on the Internet (such as news or ticket information) through videos.

[0004] In the current circumstances, the ability of television receivers, which are easy to use at home, to provide users with video, website information, e-commerce services, and other information provided over the network is becoming an extremely important theme as networking continues to advance in the future. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2006-222674 A [Patent Document 2] JP 2020-102720 A Summary of the Invention [Problem to be solved by the invention]

[0006] Advances in networks have made it easier than ever to provide video distribution services. However, there are various issues with receiving online video distribution services on television receivers, and reception has not yet become as widespread as with broadcasting. Furthermore, information terminals such as PCs now offer more advanced network services by linking distributed videos with web content, but it has been difficult to provide such linked services on television receivers up until now.

[0007] While terrestrial broadcasting broadcasts video content according to a unified standard, network video content is distributed using multiple distribution methods. Therefore, in order to select and receive video content distributed from a video platform that distributes specific videos, the receiver needs to be equipped with special functions. Also, in order to receive video content distributed to a television broadcast receiver, the television receiver needs to have the function of connecting to a network and the ability to play the received video content.

[0008] Depending on the functions and performance of the television receiver, some distributed video contents can be received and some cannot. For this reason, the video platforms and receiving terminals that realize conventional video distribution services are realized by each being equipped with their own distribution technologies. From the video platform's perspective, it was necessary to individually support receiving terminals with multiple different performances and functions, and from the receiving terminal's perspective, it was necessary to individually support video platforms with multiple different distribution methods. In addition, there are various methods for selecting video content, and a consistent program selection method cannot be provided, which causes confusion for users. This situation not only hinders the spread of video distribution, but also poses a major challenge in terms of user convenience.

[0009] On the other hand, when video content and Web content are mutually linked to provide interactive services, television receivers are operated by remote control, which is extremely poor in operability compared to the input functions of a keyboard or mouse that an information terminal such as a PC has, making it difficult for users to operate comfortably and receive advanced services.In addition, because such advanced services are implemented through the linkage between video platforms and Web sites, it is difficult to provide such linked services in common across different video platforms and television receivers with different functions and capabilities.

[0010] Therefore, it is conceivable to provide a television gateway that serves as a server, receive information including content information from a video platform that aggregates and distributes content information from content service providers, and convert the received content information so that it can be received by a television receiver.

[0011] However, when a television gateway serving as a server is provided, for example, when playing back content from a linear channel, the broadcast time is fixed, so access from television receivers to the television gateway serving as a server is concentrated. Therefore, the television gateway serving as a server needs to be designed to match the peak of access concentration from television receivers, which results in high costs.

[0012] An object of the present invention is to provide a television receiver and a television system that can avoid concentration of accesses to a server. [Means for solving the problem]

[0013] A television receiver of an embodiment is characterized in that the television receiver receives content information distributed via a server and is equipped with a load leveling unit that attempts to level the load on the server based on unique information possessed by the television receiver. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is an explanatory diagram of a first embodiment based on the present invention. [Diagram 2] FIG. 2 is a diagram showing the configuration of a network program guide in the first embodiment based on the present invention. [Diagram 3] FIG. 3 is an explanatory diagram of a network program guide according to a first embodiment of the present invention. [Figure 4] FIG. 4 shows an example of the configuration of a television receiver according to the present invention. [Diagram 5] FIG. 5 shows an example of the configuration of a video platform based on the present invention. [Figure 6] FIG. 6 shows an example of the configuration of a TV gateway based on the present invention. [Figure 7] FIG. 7 is a sequence diagram showing the flow of acquiring and displaying an Internet program guide. [Figure 8] FIG. 8 is a diagram showing an example of reserving IDs for a video platform and a TV cloud. [Figure 9] FIG. 9 is a diagram showing other IDs. [Figure 10] FIG. 10 is a diagram showing an example of the structure of network program guide data. [Figure 11] FIG. 11 is a diagram showing an example of configuration information of the network program guide data. [Figure 12] FIG. 12 is a diagram showing a peak_shift key object of the configuration information. [Figure 13] FIG. 13 is an explanatory diagram of a second embodiment based on the present invention. [Figure 14] FIG. 14 is an explanatory diagram of the ID configuration and ID combination according to the second embodiment of the present invention. [Figure 15] FIG. 15 is an explanatory diagram of ID combining processing in the second embodiment based on the present invention. [Figure 16] FIG. 16 is a diagram showing the configuration of a network program guide when IDs are combined in the second embodiment based on the present invention. [Figure 17] FIG. 17 shows an example of a screen display when IDs are combined in the second embodiment based on the present invention. [Figure 18] FIG. 18 shows information necessary for content selection in the second embodiment based on the present invention. [Figure 19] FIG. 19 illustrates an advertisement insertion method according to a second embodiment of the present invention. [Figure 20] FIG. 20 is a block diagram of a third embodiment according to the present invention. [Figure 21] FIG. 21 is a diagram illustrating the operation of the third embodiment based on the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0016] The present invention relates to a system for linking video distribution and web content, which enables video content selection in a simpler manner when selecting video content sent from multiple video distribution platforms implemented over a network on a television receiver with different performance and functions, and is suitable for linking video content with web content that provides services such as e-commerce, news, or travel information.

[0017] The system is composed of video platforms with different functions and television receivers with different functions and performance. In such a system environment, the present invention provides a good video viewing environment and further provides advanced services that link videos and Web content.

[0018] The present invention solves these problems by installing a television gateway and linking mobile terminals and television receivers.

[0019] Furthermore, in the present invention, contents from different video platforms are temporarily received by a television gateway. Furthermore, the output from the television gateway is input to a TV cloud connected to televisions having substantially the same performance and functions. Here, the television gateway converts the input from the video platform into a format that can be commonly provided to the TV cloud, and further, the TV cloud generates a screen data configuration that can be selected on the televisions under the management of the connected destination, and forms an online program guide, which is an optimal content selection screen for each television receiver.

[0020] (First embodiment) A first embodiment of the present invention is shown in Fig. 1. What differs from conventional video distribution systems is that servers, a television gateway 121 and TV clouds 131-134, are located between video platforms 111-113 and television receivers 141-150.

[0021] Video content provided by CSPs 101 to 108 and information for content selection are input to a TV gateway 121 by video platforms 111 to 113, respectively. The TV gateway 121 converts information for selecting predetermined video content, and then inputs the information to TV clouds 131 to 134.

[0022] The TV clouds 131 to 134 convert information input to the respective TV clouds 131 to 134 from the TV gateway 121 into data for forming a screen for the television receiver to select content.

[0023] The TV cloud 131 generates and transmits internet program guide data to the television receiver groups 141-143 that are connected to and under its management and have roughly equivalent functions. Similarly, the TV cloud 132 outputs to the television receiver groups 144-145, the TV cloud 133 outputs to the television receiver groups 146-147, and the TV cloud 134 outputs to the television receiver groups 148-150. Each of these television receiver groups is managed as a group having roughly equivalent functions and performance.

[0024] Here, TV clouds 131 to 134 have information on the functions and performance of the televisions to which they are connected, and generate receivable internet program guide data for the television receivers, and each television receiver creates an optimal screen based on that data.

[0025] The above operations enable video content provided by different video platforms to be commonly selected on television receivers having different functions.

[0026] The operation of this system will now be described in detail.

[0027] FIG. 2 shows an example of an internet program guide provided by this embodiment.

[0028] The video platforms 111 to 113 provide the TV gateway 121 with a timetable 201, content metadata 202, and banner data 203, which are information for content selection. These data depend on the video platforms 111 to 113, and are in different formats. Next, the TV gateway 121 converts the timetable 201, content metadata 202, and banner data 203 into common content selection data 204 to supply to each of the TV clouds 131 to 134. Here, the content selection data 204 includes a timetable and channel number for placing a banner, and metadata explaining the content.

[0029] The TV clouds 131-134 that receive the content selection data 204 from the TV gateway 121 generate the net program guide data 210 according to the functions and performance of each TV receiver. At this time, the video content provided by the video platforms 111-113 is assigned to a single or multiple channels, and the user can select video content without being aware of the difference between the video platforms. Such a screen is ultimately configured by the TV receiver's browser based on the net program guide data 210. Here, the metadata includes video and audio format information, and the possibility of playback is determined by comparing it with the information on the functions and performance of the TV receiver. Information on the TV reception functions and performance is held by each TV cloud, and programs that cannot be played are grayed out on the net program guide.

[0030] The details of the above operations are shown in FIG.

[0031] The video platforms 111-113 provide the TV gateway 121 with data sets 301-303 of timetables, content metadata, and banner data. Here, mutual compatibility is not guaranteed for the data sets 301, 302, and 303, and they are provided in different formats. The TV gateway 121 converts these data sets into common content selection data 204. The TV clouds 131-134 receive the content selection data 204 provided by the TV gateway 121, and each TV cloud generates net program guide data 341 and 344. Here, the TV clouds 131 and 134 are shown as examples. For example, the TV cloud 131 generates net program guide data 341 for the connected TV receivers 141-143, and the TV cloud 134 generates net program guide data 344 for the connected TV receivers 141-150. Each TV receiver performs screen presentation based on these data.

[0032] FIG. 4 shows a configuration diagram of a television receiver according to the present invention.

[0033] Broadcasts are received by antenna 1101, and the broadcast content converted into a digital stream by tuner 1102 is converted into audio and video signals by signal processing unit 1103. The audio signal is processed by audio processing unit 1104, and audio is played by speaker 1106. The video signal is processed by video processing unit 1105, and video is played by video display unit 1107. CPU 1109 is connected to memory 1108 and non-volatile memory 1110, and executes a control program (application) to control tuner 1102 and signal processing unit 1103. User operations are input from remote control 1113 to receiving unit 1112, and then input to the control program. Communications interface 1111 receives video content and an online program guide distributed from the network, and processes them using the control program of CPU 1109.

[0034] Fig. 5 shows a configuration diagram of a video platform according to the present invention. A CPU 1202 is connected to a memory 1201 and a storage device 1203, and executes a control program. An operator controls the operation through an operation unit 1205. A communication interface 1204 is connected to a network, and inputs and outputs video content, distributes videos, and inputs and outputs content selection information. A video processing unit 1206 encodes and encrypts the input video content, and generates a stream for video distribution.

[0035] FIG. 6 shows a configuration diagram of a TV gateway according to the present invention.

[0036] The CPU 1302 is connected to the memory 1301 and the storage device 1303, and executes a predetermined processing program. The interface 1304 performs input / output from the video platform and input / output to the TV cloud. The operator controls the operation by using the operation unit 1305.

[0037] Next, a method for transferring network program guide data will be described.

[0038] 7 is a sequence diagram showing the flow of acquiring and displaying a net program guide. As shown in FIG. 7, the exchange of net program guide data between the video platforms 111-113 and the television receivers 141-150 is performed via the television gateway 121.

[0039] The video platforms 111 to 113 upload the net program guide data to a predetermined area (EPG S3) of the TV gateway 121 (step S1). The TV gateway 121 places the uploaded net program guide data in a CDN (Contents Delivery Network) for net program guide data.

[0040] The television receivers 141 to 150 directly access the CDN for net program guide data to acquire the net program guide data (step S2).

[0041] The television gateway 121 issues a TC-ID for identifying each of the TV clouds 131 to 134, issues a PF-ID for identifying each of the video platforms 111 to 113, and issues channel numbers.

[0042] Here, Fig. 8 is a diagram showing an example of reserving IDs for the video platforms 111 to 113 and the TV clouds 131 to 134. As shown in Fig. 8, a TC-ID is reserved for the manufacturer of the television receiver corresponding to each of the TV clouds 131 to 134. Also, as shown in Fig. 8, a PF-ID is reserved for the distribution company of each of the video platforms 111 to 113.

[0043] Fig. 9 shows other IDs. As shown in Fig. 9, the HA-ID, which identifies a home agent, is issued by the manufacturer of each television receiver that owns a TC-ID. The MA-ID, which identifies a mobile agent, is issued by each distribution company that owns a PF-ID. The CS-ID, which identifies a CSP, a video content provider that provides videos belonging to a company, is issued by the distribution company.

[0044] The television gateway 121 creates a list of business information (pfids.json) according to the above PF-ID. The video platforms 111 to 113 create a list of channel information (channels.json) of the assigned channels. In this way, the television receivers 141 to 150 can obtain information on currently valid channels.

[0045] Here, FIG. 10 is a diagram showing an example of the configuration of network program guide data, and FIG. 11 is a diagram showing an example of configuration information of network program guide data.

[0046] As shown in FIG. 10, the video platforms 111 to 113 display program information ( <yyyymmdd>In addition, the video platforms 111 to 113 provide a program information list ( <yyyymmdd>Video information referenced in .json ( <vod-id>.json), series information (<series_ID> .json), advertising information ( <ad-id>Furthermore, the video platforms 111 to 113 create a VOD list (vodlist.json) which is information on programs recommended to the user and is displayed in the past program guide.

[0047] As shown in Figure 11, the configuration information of the Internet program guide data includes, in addition to the above-mentioned program information list, video information, series program information, advertising information, and recommended program information, configuration information, which is setting information, log server access information, a list of operator information, a list of channel information, and program information update information.

[0048] As shown in Fig. 11, among the configuration information of the net program guide data, the creator of the configuration information, log server access information, list of business operator information, and program information update information is the television gateway 121 (referred to as TGW in Fig. 11). Also, among the configuration information of the net program guide data, the creators of the channel information list, video information, series program information, advertisement information, program information list, and recommended program information are the video platforms 111-113 (referred to as VPF in Fig. 11).

[0049] The configuration information (Conf.json) contains, for example, peak_sift information for server access. The configuration information file unit is one in total.

[0050] The log server access information (firehose_params.json) describes access key information for uploading data to the log server (firehose stream) of the TV gateway 121. The log server access information has a single file unit as a whole.

[0051] The operator information list (pfids.json) contains the operator information of the operator distributing the program and the description of the CS-ID for which the operator provides the service. The operator information list is a single file unit.

[0052] List of channel information (<PF_ID> / channels.json) describes channel information (service_id) of the program to be distributed. The file unit of the list of channel information is each video platform 111 to 113 (denoted as VPF in FIG. 11).

[0053] Video information ( <vod-id>The file (.json) is referenced in the Internet program guide data and contains information about the videos to be distributed. Each piece of program information is composed of video information, and the video to be played is always played after checking the contract status based on the video information and the video type. Information with viewing restrictions is not displayed on the screen until the viewer's consent is obtained. The file unit for video information is each video platform 111-113 (referred to as VPF in FIG. 11).

[0054] Series program information (<Service_id> In the file (.json), a list for collecting serial dramas and related programs is written by Service_id (series identification unit), and VOD-IDs are arranged in the order of episode numbers. The file unit of the series program information is each video platform 111 to 113 (written as VPF in FIG. 11).

[0055] Advertising information ( <ad-id>.json) contains information that guides viewers to recommended programs on the screen at specified times during the program broadcast. <ad-id>.json) is not presented in the Internet program guide. The file unit of the advertisement information is each video platform 111 to 113 (indicated as VPF in FIG. 11).

[0056] Program information list ( <yyyymmdd>The program information list file (.json) contains a list of program information for the 15-day period displayed in the online program guide, organized by date. The program information list file is organized by service_id and day.

[0057] When the above-mentioned viewing age restriction setting is valid, a program for which the video information it refers to is restricted is not presented in the program guide as is, but is presented after obtaining the user's permission.

[0058] The recommended program information (vodlist.json) lists the VOD-ID list of VODs recommended by each operator. The file unit of the recommended program information is each video platform 111 to 113 (indicated as VPF in FIG. 11).

[0059] Program information update information (<service_id> _lastupdated.json) contains a program information list ( <yyyymmdd>This contains program information update information, which is information on the date and time when the program information update file (.json) was updated. The program information update file is stored on a service_id basis.

[0060] Incidentally, the television gateway 121 distributes a client_ID (PF-ID) and a client_secret as credentials to the video platforms 111 to 113 in advance.

[0061] Video platforms 111 to 113 use client_ID (PF-ID) and client_secret to create a program information list ( <yyyymmdd>.json) is uploaded to a specified area (EPG S3) of the TV gateway 121 (step S1).

[0062] When the TV gateway 121 detects that the video platforms 111 to 113 have uploaded the internet program guide data, the TV gateway 121 transmits program information update information (<service_id> _lastupdated.json) is generated for each channel (service_ID) and placed on the CDN for online program guide data together with the online program guide data.

[0063] Program information update information (<service_id> _lastupdated.json) is generated by the TV gateway 121 for each channel (Service_id) and placed in the CDN for internet program guide data.

[0064] The program information update information is stored in a predetermined area uploaded by the video platforms 111 to 113 and in a CDN arranged by the TV gateway 121. Among the daily program information update information data, the TV gateway 121 can delete data that is eight days or older.

[0065] The TV gateway 121 is a <ad-id>.json) and video information ( <vod-id>.json), series information (<Service_id> Regarding the file format (.json), when the video platforms 111 to 113 delete data in a predetermined area, the data in the CDN can be deleted.

[0066] The contents of the program information update information are as follows. { <yyyymmdd>: <Last update date and time (Epoch)>, <yyyymmdd>: <Final update date and time (Epoch)>, <yyyymmdd>: <Final update date and time (Epoch)>, <yyyymmdd>: <Final update date and time (Epoch)>, <yyyymmdd>: <Last updated date and time (Epoch)>, (lasts for 15 days) }

[0067] If the program information update information does not exist, the value of the last update date and time is set to 0.

[0068] The television gateway 121 generates an authentication key (API_key) for acquiring network program guide data to acquire program information update information. The television gateway 121 creates an IAM user with authority to access network program guide data, and updates and acquires the authentication key (API_key) for acquiring network program guide data every 12 hours. The authentication key (API_key) for acquiring network program guide data is valid for 24 hours. The authentication key (API_key) for acquiring network program guide data is discarded 24 hours after it is created. The authentication key (API_key) for acquiring network program guide data is updated periodically and in common regardless of the video platforms 111 to 113 or the channel.

[0069] The TV clouds 131 to 134 obtain an authentication key (API_key) for acquiring network program guide data from the TV gateway 121 every 12 hours, and allow the TV receivers 141 to 150 under their control to acquire the data.

[0070] The television receivers 141 to 150 add an authentication key (API_key) for acquiring network program guide data to the x-api-key header via https, and acquire program information update information.

[0071] The video platforms 111 to 113 usually update the program information update information about once a day. Note that the video platforms 111 to 113 can also update the program information update information at any time.

[0072] The television receivers 141 to 150 periodically receive program listing data from the CDN of the television gateway 121.<service_id> By checking _lastupdated.json, you can detect when program information has been updated.

[0073] The load leveling units 1109a of the television receivers 141-150, details of which will be described later, calculate device-specific access_shift_time in order to avoid concentration of access from the television receivers 141-150 to the television gateway 121 (step S3). Then, the load leveling units 1109a of the television receivers 141-150, details of which will be described later, reflect the access_shift_time when subsequently acquiring network program guide data, acquiring mpd, and uploading logs.

[0074] The load leveling unit 1109a of the television receivers 141 to 150 also determines the check time (epg_update_check_time) for updating the network program guide so as to avoid concentration of accesses to the television gateway 121 (step S3), as will be described in detail later.

[0075] The television receivers 141 to 150 link the PF-ID and MA-ID on the television gateway 121 by performing a cooperative operation with the applications of the video platforms 111 to 113.

[0076] The TV clouds 131 to 134 hold the linking status for each of the television receivers 141 to 150, and enable the television receivers 141 to 150 to obtain information.

[0077] The television receivers 141-150 can change the way in which they display the Internet program guide depending on the state of cooperation with the video platforms 111-113.

[0078] The program information and video information may include information on "viewing age restriction setting." If the user can set the viewing age restriction on the television receivers 141-150, the television receivers 141-150 impose a viewing age restriction when displaying the Internet program guide or playing a program in accordance with the viewing age restriction setting. It is desirable that such viewing age restrictions can be released by a user operation such as entering a PIN code.

[0079] Next, a method for displaying network program guide data will be described.

[0080] Internet program information can be displayed for 15 days, including the past week, the present, and the future week. <yyyymmdd>.json contains one day's worth of data. <yyyymmdd>The .json contains the start time.

[0081] When displaying the Internet program guide, the television receivers 141-150 display only the current program guide, starting from the youngest channel, for the first time. The television receivers 141-150 store the last channel played. In addition, the television receivers 141-150 focus on the last channel played from the second time onwards.

[0082] If the last channel played back is a linear channel content (a program with a fixed broadcast time), the television receivers 141 to 150 display the current program of the PF-ID and service_id of the last channel played back.

[0083] If the last played channel is VOD (Video On Demand), the television receivers 141 to 150 display the PF-ID, service_id, and event_id of the last played channel. If the event_id is beyond the display range of 15 days, the television receivers 141 to 150 display the oldest event_id of the same channel.

[0084] The display order is determined by the specifications of the manufacturers of the television receivers 141-150.

[0085] In addition, the operation specifications on the Internet program guide can be freely set by the manufacturers of the television receivers 141 to 150.

[0086] However, when the television gateway 121 serving as a server is provided as described above, the television gateway 121 receives information including content information from the video platforms 111-113 that aggregate and distribute content information from content service providers, and converts the received content information so that it can be received by the television receivers 141-150, there are problems as follows. When the television gateway 121 serving as a server is provided, for example, when playing back content on a linear channel, the broadcast time is fixed, so access from the television receivers 141-150 to the television gateway 121 serving as a server is concentrated. Therefore, the television gateway 121 serving as a server needs to be designed to match the peak of concentration of access from the television receivers 141-150, which results in high costs.

[0087] Therefore, in the television receivers 141 to 150 of this embodiment, the CPU 1109 executes the application to function as a load leveling unit 1109a. The load leveling unit 1109a distributes the access time of access to the television gateway 121, thereby avoiding concentration of access to the television gateway 121, which is a server. The process of avoiding concentration of access to the television gateway 121 will be described below.

[0088] During linear channel playback, the television receivers 141-150 acquire advertisement information from the mpd of the video platforms 111-113 and the CDN for the Internet program guide data of the television gateway 121. At this time, in order to avoid concentration of access to the television gateway 121, the load leveling units 1109a of the television receivers 141-150 shift the access time and operate using information unique to each television receiver 141-150.

[0089] The television receivers 141-150 obtain a reference value for calculating the access shift time (access_shift_time) from the configuration information (Conf.json) stored in the CDN for the network program guide data. The television receivers 141-150 check the configuration information (Conf.json) when the network program guide is started. If the reference value in the configuration information (Conf.json) has been updated, the television receivers 141-150 perform recalculation.

[0090] The access shift time (access_shift_time) is a presentation shift time of linear channel content. In order to prevent all television receivers 141-150 from accessing the linear channel at a fixed time and from concentrating access to the television gateway 121, the access shift time shifts the program presentation time for each television receiver 141-150 within a fixed time.

[0091] Fig. 12 is a diagram showing a peak_shift key object of the Configuration information. The television receivers 141 to 150 acquire the Configuration information (Conf.json) arranged in the CDN for the network program guide data of the television gateway 121. Then, as shown in Fig. 12, the television receivers 141 to 150 execute the shift within the range of the video maxdelay (seconds) in the peak_shift key object of the Configuration information (Conf.json). For example, the television receivers 141 to 150 execute the shift within a range of about 10 ms, and each television receiver 141 to 150 accesses at a different time.

[0092] An example of the calculation of the access shift time (access_shift_time) is shown below. access_shift_time=(int)(random number%(D*100+1)); / / 10ms D: Maximum delay time peak_shift.Video.maxdelay(second) U: Unique information possessed by a television receiver (ex. TV-ID (identification information assigned to each television receiver)) Set U(TV-ID) as the random number seed

[0093] The access time to the TV gateway 121 is determined by the following formula: Access time = S + access_shift_time * 10ms S:Start time

[0094] In addition, the load leveling units 1109a of the television receivers 141 to 150 also shift the update check times for the network program guide data so that concentration of accesses to the television gateway 121 does not occur.

[0095] The television receivers 141 to 150 periodically check whether the video platforms 111 to 113 have updated the net program guide by receiving program information update information (<service_id> In order to prevent such a concentration of accesses to the television gateway 121 for obtaining information, the television receivers 141 to 150 are controlled so that each television receiver accesses at a different time.

[0096] The television receivers 141 to 150 execute the shift within the range of the maxdelay (seconds) of the epg in the peak_shift key object of the configuration information (Conf.json) as shown in Fig. 12. For example, the television receivers 141 to 150 execute the shift within a range of about 10 ms, and each television receiver 141 to 150 accesses the television gateway 121 at a different time.

[0097] An example of calculating the network program guide data update check time (epg_update_checktime) is shown below. epg_update_check_time=(int)(random number%(P*100+1)); / / 10ms P: Check interval peak_shift.epg.maxdelay (second) U: Unique information of the TV receiver (e.g., TV-ID (identification information individually assigned to the TV receiver)) Set U (TV-ID) as the seed of the random number

[0098] Then, TV receivers 141 to 150 check at the following times every hour. checktime=epg.maxdelay*i*1000+epg_update_check_time*10; checktime (ms) n=(60 / epg.maxdelay); From i = 0 to i < n epg.maxdelay: A value that can evenly divide 60 minutes within one hour

[0099] In addition, the load leveling unit 1109a of TV receivers 141 to 150 also shifts the log collection time so that access concentration to the TV gateway 121 does not occur.

[0100] Here, the log collection method will be described. As described above, TV receivers 141 to 150 upload data (logs) to the log server (firehose stream) of the TV gateway 121 (step 4).

[0101] First, define the transmission interface of the measurement log to the TV gateway 121. This interface is used by applications on TV receivers 141 to 150 (the electronic program guide application and the HTML5 application for video distribution).

[0102] The timing of transmission to the TV gateway 121 depends on the service operation. However, in order to avoid concentration of access, in this embodiment, the time is shifted in each of the TV receivers 141 to 150 based on the time shift information from the TV gateway 121, and multiple logs are transmitted collectively.

[0103] First, device authentication will be described.

[0104] The television gateway 121 creates an IAM user that can only upload data to the television gateway 121's log server (firehose stream). The television gateway 121 generates an access key (a pair of an access key ID and a secret access key) for the IAM user once every 12 hours and deletes it after one day. This ensures that there are always two valid access keys. The television gateway 121 places information for uploading data to the television gateway 121's log server (firehose stream), including the generated access key, as a JSON file (firehose_params.json) in the same location as the Internet program guide data.

[0105] An example of a JSON file (firehose_params.json) is shown below. Note that the access key should be the newest of the two valid access keys. { "access_key_ID":<access key ID> , "secret_access_key":<secret access key> , "region": "ap-northeast-1", "stream_name":<firehose stream name> , "expires_in": 43200, "scope": "activity_log" }

[0106] Each of the television receivers 141 to 150 acquires the JSON file (firehose_params.json) in the same manner as acquiring the Internet program guide data. Since each of the television receivers 141 to 150 guarantees that the JSON file (firehose_params.json) is valid for the number of seconds (here, 43200 seconds, or 12 hours) written in "expires_in" after the JSON file (firehose_params.json) is acquired, the JSON file (firehose_params.json) is stored locally for that period.

[0107] When log upload is required, the television receivers 141 to 150 perform authentication using a JSON file (firehose_params.json) and transmit the log data to the log server (firehose stream) of the television gateway 121.

[0108] If the validity period has expired when the log data is transmitted, the television receivers 141 to 150 acquire the JSON file (firehose_params.json) again from the television gateway 121 and update the information.

[0109] Next, the timing of uploading will be described.

[0110] Each of the television receivers 141 to 150 temporarily buffers log information generated in order to level the load on the log server, rather than uploading the log information to the log server (firehose stream) of the television gateway 121 each time the information is generated.

[0111] Each of the television receivers 141 to 150 refers to the peak_shift.log element of the configuration information (Conf.json) prepared by the television gateway 121 on the CDN at startup.

[0112] Below is an example of the peak_shift.log element in configuration information (Conf.json). { peak_shift:{ video:{maxdelay:120,lastupdated: <epoch>}, log:{maxdelay:1800,maxsize:4000,lastupdated: <epoch>}, ... } ... }

[0113] maxdelay is server access distribution setting information, and indicates the maximum time (seconds) for which logs should be retained. maxsize is setting information related to data retention, and indicates the maximum capacity (bytes) of logs to be retained. These values ​​are not hard limits, and the television gateway 121 accepts uploads even if they are exceeded. On the other hand, the load leveling unit 1109a of each television receiver 141-150 attempts to upload promptly when the log retention time is about to exceed maxdelay or the log retention capacity has exceeded maxsize. Also, when logs cannot be retained up to close to maxsize due to restrictions on the local storage capacity of each television receiver 141-150, the load leveling unit 1109a of each television receiver 141-150 may upload regardless of maxsize, but will endeavor to retain up to each maximum value as much as possible in order to reduce the load on the log server (firehose stream) of the television gateway 121.

[0114] If the log cannot be uploaded due to a communication failure or the like, the load leveling unit 1109a of the television receivers 141 to 150 holds the log exceeding the maxdelay and maxsize limits. The load leveling unit 1109a of the television receivers 141 to 150 uses exponential backoff for retries and does not retransmit unnecessarily.

[0115] As described above, according to this embodiment, the access times of server accesses are distributed based on the unique information possessed by the television receiver, so that concentration of accesses to the server can be avoided.

[0116] The load leveling unit 1109a of the television receivers 141 to 150 may change the setting information related to data retention and the setting information related to the server access distribution setting information (Configuration information) according to the service status and the access status. This makes it possible to reliably avoid concentration of access to the server according to the service status and the access status.

[0117] Second Embodiment FIG. 13 shows a second embodiment according to the present invention.

[0118] In this embodiment, mobile terminals 401 to 410, a viewing data storage unit 451, an ID combination information storage unit 452, a content recommendation information storage unit 453, a recommended advertisement selection and insertion unit 454, and an advertisement server 455 are added to the first embodiment.

[0119] In this embodiment, the operations up to the generation of the network program guide are the same as those in the first embodiment, but the television receivers 441-450 and the mobile terminals 401-410 are linked by their respective IDs (individual identification data). Also, each television receiver 441-450 has a function of measuring what the user is watching as viewing data, and the measured viewing data is uploaded to the television gateway 421 via the TV clouds 431-434.

[0120] The television gateway 421 is coupled to a viewing data storage unit 451 and an ID combination information storage unit 452. Viewing data obtained from the television receivers 441-450 is stored in the viewing data storage unit 451 via the TV clouds 431-434 and the television gateway 421. In addition, combined information of the IDs of the television receivers 441-450 and the mobile terminals 401-410 is supplemented in the ID combination information storage unit 452.

[0121] The content recommendation information storage unit 453 calculates what content viewing tendency each television receiver has based on the information in the viewing data storage unit 451 and the ID combination information storage unit 452, and notifies the video platforms 411 to 413. This calculation is realized by measuring the viewing time of each content genre for each viewing.

[0122] On the other hand, the recommended advertisement selection and insertion unit 454 calculates which television receiver should insert what advertisement from the viewing data storage unit 451 and the ID combination information storage unit 452, obtains the desired advertisement from the advertisement server 455, and inserts the advertisement into the video content of the video platforms 411 to 413.

[0123] FIG. 14 shows an example of the ID configuration and binding in the present invention. The mobile terminals 401 to 410 have an SP-ID (smartphone ID) 501. On the other hand, the television receivers 441 to 450 have a TV-ID (television ID) 511. The SP-ID is composed of a PF-ID, which is an ID of a video platform, and a UR-ID, which is an ID of a user. The TV-ID is composed of a TC-ID, which is an ID of a TV cloud, and a DV-ID, which represents the television receiver itself as a device. The ID binding information storage unit 452 has a table 520 showing the binding information of the SP-ID and the TV-ID, and the television receiver and the mobile terminal form a linked state by the ID. Here, in the table 520, a "circle" indicates a linked state, and a "-" indicates a non-linked state. Here, there is a possibility that a plurality of mobile terminals are linked to one television receiver.

[0124] Figure 15 shows the ID combination method and the data stored in each.

[0125] The television receiver 141 and the mobile terminal 401 such as a smartphone transmit an authentication code 611 to the mobile terminal 401 using a QR code (registered trademark) or the like displayed on the television receiver. A correspondence table between this authentication code and television is stored in advance in the TV ID storage unit 603 of the TV cloud 431.

[0126] The authentication code 611 is a time-limited authentication code corresponding to a TV-ID individually assigned to the television receiver 141. This authentication code 611 is sent from the TV cloud 431 to the television receiver 141. At this time, the TV cloud 431 adds address information for connecting to the video platform 411 together with the authentication code 611 and sends it to the mobile terminal 401.

[0127] The authentication code 611 is sent from the smartphone 401 to the video platform 411 as data 612 together with the SP-ID of the mobile terminal. The video platform 411 acquires user attributes from its customer data storage unit 601 based on the acquired authentication code 611 and the SP-ID of the linked mobile terminal 401, combines it with the SP-ID and transmits it to the television gateway 421 as data 613.

[0128] The TV gateway acquires the authentication code, SP-ID, and user attributes as data 613, and then queries the TV cloud 431 based on the authentication code to acquire the corresponding TV-ID. Here, the TV cloud 431 manages the TV-IDs of the television receivers under its management, has a correspondence table between TV-IDs and authentication codes in the TV ID storage unit 602, and acquires which television receiver is the target of binding from the authentication code. The authentication code placed in data 612 and data 613 is the same as the authentication code 611.

[0129] Through these operations, the television gateway 421 combines the TV-ID and the SP-ID, and stores the combined TV-ID and SP-ID in the ID combination information storage unit 602. Furthermore, the combined TV-ID and SP-ID information is notified to the video platform 411 by a passkey 621. The passkey 621 serves as a key to the database of the ID combination information storage unit 602, and by sending the passkey 621 to the television gateway 613, the SP-ID, TV-ID, and user attributes can be extracted.

[0130] Through the above operations, the mobile terminal and the television receiver are linked by the ID. After the ID binding, the video platform 411 can provide services to the target television receiver using the passkey 621 transferred from the television gateway 421 to the video platform 411. The passkey 621 is stored in the customer data storage unit 601 so that the correspondence with the SP-ID can be known.

[0131] Although FIG. 15 has been described with reference to the video platform 411, the video platforms 412 and 413 also perform the same operations.

[0132] Figure 16 shows the network program guide when IDs are combined.

[0133] When the TV-ID and SP-ID are combined, it is possible to determine which video platform the viewing user is a customer of by the PF-ID, which is a component of the SP-ID, and therefore the channels configured by the corresponding video platform are presented in an easily accessible position on the Internet program guide. For example, in the case of Fig. 16, when the ID of the video platform 411 is included in the SP-ID 501, the channels provided by the video platform 411 are presented as the initial screen, making it easy for the user to select. In addition, recommended contents 701, 702, and 703 are simultaneously displayed by inferring viewing trends from viewing data of the television receiver identified by the TV-ID.

[0134] In this way, by binding the ID, the content of the corresponding video platform is preferentially presented to the user, so that the user can easily obtain the services provided by the video platform.

[0135] FIG. 17 shows an example of a screen display in which video content and a Web service are linked.

[0136] When TV-ID511 and SP-ID501 are in a combined state, a web service screen linked to the video platform indicated by SP-ID501 is automatically displayed on the television receiver indicated by the TV-ID. This allows the user to receive services such as related information and product explanations on an EC site as well as video viewing. In addition, the mobile app 812 and video screen 811 displayed on the mobile terminal can be linked, enabling a video content selection method that cannot be achieved with a normal remote control. For example, by touching an interesting news item on a news site of the mobile app on the mobile terminal, the related video content can be played on the television receiver, enabling unprecedented content selection. On the other hand, by displaying an EC site on the mobile app and tapping an interesting product, a user can get an unprecedented user experience, such as viewing a detailed product explanation in a video.

[0137] The above operation will be explained in detail with reference to FIG.

[0138] When video content of the video platform 411 is linked to a website 901, web link information 902 is input from the video platform 411 to the television gateway 421. Also, recommended content data 901 is input to the television gateway 421 in addition to the conventional timetable 201, content metadata 202, and banner data 203.

[0139] The television gateway 421 transfers the combined TV-ID 501 and content selection data 204, as well as recommended metadata 911 created from the recommended content data 901 and a link destination URL obtained from the Web link information to the TV cloud 431. The TV cloud 431 generates an Internet program guide together with recommended content display data 913, and sends it to the television receiver 441. At that time, the link destination URL is set in the television receiver 441 together with channel and time information so that it can be linked to video content. The television receiver 441 displays the Web content indicated by the link destination URL on the television screen when the user presses a link button or the like based on a specific channel and the time period being viewed.

[0140] When linking with a mobile app, after the mobile app is downloaded from website 901 to mobile terminal 401, the operation result of the mobile app and the SP-ID are sent to video platform 411. After that, the video platform 411 sends a passkey and mobile operation to television gateway 421, which converts it into a common operation code 903 for television, which is further converted into a television operation code by TV cloud 431 to control the television receiver 441. The passkey is obtained from customer data storage unit 601, which is a correspondence table with SP-IDs.

[0141] Although the above has been described with respect to the video platform 411, the same operation applies to other video platforms. Also, the same operation applies to TV clouds other than the TV cloud 411 and television receivers other than the television receiver 441.

[0142] FIG. 19 shows an explanation of content recommendation and advertisement insertion based on the present invention.

[0143] The information in the viewing data storage unit 451 and the ID combination information storage unit 452 is input to a content recommendation information storage unit 453, which calculates television viewing trends and determines recommended content and desirable advertisement candidates. Based on the information in the content recommendation information storage unit 453, recommended advertisements are obtained from an advertisement server 455, and based on the output of a recommended advertisement selection and insertion unit 454, the video platform 411 inserts advertisements into video content.

[0144] On the other hand, the receiver-side advertisement insertion unit transfers desirable advertisements from the advertisement server 455 based on the information in the content recommendation information storage unit 453, and inserts advertisements into the operating content in the television receiver 141 based on the output of the receiver-side advertisement insertion unit 456.

[0145] For example, when the video platform 411 distributes video by multicasting, it is not possible to insert individual advertisements for each television receiver. In this case, the video platform 411 first inserts advertisements and distributes a common advertisement, and then the television receiver overwrites the advertisement with an advertisement that is individually desired. This operation makes it possible to present advertisements suited to the user, such as targeted advertisements, to individual television receivers.

[0146] (Third embodiment) FIG. 20 shows a configuration diagram of a third embodiment according to the present invention.

[0147] The difference from the second embodiment is that conversion units 1411-1413 are inserted between the video platforms 411-413 and the television gateway 1412. In this embodiment, different data output from different video platforms 411-413 is converted into common data by the conversion units 1411-1413 in advance, and then input to the television gateway 1412. This process allows the television gateway 1412 to process common data, thereby reducing the processing load. The conversion units 1411-1413 may be provided in the television gateway 1412 as an input interface of the television gateway 1412, or may be provided in the video platforms 411-413 as an output interface of the video platforms 411-413.

[0148] In the second embodiment, different data is directly input from the video platforms 411 to 413 and is internally converted to common data, whereas in the third embodiment, conversion to common data is requested to each of the video platforms 411 to 413. This makes it possible to distribute the load.

[0149] FIG. 21 is a diagram illustrating the operation of the third embodiment according to the present invention.

[0150] 18, the difference from the operation description of the second embodiment is that a conversion unit 1411 is inserted. Data conversion is performed by the conversion unit 1411, and common banner data 1503, common content data 1501, and common Web link information 1502 are input to the television gateway 421.

[0151] These converted data are converted into data of a common format by the converters 1411 to 1413 on all the different video platforms 411 to 413 .

[0152] The mobile terminals 401 to 410 in the first to third embodiments are defined as network-connectable devices including cameras, and also include computer terminals such as smartphones, personal computers, laptop computers, and desktop computers.

[0153] In the first to third embodiments, the QR code is displayed on the television receivers 141-150, 441-450 to link the mobile terminals 401-410 and the television receivers 141-150, 441-450, but other than the QR code may be used. For example, a group of numbers such as a PIN code or a barcode may be optically detected by the mobile terminals 401-410 to detect address information for connecting to the video platform 411 together with the authentication code 611. Furthermore, although an example of optical detection has been given in the above embodiments, a function for linking between the mobile terminals 401-410 and the television receivers 141-150, 441-450 may be used. For example, address information for connecting to the video platform 411 together with the authentication code 611 may be sent by wireless connection or wired connection. [Industrial Applicability]

[0154] This technology can be applied to the application of presenting content to all television receivers through input of a single format, even if the television receivers have different capabilities and functions and their video platforms are different. In addition, by linking television receivers with mobile terminals, this technology can be applied to advanced services via mobile terminals, and furthermore, by linking with mobile terminals such as smartphones, this technology can be applied to the application of advanced linked operations that are not possible with existing remote controls. [Explanation of symbols]

[0155] 101~108 CSP 111~113, 411~413 Video Platform 121, 421 TV Gateway 131, 431~434 TV Cloud 141~150, 441~450 TV receiver 401~410 Mobile devices 1109a Load Leveling Section 1411~1413 Conversion section< / epoch> < / epoch> < / yyyymmdd> < / yyyymmdd> < / yyyymmdd> < / yyyymmdd> < / yyyymmdd> < / yyyymmdd> < / yyyymmdd> < / yyyymmdd> < / yyyymmdd> < / yyyymmdd> < / yyyymmdd> < / yyyymmdd>

Claims

1. A television receiver that receives content information distributed via a server, a load leveling unit that levels the load on the server based on unique information held by the television receiver; A television receiver comprising:

2. The load leveling unit sets the unique information as setting information and changes the unique information according to a situation.

2. A television receiver according to claim 1.

3. the load leveling unit shifts a time at which the television receiver accesses the server to a time different from that of other television receivers based on unique information possessed by the television receiver; 3. A television receiver according to claim 1 or 2.

4. the load leveling unit uses identification information individually assigned to the television receiver as the unique information; 4. A television receiver according to claim 3.

5. the load leveling unit shifts a time at which the server is accessed to a time different from that of other television receivers in order to acquire content information from the server; 5. A television receiver according to claim 3 or 4.

6. the load leveling unit shifts a time at which it accesses the server to a time different from that of other television receivers in order to check for updates of content information from the server; 6. A television receiver according to any one of claims 3 to 5.

7. the load leveling unit temporarily buffers the data when uploading the data to the server, using at least one of setting information regarding data retention and server access distribution setting information as the unique information; 3. A television receiver according to claim 1 or 2.

8. the load leveling unit uses at least one of a maximum time for which data should be held and a maximum capacity of data to be held as the unique information; 8. A television receiver as claimed in claim 7.

9. a server that converts content information received from the video platform and distributes the converted content information to a television receiver; A television receiver according to any one of claims 1 to 8, which receives content information distributed via the server; A television system comprising:

Images