JP2023012353A - bookmaker system - Google Patents

Abstract

To provide a bookmaker system configured to always refund the amount cancelled immediately and to allow an additional bet on an event whose odds vary with time with the amount refunded.SOLUTION: A bookmaker system 1 is configured to: store a user account associated with funds to be used for a bet for each user; receive vote information including a bet target bet by the user and the amount of bet; receive a cancellation of a bet by the user during an event; and add, when the cancellation of the bet is received, the amount refunded that is calculated based on a refund rate which is varied in accordance with a status of the event, to the funds of the user account of the user.SELECTED DRAWING: Figure 1

Description

The present invention relates to a bookmaker system.

Conventionally, there has been known a bookmaker system in which multiple final outcomes of events that can occur in events such as sports games and elections are each bet targets, and dividends are awarded to users who bet on bet targets that match the final results after the event ends. (For example, Patent Document 1).

A bookmaker system is known to have a configuration that allows betting not only before the event but also during the event by varying the odds of each betting target according to the progress of the event. .

U.S. Patent Application Publication No. 2020/0134973

In this way, if it takes a long time from the start of betting until the result is known, there are cases where, after placing the initial bet, it is desired to make another prediction and re-bet while the odds fluctuate according to the development of the game. However, due to the lack of results, there may be no money to bet again.

SUMMARY OF THE INVENTION Accordingly, it is an object of the present invention to provide a bookmaker system that solves the above problems.

The bookmaker system of the present invention is
A bookmaker system that allows betting at any timing on bet targets that can occur during an event, in which odds change with the passage of time,
a storage unit that stores a user account associated with the funds used for the bet for each user;
a betting information reception unit that receives betting information including a bet target and a bet amount placed by the user;
a cancellation reception unit that receives cancellation of the bet by the user during the event;
a cancellation control unit that, when the cancellation acceptance unit accepts cancellation of the bet, adds a refund amount calculated according to a refund rate that varies according to the situation of the event, to the resource of the user account of the user;
characterized by having

According to the above configuration, in a bookmaker that allows betting at any time during an event in which the odds change over time, if the user sends voting information to the bookmaker management server, the canceled amount will be refunded at any time according to the payout rate. The bet is paid out immediately, and the payout amount can be used to bet again on events whose odds change over time.

Also, in the bookmaker system of the present invention,
It may further include a presentation unit that presents information to the user based on the payout rate that fluctuates during the event.

According to the above configuration, since a variable payout rate is presented to the user, cancellation can be executed when the payout rate is desired by the user.

It is an explanatory view showing a schematic structure of the present invention. FIG. 10 is an explanatory diagram of a real-time bet; It is a block diagram showing an electrical configuration of the bookmaker system. It is a figure which shows an example of the display screen displayed on a user terminal device. FIG. 10 is an explanatory diagram of a voting information table; FIG. It is a flow chart of voting information reception processing. It is a flow chart of cancellation acceptance processing.

A terminal device of the present invention will be described based on the drawings.

As shown in FIG. 1, the bookmaker system 1 of the present embodiment temporarily changes the bet amount to A refund can be made according to the payout rate, and the refunded bet amount can be used as funds for betting during the same event. The payout rate is changed in real time according to the situation of the event to be betted on. In the following description, refunding the bet amount may be simply referred to as canceling.

In this embodiment, the “event” is exemplified by a soccer game, but is not limited to this. For example, it may be a match of another sport such as baseball. Also, the event elements that affect the bet results refer to elements that affect the final outcome of the event, such as players, referees, and equipment such as balls moved by players. It should be noted that an "event" means an event that can be a bet target, such as a process or action in which some kind of final result appears. Events include matches and games such as soccer and baseball that are executed by humans and computers, as well as changes in the natural world such as national elections and local elections, movements of animals and plants, and events that do not involve humans or computers. There may be. An event may be a phenomenon that can occur within an event as described above. Events that can occur in such an event are, for example, if it is a soccer event, whether or not a PK will occur, whether or not the generated PK will be successful, and which team will score first. It is an event that occurs at any time in the game as an event such as

