Information processing apparatus, program, information processing method, and information processing system

Abstract

To alleviate user anxiety caused by a bet losing due to an accident affecting the designated betting target according to a selected betting format, and to reduce the resulting decline in user motivation to place bets.SOLUTION: An information processing apparatus comprises: a reception part that receives, from a user, designated competitive body information identifying a competitive body specified according to a betting format for wagering on a predetermined competitive body in which a plurality of competitive bodies vie for finishing positions, together with voting information specifying a wager amount; and a compensation control part that, when the competition is held and the wager fails to win due to occurrence of a predetermined event affecting the competitive body corresponding to the designated competitive body information, executes a compensation process that refunds to the user at least a portion of the wager amount as compensation.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

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

[0003] Patent Document 1 discloses an information providing device that provides information to race fans, which uses an acquisition means to acquire race result information for a predetermined race in which a predetermined athlete has competed that can identify a person not subject to disqualification review, uses an identification means to determine whether or not the predetermined athlete is a person not subject to disqualification review based on the race result information, that is, whether or not the predetermined athlete is a participant who was subject to review but was not disqualified, identifies the number of times the predetermined athlete was not subject to disqualification review in the predetermined race based on the determination result, and outputs the number of times the predetermined athlete was not subject to disqualification review using an output means. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2018-116331 Summary of the Invention [Problem to be solved by the invention]

[0005] Until now, betting on a rider who falls off their bike in races such as Keirin has been treated as a losing ticket. As a result, some users refrained from betting on their favorite due to concerns that they might fall off their bike.

[0006] In Patent Document 1, by providing fans with the number of times that a player was judged to be disqualified but was not disqualified, it makes it easier for fans to understand whether a player is disruptive or not, but it does not alleviate the anxiety of users if the betting ticket they purchased does not win due to an accident involving the player they bet on.

[0007] To provide a technology for mitigating a user's anxiety caused by a missed vote due to an accident on a betting target designated according to a betting type, thereby reducing a decrease in the user's motivation to vote. [Means for solving the problem]

[0008] An information processing device according to one aspect of the present invention comprises a reception unit that receives from a user designated athlete information that identifies the designated athlete according to a betting method for a predetermined competition in which multiple athlete bodies compete for finishing order, and betting information that specifies a betting amount, and a compensation control unit that executes a compensation process to refund at least a portion of the betting amount to the user as compensation if the competition is successful but the betting is not successful due to a predetermined event occurring to the athlete corresponding to the designated athlete information. [Effects of the Invention]

[0009] According to one aspect of the present invention, it is possible to alleviate the anxiety of a user who loses a bet due to an accident involving the betting target specified according to the betting type, thereby reducing a decrease in the user's motivation to vote. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of an information processing apparatus according to an embodiment of the present invention. [Figure 2] 1 is a diagram showing an example of a network configuration of a betting ticket purchasing system according to an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram showing an example of functional blocks of a betting ticket purchasing system 11 in this embodiment. [Figure 4]FIG. 2 is a diagram illustrating an example of a data structure of a database managed by a management server in this embodiment. [Figure 5] FIG. 10 is a diagram showing an example of a betting ticket purchase screen in this embodiment. [Figure 6] FIG. 2 is an overall sequence diagram between a user terminal 12 and a management server 15 in this embodiment. [Figure 7A] FIG. 10 is a flowchart (part 1) illustrating an example of a compensation process according to the present embodiment. [Figure 7B] FIG. 10 is a flowchart (part 2) illustrating an example of the compensation process according to the present embodiment. [Figure 8] FIG. 10 is a flowchart illustrating an example of a compensation process according to the present embodiment (Example 1). [Figure 9] FIG. 10 is a flowchart illustrating an example of a compensation process according to the present embodiment (Example 2). [Figure 10] FIG. 10 is a flowchart illustrating an example of a compensation mode switching process according to the present embodiment (Example 3). [Figure 11] FIG. 10 is a flowchart illustrating an example of a compensation mode switching process according to the present embodiment (Example 4). [Figure 12] FIG. 13 is a flowchart illustrating an example of a compensation process according to the present embodiment (Example 5). [Figure 13] FIG. 13 is a diagram showing an example of a compensation grant confirmation message screen in this embodiment (Example 6). [Figure 14] 10 is a flowchart illustrating an example of a display process of a compensation grant confirmation message screen according to the present embodiment. [Figure 15] FIG. 13 is a diagram showing an example of a compensation setting screen in the present embodiment (Example 7). [Figure 16] FIG. 10 is a diagram illustrating a period in this embodiment (Example 7). [Figure 17] FIG. 13 is a flowchart illustrating an example of a compensation process according to the present embodiment (Example 8). [Figure 18] FIG. 2 is a block diagram illustrating an example of the configuration of a hardware environment of a computer that executes a program according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] 1 is a diagram showing an example of an information processing device in this embodiment. The information processing device 1 includes a reception unit 2 and a compensation control unit 3. An example of the information processing device 1 is a management server 15, which will be described later.

[0012] The reception unit 2 receives from the user designated racing object information that identifies the designated racing object (for example, a number that identifies the betting object, such as a car number or a horse number) according to a betting method in a predetermined racing event in which multiple racing objects compete for finishing order, and betting information that specifies the betting amount. An example of the reception unit 2 is the acquisition unit 43, which will be described later. The racing events include, for example, publicly managed racing events such as horse racing, bicycle racing, boat racing, and auto racing.

[0013] When a bet is not successful due to a predetermined event (e.g., a fall, a breakdown, or other betting accident) occurring in the racer corresponding to the designated racer information, the compensation control unit 3 executes compensation processing to refund at least a portion of the bet amount to the user as compensation. An example of the compensation control unit 3 is the compensation processing unit 47, which will be described later. While this embodiment focuses on a race being successful, a race being successful does not necessarily mean a race being unsuccessful. Examples of race unsuccessful (betting types not successful) include cancellation due to bad weather (all betting types not successful), disqualification of all bettors (all betting types not successful), consecutive numbers with only one car reaching the finish line (sequential numbers, trifecta not successful), and trifecta with only one or two cars reaching the finish line (trifecta not successful). When a race is unsuccessful (betting types not successful), all bets are returned to all bettors. Accidents may include not only falls, breakdowns, etc., but also disqualifications.

[0014] By configuring in this way, it is possible to alleviate the anxiety of the user when the bet is lost due to an accident with the betting target specified according to the betting type, and to reduce the decrease in the user's motivation to vote.

[0015] If the first user's bet is not correct because a specified event has occurred for the sporting body corresponding to the designated sporting body information a specified number of times or more, the compensation control unit 3 notifies the first user that compensation will be provided if the bet is not correct because a specified event has occurred.

[0016] By configuring in this way, it is possible to prevent users who have previously lost their bets due to an accident involving a designated player from refraining from purchasing betting tickets.

[0017] If the first user has not voted for a predetermined period of time, the compensation control unit 3 notifies the first user that compensation will be provided if the first user's vote is not successful due to the occurrence of a predetermined event.

[0018] This can prevent users who previously lost a bet due to an accident involving a designated player from refraining from purchasing betting tickets.

[0019] If the second user has designated a voting amount equal to or greater than a predetermined amount, the compensation control unit 3 executes a compensation process for the second user.

[0020] By configuring in this way, accident compensation can be provided when purchasing voting tickets worth a certain amount or more, allowing users to vote with peace of mind.

[0021] If the second user has designated a cumulative voting amount equal to or greater than a predetermined amount within a predetermined period, the compensation control unit 3 executes compensation processing for the second user.

[0022] By configuring in this way, accident compensation is provided to people who have bet a large amount on many races, and it is possible to encourage people to purchase betting tickets without fearing that their bets will be incorrect due to an accident.

[0023] The compensation control unit 3 executes a compensation process for the second user when the second user has designated a betting amount equal to or greater than a predetermined amount for the first competition.

[0024] By configuring in this way, accident compensation is provided to people who have bet a large amount on many races, and it is possible to encourage people to purchase betting tickets without fearing that their bets will be incorrect due to an accident.

[0025] The compensation control unit 3 executes a compensation process for the second user when the second user designates a betting amount equal to or greater than a predetermined amount for designated game item information corresponding to the betting type in the first game.

[0026] By configuring it in this way, even if users purchase many types of tickets for one race (single number for the most popular, single number for the second most popular, consecutive numbers, trifecta), it is possible to encourage users who are afraid of losing their horse and have small amounts on each ticket to bet a larger amount.

[0027] If the holding status of the second competition in which a specified event occurs during the second period satisfies specified conditions, the compensation control unit 3 executes compensation processing for the third competition held during a third period after the second period.

[0028] By configuring in this way, it is possible to reduce the tendency to refrain from purchasing votes for a race in which an accident has occurred due to the influence of weather or the like.

[0029] The compensation control unit 3 executes compensation processing for a competition in which a specified event is likely to occur, determined based on weather history information of the venue on the date of a past competition that has been registered in advance, the number of occurrences of a specified event, and weather forecast information of the venue on the day of the competition.

[0030] By configuring in this way, it is possible to reduce the tendency to refrain from purchasing votes for competitions held in weather conditions where accidents are more likely to occur.

[0031] The compensation control unit determines the conditions for executing the compensation process or the amount of compensation based on the user's past voting information history.

[0032] By configuring it in this way, the conditions and / or content of accident compensation can be adjusted according to the user's voting history, thereby reducing users' anxiety about voting and further encouraging them to purchase voting tickets.

[0033] The history of past voting information is the first number of times that a bet was not correct due to a predetermined event occurring in the sports body corresponding to the designated sports body information. The compensation control unit 3 reduces the conditions or increases the amount of compensation for a user whose first number of times is more than the predetermined number, compared to a user whose first number of times is less than the predetermined number.

