EP4213953A1 - Procédé, dispositif et programme d'ordinateur de gestion de gains et de suivi dans un système informatique multi-jeux - Google Patents
Procédé, dispositif et programme d'ordinateur de gestion de gains et de suivi dans un système informatique multi-jeuxInfo
- Publication number
- EP4213953A1 EP4213953A1 EP21785951.1A EP21785951A EP4213953A1 EP 4213953 A1 EP4213953 A1 EP 4213953A1 EP 21785951 A EP21785951 A EP 21785951A EP 4213953 A1 EP4213953 A1 EP 4213953A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- game
- ticket
- module
- winnings
- participation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims description 30
- 238000004590 computer program Methods 0.000 title claims description 5
- 238000012544 monitoring process Methods 0.000 title description 9
- 238000012545 processing Methods 0.000 claims description 4
- 230000005540 biological transmission Effects 0.000 claims description 3
- 238000004891 communication Methods 0.000 description 12
- 230000004044 response Effects 0.000 description 7
- 230000004048 modification Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000012360 testing method Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- A—HUMAN NECESSITIES
- A63—SPORTS; GAMES; AMUSEMENTS
- A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
- A63F3/00—Board games; Raffle games
- A63F3/08—Raffle games that can be played by a fairly large number of people
- A63F3/081—Raffle games that can be played by a fairly large number of people electric
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
- G07F17/32—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for games, toys, sports, or amusements
- G07F17/3244—Payment aspects of a gaming system, e.g. payment schemes, setting payout ratio, bonus or consolation prizes
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
- G07F17/32—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for games, toys, sports, or amusements
- G07F17/3225—Data transfer within a gaming system, e.g. data sent between gaming machines and users
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
- G07F17/32—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for games, toys, sports, or amusements
- G07F17/326—Game play aspects of gaming systems
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
- G07F17/32—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for games, toys, sports, or amusements
- G07F17/326—Game play aspects of gaming systems
- G07F17/3267—Game outcomes which determine the course of the subsequent game, e.g. double or quits, free games, higher payouts, different new games
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
- G07F17/32—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for games, toys, sports, or amusements
- G07F17/3286—Type of games
- G07F17/329—Regular and instant lottery, e.g. electronic scratch cards
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
- G07F17/42—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for ticket printing or like apparatus, e.g. apparatus for dispensing of printed paper tickets or payment cards
-
- A—HUMAN NECESSITIES
- A63—SPORTS; GAMES; AMUSEMENTS
- A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
- A63F3/00—Board games; Raffle games
- A63F3/06—Lottos or bingo games; Systems, apparatus or devices for checking such games
- A63F3/065—Tickets or accessories for use therewith
Definitions
- the invention relates to the field of game management in multi-game computer systems, in particular to the management of winnings and the monitoring of operations carried out during the life cycle of a game ticket.
- the invention applies in particular to games with an additional part and in particular to phygital games comprising participation in physical games such as scratch or lottery games followed by additional digital games such as raffle games or instant games.
- the additional game engine is therefore configured to exchange data with the main game engine, for example to receive data relating to a participation in the additional game and to transmit any winnings associated with this participation to the additional game, so that the main game engine can update a status of the ticket, calculate the total win associated with the ticket and allow the player to receive the win at the point of sale.
- the present invention aims in particular to solve these problems.
- the invention proposes an autonomous module for managing winnings and tracing tickets (real or virtual) that can interface with independent game modules (also called “game engines") for the purposes of coordinate their use with regard to a game ticket, making it possible in particular to identify additional games, to calculate winnings from several games and to monitor operations carried out during the life cycle of a ticket.
- independent game modules also called “game engines”
- the method according to the invention thus makes it possible to simplify the development of game modules and to avoid any direct interaction between them.
- the management of the winnings associated with the first game and the second game is centralized at the level of the winnings management module.
- the method further comprises a transmission to the second game module of a request for recording a participation in the second game, the recording request being associated with the identifier of the ticket .
- the method further comprises a transmission of the estimated gain, an instruction to pay the estimated gain and a modification of a status associated with the ticket.
- obtaining winning information includes querying a data structure received prior to participation in the game at the origin of the considered winning.
- obtaining winning information comprises transmitting a request comprising the identifier of the ticket to a game module and receiving the considered winning information.
- the method further comprises a determination of a status associated with the ticket.
- the estimation of a gain linked to the identifier of the ticket according to the gain information obtained is carried out according to the status associated with the ticket.
- the ticket is a ticket with a physical medium, in particular a scratch ticket, or a virtual ticket.
- a computer program implementing all or part of the method described above, installed on pre-existing equipment, is in itself advantageous, since it makes it possible to easily and quickly access and select an event likely to interest a user.
- the present invention also relates to a computer program comprising instructions for implementing the method described above, when this program is executed by a processor.
- This program can use any programming language (for example, an object language or other) and be in the form of interpretable source code, partially compiled code or fully compiled code.
- Another aspect relates to a non-transitory storage medium for a computer-executable program, comprising a set of data representing one or more programs, said one or more programs comprising instructions for, when executing said or more programs by a computer comprising a processing unit coupled operationally to memory means and to an input/output interface module, to execute all or part of the method described above.
- FIG. 1 illustrates an example of an environment in which the invention can be implemented according to particular embodiments
- FIG. 2 illustrates an example of logical architecture of a multi-game computer system according to particular embodiments of the invention
- FIG. 3 illustrates a first example of a time diagram of steps of the method of the invention according to a first particular embodiment
- FIG. 4 illustrates a second example of a time diagram of steps of the method of the invention according to a second particular embodiment
- FIG. 5 illustrates an example of steps implemented in a payment and traceability module according to a particular embodiment
- FIG. 6 illustrates an example of a device that can be used to implement, at least partially, embodiments of the invention, in particular the steps described with reference to Figures 3 to 5.
- a module for managing gains and monitoring operations linked to a ticket is implemented to interface different independent game modules.
- the winnings management and transaction monitoring module also makes it possible to offer a player, on the instructions of a first game module, to participate in one or more other games, different from the first.
- a ticket is here a pre-printed or partially pre-printed document, which may include a predetermined identifier, or a document created (or edited) during the recording of a participation in a game, to which an identifier is assigned.
- FIG. 1 illustrates an example of an environment in which the invention can be implemented according to particular embodiments.
- a user can buy a game ticket 100, for example at a point of sale also called POS (acronym for point of sale in English terminology).
- POS point of sale
- the ticket can be, for example, a ticket for a scratch game or a lottery ticket on which the player must select numbers.
- the ticket can be real or virtual. It typically includes a unique identifier. This identifier is used to know if the player has won or not and to determine a status.
- a ticket can be in a payable, already paid or blocked state, for example if it has been declared stolen.
- a ticket identifier comprises an identifier of the game with which the ticket is associated, the identifier of the game being coded or not.
- a player can go to a point of sale provided with a terminal 105 connected to a server 110 of the manager of the game in question, via a communication network 115.
- the terminal 105 comprises input means such as a keyboard or reading means such as a scanner or an RFID reader to obtain the identifier of a ticket. It also includes means for sending requests to the server 110, in particular requests comprising ticket identifiers.
- the terminal 105 can send a request to the server 110, including the identifier, to know the amount of the gain and the status of the ticket.
- the terminal receives the earnings and status information. If necessary, the point of sale can then pay the winnings to the player (it being noted that only amounts below a predetermined threshold are paid by the point of sale in cash, larger amounts being generally settled by the game manager by check or bank transfer).
- a player can use a personal device, for example a smartphone 120, a tablet 125 or a personal computer (not shown) to know the amount of winnings and the status of a ticket (a payment of winnings is made usually always at a point of sale).
- a personal device for example a smartphone 120, a tablet 125 or a personal computer (not shown) to know the amount of winnings and the status of a ticket (a payment of winnings is made usually always at a point of sale).
- a specific application or a web interface can also be used to offer the player to participate in a second game. Indeed, after having transmitted a result of a participation in a first game linked to the ticket in question, or simultaneously, the server 110 can transmit an indication that a possibility is offered to the player, holder of the ticket in question, to participate in a second game, also called an add-on.
- the player may be, for example, a "double or quits" type game or a "second chance” type game if the player has lost during his participation in the first game.
- the player can then record his participation in this second game using the specific application or the web interface.
- Such a possibility can also be offered to a player at a point of sale.
- the recording of the participation of a player in a second game is carried out automatically, for example when a player consults his ticket on the specific application or the web interface.
- FIG. 2 illustrates an example of the logical architecture of a multi-game computer system according to particular embodiments of the invention.
- This architecture can be implemented, for example, in the server 110 illustrated in FIG. According to other embodiments, it is implemented in a distributed system comprising several servers.
- the multi-game computer system 200 comprises a point of sale interface 205, denoted LTW (lottery widgets acronym in English terminology), and a user interface 210, denoted TTA (ticket tracker application acronym in Anglo-Saxon terminology).
- a point of sale or POS can thus connect to the computer system 200 via the interface 205 and a personal device denoted PD (abbreviation for personal device in Anglo-Saxon terminology), such as a smartphone or a tablet, can connect to the computer system 200 via interface 210.
- PD abbreviation for personal device in Anglo-Saxon terminology
- the interfaces 205 and 210 are connected to a payment and traceability module 215, denoted TTP (acronym for ticket tracking and payment in English terminology), itself connected to distinct game modules 220-1 to 220-n, noted GE (abbreviation for game engine in Anglo-Saxon terminology). Furthermore, the interface 205 is linked to the game modules 220-1 to 220-n to manage a player's participation in the corresponding game.
- TTP payment and traceability module
- GE abbreviation for game engine in Anglo-Saxon terminology
- the interface 205 makes it possible in particular to interrogate the module 215 to find out the status of a ticket and an amount of winnings for one or more games. This information can thus be given to a player going to a point of sale with his ticket whose identifier is used to determine the status and the amount of winnings.
- the interface 205 also makes it possible to request the module 215 to change the status of a ticket, for example after payment of the winnings.
- the interface 205 can also be used to inform a point of sale of the possibility for a player to participate in a second game, following participation in a first game, and to record the player's participation in this second game.
- the interface 210 makes it possible to interrogate the module 215 to find out the status of a ticket and an amount of winnings for one or more games. This information can thus be displayed on a player's personal device using a specific application or via a web interface after entering the ticket identifier (by the user or by reading the ticket).
- the interface 210 can also be used to inform the player of the possibility of participating in a second game, following participation in a first game, and to register his participation in this second game.
- the module 215 has in particular for its object the management of winnings resulting from participation in games, in particular the management of winnings resulting from participation in games linked, directly or indirectly, to the same ticket.
- each game module concerned addresses a list of winners, for example identified by ticket identifiers, and the amounts of winnings associated with the module 215. The latter can then determine, in response to a request from a point of sale or a personal device of a player, from a ticket identifier, whether a player has won or not and, if applicable, the amount of winnings.
- the module 215 sends a request comprising a ticket identifier to a game module which responds with a ticket status and /or a game result that may include an amount of winnings.
- the module 215 also aims to monitor operations carried out during the life cycle of a ticket, in connection with participation in games linked to the same ticket. He can in particular, from information received from a first game module, propose participation in a game managed by a second game module different from the first, and register a player in the second game, for example by using an identifier of a ticket corresponding to the first game.
- the module 215 can thus memorize a game history associated with each ticket. This history can in particular be consulted by the manager of the multi-game system, for example for monitoring, auditing or marketing purposes.
- the game modules 220-1 to 220-n advantageously do not include payment functions, the latter being remote or decentralized in the module 215. In addition to the usual game functions, they therefore include an interface, preferably standardized , with module 215.
- FIG 3 illustrates a first example of a time diagram of steps of the method of the invention according to a particular embodiment, between the user interface (TTA) or the point-of-sale interface (LTW), the payment and traceability module (TTP) and two game modules (GE1 and GE2).
- TTA user interface
- LW point-of-sale interface
- TTP payment and traceability module
- GE1 and GE2 game modules
- TTP payment and traceability module
- a player can buy a ticket giving him the right to play an instant game (game 1), for example a scratch game, implemented here in the module of game GE1, and if he has lost, to play a second chance game (game 2), for example a lottery game implemented, here, in the game module GE2.
- game 1 for example a scratch game, implemented here in the module of game GE1
- game 2 for example a lottery game implemented, here, in the game module GE2.
- the corresponding game module (GE1) determines the number of winning tickets and the associated winnings.
- the winnings or the list of winning tickets and associated winnings, depending on the game, are transmitted to the payment and traceability module (TTP).
- information that a player having a ticket to play this game also has the right to play the second game (game 2), where applicable with the conditions for participation in the second game, for example only if the player has lost is transmitted to the payment and traceability module (TTP).
- This list and this information (for example an identifier of the second game) are here stored by the payment and traceability module (TTP).
- a player buys a ticket and takes part in the game, he interrogates the multi-game system, from a personal device or from a point of sale, to find out whether he has won.
- a request comprising the identifier of the ticket is transmitted to the payment and traceability module (TTP) via the user interface (TTA) or the point of sale interface (LTW).
- TTP payment and traceability module
- the payment and traceability module (TTP) determines whether the ticket is a winner or not and, if so, obtains the amount of the win.
- the ticket determines the status of the ticket to verify the rights of the player, for example if he is entitled to be paid a win and play a second game, i.e., for example, if the ticket is in payable condition. It also determines, based on the information received from the game module, that the player has the possibility of playing the second game and, if he is not already registered, offers him to participate in it.
- TTP payment and traceability module
- TTA user interface
- LW point-of-sale interface
- GE2 game module
- the games module determines the winnings or the winning tickets and the associated winnings, depending on the game, and transmits the list of winning tickets and the associated winnings or the winnings to the payment module and traceability (TTP). The latter can then alert the winners via their personal device.
- the lists associated with the first and the second set can be independent lists or can be combined in the same list. Similarly, these lists may include information relating to all of the tickets or may only include information relating to winning tickets, tickets not present in the list then being considered as losing tickets.
- a player can request the payment of winnings. This request is sent to the payment and traceability module (TTP) via the point-of-sale interface (LTW). Upon receipt of this request, the payment and traceability module (TTP) checks the status of the ticket using its identifier. The status can be checked with each of the game modules associated with the games in which the player has participated or with the payment and traceability module (TTP) itself, the latter then summarizing the status associated with the ticket in each of the payment modules. game associated with the games in which the player has participated.
- the payment and traceability module (TTP) calculates the amount of winnings due by querying the lists concerned, here the list linked to the game targeted by the ticket (game 1) and the list linked to the game targeted by the game covered by the ticket (game 2) if the player participated in the latter.
- the payment and traceability module (TTP) modifies the status of the ticket which becomes already paid and informs the point of sale of the amount of winnings to be paid (so that the player is paid).
- the modification of the status is carried out in the payment and traceability module (TTP) and/or in each of the game modules associated with the games in which the player has participated.
- the payment and traceability module (TTP) thus centralizes the payment of winnings relating to several participations in games, here a little main and a secondary game.
- FIG 4 illustrates a second example of a time diagram of steps of the method of the invention according to a second particular embodiment, again between the user interface (TTA) or the point of sale interface (LTW), the payment and traceability module (TTP) and two game modules (GE1 and GE2).
- TTA user interface
- LTW point of sale interface
- TTP payment and traceability module
- GE1 and GE2 game modules
- the second game in FIG. 4 is an immediate participation game.
- each lottery ticket played is recorded in the corresponding game module (GE1).
- GE1 game module
- the game module identifies the winning ticket(s), based on their identifier, and the amount of the associated winnings.
- the list of winning tickets and associated winnings is transmitted to the payment and traceability module (TTP).
- information that a player having a ticket to play this game also has the right to play the second game (game 2), where applicable with the conditions for participation in the second game, for example only if the player has won, is transmitted to the payment and traceability module (TTP).
- This list and this information (for example an identifier of the second game) are here stored by the payment and traceability module (TTP). According to particular embodiments, the latter can then alert the winners via their personal device.
- a player can request the amount of his winnings.
- a request including the ticket identifier is transmitted to the payment and traceability module (TTP) via the user interface (TTA) or the point of sale interface (LTW).
- TTP payment and traceability module
- the payment and traceability module (TTP) determines whether the ticket is a winner or not and, if so, obtains the amount of the win.
- the status of the ticket to verify the rights of the player, for example if he is entitled to be paid a win and play a second game, i.e., for example, if the ticket is in payable condition. It also determines, based on the information received from the game module, that the player has the possibility of playing the second game and, if he is not already registered, offers him to participate.
- TTP payment and traceability module
- TTA user interface
- LW point-of-sale interface
- GE2 game module
- the games module (GE2) can indicate to the payment and traceability module (TTP) whether the player has won or lost. He can also indicate it directly to the player, for example depending on the game (e.g. instant participation game or deferred participation game). If he has received the result, the payment and traceability module (TTP) memorizes it, calculates the amount of winnings due by querying the list linked to the game covered by the ticket (game 1), by applying the result of the second game and preferably informs the player.
- TTP payment and traceability module
- the player can then request payment of these winnings.
- This request is sent to the payment and traceability module (TTP) via the point-of-sale interface (LTW).
- TTP payment and traceability module
- the payment and traceability module (TTP) checks the status of the ticket using its identifier. If the ticket is not in a payable state, the player is alerted. If, on the contrary, the ticket is in a payable state, the payment and traceability module (TTP) calculates, if necessary, the amount of winnings due by querying the list linked to the game covered by the ticket (game 1), by applying the result of the second game if the player participated in the latter.
- the payment and traceability module (TTP) modifies the status of the ticket which becomes already paid and informs the point of sale of the amount of winnings to be paid (so that the player is paid). Again, the modification of the status is carried out in the payment and traceability module (TTP) and/or in each of the game modules associated with the games in which the player has participated.
- the game rules and the calculation of the winnings, specific to each game are managed independently by the game modules, while the payment of the winnings is managed centrally by the module of payment and traceability which also coordinates participation in the various games according to the rules specific to each game.
- a ticket status is here managed by the module of the main game associated with the ticket in question and, preferably, by each game module associated with the games in which the ticket holder has participated. This status is, for example, in a payable state when the winnings have been determined, in a blocked state if, for example, the ticket has been declared stolen or in a pending state when the winnings have not yet been calculated.
- the ticket status is preferably updated by the game module itself according to standard rules.
- a winning status is managed by the payment and traceability module for each ticket associated with one or more winnings.
- the winning status is managed by the payment and traceability module according to its own payment rules.
- the game module with which is associated the ticket is interrogated, using the ticket identifier, to determine the status of the ticket for this game and possible eligibility to participate in a second game.
- the payment and traceability module can determine the participation of the ticket holder in different games and the status of the ticket for this s different games.
- the winnings are preferably transmitted to the payment and traceability module upon participation in the game (immediate participation game) or when the winnings are determined (deferred participation game).
- the payment and traceability module thus only memorizes winnings linked to ticket identifiers and determines the operations linked to the same ticket by interrogating the game modules concerned.
- FIG. 5 illustrates an example of steps implemented in a payment and traceability module according to a particular embodiment.
- a first step has as its object the receipt of a request to obtain a status for a ticket and/or to pay a prize corresponding to participation in the game associated with this ticket (step 500).
- This request here includes a ticket identifier. As described previously, this identifier is unique.
- a request comprising the identifier received from the ticket is sent to the game module corresponding to the game associated with the ticket to obtain a status of the ticket, if necessary a gain linked to participation in this game (the win which may be zero) and eligibility information for a second game (step 505).
- the payment and traceability module receives the requested information.
- step 510 it is determined whether the ticket is eligible for participation in a second game (step 510). If the ticket is not eligible for participation in a second game, the amount of winnings associated with the considered ticket is calculated as corresponding to the (possible) winnings obtained during participation in the first game (step 515).
- a test is carried out to determine if the player is already registered to participate in the second game, that is to say if the ticket is registered for a participation in the second game (step 520).
- this test is carried out by interrogating the game module concerned.
- this information can be stored in the payment and traceability module when a player accepts participation in a second game and thus be obtained directly.
- step 525 If the player is not already registered to participate in the second game, he is offered to participate (step 525). If he agrees to participate, corresponding information can be stored in the payment and traceability module and a request is transmitted to the corresponding game module to register the player, for example if it is a game lottery, or to play, for example if it is an instant draw (step 530). It is observed here that the information necessary for participation in the second game is transmitted to the game module associated with the latter. It can be, for example, an amount of a bet or a winning amount linked to the first game.
- a request comprising the identifier of the ticket in question is transmitted to the corresponding game module to obtain the status, for this game, of the ticket having led to this participation, if applicable the result or the gain linked to this participation and any information on eligibility for a third game (step 535).
- the payment and traceability module receives the requested information.
- all or some of the information requested is obtained directly in the payment and traceability module, this information having been previously received from the game module concerned or having been previously determined within of the payment and traceability module. Again, winnings can be obtained by the payment and traceability module as soon as they are calculated by game modules.
- step 510 to 535) are repeated for each additional game.
- step 510 to 535 the winnings resulting from the player's participation in different games, for example the first and second games, in connection with a single ticket, are determined by the payment and traceability module from the information received. game modules (step 515). If the player requests payment of all or part of the winnings, the payment and traceability module checks the possibility of such a payment according to the winning status associated with the ticket in question and to specific winnings payment rules managed by the module. payment and traceability.
- Table 1 in the appendix illustrates a first example of lists of tickets allowing the management of gains and the monitoring of operations carried out during the life cycle of a ticket.
- Each line corresponds to a ticket identified by its identifier, the first line corresponding to the default values.
- the table summarizes the gains obtained and the operations carried out during the life cycle of tickets.
- the default values line can be used when a ticket is not identified in the list or to define the default values when adding a line corresponding to a ticket to the list.
- the first column corresponds to the identifier of the tickets
- the second column corresponds to the amount of winnings associated with the ticket considered in the first game, or main game (that is to say the game associated to the ticket considered)
- the third column corresponds to the identifier of a second game
- the fourth column indicates the conditions according to which the possibility of participating in the second game is offered or not to the user
- the fifth column indicates the choice of holder of the ticket considered to participate or not in the second game (if the possibility is not offered to him, a corresponding value is, preferably, added automatically)
- the sixth column corresponds to the amount of winnings associated with participation in the second game, or additional game
- the seventh column indicates the status of the ticket.
- the ticket identifier comprises the identifier of the game with which the ticket is associated.
- the first three digits of the ticket identifier correspond to the game identifier, here 425. It is observed here that when the possibility of playing a second game is not offered to a player, the identifier of the second game, in the third column, corresponds to a predetermined value providing such an indication, for example the zero value.
- the conditions of participation in the second game are, for example, to win the first game, to lose the first game, to win a prize in the first game of an amount greater than a predetermined threshold, to win a prize in the first game of an amount lower than a predetermined threshold, etc.
- the winnings obtained following participation in the second game may be winnings of a given amount (predetermined or calculated) or may correspond to an operation to be applied to the winnings of the first game, for example canceling the winnings of the first game if the player loses or multiplying the winnings of the first game by a given factor if the player wins.
- the list represented in table 1 is for example created when information is received from the game module of the first game and completed subsequently, in particular when a player decides to participate in a second game, during the receiving information from the game module of the second game, when receiving a request for payment of winnings, etc.
- the tickets linked to the game having the identifier 425 offer, by default, the opportunity for their holder to participate to a second game, having the identifier 423, provided that the player has lost in the first game.
- the tickets are in a payable state.
- the ticket with the identifier 42512923 is a winning ticket in the first game, the gain being 10. This ticket being a winner, it does not offer its holder the possibility of participating in the second game.
- the ticket having the identifier 42531199 is not in the list of winning tickets provided by the game module corresponding to game 1. Consequently, it is considered as a ticket losing.
- the holder of this ticket connects to the payment and traceability module, he is offered to participate in the second game (due to the default values offering the possibility of participating in the second game if the holder lost in the first game ).
- a line is preferably created in the list. The gain associated with the first game is set to zero while that associated with the second game is updated at the end of the second game.
- the ticket having the identifier 42532689 is a winning ticket in the first game, the gain being 20.
- This ticket is here associated with a second game having the identifier 112 (this choice being made by the game module associated with the first game). To participate in this second game, the ticket must be a winner in the first game. As indicated in the fifth column, the ticket holder decided to participate in the second game and won. The ticket here allows its holder to win twice the gain in the first game, that is to say 40.
- the values present in the list are representative of the earnings and of the operations carried out during the life cycle of tickets.
- Table 2 in the appendix illustrates a second example of lists of tickets allowing the management of winnings and the monitoring of operations carried out during the life cycle of tickets associated with a given game, these operations relating to this game or to another.
- Each line corresponds to a ticket identified by its identifier, the first line corresponding to the default values.
- the default values line can be used when a ticket is not identified in the list or to define the default values when adding a line corresponding to a ticket to the list.
- the first column corresponds to the identifier of the tickets
- the second column corresponds to the amount of winnings associated with the ticket in question and the game with which the list in question is associated
- the third column corresponds to the identifier of a following game
- the fourth column indicates the conditions according to which the possibility of participating in the following game is offered or not to the user
- the fifth column indicates the choice of the holder of the ticket in question to participate or not in the following game (if the possibility is not offered to it, a corresponding value is preferably added automatically)
- the sixth column indicates the status of the ticket. It is observed here that the sixth column can only be used if the game associated with the list considered is directly linked to the tickets whose identifiers are listed.
- the ticket having the identifier 13232681 is a losing ticket in the first game.
- This ticket is here associated with a second game having the identifier 107. To participate in this second game, the ticket must be a loser. in the first game. The ticket holder was thus offered to play the second game however, as indicated in the fifth column, the ticket holder decided not to participate in the second game.
- Figure 6 illustrates an example of a device that can be used to implement, at least partially, embodiments of the invention, in particular the steps described with reference to Figures 3 to 5.
- the device 600 is for example a server, a computer or a terminal.
- the device 600 preferably comprises a communication bus 602 to which are connected:
- a central processing unit or microprocessor 604 (CPU, acronym for Central Processing Unit in English terminology);
- a read only memory 606 (ROM, acronym for Read Only Memory in Anglo-Saxon terminology) which may include the operating system and programs such as "Prog";
- RAM Random Access Memory
- cache memory 608 comprising registers suitable for recording variables and parameters created and modified during the execution of the aforementioned programs
- a communication interface 626 connected to a distributed communication network 628, for example a wireless communication network and/or a local communication network, the interface being capable of transmitting and receiving data, in particular to and from from a user's device.
- a distributed communication network 628 for example a wireless communication network and/or a local communication network
- the device 600 can also have the following elements:
- a hard disk 620 which may include the aforementioned "Prog" programs and data processed or to be processed according to the invention
- a keyboard 622 and a mouse 624 or any other pointing device such as a light pen, a touch screen or a remote control allowing the user to interact with the programs according to the invention
- a reader 610 of removable storage medium 612 such as a memory card or a disc, for example a DVD disc; and [0101] a graphics card 614 connected to a screen 616.
- the communication bus allows communication and interoperability between the different elements included in the device 600 or connected to it.
- the representation of the bus is not limiting and, in particular, the central unit is capable of communicating instructions to any element of the device 600 directly or via another element of the device 600.
- the executable code of each program allowing the programmable device to implement the processes according to the invention can be stored, for example, in the hard disk 620 or in ROM 606.
- the executable code of the programs can be received via the communication network 628, via the interface 626, to be stored in the same way as described previously.
- the program(s) can be loaded into one of the storage means of the device 600 before being executed.
- the central unit 604 will control and direct the execution of the instructions or portions of software code of the program(s) according to the invention, instructions which are stored in the hard disk 620 or in the ROM 606 or else in the other aforementioned storage elements.
- the program or programs which are stored in a non-volatile memory for example the hard disk 620 or the ROM 606, are transferred to the random access memory 608 which then contains the executable code of the program or programs according to the invention, as well as registers for storing the variables and parameters necessary for the implementation of the invention.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Pinball Game Machines (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR2009367A FR3114033A1 (fr) | 2020-09-16 | 2020-09-16 | Procédé, dispositif et programme d’ordinateur de gestion de gains et de suivi dans un système informatique multi-jeux |
PCT/FR2021/051574 WO2022058676A1 (fr) | 2020-09-16 | 2021-09-14 | Procédé, dispositif et programme d'ordinateur de gestion de gains et de suivi dans un système informatique multi-jeux |
Publications (1)
Publication Number | Publication Date |
---|---|
EP4213953A1 true EP4213953A1 (fr) | 2023-07-26 |
Family
ID=73401804
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP21785951.1A Pending EP4213953A1 (fr) | 2020-09-16 | 2021-09-14 | Procédé, dispositif et programme d'ordinateur de gestion de gains et de suivi dans un système informatique multi-jeux |
Country Status (5)
Country | Link |
---|---|
US (1) | US20230377414A1 (fr) |
EP (1) | EP4213953A1 (fr) |
CA (1) | CA3191378A1 (fr) |
FR (1) | FR3114033A1 (fr) |
WO (1) | WO2022058676A1 (fr) |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106204872A (zh) * | 2015-05-27 | 2016-12-07 | 国际游戏公司 | 游戏系统、游戏券和实现游戏的方法 |
US10304282B2 (en) * | 2016-01-28 | 2019-05-28 | Playtech Software Limited | Autonomously operating computerized gaming platforms and method of operating thereof |
-
2020
- 2020-09-16 FR FR2009367A patent/FR3114033A1/fr active Pending
-
2021
- 2021-09-14 US US18/026,358 patent/US20230377414A1/en active Pending
- 2021-09-14 WO PCT/FR2021/051574 patent/WO2022058676A1/fr active Search and Examination
- 2021-09-14 EP EP21785951.1A patent/EP4213953A1/fr active Pending
- 2021-09-14 CA CA3191378A patent/CA3191378A1/fr active Pending
Also Published As
Publication number | Publication date |
---|---|
WO2022058676A1 (fr) | 2022-03-24 |
US20230377414A1 (en) | 2023-11-23 |
FR3114033A1 (fr) | 2022-03-18 |
CA3191378A1 (fr) | 2022-03-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10832520B2 (en) | Fungible object award interleaved wagering system | |
US20090143128A1 (en) | Providing centralized services to game operators | |
KR101511928B1 (ko) | 맵-기반 게임에 관련해서 소프트웨어 오브젝트를 제공 및 처리하기 위한 시스템 및 방법 | |
AU2003274441B2 (en) | System and method for jackpot wagering | |
US20190051118A1 (en) | Skill-based progressive pool combined proposition wagering system | |
US10540849B2 (en) | Alternate payment mechanism interleaved skill wagering gaming system | |
AU2013311319A1 (en) | Pool wagering apparatus, methods and systems | |
US10380846B2 (en) | Market based interleaved wagering system | |
US10431042B2 (en) | Recommendation module interleaved wagering system | |
RU2643430C2 (ru) | Система и способ осуществления ставок в режиме реального времени, предусматривающие джекпот | |
US20190051112A1 (en) | Transparent prize combined proposition wagering system | |
US8235822B2 (en) | Transmitting content in wagering networks | |
EP4213953A1 (fr) | Procédé, dispositif et programme d'ordinateur de gestion de gains et de suivi dans un système informatique multi-jeux | |
FR3137301A1 (fr) | Système de jeux digitaux liés | |
WO2024003513A1 (fr) | Système de jeux digitaux liés | |
FR3131415A1 (fr) | Procédé, dispositif et programme d’ordinateur de gestion de gains de jeux digitaux d’argent et de hasard multi-joueurs | |
WO2024003512A1 (fr) | Procédé, dispositif et programme d'ordinateur de mise en oeuvre de jeux digitaux liés | |
FR3137477A1 (fr) | Procédé, dispositif et programme d’ordinateur de mise en œuvre de jeux digitaux liés | |
WO2023067274A1 (fr) | Procédé, dispositif et programme d'ordinateur d'adaptation contextuelle de jeux phygitaux | |
US11823530B2 (en) | Transaction sequences including a linked deal within an initial deal | |
WO2023126597A1 (fr) | Procédé, dispositif et programme d'ordinateur d'établissement de profils de comportements d'usagers procédé, dispositif et programme d'ordinateur d'établissement de profils de comportements d'usagers | |
US20210082228A1 (en) | Collecting and levelling up predictions as collectible cards | |
KR20030041374A (ko) | 게임기의 당첨내역과 적립금을 확인할 수 있는 인터넷용게임 시스템 및 그 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20230310 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230728 |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20240408 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: A63F 3/06 20060101ALN20240322BHEP Ipc: G07F 17/42 20060101ALI20240322BHEP Ipc: G07F 17/32 20060101ALI20240322BHEP Ipc: A63F 3/08 20060101AFI20240322BHEP |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: MEYNIEUX, ERIC Inventor name: HUGUENIN, OLIVIER |