JP2010250563A - Apparatus, method and program for supporting betting - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technique for suitably supporting the purchase of betting tickets in public-managed racing. <P>SOLUTION: A betting support apparatus includes: a condition acquisition means for respectively acquiring respective pieces of information concerned with a target collection amount and an investment amount as betting conditions of betting tickets in public-managed racing; an expected value acquisition means for respectively acquiring expected values for respective betting targets of the betting tickets; and a selection means for selecting a plurality of betting targets to be selected in the descending order of the expected values and of which the total amount of respective purchase amounts does not exceed the investment amount from betting targets to be purchase targets in accordance with the purchase amounts of respective betting targets which are determined so that the expected wining amount of the betting targets exceeds the target collection amount as recommended betting targets. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technique for supporting purchase of a voting ticket.

  Currently, there are voting systems that can purchase voting tickets for public competitions such as horse racing and boat racing from a mobile phone or a personal computer at home (hereinafter referred to as a PC). Through this voting system, the user selects a desired voting type from among a plurality of voting types such as a single winning type, a double winning type, a single winning single type, a continuous winning double type, etc., and a voting target corresponding to the selected voting type and Decide the purchase amount and purchase the desired voting ticket. In addition, the voting system provides information useful to the user when purchasing a voting ticket, such as odds corresponding to a ratio of a refund amount with respect to a purchase amount, race information, and the like.

  By the way, when the voting target (also referred to as “buying eye”) is a combination of a plurality of numbers, the number of voting tickets purchased increases according to the selected voting type. For example, when a user selects a vote type of a three consecutive winning single and wants to purchase four numbers of candidates for voting in all combinations of the three consecutive winning singles, there are 24 voting targets. However, the voting ticket purchase time increases as the number of voting objects increases.

  In order to deal with such a problem, a plurality of purchasing methods such as a sink, a multi, a box, and a formation are provided. For example, the sink method is a purchase method in which an axis number and a partner number are designated. Here, the number specified for the axis is a number that must be selected for voting, and the number specified for the other party is one or more of the specified numbers. A number selected for voting. The above-described voting system supports such a plurality of purchase methods, so that even when a vote target is determined as a combination of a plurality of numbers, a user can easily purchase a voting ticket.

  In addition, although there is no function to actually purchase a voting ticket, a voting application that supports the determination of a user's purchased voting ticket using information that is useful to the user when purchasing the voting ticket, and prediction of voting contents to multiple users There is also a user participation type voting prediction system that registers and competes for the result.

JP 2004-62295 A

  As described above, the system related to the conventional public competition provides a variety of information to support the user's determination of the purchase voting ticket, so that the purchase time of the voting ticket is not excessive. Provide a method.

  However, the support provided by such a conventional system is not based on information actually considered by the user when purchasing a voting ticket. For example, when a user purchases a voting ticket for a race, the user considers the investment amount spent in the race and the target amount to be paid back after the race (that is, the target collection amount for each race), Determine the purchase price.

  However, the conventional system has not been provided with a service that takes into account the balance of payment for each race to be purchased.

  In addition, as described above, when the user determines the purchase amount of each voting target to be a different amount in consideration of the balance, the user has to perform a purchase procedure for each voting ticket. In other words, the conventional system supports a plurality of purchase methods, but cannot set different purchase amounts for each voting target. Specifically, when four numbers determined as voting targets are purchased in a three-game winning single box method, the conventional system can set only one purchase price for each of the 24 voting targets. .

  In view of such problems, an object of the present invention is to provide a technology that appropriately supports the purchase of a voting ticket in a public competition.

  In the aspect of the present invention, the following configurations are employed in order to solve the above-described problems.

  The first mode is a condition acquisition means for acquiring each information regarding the target collection amount and the investment amount as voting conditions for voting tickets in public competitions, and an expected value acquisition for acquiring each expected value for each voting target of the voting ticket. And a plurality of voting targets that can be purchased according to the purchase amount of each voting target determined so that the scheduled winning amount of the voting target exceeds the target collection amount. And a selection means for selecting a plurality of voting targets whose total purchase amount does not exceed the investment amount as recommended voting targets.

  Here, the target collection amount means the target amount of the amount to be refunded when the voting ticket is won, and the investment amount means the total amount spent for voting ticket purchase. These target recovery amount and investment amount are set by the user, for example. In addition, the voting target of the voting ticket is also called a buying eye, and a voting type such as a winning type, a winning type, a winning type, a winning type, a winning combination, and a voting element corresponding to the voting type (for example, one frame number) , Horse number combinations, etc.). The planned winning amount is the amount that is scheduled to be refunded when the vote target (buying item) is won.

  In the first aspect, each information regarding the target collection amount and investment amount desired by the user and the expected value for each voting target are acquired, and based on these information, a recommended voting target including a plurality of voting targets is selected. Is done. Here, the plurality of voting targets selected as the recommended voting targets have a combination in which the total amount of each purchase does not exceed the investment amount desired by the user, and the planned winning amount of each voting target is determined by the user. The purchase amount is determined so as to exceed the desired target collection amount.

  Therefore, the recommended voting target selected above corresponds to the information actually considered by the user when purchasing the voting ticket, that is, the investment amount to be spent and the target recovery amount to be refunded. It becomes an object of voting appropriate for users who want to make an investment and determine a target amount of dividend when winning (successful). Therefore, such a recommended voting target becomes meaningful information for a user who is considering buying a voting ticket in a public competition. According to the first aspect, by providing the recommended voting target to a user, voting in a public competition is possible. Appropriate support for ticket purchases.

  In addition, the plurality of voting objects selected as the recommended voting objects are selected in descending order of the likelihood of winning.

