JP7381013B2 - Point system and receiver - Google Patents

Description

The present invention relates to a point system and a receiver.

Points are awarded when viewing television broadcasts. For example, Patent Document 1 discloses a system for distributing points using digital terrestrial broadcasting or the like and using the points.

Japanese Patent Application Publication No. 2005-258951

However, in the system described in Patent Document 1, points are issued based on point/coupon information added to broadcast data of digital broadcast programs, and points are issued for viewing conventional TV programs. I can't.

The present invention has been made in view of this background, and it is an object of the present invention to provide a technology that can issue points for viewing television programs.

The main invention of the present invention for solving the above problems is a point system that gives points according to the viewing of content broadcast on television, and includes viewing detection that detects that a viewer has viewed the content. a point granting unit that grants points to the viewer according to the manner in which the viewer views the content and attributes of the viewer; A point storage unit that stores points.

Other problems disclosed in the present application and methods for solving the problems will be made clear by the section of the embodiments of the invention and the drawings.

According to the present invention, points can be issued for viewing television programs.

FIG. 1 is a diagram showing an example of the overall configuration of a point system according to the present embodiment. 2 is a diagram showing an example of the hardware configuration of a receiver 2. FIG. 2 is a diagram showing an example of the software configuration of the receiver 2. FIG. 3 is a diagram showing an example of the configuration of a viewing log database 231. FIG. 1 is a diagram showing an example of a hardware configuration of a computer. 3 is a diagram showing an example of the software configuration of a log server 4. FIG. 4 is a diagram illustrating an example of a configuration of a viewing log stored in a viewing log database 431. FIG. 4 is a diagram showing an example of the structure of a point usage log stored in a point usage log database 432. FIG. 2 is a diagram showing an example of a software configuration of a campaign management server 5. FIG. 5 is a diagram illustrating a configuration example of campaign information registered in a campaign database 531. FIG. 3 is a diagram showing an example of a software configuration of a user terminal 3. FIG. 3 is a diagram showing an example of a software configuration of a user management server 6. FIG. 6 is a diagram illustrating a configuration example of a user database 631. FIG. 6 is a diagram illustrating a configuration example of a user history database 632. FIG. 2 is a diagram showing an example of the software configuration of a store terminal 7. FIG. 7 is a diagram illustrating a configuration example of a point usage log stored in a point usage log database 731. FIG. It is a figure showing the flow of registration processing of campaign information. It is a figure showing the flow of login processing to a point system by a viewer. FIG. 3 is a diagram showing the flow of processing for detecting viewing of a television program by a viewer. It is a figure showing the flow of processing which gives points to a viewer. It is a figure explaining the flow of point utilization processing. It is a diagram showing an example of a system configuration when the user terminal 3 estimates viewing.

The contents of the embodiments of the present invention will be listed and explained. A point system and a receiver according to an embodiment of the present invention have the following configuration.

[Item 1]
A point system that awards points according to the viewing of content broadcast on television,
a viewing detection unit that detects that a viewer has viewed the content;
a point granting unit that grants points to the viewer according to the manner in which the viewer views the content and the attributes of the viewer;
a point storage unit that stores the points given to the viewer in association with the content;
A point system characterized by:
[Item 2]
The point system described in item 1,
Information for specifying the content, conditions for the attributes of the viewer to whom the points are to be awarded, point calculation information to calculate the points to be awarded when viewing the content, and the period for which the points are to be awarded. It also includes a campaign management database that remembers the
The point granting unit acquires the point calculation information corresponding to the content viewed by the viewer, the attributes of the viewer, and the date and time of viewing the content from the campaign management database, and based on the point calculation information. calculating the number of points to be awarded to the viewer;
A point system featuring
[Item 3]
The point system described in item 1 or 2,
a usage point acquisition unit that acquires the number of points used by the viewer;
a usage fee output unit that charges a user of the points an amount according to the number of uses and performs calculations related to distribution of the amount;
A point system further comprising:
[Item 4]
The point system described in item 3,
a viewing log storage unit that stores a viewing log of the content viewed by the viewer;
a usage log storage unit that stores a usage log in which the points are used;
an analysis processing unit that analyzes a relationship between viewing the content and using the points based on the viewing log and the usage log, and outputting an analysis result;
A point system further comprising:
[Item 5]
A television broadcast receiver,
a viewing detection unit that detects that a viewer has viewed content broadcast on the television broadcast;
a point granting unit that grants points to the viewer according to the manner in which the viewer views the content and the attributes of the viewer;
a point transmitting unit that transmits the points given to the viewer to a server that manages the points;
A receiver comprising:

==Summary==
Hereinafter, a point system according to an embodiment of the present invention will be described. The point system of this embodiment is applicable to a wide range of stores (including physical stores and online virtual stores) that provide products or services regardless of format to viewers of content broadcast on television. It is intended to award points that can be used in Content includes at least one of television programs and advertisements. Furthermore, in the point system of the present embodiment, a number of points are given according to the viewing mode of the television broadcast by the viewer. In this embodiment, points are awarded in such a way that the longer the viewing time, the more points are awarded, but the viewing mode includes not only the viewing time (how long the viewer watched) but also the number of people watching the video. whether you watched it (alone or with more than one person), whether you watched a particular segment of a TV program, whether you watched a particular advertisement, whether you watched both a television program and an advertisement, or whether you watched a particular television program. Optionally, the manner in which one or more viewers view a television broadcast can be included, such as whether after viewing a program or advertisement, one or more viewers view other particular television programs or advertisements. The source of points is promotional expenses at stores. It can be understood that the viewer will provide a viewing log of what content he/she was watching, and that points will be issued in return for providing the viewing log. Furthermore, the broadcasting station will be paid a usage fee corresponding to the promotional cost as consideration for providing the content.

==Overall configuration==
FIG. 1 is a diagram showing an example of the overall configuration of a point system according to this embodiment.

The receiver 2 is a so-called television, and receives radio waves from TV broadcasts (including electrical signals from cable TV, etc.) (11), decodes the received radio waves, and transmits content such as TV programs and advertisements by decoding the received radio waves. Video and audio can be output. Furthermore, the receiver 2 of this embodiment has a communication function and can communicate with the user terminal 3, the log server 4, the campaign management server 5, the user management server 6, and the like. Note that communication between the receiver 2 and the user device 3 can be wireless communication such as Bluetooth (registered trademark) or WiFi.