[0034] By configuring it in this way, users who have lost votes more than a predetermined number of times due to falling off their bike in the past can be more generously compensated, thereby reducing the number of users who contribute more to the sales of the service who drop out of the service.

[0035] The compensation control unit determines the conditions for executing the compensation process or the content of the compensation process based on the number of times or amount of votes received from the user in the voting information.

[0036] By configuring in this way, users who are contributing more to the sales of the service and new users can be given preferential treatment, and it is possible to encourage them to purchase voting tickets with more confidence.

[0037] The receiving unit 2 receives from the user voting information and compensation presence / absence information indicating whether or not compensation is to be provided. If the received compensation presence / absence information indicates that compensation is to be provided, the compensation control unit 3 executes compensation processing for the user.

[0038] By configuring it in this way, the user can select whether or not to purchase accident compensation, thereby reducing the psychological burden when purchasing a betting ticket, such as worrying about what to do if the betting ticket is lost due to an accident such as falling off one's bike.

[0039] The compensation control unit 3 inquires of the user whether or not to provide compensation based on the history information relating to the predetermined cause of each of the competition objects.

[0040] By configuring it in this way, for example, beginner users who do not know which riders are likely to fall off their bikes can purchase their votes with confidence.

[0041] The receiving unit 2 receives compensation presence / absence information indicating whether or not compensation will be provided at a predetermined amount for a first unit period from a user. If the received compensation presence / absence information indicates that compensation will be provided, the compensation control unit 3 executes compensation processing for the user.

[0042] By configuring it in this way, for example, beginner users who do not know which riders are likely to fall off their bikes can purchase their votes with confidence.

[0043] The compensation control unit 3 executes the first-count compensation process in the first unit period. If the first-count compensation process is executed before the end of the first unit period, the receiving unit 2 receives second compensation presence / absence information indicating whether or not compensation should be provided up to the second count in the second unit period before the end of the first unit period.

[0044] By configuring in this way, a flat rate system can be introduced, and the convenience of accident compensation for users can be improved.

[0045] If the received compensation availability information indicates that compensation for the second unit period will not be provided, the compensation control unit 3 determines the competition that will be the subject of compensation for the first unit period after the first unit period has expired. By configuring it in this way, the convenience of the flat-rate system can be further improved.

[0046] The compensation control unit 3 executes compensation processing for the user if the voting information does not include a correct vote and the vote is not correct because a predetermined event has occurred for the sports body corresponding to the designated sports body information, and does not execute compensation processing for the user if the voting information includes a correct vote and the vote is not correct because a predetermined event has occurred for the sports body corresponding to the designated sports body information.

[0047] According to the information processing device described above, from the viewpoint of user friendliness, it is possible to flexibly operate a flat-rate system for accident compensation for users.

[0048] 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, a management server 15, an external server 16, and a communication network 17. The one or more user terminals 12, the management server 15, and the external server 16 are connected to each other via the communication network 17 so that they can communicate with each other.

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

[0050] The user terminal 12 can download and install a predetermined application program from an application program download site on the Internet. This allows the user to operate the application program by performing input operations on the operation display unit 13 of the user terminal 12. In this embodiment, as an example, it is assumed that dedicated application software (hereinafter referred to as "dedicated application software") that enables the purchase of betting tickets for publicly managed races such as horse racing, boat racing, and bicycle racing (hereinafter sometimes referred to as "races") is installed on the user terminal 12.

[0051] By starting up this dedicated application software on the user terminal 12, the user can make the user terminal 12 access the management server 15. When the user terminal 12 accesses the management server 15, for example, the user may be asked to input a pre-registered user ID.

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

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

[0054] The management server 15 is an information processing device that manages dedicated application programs installed on the user terminal 12. For example, the management server 15 can perform settlement processing for purchasing betting tickets based on betting ticket purchase instructions from the user terminal 12. After the finishing order of a race is determined, the management server 15 performs a payout process to pay out dividends (refunds) to users whose purchased betting tickets are winning, based on the winning bets, bet amounts, and odds. Furthermore, after the finishing order of a race is determined, the management server 15 performs a process to refund at least a portion of the purchase amount as compensation to users whose car numbers specified on their purchased betting tickets are not winning due to an accident such as a fall.

[0055] The management server 15 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.

[0056] The external server 16 is an information processing device that operates and manages services provided by other companies. Examples of such services include a service that provides weather information (including weather forecast information) for a certain region or the entire country.

[0057] 3 is a diagram showing an example of functional blocks of the betting ticket purchasing system 11 in this embodiment. The following describes the functions of the user terminal 12 and the management server 15.

[0058] 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 management server 15 via the communication network 17.

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

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

[0061] 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. The display control unit 23 holds the designated betting ticket information in a predetermined temporary holding area 28 in response to an operation from the operation display unit 13.

[0062] In response to an instruction from the operation display unit 13, the purchase request unit 24 transmits a purchase request to purchase the betting ticket information held in the temporary holding area 28 to the management server 15. The purchase request unit 24 receives a purchase completion notification from the management server 15, which has performed the settlement process for the purchase request.

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

[0064] The storage unit 26 also has a temporary storage area 28 that temporarily stores betting ticket information designated by the user. The temporary storage area 28 stores, for example, information that identifies the race (such as the race name or race ID), finishing order information, and bet amount.

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

[0066] The control unit 42 controls the overall operation of the management server 15. At the same time, the control unit 42 performs control such as executing processing in response to a request from the user terminal 12 and returning the execution result to the user terminal 12. The control unit 42 functions as an acquisition unit 43, a settlement processing unit 44, a dividend processing unit 45, a registration unit 46, and a compensation processing unit 47 by executing an application program according to this embodiment.

[0067] The acquisition unit 43 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. The acquisition unit 43 also acquires the confirmed race finishing order results or accident information such as a runner falling off their bike, which have been input by the race management staff. The acquisition unit 43 also acquires service information (for example, weather information, weather forecast information) acquired from the external server 16.

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

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

[0070] The registration unit 46 registers the various types of information acquired (including, for example, betting information, accident information, and weather information) in the corresponding database. Note that hereinafter, databases are referred to as "DBs." For example, when a race result is determined, the registration unit 46 registers race result information in the race result management DB 56. Also, when the race result is determined and dividend processing is completed, the registration unit 46 acquires betting information for the determined race from the betting management DB 53 and registers it in the betting history DB 54. Also, when an accident occurs in a race whose result has been determined, the registration unit 46 registers the accident information in the accident management DB 57.

[0071] If the race is successful and the bet is not correct due to a predetermined event (for example, a bet subject accident such as a fall or breakdown) occurring to the athlete of the specified group number, the compensation processing unit 47 executes a compensation process to refund at least a portion of the bet amount to the user as compensation, for example.

[0072] The storage unit 51 stores a user management DB 52 , a vote management DB 53 , a vote history DB 54 , a race management DB 55 , a race result management DB 56 , an accident management DB 57 , a compensation management DB 58 , and a weather history DB 59 .

[0073] The user management DB 52 is a database that manages information about users. The voting management DB 53 is a database that manages information about betting tickets purchased by users. The voting history DB 54 is a database that manages the voting history of each user for confirmed races. The race management DB 55 is a database that manages the operation of races. The race result management DB 56 is a database that manages the finishing order of confirmed races and confirmed odds information. The accident management DB 57 is a database that manages information about accidents (such as falls) that occur during races. The compensation management DB 58 is a database that manages information about user compensation. The weather history DB 59 is a database that manages the history of weather information for each venue of the competition.

[0074] 4 is a diagram showing an example of the data structure of databases managed by the management server 15 in this embodiment. The data structures of the user management DB 52, voting management DB 53, voting history DB 54, race management DB 55, race result management DB 56, accident management DB 57, compensation management DB 58, and weather history DB 59 described below are merely examples and are not limited to these.

[0075] The user management DB 52 includes the data items "User ID", "User Name", "Email Address", "Amount Held", and "Pt Held". The item "User ID" stores information that identifies the user (user ID). The item "User Name" stores the name of the user. The item "Amount Held" stores the amount (currency amount) that the user can currently use in the betting ticket purchasing system 11. The item "Pt Held" stores the points that the user can currently use in the betting ticket purchasing system 11.

[0076] The betting management DB53 includes data items such as "user ID," "race ID," "date of event," "betting type," "group number," "purchase amount," and "purchase points." The "user ID" item stores information (user ID) that identifies a user. The "race ID" item stores information (race ID) that identifies a race. The "date of event" item stores the date of the race. The "betting type" item stores the type of betting type (trifecta (car number trifecta), trifecta (car number trifecta), exacta (car number duplicative), duplicative (car number duplicative), exacta (gate number duplicative), doublet (gate number duplicative), wide (extended duplicative)). The "group number" item stores the number of the first place winner predicted by the user or the group numbers of the finishers from first place to a predetermined position, depending on the betting type, in the race identified by the race ID. The item "Purchase Amount" stores the bet amount (used when a bet is paid, and the bet is currency) corresponding to the betting ticket information. The item "Purchase Points" stores the bet amount (used when a bet is free, and the bet is points) corresponding to the betting ticket information.

