Information processing device, information processing method, and information processing program

Abstract

To provide an information processing device, an information processing method, and an information processing program that can meet diverse user needs regarding automatic purchase of betting tickets.SOLUTION: An information processing device comprises a competition acceptance unit, a purchase rule acceptance unit, and an automatic purchase unit. The competition acceptance unit accepts, from a user, designation of a competition for which betting tickets are to be purchased. The purchase rule acceptance unit accepts designation of betting ticket purchase rules for the designated competition. The automatic purchase unit automatically purchases betting tickets based on the purchase rules designated by the user within a prescribed time range before a closing due time when the purchase of betting tickets for the competition is closed. The purchase rules allow the user to select a betting type, and the user to designate a range of odds for the selected betting type.SELECTED DRAWING: Figure 7

Description

[Technical field]

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

[0002] In recent years, services have been provided that allow users to place bets on publicly managed races and other events via a communication network. Users of these services predict the outcome of the race and place bets by betting on their predictions, with a monetary or other value. The votes are accepted by the server computer of the service provider, and once the race results are finalized, a payout (refund) based on the winning bet is awarded to the user.

[0003] Patent document 1 describes a technology that enables members to automatically purchase betting tickets without having to repeatedly access the betting ticket vending device, and that enables repeated automatic purchases of betting tickets according to certain purchasing rules by setting purchasing rules. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2003-281313 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, the technology described in Patent Document 1 above has a problem in that there is still room for improvement in terms of meeting the diverse needs of users regarding automatic purchasing of betting tickets.

[0006] An object of the present invention is to provide an information processing device, an information processing method, and an information processing program that can meet various user needs regarding automatic purchasing of betting tickets. [Means for solving the problem]

[0007] The information processing device according to the present invention comprises: The system includes a competition reception unit, a purchase rule reception unit, and an automatic purchase unit, the competition acceptance unit accepts, from a user, a designation of a competition for which a betting ticket is to be purchased; the purchase rule acceptance unit accepts a designation of a purchase rule for a betting ticket for a designated event; the automatic purchasing unit automatically purchases betting tickets based on the purchasing rules designated by the user within a predetermined time range before a deadline at which purchase of betting tickets for the race is closed; The purchase rules allow the user to select a betting type and to specify a range of odds for the selected betting type. Effect of the Invention

[0008] According to the present invention, it is possible to meet a variety of user needs regarding automatic purchasing of betting tickets. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing a configuration of a voting system in this embodiment. [Diagram 2] 1 is an example of a home screen displayed on a display unit of a user terminal. [Diagram 3] 13 is an example of a race specification screen displayed on a display unit of a user terminal. [Figure 4] 13 is an example of a purchase rule specification screen displayed on a display unit of a user terminal. [Diagram 5] FIG. 2 is a block diagram showing a hardware configuration of a server according to the present embodiment. [Figure 6] FIG. 2 is a block diagram showing a hardware configuration of a user terminal in the present embodiment. [Figure 7] FIG. 2 is a block diagram illustrating an example of a functional configuration of a server according to the present embodiment. [Figure 8] 13 is an example of a notification screen displayed on a display unit of a user terminal. [Figure 9]13 is an example of a voting screen displayed on a display unit of a user terminal. [Figure 10] 13 is an example of a voting screen displayed on a display unit of a user terminal. [Figure 11] 13 is a flowchart showing an example of a voting process (automatic purchasing process) performed by the server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described with reference to the accompanying drawings, in which the same reference numerals denote the same or similar configurations.

[0011] (Configuration of Voting System 1) 1 shows the configuration of a voting system 1 according to this embodiment. The voting system 1 is a system for managing votes by users in various types of competitions in which betting is conducted, such as auto races, horse races, bicycle races, or boat races.

[0012] In this embodiment, the betting system 1 is used for auto racing, but the betting system 1 may be used for various competitions (not limited to public and private competitions) in which betting is performed, such as horse racing, boat racing, and bicycle racing, as well as auto racing. The betting system 1 may also be used for various competitions in which rankings are determined. The betting system 1 may also be used for simulation games for the various competitions mentioned above, and e-sports, which are computer games in which players compete against each other to win or lose.

[0013] As shown in FIG. 1, the voting system 1 includes a server 10 and multiple user terminals 20 (user terminal 20a, user terminal 20b, user terminal 20c, and user terminal 20d). The server 10 and the multiple user terminals 20 are connected to each other so as to be able to communicate with each other via a communication line 5 such as the Internet or a wireless LAN. The server 10 functions as an "information processing device" of the present invention. The user terminal 20 functions as a "terminal device" of the present invention.

[0014] In this embodiment, the users who use the user terminal 20a, the user terminal 20b, the user terminal 20c, and the user terminal 20d are referred to as user U1, user U2, user U3, and user U4, respectively. When there is no need to distinguish between the users U1, U2, U3, and U4, the users U1, U2, U3, and U4 are each referred to as user U.

[0015] Furthermore, when there is no need to distinguish between the user terminal 20a, the user terminal 20b, the user terminal 20c, and the user terminal 20d, the user terminal 20a, the user terminal 20b, the user terminal 20c, and the user terminal 20d will each be referred to as the user terminal 20.

[0016] The number of user terminals 20 included in the voting system 1 is not limited to four, but may be at least two or more user terminals 20.

[0017] The user terminal 20 is an information processing terminal such as a smartphone or a tablet terminal. The user terminal 20 may be any terminal such as a mobile phone, a personal computer (PC), a notebook PC, a personal digital assistant (PDA), a home game device, etc. The user terminal 20 may notify the server 10 of its own position detected using a global positioning system (GPS) or the like.

[0018] The server 10 may be composed of one device or may be composed of multiple devices. Furthermore, the server 10 may be a server realized on a cloud.

[0019] An overview of voting performed using the voting system 1 will be described with reference to Fig. 1. First, a user U operates a user terminal 20 to access a voting service provided by a server 10. Next, after accessing the server 10, the user U inputs information for uniquely identifying the user U (e.g., a user ID, a password, etc.) into the user terminal 20 in order to log in to the server 10. The input information is transmitted from the user terminal 20 to the server 10 via a communication line 5.

[0020] Next, the server 10 identifies the user U who is using the voting system 1 based on the information received from the user terminal 20. Next, the server 10 generates screen information including information for displaying the voting screen, and transmits it to the user terminal 20.

[0021] Next, the user terminal 20 displays a voting screen based on the screen information received from the server 10. The user U then casts a vote using the voting screen displayed on the user terminal 20. Here, the voting screen is a screen for the user U to cast a vote, and in the case of an auto race, for example, the voting screen displays options for betting methods (betting types) such as "Trifecta (car number trifecta type)", "Trifecta (car number trifecta type)", "Dual (car number bifecta type)", "Wide (expanded bifecta type)" and "Win (win type)", betting targets, and the number of bets or bet amounts of a predetermined value for the betting targets.

[0022] A trifecta is a ticket that predicts the 1st, 2nd, and 3rd place racers (corresponding to the "competitors" of this invention) based on their car numbers in the order of their finish, and hits the mark. A trifecta is a ticket that predicts the 1st to 3rd place racers based on their car numbers, regardless of their order of finish, and hits the mark. A diadem is a ticket that predicts the 1st and 2nd place racers based on their car numbers in the order of their finish, and hits the mark. A diadem is a ticket that predicts the 1st and 2nd place racers based on their car numbers, regardless of their order of finish, and hits the mark. A wide is a ticket that predicts two racers based on car numbers in the 1st to 3rd place racers, and hits the mark. A win is a ticket that predicts the 1st place racer based on car number, and hits the mark.

