JP2023070417A - bookmaker system - Google Patents

Abstract

To provide a bookmaker system and a bookmaker management method which can prevent a bet performed in a period in which reflection of change in a situation of progression of an event on odds is achieved from causing a disadvantage to a management side of a bookmaker and a user.SOLUTION: A bookmaker system 1 enables a bet to be performed at any timing in an event in which odds change over time, accepts odds resource information for determining the odds of a plurality of bet objects in the event from an exterior, determines the odds of the plurality of bet objects after change in the odds on the basis of the odds resource information, reflects the determined odds after the change on an interface for accepting the bet, and nullifies acceptance of the bet by the interface until reflection of the odds after the change on the interface is achieved after the odds resource information is accepted.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).

For example, the 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. ing.

U.S. Patent Application Publication No. 2014/0323207

However, bets made during the period until changes in the progress of the event are reflected in the odds do not correspond to the progress of the event. It could have been detrimental. For example, if the odds are greatly affected, such as when the score is tied in a soccer match, the odds immediately after that situation do not reflect that situation. By doing so, there was a possibility that the management side of the bookmaker and the user would be disadvantaged.

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

The bookmaker system of the present invention is
A bookmaker system that allows betting at any timing on a plurality of bet targets that may occur during an event, where the odds change with the passage of time,
a resource reception unit that externally receives odds resource information for determining the odds of the plurality of bet targets in the event;
an odds determination unit that determines odds after the change in the plurality of bet targets based on the odds resource information;
an interface reflection unit that reflects the changed odds determined by the odds determination unit on an interface for accepting the bet;
an interface disabling unit that disables acceptance of bets by the interface from when the resource receiving unit receives the odds resource information until the interface reflecting unit reflects the changed odds on the interface;
characterized by having

According to the above configuration, the interface for accepting bets is disabled from the time the odds resource information is accepted until the changed odds are changed based on the odds resource information. Accordingly, even if the user attempts to place a bet based on the change in the progress of the event, the user cannot place a bet until the odds match the change in the progress of the event. As a result, the user can bet with appropriate odds, and the management side of the bookmaker can be prevented from being unfairly disadvantaged.

The bookmaker management method of the present invention includes:
A bookmaker management method that enables betting at any timing on a plurality of bet targets that may occur during an event, the odds of which change with the passage of time,
externally receiving odds resource information for determining odds for the plurality of bet targets in the event;
Determining odds after changing the plurality of bet targets based on the odds resource information;
reflecting the determined odds after the change in an interface for accepting the bet;
disabling acceptance of bets by the interface from when the odds resource information is received until the interface reflection unit reflects the changed odds on the interface;
Bookmaker management method including.

According to the above configuration, the interface for accepting bets is disabled from the time the odds resource information is accepted until the changed odds are changed based on the odds resource information. Accordingly, even if the user attempts to place a bet based on the change in the progress of the event, the user cannot place a bet until the odds match the change in the progress of the event. As a result, the user can bet with appropriate odds, and the management side of the bookmaker can be prevented from being unfairly disadvantaged.

It is an explanatory view showing a schematic structure of the present invention. It is a block diagram showing an electrical configuration of the bookmaker system. FIG. 4 is an explanatory diagram showing an interface of the bookmaker system; FIG. 10 is an explanatory diagram of a voting information table; FIG. FIG. 10 is an explanatory diagram of an odds management table; It is a flow chart of odds change processing. It is a flow chart of voting information reception processing.

The bookmaker system of the present invention will be explained based on the drawings.

As shown in FIG. 1, the bookmaker system 1 of the present embodiment is configured such that bets are invalidated while the input source (odds resource information) of match situation data is switched.

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 and a bookmaker management server 680, which are connected via a communication network 400 so as to be capable of data communication. Further, the bookmaker management server 680 is connected to the event information providing server 710 via the communication network 400 so as to be capable of data communication.

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. That is, the event information providing server 710 provides the bookmaker system 1 with event information, which is odds resource information for determining odds of a plurality of bet targets in the event, from outside the bookmaker system 1 . In other words, the event information is odds resource information for determining odds for a plurality of bet objects related to the event, and is information related to the final outcome of the plurality of bet objects. 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., and the event information related to such events is sequentially provided by the bookmaker. It will be provided to the management server 680 . As described above, in the present embodiment, the event information is information indicating the game situation for determining the odds, but is not limited to this. For example, the event information provided by the event information providing server 710 may be the odds themselves after the change of the bet target.