[0077] The betting history DB54 includes the data items "User ID," "Race ID," "Event Date," "Bet Type," "Group Number," "Purchase Amount," "Purchase Points," "Win / Loss," "Payout Amount," "Payout Points," "Compensation Amount," and "Compensation Points." The items "User ID" to "Purchase Points" are the same as the items in the betting management DB53, so their explanation will be omitted. The item "Hit / Loss" stores whether or not the betting ticket was a winning ticket. The item "Payout Amount" stores the payout amount paid when the betting ticket is a winning ticket and the betting ticket was purchased with currency (purchase amount). The item "Payout Points" stores the payout points paid when the betting ticket is a winning ticket and the betting ticket was purchased with points (purchase points). The item "Compensation Amount" stores the compensation amount paid when the betting ticket is a losing ticket and an accident occurs to the athlete with the specified group number and the betting ticket was purchased with currency (purchase amount). The item "Compensation Points" stores the compensation points paid when the betting ticket is unsuccessful and an accident occurs to the player in the specified group number, and the betting ticket was purchased with points (purchase points).

[0078] The race management DB 55 includes the data items "Race ID," "Event Date," and "Compensation Mode." The "Race ID" item stores information that identifies the race (race ID). The "Event Date" item stores the date on which the race is held. The "Compensation Mode" item stores a mode for adjusting whether compensation is available for the race (Compensation Mode = "Yes" or "No").

[0079] The race result management DB56 includes the data items "race ID", "date of event", "betting type", "group number", and "odds". The item "race ID" stores information identifying the race (race ID). The item "date of event" stores the date on which the race is held. The item "betting type" stores the type of betting type. The item "group number" stores the group numbers of the confirmed finishing positions from first place to a specified place, depending on the betting type, in the race (race) identified by the race ID. The item "odds" stores odds information corresponding to each betting ticket.

[0080] The accident management DB 57 includes data items such as "race ID," "date of event," "venue of event," and "car number where the accident occurred." The item "race ID" stores information that identifies the race (race ID). The item "date of event" stores the date on which the race is held. The item "venue of event" stores the venue of the race. The item "car number where the accident occurred" stores the car number where the accident (fall-off, etc.) occurred.

[0081] The compensation management DB58 includes the data items "User ID," "Compensation Flag," "Paid / Free," "Number of Missed Bet Due to Accident," and "Refund Rate." The "Race ID" item stores information identifying the user (user ID). The "Compensation Flag" item stores "Yes" if compensation is provided, and "No" if compensation is not provided. The "Paid / Free" item stores "Paid" if compensation is provided for a fee, and stores "Free" if compensation is provided for free. The "Number of Missed Bet Due to Accident" item stores the number of times a bet was missed due to an accident such as a fall for a player with the group number specified on the betting ticket purchased by the user during the race. The "Refund Rate" item stores the refund rate for the bet when compensation is provided.

[0082] The weather history DB 59 includes data items such as "race ID," "date and time of event," "venue," "weather type," "precipitation amount," "temperature," "humidity," "wind direction," and "wind speed." The "race ID" item stores information identifying the race (race ID). The "date and time of event" item stores the date and time of the race. The "venue" item stores the location of the race. The "weather type" item stores the weather type at the date and time of event and venue (clear, sunny, slightly cloudy, cloudy, smoke, dust, storm, blizzard, fog, drizzle, rain, sleet, snow, hail, sleet, and thunder). The "precipitation amount" item stores the amount of precipitation (mm / hour) at the date and time of event and venue. The "temperature" item stores the temperature at the date and time of event and venue. The "humidity" item stores the humidity at the date and time of event and venue. The "wind direction" item stores the wind direction at the date and time of event and venue. The item "wind speed" stores the wind speed at the event date and location.

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

[0084] 5 is a diagram showing an example of a betting ticket purchase screen in this embodiment. The betting ticket purchase screen 61 includes a logged-in user display field 62, an owned points display field 64, an owned points addition specification field 64a, an owned amount display field 65, an owned amount addition specification field 65a, a race name display field 66, a betting ticket specification field 67, and a "Purchase" button 74.

[0085] The logged-in user display field 62 displays the icon and user name of the user who is currently logged in to the betting ticket purchase system 11 using the user terminal 12. The owned points display field 64 displays the points that the user currently owns in the betting ticket purchase system 11. By tapping the owned points addition specification field 64a, points (charge) that can be used only within the betting ticket purchase system 11 to purchase betting tickets free of charge can be added. The owned amount display field 65 displays the amount that the user currently owns in the betting ticket purchase system 11. By tapping the owned money addition specification field 65a, an amount for purchasing betting tickets for a fee can be added (charged) to the betting ticket purchase system 11. Note that in the betting ticket purchase system 11, betting tickets can be purchased within this charged amount or points.

[0086] The name of the race for which a betting ticket is to be purchased is displayed in the race name display field 66. Note that the race name display field 66 may also display a message informing the user of the time remaining until the deadline for purchasing betting tickets for that race.

[0087] The betting ticket designation field 67 includes a betting ticket designation list 67a, a betting amount / betting point total display field 72, and a set unit purchase button 73.

[0088] The betting ticket designation list 67a includes a betting type / group designation field 68, a number designation field 69, an odds display field 70, and a bet / bet point designation field 71. The betting type / group designation field 68 is a field for designating a bet type. The number designation field 69 is a field for designating the group number of the finishing order according to the designated betting type (including the case of a win bet). The odds display field 70 displays the odds corresponding to the group number of the finishing order designated according to the betting type. The bet / bet point designation field 71 is a field for designating the bet or bet points for each group number. The bet / bet point total display field 72 displays the total of the bet / bet point designation fields 71 ​​in the betting ticket designation list 67a.

[0089] The set purchase button 73 is a button for purchasing betting tickets in units of a set, where one set is a combination of betting tickets in the betting ticket designation list 67a. Each time the "+" button on the set purchase button 73 is pressed, the number of sets to be purchased is increased. Each time the "-" button on the set purchase button 73 is pressed, the number of sets to be purchased is decreased.

[0090] 6 is an overall sequence diagram between the user terminal 12 and the management server 15 in this embodiment. The user operates the user terminal 12 to start an installed dedicated application program. Then, the user terminal 12, on which the dedicated application program has started, makes a login request (including the user ID) to the management server 15 (S1). The management server 15 queries the user management DB 52, performs authentication processing, and returns a login completion notification to the user terminal 12 (S2).

[0091] The user operates the user terminal 12 to select a race for which to bet, and performs an operation to display the betting ticket purchase screen 61 corresponding to the selected race. The user terminal 12 then makes a betting ticket purchase screen display request (including the user ID and race ID) to the management server 15 (S3). When the management server 15 receives the betting ticket purchase screen display request (including the user ID and race ID), it obtains the amount of money and points held from the user management DB 52 based on the user ID. The management server 15 also obtains odds information for that race based on the race ID. The management server 15 sends a response to the betting ticket purchase screen display request (including the amount of money held, points held, and odds information) to the user terminal 12 (S4).

[0092] When the user terminal 12 receives a response (including the amount of money held, the points held, and odds information) to the request to display the betting ticket purchase screen from the management server 15, it displays a betting ticket purchase screen 61 on the screen 14. The user operates the user terminal 12 to specify the betting ticket set number and the purchase amount (or purchase points) according to the betting type in the betting ticket designation field 67, and taps the "Purchase" button 74. Then, the user terminal 12 transmits a purchase request including the user betting information (user ID, race ID, betting ticket set number, and purchase amount (or purchase points)) to the management server 15 based on the contents of the betting ticket designation field 67 (S5).

[0093] The management server 15 acquires the purchase request from the user terminal 12. The management server 15 (registration unit 46) registers the contents of the user voting information included in the acquired purchase request in the voting management DB 53. The management server 15 (payment processing unit 44) performs payment processing for the purchase of the betting ticket based on the purchase request. When the payment processing is completed, the management server 15 updates the amount held (or held Pt) in the user management DB 52 based on the payment details, and notifies the user terminal 12 of the completion of the payment processing (S6).

[0094] After the race, when the finishing order is determined, the management server 15 (registration unit 46) registers the determined odds information for each betting type in the race result management DB 56 based on instructions from the competition operation manager terminal. After the race, when the finishing order is determined, the management server 15 (payout processing unit 45) obtains the determined odds information for each betting type for that race from the race result management DB 56 and performs payout processing for winning betting ticket information. Furthermore, if the race is successful and the bet is not successful due to a predetermined event (for example, a fall, breakdown, or other betting target accident) occurring to the athlete of the specified group number, the management server 15 (compensation processing unit 47) executes compensation processing, for example, to refund at least a portion of the bet amount to the user as compensation (S7).

[0095] Here, the race organizer determines whether a rider has fallen, been disqualified, or had a bicycle malfunction, and the resulting status is entered as the race result. It is possible to determine whether a rider has fallen based on video alone. Disqualifications (e.g., (1) interference with other competitors, (2) violation of rules, or (3) failure to reach the finish line within the designated time frame after the first-place finish due to a fall) are determined by the organizer. Disqualifications can include factors other than those that can be determined from video, so a decision by the organizer is more accurate than a decision based on video alone. Bicycle malfunctions are also entered as status. Fall compensation can be added for free or for a fee. Compensation for losses due to accidents such as falls or malfunctions that are the subject of a bet is sometimes referred to as "accident compensation" or "fall compensation." When paying for accident compensation, in addition to paying compensation at the time of betting, the organizer may also reduce the payout or odds for winning a bet, even if no compensation is paid at the time of betting.

[0096] 7A and 7B (hereinafter referred to as "FIG. 7") are diagrams showing a flowchart of an example of compensation processing in this embodiment. FIG. 7 corresponds to part of the processing of S7 in FIG. 6. Compensation processing is performed after the race results are determined and dividend processing is performed. Before compensation processing, race result information for the race is registered in the race result management DB 56, voting information for the race registered in the voting management DB is registered in the voting history DB 54, and if an accident occurs during the race, information about the accident is registered in the accident management DB 57.