Next, a schematic functional configuration of the bookmaker system 1 will be described. Specifically, the bookmaker system 1 has a plurality of user management terminals 20, a bookmaker management server 680, and an event information providing server 710, which are capable of data communication via the communication network 400. It is connected.

The event information providing server 710 has a function of acquiring event information of an event in which a betting target is set and providing the event information to the bookmaker management server. Event information is information related to the final result of an event. For example, in the case of a soccer match, the event information includes the score of each team, the number of goals scored by each player, the occurrence of PKs, the success or failure of PKs, etc. Such event-related information is sequentially sent to the bookmaker management server 680 will be provided to

The user terminal device 20 is a device for using various procedures and contents provided by the bookmaker system 1 . By transmitting voting information to the bookmaker management server 680 via the communication network 400 using the user terminal device 20, the user can perform various procedures such as betting on the bet target set for the event, view content, and the like. made possible to do.

Note that the user terminal device 20 of the present embodiment is a smart phone having a display 201, but may be either a portable type or a stationary type. The display 201 is provided with a touch panel as a user interface and functions as an input device. Examples of portable user terminal devices 20 include mobile information devices such as portable computers, laptop computers, tablet personal computers, handheld personal computers, PDAs (Personal Data Assistants), and smart watches.

Specifically, the bookmaker management server 680 has an event setting section 686 , an odds management section 687 , a user management section 688 and a content provision section 689 . The event setting unit 686 has a function of setting a bet target for an event to be bet on. Specifically, an operator who operates a bookmaker sets bet targets and odds for the bet targets. The odds set by the event setting section 686 are provided by the odds management section 687 .

The odds management unit 687 has a function of managing odds for betting objects. The odds management unit 687 individually determines odds for each bet target, which is an event belonging to the event, according to the bet target situation transmitted from the event information providing server 710 . For example, the odds are based on past records, player status, betting status (number of bets on bet targets and total bet amount), home or away, game status (scores, injured players, ejected players, etc.). Based on real-time information, it fluctuates in real-time with a unique program. Specifically, the odds management unit 687 determines the odds of the bet target before the start of the event, and further determines the odds according to the progress of the event as described above. For example, if the event is a soccer match, the odds management unit 687 changes the odds of the bet objects belonging to this event even during the match, according to the shot chance, the number of shots, the score, and the like. Of course, the change in odds is determined by the operator and may be set manually, but preferably automatically by a program that executes a predetermined formula. Further, some odds may be automatically determined and other odds determined by the operator. Odds that vary for each betting object are preferably reproducible based on the progress history of past events. The odds management unit 687 sequentially provides information on changing odds to the event setting unit 686 .

Note that the odds management unit 687 may manage odds provided by a system other than the bookmaker system 1 . That is, the odds management unit 687 may sequentially and cumulatively store odds provided from an external system having a function of determining odds from before the event to during the event.

When the user places a bet using the user terminal device 20, the user terminal device 20 stores the odds of the bet target at the timing of the bet. When the bet target is a prize, the odds stored in the user terminal device 20 are approved by the odds management unit 687, and the prize amount is calculated and paid out to the user.

The user management unit 688 has a function of managing users who log in using the user terminal device 20 . The user management unit 688 manages login information for users to log in, information about bets made by users, funds of users, and the like. The information about the bet is, for example, bet timing information such as the bet target of the event the user bets on, the bet amount, the date and time of the bet, and seconds, and is stored in the storage unit 685 to be described later. The user's funds are information indicating the amount of funds that the user bets. When the user places a bet, the bet amount is subtracted from the funds, and when the bet target that the user bets wins, the winning amount corresponding to the winning is added to the funds. In this way, the storage unit 685 stores user accounts associated with funds used for betting for each user. Deposits and withdrawals of funds are made through systems of financial institutions, card settlement companies, virtual currency trading companies, electronic wallet companies, etc., which are not shown.