Therefore, according to the first aspect, since the voting target that is expected to have a high expected value is selected in consideration of the unique prediction information, the user is provided with effective support in determining the voting ticket to be purchased. be able to.

  As a more specific aspect of the first aspect, the voting support apparatus outputs a display instruction for displaying a plurality of voting objects selected as the recommended voting objects together with respective purchase amounts in descending order of expected value. Display control means, and purchase control means for transmitting a request to purchase a voting ticket equivalent to the purchase amount to a voting ticket selected by a user among a plurality of voting objects displayed on the screen to a voting ticket purchasing system, You may make it provide further.

  According to this specific aspect, the user can know the voting target having a high expected value expected at a glance by referring to the screen. Such an aspect is effective support in determining a betting ticket to be purchased, particularly for a user who is a beginner of horse racing, a user who does not intend to predict himself or a user who simply wants to enjoy horse racing as an investment, and the like.

  In addition, according to the specific aspect, even if different purchase amounts are determined for a plurality of voting targets, a request for purchasing a voting ticket for the purchase amount for the selected voting target is issued by the voting ticket purchase system. Therefore, the user can easily purchase the plurality of voting tickets.

  As a more specific aspect of the first aspect, the condition acquisition means wants to include either one of a number that is not desired to be included in the voting target or a number that may be included in the voting target, and the voting target. A voting target that further acquires at least one of the number as a voting condition for the voting ticket, and that the selection means matches at least one voting condition that the number that the voting target should always include and the number that the voting target should not include May be extracted as a vote target that can be the purchase target.

  According to this aspect, a voting target that more specifically reflects the user's wishes can be set as a recommended voting target.

  Note that another aspect of the present invention may be a method for realizing any of the above configurations, a program, or a computer-readable storage medium that records such a program. There may be.

  ADVANTAGE OF THE INVENTION According to this invention, the technique which supports appropriately the voting ticket purchase in a public competition can be provided.

The figure which shows the whole structure of the betting ticket investment assistance system in Example 1 and the system relevant to this. 1 is a conceptual diagram illustrating a configuration of a support server 13 in Embodiment 1. FIG. The figure which shows the example of a race information table. The figure which shows the example of an anticipation table. The figure which shows the example of the screen controlled by the screen control part. 6 is a sequence chart showing an operation example of the betting ticket investment support system in the first embodiment. 5 is a flowchart illustrating recommended betting ticket determination processing of the support server in the first embodiment. The figure which shows the example of the recommended betting ticket determination process of the assistance server in Example 1. FIG.

  Hereinafter, a betting ticket investment support system as a form for carrying out the present invention will be described with specific examples. The betting ticket investment support system according to the present embodiment uses a winning horse voting ticket (hereinafter referred to as a betting ticket) for horse racing as a voting ticket for a public competition. However, since the present invention does not limit the target of investment support, it is a system in which each voting ticket for public competitions other than horse racing such as boat racing, bicycle racing, auto racing, motor boat racing, etc. is targeted for investment support. Also good. Further, the present invention may be applied to a computer game that realizes the above public competition in a pseudo manner. Each Example given below is an illustration, respectively, and this invention is not limited to the structure of each following Example.

  Hereinafter, Example 1 of the betting ticket investment support system as an embodiment will be described.

〔System configuration〕
The system configuration of the betting ticket investment support system in the first embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating an entire configuration of a betting ticket investment support system and a system related thereto in the first embodiment. The betting ticket investment support system 10 according to the first embodiment is connected to the race information system 3, the betting ticket purchase system 5, a plurality of user terminals 9, and the like via the network 1. The network 1 may be a public network such as the Internet or an in-house network such as a LAN (Local Area Network) or a WAN (Wide Area Network). The present invention does not limit such a network 1, nor does it limit the protocol that flows on the network 1.

  The race information system 3 holds race information generated by horse racing organizers such as the Japan Central Horse Racing Association (JRA) and the National Horse Racing Association (NAR), and provides the race information via the network 1. The race information includes a race number, a race name, run table information, odds information, and the like. The start table information includes information such as start horse information, frame number, and horse number for each race. Odds means the ratio of the refund to the purchase price of the betting ticket.

  The betting ticket purchase system 5 is a system for purchasing betting tickets online in response to a request from a user who has a contract with a horse race organizer, and is, for example, an IPAT (registered trademark) system. The betting ticket purchase system 5 acquires purchased betting ticket information including a voting target and the purchase price, and purchases the betting ticket indicated by the purchased betting ticket information. The betting ticket purchase system 5 determines the refund amount of the winning betting ticket according to the race result, and withdraws the necessary amount from the bank account of the purchaser user according to the total balance for a predetermined period, or is necessary for the bank account The correct amount.

  Since the present invention does not limit the configurations of the race information system 3 and the betting ticket purchase system 5 as described above, both may be configured as one system, and are provided by a plurality of horse race organizers. Two or more systems may be configured.

  The user terminal 9 is, for example, a PC or a mobile phone. The user terminal 9 has a general communication function capable of accessing the betting ticket investment support system 10 and receiving data, a general user interface function capable of displaying and operating a screen based on the provided data, and the like. The present invention does not limit the hardware configuration and functional configuration of the user terminal 9.