[0097] The compensation processing unit 47 acquires accident information for the race for which the payout processing has been completed from the accident management DB 57 (S11). If the accident management DB 57 does not have accident information for the race (i.e., if no accident occurred in the race) (NO in S12), this flow ends.

[0098] If the accident management DB 57 contains accident information for the race (i.e., if an accident occurs in the race) (YES in S12), the compensation processing unit 47 acquires the compensation mode for the race from the race management DB 55 (S13). If the compensation mode is "off" (NO in S14), this flow ends. If the compensation mode is "on" (YES in S14), the compensation processing unit 47 acquires race result information for the race from the race result management DB 56, and extracts information on losing votes from the vote management DB 53 for each user ID based on the race result information (S15).

[0099] The compensation processing unit 47 performs the processes of S16 to S24 described below for the voting information that did not win for each user ID. First, the compensation processing unit 47 initializes a variable work to 0 (S16).

[0100] The compensation processing unit 47 performs the processes of S17 to S20 described below for each piece of betting (betting type) information. The compensation processing unit 47 determines whether the set number specified in the betting information includes the car number in which the accident occurred (S17).

[0101] If it is determined that the group number specified in the voting information includes the vehicle number in which the accident occurred (YES in S17), the compensation processing unit 47 calculates the compensation amount (or compensation Pt) based on the purchase amount (or purchase Pt) of that group number based on the compensation management information obtained from the compensation management DB 58 (S18).

[0102] The compensation processing unit 47 registers the calculated compensation (or compensation Pt) in the "compensation amount" or "compensation Pt" of the betting history information for the race of the corresponding user in the betting history DB 54 (S19). The compensation processing unit 47 adds the calculated compensation (or compensation Pt) to the variable work (S20).

[0103] If it is determined that the set number specified in the voting information does not include the car number in which the accident occurred (NO in S17), the compensation processing unit 47 performs the process of S17 on the next voting information.

[0104] When the loop process of S17 to S20 has been completed for all of the voting information of the user ID that did not win, the compensation processing unit 47 determines whether the variable work>0 (S21).

[0105] If the variable work>0 (YES in S21), the compensation processing unit 47 adds (refunds) the variable work to the retained amount (or retained Pt) of the corresponding user information in the user management DB (S22).

[0106] The compensation processing unit 47 notifies the user corresponding to the user ID of the betting result and that the compensation will be refunded (S23). When notifying the betting result in the payout process, the processing of S23 only needs to notify that the compensation will be refunded. In addition, the compensation processing unit 47 may update the "number of missed accidents" and the number of votes in the compensation management information for the user in the compensation management DB 58.

[0107] If the variable work=0 (NO in S21), the compensation processing unit 47 notifies the user corresponding to the user ID of the voting result (S24). Note that if the voting result is notified in the payout process, the process of S24 may be omitted.

[0108] Variations of examples of this embodiment will be described below. First, Example 1 will be described. In Example 1, a notification is given to a first user who has lost a vote a predetermined number of times or more due to a past accident, that at least a portion of the bet amount will be compensated for the accident if the first user loses a vote due to an accident.

[0109] Fig. 8 is a diagram showing a flowchart of an example of compensation processing in this embodiment (Example 1). Fig. 8 is obtained by adding S31 to S34 to the flowchart in Fig. 7B. The differences will be described below.

[0110] After processing S16, the compensation processing unit 47 counts the betting information including the car number in which the accident occurred from the set numbers of all the betting information that was not correct for that user ID (S31). The compensation processing unit 47 obtains the number of missed bets due to accident occurrences included in the compensation management information for that user ID from the compensation management DB 58, and adds the measured number to the obtained number of missed bets due to accident occurrences. The compensation processing unit 47 updates the number of missed bets due to accident occurrences included in the compensation management information for that user ID in the compensation management DB 58 with the number of missed bets due to accident occurrences to which the measured number has been added (S32).

[0111] The compensation processing unit 47 determines whether the updated number of missed bets due to accident occurrence is equal to or greater than a predetermined number (S33). If the number of missed bets due to accident occurrence is equal to or greater than the predetermined number (YES in S33), the compensation processing unit 47 notifies the user of the user ID that compensation money or compensation points will be provided if the bet is not a correct bet due to an accident occurring for the specified car number (S34). Thereafter, the compensation processing unit 47 performs the processes of S17 to S24. If the number of missed bets due to accident occurrence is less than the predetermined number (NO in S32), the compensation processing unit 47 performs S24.

[0112] 9, from the viewpoint of eliminating the need to differentiate between providing and not providing compensation for the same race, accident compensation is provided when the set numbers of all the user's unsuccessful bets in the race, including the car number in which the accident occurred, are counted and added to the number of accident-related misses, and the count is equal to or greater than a predetermined number. However, this is not limiting. For example, after processing S17 in FIG. 7B, the number of accident-related misses contained in the user's compensation management information may be obtained from the compensation management DB 58 and incremented, and a determination may be made as to whether the incremented number of accident-related misses is equal to or greater than a predetermined number. If the incremented number of accident-related misses is equal to or greater than the predetermined number, processing from S18 onward may be performed. If the incremented number of accident-related misses is less than the predetermined number, processing from S17 onward may be performed for the next bet. As a result, even if the voting information is for the same race and the group number specified in the voting information includes the car number in which an accident occurred, if the number of missed wins due to the accident spans over, some votes will be compensated and some will not be compensated.

[0113] In the first embodiment, when the number of missed bets due to accidents is equal to or greater than a predetermined number, the compensation processing unit 47 notifies the user that compensation will be provided, but this is not limited to this. For example, if a user has not voted for a predetermined period of time, the user may be notified that compensation will be provided in the form of compensation money or compensation points if an accident such as a fall occurs during a race and the user misses the bet. That is, the voting history DB 54 may be referenced, and such compensation may be provided to users for whom a predetermined period of time (e.g., two weeks, three weeks, one month, etc.) has passed since the last time they voted.

[0114] Next, a description will be given of Example 2. In Example 2, accident compensation will be provided to a user when the user has bet a predetermined amount or more on betting.

[0115] Fig. 9 is a diagram showing a flowchart of an example of compensation processing in this embodiment (Example 2). Fig. 9 is obtained by adding S41 to the flowchart in Fig. 7B. The difference will be described below.

[0116] If it is determined that the group number specified in the voting information includes the vehicle number in which the accident occurred (YES in S17), the compensation processing unit 47 determines whether the purchase amount (or purchase points) for the group number including that vehicle number is equal to or greater than a predetermined amount (S41).

[0117] If the purchase amount (or purchase points) for the group number including that car number is equal to or greater than a predetermined amount (YES in S41), the compensation processing unit 47 performs the processes of S18 to S20. If the purchase amount (or purchase points) for the group number including that car number is less than a predetermined amount (NO in S41), the compensation processing unit 47 performs the process of S17 for the next voting information.

[0118] In addition, users who have bet a predetermined amount or more in a predetermined period (for example, one day) may be provided with compensation for falling off their bike if they lose the bet due to an accident such as a fall during the race. This reduces the amount of bet when betting on a race in which only runners who will not fall off their bike participate, for fear of falling off their bike. However, by providing compensation for falling off to users who have bet a large amount on many races, they can bet without fear of losses due to falls.

[0119] In addition, if a user has bet a predetermined amount or more on betting during the first period, the user may be compensated for falling off the horse. This allows compensation for falling off the horse if the user has bet a predetermined amount or more during a predetermined period (from the start of the races on a predetermined day to the end of all races). For example, when a screen for the user's first bet is displayed on a predetermined day, an explanation of this function may be displayed.

[0120] Also, for example, there may be no compensation until 5,000 yen is bet per day, but if more than 5,000 yen is bet, fall compensation may be provided in the next race or later. For example, in pattern 1, if 5,000 yen is bet per day, fall compensation may be available once, and if another 5,000 yen is bet, a second compensation may be available. In pattern 2, if 5,000 yen is bet per day, fall compensation may be available once, and if 10,000 yen is bet, two fall compensations may be available. In pattern 3, if more than 5,000 yen is bet per day, fall compensation may be provided any number of times that day.

[0121] Furthermore, if a user has bet a predetermined amount or more on the first race, the user may be compensated for a fall. In other words, in FIG. 9, for each bet amount (bet amount per group number) placed on each betting information (each group number), whether or not the bet amount is a predetermined amount or more is determined, and compensation is paid if the bet amount is equal to or greater than the predetermined amount. However, this is not limiting. For example, it may be determined whether or not the total bet amount of all bets placed in the race (limited to unsuccessful bets and including the car number where the accident occurred) is equal to or greater than a predetermined amount, and compensation is paid if the total bet amount is equal to or greater than the predetermined amount. This allows compensation for a fall when a user attempts to bet a predetermined amount or more on a single race. This is expected to encourage users who bet only small amounts due to fear of a fall to bet a larger amount.

[0122] In addition, if a user has bet a predetermined amount or more on the first bet for the first race, the user may be compensated for a fall. This is expected to encourage users who have purchased many types of betting tickets for one race (single number for the first favorite, single number for the second favorite, consecutive numbers, trifecta) to bet a large amount for a small amount of betting ticket due to fear of falling.

[0123] Next, a description will be given of Example 3. In Example 3, if a race involving a rider who has fallen off his / her bike satisfies a predetermined condition during the second period, compensation for the rider's fall will be provided for a race held during a third period after the second period.

