Information processing device, special offer program, and special offer method

The information processing device addresses user disengagement by providing benefits when voting tickets lose, ensuring continued engagement and trust in voting services.

JP7587157B2Active Publication Date: 2024-11-20MIXI INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2021119789
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-07-20
Publication Date
2024-11-20
Estimated Expiration
2039-11-28

AI Technical Summary

Technical Problem

Users and video streamers may lose motivation or trust if their voting tickets or predictions do not win, leading to a decrease in engagement with voting services.

Method used

An information processing device that provides benefits to users when their voting tickets do not win, including access to bonus content or refunds, based on the results of competitions.

Benefits of technology

Ensures users continue to engage with voting services by offering opportunities to enjoy the game even if their tickets do not win, enhancing user experience and maintaining trust in video streamers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007587157000001
    Figure 0007587157000001
  • Figure 0007587157000002
    Figure 0007587157000002
  • Figure 0007587157000003
    Figure 0007587157000003
Patent Text Reader

Abstract

To provide a technique for providing a user with an enjoyable opportunity even when his / her purchased betting ticket is not winning.SOLUTION: An information processing apparatus has: a reception unit for receiving betting ticket information designating betting contents for a competition by a user; and a first providing unit for providing a privilege with the user based on a result of the competition if the betting ticket information does not include any winning betting contents. The betting contents include a betting target (e.g., corresponding to a car number, a horse number and the like), a betting type (corresponding to a win type, a place type and the like), and a betting amount (betting amount or a betting value), for example.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing device, a privilege providing program, and a privilege providing method. [Background technology]

[0002] In recent years, with the rapid spread of the Internet and improvements in the communication environment, various services are being provided via communication networks. One such service is a betting ticket purchasing system that enables betting in public races such as horse racing, boat racing, and bicycle racing.

[0003] Another example of the other services is a video distribution service. The video distribution service accepts uploads from users who wish to provide video content, and provides a service of distributing the video content to users who wish to view the video content. One example of the video distribution service is a service that distributes video content related to predictions for publicly managed races.

[0004] Also, for example, a voting prediction publication system has been disclosed in which, on a website that publishes predictions for public races on the Internet, the objective reliability of the forecaster is displayed as an image, allowing visitors to the site to visually recognize the reliability of the forecaster and use the predictions as reference (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2010-160612 A Summary of the Invention [Problem to be solved by the invention]

[0006] There are cases where a user loses their vote for a horse or its group number to run in a race in a publicly managed race. In such cases, if users continue to lose, they may lose motivation to vote again, which may lead to them abandoning the voting service.

[0007] Furthermore, for video streamers who make predictions, if their predictions turn out to be incorrect, they may lose the trust of users who used their predictions as a reference and may stop using their predictions as a reference in continuing to vote.

[0008] The present invention provides a technique for providing a user with an opportunity to have fun even if the betting ticket he or she purchased does not win. [Means for solving the problem]

[0009] An information processing device according to one embodiment of the present invention is characterized in that it comprises: a reception unit that receives betting ticket information specifying a user's betting content for a competition; and a first provision unit that provides a benefit to the user if the betting ticket information does not include a correct betting content based on the result of the competition. Effect of the Invention

[0010] According to one aspect of the present invention, it is possible to provide a user with an opportunity to have fun even if the betting ticket they purchased does not win. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of an information processing device according to an embodiment of the present invention. [Diagram 2] 1 is a diagram showing an example of a network configuration of a betting ticket purchasing system in this embodiment. [Diagram 3] FIG. 2 is a diagram showing an example of functional blocks of the betting ticket purchasing system in the present embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of a data structure of a database managed by a server in the present embodiment. [Diagram 5]FIG. 13 is a diagram showing an example of a distributor selection screen in the present embodiment. [Figure 6] FIG. 13 is a diagram showing an example of a distributor prediction screen in the present embodiment. [Figure 7] FIG. 13 is a diagram showing an example of a voting ticket purchase screen in the present embodiment. [Figure 8] FIG. 13 is a diagram showing a benefit grant notification in the present embodiment. [Figure 9] FIG. 11 is a sequence diagram showing the process between the user terminal and the server until broadcaster voting ticket information is displayed in this embodiment. [Figure 10] FIG. 11 is a sequence diagram (Example 1) of the process up to purchasing a betting ticket based on broadcaster betting ticket information between a user terminal and a server in this embodiment. [Figure 11] FIG. 11 is a sequence diagram (Example 2) of the process up to purchasing a betting ticket based on broadcaster betting ticket information between a user terminal and a server in this embodiment. [Figure 12] 13 is a flowchart of a privilege providing process (Example 1) in this embodiment. [Figure 13] 13 is a flowchart of a privilege providing process (Example 2) in this embodiment. [Figure 14] 13 is a flowchart of a privilege providing process (Example 3) in this embodiment. [Figure 15] FIG. 2 is a block diagram showing an example of the configuration of a hardware environment of a computer that executes a program according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] 1 is a diagram showing an example of an information processing device in this embodiment. The information processing device 1 includes a receiving unit 2 and a first providing unit 3. An example of the information processing device 1 is a server 16, which will be described later.

[0013] The reception unit 2 receives betting ticket information in which the user's betting details for a race are specified. An example of the reception unit 2 is the user betting ticket information acquisition unit 46 described later. The betting ticket information includes, for example, one or more betting details. Elements of the betting details include the betting target (e.g., car number, horse number, etc.), betting type (e.g., win, place, etc.), and bet (betting amount, betting value).

[0014] If the betting ticket information does not include a winning bet based on the result of the competition, the first providing unit 3 provides a reward (for example, a song, a video, a still image, etc.) to the user. An example of the first providing unit 3 is a reward providing unit 49 described later.

[0015] By configuring in this way, it is possible to provide the user with an opportunity to have fun even if the purchased betting ticket does not win.

[0016] The betting content may include a betting target and a betting amount for the betting target. In this case, the information processing device 1 may further include a second providing unit 4. When the betting ticket information includes a winning betting content based on the result of the competition, the second providing unit 4 provides the user with a refund amount of a first value (e.g., cash, points) according to the betting amount set for the winning betting content. Here, the benefit has a value different from the first value. An example of the second providing unit 4 is a payout processing unit 48 described later.

[0017] With this configuration, if the purchased betting ticket turns out to be a winning ticket, the first value can be refunded to the user.

[0018] Furthermore, the first providing unit 3 may not provide a benefit to the user when the betting ticket information includes a correct betting content.

[0019] By configuring in this way, a special benefit can be provided to the user only if the betting ticket is unsuccessful.

[0020] The reception unit 2 may also receive betting ticket information from a user based on all or part of the betting ticket information specified by a provider who provides predicted results for a race. At this time, the first provision unit 3 may provide the user with a privilege associated with the provider based on the results of the race if the betting ticket information does not include a winning bet.

[0021] With this configuration, if a user purchases a voting ticket based on the distributor's predicted voting ticket and the ticket turns out to be incorrect, the user can be given a special privilege related to the distributor.