In the first embodiment, it is assumed that the WEB system is used as an interface between the user terminal 9 and the betting ticket investment support system 10. That is, the user using the user terminal 9 browses information provided from the betting ticket investment support system 10 by accessing the betting ticket investment support system 10 using a WEB browser. Further, the user operates the screen displayed on the WEB browser using a user interface connected to the user terminal 9 to send some information to the betting ticket investment support system 10.

  The betting ticket investment support system 10 according to the first embodiment provides a user who purchases a betting ticket with information regarding a recommended betting ticket that matches the betting ticket purchase condition input by the user and is expected to have a high expected value. The betting ticket investment support system 10 includes a support server 13, a win rate generation server 15, and the like. The support server 13 is connected to the network 1 and communicates with the race information system 3 and the betting ticket purchase system 5 via the network 1. The support server 13 operates as a WEB server and communicates with the user terminal 9 as a WEB client via the network 1. The winning percentage generation server 15 and the support server 13 may or may not be connected via a network such as a LAN.

〔Device configuration〕
Hereinafter, each apparatus structure of the support server 13 and the winning percentage generation server 15 which comprise the betting ticket investment support system 10 in Example 1 is demonstrated, respectively.

<Win rate generation server>
The win rate generation server 15 is realized by a general-purpose computer such as a PC or a dedicated computer, and has an input device such as a mouse and a keyboard, a display device such as a display, and the like as a user interface.

  The winning percentage generation server 15 generates winning percentage data for each vote using race information or the like. Here, the voting target is also called a buy eye and is a unit to which odds are attached. Hereinafter, the betting object will be described using a betting ticket as an example.

  The voting target includes different voting elements depending on the voting type. The voting types include horse number wins, double wins, frame number wins, singles, frame numbers wins, doubles, horses wins, doubles, wide, horses wins 3 wins, horses wins 3 wins, etc. For example, since the horse number winning type is a type for assigning the number of the first horse, the vote object of the horse number winning type betting ticket is one horse number. The horse number 3 consecutive winning single is a type for hitting each of the first, second and third horses, so the betting object of the horse number three consecutive winning single is the number of the first horse, the number of the second horse, It is a combination of three horse numbers, the number of the third horse. For example, a horse number 3 consecutive winning single betting ticket in which the first horse number is 5, the second horse number is 1, and the third horse number is 12, is also expressed as “5-1-12”. The On the other hand, the horse number 3 consecutive winning compound type is a type for hitting the first, second and third horses without being restricted in the order of arrival, so one of the same three horse numbers as the horse number three consecutive winning single Even if it is a combination, it becomes a different type of betting ticket, and the odds are also different. About the voting object of a horse number 3 consecutive winning double type | formula, it describes with "1-5-12" in order with a small number, for example.

  The win rate generation server 15 generates win rate data for all voting targets that can be purchased in each race. The winning percentage generation server 15 generates each winning percentage data based on, for example, horse weight, jockey information included in the race information, the racetrack where the race is performed, the racetrack state of the racetrack, and the like. Each winning percentage data is data indicating the high predictability of each voting object winning. The win rate generation server 15 collects necessary data at a predetermined cycle or at an arbitrary timing, and sequentially updates the win rate data of each voting target until the betting ticket purchase deadline.

<Support server>
FIG. 2 is a conceptual diagram illustrating a configuration of the support server 13 according to the first embodiment.

As illustrated in FIG. 2, the support server 13 includes a control unit 21, a storage unit 22, a communication unit 28, and the like that are connected by a bus 25 as a hardware configuration. The storage unit 22 is a hard disk, for example, and stores various types of information used in processing executed by the control unit 21. The control unit 21 includes one or a plurality of processors such as a CPU (Central Processing Unit), peripheral circuits (ROM (Read Only Memory), RAM (Radom Access) used for processing of the processors.
Memory), interface circuit, and the like. The communication unit 28 is connected to the network 1 and transmits and receives IP (Internet Protocol) packets and the like. The support server 13 may be constructed by a general-purpose computer such as a PC or a dedicated computer. The present invention does not limit the hardware configuration of the support server 13.

  The support server 13 implements each processing unit shown in FIG. 2 by executing the application program stored in the storage unit 22 by the control unit 21. As such a processing unit, the support server 13 includes a race information collection unit 31, a win rate data collection unit 32, a prediction data generation unit 33, a recommended betting ticket determination unit 34, a screen control unit 35, a purchase processing unit 36, and the like. As a database referred to by these processing units, the storage unit 22 stores a race information table 37 and a prediction table 38. Hereinafter, each processing unit of the support server 13 will be described.

  The race information collection unit 31 acquires race information provided by the race information system 3 by communicating with the race information system 3 via the communication unit 28. The race information collection unit 31 may acquire the race information at a predetermined cycle, or may detect the timing at which the race information is updated and acquire the race information at that timing. The race information collection unit 31 stores the acquired race information in the race information table 37 and the prediction table 38, respectively.

  FIG. 3 is a diagram illustrating an example of a race information table. The race information collection unit 31 stores the race ID, race name, frame number, horse number, and the like included in the race information in the race information table 37. The race ID is composed of data that can identify, for example, an organizer, a date, a racetrack to be held, a race number, and the like.

  FIG. 4 is a diagram illustrating an example of the prediction table. In the prediction table 38, a record is formed for each voting target of each race, and each record includes a race ID, a voting type (type of FIG. 4), a voting target (buying eye), odds, win rate, and expected value. Each data is stored separately.

  The race information collection unit 31 determines all votes for each race based on the race number, frame number, and horse number included in the race information, and generates a record in the prediction table 38. Furthermore, the race information collection unit 31 sets each odds information included in the race information in the odds field of the generated record. When the acquired race information includes the horse number for canceling the race, the race information collecting unit 31 deletes the record to be voted including the horse number in the prediction table 38. Further, since the odds information is continuously updated until the betting ticket purchase time limit, the race information collection unit 31 sequentially updates the prediction table 38 for the acquired odds information.

  The winning percentage data collection unit 32 acquires the winning percentage data generated by the winning percentage generation server 15 and stores it in the prediction table 38. The win rate data may be acquired from the win rate generation server 15 by a portable storage medium such as a floppy disk (registered trademark) or a USB (Universal Serial Bus) memory, or may be acquired via a network. When the winning percentage data is updated by the winning percentage generation server 15, the winning percentage data collecting unit 32 sequentially acquires the winning percentage data and reflects it in the prediction table 38.