[0124] Fig. 10 is a diagram showing a flowchart of an example of compensation mode switching processing in this embodiment (Example 3). Fig. 10 is a flowchart for providing compensation for falls for races after a predetermined period when there are many falls in races held within a predetermined period. It is assumed that the "compensation mode" in the race management DB 55 is set to "none" by default.

[0125] The compensation processing unit 47 extracts accident information for a first predetermined period at a target venue from the accident management DB 57 and tallies the number of accident occurrences (S51). The compensation processing unit 47 determines whether the number of accident occurrences is equal to or greater than a predetermined number (S52).

[0126] If it is determined that the number of accident occurrences is equal to or greater than the predetermined number (YES in S52), the compensation processing unit 47 changes the compensation mode for the race held in the predetermined period at the target venue in the race management DB 55 to "Yes" (S53). If it is determined that the number of accident occurrences is less than the predetermined number (NO in S52), this flow ends.

[0127] Weather conditions and other factors can make the road surface slippery, and if there are many falls, this could lead to people refraining from betting. However, according to Example 3, if there are many falls in races held within a specified period, compensation for falls can be provided for races after the specified period.

[0128] Next, a fourth embodiment will be described. In the fourth embodiment, fall prediction information that can determine the possibility of a fall is acquired, and fall compensation is provided for a race in which a fall is likely to occur based on the prediction information.

[0129] Fig. 11 is a diagram showing a flowchart of an example of compensation mode switching processing in this embodiment (Example 4). Fig. 11 is a flowchart for obtaining fall prediction information that can determine the possibility of a fall, and providing fall compensation for a race where a fall is likely to occur based on the prediction information. It is assumed that the "compensation mode" in the race management DB 55 is set to "none" by default.

[0130] The compensation processing unit 47 acquires weather forecast data for the day of the race at the target venue from an external server (S61). The compensation processing unit 47 analyzes the correlation between the weather at the target venue and accidents based on the weather history DB 59 and the accident management DB 57 (S62). The compensation processing unit 47, for example, calculates the correlation coefficient between the weather type and the number of accidents at the venue on that day, the correlation coefficient between the amount of precipitation and the number of accidents, the correlation coefficient between the temperature and the number of accidents, the correlation coefficient between humidity and the number of accidents, the correlation coefficient between wind direction and the number of accidents, and the correlation coefficient between wind speed and the number of accidents.

[0131] Note that the relationship between each weather condition and the number of accidents may be calculated and used as the analysis result. For example, the number of accidents for each weather type may be calculated from the weather history DB 59 and the accident management DB 57, or the number of accidents for each precipitation amount divided into stages (for example, 0 to less than 5 mm, 5 to less than 10 mm, 10 to less than 15 mm, etc.) may be calculated, or the number of accidents may be calculated in the same way for temperature, humidity, wind direction, wind speed, etc.

[0132] The compensation processor 47 calculates the possibility of an accident (probability of an accident occurring) at the target venue on the day based on the weather forecast data for the day (weather type, precipitation, temperature, humidity, wind direction, wind speed, etc.) and the analysis results (S63). For example, the compensation processor 47 calculates the probability of an accident occurring under the conditions of the weather forecast data from the item with the highest correlation coefficient (and also the item with the second and third highest correlation coefficients) and the number of accidents that have occurred in the past. The probability of an accident occurring may also be calculated based on aggregating each weather condition and the number of accidents. For example, if 200 accidents occur out of 500 events held on rainy days, the probability of an accident occurring is 40% (= 200 / 500).

[0133] The compensation processing unit 47 determines whether the possibility of an accident (probability of an accident occurring) on ​​the day at the target venue is equal to or greater than a predetermined value (S64). Examples of the predetermined value include 20%, 30%, 40%, 50%, etc.

[0134] If it is determined that the possibility of an accident on the day at the target venue is equal to or greater than a predetermined value (YES in S64), the compensation processing unit 47 changes the compensation mode for the race held at the target venue during the predetermined period to "Yes" in the race management DB 55 (S65). If it is determined that the number of accident occurrences is less than the predetermined number (NO in S64), this flow ends.

[0135] In Example 4, it is possible to provide compensation for falls on days when the conditions, such as weather and season, are favorable for falls. For example, people may refrain from betting on the day after a rainy day or on days when the temperature is low and the road surface is slippery, due to fear of falls. In Example 4, however, fall prediction information that can determine the possibility of falls can be obtained, and fall compensation can be provided for races where there is a high possibility of falls based on the prediction information.

[0136] Next, a fifth embodiment will be described. In the fifth embodiment, it will be explained that the compensation conditions for a user who misses a prize due to an accident (for example, whether compensation for falling off the bike is paid or free, the number of times the user falls off the bike, the number of times the user has voted in the past, etc.) and / or the compensation contents (for example, the refund rate when the user falls off the bike, etc.) are determined based on the user's voting history.

[0137] Fig. 12 is a diagram showing a flowchart of an example of compensation processing in this embodiment (Example 5). Fig. 12 is obtained by adding S71 to S75 to the flowchart in Fig. 7B. The differences will be described below.

[0138] After the process of S16, the compensation processing unit 47 counts the betting information including the car number in which the accident occurred from the set numbers of all the betting information that did not win for that user ID (S71). The compensation processing unit 47 obtains the number of missed accident occurrences included in the compensation management information for that user ID from the compensation management DB 58, and adds the measured number to the obtained number of missed accident occurrences (S72).

[0139] The compensation processing unit 47 determines whether the updated number of misplays due to accident occurrence is equal to or greater than a predetermined number (S73). If the number of misplays due to accident occurrence is equal to or greater than the predetermined number (YES in S73), the compensation processing unit 47 acquires compensation information (e.g., refund rate) of the user from the compensation management DB 58 (S74).

[0140] The compensation processing unit 47 determines new compensation details based on the user's compensation information and / or voting history, and updates the compensation management DB 58 (S75). For example, if the compensation information acquired from the compensation management DB 58 is for a fee or if the number of times the user has missed a prize due to a fall is equal to or greater than a predetermined value, the compensation processing unit 47 may update the refund rate by adding an additional 10%. Also, for example, the compensation processing unit 47 may tally the user's voting history (number of votes) from the voting history DB 54, and if the number of votes is equal to or greater than a predetermined value, the compensation processing unit 47 may update the refund rate by adding an additional 10%.

[0141] If the number of accidental misses is less than the predetermined number (NO in S72), the compensation processing unit 47 calculates the compensation (or compensation Pt) based on the purchase amount (or purchase Pt) of that set number and the compensation management DB 58 (S17).

[0142] 12, from the viewpoint that there is no need to differentiate the compensation content between bets in the same race, the set numbers of all of the user's missed bets in that race, including the car number in which the accident occurred, are counted, and new compensation content is determined if the count added to the number of missed bets due to accidents is equal to or greater than a predetermined number. However, this is not limited to this. For example, after processing S17 in FIG. 7B, the number of missed bets due to accidents contained in the user's compensation management information may be obtained from the compensation management DB 58 and incremented, and it may be determined whether the incremented number of missed bets due to accidents is equal to or greater than a predetermined number. If the incremented number of missed bets due to accidents is equal to or greater than the predetermined number, processing of S74 and S75 is performed, and processing from S18 onwards is performed. If the incremented number of missed bets due to accidents is less than the predetermined number, processing of S17 may be performed for the next bet. As a result, even if the voting information is for the same race and the group number specified in the voting information includes the car number in which an accident occurred, if the number of missed wins due to the accident spans over, compensation may be based on the previous compensation content or the new compensation content.

[0143] Note that past voting history may be the number of times a user has missed a bet due to an accident such as a fall, and users with a greater number of missed bets may be given more preferential treatment in terms of content or conditions than users with a smaller number of missed bets. For example, if a user has missed a bet due to a rider falling off their bike 10 times in the past week, fall compensation from the next bet onwards may be free, with a refund rate of 80%. Alternatively, if a user has missed a bet due to a rider falling off their bike five times in the past week, 10% of the bet amount may be paid as fall compensation, with an additional refund rate of 30%. In this way, users who have missed a certain number of bets due to a rider falling off their bike more often may be given better fall compensation conditions or content than users with a smaller number of missed bets.

[0144] In addition, the terms and contents of the fall compensation can be determined based on the number of votes or the amount of votes in the past. For example, fall compensation can be provided for one month after new registration for the service. Beginners are likely to drop out of the service if they continue to lose their winnings due to falls, but this can be prevented by offering favorable compensation contents and / or conditions. Furthermore, by providing fall compensation to users who vote frequently and offering favorable compensation contents and / or conditions, it is possible to prevent users from switching to other services.

[0145] Next, a sixth embodiment will be described. In the sixth embodiment, an example will be described in which, when purchasing a betting ticket, a betting type and a betting amount for a predetermined race are designated, along with whether or not to receive compensation for falling off the race.

[0146] 13 is a diagram showing an example of a compensation grant confirmation message screen in this embodiment (Example 6). The compensation grant confirmation message screen 81 pops up when the “Purchase” button 74 on the betting ticket purchase screen 61 in FIG.

[0147] The compensation grant confirmation message screen 81 includes a "Add compensation" check box 82, an "OK" button 83, and a "Cancel" button 84. For example, the compensation grant confirmation message screen 81 displays a message stating, "If you want to add compensation, please check the 'Add compensation' check box."

[0148] When the "Add compensation" checkbox 82 is checked and the "OK" button 83 is pressed, the user terminal 12 transmits to the management server 15 a betting ticket purchase request with the compensation flag set to "Yes".

[0149] If the "OK" button 83 is pressed without checking the "Add compensation" checkbox 82, the user terminal 12 will send a betting ticket purchase request with the compensation flag set to "No" to the management server 15. If the "Cancel" button 84 is pressed, the purchase of the betting ticket will be canceled and the screen will return to the betting ticket purchase screen 61 in Figure 5.