[0022] Furthermore, the first provider 3 may provide the user with content associated with the provider in a viewable manner as a privilege. For example, the content may be data such as video, still images, and audio.

[0023] By configuring in this way, when a user purchases a voting ticket with reference to a distributor's predicted voting ticket and the ticket turns out to be incorrect, the user can be allowed to view the privileged content related to that distributor.

[0024] Furthermore, the first providing unit 3 may provide the user with a benefit according to the number of incorrect betting details in the betting ticket information.

[0025] By configuring in this manner, for example, the more times the winnings are lost, the rarer the bonus that is provided.

[0026] Furthermore, the first providing unit 3 may provide the user with information (for example, music, video, still images, etc.) related to the subject of the vote (for example, an athlete or a racehorse) as a privilege.

[0027] By configuring in this way, for example, by providing a bonus video or the like related to the object of voting, the player can feel more attached to the object of voting and can enjoy the competition even more.

[0028] Furthermore, the first providing unit 3 may provide the user with a benefit according to the total number or consecutive number of times that the received betting ticket information has not been a correct answer during a predetermined period of time.

[0029] With this configuration, for example, a privilege may be offered to the user according to the number of races in one day in which no winning combinations were recorded.

[0030] Furthermore, the first providing unit 3 may provide a privilege to the user if the amount of loss of the user due to the received betting ticket information not being correct during a predetermined period is equal to or greater than a predetermined value.

[0031] With this configuration, for example, if the amount of money lost by the user in one day's races is equal to or greater than a predetermined value, a special benefit may be provided to the user.

[0032] 2 is a diagram showing an example of a network configuration of a betting ticket purchasing system in this embodiment. The betting ticket purchasing system 11 includes one or more user terminals 12, one or more broadcaster terminals 15, a server 16, and a communication network 17. The one or more user terminals 12, the one or more broadcaster terminals 15, and the server 16 are connected to each other via the communication network 17 so as to be able to communicate with each other.

[0033] The user terminal 12 is a portable electronic terminal device having a communication function that can be connected to a communication network 17, such as a smartphone, tablet terminal, or mobile phone carried by a user. The user terminal 12 has an operation display unit 13, a microphone for inputting sound, a speaker for outputting sound, and the like. The operation display unit 13 is a device that allows input operations to be performed on a screen 14 and displays images on the screen 14, and is, for example, a touch panel display. The user terminal 12 may be a so-called personal computer.

[0034] The user terminal 12 can download and install a specific application program from an application program download site on the Internet. This allows the user to operate the application program by performing input operations on the operation display unit 13 of the user terminal 12. In this embodiment, as an example, it is assumed that dedicated application software (hereinafter referred to as "dedicated application software") that allows users to purchase betting tickets for public races such as horse races, boat races, and bicycle races (hereinafter sometimes referred to as "races") and to view distributors' predicted finishing orders is installed in the user terminal 12.

[0035] By starting up this dedicated application software on the user terminal 12, the user can make the user terminal 12 access the server 16. When the user terminal 12 accesses the server 16, for example, the user may be required to input a user ID that has been registered in advance.

[0036] When the dedicated application software installed in the user terminal 12 is started, a graphical user interface (GUI) screen, which will be described later, is displayed on the screen 14 of the user terminal 12. The GUI image displays video content related to the distributor's predictions of the finishing order of the race, as well as betting ticket information, etc. The user can predict the finishing order of the race by referring to the video content, etc. displayed on the GUI image, and purchase a betting ticket via the user terminal 12 by making a specified input.

[0037] If the betting ticket purchased by the user wins the race result, the user receives a payout based on the payout rate (also called "odds"). Betting tickets can be purchased for either a fee or free of charge. For example, the odds for a betting target may be calculated based on the betting amount (purchase amount) of the first value (paid) for the betting target. When betting tickets are purchased for a fee, the payout is, for example, paid in money. For this reason, the user ID is associated with, for example, the user's credit card number or bank account number for payment purposes. When betting tickets are purchased for free, they can be purchased using points that can be used within the betting ticket purchasing system 11.

[0038] The distributor terminal 15 is a telegraph terminal device having a communication function that can be connected to the communication network 17, such as a computer, a smartphone, a tablet terminal, or a mobile phone used by the distributor. In the present embodiment, the distributor terminal 15 may be, for example, a personal computer. The distributor terminal 15 also has an imaging device that allows the distributor to shoot and distribute videos. The imaging device may be built into the distributor terminal 15 or may be an external type.

[0039] The distributor accesses the server 16 using the distributor terminal 15. Then, the distributor distributes video content (video content related to predicted finishing orders in a race) captured by an imaging device to the user terminal 12 via the server 16.

[0040] The server 16 is an information processing device that manages dedicated application programs installed in the user terminal 12. For example, the server 16 can stream video content posted by the distributor terminal 15 to the user terminal 12.

[0041] The server 16 can also perform settlement processing and the like for purchasing betting tickets based on betting ticket purchase instructions from the user terminal 12 and the broadcaster terminal 15. After the finishing order of the race is determined, the server 16 performs a payout process to pay out dividends (refunds) to users whose purchased betting tickets are winning, based on the winning betting target, bet amount, and odds. Furthermore, after the finishing order of the race is determined, the server 16 also performs a process to provide predetermined benefits to users whose purchased betting tickets are not winning.

[0042] The server 16 may be a server system made up of one or more physical information processing devices, or may be a virtual server system made up of one or more virtual server devices.

[0043] 3 is a diagram showing an example of functional blocks of the betting ticket purchasing system 11 in this embodiment. Below, the functions of each of the user terminal 12, the broadcaster terminal 15, and the server 16 will be described.

[0044] The user terminal 12 includes an operation display unit 13, a communication unit 21, a control unit 22, and a storage unit 26. The communication unit 21 is an interface that enables communication with devices connected to a communication network 17. Here, the communication unit 21 communicates with the server 16 via the communication network 17.

[0045] The operation display unit 13 is a touch panel display that can receive inputs from a user's input operation and can also display information. In the present embodiment, a touch panel display is used as an example, but the present invention is not limited to this, and the input unit and the display unit may be independent of each other.

[0046] The control unit 22 controls the overall operation of the user terminal 12. The control unit 22 functions as a display control unit 23, a predictive adoption unit 24, and a purchase request unit 25 by executing an application program according to this embodiment.

[0047] The display control unit 23 controls the display state of the screen 14 based on user interface (UI) data 27 of a dedicated application program stored in the storage unit 26. In addition, the display control unit 23 communicates with the server 16 to display the video content distributed by the distributor and the betting ticket information specified by the distributor on the screen 14. Here, the betting ticket information specified by the distributor includes betting ticket information (unpurchased betting tickets) in which the distributor only predicted the order of arrival and purchased betting tickets.