The user terminal 3 is assumed to be a mobile terminal such as a smartphone or a tablet computer carried by the viewer. By receiving the message from the user terminal 3 (21), the receiver 2 can determine that the viewer is viewing the content (TV program or advertisement) that the receiver 2 is playing. . The content viewing log by the viewer is sent from the receiver 2 to the log server 4 (24), and is managed by the log server 4.

The broadcasting station 1 sets information (hereinafter referred to as campaign information) for calculating the number of points to be given for each content (12), and this campaign information is managed by the campaign management server 5. The campaign management server 5 can be realized by, for example, a personal computer, a smartphone, a cloud computer, or the like.

The receiver 2 inquires of the campaign management server 5 about the points to be given to the viewer (22), and notifies the user management server 6 of the points (23). Points given to viewers are managed by the user management server 6. The user management server 6 can be realized by, for example, a personal computer, a smartphone, a cloud computer, or the like. The points notified from the receiver 2 are added to the point balance in the user management server 6. The point balance is also referenced from the user terminal 3 (31).

Viewers can use points at stores. If the points are used, the user terminal 3 notifies the store terminal 7 of the points to be used (32). The store terminal 7 can be realized by, for example, a tablet computer, a personal computer, a smartphone, or the like. The store terminal 7 notifies the user management server 6 of the points used (71), and the user management server 6 subtracts the point balance. Further, the point usage log is transmitted from the store terminal 7 to the log server 4 (72), and is accumulated in the log server 4. Thereby, the log server 4 can analyze how many points are given for which content is viewed and how many of those points are used at the store.

==Receiver 2==
FIG. 2 is a diagram showing an example of the hardware configuration of the receiver 2. As shown in FIG. The receiver 2 includes a CPU 201, a memory 202, a storage device 203, a communication device 204, a broadcast receiving module 205, and an output device 206. The storage device 203 stores various data and programs, and is, for example, a hard disk drive, solid state drive, flash memory, or the like. The communication device 204 is a device for communicating, and includes, for example, an adapter for connecting to Ethernet (registered trademark), a modem for connecting to a public telephone line, a wireless communication device for wireless communication, and a serial communication device. USB (Universal Serial Bus) connectors, RS232C connectors, etc. The receiver 2 can also include a plurality of communication devices 204. The broadcast receiving module 205 is a module that receives television broadcast radio waves and decodes video and audio from the received radio waves. Note that the broadcast receiving module 205 can use hardware related to general television broadcast reception and decoding. Output device 206 includes a display and a speaker for outputting data.

FIG. 3 is a diagram showing an example of the software configuration of the receiver 2. As shown in FIG. The receiver 2 includes functional units such as a video/audio processing section 211 , a viewing detection section 212 , a viewing log registration section 213 , a viewing log transmitting section 214 , a point acquisition section 215 , and a point adding section 216 , and a viewing log database 231 . . The above-mentioned functional units are realized by the CPU 201 included in the television receiver 2 reading out programs stored in the storage device 203 into the memory 202 and executing them. It is realized as part of the provided storage area.

The video and audio processing unit 211 controls the broadcast receiving module 205 to output the video and audio of the content from the output device 206. As for video and audio output processing (television broadcast playback processing) by the video and audio processing unit 211, a general method can be adopted, and a description thereof will be omitted here.

Viewing detection unit 212 detects that a viewer is viewing a television broadcast. The viewing detection unit 212 estimates that the viewer is viewing the content output by the television receiver 2 while communication is established with the user terminal 3 . In this embodiment, a message is periodically transmitted from the user terminal 3 to the receiver 2, and the viewing detection unit 212 detects whether communication is possible with the user terminal 3 while the user terminal 3 is receiving the message. If a timeout occurs when a predetermined period of time has elapsed since the last message was received from the user terminal 3, it is detected that communication with the user terminal 3 is no longer possible, and the viewing starts. It is possible to detect that the person has finished viewing the content.

The viewing log database 231 stores logs related to viewing of content by viewers (hereinafter referred to as viewing logs). FIG. 4 is a diagram showing an example of the configuration of the viewing log database 231. The viewing log database 231 stores viewing logs, and the viewing logs include date and time, event, viewing type, channel/content, playback position, and one or more user IDs (user ID1, user ID2, user ID3... )including. In these user ID1, user ID2, user ID3, . . . , when a plurality of viewers view the program at the same time, a user ID indicating each of the plurality of viewers can be recorded. An event is an event that occurs in the receiver 3, such as when a message is first received from the user terminal 3 (smartphone login), when the receiver 3 is turned on (receiver power OK), or when the viewer Examples include a channel being selected, a message from the user terminal 3 being received for the second time or later (continuation of viewing), and communication with the user terminal 3 being disconnected (smartphone logoff). Information indicating operations and processing in the receiver 3, communication between the user terminal 3 and the receiver 2, etc. is set. The viewing classification indicates the viewing method of the content, such as real time (RT), time shift (TS), video on demand (VOD), etc. Channel/content is information for specifying the viewed content. In this embodiment, it indicates which channel or which content was viewed. For the playback position, in the case of real-time viewing, the same value as the date and time in the "date and time" column is set, and in the case of time shift or video on demand, the date and time when the content was first broadcast is set. The user ID is information indicating the viewer who viewed the content.