[0150] This allows users to choose whether or not to add a fall compensation when purchasing a betting ticket. Fall compensation can be either paid or free. For example, if a fall compensation is paid and the fall compensation is added, the odds may be reduced or the payout may be reduced if a winning bet is made. For example, if the odds for the group number "1-2" are 10 times, the odds may be 9.5 times if the fall compensation is added.

[0151] In addition, for example, if a fall compensation is available and a fee is charged, an additional amount may be paid in addition to the bet amount. For example, if a bettor bets 1,000 yen on the group number "1-2," the total amount paid may be 1,100 yen, including the fall compensation.

[0152] Alternatively, a screen may be displayed that displays fall prediction information and allows the user to select whether or not to purchase fall compensation. This will be described with reference to FIG.

[0153] Fig. 14 is a flowchart of an example of the display processing of the compensation grant confirmation message screen in this embodiment. Fig. 14 corresponds to a part of the processing of S5 in Fig. 6. When the betting ticket purchase screen 61 in Fig. 5 is displayed, the management server 15 waits until the user presses the "Purchase" button 74 (NO in S81). When the user presses the "Purchase" button 74 (YES in S81), the management server 15 acquires a compensation grant confirmation message screen display request (including the set number for each betting type) from the user terminal 12 (S82).

[0154] The management server 15 calculates the standard deviation of the number of accident occurrences of the players (population) from the player-specific accident management DB (S83). The player-specific accident management DB is a database stored in the storage unit 51, and is a database that manages data on the occurrence of accidents in the competitions of all players belonging to the sports organization.

[0155] The management server 15 calculates the deviation value of the number of accident occurrences for each player in the group number based on the calculated standard deviation (S84). The management server 15 determines whether or not there is a player whose calculated deviation value exceeds a predetermined value (S85).

[0156] If the calculated deviation value includes a runner whose value exceeds a predetermined value (YES in S85), the management server 15 displays a compensation grant confirmation message screen 81 (S86). At this time, the message displayed is, "This race will feature runners with a history of falling off their bikes. If you wish to grant compensation, please check the 'Give compensation' checkbox." If the 'Cancel' button 84 is pressed on the compensation grant confirmation message screen 81 (NO in S87), the process returns to S81.

[0157] When the "OK" button 83 is pressed on the compensation grant confirmation message screen 81 (YES in S87), the management server 15 acquires a purchase request with a compensation flag set to "Yes" or "No" depending on whether the "Enable compensation" checkbox 82 is checked (S88). Also, when the calculated deviation value does not include any player exceeding a predetermined value (NO in S85), the management server 15 acquires a purchase request with a compensation flag set to "No" (S88).

[0158] Based on the acquired purchase request, the management server 15 (registration unit 46) registers the contents of the user voting information in the voting management DB 53 and registers the compensation flag in the compensation management DB 58 (S89).

[0159] This makes it easier for beginners who do not know which riders are likely to fall off their bikes to apply for fall compensation, and reduces the risk of missing a prize due to a fall, thereby preventing them from abandoning the service.

[0160] Next, a seventh embodiment will be described. In the seventh embodiment, an example will be described in which the user is asked in advance whether or not to add a fall compensation for the third period.

[0161] 15 is a diagram showing an example of a compensation setting screen in this embodiment (Example 7). The compensation setting screen 91 includes a login user display field 92, a fixed payment amount display field 93, a period setting field 94, a field 95 for setting the number of falls compensation, a "Register" button 96, and a "Cancel" button 97.

[0162] The logged-in user display field 92 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 fixed payment amount display field 93 displays the fixed payment amount. The period setting field 94 displays the periods (1 day, 1 week, 2 weeks, 1 month, etc.) that can be set for the fixed payment amount as list items, from which any period can be selected and set. The number of times of fall compensation setting field 95 displays the number of times of fall compensation that can be set (1 time, 2 times, 3 times, etc.) in the period set in the period setting field 94 as list items, from which any number of times of fall compensation can be selected and set.

[0163] In this way, by paying a flat rate for fall compensation, users can receive fall compensation for a fixed price. For example, by paying 1,000 yen per month, they can choose options such as three fall compensations per month or one fall compensation per week. Furthermore, the flat rate payment can be selected for a period such as one week, ten days, or one month, or the number of fall compensations during the subscription period. The number of fall compensations may also be unlimited during the set period. Furthermore, if the set number of fall compensations is not used up within the set period for a flat rate payment, the remaining fall compensations may be carried over to the next period.

[0164] As another variation of the seventh embodiment, if the number of times compensation for falling off the bicycle is insufficient with a fixed payment, an additional fee may be charged to increase the number of times. This will be described with reference to FIG.

[0165] 16 is a diagram illustrating the periods in this embodiment (Example 7). Here, the user is asked in advance whether or not to receive compensation for falls up to the first number of times during the third period, and if the user has received compensation for falls up to the first number of times during the third period, the user is asked whether or not to receive compensation for falls up to the second number of times during the fourth period. For example, the following two patterns can be given for the fourth period.

[0166] Figure 16(A) shows an example in which, if the fall compensation is used up during the third period and an additional fall compensation is added by paying an additional fee, the expiration of the additional compensation period coincides with the third period. In other words, the fourth period is subordinate to the third period.

[0167] Figure 16(B) shows an example in which, if you use up your fall compensation during the third period and pay an additional fee to add fall compensation, the start of the additional compensation period (fourth period) will expire after a period equivalent to the third period has elapsed from the date of purchase. In other words, the fourth period is independent of the third period.

[0168] In this way, when the fixed payment of the fall compensation is used up, an additional increase in the number of times can be accepted. In this case, the fourth period may be until the end of the third period or may be the same length as the third period.

[0169] If the fourth period does not include the fall compensation, the races eligible for the fall compensation may be determined after the end of the third period. For example, if the user decides not to pay the additional fee, the betting tickets eligible for the fall compensation may be determined at the end of the fixed-rate payment period. For example, if a user registers for the fixed-rate payment during the third period and uses up the fall compensation during the third period, the user will be unable to place bets in the second half of the third period. For example, if the fall compensation is used for a small bet, the user will be unable to place large bets in the second half. Therefore, the races eligible for the fall compensation may be determined by the management server 15 so that the refund amount is large, or the user may select the races eligible for the fall compensation after the third period ends.

[0170] Next, an eighth embodiment will be described. In the eighth embodiment, a plurality of bets are made for a predetermined race, and compensation for a fall is provided when the bets include a miss due to an accident such as a fall, and no hits are included.

[0171] Fig. 17 is a flowchart illustrating an example of compensation processing in this embodiment (Example 8). Fig. 17 is obtained by replacing S15 in Fig. 7A with S91. The difference will be described below.

[0172] If the compensation mode is "enabled" (YES in S14), the compensation processing unit 47 extracts (S91) users who did not place a single winning bet in the race based on the bet management DB 53 and the race result management DB 56. After processing S91, the compensation processing unit 47 performs S16 to S24.

[0173] By processing S91, it is possible to exclude users who have purchased multiple ballots for that race, including a winning ballot, but whose ballots are not winning because an accident occurred on a car number with a specified set number in a ballot other than the winning ballot, i.e., it is possible not to perform compensation processing for such users.On the other hand, it is possible to perform compensation processing for users who have purchased multiple ballots for that race but not won any ballots, and whose ballots are not winning because an accident occurred on a car number with a specified set number.

[0174] This means that if you purchase multiple tickets for a certain race, and all of your tickets lose (this may include races without crashes), including tickets that lost due to crashes, you can receive compensation for the loss.It can be quite a shock if none of your purchased betting tickets are correct, but if any of your tickets include a bet that lost due to a crash, you can receive compensation for the loss.

[0175] In the eighth embodiment, all the betting information (betting tickets) may be betting information (betting tickets) purchased not only for the race in question but also for all races on the day or for all races during a predetermined period.

[0176] In this embodiment, two or more of Examples 1 to 8 may be combined in any manner.

[0177] 18 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 and a management server 15. 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.

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

[0179] When the computer 101 is the management server 15, the CPU 102 reads the program according to this embodiment from the storage device 105 and functions as an acquisition unit 43, a settlement processing unit 44, a dividend processing unit 45, a registration unit 46, and a compensation processing unit 47. The ROM 103 is a read-only memory. The RAM 104 is a memory for temporary storage.

[0180] 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 programs according to the embodiments of the present invention, various databases, data, etc. stored in the storage unit 51.

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

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

[0183] The program for realizing the processes described in the above embodiments may be stored in, for example, the storage device 105 from a program provider via a communication network and the communication I / F 108. The program for realizing the processes described in the above embodiments may also be stored in a commercially available portable storage medium. In this case, the portable storage medium may be set in the reading device 109, 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.

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

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

[0186] <Summary> [General-purpose assignment] One of the objectives of the present invention is to reduce the loss of motivation for users to vote.

[0187] Issues corresponding to [Appendix 1] One of the purposes of the present invention is to alleviate the anxiety of users who may lose their vote due to an accident involving the betting target specified according to the betting method they have chosen, thereby reducing the decrease in users' motivation to vote. [Appendix 1] A reception unit that receives, from a user, designated athletic body information that identifies the designated athletic body according to a betting method in a predetermined competition in which multiple athletic bodies compete for finishing order, and betting information that specifies a betting amount; a compensation control unit that executes a compensation process to refund at least a portion of the bet amount to the user as compensation if the competition is successful and the bet is not successful due to a predetermined event occurring in the competition body corresponding to the designated competition body information; An information processing device comprising: According to the above information processing device, it is possible to ease the user's anxiety caused by losing a bet due to an accident with the betting target specified according to the betting type, and to reduce the user's decrease in motivation to vote.