As described above, when the odds information and the winning percentage data are stored in each record of the prediction table 38, the predicted data generation unit 33 multiplies the odds information and the winning percentage data for each record (voting target) to obtain each expected value. Are calculated respectively. The prediction data generation unit 33 stores the calculated expected value in the prediction table 38. The odds are values corresponding to the popularity of the vote target (ratio of the vote count of the vote target to the total vote count). Therefore, the expected value calculated by the predicted data generation unit 33 is a value in which the popularity of each voting target by other users is added to the winning rate based on the unique prediction by the winning rate generation server 15. The prediction data generation unit 33 updates the expected value at the timing when the odds information is updated by the race information collection unit 31 and at the timing when the winning rate data collection unit 32 updates the winning rate data.

  The recommended betting ticket determination unit 34 receives the betting ticket purchase condition input by the user on the screen controlled by the screen control unit 35, and determines a recommended betting ticket that matches the betting ticket purchase condition and is expected to have a high expected value. The betting ticket purchase conditions include a narrowing condition, an investment amount, a target collection amount, a betting ticket type, and the like. Here, the investment amount is the upper limit of the total purchase amount of all the betting tickets of the target race. The target collection amount is a lower limit of the target amount of the collection amount of the target race, and indicates that the user desires to purchase a betting ticket that is equal to or more than this amount as a refund when winning.

  The narrowing-down conditions included in the betting ticket purchase conditions include predetermined conditions that the user wants to limit the voting target, such as an axis number and a target number. This narrowing condition may not be set, or a further condition may be set. Here, the axis number is a horse number or a frame number that the user always wants to select for voting, and a frame number when a type related to a frame number, such as a frame number consecutive win, is selected as the betting ticket type. Is specified, and the horse number is specified when the type related to the horse number such as the horse number winning streak is selected as the betting ticket type. The target number is a horse number or a frame number that may be included in the voting target for the user, and if a type related to a frame number such as a frame number consecutive win is selected as the betting ticket type, the frame number is If a type related to a horse number such as a horse number winning streak is selected as the betting ticket type, the horse number is specified. It should be noted that a non-target number may be designated as a narrowing condition. This non-target number is a horse number or a frame number that the user does not want to select for voting, and if a type related to a frame number such as a frame number consecutive win is selected as the betting ticket type, the frame number is If a type related to a horse number such as a horse number winning streak is selected as the betting ticket type, the horse number may be specified.

  When such a betting ticket purchase condition is acquired, the recommended betting ticket determination unit 34 selects a voting target that matches the narrowing-down condition and the betting ticket type included in the betting ticket purchase condition from all the voting targets stored in the prediction table 38. The recommended betting ticket determination unit 34 sorts the voting targets extracted according to the narrowing-down condition and the betting ticket type in the descending order of the expected value data, and determines the purchase amount of the voting target in order from the voting target having the highest expected value. At this time, the recommended betting ticket determination unit 34 determines the purchase amount of each voting target so that when the odds for each voting target are multiplied, the refund amount is equal to or greater than the target collection amount included in the betting ticket purchase condition.

  The recommended betting ticket determination unit 34 determines the voting target purchase price in order from the voting target having the highest expected value in this way, and creates a voting target list in which the total purchase price is within the investment amount included in the betting ticket purchase conditions. Extract. The recommended betting ticket determination unit 34 sends the list including the voting target extracted as described above and the purchase price thereof to the screen control unit 35 as a recommended betting ticket.

  The screen control unit 35 transmits a predetermined WEB page via the communication unit 28 in response to access from the user terminal 9. FIG. 5 is a diagram illustrating an example of a screen controlled by the screen control unit 35. A race selection screen 51, a betting ticket purchase condition setting screen 52, a recommended betting ticket display screen 60, and the like shown in FIG. 5 are displayed on the display of the user terminal 9 by the WEB page transmitted by the screen control unit 35.