The user management unit 688 accepts a request regarding a user account from the user terminal device 20 and registers or changes the user account information in the storage unit 685 . User account requests received by the user management unit 688 include user account registration, login, user name change, password change, deposit to user account, withdrawal from user account, confirmation of user bet results, and the like. are mentioned. The user management unit 688 stores the request information related to the user account in the storage unit 685 in association with the date and time when the request was received.

The content providing unit 689 has a function of providing the user terminal device 20 with the betting targets and video data of the event set by the event setting unit 686 . A betting target for an event provided to the user terminal device 20 is set as a betting timeline from before the start of the event to during the event via the touch panel of the user terminal device 20, etc., and bets and cancellations of the bets are provided. be done. Specifically, on the user terminal device 20, the odds for each betting target are displayed in real time in synchronization with the odds provided by the odds management unit 687. FIG. As a result, the bookmaker system 1 is configured to be able to bet at an arbitrary timing on a bet target that can occur during an event whose odds change over time.

The bookmaker management server 680 also has a voting information reception section 681 , a cancellation reception section 682 , a cancellation control section 683 and a storage section 685 .

The voting information receiving unit 681 has a function of receiving voting information from the user terminal device 20 by betting by the user. Specifically, at the time of betting, the user ID, bet target, odds, bet amount, and the like are transmitted from the user terminal device 20 to the betting information receiving unit 681 as betting information. In addition, if special conditions are applied to the bet, the special conditions, if there is content selected by the user regarding the bet, the content of the user's selection, and if commissions or fees are collected, the type A monetary amount may be included in the voting information. When such voting information is received, the voting information accepting unit 681 adds a bet ID for identifying each bet to the voting information and stores it in the storage unit 685 . If the event to be bet on has already started, the voting information accepting unit 681 may add the event start date and time to the voting information and store it. Thus, voting information is generated for each bet.

The cancellation accepting unit 682 has a function of accepting bet cancellation by the user during the event. Specifically, at the time of cancellation, a user ID, a bet ID, a cancellation amount, and the like are transmitted from the user terminal device 20 to the cancellation reception unit 682 as cancellation information.

When the cancellation acceptance unit 682 accepts the cancellation of the bet, the cancellation control unit 683 adds the refund amount calculated according to the refund rate that varies according to the situation of the event to the resource of the user's user account.

In this way, the bookmaker system 1 is configured to allow bets to be placed at any timing on bet targets that may occur during an event, where the odds change over time. a storage unit 685 that stores a user account associated with a bet, a betting information reception unit 681 that receives bet information including bet objects and bet amounts placed by users, and a bet cancellation by users during an event. A cancellation control unit 683 that, when the cancellation acceptance unit 682 accepts a bet cancellation, adds the refund amount calculated according to the refund rate that varies according to the situation of the event, to the resource of the user account of the user. and have

According to the above configuration, in a bookmaker that allows betting at any time during an event in which the odds change over time, if the user sends voting information to the bookmaker management server, the canceled amount will be refunded at any time according to the payout rate. The bet is paid out immediately, and the payout amount can be used to bet again on events whose odds change over time.

In addition, in the present embodiment, the content providing unit 689 in the bookmaker system 1 functions as a presenting unit that presents to the user information based on payout rates that fluctuate during the event. Specifically, every time the refund rate changes, the content providing unit 689 presents information based on the refund rate to the user terminal device 20 by email notification, web content update, push notification, etc. You may let As a presentation form in the user terminal device 20, in addition to the screen display, it may be timed by voice. The information based on the refund rate includes the refund rate, the refund amount based on the refund rate, and the like.

According to the above configuration, since a variable payout rate is presented to the user, cancellation can be executed when the payout rate is desired by the user.

As shown in FIG. 2, real-time bets can be continuously placed via the user terminal device 20 from before the start of the event to during the event, and the odds are changed according to the timing of betting on the event. It is what you get.

