Information processing device, payout control program, and payout control method

Abstract

To provide a technique, when predictions of a distributor who distributes competition prediction information do not come true, for suppressing a situation in which predictions of the distributor are not used in subsequent competitions.SOLUTION: An information processing device capable of communicating with a terminal device used by a user via a communication network includes: a providing unit that provides the user's terminal device with first voting ticket information specified by a provider who provides predicted results for competitions; an acquisition unit that acquires second voting ticket information on which the user has voted based on all or part of the first voting ticket information; an accumulation unit that accumulates part of the voting value of the second voting ticket information as an accumulated value; and a payout processing unit that pays out part of the accumulated value as a payout value to the user who has voted for the second voting ticket information based on the first voting ticket information if the first voting ticket information includes a prediction result that has come true.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an information processing device, a payout control program, and a payout control 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 such a service is a video distribution service, which accepts uploads from users who wish to receive video content and distributes the video content to users who wish to view the video content.

[0004] One such service is an amusement service, which includes, for example, a game system equipped with a jackpot lottery device that executes a jackpot lottery among a plurality of game devices that satisfies a predetermined lottery start condition (for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0006] One example of a video distribution service is a service that distributes video content related to predictions for publicly managed races. The evaluation of such video contributors (or distributors) is based on the number of page views. Generally, betting is based on the number of pageviews (PV). Therefore, in video content about predictions for publicly managed races, for example, a broadcaster predicts the order of finishes in the race, and if that prediction is correct, the number of pageviews generally tends to increase. Users who are planning to purchase betting tickets would rather refer to the predictions of broadcasters whose predictions were correct than those of broadcasters whose predictions were not correct.

[0007] However, if users only refer to the predictions of a particular broadcaster when purchasing voting tickets, purchases of voting tickets for a particular set number will be concentrated, making the service less interesting as an entertainment service.

[0008] Furthermore, for video content by distributors whose predictions were incorrect, viewers will be less likely to refer to the distributor's predictions for the next and subsequent races, and the number of page views will decrease. Therefore, even if such video content is produced, it will go unwatched and be buried. As a result, there is a risk that the number of page views for video content related to predictions for publicly managed races as a whole will decrease, and the number of users using such services may also decrease.

[0009] To provide a technique for preventing a situation where a distributor who distributes prediction information on a competition fails to predict a match, and the predictions of the distributor do not match in subsequent competitions. [Means for solving the problem]

[0010] According to one embodiment of the present invention, an information processing device capable of communicating with a terminal device used by a user via a communication network comprises: a providing unit that provides first voting ticket information specified by a provider that provides predicted results for a race to the user's terminal device; an acquiring unit that acquires second voting ticket information on which the user has voted based on all or part of the first voting ticket information; an accumulating unit that accumulates a part of the voting value of the second voting ticket information as an accumulated value; and a payout processing unit that, when the first voting ticket information includes a correct predicted result, pays out a part of the accumulated value as a payout value to a user who has voted on the second voting ticket information based on the first voting ticket information. Effect of the Invention

[0011] According to one aspect of the present invention, when a distributor who distributes prediction information for a competition predicts a result that is not correct, it is possible to prevent a situation in which the distributor's predictions in subsequent competitions are not in line with the predictions of that distributor. [Brief description of the drawings]

[0012] [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] FIG. 2 is a diagram showing an example of a network configuration of the 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 this embodiment. [Figure 4] FIG. 2 is a diagram showing an example of a data structure of a database managed by a server in this embodiment. [Diagram 5] FIG. 13 is a diagram showing an example of a distributor selection screen (non-fever state) in this embodiment. [Figure 6] 13 is a diagram showing an example of a distributor selection screen (during fever) in this embodiment. FIG. [Figure 7] FIG. 13 is a diagram showing an example of a distributor prediction screen in the present embodiment. [Figure 8] FIG. 13 is a diagram showing an example of a voting ticket purchase screen in the present embodiment. [Figure 9] FIG. 13 is a sequence diagram showing the process until broadcaster voting ticket information is displayed between the user terminal and the server in this embodiment. [Figure 10] FIG. 13 is a sequence diagram (Example 1) of a 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 a process between a user terminal and a server in this embodiment up to purchasing a betting ticket based on broadcaster betting ticket information. [Figure 12] FIG. 13 is a diagram illustrating the bonus determination process (Example 1) in this embodiment. [Figure 13] FIG. 11 is a diagram illustrating the bonus determination process (Example 2) in this embodiment. [Figure 14] 13 is a flowchart of a bonus determination process in this embodiment. [Figure 15] FIG. 2 is an example of a configuration block diagram of a hardware environment of a computer that executes a program in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] 1 is a diagram showing an example of an information processing device in this embodiment. The information processing device 1 is capable of communicating with a terminal device 6 used by a user via a communication network. An example of the information processing device 1 is a server 16 described later. An example of the terminal device 6 is a user terminal 12 described later. The information processing device 1 includes a providing unit 2, an acquiring unit 3, an accumulating unit 4, and a payout processing unit 5.

[0014] The providing unit 2 provides the first voting ticket information designated by a provider (for example, a broadcaster described later) who provides predicted results for a race, to the user's terminal device 6. An example of the providing unit 2 is the broadcaster betting ticket information providing unit 45 described later.

[0015] The acquisition unit 3 acquires second voting ticket information in which the user votes based on all or part of the first voting ticket information. An example of the acquisition unit 3 is a user voting ticket information acquisition unit 46, which will be described later.

[0016] The accumulation unit 4 accumulates a part of the voting value of the second voting ticket information as an accumulated value. An example of the accumulated value is a carryover amount described later. An example of the accumulation unit 4 is a bonus management unit 48 described later.

