JP7610153B2 - Information processing device, payout control program, and payout control method - Google Patents

Description

The present invention relates to an information processing device, a payout control program, and a payout control method.

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 ticket purchasing system that allows users to place bets in public races such as horse racing, boat racing, and bicycle racing.

Another example of such a service is a video distribution service. A 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 such service is an amusement service. For example, an amusement service is a game system equipped with a jackpot lottery device that executes a jackpot lottery for one of a number of game devices that satisfies a predetermined lottery start condition (for example, Patent Document 1).

JP 2010-131285 A

One example of a video distribution service is a service that distributes video content related to predictions for publicly managed races. Such video contributors (or distributors) are generally evaluated based on the number of page views (PV). Therefore, in video content related to predictions for publicly managed races, for example, a distributor predicts the finishing order of a publicly managed race, and if that prediction is correct, it is generally thought that the number of PVs will also tend to increase. Users who wish to purchase betting tickets would prefer to refer to the predictions of distributors whose predictions have been correct rather than those of distributors whose predictions have not been correct.

However, if users only refer to the predictions of a particular streamer when purchasing voting tickets, purchases will be concentrated on voting tickets for a particular group number, making the service less interesting as an entertainment-based service.

Furthermore, for video content by broadcasters whose predictions were incorrect, viewers will be less likely to use the broadcaster's predictions for future races as a reference, and the number of pageviews 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 pageviews for video content related to predictions for public races as a whole will decrease, and there is a risk that the number of users using such services will decrease.

The present invention provides a technology that prevents a situation in which, when a distributor who distributes prediction information for a competition predicts a result does not come true, the distributor's predictions do not match in subsequent competitions.

According to one aspect of the present invention, 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 first voting ticket information designated by a provider that provides predicted results for a competition 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 pays out a part of the accumulated value as a payout value to a user who has voted for the second voting ticket information based on the first voting ticket information when the first voting ticket information includes a predicted result that has come true.

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 for subsequent competitions do not match the results.

FIG. 1 is a diagram illustrating an example of an information processing device according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of a network configuration of the betting ticket purchasing system in this embodiment. FIG. 2 is a diagram showing an example of functional blocks of the betting ticket purchasing system in this embodiment. FIG. 2 is a diagram showing an example of a data structure of a database managed by a server in this embodiment. FIG. 13 is a diagram showing an example of a distributor selection screen (non-fever state) in the present embodiment. 13A and 13B are diagrams showing an example of a distributor selection screen (during fever) in this embodiment. FIG. 13 is a diagram showing an example of a distributor prediction screen in the present embodiment. FIG. 13 is a diagram showing an example of a voting ticket purchase screen in the present embodiment. 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. FIG. 13 is a sequence diagram (Example 1) of the process up to purchasing a betting ticket based on broadcaster betting ticket information between a user terminal and a server in this embodiment. FIG. 13 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. FIG. 13 is a diagram illustrating the bonus determination process (Example 1) in this embodiment. FIG. 13 is a diagram illustrating the bonus determination process (Example 2) in this embodiment. 13 is a flowchart of a bonus determination process in this embodiment. FIG. 2 is an example of a configuration block diagram of a hardware environment of a computer that executes a program in this embodiment.

FIG. 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, which will be described later. An example of the terminal device 6 is a user terminal 12, which will be 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.

The providing unit 2 provides the first voting ticket information specified by a provider (e.g., a broadcaster described below) who provides predicted results for the competition to the user's terminal device 6. An example of the providing unit 2 is the broadcaster voting ticket information providing unit 45 described below.

The acquisition unit 3 acquires second voting ticket information on which the user has voted based on all or part of the first voting ticket information. An example of the acquisition unit 3 is the user voting ticket information acquisition unit 46 described below.

The accumulation unit 4 accumulates a portion of the voting value of the second voting ticket information as an accumulated value. An example of the accumulated value is the carryover amount described below. An example of the accumulation unit 4 is the bonus management unit 48 described below.