The race selection screen 51 is a screen for allowing the user to select a race to be purchased. The screen control unit 35 uses the information stored in the race information table 37 to generate a WEB page for forming the race selection screen 51. When a plurality of horse racing organizers are supported, information that allows selection of the organizers may be displayed.

  The betting ticket purchase condition setting screen 52 is a screen for allowing the user to set betting ticket purchase conditions. On the betting ticket purchase condition setting screen 52, an input box for inputting each of the above conditions is displayed. The input box 53 is an area for inputting an axis number. The input box 54 is an area for inputting a target number. The input box 55 is an area for inputting an investment amount. The input box 56 is an area for inputting a target collection amount. The input box 57 is an area for inputting a betting ticket type.

  In the user terminal 9, after each condition is set in each input box of the betting ticket purchase condition setting screen 52, when the determination button 58 is selected, each condition data input in each input box is supported from the user terminal 9. It is transmitted to the server 13. The screen control unit 35 receives the condition data and sends them to the recommended betting ticket determination unit 34 as betting ticket purchase condition data.

  The recommended betting ticket display screen 60 is a screen that displays a list of recommended betting tickets determined by the recommended betting ticket determination unit 34 in descending order of the expected value of the vote target. On the recommended betting ticket display screen 60, information 61 for specifying a race, betting ticket type 62, voting target 63, purchase amount 64, odds 65, expected refund 66, and the like are displayed. The expected refund 66 is an amount obtained by multiplying the purchase amount 64 by the odds 65.

  Further, the recommended betting ticket display screen 60 displays a selection box 67 capable of selecting any of the recommended betting ticket lists. When the user terminal 9 selects a betting ticket selection box 67 on the recommended betting ticket display screen 60 and selects a purchase button 69, a purchase instruction including information indicating the recommended betting ticket is sent to the purchase processing unit 36. It is done.

  The purchase processing unit 36 requests the betting ticket purchasing system 5 to purchase the recommended betting ticket selected on the recommended betting ticket display screen 60 by performing predetermined communication with the betting ticket purchasing system 5 via the communication unit 28. The purchase processing unit 36 sends the result of this request to the screen control unit 35, thereby causing the user terminal 9 to display a screen for displaying the result.

[Operation example]
Hereinafter, an operation example of the betting ticket investment support system 10 according to the first embodiment will be described with reference to FIG. FIG. 6 is a sequence chart illustrating an operation example of the betting ticket investment support system according to the first embodiment.

  The support server 13 collects race information from the race information system 3 connected via the network 1 at a predetermined cycle or arbitrary timing (S101). At this time, the winning percentage generation server 15 also uses the race information and other necessary information to generate winning percentage data for all voting targets that can be purchased for each race. The support server 13 acquires win rate data generated by the win rate generating server 15 at a predetermined cycle or at an arbitrary timing (S102).

The support server 13 calculates the expected value by multiplying the odds included in the race information collected from the race information system 3 and the winning percentage data acquired from the winning percentage generating server 15 (S103). The support server 13 stores the race information collected from the race information system 3, the winning rate data acquired from the winning rate generation server 15, and the expected value data in the race information table 37 and the expected table 38 (S104). When the information regarding the race already stored in the race information table 37 and the prediction table 38 is acquired, the race information table 37 and the prediction are changed with the data changed from the already stored data among the acquired information. The table 38 is updated. At this time, when the winning percentage data or odds is changed, the support server 13 calculates an expected value by multiplying the winning percentage data and the odds, and stores the calculated expected value in the prediction table 38.

  In the case of an exception such as when a horse for canceling a run occurs or when a jockey changes, the race information already stored in the race information table 37 and the prediction table 38 is greatly changed. However, since the voting target such as the frame number and the horse number is not changed in the normal time, the race information that is sequentially changed in the normal time includes, for example, odds. Further, since the winning percentage data is updated according to the racetrack state or the like, it corresponds to data that is sequentially changed even during normal times. The support server 13 executes the processes (S101), (S102), (S103), and (S104) so as to hold such data that may be sequentially changed as much as possible.

  On the other hand, the user accesses the betting ticket investment support system 10 using the user terminal 9 at a desired timing (S111). This access is realized, for example, by inputting a URL (Uniform Resource Locator) of the betting ticket investment support system 10 into a WEB browser on the user terminal 9.

  The support server 13 generates a WEB page for forming a race selection screen in response to the access from the user terminal 9. This WEB page is generated using data stored in the race information table 37 held as described above. The generated WEB page is sent to the user terminal 9 so that a race selection screen (see screen 51 in FIG. 5) is displayed on the display of the user terminal 9.

  The user operates the user interface of the user terminal 9 to select a race to be purchased from among the races displayed on the race selection screen (S113). Thereby, the race number indicating the selected race is transmitted to the support server 13 (S114).

  When acquiring the race number, the support server 13 next transmits a WEB page for forming a betting ticket purchase condition setting screen to the user terminal 9. This WEB page is stored in the storage unit 22 in advance. By sending this WEB page to the user terminal 9, a betting ticket purchase condition setting screen (see screen 52 in FIG. 5) is displayed on the display of the user terminal 9.

  The user operates the user interface of the user terminal 9 to input desired betting ticket purchase conditions on the betting ticket purchase condition setting screen (S116). As betting ticket purchase conditions, a betting ticket type, an investment amount, a target collection amount, an axis number as a narrowing condition, a target number, and the like are input. Of the betting ticket purchase conditions, the narrowing conditions such as the axis number and the target number may not be input. When a desired betting ticket purchase condition is input on the betting ticket purchase condition setting screen and the determination button is pressed, the input betting ticket purchase condition is sent to the support server 13 (117).

  When receiving the betting ticket purchase condition, the support server 13 determines a recommended betting ticket using the betting ticket purchase condition and the already acquired race number (S118). The recommended betting ticket determined here includes the vote target and the purchase price. Details of the recommended betting ticket determination process will be described later. The support server 13 generates a WEB page for forming a recommended betting ticket display screen based on the recommended betting ticket information. By sending this WEB page to the user terminal 9, a recommended betting ticket display screen (see screen 60 in FIG. 5) is displayed on the display of the user terminal 9 (S119).