[0188] Issues corresponding to [Appendix 2] One of the objects of the present invention is to prevent users who have previously lost a bet due to an accident involving a designated player from refraining from purchasing betting tickets. [Appendix 2] When the first user's betting is not successful because the predetermined event has occurred for the sporting body corresponding to the designated sporting body information a predetermined number of times or more, the compensation control unit notifies the first user that compensation will be provided when the first user's betting is not successful because the predetermined event has occurred. 2. The information processing device according to claim 1. According to the information processing device described above, it is possible to prevent users who have previously lost a bet due to an accident involving a designated player from refraining from purchasing betting tickets.

[0189] Issues corresponding to [Appendix 3] One of the purposes of the present invention is to encourage users who have previously lost their bets due to an accident involving a designated player and have refrained from purchasing betting tickets to return to the service. [Supplementary Note 3] When the first user has not voted for a predetermined period of time, the compensation control unit notifies the first user that compensation will be provided if the vote is not successful due to the occurrence of the predetermined event. 3. The information processing device according to claim 2. According to the information processing device described above, it is possible to prevent users who have previously lost a bet due to an accident involving a designated player from refraining from purchasing betting tickets.

[0190] Issues corresponding to [Appendix 4] One of the purposes of the present invention is to allow users to vote with peace of mind by providing accident compensation when purchasing voting tickets worth more than a certain amount. [Supplementary Note 4] The compensation control unit executes the compensation process for the second user when the second user designates the voting amount equal to or greater than a predetermined amount. 2. The information processing device according to claim 1. According to the information processing device described above, accident compensation is provided when purchasing voting tickets worth a certain amount or more, allowing users to vote with peace of mind.

[0191] Issues corresponding to [Appendix 5] One of the purposes of the present invention is to provide accident compensation to people who bet large amounts on many races, thereby encouraging them to purchase betting tickets without fear of losing their bets due to an accident. [Supplementary Note 5] The compensation control unit executes the compensation process for the second user when the second user has cumulatively designated the voting amount equal to or greater than a predetermined amount within a predetermined period. 5. The information processing device according to claim 4. According to the information processing device, accident compensation is provided to people who have bet large amounts on many races, so that it is possible to encourage people to purchase betting tickets without fearing that their bets will be unwinning due to an accident.

[0192] Issues corresponding to [Appendix 6] One of the purposes of the present invention is to provide accident compensation to people who bet a large amount on one race, thereby encouraging them to purchase betting tickets without fear of losing their bet due to an accident. [Supplementary Note 6] The compensation control unit executes the compensation process for the second user when the second user has designated the betting amount for the first competition to be equal to or greater than a predetermined amount. 5. The information processing device according to claim 4. According to the information processing device, accident compensation is provided to people who have bet large amounts on many races, so that it is possible to encourage people to purchase betting tickets without fearing that their bets will be unwinning due to an accident.

[0193] Issues corresponding to [Appendix 7] One of the purposes of this invention is to encourage users who purchase many types of tickets for one race (single number for the most popular, single number for the second most popular, consecutive numbers, trifecta) but who are afraid of losing their horse and therefore have small amounts on each ticket to bet a larger amount. [Supplementary Note 7] The compensation control unit executes the compensation process for the second user when the second user designates the betting amount equal to or greater than a predetermined amount for the designated sporting event information corresponding to the betting type in the first sporting event. 5. The information processing device according to claim 4. According to the above information processing device, even if a user purchases many types of betting tickets for one race (single number for the most popular, single number for the second most popular, consecutive numbers, trifecta), it is possible to encourage a user who has bet a small amount on each ticket due to fear of losing their horse to bet a larger amount.

[0194] Issues corresponding to [Appendix 8] One of the purposes of the present invention is to reduce the tendency to refrain from purchasing votes for a race in which an accident has occurred due to the influence of weather or the like. [Appendix 8] The compensation control unit executes the compensation process in a third competition to be held in a third period after the second period when the holding status of the second competition in which the predetermined event occurred satisfies a predetermined condition during the second period. 2. The information processing device according to claim 1. According to the information processing device described above, it is possible to reduce the tendency to refrain from purchasing votes for a race in which an accident has occurred due to the influence of weather or the like.

[0195] Issues corresponding to [Appendix 9] One of the purposes of the present invention is to reduce the tendency to refrain from buying votes for events held during weather conditions where accidents are more likely to occur. [Appendix 9] The compensation control unit executes the compensation process for the competition in which the predetermined event is likely to occur, determined based on the weather history information of the venue on the day of the competition that has been registered in advance, the number of occurrences of the predetermined event, and the weather forecast information of the venue on the day of the competition. 2. The information processing device according to claim 1. According to the information processing device described above, it is possible to reduce the tendency to refrain from purchasing votes for competitions held in weather conditions where accidents are more likely to occur.

[0196] Issues corresponding to [Appendix 10] One of the objectives of the present invention is to reduce users' anxiety about voting and further encourage them to purchase voting tickets by adjusting the conditions and / or content of accident compensation according to the user's voting history. [Supplementary Note 10] The compensation control unit determines the conditions for executing the compensation process or the amount of the compensation based on the history of the user's past voting information. 2. The information processing device according to claim 1. According to the above information processing device, by adjusting the conditions and / or content of accident compensation according to the user's voting history, it is possible to reduce the user's anxiety about voting and further encourage them to purchase voting tickets.

[0197] Issues corresponding to [Appendix 11] One of the purposes of the present invention is to reduce the dropout of users who contribute significantly to the sales of the service by more generously compensating users who have lost votes more than a predetermined number of times in the past due to falling off their bikes. [Appendix 11] The history of the past voting information is the first number of times that the voting was not successful due to the occurrence of the predetermined event for the athletic body corresponding to the designated athletic body information, The compensation control unit reduces the condition or increases the amount of the compensation for a user whose first number of times is more than the predetermined number of times, compared to a user whose first number of times is less than the predetermined number of times. 11. The information processing device according to claim 10. According to the information processing device described above, by more generously compensating users who have lost votes more than a predetermined number of times due to past falls, it is possible to reduce the dropout of users who contribute more to the sales of the service from the service.

[0198] Issues corresponding to [Appendix 12] One of the purposes of the present invention is to give preferential treatment to users who are contributing more to the sales of the service and new users, and to encourage them to purchase voting tickets with greater peace of mind. [Supplementary Note 12] The compensation control unit determines the conditions for executing the compensation process or the content of the compensation process based on the number of times the voting information has been received from the user or the voting amount. 11. The information processing device according to claim 10. According to the information processing device described above, users who are contributing more to the sales of the service and new users can be given preferential treatment, and it is possible to encourage them to purchase betting tickets with more peace of mind.

[0199] Issues corresponding to [Appendix 13] One of the purposes of the present invention is to allow users to choose whether or not to purchase accident compensation, thereby reducing the psychological burden that may arise when purchasing a betting ticket, such as worrying about what to do if the betting ticket is lost due to an accident such as falling off one's bike. [Supplementary Note 13] The reception unit receives, from the user, the voting information and compensation presence / absence information indicating whether or not compensation is to be provided; The compensation control unit executes the compensation process for the user when the received compensation presence / absence information indicates that the compensation is to be provided. 2. The information processing device according to claim 1. According to the above-mentioned information processing device, the user can select whether or not to purchase accident compensation, thereby reducing the psychological burden when purchasing a betting ticket, such as worrying about what to do if the betting ticket is lost due to an accident such as falling off one's bike.

[0200] Issues corresponding to [Appendix 14] One of the purposes of the present invention is to allow beginner users who do not know which riders are likely to fall off their bikes to purchase votes with confidence. [Appendix 14] The compensation control unit inquires of the user whether or not to provide the compensation based on history information regarding the predetermined cause of each of the game objects. 14. The information processing device according to claim 13. According to the information processing device described above, for example, beginner users who do not know which riders are likely to fall off their bikes can purchase their votes with confidence.

[0201] Issues corresponding to [Appendix 15] One of the objects of the present invention is to introduce a flat-rate system to increase the convenience of accident compensation for users. [Supplementary Note 15] The receiving unit receives compensation presence / absence information indicating whether or not compensation is to be provided at a predetermined amount for the first unit period from the user, The compensation control unit executes the compensation process for the user when the received compensation presence / absence information indicates that the compensation is to be provided. 2. The information processing device according to claim 1. According to the information processing device, a flat-rate system can be introduced, thereby increasing the convenience of accident compensation for users.

[0202] Issues corresponding to [Appendix 16] One of the objects of the present invention is to further enhance the convenience of flat-rate systems. [Supplementary Note 16] The compensation control unit executes the compensation process a first number of times in the first unit period, When the compensation process is executed the first number of times before the end of the first unit period, the reception unit receives, before the end of the first unit period, second compensation presence / absence information indicating whether or not the compensation is to be provided up to a second number of times in a second unit period. 16. The information processing device according to claim 15. According to the information processing device, the convenience of the flat-rate system can be further improved.

[0203] Issues corresponding to [Appendix 17] One of the objects of the present invention is to enable flexible operation of a flat-rate system for user accident compensation from the viewpoint of user friendliness. [Supplementary Note 17] When the received compensation presence / absence information indicates that the compensation for the second unit period is not provided, the compensation control unit determines the competition to be covered by the compensation for the first unit period after the expiration of the first unit period. 17. The information processing device according to claim 16. According to the information processing device described above, from the viewpoint of user friendliness, it is possible to flexibly operate a flat-rate system for accident compensation for users.