The viewing log registration unit 213 registers the viewing log in the viewing log database 231. When an event occurs in the receiver 3, the viewing log registration unit 213 can create a viewing log related to the event and register the created viewing log in the viewing log database 231. Here, if the event is related to the start or end of viewing ("smartphone login" or "smartphone logoff"), the viewing log registration unit 213 stores the user ID (the viewer who sent the message or the communication (user ID indicating the viewer who timed out) is included in the new viewing log, and in other cases, the latest viewing log registered in the viewing log database 231 excluding those related to authentication is included. Copy the user ID set in , to the user ID of the new viewing log. Additionally, if the event of the latest viewing log registered in the viewing log database 231 is "smartphone logoff", the user ID of the latest viewing log is deleted from the new viewing log. can do.

The viewing log transmitter 214 transmits the viewing log to the log server 4. The viewing log transmitter 214 can, for example, monitor the viewing log database 231 and transmit viewing logs newly registered in the viewing log database 231 to the log server 4.

The point acquisition unit 215 acquires points to be given to viewers. In the present embodiment, the point acquisition unit 215 transmits a request to acquire points (hereinafter referred to as a point acquisition request) to the campaign management server 5, and receives a response from the campaign management server 5. You can get the number of points. The point acquisition request includes a user ID indicating the viewer, the channel the viewer is viewing, and the date and time of the viewing log. As mentioned above, if you are watching real-time TV broadcasts, the current date and time will be set, and if you are watching via time shift or video on demand, the date and time when the content was first broadcast will be set. will be set.

The point adding unit 216 gives points to the viewer. The point addition unit 216 transmits a request (hereinafter referred to as a point addition request) to the user management server 6 to add the points acquired by the point acquisition unit 215 to the viewer's point balance. The user management server 6 increases the viewer's point balance in response to the point addition request, as will be described later. The point adding unit 216 stores the user ID and date and time indicating the viewer to whom points are to be given, that is, the viewer who is viewing the content, the channel the viewer viewed, the store where the points can be used, and the viewer. A point addition request including the number of points to be given to the user management server 6 is sent to the user management server 6. Note that the point addition unit 216 may eliminate duplicate point addition requests so that duplicate points are not added. For example, the user management server 6 stores the contents of the point addition request (at least the user ID, date and time, and channel) as the point addition history, and the point addition unit 216 stores the point addition request (user ID, date and time, and channel) with the same contents. ) on the same channel is transmitted, it is possible to avoid adding points accordingly.

FIG. 5 is a diagram showing an example of the hardware configuration of a computer used as the user terminal 3, log server 4, campaign management server 5, user management server 6, and store terminal 7. As shown in FIG. The computer includes a CPU 101, a memory 102, a storage device 103, a communication interface 104, an input device 105, and an output device 106. The storage device 103 stores various data and programs, and is, for example, a hard disk drive, solid state drive, flash memory, or the like. The communication interface 104 is an interface for connecting to the communication network 30, and includes, for example, an adapter for connecting to Ethernet (registered trademark), a modem for connecting to a public telephone line network, and a wireless communication device for performing wireless communication. , a USB (Universal Serial Bus) connector for serial communication, an RS232C connector, etc. The input device 105 is, for example, a keyboard, mouse, touch panel, button, microphone, etc., for inputting data. The output device 106 outputs data, such as a display, printer, or speaker.

==Log server 4==
FIG. 6 is a diagram showing an example of the software configuration of the log server 4. As shown in FIG. The log server 4 includes functional units such as a viewing log registration unit 411, a point usage log registration unit 412, and an analysis processing unit 413, and storage units such as a viewing log database 431 and a point usage log database 432.

The viewing log database 431 stores viewing logs. FIG. 7 is a diagram showing a configuration example of a viewing log stored in the viewing log database 431. The viewing log registered in the viewing log database 431 is the viewing log stored in the viewing log database 231 of FIG. 4 described above, with the receiver ID indicating the receiver 2 that created the viewing log added.

The viewing log registration unit 411 registers the viewing log in the viewing log database 431. The viewing log registration unit 411 receives the viewing log transmitted from the television receiver 2, adds the receiver ID indicating the transmitting source television receiver 2 to the received viewing log, and registers the result in the viewing log database 431.

The point usage log database 432 stores logs related to the usage of points at stores (hereinafter referred to as point usage logs). FIG. 8 is a diagram showing a configuration example of a point usage log stored in the point usage log database 432. The point usage log includes the store where the points were used, the process ID indicating the process related to the use of the points, the date and time the points were used, the user ID indicating the viewer who used the points, and the products (services) related to the use of the points. (hereinafter the same applies), the price of the product, the number of points used, the promotional rate, and the payment cost. The payment cost is a sales promotion cost related to the use of points, and the sales promotion rate is information for calculating the sales promotion cost (payment cost) to be paid according to the number of points. In this embodiment, it is assumed that the payment cost can be calculated by multiplying the number of points used (“point usage”) by the sales promotion rate.

The point usage log registration unit 412 registers the point usage log in the point usage log database 432. The point usage log registration unit 412 receives a point usage log transmitted from the store terminal 7 described later, adds a store ID indicating the store to the received point usage log, and registers it in the point usage log database 432. .

The analysis processing unit 413 analyzes the relationship between content viewing and purchasing activities based on the viewing log and point usage log. For example, the analysis processing unit 413 links viewing logs and point usage logs using user IDs, and determines which content viewers have viewed and what products they have purchased based on the linked viewing logs and point usage logs. It is possible to analyze what kind of content was viewed by the viewers who purchased which products.

==Campaign management server 5==
FIG. 9 is a diagram showing an example of the software configuration of the campaign management server 5. As shown in FIG. The campaign management server 5 includes functional units such as a campaign information input section 511 , a point issuing section 513 , a point notification receiving section 514 , and a content usage fee output section 515 , and a campaign database 531 .

The campaign database 531 stores information (hereinafter referred to as campaign information) for determining points to be given to viewers. FIG. 10 is a diagram showing a configuration example of campaign information registered in the campaign database 531. The campaign information includes the TV broadcast channel, campaign start date and time, campaign end date and time, company name, target conditions, sales promotion rate, point award rate, upper limit, award points, and the like, in association with the campaign ID that specifies the campaign information. Includes usage points. The channel is a channel (video content or audio content delivered on-demand may be specified) that is the target of a campaign that gives points to viewers. Note that the channel may include information that identifies content such as a specific television program or advertisement. For example, it can be attached to a channel to include the start date and time of the content and the end date and time of the content. The company name is information that specifies a store where points can be used. Information indicating all stores ("*" in the example of FIG. 10) may be set. The target condition is a condition regarding the attributes of a viewer to whom points are to be awarded. Target conditions are used to narrow down sales promotions by awarding points to specific targets. The sales promotion rate is information for calculating the sales promotion cost that the store should pay for using points. In this embodiment, it is assumed that the coefficient is a coefficient for the points used, and that the sales promotion cost can be calculated by multiplying the number of points used by the sales promotion rate. The point award rate is information for determining the number of points to be issued according to the viewer's viewing time. In this embodiment, the point award rate is set to the unit time (5 minutes, 15 minutes, and 10 minutes are set in the example of FIG. 10) and the number of points awarded per unit time. shall be The upper limit is the upper limit of the number of points that can be issued. The usage points are the number of points actually used at the store (that is, the point usage record). Campaign information is a campaign information given to viewers whose attributes meet the target conditions among the viewers who watched the content of the "channel" between the "start date and time" and the "end date and time". This indicates that the number of points that can be used at the company (store) indicated by the "company name" will be issued according to the "point award rate" until the "points awarded" reaches the "upper limit".

