Embodiments described herein relate generally to an electronic device and a value exchange method.
Electronic devices which receive and store programs supplied by broadcasters and distributors and reproduce them in response to a user's request, for example, a recorder device (hereinafter, referred to as a client terminal or a user) which connects with a television reception device or a monitor (display) device, are capable of receiving (acquiring) and transmitting (supplying) various kinds of information via a network such as the Internet.
Information supplied (transmitted) by the user (client terminal) is often, for example, the user's taste and an access history using the Internet, etc., which are associated with video reproduced (recorded) by the user, etc. Information acquired (received) by the user is often, for example, a broadcast schedule (program table) of a program to the user's taste and information on a site on the Internet, etc.
The above-described supply of information (metadata) to the user and acquisition of information (taste, history) from the user in a network are managed by a metadata creation mechanism (data supply source).
Thus, reception or exchange of values is necessary between the user and the data supply source.
However, a method of exchanging (receiving) values between the user and the data supply source is not clearly specified at present. Delivery (supply and acquisition) of information between the metadata supply source and the user is often carried out by way of, for example, a social networking service (SNS) mechanism, a (taste information) database holding mechanism (management company) holding taste information of the user, etc., and the user does not need to be conscious of direct delivery of information to and from the metadata supply source.
A general architecture that implements the various features of the embodiments will now be described with reference to the drawings. The drawings and the associated descriptions are provided to illustrate the embodiments and not to limit the scope of the invention.
Various embodiments will be described hereinafter with reference to the accompanying drawings.
In general, according to one embodiment, a value exchange method for use in a data management device which connects with a data supply source via a network comprising: calculating a first value corresponding to information which is received from the data supply source and includes metadata extracted with a specific condition with respect to a video program and a second value corresponding to information which is supplied to the data supply source and includes history information associated with a result of viewing or recording of a video program identified by the metadata based on a prescribed value determination condition, and determining a difference between the first value and the second value as an exchange value.
Embodiments will now be described hereinafter in detail with reference to the accompanying drawings.
The external service mechanism (server/servers) 1, . . N may be generically called, for example, a cloud service (1001).
The electronic apparatus 101 will be described taking a digital television broadcast reception device (hereinafter, referred to as a television device) capable of receiving and reproducing (and recording) a digital broadcast (program) as an example. The television device 101 includes a combination of a monitor (display) device and a recorder device connected therewith, etc. Although
The external service mechanism 1, . . N include, for example, a history (taste information) server 1, an EPG server (database) 2, a calendar/channel data server (database) 3, an automatic recording recommendation server 4, a data supply source (metadata) server 5, etc. The history server 1 and the automatic recording recommendation server 4 (or the EPG server 2) are often run by, for example, manufacturers (makers) of the television device 101 or entrusted companies. On the other hand, the data supply source (metadata) server 5 is generally prepared and managed (run) by a metadata creation mechanism (metadata creation company). The EPG server 2 or the calendar/channel data server 3 may be prepared and managed (run) by an independent enterprise.
The history (taste information) server 1 holds the user's taste, for example, information on a program the user has viewed or recorded (reproduced), i.e., a history (log data), etc. The history server 1 also acquires an access history of a site accessed by the television device 101, information on settlement of merchandise purchased in an accessed site/purchase of a ticket for a concert, etc./accommodation arrangements, and the like.
The EPG server 2 acquires information on a program received by the television device (user) 101 independently of (direct) reception by television device 101, and holds it as a database (DB).
The calendar/channel data server (database) 3 holds a broadcasting date and time of a program for which the user has made a recording reservation, a name of a broadcast station (channel) in an area where the user can receive (view/record) and a name of a channel supplied by distributors, a broadcasting schedule of other stations whose broadcasting time overlaps partly with that of a program for which the user has made a recording reservation, rebroadcast information (including a program for which the user has made a recording reservation), and the like.
The automatic recording recommendation server 4 extracts and holds a program which is viewed by the user and held by the history server 1 or a program associated with a program for which the user has made a recording reservation, in order to recommend the user to view or record a program conforming to the user's taste.
The data supply source (metadata) server 5 holds data which is prepared and managed by the metadata creation mechanism (metadata creation company) that handles various kinds of information related to broadcast, i.e., metadata.
Delivery of data between the television device 101 and the history server 1, i.e., supply (transmission) of information from the television device 101 to the history server 1 and acquisition (reception) of information by the television device 101 from the history server 1, are handled by a data controller (control device) 111.
The data controller 111 connects with a table (rewritable data holder) 110. The table 110 holds the rules concerning reception of values between the data supply source server 5 and the user for acquisition of information (taste, history) by the data supply source server (data supply source) 5 from the user (television device) 101 and supply of information (metadata) from the data supply source server 5 to the user, for example, a program (computation expression), a reference table or the like for computing a value making a comparison between a value of information supplied acquired by the user and a value of information supplied to the data supply source server 5.
The data controller 111 also handles delivery of data between the external service mechanisms 1, . . ., N, i.e., between the history server 1, the EPG server 2, the calendar/channel data server 3, the automatic recording recommendation server 4 and the data supply source (metadata) server 5. The data controller 111 also handles recommendation processing of receiving a recommendation from the user and processing it as taste information (has a function as a recommendation processing engine [RE]).
In addition, the data controller 111 controls connection and data delivery between an arbitrary site (Web page) located on the Internet network 11, and the electronic device (user) 101.
As shown in
For access to and from the data controller 111, the television device 101 holds, for example, a cloud application (HTML/JS/CSS) whose example is shown in
The cloud application (HTML/JS/CSS) 103 includes, for example, a “Controller” 104 carrying out key event (core) processing, a “View” 105 carrying out screen display, a “model” 106 carrying out information acquisition from an arbitrary server (external service mechanism) 1, . . N connected through DTVMW (path to and from a browser [the Internet network 11]) and the Internet network 11, and operation of the television device 101, etc. The television device 101 includes a cloud module (CESI) 107 performing data delivery (transmission of taste information and a viewing/recording reservation, acquisition of automatic recording recommendation service information, access to facilities and distribution that have appeared in a program, etc.) between the history server 1, the EPG server 2 and the automatic recording recommendation server 4 through a network, a data processing (storage and reproduction) module 108 performing recording and reproduction of a program, search for a program and a scene/keyword (merchandise), etc., an operation input module (remote control reception module) 109 receiving input of an instruction by an operator, etc. The operation input module 109 may be, for example, a portable terminal device prepared with a predetermined application (software) to enable the operation of the television device 101 to be controlled, for example, a tablet device, a multifunctional communication terminal device (smartphone), etc.
The television device 101 transmits an IP address of the television device (itself), taste information, etc., to the automatic recording recommendation server 4 via the Internet network 11.
The automatic recording recommendation server 4 refers to a keyword input from the television device 101, program search information (date and time/channel) and user information (taste which can be estimated from a program recorded/reproduced previously) held by the history server 1, carries out matching with program information held by each of the EPG server 2, the calendar/channel data server 3 and the data supply source (metadata) server 5, i.e., extraction of an automatic recording recommendation program to the television device 101 (user), and supplies information on a matched program to the television device 101. Metadata held by the data supply source server 5 includes broadcast history data, merchandise data, store data, CM broadcast history data, etc., as shown in
The automatic recording recommendation server 4, whose example is shown in
A function provided by the automatic recording recommendation server 4 will be described. In the following description, the data controller 111 intervenes at the time of data delivery between the television device (user/client terminal) 101 and the automatic recording recommendation server 4 or the metadata server 5. As stated above, the data controller 111 can store, in the history server 1, information supplied (transmitted) from the user (the television device 101) to the metadata server 5 and information supplied from the metadata server 5 to the user (received by the user).
The automatic recording recommendation server 4 acquires various kinds of data described below and supplies them to the television device 101. Various kinds of data include, for example, “scene information”, “automatic recording recommendation” program, etc.
A list of “scene information” of a program matching a condition designated by the user (television device) 101 is acquired. If a plurality of lists of “scene information” matching a designated condition are present, all of them are acquired. If no list of “scene information” matching a condition is present, this fact is notified.
A “table of programs” in which a program whose list of “scene information” of a condition designated by the user (television device) 101 is present is listed is acquired.
A “scene information list table” which is a list of “scene information” registered in a program designated by the user (television device) 101 is acquired.
A list of “scene information” of a designated ID is acquired from “scene information list table”.
A “scene information list” including “scene information” matching a designated search condition is acquired. An arbitrary keyword input by the user can be designated as a search condition.
“Favorite scene information” registered by the user managed by the history server 1, a keyword (metadata) based on the user's taste, etc., are acquired.
Metadata supplied by the metadata server 5 is acquired.
In acquisition of metadata supplied by the metadata server 5, a WebAPI supplied by the metadata server 5 is used.
“Scene information” is created based on metadata acquired from the metadata server 5, or is extracted as an automatic recording recommendation program and is transmitted to the television device 101.
Processing executed at the time of creating “scene information” is shown below.
The metadata server 5 searches a database in the metadata server 5 based on the above-described (a) a program name, (b) a program broadcasting date and time and (c) a channel number received from the television device 101. If a corresponding program whose one or more “scene information” item is registered is present, the metadata server 5 creates the one or more “scene information” item and then transmits it to the television device 101.
If a plurality of corresponding programs are present, the metadata server 5 transmits all candidates to the television device 101.
If no corresponding program is present, the metadata server 5 transmits this fact to the television device 101. That is, the television device 101 transmits identification information (a program name, a program broadcasting date, a channel number, etc.) of a program to the metadata server 5, and receives “scene information” corresponding to a scene in a program from the metadata server 5.
The database in the metadata server 5 is searched for metadata information matching a search condition received from the television device 101, and a list of “scene information” including corresponding metadata information is transmitted to the television device 101. Metadata to be searched for is program broadcast history data, merchandise data, store data and CM broadcast history data shown in
Broadcast history data, merchandise data, store data and CM broadcast history data stored in the database in the metadata server 5 are associated, and “scene information” is created. Merchandise information and store information may not present in one “scene information” item. In addition, a plurality of merchandise data items and store data items may be associated in one “scene information” item.
The automatic recording recommendation server 4 extracts a keyword received from the television device 101 or the history server 1 and the taste of the user (the television device 101) held by the history server 1 (program information of a program the user has viewed or a program for which the user has made a recording reservation, a “keyword” included in the program, or information registered by the user), and sets a search condition.
That is, the automatic recording recommendation server 4 searches the database in the metadata server 5 for metadata information matching a set search condition, and transmits a list of “program” including corresponding metadata information as an automatic recording recommendation list to the television device 101. At this time, if a recording (viewing) reservation has been set in the television device 101, recording (viewing) of a program for which the recording (viewing) reservation has been made is carried out first. Data held by the EPG server 2 and the calendar/channel data server 3 is referred to, and if there is rebroadcast of the same program, a date and time of the rebroadcast is sent to the television device 101 as an automatic recording recommendation program.
Thus, between the user (client/television device) 101, i.e., the data controller 111, and the metadata server (data supply source server) 5, there are acquisition of information (taste, history) by the metadata server 5 from the data controller 111 (the television device 101) and supply of information (metadata) from the metadata server 5 to the user, i.e., delivery of data. Accordingly, it is necessary to receive values between the metadata server 5 and the user (the data controller 111 [the television device 101]).
A value can be appropriately determined on the basis of, for example, a multiplying factor (factor of multiplication) based on the rules of classification [A]-[E] as shown below and the ratio (X) between the number of corresponding users (the number of television devices/the number of viewers) and the number of all users, as shown in
[A] information on a recommendation program (“scene information”) is not used (is not accessed)
[B] information on a recommendation program (“scene information”) is only accessed
[C] a program is viewed (recorded) by using information on a recommendation program (“scene information”)
[D] a program recorded by using information on a recommendation program (“scene information”) is inhibited from being deleted (is protected <is set as an object to be saved for a long time>) and
[E] information in a program viewed (recorded) by using information on a recommendation program (“scene information”) is responded to (a site introduced in a program is browsed).
Thus, if a value (first value) of information supplied by the metadata supply source to the user is large as compared to a value (second value) of information supplied by the user to the metadata supply source, a “difference” between the values is supplied (paid) as a value from the user to the metadata supply source. As a matter of course, if a value (second value) of information supplied by the user to the metadata supply source is large as compared to a value (first value) of information supplied by the metadata supply source to the user, a “difference” between the values is supplied (paid) as a value from the metadata supply source to the user.
The examples shown in
Thus, a difference between values, i.e., an exchange value, is determined by comparing a value (second value) which is determined by the above multiplying factor and should be paid by the user and a value (first value) of information supplied by the data supply source.
The example shown in
The example shown in
A method of determining a value may be set per program or may be set in units of the number of users. For example, if the number of users is used as a unit, a value can occur only if a certain number of users use metadata. In addition, by the classification of rule [E], a value can occur if the contents introduced in a program receive a high response.
As the above-described rules of classification, for example, various conditions as shown below can be set a multiplying factor in accordance with the degree of interest in a program:
The calculation methods shown in
Thus, by adopting the embodiment, between the user and the data supply source, reception of values (or calculation of a value) for both of information supplied by the user and information received by the user from the data supply source can be easily and clearly achieved.
While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions. Indeed, the novel embodiments described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the embodiments described herein may be made without departing from the spirit of the inventions. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the inventions.
This application is a Continuation Application of PCT Application No. PCT/JP2013/059110, filed Mar. 27, 2013, the entire contents of which are incorporated herein by reference.
Number | Date | Country | |
---|---|---|---|
Parent | PCT/JP2013/059110 | Mar 2013 | US |
Child | 14471629 | US |