[0023] After predicting the outcome of a competition (a particular race), user U can use the voting screen to set the voting method, the betting items, and the number of bets or amount of bets of a specified value on the betting items, and then purchase a betting ticket (betting ticket) based on the set contents using a specified value, thereby voting on the outcome of the competition.

[0024] The predetermined value may be money, or may be points that can be used for a predetermined service or game, etc. Furthermore, the points may be points that the voter can receive free of charge (free points), or may be points that the voter can receive in exchange for payment of money (paid points).

[0025] When the user U has completed voting, the input voting information is transmitted from the user terminal 20 to the server 10 via the communication line 5. The server 10 then determines whether or not the user U's vote was correct based on the actual results of the race, and transmits determination result information indicating the result of the determination to the user terminal 20. The user terminal 20 then displays the determination result information received from the server 10.

[0026] The user U can check whether or not his / her bet is correct by referring to the judgment result information displayed on the user terminal 20. If the user U's bet is correct, he / she can receive a payout value (e.g., money or points) determined based on the amount of the predetermined value used for the bet and the payout rate of the bet (corresponding to the "odds" of the present invention).

[0027] The betting system 1 is equipped with an automatic purchase function (also called a "pre-purchase function") that automatically purchases betting tickets based on purchase rules specified by the user U. In the automatic purchase function, the user U specifies on the user terminal 20 the race for which the betting tickets are to be purchased and the purchase rules for the betting tickets for the specified race.

[0028] Purchase rule designation information indicating the designated purchase rule is transmitted from the user terminal 20 to the server 10 via the communication line 5. Based on the purchase rule designation information received from the user terminal 20, the server 10 automatically purchases betting tickets based on the purchase rule designated by the user U within a predetermined time range (for example, 2 to 3 minutes before) before the deadline when the purchase of betting tickets for the race included in the purchase rule designation information is closed. Here, automatically purchasing betting tickets means that the server 10 purchases betting tickets based on the purchase rule within a predetermined time range before the deadline when the purchase of betting tickets is closed, even if a purchase instruction is not issued by the user U. In addition, the purchase rule allows the user U to select a betting type and to specify a range of odds (dividend rate) for the selected betting type. This makes it possible for the voting system 1 to meet various user needs regarding the automatic purchase of betting tickets.

[0029] In the automatic purchase function, the user U may specify only the purchasing rules for the betting tickets without specifying the race for which the betting tickets are to be purchased. In this case, the server 10 determines whether or not there is a race that meets the purchasing rules specified by the user U, and if it determines that there is, automatically purchases betting tickets based on the purchasing rules specified by the user U within a predetermined time range before the deadline for the purchase of betting tickets for that race.

[0030] 2 is a diagram showing an example of a home screen displayed on the display unit 24 of the user terminal 20. The home screen is displayed at the start of a voting service after the user U logs in to the voting service provided by the server 10. Each screen described below is displayed based on screen display data transmitted from the server 10 to the user terminal 20.

[0031] 2, the home screen displays a voting button 40, a spectating button 42, an automatic purchase button 44, and the like. When the user U presses the voting button 40, a voting screen (not shown) is displayed on which the user U can set a voting method, a voting target, and a predetermined value of the number of bets or the bet amount on the voting target, and perform a regular vote based on the set contents, and the user U can perform the regular vote.

[0032] When the user U presses the watch button 42, a watch screen (not shown) for watching (viewing) the live-streamed competition video corresponding to the auto race (competition) specified by the user U is displayed, and the user U can watch the competition video. When the user U presses the automatic purchase button 44, a screen (see Figs. 3 and 4) for specifying the competition (race) for which betting tickets are to be purchased in the automatic purchase function and the betting ticket purchase rules for the specified race is displayed, and the user U can set up automatic purchase.

[0033] 3 is an example of a race designation screen displayed on the display unit 24 of the user terminal 20. The race designation screen is displayed to designate a race for which a betting ticket is to be purchased in the automatic purchase function when the automatic purchase button 44 is pressed by the user U while the home screen is displayed.

[0034] As shown in FIG. 3, the race designation screen displays race designation buttons 50, 51, 52, 53, 54, 55, etc. The race designation button 50 is a button that can be pressed to designate the 5th race as the target for which a betting ticket is purchased in the auto-purchase function. The race designation button 51 is a button that can be pressed to designate the 6th race as the target for which a betting ticket is purchased in the auto-purchase function. The race designation button 52 is a button that can be pressed to designate the 7th race as the target for which a betting ticket is purchased in the auto-purchase function. The race designation button 53 is a button that can be pressed to designate the 8th race as the target for which a betting ticket is purchased in the auto-purchase function. The race designation button 54 is a button that can be pressed to designate the 9th race as the target for which a betting ticket is purchased in the auto-purchase function. The race designation button 55 is a button that can be pressed to designate the 10th race as the target for which a betting ticket is purchased in the auto-purchase function.

[0035] 4 is an example of a purchase rule designation screen displayed on the display unit 24 of the user terminal 20. The purchase rule designation screen is displayed to designate a purchase rule for betting tickets for a designated race (the seventh race in the illustrated example) when the user U presses any of the race designation buttons 50, 51, 52, 53, 54, 55 (in the illustrated example, the race designation button 52) while the race designation screen is displayed.

[0036] 4, on the purchase rule designation screen, a Last Apply button 61 is displayed in a display area 60. The Last Apply button 61 is a button that can be pressed to designate the same content as the purchase rule previously designated on the purchase rule designation screen as the content of the betting ticket purchase rule for the designated race (the seventh race in the illustrated example).

[0037] In the display area 62 of the purchase rule designation screen, purchase timing designation buttons 63, 64, 65 and a recommendation message 66 are displayed. The purchase timing designation button 63 is a button that can be pressed to designate 1 to 2 minutes before the deadline when the purchase of betting tickets for a race (the seventh race in the illustrated example) is closed as the timing for automatically purchasing betting tickets based on the purchase rule designated by the user U. The purchase timing designation button 64 is a button that can be pressed to designate 2 to 3 minutes before the deadline when the purchase of betting tickets for a race is closed as the timing for automatically purchasing betting tickets based on the purchase rule designated by the user U. The purchase timing designation button 65 is a button that can be pressed to designate 3 to 5 minutes before the deadline when the purchase of betting tickets for a race is closed as the timing for automatically purchasing betting tickets based on the purchase rule designated by the user U. The recommendation message 66 indicates that the server 10 recommends 3 to 5 minutes before the deadline when the purchase of betting tickets for a race is closed as the timing for automatically purchasing betting tickets based on the purchase rule designated by the user U. Of the purchase timing designation buttons 63, 64, and 65, the purchase timing designation button 63 is designated as the default.

[0038] In addition, 1 to 2 minutes before the deadline is just before the deadline, so you can purchase at odds close to the final confirmed odds, but there is a risk that you may not be able to purchase in popular races where votes are concentrated. On the other hand, 3 to 5 minutes before the deadline is a margin of time from the deadline, so you can purchase stably even in popular races where votes are concentrated, but there is a possibility that the error from the final confirmed odds will be large. 2 to 3 minutes before the deadline is in between. Therefore, the user U may specify the purchase timing to be farther away from the deadline to ensure that the betting ticket is purchased, or may specify the purchase timing to be close to the deadline to purchase a betting ticket with confirmed odds as close as possible to the odds specified by the user U. The more complex the purchase rules are, the longer the voting process may take, so it is preferable to recommend 3 to 5 minutes before the deadline as the timing for automatically purchasing betting tickets based on the purchase rules specified by the user U.