When the first voting ticket information includes a correct prediction result, the payout processing unit 5 pays out a portion of the accumulated value as a payout value to a user who voted for the second voting ticket information based on the first voting ticket information. An example of the payout value is the normal Venus or special bonus described below. An example of the payout processing unit 5 is the bonus management unit 48 described below.

By configuring it in this way, a portion of the total sales of voting tickets purchased based on the distributor's predictions can be pooled, and if the distributor is correct, a portion of the pooled amount can be paid out to users who purchased voting tickets based on the distributor's predictions. This makes it possible to prevent situations where a distributor who distributes prediction information for a competition does not predict the same thing in subsequent competitions.

The accumulation unit 4 may accumulate the accumulated value in association with the provider when the first voting ticket information does not include a correct prediction result. By configuring in this manner, it is possible to accumulate the accumulated value in association with a distributor whose prediction was not correct so that a larger accumulated value can be paid out in the next race to users who voted for the second voting ticket information based on the first voting ticket information.

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

The payout processing unit 5 determines the payout value according to the correct second voting ticket information. By configuring in this way, 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 is correct, the bonus paid to the user who purchased the voting ticket can be increased in order to support the broadcaster.

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

The payout processing unit 5 may further pay out a portion of the payout value to the provider. This configuration can increase the distributor's motivation to make predictions.

Figure 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 so as to be able to communicate with each other via the communication network 17.

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, and the like. The operation display unit 13 is a device that allows input operations to be made to the 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.

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 racing, boat racing, and bicycle racing, and that allows users to view distributors' predicted finishing orders, is installed on the user terminal 12.

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

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 prediction of the finishing order of the race, as well as betting ticket information, etc. The user refers to the video content, etc. displayed on the GUI image, predicts the finishing order of the race, and purchases a betting ticket via the user terminal 12 by making the required input.

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

The distributor terminal 15 is a telegraph 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, 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.

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

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.

The server 16 can also perform payment 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 can be a server system made up of one or more physical information processing devices, or a virtual server system made up of one or more virtual server devices.

Figure 3 is a diagram showing an example of the functional blocks of the betting ticket purchase system 11 in this embodiment. The following describes the functions of the user terminal 12, the broadcaster terminal 15, and the server 16.

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 the communication network 17. Here, the communication unit 21 communicates with the server 16 via the communication network 17.

The operation display unit 13 is a touch panel display that allows input by a user's input operation and also allows display. Note that in this embodiment, a touch panel display is used as an example, but this is not limited thereto, and the input unit and the display unit may be independent of each other.

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 forecast adoption unit 24, and a purchase request unit 25 by executing the application program according to this embodiment.

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 memory unit 26. In addition, the display control unit 23 communicates with the server 16 to display on the screen 14 the video content distributed by the distributor and the betting ticket information specified by the distributor. Here, the betting ticket information specified by the distributor includes betting ticket information (unpurchased betting tickets) in which the distributor only predicts the order of arrival, and purchased betting tickets.

In addition, when the broadcaster 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 broadcaster information with the fever flag = 1.

When the prediction adoption unit 24 receives an instruction to adopt the voting ticket information specified by the broadcaster through an operation on the operation display unit 13, it holds the specified voting 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 voting ticket information specified by the broadcaster in the predetermined temporary holding area 28 through an operation on the operation display unit 13. Furthermore, the prediction adoption unit 24 may add new voting ticket information based on the user's own prediction to the information on the voting ticket held in the temporary holding area 28 through an operation on the operation display unit 13.

The purchase request unit 25 transmits a purchase request to the server 16 to purchase the betting ticket information stored in the temporary holding area 28 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.

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, etc. Here, the data includes not only status information and character data, but also graphical data.

The memory unit 26 also has a temporary holding area 28 that temporarily holds the betting ticket information specified by the user. The temporary holding area 28 can also temporarily hold some or all of the betting ticket information to be adopted when the betting ticket information specified by the broadcaster is adopted. The temporary holding area 28 holds, for example, information identifying the race (such as the race name or race ID), finishing order information, bet amount, 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).

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.

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.

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 voting 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).

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.

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 requests from the user terminal 12 or the broadcaster terminal 15, and performs control such as returning the execution results 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 broadcast control unit 43, a broadcaster voting ticket information acquisition unit 44, a broadcaster voting ticket information provision unit 45, a user voting ticket information acquisition unit 46, a payment processing unit 47, and a bonus management unit 48.

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 a user terminal 12 on which a dedicated application program is running. At the same time, the distribution control unit 43 distributes the accepted video content to a user terminal 12 on which a dedicated application program is running.

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