To give a specific example, if the first bet target as a specific event is victory or defeat of a soccer game, odds are determined for the outcome of the game such as victory or defeat, draw, point difference, etc. of the soccer game. The odds can be changed from the pre-betting period before the start of the game to the running betting period after the start of the game. The user can place a bet using the user terminal device 20 while checking the odds during the entire betting period. A bet can be made any number of times during the betting period, and can be made with the odds at each betting timing. When the game ends and the execution result of the game is determined, the winning amount for the first bet object based on the bet amount and the odds at the timing of the user's bet is paid to the user who wins the bet.

It should be noted that one or more bet target events may be executed at different timings in relation to a specific event. For example, if the specific event is a soccer game, the number of fouls and penalty kick events during this soccer game occur randomly and cannot be controlled by the sportsbook management server. In real-time betting, the management server sets odds according to the game situation for each of these randomly occurring events, and is configured so that it is possible to bet on that event.

To give a specific example, during the "running bet period", which is the period from the start of the game to the end of the game, multiple events that are different bet targets from the first bet target event occur at any time, and the result is may be determined. For example, the number of shots during the period from the elapse of a predetermined time after the start of the game to the end of the first half is the event for the second bet. During the execution of the event for the second bet, the odds for the second bet are displayed and bets are made available separately from the bet for the first bet. Then, the number of shots at the end of the first half is taken as the event execution result, and the presence or absence of winning is determined. A winning amount for the second bet object is paid to the user who wins the bet, according to the bet amount and the odds.

The winning amount may be paid at the end of each event, at the time when the execution result of the event that is the execution result of the first bet target is finally known, or at the user's request. It may be paid at the timing of betting, but it is configured so that it can be paid to the user immediately at the stage when the result of each bet target is determined, and can be used as funds for betting on other events. is preferred.

Further, in this embodiment, as described above, the bet can be canceled once, and the refunded bet amount can be used as funds for betting during the same event. For example, the user can cancel the bet on the first bet and use the refund amount to place a bet on the second bet.

Specifically, first, assume that the user bets $100 on the first betting object. In this case, the user can cancel and refund $100 during the pre-betting period of the event or the ongoing betting period. In this embodiment, the payout rate for calculating the payout amount is determined based on the remaining time until the result of the betting target is determined and the odds that change with the passage of time. As described above, the odds change according to the progress of the event over time, and serve as an indicator of the current advantage or disadvantage of the bet target. In addition, as the remaining time until the result of the bet target is determined gets closer, the room for the result to fluctuate becomes smaller, so the absolute value of the payout rate approaches 1.0. Specifically, a payout rate in the range of -1.0 to 1.0 is applied to the betting object according to the current odds. When the payout rate is positive, the payout amount is obtained by multiplying the bet amount by the bet amount minus 1.0 and the payout rate. Further, when the payout rate is negative, the payout amount is obtained by adding the bet amount multiplied by the payout rate to the bet amount. For example, as shown in FIG. 2, when $100 is betted on a betting object with odds of 2, and the betting object pays out at an advantageous timing (with a payout rate of 0.8), $180 will be added to the original funds as a refund amount. On the other hand, in the same case, if the bet object is paid out at an unfavorable timing (with a payout rate of -0.8), $20 will be added to the original funds as the payout amount. Note that the payout rate is not limited to this, and may be calculated in any manner.

In addition, the refund amount is immediately added to the resource of the user account, and additional bets can be made using this as the resource. FIG. 2 shows that the user has placed a bet on the second bet target using the cancellation amount.

In this way, after the user bets on the first bet object, if another second bet object occurs during the event, the bet amount bet on the first bet object is refunded according to the payout rate, and the second bet object is returned. It is possible to use it as a source of funds.

As shown in FIG. 3, the user terminal device 20 includes a CPU 101, a ROM 102, a RAM 103, a flash memory 104, an operation button 108, a power switch 109, a bus line 110, a network I/F 111, a camera 112, an imaging device I/F 113, a microphone 114, a speaker 115, a sound input/output I/F 116, a display I/F 117, a sensor controller 118, a short-range communication circuit 119, and an antenna 119a of the short-range communication circuit 119.