[0039] In the display area 67 of the purchase rule specification screen, betting type specification buttons 68a, 68b, 68c, 68d, 68e, 68f, etc. that can be pressed to specify a betting method (betting type) for which a betting ticket is to be purchased in the automatic purchase function are displayed. The betting type specification button 68a is a button that can be pressed to specify "Trifecta" as a betting type. The betting type specification button 68b is a button that can be pressed to specify "Trifecta" as a betting type. The betting type specification button 68c is a button that can be pressed to specify "Dual" as a betting type. The betting type specification button 68d is a button that can be pressed to specify "Dual" as a betting type. The betting type specification button 68e is a button that can be pressed to specify "Win" as a betting type. The betting type specification button 68f is a button that can be pressed to specify "Wide" as a betting type. Of the bet type selection buttons 68a, 68b, 68c, 68d, 68e, and 68f, the bet type selection button 68a is selected as the default.

[0040] In the display area 70 of the purchase rule specification screen, input boxes 72, 74, 76, 78, etc. are displayed for specifying the range of odds (payout rate) for the bet type specified by pressing any of the bet type specification buttons 68a, 68b, 68c, 68d, 68e, 68f as purchase conditions.

[0041] The input boxes 72 and 74 are input boxes into which a value can be input to specify a range of the popularity order of odds in the specified betting type. For example, if 3 is specified in the input box 72 and 7 is specified in the input box 74 (no specification in the input boxes 76 and 78), the 3rd to 7th most popular will be specified as the range of the popularity order of odds in the specified betting type. If 5 is specified in the input box 72 and no value is specified in the input box 74 (no specification in the input boxes 76 and 78), the 5th to least popular will be specified as the range of the popularity order of odds in the specified betting type. If no value is specified in the input box 72 and 4 is specified in the input box 74 (no specification in the input boxes 76 and 78), the 1st (most popular) to 4th most popular will be specified as the range of the popularity order of odds in the specified betting type.

[0042] The input boxes 76 and 78 are input boxes into which input can be made to specify the range of odds for the specified betting type. For example, if 10.5 is specified in the input box 76 and 20.0 is specified in the input box 78 (no specification in the input boxes 72 and 74), the range of odds for the specified betting type is specified as 10.5 to 20.0. If 50.0 is specified in the input box 76 and no value is specified in the input box 78 (no specification in the input boxes 72 and 74), the range of odds for the specified betting type is specified as 50.0 to the maximum. If no value is specified in the input box 76 and 10.5 is specified in the input box 78 (no specification in the input boxes 72 and 74), the range of odds for the specified betting type is specified as the minimum to 10.5. In addition, when values ​​are specified in all of the input boxes 72, 74, 76, and 78, the betting ticket with odds specified by the AND condition of the popularity order range of the odds specified in the input boxes 72 and 74 and the odds range specified in the input boxes 76 and 78 will be specified as the purchase conditions.

[0043] In the display area 80 of the purchase rule specification screen, a No Setting button 81, a race time specification button 82, input boxes 83, 84, an Enter button 85, an Exclude button 86, an ON button 87, an OFF button 88 and a player registration button 89 are displayed to enable the user U to specify detailed conditions of the purchase rules.

[0044] The no setting button 81 is a button that can be pressed to not specify detailed conditions of the purchase rules. The race time specification button 82 is a button that can be pressed to specify a race time as a detailed condition of the purchase rules. Of the no setting button 81 and the race time specification button 82, the no setting button 81 is specified as the default.

[0045] The input boxes 83 and 84 are input boxes into which a value can be input to narrow down some of the eight racers (auto racers) participating in the race (the seventh race in the illustrated example) in order of fastest race times. For example, if 1 is specified in the input box 83 and 5 is specified in the input box 84, the racers from 1st place to 5th place are specified as the specified range of race times. If 5 is specified in the input box 83 and no value is specified in the input box 84, the racers from 5th place to the last place are specified as the specified range of race times. If no value is specified in the input box 83 and 3 is specified in the input box 84, the racers from 1st place (top place) to 3rd place are specified as the specified range of race times.

[0046] The insert button 85 is a button that can be pressed to specify that a betting ticket that includes a player specified by the race time designation button 82 and the input boxes 83, 84 as a betting target is to be included in the betting lineup. The exclude button 86 is a button that can be pressed to specify that a betting ticket that includes a player specified by the race time designation button 82 and the input boxes 83, 84 as a betting target is not to be included (excluded) in the betting lineup. Of the insert button 85 and the exclude button 86, the insert button 85 is specified by default.

[0047] The ON button 87 is a button that can be pressed to specify the use of a registered player function for placing a betting ticket containing a player registered at the instruction of the user U as a betting target in a player registration screen (not shown) displayed via pressing the player registration button 89. The OFF button 88 is a button that can be pressed to specify non-use of the registered player function. The player registration button 89 is a button that can be pressed to display the player registration screen. Of the ON button 87 and the OFF button 88, the ON button 87 is specified as the default.

[0048] When the ENTER button 85 and the ON button 87 are pressed, a betting ticket that includes a player designated by the race time designation button 82 and the input boxes 83, 84 and registered in response to instructions from the user U on the player registration screen (not shown) as a betting target is placed in as a betting suggestion. Also, when the EXCLUDE button 86 and the ON button 87 are pressed, a betting ticket that includes a player designated by the race time designation button 82 and the input boxes 83, 84 and registered in response to instructions from the user U on the player registration screen as a betting target is not placed in as a betting suggestion (is excluded).

[0049] In the display area 90 of the purchase rule specification screen, an equal division button 92, input boxes 94, 98, a distribution button 96, etc. are displayed so that the user U can specify a purchase amount condition. The user U can specify by pressing only either the equal division button 92 or the distribution button 96. Furthermore, the amount that the user U can specify in the input boxes 94, 98 is 100 to 1,000,000 yen in 100 yen increments. The amount specified by default in the input boxes 94, 98 is 100 yen. Furthermore, of the equal division button 92 and the distribution button 96, the equal division button 92 is specified by default.

[0050] The divide button 92 is a button that can be pressed to specify that all the options corresponding to the content specified in the display areas 60, 62, 67, 70, and 80 are to be purchased at the amount specified in the input box 94. For example, if the points of the options corresponding to the content specified in the display areas 60, 62, 67, 70, and 80 are 20 points and the amount specified in the input box 94 is 100 yen, the purchase amount when the divide button 92 is pressed will be 2000 yen (=20 points x 100 yen).

[0051] The allocation button 96 is a button that can be pressed to specify the amount specified in the input box 94 as the total amount of purchases of the multiple bets so that the payout amount is the same regardless of which of the multiple bets corresponding to the contents specified in the display areas 60, 62, 67, 70, and 80 wins. When the allocation button 96 is pressed, the server 10 first determines the amount specified in the input box 94 as the total amount of bets, and calculates the purchase amounts (allocation amounts) of the multiple bets by calculating backwards from the odds of the multiple bets corresponding to the contents specified in the display areas 60, 62, 67, 70, and 80. For example, if the amount specified in the input box 94 is 3000 yen and the odds of two bets corresponding to the contents specified in the display areas 60, 62, 67, 70, and 80 are 5 times and 10 times, the server 10 calculates 2000 yen as the purchase amount of the bet with odds of 5 times, and calculates 1000 yen as the purchase amount of the bet with odds of 10 times.