[0017] When the first voting ticket information includes a winning prediction result, the payout processing unit 5 pays out a part of the accumulated value as a payout value to the user who voted for the second voting ticket information based on the first voting ticket information. An example of the payout value is a normal Venus or a special bonus, which will be described later. An example of the payout processing unit 5 is the bonus management unit 48, which will be described later.

[0018] By configuring it in this way, a part of the total sales of voting tickets purchased with reference to the distributor's prediction can be pooled, and if the distributor is correct, a part of the pooled amount can be paid out to the users who purchased voting tickets with reference to the distributor's prediction. Therefore, it is possible to prevent a situation in which a distributor who distributes prediction information for a competition does not predict the same race in subsequent competitions.

[0019] When the first betting ticket information does not include a winning prediction result, the accumulation unit 4 may accumulate the accumulated value in association with the provider. By configuring in this way, for a distributor whose prediction did not win, the accumulated value can be accumulated in association with the distributor so that a larger accumulated value can be paid out in the next race to a user who voted for the second betting ticket information based on the first betting ticket information.

[0020] The payout processing unit 5 determines the payout value according to the voting value of the second voting ticket information. By configuring in this way, for example, depending on whether the distributor's prediction in the previous race was correct or not, it is possible to determine a bonus to be paid to a user who purchased a voting ticket with reference to the distributor's prediction in the current race.

[0021] The payout processing unit 5 determines the payout value according to the winning second betting ticket information. By configuring in this way, for example, when the second betting ticket information is a betting ticket purchased with reference to a race finishing order prediction of a distributor whose prediction in the previous race was incorrect, if the prediction is correct, it is possible to increase the bonus paid to the user who purchased the betting ticket, with the intention of supporting the distributor.

[0022] The payout processing unit 5 adds the difference between the accumulated value in the first competition and the total amount of payout values ​​to all winning users to the accumulated value in the second competition after the first competition. By configuring in this way, the amount of the accumulated value in the first competition that has not been paid out to users can be pooled and carried over to the next race.

[0023] The payout processing unit 5 may further pay out a part of the payout value to the provider. By configuring in this way, it is possible to increase the distributor's motivation to make predictions.

[0024] 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.

[0025] 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.

[0026] 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, and that allows users to view distributors' predicted finishing orders, is installed in the user terminal 12.

[0027] 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.

[0028] 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 prediction of the finishing order of the race, betting ticket information, and the like. The user makes a prediction of the finishing order of the race by referring to the video content, etc. displayed on the GUI image, and purchases a betting ticket via the user terminal 12 by making a specified input.

[0029] If the betting ticket the user has purchased wins the race result, the user will receive a payout based on the payout rate (also called "odds"). Betting tickets can be purchased either for a fee or free of charge. If betting tickets are purchased for a fee, the payout will be made in the form of money, for example. For this reason, the user ID is associated with the user's credit card number, bank account number, or the like, for the purpose of making payments. If betting tickets are purchased free of charge, they can be purchased using points that can be used within the betting ticket purchasing system 11.

[0030] 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, smartphone, tablet terminal, or mobile phone used by the distributor. In the present embodiment, as an example, it may be 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.

[0031] The distributor accesses the server 16 using the distributor terminal 15. The distributor then transmits video content captured by an imaging device to the user terminal 12 via the server 16. (Video content regarding predictions of the finishing order in competitions) will be distributed.

[0032] 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.

[0033] Furthermore, the server 16 can 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. 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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.

[0039] Furthermore, when the distributor information received from the server 16 includes a fever flag=1, which will be described later, the display control unit 23 performs a fever display, which will be described later, for the distributor information with the fever flag=1.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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).

[0044] 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.

[0045] 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.

[0046] The input unit 33 is an input interface for inputting instructions or inputting 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).

[0047] The server 16 includes a communication unit 41, a control unit 42, and a storage unit 50. 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.

[0048] 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 broadcast 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, and a bonus management unit 48.

[0049] In response to a distribution request from a distributor, the distribution control unit 43 accepts distributor information about the distributor and video content shot by the distributor. The distribution control unit 43 registers the distributor information in the storage unit. The distribution control unit 43 distributes the registered distributor information to the user terminal 12 on which the 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.

[0050] The broadcaster betting ticket information acquisition unit 44 acquires betting ticket information (broadcaster betting ticket information) designated by the broadcaster. Here, the broadcaster betting ticket information includes predicted information on the finishing order of the race input by the broadcaster and betting ticket information purchased by the broadcaster.

[0051] 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.

[0052] 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 .

[0053] 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.

[0054] When a distributor starts distributing video content related to the current competition, the bonus management unit 48 determines whether the distributor's predictions in the previous competition were correct. If the distributor's predictions in the previous competition were not correct, the bonus management unit 48 assigns a fever flag to the distributor information of the distributor. The fever flag indicates that if the distributor's predictions in the current competition are correct, a special bonus will be paid to users who purchased voting tickets based on the distributor's predictions.

[0055] After the race is over and the order of finish is determined, if the prediction of the distributor to whom the fever flag is attached is correct, the bonus management unit 48 performs processing to pay a special bonus to the user who purchased the voting ticket based on the prediction of the distributor.

[0056] Here, the source of the bonus may be, for example, a part of the total amount of sales of betting tickets for the entire race. Also, the source of the bonus may be, for example, a part of the total amount of sales of betting tickets purchased with reference to the broadcaster's prediction. The bonus management unit 48 sets aside a part of the total amount of sales of the betting tickets. The bonus management unit 48 may determine the bonus amount according to the amount of sales of the betting tickets purchased with reference to the broadcaster's prediction. At this time, the bonus management unit 48 adds the difference between a part of the total amount of sales of betting tickets in the current race and the total amount of bonuses paid to all users who won to a part of the total amount of sales of betting tickets in the next race. It should be noted that the bonus management unit 48 may further pay out a part of the bonus to the broadcaster.

[0057] The storage unit 50 stores a broadcaster management database 51, a broadcaster betting ticket information database 52, a user possession information database 53, a user betting ticket information database 54, an odds information database 55, and a carryover money management database 56. In the following, the databases are referred to as "DBs."

[0058] The broadcaster management DB51 is a database that manages broadcasters. The broadcaster betting ticket information DB52 is a database that manages betting ticket information specified by broadcasters. The user's owned information DB53 is a database that manages the amount of money and points owned by users. The user betting ticket information DB54 is a database that manages betting ticket information purchased by users. The odds information DB55 is a database that manages information regarding odds for each betting ticket in a competition. The carryover money management DB56 is a database that is used to add the difference between a preset upper limit amount and the total amount of bonuses paid out to users in the current competition as a carryover money to the upper limit amount in the next and subsequent competitions.

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

[0060] The distributor management DB51 includes data items of "distributor ID", "race ID", "video content ID", "success flag", and "fever flag". Hereinafter, each record of the distributor management DB51 may be referred to as distributor information. The item "distributor ID" stores information (distributor ID) that identifies the distributor. The item "race ID" stores information (race ID) that identifies the race. The item "video content ID" stores information (video content ID) that identifies the video content of the corresponding distributor. The item "success flag" stores a flag that determines whether the distributor has predicted the finishing order of the race in the race. If the distributor has predicted the finishing order of the race in the race, a success flag = 1 is stored. If the distributor has not predicted the finishing order of the race in the race, a success flag = 0 is stored. The item "fever flag" stores a fever flag that indicates that if the distributor's prediction in this race is successful, a special bonus will be paid to users who purchased voting tickets based on the distributor's prediction. Specifically, if the hit flag of the previous record (distributor information) is 0, the "Fever Flag" item of the current record (distributor information) will store Fever Flag = 1. If the hit flag of the previous record (distributor information) is 1, the "Fever Flag" item of the current record (distributor information) will store Fever Flag = 0.

[0061] The broadcaster betting ticket information DB52 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 group numbers of the finishing order from 1st place to a predetermined position in the race (race) identified by the race ID. Note that in this embodiment, exacta bets, place bets, etc. are not mentioned for the sake of convenience of explanation, 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.

[0062] The user holdings information DB53 includes the data items of "User ID", "Held amount", and "Held points". The item "User ID" stores information that identifies the user (user ID). The item "Held amount" stores the amount of money currently available for use by the user in the betting ticket purchasing system 11. The item "Held points" stores the points currently available for use by the user in the betting ticket purchasing system 11.

[0063] The user betting ticket information DB54 includes data items of "User ID", "Race ID", "Bet", "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 "Bet" stores the group number of the finishing order from 1st place to a specified position in the race (race) identified by the race ID. The item "Purchase Amount" stores the stake (an item used in the case of a paid event, and the stake is in currency) corresponding to the betting ticket information. The item "Purchase Points" stores the stake (an item used in the case of a free event, and the stake is in 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.

[0064] The odds information DB55 includes the data items of "Race ID", "Bet ticket", and "Odds". The item "Race ID" stores information (race ID) that identifies the race. The item "Bet ticket" 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 ticket.

[0065] The carryover management DB56 includes data items of "Race ID", "Total Sales", "Exchange Pt Upper Limit", "Exchange Pt Refund Total", and "Carryover Amount". The item "Race ID" stores information (race ID) that identifies the race. The item "Total Sales" stores the total number of betting tickets sold in the race or the total number of betting tickets purchased in the race with reference to the broadcaster's prediction. In this embodiment, betting tickets can be purchased for 100 yen each. The item "Exchange Pt Upper Limit" stores the upper limit of the total amount of money (or points) that can be paid out to users in the race. The item "Exchange Pt Refund Total" stores the total amount of bonuses paid to users who purchased betting tickets with reference to the broadcaster's prediction that specified a winning betting ticket in the race. The item "Carryover Amount" stores the difference (carryover amount) between the "Exchange Pt Upper Limit" and the "Exchange Pt Refund Total" in the race.

[0066] Next, the user interface of the dedicated application program installed in the user terminal 12 will be described with reference to Figures 5, 6, 7 and 8. 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.

[0067] 5 is a diagram showing an example of a broadcaster selection screen (non-fever mode) in this embodiment. A broadcaster selection screen 61 includes a login user display field 62, an owned amount display field 63, an owned points display field 64, a purchase target race name display field 65, and a broadcaster list 66.

[0068] 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.

[0069] In the distributor list 66, thumbnail images 66a, 66b, 66c, ... corresponding to distributor information related to race predictions are displayed for the race displayed in the purchase target race name display field 65. The distributor list 66 can be scrolled using the operation display unit 13 to display distributor information that is not currently displayed.

[0070] FIG. 6 is a diagram showing an example of a broadcaster selection screen (during fever) in this embodiment. In the broadcaster selection screen 61 in FIG. 6, a specific broadcaster or any broadcaster in the broadcaster list 66 is in fever state. The fever state is a state in which, if a specific broadcaster or any broadcaster does not predict correctly in the previous race, a special bonus will be awarded if a betting ticket is purchased in the current race based on the broadcaster's prediction. A fever display 67 is displayed on the thumbnail image 66 of a broadcaster in fever state. For example, when a thumbnail image 66 with a fever display 67 is tapped, the screen in FIG. 7 is displayed.

[0071] 7 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 fever display 75, a fever content field 76, a broadcaster betting ticket information display field 77, and a details display button 78.

[0072] 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 distributor display field 73 displays the name of the distributor selected in the distributor list 66 on the distributor selection screen 61. The distributor video content display field 74 displays the video content (e.g., live streaming video in streaming format) of the selected distributor. The fever display 75 displays a display indicating that the distributor is in a fever state. The fever content field 76 displays the fact that the distributor is currently in a fever state, the amount of the carryover money, and if a user purchases a betting ticket based on the broadcaster's prediction this time, the carryover money will be split among the users who purchased the ticket. The distributor betting ticket information display field 77 displays the set number of the betting ticket specified by the distributor and its odds. When the detailed display button 78 is tapped, the screen of FIG. 8 is displayed, and the user can check the detailed contents of the betting ticket specified by the distributor.

[0073] 8 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 designation field 84, an owned amount display field 85, an owned amount designation field 86, a distributor predicted voting ticket display field 87, a fever display field 89, and a purchase execution button 96.

[0074] 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.

[0075] The broadcaster predicted betting ticket display field 87 includes a predicted betting ticket list 87a, a betting amount / betting point total display field 91, a set unit purchase button 92, an edit button 93, and a delete button 94. The broadcaster predicted betting ticket display field 87 displays the set number of the betting ticket and the betting amount or betting points specified by broadcaster A by default.

[0076] The prediction betting ticket list 87a includes a group number display field 88, an odds display field 89, and a bet / betting 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. 8, 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".

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

[0078] 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.

[0079] 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.

[0080] The fact that the player is currently in a fever state and the amount of the carried-over money are displayed in the fever display field 89. When the purchase execution button 96 is tapped, the purchase process of the betting ticket information specified on the betting ticket purchase screen 81 is executed.

[0081] 9 is a sequence diagram of the process until broadcaster betting ticket information is displayed between the user terminal 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).

[0082] The server 16 (bonus management unit 48) identifies a broadcaster who is making a prediction about a race that is about to start from the broadcaster management DB 51, and refers to the hit flag of the broadcaster information about the race immediately before the identified broadcaster information. If the hit flag is 0 (not hitting), the server 16 (bonus management unit 48) updates the fever flag of the current broadcaster information of the identified broadcaster to 1 (S3).

[0083] The server 16 acquires distributor information (including distributor ID, race ID, video content ID, and fever flag) of the identified distributor (distributor making predictions about the upcoming race) from the distributor management DB 51 (S4). The server 16 transmits the acquired distributor information to the user terminal 12 (S5).

[0084] 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. 6 (S6). At this time, the user terminal 12 adds a fever display 67 to thumbnail images of distributor information that includes a fever flag = 1.

[0085] The user selects, for example, a thumbnail image 66a of distributor information of distributor A from the distributor list 66 (S7). Then, the user terminal 12 requests video content from distributor A based on the video content ID (S8). In response to the request, the user terminal 12 receives the video content from the server 16 (S9). The user terminal 12 plays the received video content on the distributor prediction screen 71 of FIG.

[0086] When broadcaster A designates a betting ticket, the server 16 (broadcaster betting ticket information acquisition unit 44) acquires the contents (broadcaster betting ticket information) (S10). 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 52. 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 (S11).

[0087] 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 77 of the broadcaster prediction screen 71 of FIG. 7 (S12).

[0088] 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.

[0089] The user taps the details display button 78 on the broadcaster prediction screen 71 in Fig. 7. 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. 8 is displayed.

[0090] On the betting ticket purchase screen 81, the user may erase part of the broadcaster betting ticket information, or add the user's own betting ticket information to the broadcaster betting ticket information. The user may also specify the amount of bet for each piece of betting ticket information (S22). In response to these operations, the user terminal 12 (The prediction adopting unit 24) updates the information held in the temporary holding area 28. That is, the user terminal 12 (the prediction adopting unit 24) updates the contents of the temporary holding area 28 in response to an input operation on the betting ticket purchase screen 81 (holds all or a part of the broadcaster betting ticket information in the temporary holding area 28).

[0091] On the betting ticket purchase screen 81, when the user has confirmed 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).

[0092] The server 16 (user voting ticket information acquisition unit 46) acquires the purchase request. The (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 54. 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 owned information DB 53 based on the payment details, and notifies the user terminal 12 of the completion of the payment processing (S26).

[0093] After the betting period for the race is closed, the server 16 registers the finalized odds information in the odds information DB 55. After the race, when the finishing order is finalized, the server 16 (bonus management unit 48) performs a bonus determination process (S27).

[0094] 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.

[0095] After S12 in FIG. 9, the user taps the details display button 78 on the broadcaster prediction screen 71 in FIG. 7. Then, the user terminal 12 (prediction adoption unit 24) holds the broadcaster betting ticket information of broadcaster A in the temporary holding area 28 (S31). At this time, the betting ticket purchase screen 81 in FIG. 8 is displayed. After that, the user operates the operation display unit 13 to return to the broadcaster selection screen 61 in FIG. 6. 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. 8 for broadcaster A, the broadcaster betting ticket information of broadcaster A will be displayed.

[0096] 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 (S32). Then, the user terminal 12 requests video content from distributor B (S33). In response to the request, the user terminal 12 receives the video content from the server 16 (S34). The user terminal 12 plays the received video content on the distributor prediction screen 71 of FIG.

[0097] 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 52. 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 (S35).

[0098] 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 (S36). Then, the user taps the details display button 78 on the broadcaster prediction screen 71 of Fig. 7. Then, the user terminal 12 (prediction adoption unit 24) holds the broadcaster voting ticket information of broadcaster B in the temporary holding area 28 (S27). At this time, the voting ticket purchase screen 81 of Fig. 8 is displayed.

[0099] On the betting ticket purchase screen 81, the user may erase part of the broadcaster voting ticket information for 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 (S38). 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).

[0100] On the betting ticket purchase screen 81, when the user has confirmed the betting ticket to be purchased, he / she taps the purchase execution button 96 (S39). 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 (S40).

[0101] Here, the purchase request is a purchase request based on the contents of the temporary holding area 28 specified in S37 and S38. This may purchase only the betting tickets purchased on the screen on which 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 distributors 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.

[0102] The server 16 (user voting ticket information acquisition unit 46) acquires the purchase request. The (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 54. The server 16 (payment processing unit 47) performs payment processing for the purchase of the betting ticket based on the purchase request (S41). When the payment processing is completed, the server 16 updates the contents of the user owned information DB 53 based on the payment details, and notifies the user terminal 12 of the completion of the payment processing (S42).

[0103] After the betting period for the race is closed, the server 16 registers the confirmed odds information in the odds information DB 55. After the race, when the finishing order is confirmed, the server 16 (bonus management unit 48) performs a bonus determination process (S43).

[0104] Fig. 12 is a diagram for explaining the bonus determination process (Example 1) in this embodiment. In the bonus determination process explained in Fig. 12, when none of the broadcasters are in a fever state, a normal bonus is paid out to each user who has purchased a betting ticket with reference to the broadcaster's prediction in that race and has won. When a specific broadcaster has won a prediction in a fever state, a special bonus is paid out to each user who has purchased a betting ticket with reference to the specific broadcaster's prediction and has won.

[0105] Fig. 12(A) is a table explaining the bonus determination process for the first race. Fig. 12(B) is a table explaining the bonus determination process for the second race. Fig. 12(C) is a table explaining the bonus determination process for the third race. Figs. 12(A) to 12(C) each show the purchase amounts tallied by grouping the user betting ticket information DB54 by race ID, distributor ID, and betting ticket set number.

[0106] For example, if a particular broadcaster does not win a prediction for a given race, a fever state is generated to support the broadcaster. That is, if a user purchases a betting ticket for the next race based on the broadcaster's prediction during the fever state and the ticket wins, the bonus for the user is increased. The amount of increase in the special bonus when a fever occurs is determined by the number of tickets (total purchase amount by users) purchased based on the broadcaster's prediction for the race that did not win. The amount of increase in the special bonus may be determined by the popularity of the broadcaster for the race that did not win.

[0107] In the example of Fig. 12, X% (X: any integer) of the total amount of sales of voting tickets purchased based on the broadcaster's predictions may be returned to users as exchange points, and all points not paid out are pooled. In the race following a race in which no winning combinations were achieved, a specific broadcaster goes into a fever state, and the pooled points are shared among users who purchased voting tickets based on the broadcaster's predictions for that race and won. In the example of Fig. 12, the specific broadcasters are Broadcaster A and Broadcaster B.

[0108] In FIG. 12(A), the total number of voting tickets sold by each broadcaster in the first race (=total sales amount of voting tickets purchased by users based on broadcaster predictions / 100 yen) is 5100. In this embodiment, the exchange point (Pt) return rate on the total sales amount of voting tickets sold in the held race is, for example, 1%. In this case, the upper limit of exchange Pt is 5100 tickets x 100 yen x 0.01 = 5100 yen. In the first race, the broadcasters (broadcasters whose predictions were used as reference and whose voting tickets were purchased by users) are Broadcaster A, Broadcaster B, Broadcaster C, and Broadcaster D. The number of voting tickets sold by each broadcaster based on the broadcaster voting ticket information is as shown in the table.

[0109] In the first race, let's say that ticket B wins. In this case, the total amount of exchange points paid out by each broadcaster who predicted that ticket B would win is (50 + 50 + 200 + 50) x odds 4.5 (multiplication factor) x 100 yen x maximum user return rate 0.02 = 3,150 yen (total amount of exchange points paid out).

[0110] Here, the total exchange point refund amount: 3150 yen does not exceed the exchange point upper limit amount: 5100 yen, so the exchange points (regular bonus) refunded to users who purchased voting tickets based on the predictions of the broadcaster who made the correct predictions will be as follows. For example, if one voting ticket is given per user, the exchange points (regular bonus) will be determined as 3150 yen / (50 people + 50 people + 200 people + 50 people) = 9 yen / person. The amount of 1950 yen obtained by subtracting the total exchange point refund amount: 3150 yen from the exchange point upper limit amount: 5100 yen will be carried over as a carryover amount to the exchange point upper limit amount for the next race.

[0111] In FIG. 12(B), the total number of betting tickets sold by each broadcaster in the second race (=total sales amount of betting tickets purchased by users based on broadcaster predictions / 100 yen) is 3680. Also, since the exchange point return rate is 1%, the upper limit of exchange points is 3680 tickets x 100 yen x 0.01 = 3680 yen. In this case, the carryover amount of 1950 yen from the previous race is added, and the upper limit of exchange points becomes 5630 yen.

[0112] In the second race, let's say that ticket E wins. In this case, the total amount of exchange points paid out by each distributor who predicted that ticket B would win will be (0 + 0 + 10 + 10) x odds 15 (multiplication factor) x 100 yen x maximum user return rate 0.02 = 600 yen (total amount of exchange points paid out).

[0113] Here, since the total exchange point refund amount of 600 yen does not exceed the exchange point upper limit of 5,630 yen, the exchange points (regular bonus) refunded to users who purchased voting tickets based on the predictions of a specific broadcaster who made a correct prediction will be as follows. For example, if there is one voting ticket per user, the exchange points (regular bonus) will be determined as 600 yen / (0 people + 0 people + 10 people + 10 people) = 30 yen / person. The amount of 5,030 yen obtained by subtracting the total exchange point refund amount of 600 yen from the exchange point upper limit of 5,630 yen will be carried over as a carryover amount to the exchange point upper limit of the next race.

[0114] Here, in the second race, even though users purchased betting tickets based on the predictions of specific broadcasters A and B, their predictions did not come true, so a feverish state occurs in the next race (Figure 12(C)).

[0115] In FIG. 12(C), the total number of tickets sold by each broadcaster in the third race (=total sales amount of tickets purchased by users based on broadcaster predictions / 100 yen) is 2590. Also, since the exchange point return rate is 1%, the upper limit of exchange points is 2590 tickets x 100 yen x 0.01 = 2590 yen. In this case, the carryover amount of 5030 yen from the previous race is added, and the upper limit of exchange points is 7620 yen.

[0116] In the third race, let's say ticket A wins. In this case, the total amount of exchange points paid out by each streamer who predicted that ticket A would win will be (150 voting tickets purchased based on streamer C's prediction + 50 voting tickets purchased based on streamer D's prediction) x odds 3.5 (multiplication factor) x 100 yen x maximum user return rate 0.02 + 5030 carried over from the previous race = 6430 yen (total amount of exchange points paid out).

[0117] Here, the total exchange point refund amount: 6430 yen does not exceed the upper limit of exchange points: 7620 yen. In this case, the exchange points (regular bonus) refunded to users who purchased voting tickets based on broadcaster C's predictions is (150 voting tickets purchased based on broadcaster C's predictions) x odds 3.5 (multiplication factor) x 100 yen x maximum user return rate 0.02 = 1050 yen. For example, if one voting ticket is purchased per user, the exchange points (regular bonus) is 1050 yen / 150 people = 7 yen / person.

[0118] The exchange points (regular bonus) that will be returned to users who purchased voting tickets based on Streamer D's predictions will be calculated as follows: (50 voting tickets purchased based on Streamer D's predictions) x odds 3.5 (Multiplier) x 100 yen x maximum user return rate 0.02 = 350 yen. For example, if one voting ticket is given to each user, the exchange points (regular bonus) will be 350 yen / 50 people = 7 yen / person.

[0119] On the other hand, the exchange points (special bonus) refunded to users who purchased voting tickets based on the predictions of streamers A and B during the fever state will be the amount of the carryover funds from the previous time, 5,030 yen, divided equally among the number of users. For example, if one voting ticket is issued per user, the exchange points (special bonus) will be 5,030 yen / (200 people + 100 people) = 16 yen / person.

[0120] Fig. 13 is a diagram for explaining the bonus determination process (Example 2) in this embodiment. Fig. 13(A) and Fig. 13(B) are the same tables as Fig. 12(A) and Fig. 12(B). Fig. 13(C) is different from Fig. 12(C) in the exchange Pt payout amount.

[0121] In FIG. 12(C), when a particular broadcaster makes a correct prediction during a fever state, the exchange points (special bonus) that are refunded to users who purchased voting tickets based on the particular broadcaster's prediction are split equally between those users in the form of carryover points from the previous time.

[0122] In contrast, in Figure 13 (C), the exchange points (special bonus) paid out to users who purchased betting tickets based on the predictions of a specific broadcaster are divided equally between the users after subtracting the exchange points (regular bonus) paid out to users who purchased betting tickets based on the predictions of a broadcaster who is not in a fever state from the exchange point limit for the current race (including the carryover points from the previous race).

[0123] In FIG. 13(C), the exchange points (regular bonus) paid out to users who purchased voting tickets based on the predictions of broadcasters C and D is 7 yen per person.

[0124] On the other hand, the exchange points (special bonus) paid out to users who purchased voting tickets based on the predictions of broadcasters A and B in a fever state is 6220 yen, calculated by subtracting the exchange points (regular bonus) of 1400 yen paid out to users who purchased voting tickets based on the predictions of broadcasters C and D from the exchange points of 7620 yen. For example, if one user receives one voting ticket, the exchange points (special bonus) is 6220 yen / (200 people + 100 people) = 20 yen / person.

[0125] This allows the management side to support the broadcaster if the broadcaster's prediction is incorrect, and to pay out more money or points than usual to users who purchased voting tickets based on the broadcaster's prediction when the broadcaster is correct.

[0126] In addition, in FIG. 12 and FIG. 13, the normal bonus and the special bonus may be paid out to the broadcaster. That is, in the case of a normal bonus, the broadcaster may be paid out the total exchange points / (the number of users who purchased voting tickets based on the predictions of each broadcaster + the number of broadcasters). In the case of a special bonus, the broadcaster may be paid out the exchange points (special bonus) = the previous carryover amount / (the number of users who purchased voting tickets based on the predictions of each broadcaster with a fever flag and were correct + the number of broadcasters with a fever flag (broadcasters who were correct this time)). In addition, the exchange points (special bonus) paid out to the broadcaster is calculated by subtracting the exchange points (normal bonus) paid out to users who purchased voting tickets based on the predictions of broadcasters without a fever flag and were correct from the upper limit of exchange points for this race (carrying over the carryover amount from the previous race), It can also be calculated by dividing by (the number of users who purchased voting tickets based on the predictions of each streamer with a fever flag and got the predictions correct + the number of streamers with a fever flag (streamers who got the predictions correct this time)).

[0127] 14 is a flowchart of the bonus determination process in this embodiment. When the bonus management unit 48 receives a notification that the finishing order of the race has been determined (S51), it groups the user betting ticket information DB 54 by race ID, distributor ID, and betting ticket set number, and tallies the purchase amounts. Furthermore, the bonus management unit 48 calculates the total sales amount of the betting tickets sold in that race from the tallied purchase amounts (S52).

[0128] The bonus management unit 48 acquires the carryover amount from the previous race from the carryover amount management DB 56 (S53). The bonus management unit 48 calculates the upper limit of exchange points from the exchange point return rate (e.g., 1%) relative to the total sales amount of the betting tickets purchased by the user, with reference to the distributor's predictions for that race. At this time, if there is carryover amount in S53, the bonus management unit 48 adds the amount to the calculated upper limit and sets it as the upper limit of exchange points (S54).

[0129] The bonus management unit 48 acquires the fever flags of the distributors who are predicting the current race from the distributor management DB 51 (S55). The bonus management unit 48 calculates the exchange points (normal bonus) for users who purchased voting tickets based on the predictions of distributors who do not have a fever flag using the following formula (S56). Exchange points (regular bonus) refunded to all users who purchased voting tickets based on each streamer's predictions = (number of voting tickets purchased based on each streamer's predictions) x odds x 100 yen x maximum user return rate

[0130] The bonus management unit 48 calculates exchange points (special bonus) for users who have purchased voting tickets with reference to the predictions of the distributors for whom the fever flag has been raised, using the following formula (S57). Exchange points (special bonus) returned to each user who purchased a voting ticket based on the predictions of each streamer with a fever flag and got the correct answer = previous carryover points / (number of users who purchased a voting ticket based on the predictions of each streamer with a fever flag and got the correct answer)

[0131] As explained in Figure 13 (C), the exchange points (special bonus) may be calculated by subtracting the exchange points (regular bonus) paid out to users who purchase voting tickets based on the predictions of streamers who do not have a fever flag and win, from the upper limit of exchange points for the current race (including carryover points from the previous race), and dividing the remainder by the number of users who purchase voting tickets based on the predictions of streamers who have a fever flag and win.

[0132] The bonus management unit 48 determines whether the total exchange Pt is equal to or less than the exchange Pt upper limit (S58). If the total exchange Pt exceeds the exchange Pt upper limit (NO in S58), the bonus management unit 48 adjusts the bonus paid out to the user so that it is within the exchange Pt upper limit. For example, the bonus management unit 48 adjusts the user maximum return rate of the normal bonus so that the total exchange Pt is equal to or less than the exchange Pt upper limit. For example, the user maximum return rate can be adjusted within a range of 0.01% to 2%.

[0133] If the total exchange points is equal to or less than the upper limit of exchange points (YES in S58), the bonus management unit 48 determines and pays out the bonus amount calculated in S56 and S57 (S60). At this time, the bonus management unit 48 updates the amount of money (or points) held by the user to whom the bonus is paid out in the user holding information DB 53.

[0134] The bonus management unit 48 registers the amount obtained by subtracting the total exchange Pt refund amount from the exchange Pt upper limit amount as a carryover amount in the carryover amount management DB 56 (S61). At this time, the bonus management unit 48 registers the race ID, the total number of betting tickets sold for that race, the exchange Pt upper limit amount calculated in S54, the total exchange Pt refund amount, and the carryover amount in the carryover amount management DB 56 as carryover amount management information.

[0135] The bonus management unit 48 updates the hit flag and fever flag of the distributor in the distributor management DB 62 based on the hit result of the current race (S62). For example, the bonus management unit 48 sets the hit flag of a distributor whose prediction in the current race was successful to 1. The bonus management unit 48 sets the hit flag of a distributor whose prediction in the current race was not successful to 0. In addition, if the prediction of a distributor who was in a fever state in the current race was successful, the bonus management unit 48 sets the fever flag of that distributor to 0.

[0136] In this way, a few percent of the total amount of sales of voting tickets purchased based on the broadcaster's predictions may be returned to users as exchange points, and any remaining points not paid out may be pooled. Using this as a source of funds, a special bonus can be paid out to users who purchase voting tickets based on the current race predictions of broadcasters whose predictions in the previous race did not come true, but who do come true.

[0137] 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.

[0138] 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.

[0139] 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, and a bonus management unit 48. The ROM 103 indicates a read-only memory. The RAM 104 is a memory for temporary storage.

[0140] 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.

[0141] 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.

[0142] 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.

[0143] 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.

[0144] 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.

[0145] According to this embodiment, for a distributor whose predictions in the previous race were not successful, a user is made to be in a fever state for the next race, and a betting ticket is purchased based on the predictions of such a distributor to show support, and if the prediction is successful, the bonus amount for the user is increased. This makes it possible to prevent a situation in which a distributor who delivers prediction information for a race does not predict the same race in subsequent races.

[0146] In this embodiment, if a specific distributor's prediction in a specific race is not correct, the next race is put into a fever state, but this is not limited to this and may be applied to all distributors. In other words, if any distributor's prediction in a specific race is not correct, the next race is put into a fever state.

[0147] In addition, the bonus amount may be increased and paid not only to users who purchase based on the predictions of a broadcaster in a fever state and get the predictions right, but also to the broadcaster. The bonus payout is the same whether it is paid for (e.g., yen) or free (e.g., points).

[0148] 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.

[0149] In addition to the above embodiment, the following is further noted. (Appendix 1) An information processing device capable of communicating with a terminal device used by a user via a communication network, A providing unit that provides first betting ticket information designated by a provider that provides a predicted result of a race to the terminal device of the user; an acquisition unit that acquires second voting ticket information on which the user voted based on all or a part of the first voting ticket information; An accumulation unit that accumulates a part of the voting value of the second voting ticket information as an accumulated value; a payout processing unit that pays out a part of the accumulated value as a payout value to a user who voted for the second betting ticket information based on the first betting ticket information when the first betting ticket information includes a correct prediction result; An information processing device comprising: By configuring it in this way, a part of the total sales of voting tickets purchased with reference to the distributor's prediction can be pooled, and if the distributor is correct, a part of the pooled amount can be paid out to the users who purchased voting tickets with reference to the distributor's prediction. Therefore, if the prediction of a distributor who distributes prediction information for a competition is not correct, it is possible to prevent a situation in which the prediction of that distributor is not followed in subsequent competitions. (Appendix 2) The accumulation unit accumulates the accumulated value in association with the provider when the first betting ticket information does not include a winning prediction result. 2. The information processing device according to claim 1 . By configuring in this manner, in the case of a distributor whose prediction was not correct, the accumulated value can be accumulated in association with that distributor so that a larger accumulated value can be paid out in the next race to the user who voted for the second voting ticket information based on the first voting ticket information. (Appendix 3) The payout processing unit determines the payout value according to the voting value of the second voting ticket information. 3. The information processing device according to claim 1 or 2. By configuring it in this manner, for example, the bonus to be paid to a user who purchases a betting ticket can be determined by referring to the distributor's prediction for the current race, depending on whether or not the distributor's prediction for the previous race was correct. (Appendix 4) The payout processing unit determines the payout value according to the winning second betting ticket information. 4. The information processing device according to claim 1, By configuring it in this manner, for example, the bonus to be paid to a user who purchases a betting ticket can be determined by referring to the distributor's prediction for the current race, depending on whether or not the distributor's prediction for the previous race was correct. (Appendix 5) The payout processing unit adds the difference between the accumulated value in the first competition and the total amount of payout values ​​to all winning users to the accumulated value in a second competition subsequent to the first competition. 5. The information processing device according to claim 1, By configuring it in this manner, for example, if the second voting ticket information is a voting ticket purchased based on a prediction of the finishing order of a race by a broadcaster whose prediction in the previous race was incorrect, and that prediction turns out to be correct, the bonus paid to the user who purchased the voting ticket can be increased as a token of support for the broadcaster. (Appendix 6) The payout processing unit further pays out a part of the payout value to the provider. 6. The information processing device according to claim 1, By configuring in this way, it is possible to increase the distributor's motivation for making predictions. (Appendix 7) A computer capable of communicating with a terminal device used by a user via a communication network, A provision process of providing first betting ticket information designated by a provider who provides a predicted result for a race to the terminal device of the user; an acquisition process for acquiring second voting ticket information on which the user voted based on all or a part of the first voting ticket information; an accumulation process of accumulating a part of the voting value of the second voting ticket information as an accumulated value; a payout process for paying out a part of the accumulated value as a payout value to a user who voted for the second betting ticket information based on the first betting ticket information when the first betting ticket information includes a correct prediction result; A dispensing control program that executes the above. By configuring in this manner, it is possible to prevent a situation in which, when a distributor who distributes prediction information for a competition predicts a result does not come true, the predictions of that distributor do not come true in subsequent competitions. (Appendix 8) A computer capable of communicating with a terminal device used by a user via a communication network, A provision process of providing first betting ticket information designated by a provider who provides a predicted result for a race to the terminal device of the user; an acquisition process for acquiring second voting ticket information on which the user voted based on all or a part of the first voting ticket information; an accumulation process of accumulating a part of the voting value of the second voting ticket information as an accumulated value; a payout process for paying out a part of the accumulated value as a payout value to a user who voted for the second betting ticket information based on the first betting ticket information when the first betting ticket information includes a correct prediction result; A dispensing control method that executes the above. By configuring in this manner, it is possible to prevent a situation in which, when a distributor who distributes prediction information for a competition predicts a result does not come true, the predictions of that distributor do not come true in subsequent competitions. [Explanation of symbols]

[0150] 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 Bonus Management Department 50 Storage section 51 Broadcaster Management DB 52 Broadcaster voting ticket information DB 53 User-owned information DB 54 User voting ticket information DB 55 Odds Information DB 56 Carryover Management DB

Claims

1. a processor, the processor comprising: Providing first betting ticket information designated by the prediction provider for the first race to a terminal device of a user; acquiring second voting ticket information on which the user voted based on the first voting ticket information; Adding a part of the voting value of the second betting ticket information to an accumulated value stored in association with the first event; A payout value, which is a part of the cumulative value granted to a user who wins based on the first betting ticket information, is subtracted from the cumulative value, and the updated cumulative value is carried over to a second competition subsequent to the first competition. Information processing device.

2. The processor provides first betting ticket information designated by the prediction provider for the first race to a terminal device of the user; A processor obtains second voting ticket information in which a user votes based on the first voting ticket information; A processor adds a part of the voting value of the second betting ticket information to a cumulative value stored in association with the first event; The processor subtracts a payout value, which is a part of the cumulative value granted to the user who wins based on the first betting ticket information, from the cumulative value, and carries over the updated cumulative value to a second competition subsequent to the first competition. Information processing methods.

3. Displaying the first voting ticket information designated by the prediction provider for the first competition on the screen of the user's terminal device; accepting votes of second voting ticket information from a user based on the first voting ticket information; A program for causing a computer to execute a process, A part of the voting value of the second voting ticket information is added to an accumulated value stored in association with the first competition, A payout value, which is a part of the accumulated value granted to a user who wins based on the first betting ticket information, is subtracted from the accumulated value, and the accumulated value updated is carried over to a second competition subsequent to the first competition. program.

4. A server and a terminal device are provided, The server, Providing first betting ticket information designated by the prediction provider for the first race to a terminal device of a user; acquiring second voting ticket information on which the user voted based on the first voting ticket information; Adding a part of the voting value of the second betting ticket information to an accumulated value stored in association with the first event; A payout value, which is a part of the cumulative value granted to a user who wins based on the first betting ticket information, is subtracted from the cumulative value, and the updated cumulative value is carried over to a second competition subsequent to the first competition. system.

Images