Also, the bookmaker management server 680 and the event information providing server 710 are so-called computers equipped with a CPU 1101 , a ROM 1102 , a RAM 1103 , a storage device 1104 such as a hard disk drive, and a network I/F 1111 .

A CPU (Central Processing Unit) 101 and a CPU 1101 function as a main component of the controller and control the operation of the first application system 100 as a whole. ROMs (Read Only Memory) 102 and ROM 1102 store programs used to drive the CPUs 101 and 1101, such as IPLs (Initial Program Loaders).

A RAM (Random Access Memory) 103 and a RAM 1103 are used as work areas for the CPU 101 and the CPU 1101 . The flash memory 104 stores various data such as application programs, communication programs, image data, and sound data. The operation button 108 is a button that is operated when initializing the user terminal device 20, for example. The power switch 109 is a switch for switching ON/OFF of the power of the user terminal device 20 .

The storage device 1104 functions as a database and stores application data for each of multiple user terminal devices 20 . The bookmaker management server 680 appropriately refers to the database of the storage device 1104 and returns a response to a request from the application program of the user terminal device 20 . The event information providing server 710 sequentially returns event information responses to requests from the bookmaker management server 680 .

A network I/F (Interface) 111. A network I/F 1111 is an interface for data communication using a communication network such as the Internet. The camera 112 is a type of built-in imaging means for imaging a subject and obtaining image data under the control of the CPU 101 . The imaging device I/F 113 is a circuit that controls driving of the camera 112 . The microphone 114 is a type of built-in sound collecting means for inputting sound. The sound input/output I/F 116 is a circuit for processing input/output of sound signals between the microphone 114 and the speaker 115 under the control of the CPU 101 . A display I/F 117 is a circuit that transmits image data to the display 2 under the control of the CPU 101 . The display 2 is provided on the front surface of the housing 11 . The sensor controller 118 is a circuit that receives input from the touch panel 5 provided on the display 2 . The short-range communication circuit 119 is a communication circuit such as NFC (Near Field Communication) (registered trademark) or Bluetooth (registered trademark). A bus line 110 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 101 .

Next, an example of a display mode displayed on the display 201 of the user terminal device 20 in the bookmaker system 1 will be described.

FIG. 4 shows a cancel screen 2010 on which information on a bet target on which the user has bet is displayed. The user operates the user terminal device 20 to transition the screen from the list screen (not shown) of the betting targets that the user has made to the cancel screen 2010 . On the cancel screen 2010, the user can cancel the displayed bet target. The bet target screen is content provided by the bookmaker management server 680 (content providing unit 689), and is displayed when the user terminal device 20 periodically acquires the content.

The cancel screen 2010 is provided with an event information area 2010a, an odds display portion 2010b, and a cancel execution button 2010c. Details of the event are displayed in the event information area 2010a. In this embodiment, the content of the event, the bet target the user is betting, the odds when the user bets, and the bet amount are displayed, but the present invention is not limited to this. The odds display portion 2010b is a display area in which the current bet target odds are displayed. The odds display section 2010b is updated in real time based on information from the bookmaker management server 680. FIG. The cancel execution button 2010c is an area in which a refund amount to be refunded by executing the cancellation, the remaining time until the result of the betting target is determined, and a refund rate determined based on the current odds are displayed. It is an input interface for executing cancellation. The refund amount and refund rate displayed on the cancel execution button 2010 c are updated in real time based on information from the bookmaker management server 680 .

When the cancel execution button 2010c of the cancel screen 2010 is operated, the odds display section 2010b and the cancel execution button 2010c are hidden, and the cancellation result display area 2010d is displayed instead. The cancellation result display area 2010d displays the refund amount and the fact that the refund has been executed.

Next, the data table stored in the storage device 1104 of the bookmaker management server 710 will be described.

FIG. 5 is a diagram showing a voting information table. The betting information table is a data table to which data for each bet is added each time the bookmaker management server 680 receives betting information from the user terminal device 20 , and is stored in the storage device 1104 of the bookmaker management server 680 . As shown in FIG. 3, the voting information table includes a user ID column, a bet ID column, a bet date and time column, a bet object column, an odds column, a bet amount column, an event start date and time column, and an event end date and time. It has a column, a result column, a prize column, and a result confirmation date and time column.

The user ID column stores a user ID that identifies a user who has placed a bet. A bet ID for identifying a bet is stored in the bet ID. The bet ID is an identification number assigned when the bookmaker management server 680 receives the voting information. The date and time when the bet was placed is stored in the bet date and time column. In this embodiment, the date and time stored in the betting date and time column is the date and time indicated by the system clock of the bookmaker management server 680 at the timing at which the bookmaker management server 680 received the betting information. Note that this is not a limitation, and the date and time indicated by the system clock of the user terminal device 20 that transmitted the voting information at the time of transmission may also be used. Also, a plurality of these may be stored.

The bet target field stores the bet target on which the bet is placed. The bet target column stores an identification number that identifies the bet target, but is not limited to this, and may be a team name, a player name, or the like on which a bet was placed. The odds column stores the odds at the timing when the user places a bet. That is, the odds transmitted from the user terminal device 20 are applied. The bet amount column stores the bet amount bet on the bet object.

The event start date and time column stores the date and time when an event for determining a bet target was started. The event end date and time column stores the date and time when the event for determining the bet target was finished. The result column stores WIN or LOSE, which is the bet result. In addition, in the result column, when the bet is refunded, information indicating that the bet was refunded and the refund rate used for the refund are stored. The prize column stores the prize amount to be paid to the user. In addition, when the bet is refunded, the refunded amount is stored in the prize column. The date and time when the user confirmed the bet result is confirmed in the result confirmation date and time column. The last update date and time column stores the timing at which data was added to the voting information table and the timing at which each column of the voting information table was updated.

Next, referring to FIG. 6, a program for voting information reception processing executed in the bookmaker system 1 will be described.

First, when a bet request is made in the user terminal device 20 (SQ11), voting information is transmitted from the user terminal device 20 to the bookmaker management server 680. FIG. The betting information to be sent includes user ID, betting date and time, betting target, odds, and betting amount.

When receiving the voting information, the CPU 1101 of the bookmaker management server 680 assigns a bet ID to the bet (S11). Then, the CPU 1101 of the bookmaker management server 680 adds the numbered bet ID and the bet date and time when the bet was received to the voting information, and adds it to the voting information table (see FIG. 5) of the storage device 1104 of the bookmaker management server 680. ) (S12). Then, the CPU 1101 of the bookmaker management server 680 updates the user's resource stored in the user account with the value obtained by subtracting the bet amount of the requested bet (S13). Then, the CPU 1101 of the bookmaker management server 680 makes a reception completion response to the bet request from the user terminal device 20 (S14). Specifically, the CPU 1101 of the bookmaker management server 680 responds with voting information including a bet ID as bet completion information.

When receiving the bet completion information, the user terminal device 20 displays the bet completion information (not shown) on the display 201 (SQ12).

Next, with reference to FIG. 7, a program for cancellation reception processing executed by the CPU 1101 of the bookmaker management server 680 in the bookmaker system 1 will be described.

First, when a cancellation request is made on the cancellation screen 2010 (see FIG. 4) of the user terminal device 20 (SQ41), cancellation information is transmitted from the user terminal device 20 to the bookmaker management server 680. FIG. The transmitted cancellation information includes a user ID, a bet ID indicating a bet target, current odds, and a payout rate.

Upon receiving the cancellation information, the CPU 1101 of the bookmaker management server 680 determines whether or not it is a period during which cancellation is possible (S41). Although not shown, in the case of a period during which cancellation is not possible, a message to the effect that cancellation is not possible may be transmitted to the user terminal device 20 and the user terminal device 20 may be caused to display the fact. If it is a period during which cancellation is possible, the CPU 1101 of the bookmaker management server 680 determines that the remaining time until the result of the betting target is determined, the current odds, and the payout rate calculated from the odds, which are included in the cancellation information, are correct. It is authenticated whether it is a thing (S42). Then, if the odds and the payout rate are correct, the CPU 1101 of the bookmaker management server 680 calculates the payout amount (S43).

Then, the CPU 1101 of the bookmaker management server 680 refers to the voting information table (see FIG. 5) and detects data matching the user ID and bet ID included in the cancellation information (S44). Then, the CPU 1101 of the bookmaker management server 680 updates the result column of the detected target data with the information indicating that the refund has been made and the refund rate, and further updates the prize column with the refund amount (S45). ).

Then, CPU 1101 of bookmaker management server 680 adds the refund amount to the resource of the user account stored in storage device 1104 (S46). Then, the CPU 1101 of the bookmaker management server 680 responds to the user terminal device 20 with result information including the fact that the cancellation was performed normally. (S42).

When receiving the result information from the bookmaker management server 680, the user terminal device 20 displays the result information on the display 201 (SQ42). That is, the bookmaker management server 680 causes the user terminal device 20 to display the cancellation result display area 2010 d on the cancellation screen 2010 .

Although the embodiments of the present invention have been described above, the specific examples are merely illustrated, and the present invention is not particularly limited. Moreover, the effects described in the embodiments of the present invention are merely enumerations of the most suitable effects resulting from the present invention, and the effects of the present invention are limited to those described in the embodiments of the present invention. is not.

In addition, in the above detailed description, the characteristic parts have been mainly described so that the present invention can be understood more easily. The present invention is not limited to the embodiments set forth in the foregoing detailed description, but may be applied to other embodiments and its scope of application is diverse. Moreover, the terms and usage used in this specification are used to describe the present invention precisely, and are not used to limit the interpretation of the present invention. In addition, it is believed that those skilled in the art can easily conceive of other configurations, systems, methods, etc. included in the concept of the present invention from the concept of the invention described herein. Therefore, the claims should be considered to include equivalent configurations within the scope of the technical idea of the present invention. In addition, the purpose of the abstract is to facilitate understanding of the technical content and essence of the application by the Patent Office, general public institutions, and engineers in this technical field who are unfamiliar with patents, legal terms, or technical terms. It is intended to make it possible to make a quick judgment through a thorough investigation. The Abstract, therefore, is not intended to limit the scope of the invention, which should be evaluated by the claims. In addition, in order to fully understand the purpose of the present invention and the unique effects of the present invention, it is desired that the description should be interpreted with sufficient consideration given to the literatures that have already been disclosed.

The foregoing detailed description includes computer-implemented processes. The above explanations and representations are provided for the purpose of most efficient understanding by those skilled in the art. As used herein, each treatment used to derive a result of 1 should be understood as a self-consistent treatment. In each process, transmission/reception, recording, etc. of electrical or magnetic signals are performed. Note that the operations in each process represent such signals as bits, values, symbols, characters, terms, numbers, etc., which are used merely for convenience of explanation. There is a need. In addition, the processing in each processing may be described in terms common to human behavior, but the processing described in this specification is basically executed by various devices. Also, other configurations required to perform each process are self-explanatory from the above description.

1 bookmaker system 20 user terminal device 201 display 680 bookmaker management server 710 event information providing server

Claims (2)

A bookmaker system that allows betting at any timing on bet targets that can occur during an event, in which odds change with the passage of time,
a storage unit that stores a user account associated with the funds used for the bet for each user;
a betting information reception unit that receives betting information including a bet target and a bet amount placed by the user;
a cancellation reception unit that receives cancellation of the bet by the user during the event;
a cancellation control unit that, when the cancellation acceptance unit accepts cancellation of the bet, adds a refund amount calculated according to a refund rate that varies according to the situation of the event, to the resource of the user account of the user;
A bookmaker system characterized by comprising: 2. The bookmaker system according to claim 1, further comprising a presentation unit that presents information to the user based on the payout rate that fluctuates during the event.

Images