[0052] Below the display area 90 of the purchase rule specification screen, the suggested purchase points (5 points in the illustrated example) of the bets corresponding to the content specified in the display areas 60, 62, 67, 70, 80, a confirmation button 100, etc. are displayed. The confirmation button 100 is a button that can be pressed to confirm the content specified in the display areas 60, 62, 67, 70, 80, 90 as the content of the betting ticket purchase rule for the specified race (the seventh race in the illustrated example). When the confirmation button 100 is pressed by the user U, the server 10 sets the content specified in the display areas 60, 62, 67, 70, 80, 90 as the content of the betting ticket purchase rule for the specified race.

[0053] (Server 10 hardware configuration) 5 is a block diagram showing a hardware configuration of the server 10 in this embodiment. As shown in FIG. 5, the server 10 includes a control unit 11, a storage unit 12, a communication unit 13, an operation input unit 14, and a monitor 15.

[0054] The control unit 11 is, for example, a CPU (Central Processing Unit), a microprocessor, a DSP (Digital Signal Processor), or the like, and controls the overall operation of the server 10.

[0055] A part of the storage unit 12 is composed of, for example, a random access memory (RAM) or a dynamic random access memory (DRAM), and is used as a work area when the control unit 11 executes processes based on various programs.

[0056] Furthermore, a part of the storage unit 12 is, for example, a non-volatile memory such as a ROM (Read Only Memory) or an HDD (Hard Disk Drive), and stores various data and programs used in the processing of the control unit 11. The storage unit 12 can hold a database including one or more tables for recording various information, processing results, and the like.

[0057] The storage unit 12 stores the voting details (e.g., voting method (betting type), betting target, number of bets of a predetermined value or betting amount on the betting target, etc.) cast by the user U in association with a user ID that uniquely identifies the user U. The storage unit 12 also stores purchase rule designation information that indicates a purchase rule designated by the user U.

[0058] The programs stored in the memory unit 12 include, for example, an OS (Operating System) for realizing the basic functions of the server 10, drivers for controlling various hardware, programs for realizing various functions, etc., and include a program that functions as the "information processing program" of the present invention.

[0059] The communication unit 13 is, for example, a NIC (Network Interface Controller), and has a function of connecting to the communication line 5. Instead of or together with the NIC, the communication unit 13 may have a function of connecting to a wireless LAN (Local Area Network), a function of connecting to a wireless WAN (Wide Area Network), a function of enabling short-distance wireless communication such as Bluetooth (registered trademark), and infrared communication, etc. The server 10 is connected to the user terminal 20, etc. via the communication line 5, and can transmit and receive various data to and from the user terminal 20, etc.

[0060] The operation input unit 14 is composed of a keyboard, a mouse, etc., and accepts input of various operations by a user U who uses the server 10. The monitor 15 is, for example, a liquid crystal display device, etc., and displays various images.

[0061] The control unit 11, the storage unit 12, the communication unit 13, the operation input unit 14, and the monitor 15 are electrically connected to one another via a system bus 16. Therefore, the control unit 11 can access the storage unit 12, display images on the monitor 15, grasp the operation state of the operation input unit 14 by the user U, and access various communication networks and the user terminal 20 via the communication unit 13.

[0062] (Hardware configuration of user terminal 20) Fig. 6 is a block diagram showing a hardware configuration of the user terminal 20 in this embodiment. As shown in Fig. 3, the user terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, a display unit 24, a speaker 25, a microphone 26, a camera 27, and an operation button 28.

[0063] The control unit 21 is, for example, a CPU (Central Processing Unit), a microprocessor, a DSP (Digital Signal Processor), or the like, and controls the overall operation of the user terminal 20.

[0064] A part of the storage unit 22 is composed of, for example, a random access memory (RAM) or a dynamic random access memory (DRAM), and is used as a work area when the control unit 21 executes processes based on various programs.

[0065] Furthermore, a part of the storage unit 22 is, for example, a non-volatile memory such as a ROM (Read Only Memory) or an HDD (Hard Disk Drive), and stores various data and programs used in the processing of the control unit 21. The storage unit 22 can hold a database including one or more tables for recording various information, processing results, and the like.

[0066] The programs stored in the storage unit 22 include, for example, an OS (Operating System) for implementing basic functions of the user terminal 20, drivers for controlling various hardware, programs for implementing various functions, and the like.

[0067] The communication unit 23 is, for example, a network interface controller (NIC), and has a function of connecting to the communication line 5. Instead of or together with the NIC, the communication unit 23 may have a function of connecting to a wireless local area network (LAN), a function of connecting to a wireless wide area network (WAN), a function of enabling short-distance wireless communication such as Bluetooth (registered trademark), and infrared communication. The user terminal 20 is connected to the server 10, other user terminals 20, etc. via the communication line 5, and can transmit and receive various data to and from the server 10, other user terminals 20, etc.

[0068] The display unit 24 is a touch panel display or the like, and is capable of displaying images and the like and accepting operations by the user U.

[0069] The speaker 25 outputs various sounds under the control of the control unit 21. The microphone 26 inputs various sounds under the control of the control unit 21. The camera 27 captures an image of a subject under the control of the control unit 21.

[0070] The operation button 28 is provided on, for example, the side surface of the user terminal 20, and includes a power button for starting or stopping the user terminal 20, a button for adjusting the volume of the sound output from the speaker 25, and the like.

[0071] The control unit 21, the storage unit 22, the communication unit 23, the display unit 24, the speaker 25, the microphone 26, the camera 27, and the operation buttons 28 are electrically connected to one another via a system bus 29. Therefore, the control unit 21 can access the storage unit 22, display images on the display unit 24, grasp the operation state of the touch panel display (display unit 24) and the operation buttons 28 by the user U, input sound to the microphone 26, output sound from the speaker 25, control the camera 27, and access various communication networks, the server 10, other user terminals 20, etc. via the communication unit 23.

[0072] 7 is a block diagram showing an example of the functional configuration of the control unit 11 provided in the server 10 in this embodiment. As shown in FIG. 7, the control unit 11 includes, as its functional configuration, a vote acceptance unit 11a, a vote management unit 11b, a competition acceptance unit 11c, a purchase rule acceptance unit 11d, an automatic purchase unit 11e, a purchase timing acceptance unit 11f, a purchase timing recommendation unit 11g, a display control unit 11h, a notification unit 11i, and a setting recommendation unit 11j. In general, the control unit 11 of the server 10 has various functions other than those described above, but here, only the characteristic functions in the voting system 1 in this embodiment will be described, and other known functions and the like will not be illustrated or described.

[0073] The vote acceptance unit 11a accepts votes from the user U (e.g., user U1) for the results of the competition (auto race) via the user U's (e.g., user U1's) operation on the display unit 24 of the user terminal 20. Then, the vote acceptance unit 11a stores in the memory unit 12 vote information indicating the accepted vote content (e.g., betting method, betting target, predetermined value such as betting amount, etc.).

[0074] The voting management unit 11b executes the voting of the user U on the result of the competition in accordance with the vote of the user U accepted by the voting acceptance unit 11a. Furthermore, when the competition ends, if the vote is correct based on the result of the competition, the voting management unit 11b calculates a payout value (e.g., money or points) that is determined based on the amount of the predetermined value used for the vote and the payout rate (odds) of the bet, and grants the calculated payout value to the user U.