[0048] When the prediction adoption unit 24 receives an instruction to adopt the betting ticket information designated by the broadcaster through an operation from the operation display unit 13, it holds the designated betting ticket information in a predetermined temporary holding area 28. At this time, the prediction adoption unit 24 can hold a part or all of the betting ticket information designated by the broadcaster in the predetermined temporary holding area 28 through an operation from the operation display unit 13. Furthermore, the prediction adoption unit 24 may add new betting ticket information based on the user's own prediction to the information on the betting ticket held in the temporary holding area 28 through an operation from the operation display unit 13.

[0049] The purchase request unit 25 transmits a purchase request to purchase the betting ticket information held in the temporary holding area 28 to the server 16 in response to an instruction from the operation display unit 13. The purchase request unit 25 receives a purchase completion notification from the server 16 that has performed the settlement process for the purchase request.

[0050] The storage unit 26 stores installed programs (including the dedicated application program according to this embodiment) and various data. In this embodiment, the storage unit 26 stores, as an example, UI data 27. Here, the data includes not only status information and character data, but also graphical data.

[0051] The storage unit 26 also has a temporary storage area 28 for temporarily storing betting ticket information designated by the user. When the betting ticket information designated by the broadcaster is adopted, the temporary storage area 28 can also temporarily hold a part or all of the adopted betting ticket information. For example, the temporary storage area 28 stores information identifying a race (such as a race name or race ID), finishing order information, a bet, and, when the betting ticket information is held by the prediction adoption unit 24, information identifying the broadcaster on whose behalf the betting ticket information is based (such as the broadcaster name or broadcaster ID).

[0052] The distributor terminal 15 includes a communication unit 31, a control unit 32, an input unit 33, and an imaging unit 34. The communication unit 31 is an interface that enables communication with devices connected to the communication network 17. The communication unit 31 communicates with the server 16 via the communication network 17.

[0053] The control unit 32 controls the overall operation of the distributor terminal 15. Based on instructions from the input unit 33, the control unit 32 distributes video content captured by the imaging unit 34 to the user terminal 12 via the server 16.

[0054] The input unit 33 is an input interface that inputs instructions and data to the control unit 32. A distributor uses the input unit 33 to input predicted finishing order details for a target race, purchase voting tickets, and input instructions regarding distribution of video content. The imaging unit 34 is an imaging device such as a CCD (Charge Coupled Device).

[0055] The server 16 includes a communication unit 41, a control unit 42, and a storage unit 51. The communication unit 41 is an interface that enables communication with devices connected to the communication network 17. The communication unit 41 communicates with the user terminal 12 and the distributor terminal 15 via the communication network 17.

[0056] The control unit 42 controls the operation of the entire server 16. At the same time, the control unit 42 executes processing in response to a request from the user terminal 12 or the broadcaster terminal 15, and performs control such as returning the execution result to the user terminal 12 or the broadcaster terminal 15. The control unit 42 executes an application program according to this embodiment, thereby functioning as a distribution control unit 43, a broadcaster betting ticket information acquisition unit 44, a broadcaster betting ticket information provision unit 45, a user betting ticket information acquisition unit 46, a settlement processing unit 47, a dividend processing unit 48, a privilege provision unit 49, and a voting result registration unit 50.

[0057] In response to a distribution request from a distributor, the distribution control unit 43 accepts distributor information about the distributor and video content (including bonus video content, etc.) shot by the distributor. The distribution control unit 43 registers the distributor information in the storage unit 51. The distribution control unit 43 distributes the registered distributor information to the user terminal 12 on which a dedicated application program is running. At the same time, the distribution control unit 43 distributes the accepted video content to the user terminal 12 on which the dedicated application program is running.

[0058] The broadcaster betting ticket information acquisition unit 44 acquires the betting ticket information (broadcaster betting ticket information) specified by the broadcaster. Here, the broadcaster betting ticket information includes the predicted finishing order information of the race entered by the broadcaster and the betting ticket information purchased by the broadcaster.

[0059] The broadcaster betting ticket information providing unit 45 provides the broadcaster betting ticket information acquired by the broadcaster betting ticket information acquiring unit 44 to the user terminal 12 in association with the video content of the corresponding broadcaster.

[0060] The user betting ticket information acquisition unit 46 acquires the user's betting ticket information stored in the temporary holding area 28 of the user terminal 12 in response to a betting ticket purchase request from the user terminal 12 .

[0061] The payment processing unit 47 performs payment processing for purchasing a betting ticket based on the user's betting ticket information acquired by the user betting ticket information acquisition unit 46. The payment processing is performed based on a pre-registered credit card, account number, etc.

[0062] After the results of a competition are determined, if the betting ticket information purchased for that competition includes a betting ticket for a winning number or set number, the payout processing unit 48 calculates a payout amount by multiplying the betting amount cast for that number or set number by the determined odds. The payout processing unit 48 pays out the calculated payout amount to users whose voting rights were winning.

[0063] The reward provision unit 49 distributes a predetermined reward to users who did not win when the purchased betting ticket does not include a winning betting target (a number or a set number for a betting target in a race). The reward provision unit 50 may also provide rewards to users according to the number of races that they did not win (e.g., the total number of times, the consecutive number of times) during a predetermined period.

[0064] The voting result registration unit 50 registers information regarding the voting results of each user who purchased a voting ticket (win / lose information, bet amount, refund amount, etc.).

[0065] The storage unit 51 stores a broadcaster management database 52, a broadcaster betting ticket information database 53, a user information management database 54, a user betting ticket information database 55, an odds information database 56, a bonus management database 57, and a user betting result management database 58. In the following, the databases are referred to as "DBs."

[0066] The broadcaster management DB52 is a database that manages broadcasters. The broadcaster betting ticket information DB53 is a database that manages betting ticket information specified by broadcasters. The user information management DB54 is a database that manages information about users. The user betting ticket information DB55 is a database that manages betting ticket information purchased by users. The odds information DB56 is a database that manages information about odds for each betting ticket in a race. The bonus management DB57 is a database related to bonuses. The user voting result management DB58 is a database that manages information about users' voting results for each race.

[0067] FIG. 4 is a diagram showing an example of the data structure of a database managed by the server 16 in this embodiment.

[0068] The distributor management DB 52 includes data items of "distributor ID", "race ID", and "video content ID". Hereinafter, each record in the distributor management DB 52 may be referred to as distributor information. The item "distributor ID" stores information that identifies the distributor (distributor ID). The item "race ID" stores information that identifies the race (race ID). The item "video content ID" stores information that identifies the video content of the corresponding distributor (video content ID).

[0069] The broadcaster betting ticket information DB53 includes data items of "broadcaster ID", "race ID", "betting ticket", "purchase amount", and "video content ID". The item "broadcaster ID" stores information (broadcaster ID) that identifies the broadcaster. The item "race ID" stores information (race ID) that identifies the race. The item "betting ticket" stores the number of the first place winner in the race (race) identified by the race ID, or the group number of the winning order from first place to a predetermined rank. In this embodiment, for the sake of convenience, exacta bets, place bets, etc. are not mentioned, but these are not excluded. The item "purchase amount" stores the bet amount corresponding to the betting ticket information. The item "video content ID" stores information (video content ID) that identifies the video content of the corresponding broadcaster.