By referring to the recommended betting ticket display screen displayed on the display of the user terminal 9, the user can obtain a list of betting tickets including the voting targets and purchase amounts recommended by the betting ticket investment support system 10. Further, on the recommended betting ticket display screen, recommended betting tickets are displayed in a list in descending order of expected value of each vote target.

  Thereby, since the user can obtain the betting ticket information according to the investment amount and the target collection amount considered as the purchase condition, effective information that takes into account the balance of each race when actually purchasing the betting ticket is obtained. Obtainable.

  Furthermore, since the betting ticket information corresponding to the prediction (expected value) of the betting ticket investment support system 10 can be obtained, for a user who is a beginner of racing, a user who does not intend to predict himself or a user who simply wants to enjoy horse racing as an investment, etc. Information that can be used as a reference for purchasing betting tickets can be obtained. By referring to the recommended betting ticket display screen, such a user can know at a glance the betting ticket having a high expected value predicted by the betting ticket investment support system 10. Furthermore, in the betting ticket investment support system 10, since the popular vote target (low odds) is not necessarily recommended, it is possible to increase the enjoyment of investment for the user who considers purchasing betting tickets as an investment. .

  In addition to referring to the recommended betting ticket display screen, the user selects the betting ticket to be purchased from the recommended betting ticket list by operating the user interface of the user terminal 9 when actually purchasing the displayed recommended betting ticket. (S120). When a betting ticket desired to be purchased is selected on the recommended betting ticket display screen and the purchase button is pressed (S121), the selected betting ticket information is sent to the support server 13 (S122).

  Upon receiving the selected betting ticket information, the support server 13 sends a betting ticket purchase request including the betting ticket information to the betting ticket purchase system 5 (S123). Thereby, the requested betting ticket is actually purchased in the betting ticket purchase system 5, and a notification of completion thereof is sent to the support server 13 (S124). Eventually, the user can confirm the completion of the purchase on the user terminal 9.

  Thus, in the past, when it was desired to specify different purchase amounts for a plurality of voting targets, it was necessary to perform individual input operations for each voting target. According to the betting ticket purchase system 5, it is desired to purchase on the recommended betting ticket display screen. Simply select a betting ticket and press the purchase button to purchase.

  Next, the recommended betting ticket determination process of the support server 13 in the first embodiment will be described with reference to FIGS. FIG. 7 is a flowchart illustrating a recommended betting ticket determination process of the support server in the first embodiment. FIG. 8 is a diagram illustrating an example of recommended betting ticket determination processing of the support server in the first embodiment. Hereinafter, the flowchart shown in FIG. 7 will be described with reference to the data example of FIG.

The recommended betting ticket determination unit 34 of the support server 13 receives the target race input on the race selection screen and the betting ticket purchase conditions input on the betting ticket purchase condition setting screen (S200). Specifically, “2nd Nakayama 3rd Day 11R” is designated as the target race, and the betting ticket purchase conditions are “800 yen” for the investment amount, “3000 yen” for the target collection amount, ", The axis number of the narrowing condition is" 1 ", and the target numbers of the narrowing condition are" 2, 3, 4, 4 ".

The recommended betting ticket determination unit 34 extracts, from all the voting target records stored in the prediction table 38, the voting target record of the target race that matches the betting ticket type and includes the axis number and the target number (S201). ). Specifically, it is a voting target of “2nd Nakayama 3rd day 11R”, the betting ticket type is “horse number consecutive winning single”, includes horse number “1”, and horse number “2” , “No. 3”, “No. 4” and “No. 5” are extracted as records for all votes. Here, it is assumed that a record as indicated by reference numeral 81 in FIG. 8 is extracted. For example, when a non-target number is designated as the narrowing-down condition, a record to be voted including the designated number may be excluded.

The recommended betting ticket determination unit 34 sorts the voting target records extracted in this way in descending order of expected value (S202). According to the example of FIG. 8, the voting target “1” having the expected value “1.1422830”.
-2 ”record has the highest expected value, and thereafter, the voting target“ 1.0538028 ”has the expected value“
The voting target “1-5” having the expected value “0.9751707” and the voting target “1-3” having the expected value “0.7966880” are arranged in this order.