The campaign information input unit 511 performs new registration or updating of campaign information. The campaign information input section 511 includes information on the channel related to the campaign that gives points, the start date and time of the campaign, the end date and time of the campaign, the store (company name) where the points can be used, target conditions, and the sales promotion rate for calculating the promotional expenses related to the use of the points. , point award rate, and upper limit are received, and campaign information in which these are set is created and registered in the campaign database 531. Note that the campaign information input unit 511 can also receive the contents of one or more items of campaign information and update the campaign information registered in the campaign database 531. The campaign information input unit 511 can receive this information from a computer used by a user of the broadcasting station 1, for example.

Point issuing unit 513 issues points to viewers. It is assumed that the point issuing unit 513 calculates points to be issued to the viewer and responds to the point acquisition request transmitted from the television receiver 2 . The point issuing unit 513 transmits to the user management server 6 a request for acquiring viewer attributes (hereinafter referred to as a viewer attribute acquisition request) in which the user ID included in the point acquisition request is set, The viewer's attributes, which are responded from the user management server 6 in response to the viewer attribute acquisition request, are acquired. For example, the point issuing unit 513 corresponds to the channel included in the point acquisition request, the date and time included in the point acquisition request falls between the start date and time and the end date and time, and the attribute of the acquired viewer is the target. Campaign information that satisfies the conditions can be searched from the campaign database 531, and the point award rate of the searched campaign information can be responded as the number of points. The point issuing unit 513 can also respond with the store (company name of campaign information) where points can be used. Further, a point acquisition period is set in the campaign information, and the point issuing unit 513 issues points if the date and time of receiving the point acquisition request is within the acquisition period, and Points may not be issued outside the acquisition period.

Point notification receiving section 514 receives notification of points used (hereinafter referred to as point usage notification). In this embodiment, the point notification receiving unit 514 receives point usage notifications from the user management server 6. The point usage notification includes the store (company name) where the points were used, the date and time of point usage, and the number of points used. The point notification receiving unit 514 selects points from the campaign database 531 for the points used in the campaign information corresponding to the company name included in the received point usage notification and whose usage date and time included in the point usage notification is from the start date and time to the end date and time. Add up the number of points included in the usage notification.

The content usage fee output unit 515 outputs the content usage fee to be paid to the broadcast station. The content usage fee output unit 515 reads the campaign information of the corresponding channel from the campaign database 531 for each broadcast station, and determines the usage fee based on the usage points included in the read campaign information. The content usage fee output unit 515 may calculate the usage fee by, for example, multiplying the number of usage points by a constant coefficient or a coefficient set in advance for each broadcasting station. Further, the content usage fee output unit 515 can also output the sales promotion fee that the store (the person conducting the sales promotion) should pay for the use of the points. The content usage fee output unit 515 accepts the designation of the target store, reads campaign information corresponding to the designated store from the campaign database 531, and multiplies the usage points by the sales promotion rate of the read campaign information, thereby increasing sales promotion costs. can be calculated. The store may be specified by accepting input from an input device such as a keyboard, or by receiving a promotional expense request (hereinafter referred to as a promotional expense acquisition request) from an external source that includes information that specifies the store. Good too. When receiving a promotional expense acquisition request, the content usage fee output unit 515 can also send the calculated promotional expense as a response to the promotional expense acquisition request. Furthermore, when allocating promotional expenses to a servicer related to the receiver 2 (for example, a manufacturer of the receiver 2, a business that distributes and operates the receiver 2, etc.), the content usage fee output unit 515 The service fee to the servicer may also be calculated. In this case, the content usage fee output unit 515 can calculate and output a usage fee according to the amount of logs transmitted by the receiver 2 to the log server 4, for example. That is, the content usage fee output unit 515 outputs the sales promotion expenses so that the sales promotion expenses from the store (advertiser) are distributed to the usage fee of the point system of this embodiment, the content usage fee, the service fee to the servicer, etc. Calculations related to distribution can be performed. The content usage fee output unit 515 may process the payment of the calculated content usage fee (as well as the system usage fee and the service fee to the servicer).

==User terminal 3==
FIG. 11 is a diagram showing an example of the software configuration of the user terminal 3. As shown in FIG. The user terminal 3 includes a login processing section 311, a point balance display section 312, a connection processing section 313, and a point utilization section 314.

The login processing unit 311 performs login processing to receive user authentication. The login processing unit 311 performs login processing by communicating with the user management server 6, which will be described later. In this embodiment, it is assumed that the connection processing unit 313 transmits the user ID and password to the campaign management server 5, and the password is verified in the user management server 6.

The point balance display section 312 acquires and displays the viewer's point balance managed by the user management server 6. The point balance display section 312 can send a request for point balance (hereinafter referred to as point balance request) to the user management server 6 and receive the balance in response from the user management server 6. A user ID is set in the point balance request.

The connection processing unit 313 transmits a message to the receiver 2. The connection processing unit 313 periodically transmits a message to the receiver 2 (for example, any time can be set such as every 15 seconds, every 1 minute, every 5 minutes, etc.). As described above, while the receiver 2 is receiving the message transmitted from the connection processing unit 313, it is estimated that the viewer is viewing the content output from the receiver 2.

The point utilization unit 314 performs processing related to the use of points. For example, when making a payment for a product, the point usage unit 314 receives a designation of the number of points to be used up to the point balance acquired by the point balance display unit 312 described above, and specifies the designated number of points and a user ID. Points can be used by transmitting a request (hereinafter referred to as a point use request) to the store terminal 7. At the store terminal 7, payment processing is performed by subtracting an amount corresponding to the number of points set in the point usage request from the product price.