[0075] The race acceptance unit 11c accepts, via an operation by the user U (eg, user U1) on the display unit 24 of the user terminal 20 on the race selection screen shown in FIG. 3, a selection of a race for which a betting ticket is to be purchased from the user U.

[0076] The purchase rule receiving unit 11d receives designation of a purchase rule for betting tickets for a specified race, via an operation of a user U (e.g., user U1) on the display unit 24 of the user terminal 20, on a purchase rule designation screen shown in Fig. 4. The purchase rule allows the user U to select a betting type (in this embodiment, trifecta, trifecta, diadem, diadem, wide, and win) and to designate a range of odds (payout rate) for the selected betting type (in this embodiment, a range of odds in order of popularity, a range of odds).

[0077] The automatic purchasing unit 11e automatically purchases betting tickets based on purchasing rules specified by the user U within a predetermined time range (in this embodiment, 1-2 minutes, 2-3 minutes, or 3-5 minutes before) before the deadline when purchase of betting tickets for a race is closed. This makes it possible to meet a variety of user needs regarding the automatic purchase of betting tickets.

[0078] The purchase timing receiving unit 11f receives a designation from the user U (e.g., user U1) of the timing for automatically purchasing betting tickets within a predetermined time range (in this embodiment, 1 to 2 minutes, 2 to 3 minutes, or 3 to 5 minutes before) before the deadline when purchase of betting tickets for a competition (race) is closed, via the user U's (e.g., user U1) operation on the display unit 24 of the user terminal 20 on the purchase rule designation screen shown in Fig. 4. In this case, the automatic purchasing unit 11e automatically purchases betting tickets based on the purchase rules at the timing designated by the user U.

[0079] This allows the user U to automatically purchase a voting ticket at a timing desired by the user U. In particular, immediately before the deadline when the purchase of the voting ticket is closed, votes tend to be concentrated and the load of the voting process on the server 10 becomes large, so by specifying an earlier timing (e.g., 3 to 5 minutes before) within a predetermined time range before the deadline (in this embodiment, 1 to 2 minutes before, 2 to 3 minutes before, 3 to 5 minutes before), the load of the voting process on the server 10 can be distributed and reduced. Also, if an attempt is made to purchase a voting ticket based on a purchase rule with complicated conditions immediately before the deadline when the purchase of the voting ticket is closed, it is possible that the voting process will take time and the purchase will not be possible. Therefore, from the viewpoint of ensuring automatic purchase of the voting ticket, the user U can specify an earlier timing (e.g., 3 to 5 minutes before) within a predetermined time range before the deadline (in this embodiment, 1 to 2 minutes before, 2 to 3 minutes before, 3 to 5 minutes before).

[0080] The purchase timing recommendation unit 11g recommends to the user U the timing for automatically purchasing a betting ticket within a predetermined time range (1 to 2 minutes, 2 to 3 minutes, or 3 to 5 minutes before, in this embodiment) before the deadline when the purchase of the betting ticket is closed, based on the purchase rule specified by the user U. The purchase timing recommendation unit 11g displays a recommendation message 66 on the purchase rule specification screen shown in FIG. 4, thereby recommending to the user U 3 to 5 minutes before the deadline as the timing for automatically purchasing a betting ticket. This allows the user U to suitably specify the timing for automatically purchasing a betting ticket. In particular, in the case of a complicated betting type (for example, a trifecta or a trifecta combination) or when there are many points (bet combinations) that may be purchased in accordance with the purchase rule, it is possible to recommend to the user U to purchase a betting ticket in an earlier time period from the deadline, such as 3 to 5 minutes before the deadline.

[0081] The automatic purchasing unit 11e automatically purchases betting tickets based on the purchasing rules for a race, whose odds have changed by a predetermined amount or more in a predetermined period (e.g., 5 to 10 minutes before) before the deadline when the purchase of betting tickets is closed, at a later time than betting tickets whose odds have changed by less than the predetermined amount in the predetermined period. For example, the automatic purchasing unit 11e automatically purchases betting tickets whose odds have changed by more than the predetermined amount in the predetermined period just before the deadline, and automatically purchases betting tickets whose odds have changed by less than the predetermined amount in the predetermined period in an earlier time period from the deadline, thereby dispersing the timing of purchasing betting tickets. This reduces the possibility that betting tickets whose odds have changed by more than the predetermined amount in the predetermined period before the deadline are automatically purchased according to the purchasing rules, but that odds just before the deadline are different from those of the purchasing rules, and thus increases the possibility of the user U making the bet that he or she intends.

[0082] The automatic purchasing unit 11e automatically purchases betting tickets for a second betting type (e.g., trifecta) in which the odds change range is larger than that of a first betting type (e.g., win) for betting tickets based on purchase rules for a competition (race) at a later time than betting tickets for the first betting type (win). For example, the automatic purchasing unit 11e automatically purchases betting tickets for the second betting type in which the odds change range is larger just before the deadline, and automatically purchases betting tickets for the first betting type in which the odds change range is smaller in an earlier time period from the deadline, thereby dispersing the timing of purchasing betting tickets. This reduces the possibility that betting tickets for a betting combination with a different odds from the purchase rules will be purchased at the odds just before the deadline for betting tickets for the second betting type in which the odds change range is larger, even if they are automatically purchased according to the purchase rules, and thus increases the possibility of the user U making the bet that he or she intends.

[0083] The automatic betting unit 11e purchases betting tickets in a distributed manner based on the purchase rules for a race at multiple times, thereby reducing the load of betting processing on the server 10.

[0084] When the user U manually purchases a betting ticket for a first race (e.g., the 10th race), the display control unit 11h causes the user terminal 20 used by the user U to identifiably display a first auto racer (corresponding to the "first race body" of the present invention) participating in the first race and a second race (e.g., the 7th race) corresponding to the winning betting ticket that was automatically purchased based on the purchase rules specified by the user U, and a second auto racer (corresponding to the "second race body" of the present invention) participating in the first race but not participating in the second race. This allows the user U to identify and recognize the first auto racer who is also participating in the race corresponding to the winning betting ticket that was automatically purchased based on the purchase rules among the auto racers participating in the first race when manually purchasing a betting ticket for the first race. Then, the user U can purchase a betting ticket for the first race and watch the first race with a strong desire to support the first auto racer that he or she has identified.

[0085] If there are no betting tickets with odds matching the purchase rules in the race specified by the user U a predetermined time (e.g., 5 minutes) before the deadline for the purchase of betting tickets is closed, the notification unit 11i notifies the user terminal 20 used by the user U of this fact. This allows the user U to know in advance that there is a possibility that a betting ticket with odds matching the purchase rules will not be purchased.

[0086] In addition, examples of notification modes of the fact that there are no betting tickets with odds matching the purchase rules include an audio notification mode by playing an audio signal on the speaker 25 of the user terminal 20, a visual notification mode by displaying an image on the display unit 24 of the user terminal 20, a visual notification mode by controlling the color of light, the pattern of lighting / flashing, the intensity of light, etc. in the user terminal 20 to generate light, a tactile notification mode by controlling the pattern and intensity of vibrations to generate vibrations using the vibration function of the user terminal 20, and an olfactory notification mode by firing air with a specific odor such as an irritating odor toward the nasal cavity of the user U using a swingable air cannon in the user terminal 20. In addition, the audio signal includes a human voice message, a buzzer sound, a chime sound, an alarm sound, and the like. The image displayed on the display unit 24 is an image that includes at least one element such as a figure, computer graphics, a photo, a letter, a number, and a symbol, and may be an image that includes a combination of two or more elements. Furthermore, the image may be either a monochrome image or a color image, and may be either a still image or a moving image.