The user terminal device 20 is a device for using various procedures and contents provided by the bookmaker system 1 . By connecting the user terminal device 20 to the bookmaker management server 680 via the communication network 400, the user can perform various procedures such as betting on the bet target set for the event, view content, and the like. made possible. That is, the user terminal device 20 is provided with an interface for accepting a bet by the bookmaker management server 680 . A user makes a bet or the like via an interface presented on the user terminal device 20 .

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.

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. The bet target and the odds for the bet target are set by the operator who operates the bookmaker. 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 betting target, which is an event belonging to the event, according to the event information indicating the status of the betting target transmitted from the event information providing server 710 . The event information is received by a resource reception unit 683, which will be described later. 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 determined automatically 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 . In this way, it is possible to change the odds of each bet target according to the progress of 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 bet information is, for example, bet timing information such as the bet target, the bet amount, the date and time of betting, and seconds for the event that the user has bet on. The user's funds are information indicating the amount of money that the user makes a bet with. When the user places a bet, the bet amount is subtracted from the funds, and when the bet target the user bets wins, the winning amount corresponding to the winning is added to the funds. Deposits and withdrawals of funds are carried out through systems of financial institutions, card settlement companies, virtual currency trading companies, electronic wallet companies, etc. (not shown).

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 . That is, the content providing unit 689 provides the user terminal device 20 with an interface that enables betting on an event betting target and cancellation of the betting via a touch panel or the like. On the user terminal device 20, the odds for each betting object are displayed in real time while changing 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 any timing during an event in which the odds change over time.

The bookmaker management server 680 also has a voting information reception unit 681, a voting information management unit 682, a resource reception unit 683, an interface reflection unit 684, an interface invalidation unit 685, and a storage unit 692. .

The betting information accepting unit 681 has a function of accepting betting information including a betting target, odds, and bet amount bet by the user. Specifically, at the time of betting, the user ID, bet target, odds, bet amount, etc. are transmitted from the user terminal device 20 to the bookmaker management server 680 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 692 . Note that, 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. In this way, voting information is generated for each bet and stored in the storage unit 692 as one piece of data for each bet.

The voting information management unit 682 stores information such as when the event period is updated, when the result of a bet made by the user is output, when the result of the bet made by the user is confirmed by the user, and so on. 692 has the ability to update the voting information stored. Specifically, when the event period is updated, the voting information management unit 682 adds the event start date and time and the event end date and time to the voting information stored in the storage unit 692 . Also, when the result of a bet made by the user is output, the betting information management unit 682 adds the bet result, the prize amount, etc. to the betting information stored in the storage unit 692 . Also, when the result of a bet made by the user is confirmed by the user, the voting information management unit 682 adds the date and time of the confirmed timing to the voting information stored in the storage unit 692 .

The resource reception unit 683 receives event information, which is odds resource information for determining odds for a plurality of bet targets in an event, from the event information providing server 710 . The event information is not limited to information indicating the game situation of the event, and may be information indicating the changed odds themselves. In that case, the resource reception unit 683 transmits information indicating the odds themselves to the odds management unit 687 . The odds management unit 687 that receives the information indicating the odds themselves transmits the odds indicated by the information to the content providing unit 689 . Further, the resource reception unit 683 transmits information indicating reception of the event information to the interface invalidation unit 684 .

The interface reflection unit 684 has a function of reflecting the determined odds after the change on an interface for accepting a bet. The post-change odds are determined by the odds management unit 687 functioning as an odds decision unit that determines post-change odds for a plurality of bet targets based on the event information as the odds resource information, as described above.

The interface disabling unit 685 has a function of disabling acceptance of bets through the interface from when the resource receiving unit 683 receives the odds resource information until the interface reflecting unit 684 reflects the post-change odds on the interface. As described above, an interface for accepting bets is provided to the user terminal device 20 by the content providing unit 689 . Then, the interface is displayed on the user terminal device 20, and input to the interface is accepted. "Disabling acceptance of bets through the interface" may mean disabling input to the interface in the user terminal device 20, or disabling acceptance of bets in the bookmaker management server 680. can be anything. Here, invalidity includes cancellation after acceptance. That is, the interface invalidation unit 685 may invalidate the reception by the voting information reception unit 681, or may invalidate the vote received by the voting information reception unit 681 later.

Further, the interface disabling section 685 may determine whether to disable acceptance of bets through the interface according to the rate of change in odds. For example, even if the resource reception unit 683 receives event information that is odds resource information, if the odds do not change or if the odds fluctuation rate is less than a predetermined value, acceptance of bets through the interface does not need to be disabled. good.

The storage unit 692 has a function of storing odds resource information, voting information, an interface provided to the user terminal device 20, and the like.

In this way, the bookmaker system 1 can bet at arbitrary timing on a plurality of bet targets that can occur during an event, the odds of which change over time. Then, the bookmaker system 1 includes a resource reception unit 683 that receives odds resource information for determining odds for a plurality of bet targets in an event from the outside, and a resource reception unit 683 that determines odds after change for the plurality of bet targets based on the odds resource information. an interface reflection unit 684 for reflecting the changed odds determined by the odds management unit 687 on the interface for accepting bets; and an interface invalidation section 685 that invalidates acceptance of bets through the interface until the interface reflects the odds after the change in the interface.