The broadcaster voting ticket information providing unit 45 associates the broadcaster voting ticket information acquired by the broadcaster voting ticket information acquiring unit 44 with the video content of the corresponding broadcaster and provides it to the user terminal 12.

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

The payment processing unit 47 performs payment processing to purchase 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.

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 adds 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.

After the race ends and the finishing order is determined, if the prediction of the distributor to whom the fever flag was assigned turns out to be correct, the bonus management unit 48 performs processing to pay a special bonus to users who purchased voting tickets based on the prediction of that distributor.

Here, the source of the bonus may be, for example, a portion of the total amount of sales of betting tickets for the entire race. Also, the source of the bonus may be, for example, a portion 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 portion 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 portion of the total amount of sales of betting tickets for the current race and the total amount of bonuses paid to all users who won to a portion of the total amount of sales of betting tickets for the next race. Note that the bonus management unit 48 may further pay out a portion of the bonus to the broadcaster.

The memory unit 50 stores a broadcaster management database 51, a broadcaster betting ticket information database 52, a user-owned 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."

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 about the odds for each betting ticket in a competition. The carryover money management DB56 is a database that is used to add the difference between the 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 subsequent competitions.

Figure 4 shows an example of the data structure of a database managed by server 16 in this embodiment.

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 order of finish in the race. If the distributor has predicted the order of finish in the race, a success flag = 1 is stored. If the distributor has not predicted the order of finish 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, then the "Fever Flag" field of the current record (distributor information) will store Fever Flag = 1. If the hit flag of the previous record (distributor information) is 1, then the "Fever Flag" field of the current record (distributor information) will store Fever Flag = 0.

The broadcaster betting ticket information DB52 includes the data items of "broadcaster ID", "race ID", "betting ticket", "purchase amount", and "video content ID". The item "broadcaster ID" stores information that identifies the broadcaster (broadcaster ID). The item "race ID" stores information that identifies the race (race ID). The item "betting ticket" stores the group numbers of the finishing order from 1st place to a specified 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 corresponding to the betting ticket information. The item "video content ID" stores information that identifies the video content of the corresponding broadcaster (video content ID).

The user holdings information DB53 includes the data items "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 that the user can currently use in the betting ticket purchasing system 11. The item "Held points" stores the points that the user can currently use in the betting ticket purchasing system 11.

The user betting ticket information DB54 includes the data items of "User ID", "Race ID", "Bet", "Purchase Amount", "Purchase Points", and "Broadcaster ID". The "User ID" item stores information that identifies the user (user ID). The "Race ID" item stores information that identifies the race (race ID). The "Bet" item stores the group number of the finishing order from 1st place to a specified position in the race (race) specified by the race ID. The "Purchase Amount" item stores the stake corresponding to the betting ticket information (this item is used when there is a fee, and the stake is in currency). The "Purchase Points" item stores the stake corresponding to the betting ticket information (this item is used when there is no fee, and the stake is in points). The "Broadcaster ID" item stores the broadcaster ID of a broadcaster when a user purchases a betting ticket using a betting ticket specified by the broadcaster.

The odds information DB55 includes the data items "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.

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

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 the target race, the screen in Figure 5 is displayed.

Figure 5 shows an example of a broadcaster selection screen in this embodiment (non-fever mode). The broadcaster selection screen 61 includes a logged-in 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.

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 held amount display field 63 displays the amount of money currently held by the user in the betting ticket purchasing system 11. The held points display field 64 displays the points currently held 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. Note that the purchase target race name display field 65 displays a message informing the user of the time remaining until the deadline for purchasing betting tickets for that race.

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