[0070] The user information management DB54 includes the data items of "User ID", "Email address", "Amount held", and "Amount held". The "User ID" item stores information that identifies the user (user ID). The "User name" item stores the name of the user. The "Amount held" item stores the amount currently available for use by the user in the betting ticket purchasing system 11. The "Amount held" item stores the points currently available for use by the user in the betting ticket purchasing system 11.

[0071] The user betting ticket information DB55 includes data items of "user ID", "race ID", "betting ticket", "purchase amount", "purchase points", and "broadcaster ID". The item "user ID" stores information (user ID) that identifies the user. The item "race ID" stores information (race ID) that identifies the race. The item "betting ticket" stores the number of the first place winner in the race (race) identified by the race ID, or the group number of the finish order from first place to a specified rank. The item "purchase amount" stores the bet (an item used in the case of a paid bet, and the bet is currency) corresponding to the betting ticket information. The item "purchase points" stores the bet (an item used in the case of a free bet, and the bet is points) corresponding to the betting ticket information. The item "broadcaster ID" stores the broadcaster ID of a broadcaster when a user purchases a betting ticket using a betting ticket designated by the broadcaster.

[0072] The odds information DB56 includes the data items of "Race ID", "Bet", and "Odds". The item "Race ID" stores information (race ID) that identifies the race. The item "Bet" stores the group numbers of the finish order from 1st place to a specified position in the race (race) identified by the race ID. The item "Odds" stores odds information corresponding to each bet.

[0073] The bonus management DB57 includes data items of "race ID", "broadcaster ID", "bonus ID", and "bonus location". The "race ID" item stores information that identifies the race (race ID). The "broadcaster ID" item stores information that identifies the broadcaster (broadcaster ID). The "bonus ID" item stores information that identifies the bonus (bonus ID). The "bonus location" item stores an address that indicates the storage location of the bonus identified by the bonus ID (e.g. bonus video content, still images, character image data, etc.).

[0074] The user betting result management DB58 includes the data items of "user ID", "race ID", "win flag", "betting amount", "refund amount", and "loss amount". The item "race ID" stores information identifying the user (user ID). The item "win flag" stores a winning flag = 1 if the betting ticket purchased for that race is a winning ticket, and stores a winning flag = 0 if the betting ticket is not a winning ticket. The "betting amount" stores the purchase amount (betting amount) of the betting ticket (betting target) purchased in that race. The "refund amount" stores the refund amount to be refunded if the betting tickets purchased for that race include a winning ticket. The "loss amount" stores the amount obtained by subtracting the refund amount from the betting amount.

[0075] Next, the user interface of the dedicated application program installed in the user terminal 12 will be described with reference to Figures 5, 6, and 7. When the dedicated application program is started up in the user terminal 12, a screen for selecting races for which betting tickets can be purchased at that time is displayed on the screen 14. When the user operates the operation display unit 13 to select a target race, the screen of Figure 5 is displayed.

[0076] 5 is a diagram showing an example of a broadcaster selection screen in this embodiment. A broadcaster selection screen 61 includes a login user display field 62, an ownership amount display field 63, an ownership point display field 64, a purchase target race name display field 65, and a broadcaster list 66.

[0077] The logged-in user display field 62 displays the icon and user name of the user currently logged in to the betting ticket purchasing system 11 using the user terminal 12. The retained amount display field 63 displays the amount of money currently retained by the user in the betting ticket purchasing system 11. The retained points display field 64 displays the points currently retained by the user in the betting ticket purchasing system 11. The purchase target race name display field 65 displays the name of the race for which a betting ticket is to be purchased. The purchase target race name display field 65 also displays a message informing the user of the time remaining until the deadline for purchasing betting tickets for that race.

[0078] In the broadcaster list 66, thumbnail images 66a, 66b, 66c, ... corresponding to broadcaster information related to race predictions for the race displayed in the purchase target race name display field 65 are displayed. The broadcaster list 66 can display broadcaster information that is not currently displayed by scrolling the operation display unit 13. When the thumbnail image 66 of any broadcaster is tapped, the screen in FIG. 6 is displayed for that broadcaster.

[0079] 6 is a diagram showing an example of a broadcaster prediction screen in this embodiment. A broadcaster prediction screen 71 includes a race name display field 72, a selected broadcaster display field 73, a broadcaster video content display field 74, a broadcaster betting ticket information display field 75, and a details display button 76.

[0080] The race name display field 72 displays the name of the current race. The race name display field 72 also displays a message informing the user of the time remaining until the deadline for purchasing betting tickets for that race. The selected broadcaster display field 73 displays the name of the broadcaster selected in the broadcaster list 66 on the broadcaster selection screen 61. The broadcaster video content display field 74 displays the video content (e.g., live streaming video in streaming format) of the selected broadcaster. The broadcaster betting ticket information display field 75 displays the pair number (including the target number if the betting type is win or place; the same applies below) and the odds of the betting ticket specified by that broadcaster. When the detailed display button 76 is tapped, the screen in FIG. 7 is displayed, and the user can check the detailed contents of the betting ticket specified by that broadcaster.

[0081] 7 is a diagram showing an example of a voting ticket purchase screen in this embodiment. A voting ticket purchase screen 81 includes a distributor video content display field 82, an owned point display field 83, an owned point addition specification field 84, an owned amount display field 85, an owned amount addition specification field 86, a distributor predicted voting ticket display field 87, and a purchase execution button 95.

[0082] The distributor video content display field 82 displays the video content of the selected distributor (for example, live broadcast video in streaming format). The owned points display field 83 displays the points currently owned by the user in the betting ticket purchasing system 11. By tapping the owned points addition designation field 84, points (charge) that can be used only in the betting ticket purchasing system 11 to purchase betting tickets free of charge can be added. The owned amount display field 85 displays the amount of money currently owned by the user in the betting ticket purchasing system 11. By tapping the owned money addition designation field 86, an amount for purchasing betting tickets for a fee can be added (charged) to the betting ticket purchasing system 11. Note that in the betting ticket purchasing system 11, betting tickets can be purchased within the charged amount or points.

[0083] The broadcaster predicted voting ticket display field 87 includes a predicted voting ticket list 87a, a bet / bet point total display field 91, a set unit purchase button 92, an edit button 93, and a delete button 94. In the broadcaster predicted voting ticket display field 87, the set number of the voting ticket specified by broadcaster A and the bet or bet points are displayed by default.

[0084] The prediction betting ticket list 87a includes a group number display field 88, an odds display field 89, and a bet / bet point display field 90. The betting group number display field 88 is a field for displaying the group number to be bet on, and displays the group number specified by the distributor. In the example of FIG. 7, the prediction betting ticket list 87a displays four group numbers: the group number of "1st place No. 1, 2nd place No. 4", the group number of "1st place No. 3, 2nd place No. 8", the group number of "1st place No. 5, 2nd place No. 2", and the group number of "1st place No. 8, 2nd place No. 5, 3rd place No. 2".