[0087] When there is no betting ticket with odds matching the purchase rule in the race specified by the user U a predetermined time (e.g., 5 minutes) before the deadline when the purchase of betting tickets is closed, the setting recommendation unit 11j recommends the user U to set a purchase rule different from the purchase rule. For example, when there is no betting ticket with odds matching the purchase rule in the race specified by the user U, the setting recommendation unit 11j recommends the user U to set a purchase rule different from the purchase rule by changing the purchase rule. In addition, when there is no betting ticket with odds matching the purchase rule in the race specified by the user U, the setting recommendation unit 11j recommends the user U to set a new purchase rule different from the purchase rule. As described above, even if there is a possibility that a betting ticket with odds matching the purchase rule will not be purchased, the user U can take appropriate measures such as setting a purchase rule different from the purchase rule before the deadline.

[0088] When a user U manually purchases a betting ticket for a competition (race), the display control unit 11h causes the user terminal 20 used by the user U to distinguish between a first betting ticket that matches the purchase rule specified by the user U for that competition and a second betting ticket that does not match the purchase rule. Then, when the user U selects the first betting ticket as the one to be purchased, the display control unit 11h causes the user terminal 20 to display a warning. This makes it possible to reduce the possibility of the user U purchasing a betting ticket manually, overlapping with a betting ticket that matches the purchase rule.

[0089] The automatic purchasing unit 11e automatically purchases betting tickets, excluding betting tickets manually purchased by the user U, from betting tickets based on the purchasing rules for a competition (race) specified by the user U. This allows betting tickets based on the purchasing rules to be automatically purchased, excluding betting tickets purchased by the user U.

[0090] Fig. 8 is an example of a notification screen displayed on the display unit 24 of the user terminal 20. As shown in Fig. 8, display messages 110, 112, etc. are displayed on the notification screen.

[0091] If there are no betting tickets with odds matching the purchase rules in the race specified by the user U a predetermined time (e.g., 5 minutes) before the deadline for the purchase of betting tickets is closed, the notification unit 11i causes the display unit 24 of the user terminal 20 to display a display message 110 indicating that fact. This allows the user U to know in advance that there is a possibility that a betting ticket with odds matching the purchase rules will not be purchased.

[0092] When there are no betting tickets with odds matching the purchase rules in the race specified by the user U a predetermined time (e.g., 5 minutes) before the deadline when the purchase of betting tickets is closed, the setting recommendation unit 11j displays a display message 112 on the display unit 24 of the user terminal 20, recommending to the user U to set new purchase rules different from the purchase rules. This allows the user U to take appropriate measures, such as setting new purchase rules different from the purchase rules, before the deadline, even if there is a possibility that a betting ticket with odds matching the purchase rules will not be purchased.

[0093] Fig. 9 is an example of a voting screen displayed on the display unit 24 of the user terminal 20 when a betting ticket for the first race (e.g., the tenth race) is manually purchased by the user U. As shown in Fig. 9, the voting screen displays betting content information 120, 124 indicating the contents (betting target, odds, betting amount) of the betting ticket corresponding to the vote of the user U accepted by the betting acceptance unit 11a, a purchase button 128 that can be pressed to bet (purchase) with the contents of the betting ticket, and the like.

[0094] The betting content information 120 indicates the betting target "a trifecta with auto racer number 3 coming in first, auto racer number 5 coming in second, and auto racer number 7 coming in third," with odds of "13.7:1," and a betting amount of "500 yen." The betting content information 124 indicates the betting target "a duplica with auto racer number 6 coming in first and auto racer number 4 coming in second," with odds of "12.5:1," and a betting amount of "1000 yen."

[0095] When a user U manually purchases a betting ticket for a first race (e.g., the tenth race), the display control unit 11h causes a first auto racer participating in the first race and a second race (e.g., the seventh race) corresponding to a winning betting ticket that was automatically purchased based on the purchase rules specified by the user U, and a second auto racer participating in the first race but not in the second race to be identifiable on the betting screen. For example, the display control unit 11h causes a thick frame 122 to surround the "5" indicating the first auto racer (in the illustrated example, the auto racer no. 5) in the betting target of the betting content information 120, but does not cause the thick frames 122 to surround the "3" and "7" indicating the second auto racers (in the illustrated example, the auto racers no. 3 and no. 7). As a result, when user U manually purchases a betting ticket for the first race, he or she can identify and grasp the first auto racer (in the illustrated example, auto racer number 5) among the auto racers participating in the first race who is also participating in the race corresponding to the winning betting ticket that was automatically purchased based on the purchasing rules.

[0096] When the user U manually purchases a betting ticket for a first race (for example, the 10th race), the display control unit 11h displays on the betting screen a first betting ticket that matches the purchase rule specified by the user U in the first race and a second betting ticket that does not match the purchase rule in a distinguishable manner. As shown in FIG. 9, for a first betting ticket (corresponding to the betting content information 124) that matches the purchase rule specified by the user U in the first race, match information 126 indicating that the ticket matches the purchase rule is displayed in the betting target of the betting content information 124, and for a second betting ticket (corresponding to the betting content information 120) that does not match the purchase rule specified by the user U in the first race, match information 126 indicating that the ticket matches the purchase rule is not displayed in the betting target of the betting content information 120. This can reduce the possibility that the user U will purchase a betting ticket that matches the purchase rule when purchasing a betting ticket manually.

[0097] Fig. 10 is an example of a voting screen displayed on the display unit 24 of the user terminal 20 when the user U manually purchases a betting ticket for the first race (for example, the tenth race). As shown in Fig. 10, the voting screen further displays a display message 130 as a difference from the voting screen shown in Fig. 9. When the user U selects the first voting ticket (corresponding to the voting content information 124) as the purchase target, the display control unit 11h displays a warning by displaying a display message 130 indicating that the first voting ticket (corresponding to the voting content information 124) is selected as the purchase target by the user U on the voting screen. This can further reduce the possibility of the user U purchasing a duplicate betting ticket that matches the purchase rule when manually purchasing a betting ticket.

[0098] 11 is a flowchart showing an example of a voting process (automatic purchase process) performed by the server 10 in this embodiment. The voting process shown in FIG. 11 is started when the user U presses the automatic purchase button 44 on the home screen shown in FIG.

[0099] First, the competition acceptance unit 11c accepts a designation of a competition (race) for which a betting ticket is to be purchased from a user U (e.g., user U1) via an operation of the user U on the display unit 24 of the user terminal 20 on the race designation screen shown in FIG. 3 (step S100).

[0100] Next, the purchase rule accepting unit 11d accepts the specification of the purchase rule for the betting ticket for the specified race via the operation of the user U (e.g., user U1) on the display unit 24 of the user terminal 20 on the purchase rule specification screen shown in FIG. 4 (step S110).

[0101] Next, the control unit 11 sets rules for purchasing betting tickets for the race specified in steps S100 and S110 (step S120). Next, the automatic purchasing unit 11e determines whether or not it is within a predetermined time range (in this embodiment, 1 to 2 minutes, 2 to 3 minutes, or 3 to 5 minutes) before the deadline at which purchasing betting tickets for the race specified in step S110 is closed (step S130).

[0102] If the result of the determination is that it is not within the predetermined time range before the deadline (step S130, NO), the process returns to before step S130. On the other hand, if it is within the predetermined time range before the deadline (step S130, YES), the automatic purchasing unit 11e automatically purchases betting tickets based on the purchasing rules specified by the user U in step S110 (step S140). Completion of the process of step S140 causes the server 10 to end the voting process shown in FIG.

[0103] As described above in detail, in this embodiment, the server 10 (information processing device) includes a race acceptance unit 11c, a purchase rule acceptance unit 11d, and an automatic purchase unit 11e. The race acceptance unit 11c accepts the designation of a race for which a betting ticket is to be purchased from the user U. The purchase rule acceptance unit 11d accepts the designation of the purchase rule of the betting ticket for the designated race. The automatic purchase unit 11e automatically purchases betting tickets based on the purchase rule designated by the user U within a predetermined time range before the deadline when the purchase of betting tickets for the race is closed. Here, the purchase rule can be selected by the user U as a betting type and can be designated by the user U as a range of odds for the selected betting type.

[0104] According to the present embodiment configured as described above, it is possible to meet a variety of user needs regarding automatic purchase of betting tickets.

[0105] It should be noted that the above-mentioned embodiments are merely examples of the implementation of the present invention, and the technical scope of the present invention should not be interpreted as being limited by these embodiments. In other words, the present invention can be implemented in various forms without departing from the gist or main features of the present invention.

[0106] <Summary> [General-purpose subject] One object of the present invention is to meet the needs of users regarding the purchase of voting tickets.

[0107] Issues corresponding to [Appendix 1] One of the objects of the present invention is to meet the diverse needs of users regarding automatic purchasing of betting tickets. [Supplementary Note 1] The information processing device of this embodiment comprises a race acceptance unit that accepts from a user the designation of a race for which betting tickets are to be purchased, a purchase rule acceptance unit that accepts designation of betting ticket purchasing rules for the designated race, and an automatic purchasing unit that automatically purchases betting tickets based on the purchasing rules designated by the user within a predetermined time range before the deadline for the purchase of betting tickets for the race, and the user can specify the purchase rules by selecting a betting type and the range of odds for the selected betting type. According to the above information processing device, it is possible to meet various user needs regarding automatic purchase of betting tickets.

[0108] Issues corresponding to [Appendix 2] One of the objects of the present invention is to enable a user to automatically purchase a voting ticket at a timing desired by the user. [Appendix 2] An information processing device as described in Appendix 1, further comprising a purchase timing receiving unit that receives from a user a designation of the timing within a predetermined time range for automatically purchasing betting tickets, and the automatic purchasing unit automatically purchases betting tickets based on the purchase rules at the timing designated by the user. This allows the user to automatically purchase a voting ticket at a time desired by the user.

[0109] Issues corresponding to [Appendix 3] One object of the present invention is to enable a user to suitably specify the timing for automatically purchasing betting tickets. [Supplementary Note 3] The information processing device according to Supplementary Note 2, further comprising a purchase timing recommendation unit that recommends to the user the timing for automatically purchasing betting tickets within a predetermined time range based on a purchase rule specified by the user. This allows the user to conveniently specify the timing for automatically purchasing the betting ticket.

[0110] Issues corresponding to [Appendix 4] One of the goals of the present invention is to increase the likelihood that a user's vote will be what he or she intended. [Appendix 4] An information processing device as described in any one of Appendices 1 to 3, wherein the automatic purchasing unit automatically purchases, for betting tickets based on purchasing rules for a competition, betting tickets whose odds fluctuation amount during a specified period before the closing time is equal to or greater than a specified fluctuation amount, at a later time than betting tickets whose odds fluctuation amount during the specified period is less than the specified fluctuation amount. This can increase the likelihood that the user will vote as intended.

[0111] Issues corresponding to [Appendix 5] One of the goals of the present invention is to increase the likelihood that a user's vote will be what he or she intended. [Appendix 5] An information processing device as described in any one of Appendices 1 to 4, wherein the automatic purchasing unit automatically purchases betting tickets for a second betting type, in which the range of change in odds is greater than that of the first betting type, for betting tickets based on purchasing rules for a race, at a later time than the betting tickets for the first betting type. This can increase the likelihood that the user will vote as intended.

[0112] Issues corresponding to [Appendix 6] One object of the present invention is to reduce the load of voting processing on an information processing device. [Supplementary Note 6] The information processing device according to any one of Supplementary Notes 1 to 5, wherein the automatic purchasing unit purchases betting tickets in a distributed manner at multiple times based on purchasing rules for the race. This reduces the load of the voting process on the information processing device.

[0113] Issues corresponding to [Appendix 7] One of the objectives of the present invention is to enable a user, when manually purchasing a betting ticket for a competition, to be able to ascertain the competing entities that are also participating in the competition corresponding to the winning betting ticket that was automatically purchased based on the purchasing rules. [Appendix 7] An information processing device as described in any one of Appendices 1 to 6, further comprising a display control unit that, when a user manually purchases a betting ticket for a first competition, causes a first competing body participating in the first competition and a second competition corresponding to the winning betting ticket that was automatically purchased based on the purchase rules, and a second competing body participating in the first competition but not in the second competition, to be identifiable on a terminal device used by the user. This allows a user, when manually purchasing a betting ticket for the first race, to identify and grasp the competing entities participating in the first race that are also participating in the race corresponding to the winning betting ticket that was automatically purchased based on the purchase rules.

[0114] Issues corresponding to [Appendix 8] One of the objectives of the present invention is to let a user understand that there is a possibility that a betting ticket with odds that match the purchase rules will not be purchased. [Appendix 8] An information processing device as described in any one of Appendices 1 to 7, further comprising a notification unit that notifies a terminal device used by a user of the fact that there are no betting tickets with odds that match the purchase rules for a race before a predetermined time from the deadline. This allows the user to know in advance that there is a possibility that a betting ticket with odds that match the purchase rules will not be purchased.

[0115] Issues corresponding to [Appendix 9] One of the objects of the present invention is to enable a user to take appropriate action even when there is a possibility that a betting ticket with odds that match the purchase rules will not be purchased. [Appendix 9] An information processing device as described in any one of Appendices 1 to 8, further comprising a setting recommendation unit that recommends to a user to set purchase rules different from the purchase rules if there are no betting tickets with odds that match the purchase rules for a race before a predetermined time from the deadline. This allows the user to take measures to set purchasing rules different from the purchasing rules before the deadline, even if there is a possibility that a betting ticket with odds that match the purchasing rules will not be purchased.

[0116] Issues corresponding to [Appendix 10] One of the objectives of the present invention is to reduce the possibility that, when a user manually purchases a ballot, the user will purchase the same ballot as a ballot that meets the purchasing rules. [Appendix 10] An information processing device as described in any one of Appendices 1 to 9, further comprising a display control unit that, when a user manually purchases a voting ticket for a competition, causes a first voting ticket that matches a purchasing rule for the competition and a second voting ticket that does not match the purchasing rule to be displayed on a terminal device used by the user in a distinguishable manner, and that, when the first voting ticket is selected by the user as the item to be purchased, causes a warning to be displayed on the terminal device. This makes it possible to reduce the possibility that a user will purchase a betting ticket that is the same as a betting ticket that matches the purchasing rules when manually purchasing a betting ticket.