==User management server 6==
FIG. 12 is a diagram showing an example of the software configuration of the user management server 6. As shown in FIG. The user management server 6 includes a user information registration section 611, an authentication processing section 612, a point transmission section 613, a point addition request reception section 614, a point subtraction request reception section 615, a point notification transmission section 616, and a viewer attribute provision section 617. It includes a functional unit, and storage units for a user database 631 and a user history database 632.

The user database 631 stores information regarding viewers (users) (hereinafter referred to as user information). FIG. 13 is a diagram showing an example of the configuration of the user database 631. The user information registered in the user database 631 includes authentication information (password), attributes related to the viewer, and point balance in association with a user ID that identifies the viewer. The authentication information may be any information used to authenticate the viewer (or the user terminal 3), such as a feature such as a fingerprint or an iris, or a public key, instead of a password. The attributes may be various attributes regarding the viewer, such as demographic attributes, psychographic attributes, geographic attributes, and the like. Attributes are information that can specify segments that can be targets of so-called targeted advertisements. Further, in the example of FIG. 13, the user information includes the main point balance, the company A point balance, and the company B point balance. That is, the user information includes, for each store, the balance of points that can be used at that store. The main point balance is the balance of points that can be used at any store. In the example of FIG. 13, the point balance for each store is added as a column in the user information, but one or more pieces of balance information that associate stores and balances may be included.

The user information registration unit 611 registers user information in the user database 631. The user information registration unit 611 can accept the input of the user ID and password, create user information in which the received user ID and password are set, set the point balance to 0, and register it in the user database 631.

The authentication processing unit 612 authenticates the viewer. The authentication processing unit 612 can authenticate the viewer using authentication information (for example, a password) included in the user information. The authentication processing unit 612 can perform authentication by, for example, receiving a user ID and password from the user terminal 3 and comparing the password of the user information corresponding to the received user ID with the received password. It should be noted that a general user authentication method can be adopted, and a description thereof will be omitted here.

The point transmitter 613 responds with the point balance in response to the point balance request. As described above, the user ID is set in the point balance request transmitted from the user terminal 3. The point transmitter 613 can read the point balance corresponding to the user ID included in the point balance request from the user database 631 and respond.

The user history database 632 stores history of points usage by viewers. FIG. 14 is a diagram showing an example of the configuration of the user history database 632. Each usage history included in the user history database 632 is associated with the user ID and date and time, and includes channels viewed, number of points added (addition details), number of points used (subtraction details), point balance, and points awarded. Or store the store used (processing target).

In response to the point addition request, the point addition request receiving unit 614 registers the point usage history and increases the viewer's point balance. Upon receiving the point addition request, the point addition request receiving unit 614 generates a new usage history, and uses the user ID, date and time, channel, store, and number of points included in the received point addition request as the generated usage history. Set the user ID, date and time, viewing channel, processing details, and addition details of the history. Further, the point addition request receiving unit 614 updates the user database 631 so as to add the number of points to the balance corresponding to the store in the user information corresponding to the user ID. Further, the point addition request receiving unit 614 sets the balance of the updated user information as the point balance of the generated usage history and registers it in the user history database 632.

The point subtraction request receiving unit 615 registers a point usage history in response to a request to subtract the number of points used from the viewer's point balance (hereinafter referred to as a point subtraction request), and Point balance will be decreased. Point subtraction request receiving section 615 receives a point subtraction request from store terminal 7 . The point subtraction request includes the user ID, the date and time of point use, the number of points used, and the store where the points were used. Upon receiving the point subtraction request, the point subtraction request receiving unit 615 generates a new usage history, and inputs the user ID, date and time, number of points, and store included in the received point subtraction request to the user of the generated usage history. Set the ID, date and time, subtraction details, and processing target. Further, the point subtraction request receiving unit 615 updates the user database 631 so as to subtract the number of points from the balance corresponding to the store in the user information corresponding to the user ID. Further, the point subtraction request receiving unit 615 sets the balance of the updated user information as the point balance of the generated usage history and registers it in the user history database 632.

The point notification transmitting unit 616 transmits a point usage notification to the campaign management server 5. The point notification transmitting unit 616 transmits a corresponding point usage notification each time a point subtraction request is received. The point notification sending unit 616 manages the campaign by sending a point usage notification that includes the processing target (store), date and time, and subtraction details of the usage history registered in response to the point deduction request as the company name, usage date and time, and number of points, respectively. Send to server 5. As described above, the campaign management server 5 manages the number of points used in association with the number of issued points.

The viewer attribute providing unit 617 provides viewer attributes in response to the viewer attribute acquisition request. A user ID is set in the viewer attribute acquisition request, and the viewer attribute providing unit 617 searches the user database 631 for user information corresponding to the user ID, and responds with various attributes included in the user information. can do. Note that the viewer attribute providing unit 617 may provide user information in response to a viewer attribute acquisition request.

==Store terminal 7==
FIG. 15 is a diagram showing an example of the software configuration of the store terminal 7. As shown in FIG. The store terminal 7 includes functional units such as a point processing unit 711, a payment processing unit 712, a point subtraction request transmission unit 713, a point usage log transmission unit 714, and a sales promotion expense output unit 715, and a storage unit of a point usage log database 731. Equipped with The above-mentioned functional units are realized by the CPU 101 included in the store terminal 7 reading out programs stored in the storage device 103 into the memory 102 and executing them, and the storage unit is realized by the CPU 101 included in the store terminal 7 It is realized as part of the storage area provided by the storage device 103.

The point usage log database 731 stores a point usage log related to points used at a store. FIG. 16 is a diagram showing a configuration example of a point usage log stored in the point usage log database 731. The point usage log is obtained by removing the store ID from the point usage log stored in the point usage log database 432 shown in FIG.

The payment processing unit 712 performs processing related to payment of products. Here, when a point usage request is sent from the user terminal 3, the payment processing unit 712 receives the point usage request and subtracts an amount corresponding to the number of points set in the point usage request from the product price. to process the payment.

The point processing unit 711 performs processing related to the use of points. The point processing unit 711 includes a processing ID that specifies the payment processing by the payment processing unit 712, a date and time when the payment processing was performed, a user ID included in the point usage request, a product ID indicating the product for which the payment processing was performed, Generate a point usage log that sets the price of the product, the number of points included in the point usage request, the promotional rate set in advance for the product, and the payment cost calculated by multiplying the points by the promotional rate, and use the points. It is registered in the log database 731.

The point subtraction request transmitter 713 transmits a point subtraction request to the user management server 6. The point subtraction request includes the user ID indicating the viewer, the date and time when the points were used, the store where the points were used, and the number of points used.

The point usage log transmitter 714 transmits the point usage log registered in the point usage log database 731 to the outside. In this embodiment, the point usage log transmitter 714 transmits the point usage log to the log server 4. The point usage log transmitting unit 714 may identify the newly registered point usage log and transmit it to the log server 4 each time a new point usage log is registered, or may transmit the current A point usage log that includes a date and time that is a certain period of time later than the date and time can be read from the point usage log database 731 and transmitted to the server 4.

The sales promotion expense output unit 715 calculates the sales promotion expenses to be paid. For example, the sales promotion expense output unit 715 can calculate the total payment expense by multiplying the point usage by the sales promotion rate and output it as the sales promotion expense. Note that the sales promotion expense output unit 715 may perform processing for paying sales promotion expenses. The payee can be the operator of the point system according to this embodiment. Further, the calculation of sales promotion expenses may be performed in the campaign management server 5. In this case, the promotional expense output unit 715 transmits a promotional expense acquisition request in which information specifying the store corresponding to the store terminal 7 is set to the campaign management server 5, and receives the promotional expenses responded from the campaign management server 5. be able to.

The processing executed in the point system according to this embodiment will be described below.

==Campaign information registration process==
FIG. 17 is a diagram showing the flow of campaign information registration processing. At broadcasting station 1, a computer accepts and sets inputs for channels related to campaigns that award points, start and end dates and times of campaigns, stores (company names) where points can be used, point award rates, and upper limits. A campaign information registration request can be sent to the campaign management server 5 (S821). For example, the campaign information input unit 511 sends an input screen in which form information is set to a computer operated by a user of the broadcasting station 1, and the campaign management server 5 sends a request in which the data entered in this input screen is set. This can be achieved by accepting it. The campaign information input unit 511 generates campaign information in which various information set in the received campaign information registration request is set and registers it in the campaign database 531 (S822), and sends a message indicating that the registration is completed to the campaign information registration. It can be sent as a response to the request (S823).

==Login processing==
FIG. 18 is a diagram showing the flow of the viewer's login process to the point system.

The login processing unit 311 of the user terminal 3 transmits a request to obtain a login screen for logging in (login screen request) to the user management server 6 (S801). The authentication processing unit 612 of the user management server 6 responds to the user terminal 3 with information for displaying a login screen (for example, screen data written in HTML) (S802). The login processing unit 311 of the user terminal 3 receives input of a user ID and password from the viewer (S803). Note that the login processing unit 311 may store the user ID and password in the storage device 103 of the user terminal 3, and read out the stored user ID and password. The login processing unit 311 sends the login request with the accepted user ID and password set to the user management server 6 (S804), and the authentication processing unit 612 of the user management server 6 sets the user ID and password included in the login request. The viewer is authenticated using a password (S805). The authentication processing unit 612 can perform authentication processing by, for example, comparing the user ID and password of user information registered in the user history database 632 with the user ID and password included in the login request. . The authentication processing unit 612 responds to the user terminal 3 with the authentication result (S806).

If the authentication is successful, the point balance display section 312 of the user terminal 3 transmits a point balance request to the user management server 6 (S807), and the point transmission section 613 of the user management server 6 sends the points included in the point balance request. The point balance corresponding to the user ID being read is read from the user database 631 (S808), and the read point balance is returned to the user terminal 3 (S809). The point balance display section 312 of the user terminal 3 can output the responded point balance (S810).

==Viewing detection processing==
FIG. 19 is a diagram showing the flow of processing for detecting viewing of content by a viewer.
The connection processing unit 313 of the user terminal 3 transmits the first message (check-in message) to the receiver 2 (S841), and the viewing detection unit 212 of the receiver 2 determines that the communication with the user terminal 3 is complete. Establishment can be detected as the viewer starting viewing (S842).

The connection processing unit 313 of the user terminal 3 periodically sends a message to the receiver 2 (S843), and the connection processing unit 313 receives the message from the user terminal 3 before it times out, thereby allowing viewers to It can be determined that the viewing of the content continues (S844). If a predetermined period of time has elapsed since the last message was received from the user terminal 3 and a timeout occurs, the connection processing unit 313 can determine that viewing has ended (S845).

==Point granting process==
FIG. 20 is a diagram showing the flow of processing for giving points to viewers.
Messages are continuously sent from the connection processing unit 313 of the user terminal 3 to the receiver 2 (S861), and as shown in FIG. 19, the viewing detection unit 212 of the receiver 2 detects that viewing is continuing. It is assumed that it has been determined that

The point acquisition unit 215 of the television receiver 2 transmits a point acquisition request in which the currently viewed channel and the detected user ID are set to the campaign management server 5 (S862), and the point issuing unit 513 of the campaign management server 5 , transmits a viewer attribute acquisition request with a user ID set to the user management server 6 (S863), and the user management server 6 responds with the attributes of the user information corresponding to the user ID (S864), and sends a point acquisition request and viewing request. Campaign information corresponding to the person's attributes is acquired (S865). Specifically, the point issuing unit 513 corresponds to the channel included in the point acquisition request, and the date and time included in the point acquisition request falls between the start date and time and the end date and time, and the viewer who acquired the point Campaign information whose attributes satisfy target conditions can be searched from the campaign database 531. The point issuing unit 513 determines the number of points according to the acquired campaign information, and responds with the determined number of points and the store (company name) (S866). For example, the point issuing unit 513 can determine the point award rate included in the campaign information as the number of points.

The point addition unit 216 of the television receiver 2 sends a point addition request to the user management server 6 in which the user ID, date and time, and channel included in the latest viewing log and the store and number of points received from the campaign management server 5 are set. (S867). The point addition request receiving unit 614 of the user management server 6 adds the granted points to the viewer's point balance in response to the point addition request (S868). For example, the point addition request receiving unit 614 selects the point balance included in the user information corresponding to the user ID included in the point addition request that corresponds to the store included in the point addition request. The user database 631 can be updated to add the number of points included in the point addition request. Furthermore, in the present embodiment, the point addition request receiving unit 614 generates a new usage history, and records the user ID, date and time, channel, store, and number of points included in the received point addition request, as well as the updated user. The point balance information is set in the user ID, date and time, viewing channel, processing details, addition details, and point balance of the generated usage history, and is registered in the user history database 632.

The point notification transmitting unit 616 transmits a point usage notification including the processing target (store), date and time, and subtraction details of the usage history as the company name, usage date and time, and number of points, respectively, to the campaign management server 5 (S869). The point notification receiving unit 514 of the campaign management server 5 adds the number of points given to the points given in the campaign information in response to the point notification (S870). For example, the point notification receiving unit 514 receives information from the campaign database 531 that corresponds to the company name included in the received point usage notification, and that the usage date and time included in the point usage notification corresponds to the usage points in the campaign information from the start date and time to the end date and time. , the number of points included in the point usage notification can be added.

The point notification transmitter 616 may notify the user terminal 3 of the updated point balance (S871). The point balance display section 312 of the user terminal 3 can update the display based on the received point balance.

==Point usage processing==
FIG. 21 is a diagram illustrating the flow of point usage processing. Here, it is assumed that the viewer uses points when visiting a store and purchasing products.

When the viewer visits a store, the viewer operates the user terminal 3 to designate the number of points to be used. The point use unit 314 of the user terminal 3 transmits a point use request in which the specified number of points is set to the store terminal 7 (S881).

The payment processing unit 712 of the store terminal 7 performs payment processing by subtracting an amount corresponding to the number of points set in the point use request from the product price (S882). The point processing unit 711 sends a point subtraction request to the user management server 6, which sets the user ID indicating the viewer, the date and time when the points were used, the store where the points were used, and the number of points used (S883). .

The point subtraction request receiving unit 615 of the user management server 6 subtracts points from the user's point balance in response to the received point subtraction request (S884). The point subtraction request receiving unit 615 updates the user database 631 to subtract the number of points from the balance corresponding to the store in the user information corresponding to the user ID set in the point subtraction request, and also A usage history in which the user ID, date and time, number of points, store, and point balance of updated user information are set can be generated and registered in the user history database 632. In response to the point subtraction request, the point notification sending unit 616 sends a point usage notification setting the processing target (store), date and time, and subtraction details of the registered usage history to the campaign management server 5 (S885).

The point notification receiving unit 514 of the campaign management server 5 adds to the usage points of the campaign information according to the point usage notification received from the user management server 6 (S886). The point notification receiving unit 514 selects points from the campaign database 531 for the points used in the campaign information corresponding to the company name included in the received point usage notification and whose usage date and time included in the point usage notification is from the start date and time to the end date and time. The number of points included in the usage notification can be added. In the campaign management server 5, the content usage fee output unit 515 calculates and outputs the content usage fee according to the usage points of the campaign information, and the content usage fee is paid (S887). The content usage fee output unit 515 may perform payment processing.

The point usage log transmission unit 714 of the store terminal 7 transmits the point usage log registered in the point usage log database 731 to the log server 4 (S888), and the point usage log registration unit 412 of the log server 4 transmits the received usage log. A store ID indicating the store is added to the log and registered in the point usage log database 432 (S889). In the store terminal 7, the promotional expense output unit 715 calculates and outputs the promotional expense to be paid according to the use of the points, and the promotional expense is paid (S890). The sales promotion cost can be calculated by, for example, the sales promotion cost output unit 715 multiplying the value of point usage in the usage log by the coefficient of the sales promotion rate. The promotional expense output unit 715 may perform processing related to payment of promotional expenses.

As described above, according to the point system of this embodiment, points that can be used at a store can be awarded according to the time the viewer views the content output from the television receiver 2. Therefore, it becomes possible to use content provided on television broadcasts as advertisements for sales promotion in stores. On the other hand, using the user terminal 3 of the viewer, it is possible to link TV viewing and point usage based on the user ID, so advertising activities by issuing points using TV broadcasting, which is a medium of mass advertising. It is possible to accurately grasp the effects of

Furthermore, according to the point system of this embodiment, by communicating between the user terminal 3 and the receiver 2, it is possible to estimate the time that the viewer is viewing the television broadcast. Conventionally, it has been difficult to grasp the viewing status of mass broadcast television, but with the point system of this embodiment, it is possible to accurately estimate whether or not viewers are watching.

In addition, the user terminal 3 is a device that the viewer is expected to carry with him at all times, such as a smartphone, and the communication between the user terminal 3 and the receiver 2 is performed using, for example, Bluetooth (registered trademark). If the method is limited to communication over relatively short distances, it becomes clear that at least the viewer is present in the vicinity of the receiver 2, so it is clear that the viewer is listening to the output from the receiver 2. Since the probability is high that the viewer is at least listening to the audio, the viewing time by the viewer can be estimated with high accuracy.
In addition, in the point system of this embodiment, since TV viewing logs and point usage logs are accumulated in the log server 4, points issued for viewing which channel (content) can be used at which stores and for which products. It is possible to analyze whether it was used for purchasing. Therefore, it is possible to accurately measure the advertising effect and utilize it for the next promotional activity.

Furthermore, according to the point system of this embodiment, since the server is accessed from the receiver 2 rather than the user terminal 3, points can be issued in a situation where at least it is ensured that the content is being played.

Further, according to the point system of this embodiment, the sales promotion expenses at the store can be returned to the broadcasting station 1 that provided the content. Therefore, in addition to making it possible to attach new sponsors in addition to sponsors for conventional TV programs and channels, in this embodiment, the number of points is awarded according to the viewing time. It is expected that the quality of content will improve.

Although the present embodiment has been described above, the above embodiment is for facilitating understanding of the present invention, and is not for construing the present invention in a limited manner. The present invention may be modified and improved without departing from the spirit thereof, and the present invention also includes equivalents thereof.