[0085] The odds display field 89 displays odds corresponding to the group number displayed in the betting group number display field 88. The bet / bet point display field 90 displays the bet or bet points for each group number. The bet / bet point total display field 91 displays the total of the bet / bet point display fields 90 in the predicted betting ticket list 87a.

[0086] The set purchase button 92 is a button for purchasing betting tickets in units of a set, where a combination of betting tickets in the prediction betting ticket list 87a is considered as one set. Each time the "+" button of the set purchase button 92 is pressed, the number of sets to be purchased is increased. Each time the "-" button of the set purchase button 92 is pressed, the number of sets to be purchased is decreased.

[0087] Pressing the edit button 93 allows the user to edit the contents of the predicted voting ticket list 87a. For example, the user can change the purchase unit from points (free) to yen (paid), or from yen (paid) to points (free), add a new prediction of the user's own to the predicted voting ticket list 87a, or delete a specified group number from the predicted voting ticket list 87a. Pressing the delete button 94 allows the distributor predicted voting ticket display column 87 to be deleted.

[0088] Fig. 8 is a diagram showing a bonus notification in this embodiment. Suppose that after a user purchases a betting ticket using Fig. 7, the race is held, and the finishing order is determined, the purchased betting ticket does not win anything. In this case, a message 100 notifying the user that a bonus has been awarded is displayed on the screen 14. When the user taps the address written in the message 100, a predetermined video content (for example, video content by distributor A) is displayed on the screen 14 as a bonus.

[0089] 9 is a sequence diagram of the process until broadcaster betting ticket information is displayed between the user terminal 12 and the server 16 in this embodiment. The user operates the user terminal 12 to start up an installed dedicated application program (S1). Then, the user terminal 12 with the dedicated application program started up makes a data acquisition request to the server 16 (S2).

[0090] The server 16 acquires the distributor information (including the distributor ID, race ID, video content ID, and fever flag) of the distributor who will make predictions about the upcoming race from the distributor management DB 52 (S3). The server 16 transmits the acquired distributor information to the user terminal 12 (S4).

[0091] When the user terminal 12 receives the distributor information from the server 16, it displays the distributor information in the distributor list 66 of FIG. 5 (S5). The user selects, for example, a thumbnail image 66a of distributor information of distributor A from the distributor list 66 (S6). The user terminal 12 then requests video content from distributor A based on the video content ID (S7). In response to the request, the user terminal 12 receives the video content from the server 16 (S8). The user terminal 12 plays the received video content on the distributor prediction screen 71 of FIG. 6.

[0092] When broadcaster A designates a betting ticket, the server 16 (broadcaster betting ticket information acquisition unit 44) acquires the contents (broadcaster betting ticket information) (S9). The broadcaster betting ticket information includes the broadcaster ID, race ID, betting ticket set number, purchase amount, and video content ID. The server 16 (broadcaster betting ticket information acquisition unit 44) registers the acquired broadcaster betting ticket information in the broadcaster betting ticket information DB 53. The server 16 (broadcaster betting ticket information provision unit 45) then distributes the broadcaster betting ticket information to the user terminal 12 that is watching the video content of broadcaster A (S10).

[0093] The user terminal 12 displays the set number of the voting ticket included in the broadcaster voting information of the broadcaster A transmitted from the server 16 in the broadcaster voting ticket information display field 75 of the broadcaster prediction screen 71 of FIG. 6 (S11).

[0094] FIG. 10 is a sequence diagram (Example 1) of the process up to purchasing a betting ticket based on broadcaster betting ticket information between the user terminal 12 and the server 16 in this embodiment.

[0095] The user taps the details display button 76 on the broadcaster prediction screen 71 in Fig. 6. Then, the user terminal 12 (prediction adoption unit 24) holds the broadcaster voting ticket information in the temporary storage area 28 (S21). At this time, the voting ticket purchase screen 81 in Fig. 7 is displayed.

[0096] On the betting ticket purchase screen 81, the user may erase part of the broadcaster voting ticket information, or add the user's own predicted voting ticket information to the broadcaster voting ticket information. The user also designates a bet for each piece of voting ticket information (S22). In response to these operations, the user terminal 12 (prediction adoption unit 24) updates the information stored in the temporary storage area 28. That is, the user terminal 12 (prediction adoption unit 24) updates the contents of the temporary storage area 28 in response to the input operation on the betting ticket purchase screen 81 (storing all or part of the broadcaster voting ticket information in the temporary storage area 28).

[0097] On the betting ticket purchase screen 81, when the user has finalized the betting ticket to be purchased, he / she taps the purchase execution button 96 (S23). Then, the user terminal 12 (purchase request unit 25) transmits a purchase request including the user betting ticket information (including the user ID, race ID, betting ticket set number, purchase amount (or purchase points), and broadcaster ID) based on the contents of the temporary holding area 28 to the server 16 (S24). Note that if the user adds a betting ticket that differs from the broadcaster's prediction, the betting ticket information may not include broadcaster ID information.

[0098] The server 16 (user voting ticket information acquisition unit 46) acquires the purchase request. The server 16 (user voting ticket information acquisition unit 46) registers the contents of the user voting ticket information included in the acquired purchase request in the user voting ticket information DB 55. The server 16 (payment processing unit 47) performs payment processing for the purchase of the voting ticket based on the purchase request (S25). When the payment processing is completed, the server 16 updates the contents of the user information management DB 54 based on the payment details, and notifies the user terminal 12 of the completion of the payment processing (S26).

[0099] After the betting time for the race is closed, the server 16 registers the confirmed odds information in the odds information DB 56. After the race, when the finishing order is confirmed, the server 16 (the payout processing unit 48) performs payout processing for the winning betting ticket information (S27).

[0100] Meanwhile, the server 16 (privilege provider 50) performs a privilege provision process for the non-winning betting ticket information (S28). Then, the server 16 (voting result registration unit 50) registers the voting results of each user in the user voting result DB 57 using the user voting ticket information (S29). The server 16 transmits a privilege provision notice to the user terminal 12 for each user who is to be granted a privilege by the privilege provision process (S28) (S30).

[0101] For example, a message 100 shown in Fig. 8 is displayed on the screen 14 of the user terminal 12 that has received the benefit notification (S31). The user taps, for example, the address displayed in the message 100 in Fig. 8. The user terminal 12 then makes a benefit viewing request (or a benefit viewing request; the same applies below) to the server 16 (S32).

[0102] The server 16 distributes the bonus video content in response to the bonus viewing request to the user terminal 12 that made the request (S33).

[0103] The distributed bonus video content is displayed on the screen 14 of the user terminal 12 (S34). This allows the user to view the bonus video content if the user loses the race.

[0104] Fig. 11 is a sequence diagram (Example 2) of purchasing a voting ticket based on broadcaster voting ticket information between the user terminal 12 and the server 16 in this embodiment. Fig. 11 is a sequence diagram of a case where broadcaster voting ticket information of other broadcasters is displayed after broadcaster A's voting ticket information is stored in the temporary holding area 28 and before purchase.

