WO1998029162A1 - Procede et appareil permettant de gerer des defaillances et des anomalies - Google Patents

Procede et appareil permettant de gerer des defaillances et des anomalies Download PDF

Info

Publication number
WO1998029162A1
WO1998029162A1 PCT/US1997/023940 US9723940W WO9829162A1 WO 1998029162 A1 WO1998029162 A1 WO 1998029162A1 US 9723940 W US9723940 W US 9723940W WO 9829162 A1 WO9829162 A1 WO 9829162A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
routine
subsystems
subsystem
recited
Prior art date
Application number
PCT/US1997/023940
Other languages
English (en)
Other versions
WO1998029162A9 (fr
Inventor
Andrew Pascal
Michael Barnett
Clayton Wishoff
Original Assignee
Silicon Gaming-Nevada
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Silicon Gaming-Nevada filed Critical Silicon Gaming-Nevada
Priority to AU58075/98A priority Critical patent/AU5807598A/en
Publication of WO1998029162A1 publication Critical patent/WO1998029162A1/fr
Publication of WO1998029162A9 publication Critical patent/WO1998029162A9/fr

Links

Classifications

    • 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
    • G07F17/3232—Data transfer within a gaming system, e.g. data sent between gaming machines and users wherein the operator is informed
    • G07F17/3237—Data transfer within a gaming system, e.g. data sent between gaming machines and users wherein the operator is informed about the players, e.g. profiling, responsible gaming, strategy/behavior of players, location of players
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1438—Restarting or rejuvenating
    • 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

Definitions

  • This invention is generally related to fault tolerant recovery systems, and in particular, a fault-tolerant software system which maintains audio and visual capability in the event of a fault.
  • Game machines displayed in public entertainment localities are made available for public usage in exchange for payment. This is particularly the case for casinos and game parlors where there are a large number of machines. However, these machines occasionally malfunction and enter into a lock up state, ceasing all functions and leaving the player stranded. The player at the malfunctioned machine would either abandon the machine after a few attempts at "fixing" the machine, or wait for an attendant's assistance. In waiting for an attendant's assistance, it would be desirable to maintain the player's interest and keep the player occupied.
  • One way of accomplishing this goal is to show a computer driven video clip using the existing hardware and software already provided by the machine. The content of the video clip can be determined by the management and can be periodically updated.
  • the video clip can be thought of as a commercial or infomercial of some type.
  • the operating system software for the machine must be set up in a manner such that in the event of a fault, the integrity of the operating system, including the audio and video modules, are maintained.
  • the present invention provides an operating system having a multitude of subsystems where each subsystem performs a distinct function and may register with other subsystems to receive notification (or callbacks) upon the ocurrence of certain events.
  • the subsystems are programmed in such a manner where in the event of a fault (or exception) they can be instructed to cease the calling of other subsystems, thereby allowing each of the subsystems to complete its distinctive task without commencing further additional activities.
  • the state of the system as indicated by the parameters at the various registers and addresses are saved.
  • the system can initiate a service call for an attendant through one of the provided mechanisms or routine calls.
  • the system can initiate an intermission (play stoppage) routine using full audio and video capabilities to explain to the player in a user-friendly manner the problems encountered and play a video clip or the like in entertaining and occupying the player.
  • the architecture of the machine must be programmed in such a manner to facilitate the desired functionalities. More specifically, the modules of the operating system is processed by an event manager. Upon the detection of a fault, a series of steps are performed to "strangle" the system in order to gracefully stop the execution of the currently executing modules. Then, the state of the system is saved and a play stoppage application is started to entertain the player.
  • the description herein uses a gaming machine for illustration purposes but is not limited to this type of machine.
  • the present invention is of special importance-in the area of gaming machines where the user may have remaining credits on the machine at the time of the fault and the current state of the machine may affect the outcome of the game payout.
  • Fig. 1 illustrates a general block diagram of a gaming machine
  • Fig. 2 shows the processing steps in powering up an embodiment of the present invention
  • Fig. 3a shows the type of data in the ROM
  • Fig. 3b shows the components in the anchor application
  • Figs 3c - 3e shows the type of applications that can be started by the anchor application
  • Fig. 4 illustrates the processing steps performed by the event manager
  • Fig. 5 illustrates the general steps in interrupting a running application
  • Fig. 6a shows the processing substeps for the enter sequence step
  • Fig. 6b shows the substeps in the run sequence step
  • Fig. 6c illustrates the substeps in the exit sequence step
  • Fig. 7 illustrates a simple flow diagram for the play stoppage application.
  • Fig. 1 illustrates in block diagram form the components of a general gaming system that may embody the present invention.
  • a CPU 10 interfaces with a bus controller 12 to access information available from the various components and information from the RAM 14.
  • the bus controller 12 sends and receives information via bus 16 to the various components.
  • the bus is not limited to a particular type and can be an ISA bus, EISA bus, PCI bus or others. Moreover, it can be linked to an external bus connector to further extend the system.
  • information from the ROM 18 is read and is used to configure the initial operational parameters of the system. Further information can also be obtained from the hard disk 20 via the disk controller 22.
  • the disk controller can be connected to an external disk drive port 24 for connection to external disk drives.
  • information to be displayed is written to a frame buffer 26 and sent to a display monitor 28.
  • the system can also be connected to a network via the network interface 34 such that a number of game machines can be connected for multi-player action.
  • One or more parallel ports 36 and serial ports 38 provide connections to peripheral devices.
  • a timer 40 provides clock pulses for synchronizing the components and the operation of the system.
  • the components of the system dedicated to the operation of the game is illustrated in block 42 which can be a separate subsystem with its own system bus and the like. In the alternative, all of the components of the system can be integrated as a single system.
  • an expansion bus 44 for connecting to the system a custom gaming network 46.
  • There is a hopper 52 which is a mechanism for tracking and dispensing coin drops and winnings.
  • An internal credit display 56 can be installed inside of the cabinet of the machine to display the available credits.
  • the bill acceptor 58 is connected via a serial port 60 and there is an external screen 62 connected to the serial port to display low level messages.
  • the system boot process starts from a reset condition that is either a cold start process or a warm start process 80.
  • a cold start process is started from a power off condition and power is supplied to the system to start the boot process.
  • a warm start process is any reset that occurs after power is supplied to the system, and can be generated from pressing the reset button of the system, from the expiration of the watchdog timer, from a software generated reset, or from certain system faults.
  • the system When the system starts from either a warm boot or a cold boot, it reads and executes codes located in the ROM BIOS portion 82 of the Read Only Memory (ROM).
  • the BIOS code is responsible for initializing all of the devices located on the motherboard.
  • the system executes the ROM Boot Loader codes 84.
  • the ROM Boot Loader starts the operation system 86 and initializes the drivers that are linked with the operating system 86, including drivers for the hard disk-controller, the serial port, the ethernet port, the interrupt service routines, etc.
  • the ROM Boot Loader reads the machine configuration data from an EEPROM 86 where the configuration data will indicate the location of the anchor application, which is the main program for the system.
  • the anchor application is then loaded into memory (from either the network or the disk) and the system executes the loaded anchor application 87.
  • the anchor application contains the bulk of the system and application codes, including additional drivers and API's, which include memory manager, shell, frame buffer event manager, the hopper, buttons, meters, coin diverter, bill acceptor, threaded file I/O, FIP daemon, cashier, display manager, hotspot manager, sound manager, deferred execution managers, etc.
  • additional drivers and API's include memory manager, shell, frame buffer event manager, the hopper, buttons, meters, coin diverter, bill acceptor, threaded file I/O, FIP daemon, cashier, display manager, hotspot manager, sound manager, deferred execution managers, etc.
  • the system Before the anchor application is loaded, the system is in a minimal state with virtually no I/O interaction except for the diagnostic display (a LED display). The reason for this rather crippled state is because nearly all of the device drivers and API's are located in the anchor application.
  • the event manager is started next 88.
  • the event manager is responsible for collecting non-fatal exceptions and starting an application based on the type of exceptions received. Events are delivered to the event manager via a queue and are posted by various driver routines when they detect an event that the event manager needs to process.
  • the event manager is implemented as a very high priority task that polls the queue for events. When an event is accepted by the event manager 89, it is evaluated along with all other outstanding events to determine the corresponding action to undertake. Some events cause play stoppage to begin while other events cause play stoppage to be cleared.
  • Fig. 4 illustrates an event processing scheme of the preferred embodiment of the present invention.
  • There is an event input queue 120 that receives event notifications from a variety of sources. These sources can include a notice from the hopper processing module 122, the game module 124, the door sensor processing module 126 or other modules.
  • the notification of the events in the event input queue 120 are processed by the event manager 128.
  • the event manager evaluates the outstanding events 130 and performs handling of these events by calling a corresponding action which can be the calling of a play stoppage application, the starting of a machine management system 136, or the activation of a service signal 138.
  • Boot Failures If an error or failure occurred in the boot sequence, the failure must be reported to a technician so the problem can be corrected.
  • the system can report failures in two different ways. If a failure is critical and occurs before the boot sequence is completed, the minimal reporting mechanism, the diagnostic display (LEDs), is used. If a failure is non-critical and the anchor application initialization process successfully completes, the error is reported using the high level error reporting mechanism, which is play stoppage.
  • the minimal reporting mechanism As the system initializes, it will, at each step of the boot process, write a diagnostic code to the diagnostic display. When a critical failure occurs, the diagnostic code will tell the technician where in the sequence the problem has occurred. For example, just before the SCSI driver is initialized, a code of "104" is displayed. When the SCSI initialization completes, the code is updated to "105". If a problem occurred in the SCSI initialization, the system halts and would not update the code to 105. When the technician checks the error code, he or she will see code 104 which indicates that the SCSI subsystem is the source of the problem.
  • a serial port can be connected to an external subsystem to display expanded information of the boot process.
  • the startup message sent to the event manager would indicate to the event manager that the trouble shooting Machine Management System (MMS) and/or a stoppage application should be executed rather than a game application.
  • MMS Machine Management System
  • the MMS would cause the stoppage application to put up an out of service message and wait for a technician to turn the MMS key switch to enter the MMS diagnostics mode.
  • the event manager can be programmed to allow game play and run a game application.
  • a light strobe or signal would be lit to indicate that the machine is having some problems but otherwise the machine operates normally.
  • Exceptions are errors or events that can interrupt the system at any time. Exceptions are classified in one of two ways, fatal and non-fatal.
  • Fatal exceptions are serious enough to cause the system to shut down.
  • the system writes a diagnostic code to the diagnostic display and locks up. The technician then troubleshoots the problem using the diagnostic code. These errors are considered serious enough that the continuation of code execution could jeopardize the integrity of the system or cripple the system to a point that the MMS could not be ran.
  • Some examples of fatal exceptions include: hard disk failure, certain RAM errors that are not recoverable, corrupted program code, processor faults, OS internal errors, etc.
  • the fatal error handler turns on the signal strobe and hangs or ceases system operation until the system resets. In order to 'hang' the system, the handler continuously resets the watchdog timer so that the watchdog timer does not expire and reset the system. For fatal errors where an automatic restart of the system would clear the problem, the handler resets the system via a software reset.
  • Non-fatal exceptions are handled using play stoppage.
  • the event manager When a non-fatal exception is detected, the event manager is notified of the event. The event manager evaluates the event and determines the stoppage application to execute. Examples of non-fatal exceptions include: hopper jams, coin jam, door open, bill acceptor failure, hand-pay jackpots, network out of service, etc.
  • Fig. 3a illustrates the types of data in the ROM, which includes codes for the ROM Boot Loader, the operating system, the operating system based devices, the secured functions, and the BIOS.
  • Fig. 3b illustrates the major components of the anchor application which includes device initiation codes 98, the event manager 100, system drivers 102, graphics application interface 104, secured loader 106 and a random number generator 108.
  • Figs. 3c to 3e each is a loadable application to be handled by the anchor application. More specifically, Fig. 3c is a game application, Fig. 3d is a play stoppage application, and Fig. 3e is the Machine Management System.
  • the navigator which is an application providing a number of game selections, is launched by the event manager. If the navigator is asked by the user to launch a game, it sends a corresponding launch message to the event manager.
  • This type of launch is "normal" in that it does not interrupt other applications. If multiple applications are launched using the normal scheme, they would run in parallel.
  • each subsystem may register with another subsystem to receive information and notification in the event of an occurrence of certain events.
  • the host subsystem sends the client subsystem a notification (or callback request) of the event.
  • the client subsystem handles the callback accordingly. For example, a game subsystem (client) registers with the button subsystem (host) for a callback so that when a particular button is pressed, the button subsystem would inform the game subsystem of the particular button pressed.
  • each subsystem When a button is actually pressed, the button subsystem processes its callback list. In the process, the game subsystem being on the callback list is informed of the particular button pressed and the corresponding code in the game subsystem is executed. Under this structure, each subsystem has a callback list.
  • the subsystem When a subsystem is asked to push its state, the subsystem will save away enough information so that the state of the controlling software and hardware can be restored at a later time. In addition, it will save data structures representing the current state of the subsystem. Once the state information is saved, the data structures, software parameters, and hardware are set to a "clean" state, which means setting the hardware to the normal idle state and disconnecting any clients that may be receiving information about this subsystem.
  • a push of the subsystem can be thought of in terms of levels. For example, the normal idle state has a level of 1. When the subsystem is pushed, the level is incremented to 2. If pushed again, the level would go to 3. When a pop occurs, the level is decreased back down to 2. When an event occurs in a subsystem, only those clients that are registered with the subsystem at the current level are called. So, if the level were 3, only level 3 clients would get a callback.
  • the net effect of a push is to make the system available for starting up a new virtual machine for an interrupting application such as the play stoppage application.
  • the currently executing virtual machine will be "frozen” and restored when the play stoppage application completes.
  • the processing steps for pushing, popping and launching generally can be categorized in blocked steps including an enter sequence step 140, a run sequence step 142, and an exit sequence step 144.
  • a play stoppage application an interrupting application
  • a series of steps need to be taken in order to perform the high level push operation. This sequence of operations is called the "enter sequence”.
  • An enter sequence performed by the event manager is illustrated in Fig. 6a. Referring to Fig. 6a, the enter sequence starts by calling a strangle routine as indicated at 150. The strangle routine asks each and every subsystem to "strangle" or to stop any initiation of new callbacks by one subsystem to another subsystem. The stop of any callbacks is not an immediate stop. If a subsystem is in the middle of processing its callback list, the subsystem is allowed to finish the callbacks on the list in order to allow the subsystem to come to a good stopping point. Once all the callbacks for a subsystem are completed, the subsystem informs the event manager that it has completed its strangle routine.
  • the pause routine for the current application is called 152 to pause it.
  • an application When an application is started, it registers with the event manager a callback routine for pause and resume. For certain game applications this routine performs no particular function because these applications are run entirely within the callback context. Since all callbacks to the game have been disabled via the strangle function, no additional processing steps are needed to pause these applications.
  • the callback lock 154 is used to ensure that no additional callbacks occur. This is a special lock in that only during the enter sequence does using the lock have the potential to cause the game to depend on the lock. If the enter or exit sequence is not being executed, the lock will always be granted to the game.
  • each subsystem's push routine is called by the event manager, where each push operation saves the respective subsystem's list of registered callback clients and the subsystem's predetermined software and hardware information.
  • the last step of the enter sequence is the calling of the unstrangle routine 162 where all subsystems are allowed to execute callbacks again.
  • Run Sequence After the enter sequence is performed, a new virtual machine is ready for use by a stoppage application (or any other interrupting application).
  • a stoppage application is loaded 170 and executed by the event manager 172.
  • the stoppage application and its respective subsystems would register with the various subsystems for callbacks just like a game application.
  • the stoppage application also registers with the event manager its exit callback routine.
  • the event manager will call this routine when an event that would clear the currently executing stoppage application is received. For each event that is received by the event manager, the event manager checks to see if the stoppage application should be cleared.
  • the exit callback routine for the stoppage application would be executed. After the stoppage application completes its cleanup, it sends an END OF STOPPAGE event to the event manager. The end-event signals the event manager to unload the stoppage application and begin the exit procedure 174.
  • An alternative to having the event manager clearing the stoppage application is to put all of the clear stoppage code within the stoppage application itself. For example, the door open stoppage would wait for a door close event and then exit.
  • One problem with having the stoppage application determine events is that the clear event may occur while the stoppage application is being interrupted. If, for example, the door open stoppage application was interrupted by the MMS and then the door was closed while the MMS was running, the open stoppage application would not see the door close event when it resumed execution. Thus, the alternative method is not generally used.
  • the first operation is to strangle all subsystems to stop all callbacks 180.
  • the subsystems that registered callbacks with other subsystems remove their callback registrations (de-init) 184.
  • the event manager calls the pop routine for each of the subsystems 188.
  • a pop operation will restore the subsystem's hardware and data structures to their previously pushed state. This means that the callback lists for the subsystems will be restored to the previous state.
  • the game is then allowed to resume 190, the system is unstrangled 192, and the callback lock released 194. Play Stoppage Application
  • the Play Stoppage application is an application that runs any time there is an interruption to the gaming experience. This application is comprised of a number of short linear segments that keep the player entertained until the machine can be returned to play. Events that can trigger the play stoppage application include a hopper fill event, a jackpot event, a coin jam event, a hopper jam event, and a service call. It is preferable that when play stoppage occurs, a dramatic audio visual experience occurs within the provided environment, indicating that something has happened.
  • the player is provided with an explanation of the problem as well as the action undertaken to solve the problem 200. Since the necessary action required for solving the problem may require certain amount of time, entertainment of some type is provided to the player 202. If the event causing the play stoppage has been cleared, the play stoppage application is unloaded 206. Otherwise, the play stoppage application continues with the playing of the entertainment.
  • the MMS is launched by the event manager when a MMS key turn is detected.
  • no event will cause a stoppage application to execute (the MMS is not interruptible).
  • Some stoppage applications will want to change the behavior of the MMS key.
  • the hand-pay stoppage application uses an MMS key turn as an indication that the hand-pay information window should be displayed. In this case, the MMS will not be launched when the key is turned.
  • the event manager needs to be informed by the stoppage application that it wishes to disable MMS launches via the key switch.
  • These stoppage applications should provide a way for the technician to launch the MMS from the application itself. For example, in the hand-pay stoppage application, the MMS key will bring up a dialog that contains information needed to complete the stoppage transaction.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Social Psychology (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • Retry When Errors Occur (AREA)
  • Pinball Game Machines (AREA)

Abstract

L'invention concerne un système d'exploitation (94) pourvu de plusieurs sous-systèmes (fig. 1). Chaque sous-système remplit une fonction précise et peut entrer en communication avec d'autres sous-systèmes afin de recevoir une notification ou un rappel automatique, lorsque certains événements se produisent (fig. 3-4, 6). Ces sous-systèmes sont programmés de manière à interrompre leurs communications avec d'autres sous-systèmes dans l'éventualité d'une défaillance ou d'une anomalie (fig. 4), ce qui permet à chacun de ces sous-systèmes de remplir la tâche qui lui est propre sans entamer d'autres activités. Lorsque toutes les activités ont cessé, l'état du système indiqué par les paramètres des différents registres et adresses est sauvegardé. Le système provoque l'intervention d'un opérateur par l'intermédiaire de l'un de ses mécanismes ou appels de routine (fig. 4). Le système provoque également une interruption ou exécute une routine d'arrêt de jeu avec l'ensemble de ses moyens audio et visuels (fig. 7), afin d'expliquer de manière conviviale au joueur quels problèmes sont survenus; un clip vidéo ou tout autre intermède similaire lui est alors présenté afin de le divertir et de l'occuper.
PCT/US1997/023940 1996-12-27 1997-12-24 Procede et appareil permettant de gerer des defaillances et des anomalies WO1998029162A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU58075/98A AU5807598A (en) 1996-12-27 1997-12-24 Method and apparatus for managing faults and exceptions

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US08/774,826 1996-12-27
US08/774,826 US5971851A (en) 1996-12-27 1996-12-27 Method and apparatus for managing faults and exceptions

Publications (2)

Publication Number Publication Date
WO1998029162A1 true WO1998029162A1 (fr) 1998-07-09
WO1998029162A9 WO1998029162A9 (fr) 1998-12-17

Family

ID=25102431

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1997/023940 WO1998029162A1 (fr) 1996-12-27 1997-12-24 Procede et appareil permettant de gerer des defaillances et des anomalies

Country Status (4)

Country Link
US (1) US5971851A (fr)
AU (1) AU5807598A (fr)
WO (1) WO1998029162A1 (fr)
ZA (1) ZA9711661B (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007110294A3 (fr) * 2006-03-29 2007-11-15 Ibm Système, procédé et produit de programme informatique pour stocker de multiples types d'informations
CN113568719A (zh) * 2020-04-29 2021-10-29 北京猎户星空科技有限公司 一种业务故障处理方法、装置、电子设备及存储介质

Families Citing this family (96)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5688174A (en) * 1995-10-06 1997-11-18 Kennedy; Julian J. Multiplayer interactive video gaming device
US6964611B2 (en) * 1996-12-30 2005-11-15 Walker Digital, Llc System and method for automated play of lottery games
US6634942B2 (en) * 1996-12-30 2003-10-21 Jay S. Walker System and method for automated play of multiple gaming devices
US6234896B1 (en) * 1997-04-11 2001-05-22 Walker Digital, Llc Slot driven video story
US8113935B2 (en) 1997-03-12 2012-02-14 Igt System and method for presenting payout ranges and audiovisual clips at a gaming device
US8328624B2 (en) 1997-04-11 2012-12-11 Igt Slot driven video story
US6302790B1 (en) * 1998-02-19 2001-10-16 International Game Technology Audio visual output for a gaming device
CA2264341A1 (fr) 1998-04-14 1999-10-14 Mikohn Gaming Corporation Jeu pachinko autonome offrant des bonis
US6935946B2 (en) 1999-09-24 2005-08-30 Igt Video gaming apparatus for wagering with universal computerized controller and I/O interface for unique architecture
US6556950B1 (en) * 1999-09-30 2003-04-29 Rockwell Automation Technologies, Inc. Diagnostic method and apparatus for use with enterprise control
CA2402389A1 (fr) * 2000-03-08 2002-09-19 Shuffle Master, Inc. Systeme de jeu informatise, procede d'utilisation et appareil
US7988559B2 (en) 2001-03-08 2011-08-02 Igt Computerized gaming system, method and apparatus
US20010024970A1 (en) 2000-03-08 2001-09-27 Mckee Eileen Electronic video gambling device with player controlled amusement feature
US7043641B1 (en) 2000-03-08 2006-05-09 Igt Encryption in a secure computerized gaming system
US6942574B1 (en) * 2000-09-19 2005-09-13 Igt Method and apparatus for providing entertainment content on a gaming machine
US20060084488A1 (en) * 2000-09-19 2006-04-20 Igt Bonusing digital media
US8064889B2 (en) * 2000-09-19 2011-11-22 Igt Virtual casino host
US9626824B2 (en) * 2000-10-11 2017-04-18 Igt Game result graphical verification on remote clients
US6863608B1 (en) * 2000-10-11 2005-03-08 Igt Frame buffer capture of actual game play
US7384339B2 (en) * 2000-10-11 2008-06-10 Igt Frame capture of actual game play
US7111141B2 (en) * 2000-10-17 2006-09-19 Igt Dynamic NV-RAM
US6804763B1 (en) * 2000-10-17 2004-10-12 Igt High performance battery backed ram interface
US6918831B2 (en) * 2002-09-13 2005-07-19 Igt Method and apparatus for independently verifying game outcome
US8550922B2 (en) * 2006-03-03 2013-10-08 Igt Game removal with game history
US7203841B2 (en) * 2001-03-08 2007-04-10 Igt Encryption in a secure computerized gaming system
US7188343B2 (en) * 2001-05-18 2007-03-06 Hewlett-Packard Development Company, L.P. Distributable multi-daemon configuration for multi-system management
US7162036B2 (en) 2001-08-06 2007-01-09 Igt Digital identification of unique game characteristics
US6685567B2 (en) 2001-08-08 2004-02-03 Igt Process verification
US6890259B2 (en) 2001-09-10 2005-05-10 Igt Modular tilt handling system
US6902481B2 (en) * 2001-09-28 2005-06-07 Igt Decoupling of the graphical presentation of a game from the presentation logic
US8708828B2 (en) 2001-09-28 2014-04-29 Igt Pluggable modular gaming modifiers and configuration templates for gaming environments
US7931533B2 (en) 2001-09-28 2011-04-26 Igt Game development architecture that decouples the game logic from the graphics logics
US7179170B2 (en) * 2001-11-26 2007-02-20 Igt Pass-through live validation device and method
US9064372B2 (en) 2002-02-15 2015-06-23 Wms Gaming Inc. Wagering game with simulated mechanical reels having an overlying image display
US6962530B2 (en) 2002-04-25 2005-11-08 Igt Authentication in a secure computerized gaming system
US7918730B2 (en) 2002-06-27 2011-04-05 Igt Trajectory-based 3-D games of chance for video gaming machines
US7478387B2 (en) * 2002-09-25 2009-01-13 International Business Machines Corporation System and method for creating a restartable non-native language routine execution environment
US7207883B2 (en) * 2002-11-19 2007-04-24 Aruze Corporation Gaming machine
US20040106452A1 (en) * 2002-12-02 2004-06-03 Igt Hosted game development environment
US7231269B2 (en) * 2003-03-20 2007-06-12 Microsoft Corporation Recovery upon access violation by audio processing object
ITBO20030368A1 (it) * 2003-06-17 2004-12-18 Qubica S P A Sistema per la gestione di almeno un evento in un impianto da bowling.
US7491122B2 (en) * 2003-07-09 2009-02-17 Wms Gaming Inc. Gaming machine having targeted run-time software authentication
US7226357B2 (en) * 2004-07-07 2007-06-05 Progressive Gaming International Corporation Mechanical wheel casino game of chance having a free-motion internal indicator and method therefor
JP2006065481A (ja) * 2004-08-25 2006-03-09 Aruze Corp 情報処理装置
US8038530B2 (en) 2005-02-28 2011-10-18 Wms Gaming Inc. Method and apparatus for filtering wagering game content
CA2606189A1 (fr) * 2005-05-03 2006-11-09 Igt Dispositif et procede pour interface utilisateur a configuration dynamique pour jeu de hasard
WO2007008845A2 (fr) * 2005-07-08 2007-01-18 Wms Gaming Inc. Systemes de jeu tolerants aux pannes
WO2007027427A2 (fr) * 2005-08-29 2007-03-08 Wms Gaming Inc. Cryptage 'en marche' d'une machine de jeu
EP1954362A4 (fr) 2005-11-22 2011-08-24 Igt Reno Nev Jeu reglemente mise en scene de jeux a actes multiples regulated gaming-staging multi-act games
US7951008B2 (en) * 2006-03-03 2011-05-31 Igt Non-volatile memory management technique implemented in a gaming machine
US7967682B2 (en) 2006-04-12 2011-06-28 Bally Gaming, Inc. Wireless gaming environment
US8366109B2 (en) 2006-04-12 2013-02-05 Bally Gaming, Inc. System and method to handle playing cards, employing elevator mechanism
US8100753B2 (en) 2006-05-23 2012-01-24 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games with selectable odds
US8052519B2 (en) 2006-06-08 2011-11-08 Bally Gaming, Inc. Systems, methods and articles to facilitate lockout of selectable odds/advantage in playing card games
US8206215B2 (en) * 2006-08-31 2012-06-26 Igt Gaming machine systems and methods with memory efficient historical video re-creation
CA2767057A1 (fr) * 2006-09-08 2008-03-13 E-Max Gaming Corporation Unite de jeu electronique sans fil
US7963839B2 (en) * 2006-09-19 2011-06-21 Mudalla Technology, Inc. Regulated gaming exchange
US9101820B2 (en) 2006-11-09 2015-08-11 Bally Gaming, Inc. System, method and apparatus to produce decks for and operate games played with playing cards
US8478833B2 (en) * 2006-11-10 2013-07-02 Bally Gaming, Inc. UDP broadcast for user interface in a download and configuration gaming system
US8195825B2 (en) * 2006-11-10 2012-06-05 Bally Gaming, Inc. UDP broadcast for user interface in a download and configuration gaming method
US9508218B2 (en) 2006-11-10 2016-11-29 Bally Gaming, Inc. Gaming system download network architecture
US9111078B2 (en) 2006-11-10 2015-08-18 Bally Gaming, Inc. Package manager service in gaming system
US8191121B2 (en) 2006-11-10 2012-05-29 Bally Gaming, Inc. Methods and systems for controlling access to resources in a gaming network
US8631501B2 (en) 2006-11-10 2014-01-14 Bally Gaming, Inc. Reporting function in gaming system environment
US8920233B2 (en) 2006-11-10 2014-12-30 Bally Gaming, Inc. Assignment template and assignment bundle in a gaming configuration and download system
US8784212B2 (en) 2006-11-10 2014-07-22 Bally Gaming, Inc. Networked gaming environment employing different classes of gaming machines
US9082258B2 (en) 2006-11-13 2015-07-14 Bally Gaming, Inc. Method and system for providing download and configuration job progress tracking and display via host user interface
US8347280B2 (en) 2006-11-13 2013-01-01 Bally Gaming, Inc. System and method for validating download or configuration assignment for an EGM or EGM collection
US8131829B2 (en) 2006-11-13 2012-03-06 Bally Gaming, Inc. Gaming machine collection and management
US8930461B2 (en) 2006-11-13 2015-01-06 Bally Gaming, Inc. Download and configuration management engine for gaming system
US20080318655A1 (en) * 2007-06-25 2008-12-25 Igt Method and apparatus for players of wagering games to find friends in a gaming environment
US8734245B2 (en) 2007-11-02 2014-05-27 Bally Gaming, Inc. Game related systems, methods, and articles that combine virtual and physical elements
US8201229B2 (en) 2007-11-12 2012-06-12 Bally Gaming, Inc. User authorization system and methods
US8616958B2 (en) 2007-11-12 2013-12-31 Bally Gaming, Inc. Discovery method and system for dynamically locating networked gaming components and resources
US8856657B2 (en) 2008-04-30 2014-10-07 Bally Gaming, Inc. User interface for managing network download and configuration tasks
US9005034B2 (en) 2008-04-30 2015-04-14 Bally Gaming, Inc. Systems and methods for out-of-band gaming machine management
US9483911B2 (en) 2008-04-30 2016-11-01 Bally Gaming, Inc. Information distribution in gaming networks
US8721431B2 (en) 2008-04-30 2014-05-13 Bally Gaming, Inc. Systems, methods, and devices for providing instances of a secondary game
US8382584B2 (en) 2008-05-24 2013-02-26 Bally Gaming, Inc. Networked gaming system with enterprise accounting methods and apparatus
WO2009155047A2 (fr) 2008-05-30 2009-12-23 Bally Gaming, Inc. Pages web pour appareils de jeux de hasard
US8578338B2 (en) * 2008-06-02 2013-11-05 Igt Game production and regulatory approval systems
US8245214B2 (en) * 2008-06-05 2012-08-14 International Business Machines Corporation Reliably updating computer firmware while performing command and control functions on a power/thermal component in a high-availability, fault-tolerant, high-performance server
WO2009158538A1 (fr) 2008-06-27 2009-12-30 Wms Gaming, Inc. Composants d’authentification dans les systèmes de jeux de paris
WO2010006187A2 (fr) 2008-07-11 2010-01-14 Bally Gaming, Inc. Passerelle d'intégration
US8347303B2 (en) 2008-11-14 2013-01-01 Bally Gaming, Inc. Apparatus, method, and system to provide a multi-core processor for an electronic gaming machine (EGM)
US8266213B2 (en) 2008-11-14 2012-09-11 Bally Gaming, Inc. Apparatus, method, and system to provide a multiple processor architecture for server-based gaming
US8423790B2 (en) 2008-11-18 2013-04-16 Bally Gaming, Inc. Module validation
US8192283B2 (en) 2009-03-10 2012-06-05 Bally Gaming, Inc. Networked gaming system including a live floor view module
US8146082B2 (en) * 2009-03-25 2012-03-27 Vmware, Inc. Migrating virtual machines configured with pass-through devices
US9508219B2 (en) * 2009-04-03 2016-11-29 Bally Gaming, Inc. Dynamic management of wagering game availability
US8747228B2 (en) * 2009-10-16 2014-06-10 Nathalie Beaudoin Intermediary module for gaming systems
US8881134B2 (en) * 2010-04-29 2014-11-04 International Business Machines Corporation Updating elements in data storage facility using predefined state machine over extended time period
US9058716B2 (en) 2011-06-06 2015-06-16 Bally Gaming, Inc. Remote game play in a wireless gaming environment
US9120007B2 (en) 2012-01-18 2015-09-01 Bally Gaming, Inc. Network gaming architecture, gaming systems, and related methods
US8974305B2 (en) 2012-01-18 2015-03-10 Bally Gaming, Inc. Network gaming architecture, gaming systems, and related methods
KR20150004638A (ko) * 2013-07-03 2015-01-13 삼성전자주식회사 터치 제어 방법 및 그 전자 장치

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4782468A (en) * 1986-08-05 1988-11-01 Bally Manufacturing Corporation Line power failure scheme for a gaming device
US4948138A (en) * 1982-12-06 1990-08-14 Igt Device for maintaining game state audit trail upon instantaneous power failure

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4283709A (en) * 1980-01-29 1981-08-11 Summit Systems, Inc. (Interscience Systems) Cash accounting and surveillance system for games
US4652998A (en) * 1984-01-04 1987-03-24 Bally Manufacturing Corporation Video gaming system with pool prize structures
US4582324A (en) * 1984-01-04 1986-04-15 Bally Manufacturing Corporation Illusion of skill game machine for a gaming system
US4660833A (en) * 1985-01-02 1987-04-28 Igt Reel monitoring and diagnostic device for an amusement machine
US4911449A (en) * 1985-01-02 1990-03-27 I G T Reel monitoring device for an amusement machine

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4948138A (en) * 1982-12-06 1990-08-14 Igt Device for maintaining game state audit trail upon instantaneous power failure
US4782468A (en) * 1986-08-05 1988-11-01 Bally Manufacturing Corporation Line power failure scheme for a gaming device

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007110294A3 (fr) * 2006-03-29 2007-11-15 Ibm Système, procédé et produit de programme informatique pour stocker de multiples types d'informations
CN113568719A (zh) * 2020-04-29 2021-10-29 北京猎户星空科技有限公司 一种业务故障处理方法、装置、电子设备及存储介质
CN113568719B (zh) * 2020-04-29 2024-04-19 北京猎户星空科技有限公司 一种业务故障处理方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
US5971851A (en) 1999-10-26
ZA9711661B (en) 1998-12-08
AU5807598A (en) 1998-07-31

Similar Documents

Publication Publication Date Title
US5971851A (en) Method and apparatus for managing faults and exceptions
WO1998029162A9 (fr) Procede et appareil permettant de gerer des defaillances et des anomalies
KR100620216B1 (ko) 기능하는 운영 체제 없이 컴퓨터의 원격 관리를 가능하게 하는 네트워크 확장 기본 입출력 시스템
US6438709B2 (en) Method for recovering from computer system lockup condition
JP4356957B2 (ja) 遊技機
JPH07507651A (ja) コンピュータの障害回復および警報システム
US20090204856A1 (en) Self-service terminal
JP2002259130A (ja) 情報処理システムおよびその起動制御方法
JP2008061707A (ja) 遊技機
EP1864701B1 (fr) Dispositif de jeu et methode de detection de fraude pour le dispositif de jeu
JP2002085656A (ja) 遊技機
JP4947731B2 (ja) 遊技機
JP4191351B2 (ja) 遊技機
JP2001198329A (ja) 遊技機
JP4947730B2 (ja) 遊技機
JP2002186757A (ja) 遊技機
JP4744591B2 (ja) 遊技機
JP2001198272A (ja) 遊技機
JP2009119284A (ja) 遊技機
WO2001080007A2 (fr) Procedes et appareil assurant le fonctionnement consistant d'un systeme informatique comportant des composants redondants
JP2002224400A (ja) 遊技機
JP2009061344A (ja) 遊技機
JP2009061345A (ja) 遊技機
JP2009061347A (ja) 遊技機
JP2009061348A (ja) 遊技機

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM GW HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZW AM AZ BY KG KZ MD RU TJ TM

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SZ UG ZW AT BE CH DE DK ES FI FR GB GR IE

COP Corrected version of pamphlet

Free format text: PAGES 1/9-9/9, DRAWINGS, REPLACED BY NEW PAGES 1/8-8/8; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase