Information processing device, privilege provision program, and privilege provision method

Abstract

To provide a technique which provides a user with a chance to have fun even if a voting ticket the user bought does not hit the mark.SOLUTION: The above challenge is cleared by an information processing device comprising a reception unit configured to receive voting ticket information specifying voting content of a user for a race, and a first provision unit configured to provide the user with a privilege when voting content on the mark is not included in the voting ticket information according to a race result.SELECTED DRAWING: Figure 1

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 allows users to place bets in publicly managed races such as horse racing, boat racing, and bicycle racing.

[0003] Another example of such a service 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 such a video distribution service is a service that distributes video content related to predictions on publicly managed races.

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

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-160612 Summary of the Invention [Problem to be solved by the invention]

[0006] There are cases where a user bets on a horse or its group number to run in a race in a publicly managed competition, but ends up losing. In such cases, if the user continues to lose interest, 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 wrong, they may lose the trust of users who used their predictions as a reference and may no longer use their predictions as a reference.

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

[0009] An information processing device according to one embodiment of the present invention is characterized by comprising: 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 winning betting content based on the results of the competition. [Effects of the Invention]

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

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of an information processing apparatus according to an embodiment of the present invention. [Figure 2] 1 is a diagram showing an example of a network configuration of a betting ticket purchasing system according to an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram showing an example of functional blocks of the betting ticket purchasing system according to 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 this embodiment. [Figure 5]FIG. 10 is a diagram showing an example of a distributor selection screen in the present embodiment. [Figure 6] FIG. 10 is a diagram showing an example of a broadcaster prediction screen in the present embodiment. [Figure 7] FIG. 10 is a diagram showing an example of a betting ticket purchase screen in this embodiment. [Figure 8] FIG. 10 is a diagram showing a benefit grant notification in the present embodiment. [Figure 9] FIG. 10 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. 10 is a sequence diagram (Example 1) of the process from purchasing a betting ticket based on broadcaster betting ticket information between a user terminal and a server in this embodiment. [Figure 11] FIG. 10 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] 10 is a flowchart of a benefit providing process (Example 1) in this embodiment. [Figure 13] 10 is a flowchart of a benefit providing process (Example 2) according to the present embodiment. [Figure 14] 10 is a flowchart of a benefit providing process (Example 3) according to the present embodiment. [Figure 15] FIG. 2 is a block diagram illustrating 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 INVENTION

[0012] 1 is a diagram showing an example of an information processing device in this embodiment. The information processing device 1 includes a reception unit 2 and a first provision 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 specifying the user's betting details for a race. An example of the reception unit 2 is the user betting ticket information acquisition unit 46, which will be 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., corresponding to the car number, horse number, etc.), the betting type (corresponding to win, place, etc.), and the bet amount (betting amount, betting value).

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

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

[0016] The betting content may also 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 results of the competition, the second providing unit 4 provides the user with a refund amount of a first value (e.g., cash, points) corresponding to the betting amount specified 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, which will be described later.

[0017] By configuring in this way, if the purchased betting ticket is 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 winning bet.

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

[0020] Furthermore, the reception unit 2 may 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. In this case, the first provision unit 3 may provide the user with a benefit associated with the provider based on the results of the race if the betting ticket information does not include any winning bets.

[0021] By configuring in this way, if a user purchases a voting ticket based on the broadcaster's predicted voting ticket and the ticket turns out to be a wrong choice, the user can be given a special benefit related to the broadcaster.

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

[0023] By configuring in this way, if a user purchases a voting ticket with reference to the distributor's predicted voting ticket and the ticket turns out to be a loser, the user can be allowed to view the special 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 bets in the betting ticket information.

[0025] By configuring it in this way, for example, the more times you miss, the rarer the benefit you will be given.

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

[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 enjoy the competition more.

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

[0029] By configuring in this way, for example, a benefit may be offered to the user according to the number of races in which no winning bids were made in one day.

[0030] Furthermore, the first providing unit 3 may provide a benefit to a user if the amount of loss suffered by 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] By configuring in this way, 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 the 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 that they can communicate with each other.

[0033] The user terminal 12 is a portable electronic terminal device with 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, etc. The operation display unit 13 is a device that allows input operations to be made on the screen 14 and displays images on the screen 14, such as a touch panel display. The user terminal 12 may also be a so-called personal computer.

[0034] The user terminal 12 can download and install a predetermined 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") is installed on the user terminal 12, which enables users to purchase betting tickets for publicly managed races such as horse racing, boat racing, and bicycle racing (hereinafter sometimes referred to as "races") and to view distributors' predicted finishing orders.

[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, the user may be required to input, for example, a pre-registered user ID.

[0036] When the dedicated application software installed on 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 predetermined input.

[0037] If the betting ticket that the user purchased wins the race result, the user will receive a payout based on the payout ratio (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 amount of a first value (paid) bet (purchase amount) for the betting target. If betting tickets are purchased for a fee, the payout may be paid in money, for example. For this reason, the user ID is associated with information for making payments, such as the user's credit card number or bank account number. If 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 telecommunication terminal device with a communication function that can be connected to the communication network 17, such as a computer, smartphone, tablet terminal, or mobile phone used by the distributor. In this embodiment, the distributor terminal 15 may be, for example, a personal computer. The distributor terminal 15 also has an imaging device that the distributor uses to shoot and distribute videos. The imaging device may be built into the distributor terminal 15 or may be an external device.

[0039] The distributor accesses server 16 using distributor terminal 15. Then, the distributor distributes video content (video content related to predicted finishing orders in a race) captured using an imaging device to user terminal 12 via 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 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 bet 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, broadcaster terminal 15, and 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 display and input data through a user's input operation. In this 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 predicted 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) on which the distributor only predicted the finishing order, 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 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 payment 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 that temporarily stores betting ticket information designated by the user. When betting ticket information designated by a broadcaster is adopted, the temporary storage area 28 can also temporarily hold some or all of the adopted betting ticket information. The temporary storage area 28 stores, for example, information identifying the race (race name or race ID, etc.), finishing order information, bet amount, and, when betting ticket information is held by the prediction adoption unit 24, information identifying the broadcaster who is the basis of the betting ticket information (broadcaster name or broadcaster ID, etc.).

[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. The distributor uses the input unit 33 to input predicted finishing order details for the target race, purchase betting tickets, and input instructions regarding the 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 overall operation of the server 16. At the same time, the control unit 42 performs control such as executing processing in response to a request from the user terminal 12 or the broadcaster terminal 15 and returning the execution result to the user terminal 12 or the broadcaster terminal 15. The control unit 42 executes the 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 bonus 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 user terminals 12 running a dedicated application program. At the same time, the distribution control unit 43 distributes the accepted video content to user terminals 12 running a dedicated application program.

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

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

[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 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 amount of bets placed on 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] If the purchased betting ticket does not include a winning betting target (a number or set number for a betting target in a race), the reward provision unit 49 will provide a predetermined reward to the user who did not win. In addition, the reward provision unit 50 may provide a reward to the user according to the number of races in which the user did not win (for example, the total number of times, the consecutive number of times) during a predetermined period.

[0064] The voting result registration unit 50 registers information relating to the voting results of each user who purchased a voting ticket (win / loss 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 benefit management database 57, and a user betting result management database 58. Note that, hereinafter, the databases will be referred to as "DBs."

[0066] The broadcaster management DB 52 is a database that manages broadcasters. The broadcaster betting ticket information DB 53 is a database that manages betting ticket information specified by broadcasters. The user information management DB 54 is a database that manages information about users. The user betting ticket information DB 55 is a database that manages information about betting tickets purchased by users. The odds information DB 56 is a database that manages information about odds for each betting ticket in a race. The bonus management DB 57 is a database related to bonuses. The user betting result management DB 58 is a database that manages information about users' betting 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 the 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 the data items of "broadcaster ID," "race ID," "betting ticket," "purchase amount," and "video content ID." The "broadcaster ID" item stores information identifying the broadcaster (broadcaster ID). The "race ID" item stores information identifying the race (race ID). The "betting ticket" item stores the number of the first place winner or the group number of the winning order from first place to a predetermined place in the race (race) identified by the race ID. Note that in this embodiment, exacta bets, place-to-place bets, etc. are not mentioned for the sake of convenience, but these are not excluded. The "purchase amount" item stores the bet amount corresponding to the betting ticket information. The "video content ID" item stores information identifying the video content of the corresponding broadcaster (video content ID).

[0070] The user information management DB 54 includes the data items "User ID," "Email address," "Amount held," and "Points held." The item "User ID" stores information that identifies the user (user ID). The item "User name" stores the user's name. The item "Amount held" stores the amount that the user can currently use in the betting ticket purchasing system 11. The item "Points held" stores the points that the user can currently use in the betting ticket purchasing system 11.

[0071] The user betting ticket information DB55 includes the data items "User ID," "Race ID," "Bet," "Purchase Amount," "Purchase Points," and "Broadcaster ID." The "User ID" item stores information identifying a user (User ID). The "Race ID" item stores information identifying a race (Race ID). The "Bet" item stores the number of the first place winner in the race (race) identified by the race ID, or the group number of the finishers from first place to a predetermined position. The "Purchase Amount" item stores the bet corresponding to the betting ticket information (this item is used in the case of paid betting, and the bet is currency). The "Purchase Points" item stores the bet corresponding to the betting ticket information (this item is used in the case of unpaid betting, and the bet is points). The "Broadcaster ID" item stores the broadcaster ID of a broadcaster when a user purchases a betting ticket using a betting ticket designated by that broadcaster.

[0072] The odds information DB 56 includes the data items of "race ID," "betting ticket," and "odds." The item "race ID" stores information (race ID) that identifies the race. The item "betting ticket" stores the group numbers of the finishers from first place to a predetermined position in the race (race) identified by the race ID. The item "odds" stores odds information corresponding to each betting ticket.

[0073] The bonus management DB57 includes data items such as "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 (for example, bonus video content, still images, character image data, etc.).

[0074] The user betting result management DB58 includes the data items "User ID," "Race ID," "Winning Flag," "Bet Amount," "Payout Amount," and "Loss Amount." The "Race ID" item stores information identifying the user (User ID). The "Winning Flag" item 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. "Bet Amount" stores the purchase amount (betting amount) of the betting ticket (betting target) purchased for that race. "Payout Amount" stores the payout amount that will be paid if the betting tickets purchased for that race include a winning ticket. "Loss Amount" stores the amount obtained by subtracting the payout amount from the betting amount.

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

[0076] 5 is a diagram showing an example of a broadcaster selection screen in this embodiment. The broadcaster selection screen 61 includes a logged-in user display field 62, a holding amount display field 63, a holding 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 who is currently logged in to the betting ticket purchasing system 11 using the user terminal 12. The held amount display field 63 displays the amount of money that the user currently holds in the betting ticket purchasing system 11. The held points display field 64 displays the points that the user currently holds 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] The broadcaster list 66 displays thumbnail images 66a, 66b, 66c, etc. corresponding to broadcaster information related to race predictions for the race displayed in the purchase target race name display field 65. The broadcaster list 66 can be scrolled using the operation display unit 13 to display broadcaster information that is not currently displayed. When the thumbnail image 66 of any broadcaster is tapped, the screen shown in FIG. 6 is displayed for that broadcaster.

[0079] 6 is a diagram showing an example of a broadcaster prediction screen in this embodiment. The 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 users 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) of the selected broadcaster. The broadcaster betting ticket information display field 75 displays the pair number of the betting ticket specified by that broadcaster (including the target number if the betting type is win or place; the same applies below) and its odds. Tapping the details display button 76 displays the screen shown in Figure 7, where users 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. The voting ticket purchase screen 81 includes a distributor video content display field 82, an owned points display field 83, an owned points addition specification field 84, an owned amount display field 85, an owned amount 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 streaming video). The owned points display field 83 displays the points that the user currently owns in the betting ticket purchase system 11. By tapping the owned points addition specification field 84, points (charge) that can be used only within the betting ticket purchase system 11 to purchase betting tickets free of charge can be added. The owned amount display field 85 displays the amount of money that the user currently owns in the betting ticket purchase system 11. By tapping the owned money addition specification field 86, the amount of money that can be used to purchase betting tickets for a fee can be added (charged) to the betting ticket purchase system 11. Note that in the betting ticket purchase 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. The broadcaster predicted voting ticket display field 87 displays, by default, the set number of the voting ticket designated by broadcaster A and the bet or bet points.

[0084] The prediction betting ticket list 87a includes a pair number display column 88, an odds display column 89, and a bet / bet point display column 90. The betting pair number display column 88 is a column for displaying the pair number to be bet on, and displays the pair number designated by the distributor. In the example of FIG. 7, the prediction betting ticket list 87a displays four pair numbers: the pair number of "1st place No. 1, 2nd place No. 4," the pair number of "1st place No. 3, 2nd place No. 8," the pair number of "1st place No. 5, 2nd place No. 2," and the pair 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 unit purchase button 92 is a button for purchasing betting tickets in units of a set, where one set is a combination of betting tickets in the prediction betting ticket list 87a. Each time the "+" button on the set unit purchase button 92 is pressed, the number of sets to be purchased is increased. Each time the "-" button on the set unit 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 prediction voting ticket list 87a. Editing can be done, for example, by changing the purchase unit from points (free) to yen (paid), or from yen (paid) to points (free), by adding the user's own new predictions to the prediction voting ticket list 87a, or by deleting a predetermined group number from the prediction voting ticket list 87a. Pressing the delete button 94 allows the distributor prediction voting ticket display column 87 to be deleted.

[0088] FIG. 8 is a diagram showing a bonus notification in this embodiment. Suppose a user purchases a betting ticket using FIG. 7, the race is held, and the finishing order is determined, but none of the purchased betting tickets win. 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 listed in the message 100, predetermined video content (for example, video content by broadcaster A) is displayed on the screen 14 as a bonus.

[0089] 9 is a sequence diagram showing the process until broadcaster voting 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 the installed dedicated application program (S1). Then, the user terminal 12, on which the dedicated application program has 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 a prediction 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 for 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 broadcaster A's video content (S10).

[0093] The user terminal 12 displays the set number of the betting ticket included in the broadcaster voting information for broadcaster A transmitted from the server 16 in the broadcaster betting ticket information display field 75 on 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 detail display button 76 on the broadcaster prediction screen 71 in Fig. 6. Then, the user terminal 12 (prediction adoption unit 24) stores 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 betting ticket information or add the user's own predicted betting ticket information to the broadcaster betting ticket information. The user also specifies the amount of bet for each piece of betting 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 betting ticket information in the temporary storage area 28).

[0097] On the betting ticket purchase screen 81, once the user has finalized the betting ticket to be purchased, they tap the purchase execution button 96 (S23). Then, the user terminal 12 (purchase request unit 25) sends 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) to the server 16 based on the contents of the temporary holding area 28 (S24). Note that if the user adds a betting ticket that differs from the broadcaster's prediction, the broadcaster ID information may not be included in the betting ticket information.

[0098] The server 16 (user betting ticket information acquisition unit 46) acquires the purchase request. The server 16 (user betting ticket information acquisition unit 46) registers the contents of the user betting ticket information included in the acquired purchase request in the user betting ticket information DB 55. The server 16 (payment processing unit 47) performs payment processing for the purchase of the betting 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 has 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 (payout processing unit 48) performs payout processing for the winning betting ticket information (S27).

[0100] Meanwhile, the server 16 (benefit provision unit 50) performs a benefit provision process for the betting ticket information that did not win (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 betting ticket information (S29). The server 16 transmits a benefit provision notice to the user terminal 12 for each user who is eligible for a benefit through the benefit 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), so that the user can view the bonus video content if he or she loses the race.

[0104] Fig. 11 is a sequence diagram (Example 2) of the process from 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 the case where broadcaster voting ticket information of another broadcaster is displayed after broadcaster A's voting ticket information is stored in the temporary holding area 28 and before the purchase.

[0105] After S11 in FIG. 9, the user taps the detail display button 76 on the broadcaster prediction screen 71 in FIG. 6. Then, the user terminal 12 (prediction adoption unit 24) stores the broadcaster betting ticket information of broadcaster A in the temporary storage area 28 (S41). At this time, the betting ticket purchase screen 81 in FIG. 7 is displayed. Thereafter, 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 stored in the temporary storage area 28 is stored until the end of the race, so if the user returns to the betting ticket purchase screen 81 in FIG. 7 for broadcaster A, the broadcaster betting ticket information of broadcaster A will be displayed.

[0106] From the list of distributors 66 on the distributor selection screen 61, the user selects the thumbnail image 66b of distributor information for 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 specifies 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. Then, the server 16 (broadcaster betting ticket information provision unit 45) 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 betting ticket included in the broadcaster voting information of broadcaster B transmitted from the server 16 in the broadcaster voting ticket information display field 75 on 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) stores the broadcaster voting ticket information of broadcaster B in the temporary holding area 28 (S47). At this time, the betting 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 betting ticket information for broadcaster B, or add the user's own predicted betting ticket information to the broadcaster betting ticket information. The user also designates a bet amount for each piece of betting 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 betting ticket information in the temporary storage area 28).

[0110] On the betting ticket purchase screen 81, once the user has finalized the betting ticket to be purchased, they tap the purchase execution button 96 (S49). Then, the user terminal 12 (purchase request unit 25) sends 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) to the server 16 based on the contents of the temporary holding area 28 (S50). Note that if the user adds a betting ticket that differs from the broadcaster's prediction, the broadcaster ID information may not be included in the betting ticket information.

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

[0112] The server 16 (user betting ticket information acquisition unit 46) acquires the purchase request. The server 16 (user betting ticket information acquisition unit 46) registers the contents of the user betting ticket information included in the acquired purchase request in the user betting ticket information DB 55. The server 16 (payment processing unit 47) performs payment processing for the purchase of the betting 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 has 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 (payout processing unit 48) performs payout processing for the winning betting ticket information (S53).

[0114] Meanwhile, the server 16 (benefit provider 50) performs a benefit provision process for the betting ticket information that did not win (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 benefit provision notice to the user terminal 12 for each user who is to be given a benefit through the benefit 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), so that the user can view the bonus video content if their betting ticket is not successful in that race.

[0118] 12 is a flowchart of the benefit provision process (Example 1) in this embodiment. When the benefit 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 winning betting tickets for the current race from the user betting ticket information DB 55 (S72).

[0119] The reward provider 49 acquires the user ID, race ID, and broadcaster ID from the extracted user betting ticket information (S73). The reward provider 49 acquires the corresponding reward ID and reward location information from the reward management DB 57 using the acquired race ID and broadcaster ID as keys (S74). The reward provider 49 transmits a reward grant notification including the acquired reward 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 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 corresponding to the broadcaster that was used as a reference can be distributed to the user.

[0122] It is also possible to provide different benefits to users depending on the number of times they have missed the mark. For example, the more times they have missed the mark, the better the benefit (for example, a bonus video content with a longer playback time). Furthermore, benefits may be provided to users depending on the user's voting results over a predetermined period of time and the user's losing status. This will be described with reference to FIG. 13.

[0123] 13 is a flowchart of the benefit providing process (Example 2) in this embodiment. The benefit providing unit 49 counts the total number of times or the 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 reward provider 49 determines a reward 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 reward information (including information on the location of the reward) corresponding to the total number or consecutive number of times the hit flag = 0 has been registered in advance in the storage unit 51. In this case, the reward provider 49 can determine a reward 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 granting 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 granting notification, the privilege providing unit 49 delivers the privilege video content to the user terminal 12 that has made the request (S84).

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

[0127] In addition, if a user's loss amount (=total amount of bets - total amount of refunds > 0) exceeds a predetermined value during a predetermined period, a special benefit may be awarded to the user. This will be explained using FIG. 14.

[0128] 14 is a flowchart of the benefit providing process (Example 3) in this embodiment. The benefit 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 provider 49 determines a reward (S93). Here, different rewards 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 pre-registered in the storage unit 51. The reward provider 49 can determine a reward for each user from the database depending on the loss amount.

[0131] The privilege provider 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 provider 49 delivers the privilege video content to the user terminal 12 that has made the request (S95).

[0132] As a result, if the amount of loss of a user reaches or exceeds a predetermined value within a predetermined period (for example, one day), a special benefit 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. The bus 110 is connected to the CPU 102, ROM 103, RAM 104, storage device 105, input I / F 106, output I / F 107, communication I / F 108, and, if necessary, a reading device 109.

[0135] When the computer 101 is the server 16, the CPU 102 reads 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 benefit provision unit 59, and a voting result registration unit 50. The ROM 103 is a read-only memory. The RAM 104 is a memory for temporary storage.

[0136] The storage device 105 is a device that stores large amounts of information. Various types of storage devices can be used as the storage device 105, such as a hard disk, a solid state drive (SSD), or a flash memory card. The storage device 105 stores a program according to an embodiment of the present invention and various types of 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 portable recording media.

[0139] The program for realizing the processes described in the above embodiments may be stored in, for example, the storage device 105 from a program provider via a communication network and the communication I / F 108. The program for realizing the processes described in the above embodiments may also be stored in a commercially available portable storage medium. 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. Various types of storage media can be used as the portable storage medium, such as a CD-ROM, a flexible disk, an optical disk, a magneto-optical disk, an IC card, a USB memory device, or a semiconductor memory card. The program stored in such a storage medium is read by the reading device 109.

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

[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-described embodiment, this is not limited thereto, and may be determined, for example, for each venue where a competition is being held, or for each competition (race). Furthermore, the reward 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 manga, etc. The text data may be content such as a novel. The music data may be a recording of only the audio portion of video content, or simply audio data, or may be song data. The predetermined program may be, for example, a game program. The reward may also be access rights to a predetermined website, an item object that can be used in a predetermined game program, or experience points for leveling up. The reward may also be a voucher for a predetermined product or service related to the competition.

[0142] This aspect has been described above based on embodiments and modifications. However, the above-described embodiments are intended to facilitate understanding of this aspect and are not intended to limit this aspect. This aspect may be modified or improved without departing from the spirit and scope of the claims, and equivalents thereof are included in this 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 the result of the competition; An information processing device comprising: By configuring in this way, even if the purchased betting ticket does not win, it is possible to provide the user with an opportunity to have fun. (Appendix 2) The voting content includes a voting target and a voting amount for the voting target, The information processing device further comprises: a second providing unit that provides the user with a payout amount of 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, By configuring in this way, if the purchased betting ticket is a winning ticket, the first value can be refunded to the user. (Appendix 3) The first providing unit does not provide the benefit 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 not won. (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 predicted results 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 any one of claims 1 to 3. By configuring in this way, if a user purchases a voting ticket based on the broadcaster's predicted voting ticket and the ticket turns out to be a wrong choice, the user can be given a special benefit related to the broadcaster. (Appendix 5) The first providing unit provides the user with, as the benefit, content associated with the provider in a viewable manner. 5. The information processing device according to claim 4, By configuring it in this way, if a user purchases a voting ticket based on the distributor's predicted voting ticket and the ticket turns out to be a loser, the user can view a bonus video related to the distributor. (Appendix 6) The first providing unit provides the user with the benefit according to the number of incorrect bets among the betting ticket information. 6. The information processing device according to any one of Supplementary Notes 1 to 5. By configuring it in this way, for example, the more times you miss, the rarer the benefit you will be given. (Appendix 7) The first providing unit provides the user with information about the target of the vote as the benefit. 7. The information processing device according to any one of Supplementary Notes 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 enjoy the competition more. (Appendix 8) The first providing unit provides the user with the benefit according to the total number of times or consecutive number of times the received betting ticket information has not been a winner during a predetermined period. 8. The information processing device according to any one of Supplementary Notes 1 to 7. By configuring in this way, for example, a benefit may be offered to the user according to the number of races in which no winning bids were made in one day. (Appendix 9) The providing unit provides the user with the benefit if the amount of loss of the user due to the received betting ticket information not being a hit is equal to or greater than a predetermined value within a predetermined period. 3. The information processing device according to claim 2, By configuring in this way, 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 provision 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, even if the purchased betting ticket does not win, it is possible to provide the user with an opportunity to have fun. (Appendix 11) The 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 special benefit is provided to the user. A method for providing a benefit. By configuring in this way, even if the purchased betting ticket does not win, it is possible to provide the user with an opportunity to have fun. [Explanation of symbols]

[0144] 1. Information processing equipment 2 Providing Department 3 Acquisition part 4 Decision Section 5 Terminal Devices 11 Voting Ticket Purchase System 12 User terminal 15 Streamer terminal 16 servers 17. Communication Networks 41 Communications Department 42 Control Unit 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

[Claim 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 the result of the competition; An information processing device comprising:

Images