[0105] After S11 in FIG. 9, the user taps the details display button 76 on the broadcaster prediction screen 71 in FIG. 6. Then, the user terminal 12 (prediction adoption unit 24) holds the broadcaster betting ticket information of broadcaster A in the temporary holding area 28 (S41). At this time, the betting ticket purchase screen 81 in FIG. 7 is displayed. After that, the user operates the operation display unit 13 to return to the broadcaster selection screen 61 in FIG. 5. Note that the broadcaster betting ticket information of broadcaster A held in the temporary holding area 28 is held until the end of the race, so if the user returns to the betting ticket purchase screen 81 in FIG. 7 for broadcaster A again, the broadcaster betting ticket information of broadcaster A will be displayed.

[0106] From the distributor list 66 on the distributor selection screen 61, the user selects the thumbnail image 66b of the distributor information of distributor B (S42). Then, the user terminal 12 requests video content from distributor B (S43). In response to the request, the user terminal 12 receives the video content from the server 16 (S44). The user terminal 12 plays the received video content on the distributor prediction screen 71 of FIG. 6.

[0107] When broadcaster B designates a betting ticket, the server 16 (broadcaster betting ticket information acquisition unit 44) acquires the contents (broadcaster betting ticket information). The broadcaster betting ticket information includes the broadcaster ID, race ID, betting ticket set number, purchase amount, and video content ID. The server 16 (broadcaster betting ticket information acquisition unit 44) registers the acquired broadcaster betting ticket information in the broadcaster betting ticket information DB 53. The server 16 (broadcaster betting ticket information provision unit 45) then distributes the broadcaster betting ticket information of broadcaster B to the user terminal 12 that is watching the video content of broadcaster B (S45).

[0108] The user terminal 12 displays the set number of the voting ticket included in the broadcaster voting information of broadcaster B transmitted from the server 16 in the broadcaster voting ticket information display field 75 of the broadcaster prediction screen 71 of Fig. 6 (S46). Then, the user taps the details display button 76 on the broadcaster prediction screen 71 of Fig. 6. Then, the user terminal 12 (prediction adoption unit 24) holds the broadcaster voting ticket information of broadcaster B in the temporary holding area 28 (S47). At this time, the voting ticket purchase screen 81 of Fig. 7 is displayed.

[0109] On the betting ticket purchase screen 81, the user may erase part of the broadcaster voting ticket information of broadcaster B, or add the user's own predicted voting ticket information to the broadcaster voting ticket information. The user also designates a bet for each piece of voting ticket information (S48). In response to these operations, the user terminal 12 (prediction adoption unit 24) updates the information stored in the temporary storage area 28. That is, the user terminal 12 (prediction adoption unit 24) updates the contents of the temporary storage area 28 in response to the input operation on the betting ticket purchase screen 81 (storing all or part of the broadcaster voting ticket information in the temporary storage area 28).

[0110] On the betting ticket purchase screen 81, when the user has finalized the betting ticket to be purchased, he / she taps the purchase execution button 96 (S49). Then, the user terminal 12 (purchase request unit 25) transmits a purchase request including the user betting ticket information (including the user ID, race ID, betting ticket set number, purchase amount (or purchase points), and broadcaster ID) based on the contents of the temporary holding area 28 to the server 16 (S50). Note that, if the user adds a betting ticket that differs from the broadcaster's prediction, the betting ticket information may not include broadcaster ID information.

[0111] Here, the purchase request is a purchase request based on the contents of the temporary holding area 28 specified in S47 and S48. This may purchase only the betting tickets purchased on the screen where the purchase execution button 96 was most recently tapped. Furthermore, the user terminal 12 (purchase request unit 25) may also transmit a purchase request based on the contents of the temporary holding area 28 specified in S21. That is, the betting ticket information that the user has indicated an intention to purchase based on the betting tickets specified by each of the multiple broadcasters may be held in the temporary holding area 28 each time, and when the purchase execution button 96 is tapped, the user device 12 may transmit the betting ticket information that has been held in the temporary holding area 28 up to that point all together to the server 16. This allows the payment process to be performed all at once.

[0112] The server 16 (user voting ticket information acquisition unit 46) acquires the purchase request. The server 16 (user voting ticket information acquisition unit 46) registers the contents of the user voting ticket information included in the acquired purchase request in the user voting ticket information DB 55. The server 16 (payment processing unit 47) performs payment processing for the purchase of the voting ticket based on the purchase request (S51). When the payment processing is completed, the server 16 updates the contents of the user information management DB 54 based on the payment details, and notifies the user terminal 12 of the completion of the payment processing (S52).

[0113] After the betting time for the race is closed, the server 16 registers the confirmed odds information in the odds information DB 56. After the race, when the finishing order is confirmed, the server 16 (the payout processing unit 48) performs payout processing for the winning betting ticket information (S53).

[0114] Meanwhile, the server 16 (privilege provider 50) performs a privilege provision process for the non-winning betting ticket information (S54). Then, the server 16 (voting result registration unit 50) registers the voting results of each user in the user voting result DB 57 (S55). The server 16 transmits a privilege provision notice to the user terminal 12 for each user who is to be granted a privilege through the privilege provision process (S56).

[0115] For example, a message 100 shown in Fig. 8 is displayed on the screen 14 of the user terminal 12 that has received the benefit notification (S57). The user taps, for example, the address displayed in the message 100 in Fig. 8. The user terminal 12 then makes a benefit viewing request to the server 16 (S58).

[0116] The server 16 distributes the bonus video content in response to the bonus viewing request to the user terminal 12 that made the request (S59).

[0117] The distributed bonus video content is displayed on the screen 14 of the user terminal 12 (S60). This allows the user to view the bonus video content if their betting ticket is a losing ticket for that race.

[0118] 12 is a flowchart of the privilege provision process (Example 1) in this embodiment. When the privilege provision unit 49 receives a notification that the finishing order of the race has been determined (S71), it extracts user betting ticket information that does not include a winning betting ticket for the current race from the user betting ticket information DB 55 (S72).

[0119] The bonus provision unit 49 acquires the user ID, race ID, and distributor ID from the extracted user betting ticket information (S73). The bonus provision unit 49 acquires the corresponding bonus ID and bonus location information from the bonus management DB 57 using the acquired race ID and distributor ID as keys (S74). The bonus provision unit 49 transmits a bonus grant notification including the acquired bonus location information to the user terminal 12 used by the user identified by the user ID (S75).

[0120] In response to a request for viewing a privilege from the user terminal 12 in response to the notification of granting of the privilege, the privilege providing unit 49 delivers the privilege video content to the user terminal 12 that has made the request (S76).

[0121] In this way, benefits can be distributed to users whose voting tickets did not win. Also, if a user purchases a voting ticket based on a broadcaster's prediction but does not win, a benefit according to the broadcaster that was used as a reference can be distributed to the user.

[0122] A different bonus may be given to a user depending on the number of times the user's vote was incorrect. For example, the more times the user was incorrect, the better the bonus (for example, bonus video content with a longer playback time). In addition, a bonus may be given to a user depending on the user's voting results in a predetermined period of time and the user's losing situation. This will be described with reference to FIG. 13.