For example, in this embodiment, points are managed in a distributed manner between the campaign management server 5 and the user management server 6, but the campaign management server 5 and the user management server 6 can also be operated as a single server. Similarly, the log server 4, campaign management server 5, and user management server 6 may be operated as a single server or as two servers.

Furthermore, in the present embodiment, when points are used, a point usage request is sent from the user terminal 3 to the store terminal 7, but the point usage request is transmitted from the user terminal 3 to the store terminal 7 without any communication between the user terminal 3 and the store terminal 7. You may also make use of it. For example, points may be used by displaying a barcode, QR code (registered trademark), etc. on the user terminal 3 and reading this with a code reader provided in the store terminal 7. In this case, the store terminal 7 can check the point balance, approve the use of points, etc. with the user management server 6 before processing the payment. In addition, the user terminal 3 displays a coupon code, passcode, etc., and the viewer verbally conveys this to a store clerk and the clerk inputs it into the store terminal 7, or the viewer inputs it into the store terminal 7. , points may be used.

Further, in this embodiment, it is assumed that the viewer is viewing the video by communicating between the receiver 2 and the user terminal 3, but the user can detect that the viewer is viewing the video. The terminal 3 may estimate it. An example of the configuration of the point system in this case is shown in FIG. In the configuration example shown in FIG. 22, unlike the example shown in FIG. (22'), addition of points from the receiver 2 to the campaign management server 5 is also performed from the user terminal 3 (23'), and registration of viewing logs from the receiver 2 to the log server 4 is also performed from the user terminal 3. (24'). In this case, the user terminal 3 is equipped with a viewing detection section, and the viewing detection section of the user terminal 3 extracts a feature amount from the audio output from the receiver 2, and identifies the content currently being output. You can do it like this. The feature amount for each content may be obtained from the broadcasting station 1 or the like in advance and set in the user terminal 3.

Furthermore, in the present embodiment, the television receiver 2 transmits a point acquisition request to the campaign management server 5, and the campaign management server 5 determines the points to be given to the viewer. You can also do this. In this case, the receiver 2 includes a campaign information acquisition unit that acquires campaign information from the campaign management server 5, a campaign information storage unit that stores campaign information, and a point issuing unit, and the point issuing unit Points to be issued can be determined based on the following.

Furthermore, in this embodiment, the campaign information is input from the broadcasting station 1, but it may be registered from a source other than the broadcasting station 1. For example, advertisers (store operators, advertising agencies, manufacturers of products offered at stores, planning companies such as advertising agencies that plan campaigns to gain awareness of products and promote sales, etc.) register campaign information. You can do it like this. In this case, it becomes possible to provide a service for giving points without requiring the broadcasting station 1 to take any trouble.

Furthermore, in this embodiment, the viewer attributes included in the user information are preset, but are not limited to this, and can be automatically inferred by analyzing the viewer's viewing behavior. It's okay. For example, a viewer's attributes can be estimated based on the viewer's content viewing history. In addition, if the receiver 2 is used to access the Internet (for example, browsing web pages or shopping at online shopping sites), the content of the web page viewed using the receiver 2 Viewer attributes can be inferred based on viewer information and purchase history. For this estimation process, it is possible to use general techniques such as, for example, analyzing web server access logs and analyzing cookie information.

In addition, in this embodiment, if the viewer attribute satisfies the target condition, a uniform number of points is issued based on the campaign information, but depending on the attribute, a different number of points may be given, or a different number of points may be issued depending on the attribute. Content coupon information may also be provided. In this case, for example, the target conditions of the campaign information can include information for determining the number of points to be issued and the content of the coupon depending on the attribute.

1 Broadcasting station 2 Receiver 3 User terminal 4 Log server 5 Campaign management server 6 User management server 7 Store terminal 211 Video and audio processing section 212 Viewing detection section 213 Viewing log registration section 214 Viewing log transmitting section 215 Point acquisition section 216 Point addition section 231 Viewing log database 311 Login processing section 312 Point balance display section 313 Connection processing section 314 Point usage section 411 Viewing log registration section 412 Point usage log registration section 413 Analysis processing section 431 Viewing log database 432 Point usage log database 511 Campaign information input section 513 Point transmission unit 514 Point notification reception unit 515 Content usage fee output unit 531 Campaign database 611 User information registration unit 612 Authentication processing unit 613 Point transmission unit 614 Point addition request reception unit 615 Point subtraction request reception unit 616 Point notification transmission unit 617 Viewing User attribute provision unit 631 User database 632 User history database 711 Point processing unit 712 Payment processing unit 713 Point subtraction request transmission unit 714 Point usage log transmission unit 715 Sales promotion expense output unit 731 Point usage log database

Claims (4)

A point system that awards points according to the viewing of content broadcast on television,
a viewing detection unit that detects that a viewer has viewed the content on the television broadcast receiver;
a point granting unit that grants points to the viewer according to the manner in which the viewer views the content and the attributes of the viewer;
a point storage unit that stores the points given to the viewer in association with the content;
Equipped with
comprising one or more user terminals communicatively connected to the receiver,
The point system is characterized in that the viewing detection unit detects how many viewers have viewed the content output by the television receiver using a user terminal connected to the television receiver. The point system according to claim 1,
Information for specifying the content, conditions for the attributes of the viewer to whom the points are to be awarded, point calculation information to calculate the points to be awarded when viewing the content, and the period for which the points are to be awarded. It also includes a campaign management database that remembers the
The point granting unit acquires the point calculation information corresponding to the content viewed by the viewer, the attributes of the viewer, and the date and time of viewing the content from the campaign management database, and based on the point calculation information. calculating the number of points to be given to the user terminal of the viewer;
A point system featuring The point system according to claim 1 or 2,
a usage point acquisition unit that acquires the number of points used by the viewer;
a usage fee output unit that charges a user of the points an amount according to the number of uses and performs calculations related to distribution of the amount;
A point system further comprising: 4. The point system according to claim 3,
a viewing log storage unit that stores a viewing log of the content viewed by the viewer;
a usage log storage unit that stores a usage log in which the points are used;
an analysis processing unit that analyzes a relationship between viewing the content and using the points based on the viewing log and the usage log, and outputting an analysis result;
A point system further comprising:

Images