The recommended betting ticket determination unit 34 first selects a voting target record having the highest expected value (S203). Here, the record of the voting target “1-2” having the expected value “1.1422830” is selected. The recommended betting ticket determination unit 34 determines the purchase amount of the voting target “1-2” to be the minimum amount at which the payout amount at the time of winning is equal to or more than the target collection amount of the betting ticket purchase condition (S204). Specifically, the odds for the voting target “1-2” is “100.5” times, the target recovery amount is “3000 yen”, and the purchase unit amount is “100 yen” (this amount is determined in horse racing) Therefore, the purchase price is determined to be “100 yen”. As a result, the expected refund amount is 10050 yen, which is the purchase amount "100 yen" multiplied by the odds "100.5" times, so the target recovery amount is "3000 yen" or more.

The recommended betting ticket determination unit 34 calculates the total purchase amount and determines whether or not the total amount is equal to or less than the investment amount of the betting ticket purchase condition (S205). Here, only the purchase price of the voting target with the highest expectation value is determined, so the total purchase price is 100 yen. Therefore,
The recommended betting ticket determination unit 34 determines that the total purchase amount “100 yen” is equal to or less than the investment amount “800 yen” (S205; YES), and determines from the selected vote target with the highest expected value and the purchase amount. Is included in the recommended betting ticket list (S206). That is, the betting ticket of the purchase amount “100 yen” of the voting target “1-2” of the horse number consecutive winning single is set in the recommended betting ticket list.

The recommended betting ticket determination unit 34 determines whether there is a voting target record having the next highest expected value among the sorted voting target records (S207). If the recommended betting ticket determination unit 34 determines that there is a next voting target record with the highest expected value (S207; YES), the voting target record with the next highest expected value among the sorted voting target records. Is selected (S208). Here, the vote target “1-4” having the expected value “1.0538028” is selected as the vote target record having the next highest expected value.

The recommended betting ticket determination unit 34 determines the purchase price of the selected vote target in the same manner as described above (S204). That is, since the odds of the voting target “1-4” is “20.1” times and the target collection amount is “3000 yen”, the purchase amount is determined to be “200 yen”. As a result, the estimated refund amount is “4020 yen” obtained by multiplying the purchase amount “200 yen” by the odds “20.1” times, and thus the target recovery amount is “3000 yen” or more.

Subsequently, in the same manner as described above, the recommended betting ticket determination unit 34 calculates the total of the purchase amount and determines whether or not the total amount is equal to or less than the investment amount of the betting ticket purchase condition (S205). Here, since the total purchase amount is 300 yen (= 100 yen +200 yen), the recommended betting ticket determination unit 34 determines that the total purchase amount “300 yen” is equal to or less than the investment amount “800 yen”. (S205; YES), the betting ticket including the selected voting target “horse number consecutive winning single” “1-4” and the purchase amount “200 yen” is included in the recommended betting ticket list (S206).

The recommended betting ticket determination unit 34 further determines whether there is a voting target record having the next highest expected value (S207). Here, there is a voting target record with the next highest expected value (S
207; YES), the recommended betting ticket determination unit 34 selects the record of the voting target “1-5” having the expected value “0.9751707” as the voting target record having the next highest expected value (S208). The purchase amount to be voted is determined in the same manner as described above (S204). Here, since the odds of the voting target “1-5” is “6.3” times and the target recovery amount is “3000 yen”, the purchase amount is determined to be “500 yen”. As a result, the expected refund amount is 3150 yen, which is the purchase amount of "500 yen" multiplied by the odds of "6.3", so the target recovery amount is "3000 yen" or more.

  The recommended betting ticket determination unit 34 calculates the total purchase price again. Here, the recommended betting ticket determination unit 34 calculates “800 yen” (= 100 yen + 200 yen + 500 yen) as the total amount of purchase amount, and the total amount of purchase amount “800 yen” is equal to or less than the investment amount “800 yen”. (S205; YES). Thereby, the recommended betting ticket determination unit 34 includes the betting ticket including the selected voting target “horse number consecutive winning single” “1-5” and the purchase amount “500 yen” in the recommended betting ticket list (S206).

The recommended betting ticket determination unit 34 further determines whether there is a voting target record having the next highest expected value (S207). Here, since there is a voting target record with the next highest expected value (S207; YES), the recommended betting ticket determination unit 34 has the expected value “0.7966880” as the voting target record with the next highest expected value. The record “1-3” is selected (S208), and the purchase price of the selected voting target is determined in the same manner as described above (S204). Here, since the odds of the voting target “1-3” is “343.4” times and the target collection amount is “3000 yen”, the purchase amount is determined to be “100 yen”. As a result, the expected refund amount is 34340 yen obtained by multiplying the purchase amount "100 yen" by the odds "343.4", and thus the target recovery amount is "3000 yen" or more.

The recommended betting ticket determination unit 34 calculates the total purchase price again. Here, the recommended betting ticket determination unit 34 calculates “900 yen” (= 100 yen + 200 yen + 500 yen + 100 yen) as the total purchase amount, and the total purchase amount “900 yen” is the investment amount “800 yen. It is determined that it is not below (S205; NO). Thereby, the recommended betting ticket determination unit 34 ends the process without including the selected voting target “horse number consecutive winning single” “1-3” in the recommended betting ticket list. As a result, the recommended betting ticket list determined in this way is displayed on the recommended betting ticket display screen 60.

  In the example of FIG. 8, there is a record of the vote that has the next highest expected value until the total purchase amount exceeds the investment amount, but the next expected value before the total purchase amount exceeds the investment amount. If there is no voting target record with a high (S207; NO), the process is terminated there.