[0204] Issues corresponding to [Appendix 18] One of the purposes of this invention is to reduce the mental shock of users who have purchased betting tickets for a specified race and all of their betting tickets are lost (this may include races without accidents), including tickets that were lost due to an accident, by providing compensation for falling off the bike. [Appendix 18] The compensation control unit executes the compensation process for the user when the winning vote is not included in the voting information and the voting is not correct because a predetermined event occurs for the athlete corresponding to the designated athlete information, and does not execute the compensation process for the user when the winning vote is included in the voting information and the voting is not correct because a predetermined event occurs for the athlete corresponding to the designated athlete information. 2. The information processing device according to claim 1. According to the information processing device described above, when a user purchases betting tickets for a specified race, if all of the betting tickets are lost (this may include races without accidents), including tickets that were lost due to an accident, compensation for falling off the bike can be provided, thereby reducing the mental shock of the user who has lost all of their betting tickets.

[0205] Issues corresponding to [Appendix 19] One of the purposes of the present invention is to alleviate the anxiety of users who may lose their vote due to an accident involving the betting target specified according to the betting method they have chosen, thereby reducing the decrease in users' motivation to vote. [Appendix 19] The processor receives, from a user, designated athletic body information that identifies the designated athletic body according to a betting method in a predetermined competition in which a plurality of athletic bodies compete for finishing order, and betting information that specifies a betting amount; a processor that, when the competition is established and the bet is not successful due to a predetermined event occurring in the competition body corresponding to the designated competition body information, refunds at least a portion of the bet amount to the user as compensation; A program that executes a process. According to the above program, it is possible to ease the anxiety of the user when the bet is lost due to an accident with the betting target specified according to the betting type, and to reduce the decrease in the user's motivation to vote.

[0206] Issues corresponding to [Appendix 20] One of the purposes of the present invention is to alleviate the anxiety of users who may lose their vote due to an accident involving the betting target specified according to the betting method they have chosen, thereby reducing the decrease in users' motivation to vote. [Supplementary Note 20] The processor receives, from a user, designated athletic body information that identifies the designated athletic body according to a betting method in a predetermined competition in which a plurality of athletic bodies compete for finishing order, and betting information that specifies a betting amount; If the competition is successful and the bet is not successful due to a predetermined event occurring in the competition body corresponding to the designated competition body information, the processor refunds at least a portion of the bet amount to the user as compensation. Information processing methods. According to the above information processing method, it is possible to ease the anxiety of the user caused by losing a bet due to an accident with the betting target specified according to the betting type, and to reduce the decrease in the user's motivation to vote.

[0207] Issues corresponding to [Appendix 21] One of the purposes of the present invention is to alleviate the anxiety of users who may lose their vote due to an accident involving the betting target specified according to the betting method they have chosen, thereby reducing the decrease in users' motivation to vote. [Appendix 21] A server and a terminal device are provided, The server Accepting designated athletic body information, which identifies the designated athletic body in accordance with a betting method for a predetermined competition in which a plurality of athletic bodies compete for finishing order, and betting information, which specifies a betting amount, from the user's terminal device; If the competition is successful and the bet is not successful due to a predetermined event occurring in the competition body corresponding to the designated competition body information, at least a portion of the bet amount will be refunded to the user as compensation. Information processing system. According to the above information processing system, it is possible to ease the anxiety of the user caused by losing the bet due to an accident with the betting target specified according to the betting type, and to reduce the decrease in the user's motivation to vote. [Explanation of symbols]

[0208] 1. Information processing equipment 2. Reception 3 Compensation control section 11 Voting Ticket Purchase System 12 User terminal 15 Management Server 16 External Servers 17. Communication Networks 41 Communications Department 42 Control Unit 43 Acquisition Department 44 Payment processing section 45 Dividend Processing Section 46 Registration Department 47 Compensation Processing Unit 48 Dividend Processing Section 49 Special Offer Department 50 Voting Results Registration Department 51 Storage section 52 User Management DB 53 Voting management DB 53 Voting history DB 55 Race Management DB 56 Race results management DB 57 Accident Management DB 58 Compensation management DB 59 Weather History DB

Claims

1. a receiving unit that receives, from a user, designated athletic body information that identifies the designated athletic body according to a betting method for a predetermined athletic body in which a plurality of athletic bodies compete for finishing order, and betting information that specifies a betting amount; a compensation control unit that executes a compensation process to refund at least a portion of the bet amount to the user as compensation if the competition is successful and the bet is not successful due to a predetermined event occurring in the competition body corresponding to the designated competition body information; An information processing device comprising:

2. When the first user's betting is not successful because the predetermined event has occurred for the sporting object corresponding to the designated sporting object information a predetermined number of times or more, the compensation control unit notifies the first user that compensation will be provided when the first user's betting is not successful because the predetermined event has occurred. The information processing device according to claim 1 .

3. When the first user has not voted for a predetermined period of time, the compensation control unit notifies the first user that compensation will be provided if the vote is not successful due to the occurrence of the predetermined event. The information processing device according to claim 2 .

4. The compensation control unit executes the compensation process for the second user when the second user designates the voting amount equal to or greater than a predetermined amount. The information processing device according to claim 1 .

5. The compensation control unit executes the compensation process for the second user when the second user has designated a cumulative voting amount equal to or greater than a predetermined amount within a predetermined period. The information processing device according to claim 4 .

6. The compensation control unit executes the compensation process for the second user when the second user has designated the betting amount for the first competition as being equal to or greater than a predetermined amount. The information processing device according to claim 4 .

7. The compensation control unit executes the compensation process for the second user when the second user designates the betting amount equal to or greater than a predetermined amount for the designated competition item information corresponding to a betting type in a first competition. The information processing device according to claim 4 .

8. The compensation control unit executes the compensation process in a third competition to be held in a third period after the second period when the holding status of the second competition in which the predetermined event occurred satisfies a predetermined condition during the second period. The information processing device according to claim 1 .

9. The compensation control unit executes the compensation process for the competition in which the predetermined event is likely to occur, determined based on pre-registered weather history information of the venue on the past dates of the competition, the number of occurrences of the predetermined event, and weather forecast information of the venue on the current day of the competition. The information processing device according to claim 1 .

10. The compensation control unit determines the conditions for executing the compensation process or the amount of the compensation based on the history of the user's past voting information. The information processing device according to claim 1 .

11. The history of the past voting information is a first number of times that the voting was not successful due to the occurrence of the predetermined event for the athlete corresponding to the designated athlete information, The compensation control unit reduces the condition or increases the amount of the compensation for a user whose first number of times is more than the predetermined number of times, compared to a user whose first number of times is less than the predetermined number of times. The information processing device according to claim 10.

12. The compensation control unit determines a condition for executing the compensation process or a content of the compensation process based on the number of times the voting information has been received from the user or the voting amount. The information processing device according to claim 10.

13. the receiving unit receives, from the user, the voting information and compensation presence / absence information indicating whether or not compensation is to be provided; The compensation control unit executes the compensation process for the user when the received compensation presence / absence information indicates that the compensation is to be provided. The information processing device according to claim 1 .

14. The compensation control unit inquires of the user whether or not to provide the compensation based on history information regarding the predetermined event for each of the players. The information processing device according to claim 13.

15. the receiving unit receives, from the user, compensation presence / absence information indicating whether or not compensation is to be provided at a predetermined amount for a first unit period; The compensation control unit executes the compensation process for the user when the received compensation presence / absence information indicates that the compensation is to be provided. The information processing device according to claim 1 .

16. the compensation control unit executes the compensation process a first number of times in the first unit period, When the compensation process is executed the first number of times before the end of the first unit period, the reception unit receives, before the end of the first unit period, second compensation presence / absence information indicating whether or not the compensation is to be provided up to a second number of times in a second unit period. The information processing device according to claim 15.

17. When the received compensation presence / absence information indicates that the compensation for the second unit period is not provided, the compensation control unit determines the competition to be compensated for the first unit period after the expiration of the first unit period. The information processing device according to claim 16.

18. the compensation control unit executes the compensation process for the user if the voting information does not include the winning vote and the voting is not correct because a predetermined event has occurred for the sports body corresponding to the designated sports body information, and does not execute the compensation process for the user if the voting information includes the winning vote and the voting is not correct because a predetermined event has occurred for the sports body corresponding to the designated sports body information; The information processing device according to claim 1 .

19. a processor receiving, from a user, designated athletic body information that identifies the designated athletic body according to a betting method for a predetermined athletic body in which a plurality of athletic bodies compete for finishing order, and betting information that specifies a betting amount; a processor that, when the competition is established and the bet is not successful due to a predetermined event occurring in the competition body corresponding to the designated competition body information, refunds at least a portion of the bet amount to the user as compensation; A program that executes a process.

20. The processor receives, from the user, designated athletic body information that identifies the designated athletic body according to a betting method for a predetermined athletic body in which a plurality of athletic bodies compete for finishing order, and betting information that specifies a betting amount; If the competition is successful and the bet is not successful due to a predetermined event occurring in the competition body corresponding to the designated competition body information, the processor refunds at least a portion of the bet amount to the user as compensation. Information processing methods.

21. A server and a terminal device are provided, The server Accepting designated athletic body information, which identifies the designated athletic body in accordance with a betting method for a predetermined competition in which a plurality of athletic bodies compete for finishing order, and betting information, which specifies a betting amount, from the user's terminal device; If the competition is successful and the bet is not successful due to a predetermined event occurring in the competition body corresponding to the designated competition body information, at least a portion of the bet amount will be refunded to the user as compensation. Information processing system.

Images