[0117] Issues corresponding to [Appendix 11] One of the objectives of the present invention is to prevent a user, when manually purchasing a ballot ticket, from purchasing the same ballot ticket as a ballot ticket that meets the purchasing rules. [Appendix 11] An information processing device as described in any one of Appendices 1 to 10, wherein the automatic purchasing unit automatically purchases betting tickets for a sport specified by the user from betting tickets based on purchasing rules, excluding betting tickets manually purchased by the user. This makes it possible to prevent a user from purchasing a betting ticket that is the same as a betting ticket that matches the purchasing rules when manually purchasing a betting ticket.

[0118] Issues corresponding to [Appendix 12] One of the objects of the present invention is to meet the diverse user needs regarding the automatic purchase of betting tickets for each venue where a competition is held. [Appendix 12] In the information processing method of this embodiment, the processor accepts from the user the designation of the race for which voting tickets are to be purchased, the processor accepts designation of the purchasing rules for the voting tickets for the designated race, and the processor automatically purchases the voting tickets based on the purchasing rules designated by the user within a predetermined time range before the deadline when the purchase of voting tickets for the race is closed, and the purchasing rules allow the user to select a betting type and specify a range of odds for the selected betting type. According to the above information processing method, it is possible to meet a variety of user needs regarding automatic purchasing of betting tickets.

[0119] Issues corresponding to [Appendix 13] One of the objects of the present invention is to meet the diverse needs of users regarding automatic purchasing of betting tickets. [Appendix 13] The information processing program of this embodiment causes the processor to execute a process of accepting from a user the designation of a race for which voting tickets are to be purchased, accepting designation of purchasing rules for the designated race, and automatically purchasing voting tickets based on the purchasing rules designated by the user within a predetermined time range before the deadline for purchasing voting tickets for the race, and the purchasing rules allow the user to select a betting type and specify a range of odds for the selected betting type. According to the above information processing program, it is possible to meet various user needs regarding automatic purchase of betting tickets. [Explanation of symbols]

[0120] 1: Voting system, 10: Server, 11: Control unit, 11a: Voting acceptance unit, 11b: Voting management unit, 11c: Competition acceptance unit, 11d: Purchase rule acceptance unit, 11e: Automatic purchase unit, 11f: Purchase timing acceptance unit, 11g: Purchase timing recommendation unit, 11h: Display control unit, 11i: Notification unit, 11j: Setting recommendation unit, 12: Memory unit, 13: Communication unit, 14: Operation input unit, 15: Monitor, 16: System bus, 20, 20a, 20b, 20c: User terminal, 21: Control unit, 22: Memory unit, 23: Communication unit, 24: Display unit, 25: Speaker, 26: Microphone, 27: Camera, 28: Operation button, 29: System bus, 40: Voting button, 42: Watching button, 44: Automatic purchase button, 50, 51, 52, 53, 54, 55: Race designation Buttons, 60, 62, 67, 70, 80, 90: Display area, 61: Last applied button, 63, 64, 65: Purchase timing designation button, 66: Recommended message, 68a, 68b, 68c, 68d, 68e, 68f: Betting type designation button, 72, 74, 76, 78, 83, 84, 94, 98: Input box, 81: No setting button, 82: Competition time designation button, 85: Add button, 86: Exclude button, 86, 87: ON button, 88: OFF button, 89: Player registration button, 92: Equal division button, 96: Allocation button, 100: Confirm button, 110, 112, 130: Display message, 120, 124: Voting content information, 122: Thick frame, 126: Match information, 128: Purchase button, U, U1, U2, U3, U4: User

Claims

1. The system includes a competition reception unit, a purchase rule reception unit, and an automatic purchase unit, the competition acceptance unit accepts, from a user, a designation of a competition for which a betting ticket is to be purchased; the purchase rule acceptance unit accepts a designation of a purchase rule for a betting ticket for a designated event; the automatic purchasing unit automatically purchases betting tickets based on the purchasing rules designated by the user within a predetermined time range before a deadline at which purchase of betting tickets for the race is closed; The purchase rule allows the user to select a betting type and to specify a range of odds for the selected betting type. Information processing device.

2. A purchase timing reception unit is further provided, the purchase timing receiving unit receives from the user a designation of a timing for automatically purchasing a betting ticket within the predetermined time range; The automatic purchasing unit automatically purchases betting tickets based on the purchasing rules at a timing designated by the user. The information processing device according to claim 1 .

3. It also has a purchase timing recommendation section, the purchase timing recommendation unit recommends to the user a timing for automatically purchasing a ballot ticket within the predetermined time range based on the purchase rule designated by the user. The information processing device according to claim 2 .

4. the automatic purchasing unit automatically purchases, for betting tickets based on the purchasing rules for the race, betting tickets for which the amount of fluctuation in odds during a predetermined period before the deadline is equal to or greater than a predetermined amount of fluctuation, at a later time than betting tickets for which the amount of fluctuation in odds during the predetermined period is less than the predetermined amount of fluctuation. The information processing device according to claim 1 .

5. the automatic purchasing unit automatically purchases, for the betting tickets based on the purchasing rules for the race, a betting ticket for a second betting type in which the odds change range is larger than that of a first betting type, at a time later than that of the betting tickets for the first betting type. The information processing device according to claim 1 .

6. the automatic betting unit purchases betting tickets for the race in a distributed manner based on the betting rules at a plurality of timings; The information processing device according to claim 1 .

7. A display control unit is further provided, When the user manually purchases a betting ticket for a first competition, the display control unit causes a first playing object participating in the first competition and a second competition corresponding to the winning betting ticket that was automatically purchased based on the purchase rules, and a second playing object participating in the first competition but not participating in the second competition, to be identifiable on a terminal device used by the user. The information processing device according to claim 1 .

8. A notification unit is further provided, the notification unit, if there is no betting ticket with odds matching the purchase rule for the race, notifies the terminal device used by the user of that fact before a predetermined time from the deadline; The information processing device according to claim 1 .

9. Further comprising a setting recommendation section; the setting recommendation unit, when there is no betting ticket with odds matching the purchase rule for the race before a predetermined time from the deadline, recommends to the user a setting of a purchase rule different from the purchase rule; The information processing device according to claim 1 .

10. A display control unit is further provided, the display control unit, when the user manually purchases a ballot for the competition, causes a first ballot that matches the purchase rule for the competition and a second ballot that does not match the purchase rule to be distinguishably displayed on a terminal device used by the user, and when the user selects the first ballot as a ballot to be purchased, causes a warning to be displayed on the terminal device. The information processing device according to claim 1 .

11. the automatic purchasing unit automatically purchases betting tickets, for the event designated by the user, from the betting tickets based on the purchasing rules, excluding betting tickets manually purchased by the user; The information processing device according to claim 1 .

12. The processor accepts from the user the designation of the event for which the betting ticket is to be purchased, The processor accepts a designation of rules for purchasing betting tickets for a designated competition; a processor automatically purchases betting tickets based on the purchase rules designated by the user within a predetermined time range before a deadline at which purchase of betting tickets for the race is closed; The purchase rule allows the user to select a betting type and to specify a range of odds for the selected betting type. Information processing methods.

13. The processor: Accept the user's designation of the event for which the betting ticket is to be purchased, Accept the specification of rules for purchasing betting tickets for the specified competition, automatically purchasing betting tickets based on the purchase rule designated by the user within a predetermined time range before a deadline at which purchase of betting tickets for the race is closed; Execute the process, The purchase rule allows the user to select a betting type and to specify a range of odds for the selected betting type. Information processing program.

Images