[Modification]
In the first embodiment described above, an example in which the betting ticket purchase condition is set for each race is shown, but the betting ticket purchase condition may be set for a plurality of races desired by the user. In this case, the screen control unit 35 may generate the WEB page so that a plurality of races can be selected on the race selection screen 51 shown in FIG. 5, or the betting ticket purchase condition setting screen shown in FIG. In 52, the screen control unit 35 may generate the WEB page so that the purchase target race can be conditionally set.

In this case, the investment amount input on the betting ticket purchase condition setting screen 52 is regarded as the total investment amount of a plurality of races set as purchase targets, and the recommended betting ticket determination unit 34 uses the total investment amount as the number of races. The divided investment amount for each race may be determined, and the recommended betting ticket list may be determined in the same manner as in the first embodiment using the investment amount thus determined. As a result, the recommended betting ticket display screen 60 displays a recommended betting ticket list for a plurality of races. Note that such a modification example for a plurality of races is not limited to the above-described form, and may be realized as another aspect.

  In this way, a betting ticket can be determined by investing a plurality of races, so that further enjoyment can be provided to the user.

  In the first embodiment described above, an example in which one betting ticket type is set as a betting ticket purchase condition is shown, but a plurality of betting ticket types may be set. In this case, the recommended betting ticket determination unit 34 may extract the voting objects corresponding to the plurality of betting ticket types when extracting the voting objects from the prediction table 38.

  Further, in the above-described first embodiment, an example in which the purchase button 69 is displayed on the recommended betting ticket display screen 60 is shown, but the display of the purchase button 69 is switched according to the user who uses the user terminal 9. It may be. For example, when the support server 13 includes a user registration database and is accessed by a user, the purchase button is displayed on the recommended betting ticket display screen 60 only when the support server 13 stores data related to the user who accesses the user registration database. 69 may be displayed.

  Further, only the user data registered in the betting ticket purchase system 5 is stored in the user registration database, and the same user data (user ID, password) as the data registered in the betting ticket purchase system 5 is stored. Etc.) are stored. Then, when the purchase button 69 on the recommended betting ticket display screen 60 is pressed and a purchase request is transmitted to the betting ticket purchase system 5, the user data of the user is transmitted. Authentication can also be performed automatically.

  In this way, only the user who can actually purchase the betting ticket with the betting ticket purchasing system 5 is allowed to perform the purchasing operation, so that the user can perform a smooth operation.

1 network 3 race information system 5 betting ticket purchase system 9 user terminal 10 betting ticket investment support system 13 support server 15 win rate generation server 21 control unit 22 storage unit 28 communication unit 31 race information collection unit 32 win rate data collection unit 33 prediction data generation unit 34 Recommended betting ticket determination unit 35 Screen control unit 35
36 Purchase processing section 37 Race information table 38 Prediction table

Claims (5)

Condition acquisition means for acquiring each information on the target collection amount and investment amount as voting conditions for voting tickets in public competitions,
Expected value acquisition means for acquiring the expected value for each voting target of the voting ticket,
A plurality of voting targets that are selected in descending order of the expected value from among the voting targets that can be purchased according to the purchase amount of each voting target that is determined so that the scheduled winning amount for voting exceeds the target collection amount And a selection means for selecting a plurality of voting objects whose total purchase amount does not exceed the investment amount as a recommended voting object,
A voting support apparatus comprising: Display control means for outputting a display instruction of a screen for displaying a plurality of voting targets selected as the recommended voting targets together with respective purchase amounts in order of the expected value;
Purchase control means for transmitting a request to purchase a voting ticket corresponding to the purchase amount to a voting ticket selected by the user among a plurality of voting objects displayed on the screen;
The voting support apparatus according to claim 1, further comprising: The condition acquisition means further acquires at least one of a number that should be included in the voting target and a number that is not included in the voting target as voting conditions for the voting ticket,
The selection means meets at least one of the voting conditions of a number that is not desired to be included in the voting target and a number that may be included in the voting target, and a number that is necessarily included in the voting target. Extracting the voting object as a voting object that can be the purchase object,
The voting support apparatus according to claim 1 or 2, wherein Computer
Obtaining each information regarding the target collection amount and investment amount as voting conditions for voting tickets in public competitions,
Obtaining an expected value for each voting target of the voting ticket,
A plurality of voting targets that are selected in descending order of the expected value from among the voting targets that can be purchased according to the purchase amount of each voting target that is determined so that the scheduled winning amount for voting exceeds the target collection amount Selecting a plurality of voting targets whose total purchase amount does not exceed the investment amount as recommended voting targets;
Voting support method characterized by executing On the computer,
Obtaining each information regarding the target collection amount and investment amount as voting conditions for voting tickets in public competitions,
Obtaining each expected value indicating a high probability of winning expected for each voting target of the voting ticket;
A plurality of voting targets that are selected in descending order of the expected value from among the voting targets that can be purchased according to the purchase amount of each voting target that is determined so that the scheduled winning amount for voting exceeds the target collection amount Selecting a plurality of voting targets whose total purchase amount does not exceed the investment amount as recommended voting targets;
A voting support program characterized by having

Images