[0123] 13 is a flowchart of the privilege providing process (Example 2) in this embodiment. The privilege providing unit 49 counts the total number or consecutive number of times the hit flag=0 for each user during a predetermined period from the user voting result management DB 58 (S81).

[0124] The privilege provision unit 49 determines a privilege for each user according to the total number or consecutive number of times the hit flag=0 (S82). Here, for example, it is assumed that a database that manages privilege information (including privilege location information) corresponding to the total number or consecutive number of times the hit flag=0 is registered in advance in the storage unit 51. In this case, the privilege provision unit 49 can determine a privilege for each user from the database according to the total number or consecutive number of times the hit flag=0.

[0125] The privilege providing unit 49 transmits a privilege grant notification including location information of the acquired privilege to the user terminal 12 used by the user identified by the user ID (S83). In response to a privilege viewing request from the user terminal 12 in response to the privilege grant notification, the privilege providing unit 49 delivers the privilege video content to the user terminal 12 that made the request (S84).

[0126] In this way, the benefit may be determined according to the total number or consecutive number of times that the ballot ticket does not hit the winning number during a predetermined period (for example, one day).

[0127] Also, if the user's loss amount (=total amount of bets-total amount of refund>0) becomes equal to or exceeds a predetermined value during a predetermined period, a privilege may be given to the user. This will be described with reference to FIG.

[0128] 14 is a flowchart of the privilege providing process (Example 3) in this embodiment. The privilege providing unit 49 tallies the loss amount for each user in a predetermined period from the user voting result management DB 58 (S91).

[0129] The privilege provider 49 performs the processes of S92 to S95 described below for each user. First, the privilege provider 49 determines whether the total loss amount is equal to or greater than a predetermined value (S92). If the total loss amount is less than the predetermined value (NO in S92), the privilege provider 49 performs the process for the next user.

[0130] If the total loss amount is equal to or greater than a predetermined value (YES in S92), the reward provision unit 49 determines a reward (S93). Here, a different reward may be determined depending on the total loss amount. For example, a database that manages reward information (including reward location information) corresponding to the loss amount is registered in advance in the storage unit 51. The reward provision unit 49 can determine a reward for each user from the database depending on the loss amount.

[0131] The privilege providing unit 49 transmits a privilege grant notification including location information of the acquired privilege to the user terminal 12 used by the user identified by the user ID (S94). In response to a privilege viewing request from the user terminal 12 in response to the privilege grant notification, the privilege providing unit 49 delivers the privilege video content to the user terminal 12 that made the request (S95).

[0132] In this way, if the amount of loss of a user reaches or exceeds a predetermined value within a predetermined period (for example, one day), a privilege may be given to the user.

[0133] 15 is an example of a configuration block diagram of a hardware environment of a computer that executes a program in this embodiment. A computer 101 functions as a user terminal 12, a distributor terminal 15, or a server 16. The computer 101 is composed of a CPU 102, a ROM 103, a RAM 104, a storage device 105, an input I / F 106, an output I / F 107, a communication I / F 108, a reading device 109, and a bus 110.

[0134] Here, CPU refers to a central processing unit. ROM refers to a read-only memory. RAM refers to a random access memory. I / F refers to an interface. A CPU 102, a ROM 103, a RAM 104, a storage device 105, an input I / F 106, an output I / F 107, a communication I / F 108, and a reading device 109 as necessary are connected to a bus 110.

[0135] When the computer 101 is the server 16, the CPU 102 reads out the program according to this embodiment from the storage device 105, and functions as a distribution control unit 43, a distributor betting ticket information acquisition unit 44, a distributor betting ticket information provision unit 45, a user betting ticket information acquisition unit 46, a settlement processing unit 47, a dividend processing unit 48, a privilege provision unit 59, and a voting result registration unit 50. The ROM 103 indicates a read-only memory. The RAM 104 is a temporary storage memory.

[0136] The storage device 105 is a device that stores a large amount of information. As the storage device 105, various types of storage devices such as a hard disk, a solid state drive (SSD), a flash memory card, etc. are usable. The storage device 105 stores a program according to an embodiment of the present invention and various data stored in the storage unit 40.

[0137] The input I / F 106 can be connected to input devices such as a keyboard, a mouse, an electronic camera, a web camera, a microphone, a scanner, a sensor, a tablet, a touch panel display, an information reading device, etc. The output I / F 107 can be connected to output devices such as a display, a touch panel, a projector, a printer, a speaker, etc.

[0138] The communication I / F 108 is an interface such as a port for connecting to a communication network and communicating with other devices. The communication network may be the Internet, a local area network (LAN), a wide area network (WAN), a dedicated line, a wired line, a wireless line, etc. The reading device 109 is a device for reading a portable recording medium.

[0139] The program for realizing the process described in the above embodiment may be stored, for example, in the storage device 105 from the program provider via the communication network and the communication I / F 108. The program for realizing the process described in the above embodiment may be stored in a portable storage medium that is commercially available and distributed. In this case, the portable storage medium may be set in the reading device 105, and the program may be read and executed by the CPU 102. As the portable storage medium, various types of storage media such as CD-ROM, flexible disk, optical disk, magneto-optical disk, IC card, USB memory device, and semiconductor memory card can be used. The program stored in such a storage medium is read by the reading device 109.

[0140] The program may be installed on a stand-alone computer, or may be installed by a cloud computer and provide only the functions to the user. In the present embodiment, an application program capable of communicating with the server 16 is installed on the user terminal 12 to control the betting ticket purchasing system in the present embodiment, but this is not limiting. For example, a web browser installed on the user terminal 12 may be used to access the server 16 and use the system according to the present embodiment operated on the server 16 side.

[0141] According to this embodiment, even if the purchased betting ticket does not win, it is possible to provide the user with an opportunity to enjoy. Note that, although the benefits are determined according to the distributor in the above embodiment, the present invention is not limited to this and may be determined, for example, for each venue where the competition is being held, or for each competition (race). The bonus may be not only a video but also a still image, music data, text data, or a predetermined program. The still image may include not only a photograph but also a character design, a cartoon, etc. The text data may be content such as a novel. The music data may be a recording of only the audio portion of the video content, or may be data containing only audio, or may be song data. The predetermined program may be, for example, a game program. The bonus may be an access right to a predetermined website, an item object that can be used in a predetermined game program, or experience points for leveling up. The bonus may be a voucher for a product or service that is predetermined for the competition.

[0142] Although the present aspect has been described above based on the embodiment and modified examples, the above-mentioned embodiment of the aspect is intended to facilitate understanding of the present aspect and does not limit the present aspect. The present aspect may be modified or improved without departing from the spirit and scope of the claims, and equivalents are included in the present aspect. Furthermore, if a technical feature is not described as essential in this specification, it may be deleted as appropriate.