Figure 6 is a diagram showing an example of a broadcaster selection screen (during fever) in this embodiment. In the broadcaster selection screen 61 in Figure 6, a specific broadcaster or any broadcaster in the broadcaster list 66 is in fever state. A fever state is a state in which, if a specific broadcaster or any broadcaster did not predict correctly in the previous race, a special bonus will be awarded if a betting ticket is purchased based on the broadcaster's prediction for the current race. 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 Figure 7 is displayed.

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

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 of 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 the fact that the distributor is in a fever state. The fever content field 76 displays the fact that the user is currently in a fever state, the amount of the carryover money, and that if a user purchases a betting ticket based on the broadcaster's prediction this time, the carryover money will be split between 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 in FIG. 8 is displayed, and the user can check the detailed content of the betting ticket specified by the distributor.

Figure 8 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 addition specification field 86, a distributor predicted voting ticket display field 87, a fever display field 89, and a purchase execution button 96.

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 specification 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 specification 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.

The broadcaster predicted betting ticket display field 87 includes a predicted betting ticket list 87a, a stake/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 stake or betting points specified by broadcaster A by default.

The predicted 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 predicted betting ticket list 87a displays four group numbers: the group number for "1st place No. 1, 2nd place No. 4", the group number for "1st place No. 3, 2nd place No. 8", the group number for "1st place No. 5, 2nd place No. 2", and the group number for "1st place No. 8, 2nd place No. 5, 3rd place No. 2".

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

The set purchase button 92 is a button for purchasing voting tickets in sets, where a combination of voting tickets in the predicted voting ticket list 87a is considered to be one set. Each time the "+" button on the set purchase button 92 is pressed, the number of sets to be purchased is increased. Each time the "-" button on the set purchase button 92 is pressed, the number of sets to be purchased is decreased.

By pressing the edit button 93, the contents of the predicted voting ticket list 87a can be edited. For example, the purchase unit can be changed from points (free) to yen (paid), or from yen (paid) to points (free), the user's own predictions can be added to the predicted voting ticket list 87a, or a specific group number can be deleted from the predicted voting ticket list 87a. By pressing the delete button 94, the distributor predicted voting ticket display column 87 can be deleted.

The fever display field 89 displays the fact that the player is currently in a fever state and the amount of the carryover funds. 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.

Figure 9 is a sequence diagram showing the process between the user terminal and the server 16 in this embodiment until broadcaster voting ticket information is displayed. The user operates the user terminal 12 to start up the 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).

The server 16 (bonus management unit 48) identifies a broadcaster who is making a prediction about an upcoming race from the broadcaster management DB 51, and references the hit flag of the broadcaster information about the race immediately preceding the identified broadcaster information. If the hit flag is 0 (not a hit), the server 16 (bonus management unit 48) updates the fever flag of the current broadcaster information of the identified broadcaster to 1 (S3).

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

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 of 1.

The user selects, for example, a thumbnail image 66a of distributor information for distributor A from the distributor list 66 (S7). The user terminal 12 then 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. 7.

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).

The user terminal 12 displays the set number of the voting ticket included in the broadcaster voting information for broadcaster A transmitted from the server 16 in the broadcaster voting ticket information display field 77 on the broadcaster prediction screen 71 of FIG. 7 (S12).

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

The user taps the details display button 78 on the broadcaster prediction screen 71 in FIG. 7. The user terminal 12 (prediction adoption unit 24) then stores the broadcaster voting ticket information in the temporary holding area 28 (S21). At this time, the voting ticket purchase screen 81 in FIG. 8 is displayed.

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 adoption unit 24) updates the information held in the temporary holding area 28. That is, the user terminal 12 (the prediction adoption 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).

When the user has confirmed the betting ticket to be purchased on the betting ticket purchase screen 81, the user taps the purchase execution button 96 (S23). The user terminal 12 (purchase request unit 25) then sends a purchase request including the user betting ticket information (including the user ID, race ID, betting ticket set number, purchase amount (or purchase Pt), and broadcaster ID) based on the contents of the temporary holding area 28 to the server 16 (S24).

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

After the betting period for the race has closed, the server 16 registers the confirmed odds information in the odds information DB 55. In addition, after the race, when the finishing order is confirmed, the server 16 (bonus management unit 48) performs a bonus determination process (S27).

Figure 11 is a sequence diagram (Example 2) of the process from the user terminal 12 to the server 16 in this embodiment until a voting ticket is purchased based on broadcaster voting ticket information. Figure 11 is a sequence diagram of the case where broadcaster voting ticket information of other broadcasters is displayed before a purchase is made after broadcaster A's broadcaster voting ticket information is stored in the temporary holding area 28.

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 voting ticket information of broadcaster A in the temporary holding area 28 (S31). At this time, the voting 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 voting 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 voting ticket purchase screen 81 in FIG. 8 for broadcaster A, the broadcaster voting ticket information of broadcaster A will be displayed.

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 (S32). The user terminal 12 then 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. 7.

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 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).

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 display details 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.

On the voting 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 specifies the amount of 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 held in the temporary holding area 28. That is, the user terminal 12 (prediction adoption unit 24) updates the contents of the temporary holding area 28 in response to the input operation on the voting ticket purchase screen 81 (holding all or part of the broadcaster voting ticket information in the temporary holding area 28).

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 Pt), and broadcaster ID) based on the contents of the temporary holding area 28 to the server 16 (S40).

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 allow only the betting tickets purchased on the screen where 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 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 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 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.

The server 16 (user betting ticket information acquisition unit 46) acquires the purchase request.
The (user voting ticket information acquisition unit 46) registers the contents of the user voting ticket information included in the acquired purchase request in the user voting ticket information DB 54. The server 16 (payment processing unit 47) performs payment processing for the purchase of the voting 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).

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

Figure 12 is a diagram illustrating the bonus determination process (Example 1) in this embodiment. In the bonus determination process described in Figure 12, if none of the broadcasters are in a fever state, a normal bonus is paid out to each user who purchases a voting ticket based on the broadcaster's prediction for that race and wins. If a specific broadcaster is in a fever state and their prediction wins, a special bonus is paid out to each user who purchases a voting ticket based on the broadcaster's prediction and wins.

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

For example, if a particular broadcaster's prediction for a given race turns out to be incorrect, a fever state is triggered to support the broadcaster. In other words, during the fever state, if a user purchases a betting ticket based on the broadcaster's prediction for the next race and the ticket turns out to be correct, the bonus for that user is increased. The amount of increase in the special bonus when a fever occurs is determined by the number of betting tickets (total purchase amount by users) purchased based on the broadcaster's prediction for the race that turned out to be incorrect. Note that the amount of increase in the special bonus may also be determined by the popularity of the broadcaster for the race that turned out to be incorrect.

In the example of Figure 12, X (X: any integer)% of the total sales of voting tickets purchased based on a broadcaster's predictions may be returned to users as exchange points, and any points not paid out are pooled. If a specific broadcaster goes into a fever state in the race following a race in which there are no correct answers, the pooled points up to that point will be split among users who purchased voting tickets based on the broadcaster's predictions for that race and got a correct answer. In the example of Figure 12, the specific broadcasters are Broadcaster A and Broadcaster B.

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 the broadcaster's 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 based on the broadcaster's voting ticket information for each broadcaster is as shown in the table.

Let's say that ticket B wins in the first race. In this case, the total amount of exchange points paid out by each distributor who predicted that ticket B would win will be (50 + 50 + 200 + 50) x odds 4.5 (multiplier) x 100 yen x maximum user return rate 0.02 = 3,150 yen (total amount of exchange points paid out).

Here, the total exchange point refund amount of 3,150 yen does not exceed the exchange point upper limit of 5,100 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 issued per user, the exchange points (regular bonus) will be determined as 3,150 yen/(50 people + 50 people + 200 people + 50 people) = 9 yen/person. The amount of 1,950 yen obtained by subtracting the total exchange point refund amount of 3,150 yen from the exchange point upper limit of 5,100 yen will be carried over as a carryover amount to the exchange point upper limit for the next race.

In FIG. 12(B), the total number of tickets sold by each broadcaster in the second race (= total sales amount of tickets purchased by users based on broadcaster predictions / 100 yen) is 3,680. Also, since the exchange point return rate is 1%, the upper limit of exchange points is 3,680 tickets x 100 yen x 0.01 = 3,680 yen. At this time, the carryover amount of 1,950 yen from the previous race is added, and the upper limit of exchange points is 5,630 yen.

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

Here, the total exchange point refund amount of 600 yen does not exceed the exchange point upper limit of 5,630 yen, so 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 for the next race.

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

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. At this time, the carryover amount of 5030 yen from the previous race is added, and the upper limit of exchange points becomes 7620 yen.

Let's say that ticket A wins in the third race. 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 (multiple) x 100 yen x maximum user return rate 0.02 + 5,030 carried over from the previous race = 6,430 yen (total exchange points paid out).

Here, the total exchange point refund amount of 6,430 yen does not exceed the upper limit of exchange points of 7,620 yen. In this case, the exchange points (regular bonus) refunded to users who purchased voting tickets based on broadcaster C's predictions will be (150 voting tickets purchased based on broadcaster C's predictions) x odds 3.5 (multiplier) x 100 yen x maximum user return rate 0.02 = 1,050 yen. For example, if each user receives one voting ticket, the exchange points (regular bonus) will be 1,050 yen/150 people = 7 yen/person.

The exchange points (regular bonus) that will be returned to users who purchased voting tickets based on the predictions of distributor D will be calculated as follows: (50 voting tickets purchased based on the predictions of distributor D) x odds 3.5
(Multiplication factor) 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 (normal bonus) will be 350 yen/50 users = 7 yen/user.

On the other hand, the exchange points (special bonus) refunded to users who purchased voting tickets based on the predictions of broadcasters A and B, who are in a fever state, will be the amount of 5,030 yen carried over from the previous time, divided equally among the number of users. For example, if each user receives one voting ticket, the exchange points (special bonus) will be 5,030 yen/(200 people + 100 people) = 16 yen/person.

Figure 13 is a diagram explaining the bonus determination process (Example 2) in this embodiment. Figures 13(A) and 13(B) are the same tables as Figures 12(A) and 12(B). Figure 13(C) differs from Figure 12(C) in the amount of exchange Pt payout.

In FIG. 12(C), when a specific broadcaster predicts something to happen during a fever, the exchange points (special bonus) that are returned to users who purchased voting tickets based on the specific broadcaster's prediction are split equally between those users as carryover points from the previous time.

In contrast, in FIG. 13(C), the exchange points (special bonus) paid out to users who purchased voting tickets based on the predictions of a particular broadcaster are split equally between the users after subtracting the exchange points (regular bonus) paid out to users who purchased voting tickets based on the predictions of broadcasters who are not in a fever state from the upper limit of exchange points for the current race (including carryover points from the previous race).

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.

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, who are in a fever state, is 6,220 yen, calculated by subtracting the exchange points (regular bonus) of 1,400 yen paid out to users who purchased voting tickets based on the predictions of broadcasters C and D from the exchange points of 7,620 yen. For example, if each user receives one voting ticket, the exchange points (special bonus) will be 6,220 yen/(200 people + 100 people) = 20 yen/person.

This means that if a streamer does not predict the winner, the management side can support the streamer by paying more money or points than usual to users who purchased voting tickets based on the streamer's prediction when the streamer predicts the winner.

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 the 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 the 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) 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 the current race (carrying over the carryover amount from the previous race),
It may 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)).

Figure 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 a race has been determined (S51), it groups the user betting ticket information DB 54 by race ID, broadcaster 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).

The bonus management unit 48 obtains the carryover funds from the previous race from the carryover funds 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 betting tickets purchased by users, with reference to the broadcaster's predictions for that race. At this time, if there are carryover funds 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).

The bonus management unit 48 acquires the fever flags of the broadcasters who are predicting the current race from the broadcaster 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 broadcasters who do not have a fever flag using the following formula (S56).
Exchange points (regular bonus) returned 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

The bonus management unit 48 calculates exchange points (special bonus) for users who 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)

As explained in FIG. 13(C), the exchange points (special bonus) may be calculated by subtracting the exchange points (regular bonus) paid 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.

The bonus management unit 48 determines whether the total exchange Pt is equal to or less than the upper limit of exchange Pt (S58). If the total exchange Pt exceeds the upper limit of exchange Pt (NO in S58), the bonus management unit 48 adjusts the bonus paid out to the user so that it is within the upper limit of exchange Pt. 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 upper limit of exchange Pt. For example, the user maximum return rate can be adjusted in the range of 0.01% to 2%.

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 (or held points) of the user to whom the bonus is paid out in the user holding information DB 53.

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.

The bonus management unit 48 updates the hit flags and fever flags of the broadcasters in the broadcaster management DB 62 based on the winning results of the current race (S62). For example, the bonus management unit 48 sets the hit flags of broadcasters whose predictions in the current race were correct to 1. The bonus management unit 48 sets the hit flags of broadcasters whose predictions in the current race were not correct to 0. Furthermore, if a broadcaster who was in a fever state predicts a winning result in the current race, the bonus management unit 48 sets the fever flag of that broadcaster to 0.

In this way, a few percent of the total sales of voting tickets purchased based on the streamer's predictions can be returned to users as exchange points, and any points not paid out can 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 streamers who did not get their predictions right in the previous race, but who get their predictions right.

Figure 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.

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.

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 voting ticket information acquisition unit 44, a distributor voting ticket information provision unit 45, a user voting ticket information acquisition unit 46, a payment processing unit 47, and a bonus management unit 48. The ROM 103 indicates a read-only memory. The RAM 104 is a temporary storage memory.

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 data stored in the storage unit 40.

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

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, or other communication network. The reading device 109 is a device for reading portable recording media.

The program that realizes the processing 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 that realizes the processing described in the above embodiment may also be stored in a portable storage medium that is commercially available and in circulation. 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.

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 this 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 this embodiment, but this is not limited to this. 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 this embodiment operated on the server 16 side.

According to this embodiment, for a distributor whose predictions in the previous race were not successful, a user is put in a feverish state for the next race as a sign of support, and a betting ticket is purchased based on the predictions of such a distributor, 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 distributes prediction information for a race does not predict the same race in subsequent races.

In this embodiment, if a specific broadcaster's prediction in a specific race is not correct, a fever state is entered in the next race, but this is not limited to this and may be applied to all broadcasters. In other words, if any broadcaster's prediction in a specific race is not correct, a fever state may be entered in the next race.

In addition, the bonus amount may be increased and paid not only to users who purchase tickets based on the predictions of a broadcaster in a fever state and get them right, but also to that broadcaster. The process of paying out bonuses is the same whether the bonus is paid for (e.g., yen) or for free (e.g., points).

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

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 voting 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 information processing device according to claim 1, wherein the accumulation unit accumulates the accumulated value in association with the provider when the first betting ticket information does not include a correct prediction result.
By configuring in this way, in the case of a distributor whose prediction did not come true, 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 information processing device according to claim 1 or 2, wherein the payout processing unit determines the payout value according to a voting value of the second betting ticket information.
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 information processing device according to any one of appendices 1 to 3, wherein the payout processing unit determines the payout value according to the winning second betting ticket information.
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 information processing device described in any one of appendices 1 to 4, characterized in that 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 after the first competition.
By configuring it in this manner, for example, in the case where 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, if 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 information processing device according to any one of appendices 1 to 5, wherein the payout processing unit further pays out a portion of the payout value to the provider.
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 for providing first voting 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 for providing first voting 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.

REFERENCE SIGNS LIST 1 Information processing device 2 Provision unit 3 Acquisition unit 4 Determination unit 5 Terminal device 11 Betting ticket purchase system 12 User terminal 15 Broadcaster terminal 16 Server 17 Communication network 41 Communication unit 42 Control unit 43 Distribution control unit 44 Broadcaster betting ticket information acquisition unit 45 Broadcaster betting ticket information provision unit 46 User betting ticket information acquisition unit 47 Settlement processing unit 48 Bonus management unit 50 Storage unit 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 fund management DB

Claims (4)

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. 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. Displaying first betting ticket information designated by the prediction provider for the first race on a screen of a terminal device of a user ;
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. 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