In other words, the bookmaker system 1 having the above units implements a bookmaker management method that implements the functions (processes) executed by the units. According to the configuration of the bookmaker system 1 or the bookmaker management method realized by the bookmaker system 1, the interface for accepting bets receives the odds resource information and then converts the changed odds based on the odds resource information. Disabled until changed. Accordingly, even if the user attempts to place a bet based on the change in the progress of the event, the user cannot place a bet until the odds match the change in the progress of the event. As a result, the user can bet with appropriate odds, and the management side of the bookmaker can be prevented from being unfairly disadvantaged.

As shown in FIG. 2, 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 image sensor 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 an interface display mode displayed on the display 201 of the user terminal device 20 in the bookmaker system 1 will be described.

FIG. 3 is a bet screen for the user to bet on an event. The bet screen is provided with an event status display portion 2012, an event bet target display portion 2013, and a bet target display portion 2014 that displays events that can occur in the event. An event that can occur in an event means an event that can be another betting target different from the betting target of the event itself that can occur during the event.

The event status display portion 2012 displays the current status of the event, which can be used as a reference for the user to decide whether to place a bet. The bet object display portion 2013 of the event displays bet object buttons 2010 that indicate bet objects regarding the result of the event in the form of buttons. The user can place a bet by touching the bet object button 2010 of the bet object on which the user desires to bet. The betting target is displayed with odds that change over time.

A bet object button 2011 is provided in the bet object display portion 2014 of events that can occur in the event. The bet target button 2011 for events that can occur in the event displays bet targets related to the outcome of events that can occur in the event in the form of buttons. Odds that change over time are displayed on each of the bet target buttons 2011 of events that can occur in the event. The user can place a bet on an event that can occur in the event by touching the bet target button 2011 of the event that can occur in the event for which the user wishes to bet.

Here, an event that can occur in an event is, for example, in the case of soccer, events that occur in the game, such as whether a specific player will score a goal or which team will score first. is a bet target. The event element display button is displayed when the betting target of an event that can occur in the event is related to a specific event element.

For example, in this embodiment, as shown in the left part of FIG. 3, a case where an event related to odds fluctuation occurs will be described. In this case, as shown in the central part of FIG. 3, on the bet screen, which is an interface for placing a bet, the bet target button 2010 and the bet target button 2011 for accepting the user's bet are grayed out, and the touch operation is disabled. set to disabled. Then, as shown in the right part of FIG. 3, after the event related to the change in the odds is reflected in the odds, the display of the bet object button 2010 and the bet object button 2011 is restored, and the touch operation is disabled. Re-enabled.

Next, the data table stored in the storage device 1104 of the bookmaker system 1 will be explained.

FIG. 4 is a diagram showing a voting information table. The voting information table is a data table to which data for each bet is added each time voting information is received from the user terminal device 20 . As shown in FIG. 4, the voting information table includes a user ID column, a bet ID column, a bet date and time column, a bet target column, an odds column, a bet amount column, an event start date and time column, and an event end date and time. column, result column, award column, and 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 betting information date and time column stores the date and time when the bet was made. 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. However, the present invention is not limited to this, and may be 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, or both 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 made. 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. A bet result is stored in the result column. The prize column stores the prize amount to be paid to the user. The date and time when the user confirmed the bet result is confirmed in the result confirmation date and time column.

For example, among the data stored in the betting information table, bets placed during a period when acceptance of bets through the interface was disabled may be invalidated. Further, this may realize invalidation of acceptance of bets.

FIG. 5 is a diagram showing an odds management table. Data of the odds management table is created or updated each time event information, which is odds resource information for determining odds for a plurality of bet targets in an event, is received from the event information providing server 710, and the odds after change and the interface are changed. This table manages the invalid period.

As shown in FIG. 5, the odds management table has a bet target column, pre-change odds, post-change odds, invalid start date and time, and invalid end date and time. The bet target column stores bet targets that are objects of odds fluctuation. The bet target field may be one data for each bet target and updated, or may be newly created each time the odds resource information is received. The column of odds before change and the column of odds after change store odds before change and odds after change, respectively. The invalid start date and time stores the time when the event information was received. The invalid end date and time stores the date and time when the changed odds are reflected in the interface. The odds management table is used to update the odds of the interface.

Next, referring to FIG. 6, a program for odds variation processing executed by the CPU 1101 of the bookmaker management server 680 in the bookmaker system 1 will be described.

First, when event information, which is odds resource information, is transmitted from the event information providing server 710 (SS11), the CPU 1101 of the bookmaker management server 680 receives the event information (S11), and immediately after that, disables the interface ( S12) is performed. Specifically, as shown in the central part of FIG. 3, the CPU 1101 provides the user terminal device 20 with an interface that disables the operation of the buttons (bet target buttons 2010 and 2011) for placing bets in the content. .

Then, the CPU 1101 of the bookmaker management server 680 invalidates bet acceptance (S13). Disabling bet acceptance is, for example, turning on a flag indicating that bet acceptance is being disabled (hereinafter also referred to as a bet acceptance invalidation flag) in a predetermined area of the storage device 1104 of the bookmaker management server 680 .

Based on the received event information, the CPU 1101 of the bookmaker management server 680 determines the odds after the change of the bet target related to the event of the event information (S14). Even if the odds do not change, the CPU 1101 of the bookmaker management server 680 confirms that the odds do not change. The odds after the change are stored in the odds management table (see FIG. 5) together with the odds before the change.

Then, the CPU 1101 of the bookmaker management server 680 reflects the changed odds on the interface provided to the user terminal device 20 (S15). That is, the data referred to by the interface is updated so that the changed odds are displayed when the user terminal device 20 presents the interface.

Then, the CPU 1101 of the bookmaker management server 680 re-enables the bet acceptance disabled in step S13 (S16). Specifically, the bet reception invalidation flag in a predetermined area of the storage device 1104 of the bookmaker management server 680 is turned off, and the current time is stored in the invalid end date and time of the odds management table (see FIG. 5).

Then, the CPU 1101 of the bookmaker management server 680 checks whether the accepted bet has been made within the invalid period (S17). That is, the CPU 1101 of the bookmaker management server 680 checks whether the bet dates of all bets in the betting information table are outside the invalid period of the odds management table. Although not shown, if there is a bet whose bet date is between the invalid start date and time and the invalid end date and time, the bet may be canceled.

After that, the CPU 1101 of the bookmaker management server 680 activates the interface (S18). Specifically, as shown in the right part of FIG. 3, the CPU 1101 enables the operation of buttons (bet target buttons 2010 and 2011) for betting in the content, and the interface is updated to the post-change odds. is provided to the user terminal device 20 .

Next, referring to FIG. 7, a program for voting information reception processing executed by the CPU 1101 of the bookmaker management server 680 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 the CPU 1101 of the bookmaker management server 680 receives the voting information from the user terminal device 20, it determines whether or not acceptance of the bet at the time of reception is valid (S21). That is, it is determined whether or not the bet acceptance invalidation flag, which is turned ON in step S13 of the odds variation process (see FIG. 6) and set to OFF in step S16, is ON.

When the bet acceptance invalidation flag is OFF (S21: NO), the CPU 1101 of the bookmaker management server 680 assigns a bet ID to the bet (S22). 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 the data to the voting information table (FIG. 4) of the storage device 1104 ( S23).

Then, the CPU 1101 of the bookmaker management server 680 responds to the bet request from the user terminal device 20 (S24). Specifically, when the CPU 1101 of the bookmaker management server 680 performs the processing of steps S22 and S23 and accepts a bet, it responds with voting information including a bet ID as bet completion information. If the acceptance is invalid (S21: YES), the CPU 1101 of the bookmaker management server 680 responds that the bet has not been accepted as bet completion information.

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

As described above, in the present embodiment, as a method of disabling acceptance of bets through the interface when the odds change, first, operation of the interface (bet target button 2010, bet target button 2011) in the user terminal device 20 is disabled. , secondly, invalidate acceptance of bets in the bookmaker management server 680; We use three types of invalidation from However, it is not limited to this, and may be realized using any one of them, or may be realized using two or more of them.

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. isn't it.

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. Further, other configurations required for performing 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 a plurality of bet targets that may occur during an event, where the odds change with the passage of time,
a resource reception unit that externally receives odds resource information for determining the odds of the plurality of bet targets in the event;
an odds determination unit that determines odds after the change in the plurality of bet targets based on the odds resource information;
an interface reflection unit that reflects the changed odds determined by the odds determination unit on an interface for accepting the bet;
an interface disabling unit that disables acceptance of bets by the interface from when the resource receiving unit receives the odds resource information until the interface reflecting unit reflects the changed odds on the interface;
A bookmaker system characterized by comprising: A bookmaker management method that enables betting at any timing on a plurality of bet targets that may occur during an event, the odds of which change with the passage of time,
externally receiving odds resource information for determining odds for the plurality of bet targets in the event;
Determining odds after changing the plurality of bet targets based on the odds resource information;
reflecting the determined odds after the change in an interface for accepting the bet;
disabling acceptance of bets by the interface from when the odds resource information is received until the interface reflection unit reflects the changed odds on the interface;
Bookmaker management method including.

Images