[0143] In addition to the above embodiment, the following is further noted. (Appendix 1) a reception unit that receives betting ticket information specifying the user's betting details for the competition; a first providing unit that provides a benefit to the user when the betting ticket information does not include a winning bet based on a result of the competition; An information processing device comprising: By configuring in this way, it is possible to provide the user with an opportunity to have fun even if the purchased betting ticket does not win. (Appendix 2) The voting contents include a voting object and a voting amount for the voting object, The information processing device further includes: a second providing unit that provides the user with a payout amount based on a first value corresponding to a bet amount determined for the winning bet content when the betting ticket information includes the winning bet content based on the result of the competition, The reward has a value different from the first value. 2. The information processing device according to claim 1 . With this configuration, if the purchased betting ticket turns out to be a winning ticket, the first value can be refunded to the user. (Appendix 3) The first providing unit does not provide the privilege to the user when the betting ticket information includes a winning bet. 3. The information processing device according to claim 1 or 2. By configuring in this way, a special benefit can be provided to the user only if the betting ticket is unsuccessful. (Appendix 4) the accepting unit accepts the betting ticket information from the user based on all or part of the betting ticket information designated by a provider who provides a predicted result for the race; The first providing unit provides the user with the benefit associated with the provider when the betting ticket information does not include a winning bet based on the result of the competition. 4. The information processing device according to claim 1, With this configuration, if a user purchases a voting ticket based on the distributor's predicted voting ticket and the ticket turns out to be incorrect, the user can be given a special privilege related to the distributor. (Appendix 5) The first providing unit provides the user with, as the privilege, content associated with the provider in a viewable manner. 5. The information processing device according to claim 4. By configuring in this way, if the voting ticket purchased by the user based on the predicted voting ticket of the distributor turns out to be a losing bet, the user can be made to view a bonus video related to that distributor. (Appendix 6) The first providing unit provides the user with the benefit according to the number of incorrect betting contents among the betting ticket information. 6. An information processing device according to any one of claims 1 to 5. By configuring in this manner, for example, the more times the winnings are lost, the rarer the bonus that is provided. (Appendix 7) The first providing unit provides the user with information regarding the voting target as the benefit. 7. An information processing device according to any one of claims 1 to 6. By configuring in this way, for example, by providing a bonus video or the like related to the object of voting, the player can feel more attached to the object of voting and can enjoy the competition even more. (Appendix 8) The first providing unit provides the user with the benefit according to the total number or consecutive number of times the accepted betting ticket information has not been a winning combination during a predetermined period. 8. An information processing device according to any one of claims 1 to 7. With this configuration, for example, a privilege may be offered to the user according to the number of races in one day in which no winning combinations were recorded. (Appendix 9) The providing unit provides the privilege to the user when the amount of loss of the user due to the received betting ticket information not being a winning ticket is equal to or greater than a predetermined value during a predetermined period. 3. The information processing device according to claim 2. With this configuration, for example, if the amount of money lost by the user in one day's races is equal to or greater than a predetermined value, a special benefit may be provided to the user. (Appendix 10) In the information processing device, An acceptance process for accepting betting ticket information specifying the user's betting details for the competition; a first providing process for providing a benefit to the user when the betting ticket information does not include a winning bet based on the result of the competition; A reward program that allows you to: By configuring in this way, it is possible to provide the user with an opportunity to have fun even if the purchased betting ticket does not win. (Appendix 11) An information processing device, accepting voting ticket information specifying the user's voting details for the competition; Based on the results of the competition, if the betting ticket information does not include a winning bet, a reward is provided to the user. A method for providing a privilege. By configuring in this way, it is possible to provide the user with an opportunity to have fun even if the purchased betting ticket does not win. [Explanation of symbols]

[0144] 1. Information processing device 2 Providing Department 3 Acquisition part 4 Decision Section 5 Terminal Equipment 11. Voting Ticket Purchase System 12 User terminal 15 Distributor terminal 16 Servers 17. Communications Networks 41 Communications Department 42 Control section 43 Distribution control section 44 Broadcaster Voting Ticket Information Acquisition Department 45 Broadcaster Voting Ticket Information Department 46 User voting ticket information acquisition unit 47 Payment Processing Unit 48 Dividend Processing Section 49 Special Offer Department 50 Voting Results Registration Department 51 Storage section 52 Broadcaster Management DB 53 Broadcaster voting ticket information DB 53 User information management DB 55 User voting ticket information DB 56 Odds Information DB 57 Benefit management DB 58 User Voting Result Management DB

Claims

1. a processor, the processor comprising: accepting a first vote for the race from a provider providing a prediction for the race based on voting ticket information specified by the provider; providing the provider with a value corresponding to a betting amount determined for the winning betting content when the betting ticket information designated by the provider includes the winning betting content; accepting a second vote for the competition from a user based on all or part of the betting ticket information specified by the provider; providing the user with a reward associated with the provider when the second vote does not include a winning vote based on the result of the competition; Information processing device.

2. The processor, providing the user with a viewable video content received from the provider as a privilege associated with the provider; The information processing device according to claim 1 .

3. The processor, displaying the content received from the provider in a selectable manner for the user in response to a distribution request received from the provider; When a selection of the content is accepted from the user, providing the user with set number information of a ballot included in the first vote accepted from the provider corresponding to the selected content; accepting the second vote based on an input received from the user with respect to the provided set number information; The information processing device according to claim 1 .

4. The processor, If the second vote does not include a winning vote, provide the reward to the user; If the second vote includes a winning vote content, provide the user with the value according to the winning vote content, and do not provide the user with the benefit. The information processing device according to claim 1 .

5. The processor, accepting a plurality of the second votes from the user based on betting ticket information designated by a plurality of the providers; providing the user with the benefit associated with the provider associated with the second vote that does not include a winning vote content among the plurality of second votes received; The information processing device according to claim 1 .

6. The processor, providing the user with the benefit determined according to the number of votes not including a winning vote among the second votes received from the user during a predetermined period; The information processing device according to claim 1 .

7. a processor receiving a first vote for the race from a provider providing a prediction for the race based on voting ticket information specified by the provider; a processor, when the betting ticket information specified by the provider includes a winning bet, providing the provider with a value corresponding to a betting amount determined for the winning bet; a processor accepting a second vote for the competition from a user based in whole or in part on the betting ticket information specified by the provider; a processor providing the user with a reward associated with the provider when the second vote does not include a winning vote based on the result of the competition; Information processing methods.

8. The processor: A function of accepting a first vote for a race from a provider who provides a prediction for the race based on voting ticket information specified by the provider; a function of providing the provider with a value according to a betting amount determined for the winning betting content when the betting ticket information specified by the provider includes the winning betting content; a function of accepting a second vote for the race from a user based on all or part of the betting ticket information specified by the provider; a function of providing the user with a benefit associated with the provider when the second vote does not include a winning vote based on the result of the competition; A program for executing.

Citation Information

Patent Citations

  • Integrated system for gambling place

    JP1998334170A

  • Privilege granting method in public race, betting ticket adjustment machine, and betting ticket

    JP2005128723A

  • Voting forecast disclosure system, method, and computer program

    JP2010160612A