AU2011253637A1 - A system and method for managing meters in a gaming system - Google Patents

Abstract

- 18 A method of managing meters in a gaming system comprises a first step of temporarily storing meter information in a 5 cache of a gaming management module. Upon receipt of an instruction from the gaming system, the meter information temporarily stored in cache is written to a storage location. 10 Figure 3. 29706021 (GHMatlers) P73958 AU.2

Description

AUSTRALIA Patents Act 1990 COMPLETE SPECIFICATION Standard Patent Applicant(s): ACEI AB Invention Title: A SYSTEM AND METHOD FOR MANAGING METERS IN A GAMING SYSTEM The following statement is a full description of this invention, including the best method for performing it known to me/us: -2 A SYSTEM AND METHOD FOR MANAGING METERS IN A GAMING SYSTEM FIELD OF THE INVENTION 5 The present invention relates to a system and method for managing meters in a gaming system. Embodiments of the invention find particular, but not exclusive, use in gaming machines. 10 BACKGROUND OF THE INVENTION It is often desirable or necessary to require the collection and recording of a number of events and measurement parameters that occur when a user interacts 15 with a gaming machine or a gaming system. Such events or parameters are also called meters or meter information. One example of a meter is a physical hardware, non resettable (i.e. absolute) counter that registers events such as the input and output of money (e.g. the payment of 20 bills or coins), the number of win events and the amount of each stake or bet. Particular games may also include further counters specific to the game type. In network based gaming systems (i.e. where a number 25 of gaming machines are connected to a central server), it is known to send information gathered from the meters to the server, for reporting and other requirements. In a client-server based gaming system with a large number of gaming machines connected to a number of game 30 application servers that record data in a database there is a large number of transactions relating to the meters. SUMMARY OF INVENTION 35 In a first aspect, the present invention provides a method of managing meters in a gaming system, comprising the steps of, temporarily storing meter information in a 29706021 (GHMatters) P73858.AU.2 - 3 cache of a gaming management module, and writing the meter information from the cache to a storage location on the receipt of an instruction from the gaming system. The method may include the further step of, on 5 receipt of the instruction from the gaming system, updating the cached meter information prior to writing the meter information to the storage location. The instruction may be event information received from a device associated with the gaming system, such as, 10 for example, the initiation of a game event by a user. In more detail, the event information may be the addition of credit by a user. The method may include the further step of requesting predefined meter information from the device, and writing 15 the predefined information to the storage location. The information may be deemed as committed on the successful completion of the event, and if so, a message may be returned to the system reporting the successful storage of the meter information. 20 The meter information may be information pertaining to a game provided by the system or information pertaining to a parameter in the device. In one embodiment, the device is a gaming device. The storage location may be a database and the 25 information and/or meter information may be provided in an XML format. In a second aspect, the present invention provides a system for managing meters in a gaming system, comprising, a game management module including a cache arranged to 30 temporarily store meter information, and a write module arranged to write the meter information from the cache to a storage location on the receipt of an instruction from the gaming system. In a third aspect, the present invention provides a 35 computer program arranged to, when executed on a computing system, carry out the method steps in accordance with the first aspect of the invention. 2970802_1 (GHMatters) P73858.AU.2 -4 In a fourth aspect, the present invention provides a computer readable medium storing a computer program in accordance with a third aspect of the invention. In a fifth aspect, the present invention provides a 5 data signal comprising the computer program code in accordance with the third aspect. DETAILED DESCRIPTION OF THE DRAWINGS 10 Embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings in which: Figure 1 is an example computing system capable of implementing an embodiment of the invention; 15 Figure 2 is an example network environment capable of interacting with an embodiment of the invention; Figure 3 is a schematic diagram illustrating the component parts of a system in accordance with an embodiment of the invention; 20 Figure 4 is a flow chart depicting the method steps performed by an embodiment of the invention; Figures 5 and 6 are flow charts depicting the method steps performed to execute two example transactions in accordance with an embodiment of the invention; 25 Figure 7 is an example of a portion of a database structure in accordance with an embodiment of the invention; Figures 8 and 9 are XML Schemas utilised to transfer game meter data in accordance with an embodiment of the 30 invention; and Figures 10, 11 and 12 are examples of XML utilised to transfer game meter data in accordance with an embodiment of the invention. 35 DESCRIPTION OF AN EMBODIMENT The present invention, in at least one embodiment, 2970602_1 (GHMatters) P73858 AU 2 -5 provides a method of managing meters in a gaming system. Meter information is temporarily stored in a cache of a gaming management module, and the meter information is written from the cache to a storage location. The writing 5 occurs on the receipt of an instruction from the gaming system. The system, method and associated software application in accordance with an embodiment of the invention may be executed on a computing system such as 10 the example computing system shown in Figure 1. At Figure 1 there is shown a schematic diagram of a computing system 100 suitable for use with an embodiment of the present invention. The computing system 100 may be used to execute applications and/or system services such 15 as the collection, aggregation, processing and reporting of data in accordance with an embodiment of the present invention. The computing system 100 preferably comprises a processor 102, read only memory (ROM) 104, random access 20 memory (RAM) 106, and input/output devices such as disk drives 108, keyboard 110 (or other input peripherals such as a mouse, not shown), display 112 (or other output peripherals such as a printer, not shown) and communications link 114. The computer includes programs 25 that may be stored in ROM 104, RAM 106, or disk drives 108 and may be executed by the processor 102. The communications link 114 connects to a computer network but could be connected to a telephone line, an antenna, a gateway or any other type of communications 30 link. Disk drives 108 may include any suitable storage media, such as, for example, floppy disk drives, hard disk drives, CD ROM drives or magnetic tape drives. The computing system 100 may use a single disk drive or multiple disk drives. The computing system 100 may use any 35 suitable operating system, such as Windows" or Unix". The computing system 100 may be a gaming server arranged to be networked to a plurality of gaming 297002_1 (GHMatters) P73858.AU.2 - 6 machines, such that information may be sent from the gaming server to one or more gaming machines, or from the one or more gaming machines to the gaming server. The computing system 100 may be capable of executing 5 a software application 116 (which may be in the form of an API) in accordance with an embodiment of the invention. It will be understood that the computing system described in the preceding paragraphs is illustrative only and that the presently described embodiment or other 10 embodiments which fall within the scope of the claims of the present application may be executed on any suitable computing system, which in turn may be realized utilizing any suitable hardware and/or software. Other computing systems that may be suitable include 15 server computers, hand-held or portable computing devices, consumer electronics devices, and other devices capable of receiving and/or processing electronic information, including automated 'teller' machines and vending machines. 20 Figure 2 illustrates an example network environment 200, with a server computer 202 in communication with client computers 204a, 204b, 204c, etc., via a network (or a bus) 206, in which an embodiment of the present invention may be employed. 25 In more detail, the server 202 may be a gaming server, arranged to interconnect a number of gaming machines 204a, 204b, 204c, etc., via the communications network 206, which may be a local or wide area network, such as an intranet, the Internet, etc. 30 It will be understood that the client computers need not be gaming machines, but may be a terminal, another computing system, a portable communications device, such as a mobile telephone, or any other device capable of receiving information from the server. 35 The server 202, and the client devices 204a, 204b, 204c, etc., may communicate with each other over the communications network 206 by use of any suitable 2970602.1 (GHMatters) P73858 AU.2 - 7 networking protocol, such as TCP/IP, GSA G2S (Gaming Standards Association Game-to-System protocol), GSA S2S (Gaming Standards Association System-to-System protocol) or any other suitable protocol for the exchange of 5 information 208. The exchange of information may include the provision of XML files, the XML files providing information to be utilized by any or all of the servers and client devices. Referring now to Figure 3, there is shown a schematic 10 diagram illustrating the components of a system in accordance with an embodiment of the present invention. Figure 3 is a schematic diagram that depicts a system in accordance with an embodiment of the present invention. A gaming machine 300 is connected to a game application 15 server 302. The game application server 302 is connected to (or includes) a game server database 304. The game server database 304 utilises a database logic layer 306 to interact with the game application server 302. While the embodiment described with reference to Figure 3 only shows 20 one gaming machine 300 connected to one game application server 302, it will be understood that a plurality of gaming machines may be connected to the game application server 302. The gaming machine 300 contains and is capable of 25 executing client game software, which may allow a number of games, 308a, 308b, 308c, etc. to be played on the gaming machine. The game application server 302 includes a plurality of software modules, including manager modules 310, 30 wherein each manager module is arranged to manage a different function of the game application server 302. It will be understood that each module may also contain sub-modules, arranged to perform particular functions. 35 In the embodiment described herein, there is included the following modules: - a gaming machine manager 312; 29708021 (GHMatters) P73858.AU.2 - 8 - a game manager 314 which includes combined game application interface (GDK) and server game software modules 316 for each of games Game 1 to Game #; - a jackpot manager 318; 5 - a meter manager 320 comprising meter logic 322, a platform meter cache 324 and a game meter cache 326. The cache 326, in the embodiment described herein, is dynamically created in the gaming application server 302, by any appropriate method, such as, for example, the 10 allocation or 'blocking' of a portion of memory in RAM or ROM. In the specific embodiment described herein, there is provided one platform meter cache instance per gaming machine 300 that is connected to the game application 15 server 302. In other words, there is one game meter cache per gaming machine and per game. It will be understood that the cache, in the embodiment described, is contained in the game application server, and is arranged to hold information pertaining to 20 a number of metres, including so-called "game specific" meters. The game application server and the platform as a whole, while containing the cache, need have no specific knowledge of the game specific meters. That is, the game specific meters may be retrieved, set and incremented by 25 the game, wherein the gaming machine interacts directly with the game specific meter and cache. In other words, game specific meters may be used where a game keeps statistical information that is game specific and not needed by the system as a whole for the 30 successful execution of the game. Furthermore, additional game specific meters can be generated dynamically (i.e. post implementation) upon instruction by the individual gaming machines. For example, new game meters can be generated to cater for new regulatory requirements (e.g. 35 to gather prescribed statistical information not already collected by the pre-existing meters) thereby allowing the machines to be implemented in that region without needing 2970602_1 (GHMatts) P73858.AU.2 - 9 to modify the platform. It will be understood that while, in the embodiment described, the cache 326 resides in the game application server, an alternate embodiment may include the cache in 5 the gaming machine 300. In the client-server based gaming system all events occurring in the course of executing a game are registered in the game server database 304. Predefined meters are also registered in the database. The meters are handled 10 separately from but tightly coupled with the normal event registration. The meter registration is handled in a sequence with the normal event registration as a part of an "atomic" transaction in the sense that all steps are performed or 15 the transaction is considered not to have occurred. The transaction is managed by the logic layer 306 of the database 304. The transaction includes two separate database storage operations that are required to have occurred 20 before the transaction can be committed. Referring to Figure 4, there is described in detail the method steps by which a transaction is committed to the database 304. The method steps in accordance with the described 25 embodiment include: At initial step 400, an event that requires a meter to be updated occurs in the gaming machine 300. This may be due to player input or due to some external factor (e.g. the application of credit to the machine by the game 30 application server); At subsequent step 402, there is triggered a request to send associated event information from the gaming machine 300 to the gaming machine manager 312 of the game application server 302; 35 At step 404, a database transaction is initiated; At step 406, event information is stored in the database 304; 2970602_1 (GHMatlrs) P73858.AU.2 - 10 At step 408, the meter values are appropriately incremented; At step 410, the updated meter values are stored in the database 304; 5 At step 412, the database transaction is committed; At step 414, the event is processed and a result is generated. The event may involve calculation, random number generation or game result generation. If this is the case, then the meters may be further updated. If so, 10 the method reverts to step 404, to store the new meter information; At step 416, once the new meter information has been committed to the database, a result response message is generated and sent to the gaming machine 300; and 15 At step 418, a result presentation is generated in the gaming machine and presented to the player. After the result is displayed, the gaming machine reverts to step 400 (i.e. the gaming machine 300 waits for a new event). Referring now to Figure 5, there is provided a 20 flowchart outlining the method steps performed by an embodiment of the invention when an example transaction is performed. The example of Figure 5 describes the method steps performed when updating the platform meter. Step 500: The Player inserts an amount of money in a 25 gaming machine 300. Step 502: The gaming machine 300 sends information about the amount of money inserted to the gaming machine manager 312 in game application server 302. Step 504: The gaming machine manager 312 stores a value 30 representing the amount of money inserted into the machine in the database 304. The value may be defined as a number of 'credits' available for play. In turn, a database transaction T is initiated, which is managed by the logic layer 306 of the database 304. 35 Step 506: The database 304 reports the current balance of credits to the gaming machine manager 312. Step 508: The gaming machine manager 312 sends predefined 2970602.1 (GHMatters) P73858AU.2 - 11 meter information to the meter logic 322 of the meter manager 320. Step 510: The meter logic 322 collects the values of each of the current meters associated with the gaming machine 5 in the platform meter cache 324. Step 512: The meter logic 322 stores the set of retrieved meter values in the database 304. Step 514: The transaction T is committed and a commit message is sent by the database logic layer 306 to the 10 gaming machine manager 312. Step 516: The gaming machine manager 312 generates and sends a message to the gaming machine 300 with information about the current balance of credits. The current balance is presented to the player on the gaming machine and the 15 gaming machine waits for the next input by the player. Referring now to Figure 6, there is provided a further flowchart outlining the method steps performed by an embodiment of the invention when another example transaction is performed. The example of Figure 6 20 describes the method steps performed when updating the game meter. Step 600: A player has started a game, selects an amount to bet and initiates a game. Step 602: The gaming machine 300 sends information about 25 the bet to the game manager 314 in game application server 302. Step 604: The game manager 314 stores the bet value and possible other game related information in the database 304 and thereby starts a database transaction T1 managed 30 by the logic layer 306 of the database 304. Step 606: The game manager 314 sends predefined game meter information to the meter logic 322 of the meter manager 320. Step 608: The meter logic 322 utilises the game meter 35 cache to update stored meter values (e.g. bet value, game round, and other game related meter information provided at step 602) and stores the updated (i.e. now current) 2970602_1 (GHMatters) P73853.AU.2 - 12 meter values in the database 304. It will be understood by persons skilled in the art that the step of updating the meter values may involve various processing operations including incrementing the meter values, decreasing the 5 meter values or otherwise adjusting the meter values. Step 610: The transaction T1 is committed and a commit message is sent by the database logic layer 306 and the commit message is sent to the game manager 314. Step 610: The game manager 314 generates a result, and 10 stores the result information in the database 304, thereby initiating a database transaction T2 managed by the logic layer 306 of the database 304. Step 612: The game manager 314 sends predefined game meter information to the meter logic 322 of the meter manager 15 320 both with regard to any affected platform meters and game meters. Step 614: The meter logic 322 updates meters associated with the game in the platform meter cache 324 (e.g. a new balance) and in the game meter cache 326 (e.g. win count, 20 win amount, game round start meters, game round end meters). Again, the step of updating involves appropriately adjusting the previously stored meter values to attain the current meter values (i.e. incrementing, decrementing, etc.) 25 Step 616: The transaction T2 is committed and a commit message is sent by the database logic layer 306. Step 618: The game manager 314 generates and sends a message to the gaming machine 300 with result information and the result is presented to the player on the gaming 30 machine. The machine then returns to initial step 600 to wait for next player input. With reference to Figure 7, there is now described an example of the data structure utilised to contain and transmit meter information in the gaming system of 35 Figure 3. In the present embodiment, the meter information is created, transmitted and stored in an XML format. In more detail, meters are kept in a meter 2970602_1 (GHMatters) P73858.AU.2 - 13 collection, wherein each meter is ascribed a different name. In the example described with reference to Figure 7, the collection is termed "Meters". The Meters collection is used to update meters and to generate the XML used for 5 storage in the database and for sending meter update messages to the gaming machine. With reference to database table 700 in Figure 7, there are shown two example functions in the meter collection. The function ToXml generates a full meter set 10 in XML. The function ModifiedToXml only generates a modified meter set (i.e. it returns only the meter values which have been modified since the last meter read). ModifiedToXml also clears a "modified" flag on each meter. In one embodiment, a modified meter list may be 15 utilised in the Meters collection instead of utilising a flag for each meter. The MeterCache holds meters by ID (an alphanumeric identifier) and is used for the platform by client ID. Game meters will be cached by game variant ID and client 20 ID by storing the Meters in the running game session cache for the current game by client. Figure 8 is an example XML Schema definition, which is used for periodic and audit (freeze) values. In a situation where space is limited in the database (for 25 example, where an embodiment of the present invention is retrofitted into a legacy gaming system with limited memory and/or processing facilities), a compact version of the XML schema may be used. An example of such a schema is given in Figure 9. 30 Figure 10 provides some examples of XML based on the XML schemas of Figures 8 and 9. Moreover, in some situations, to reduce network traffic, it is possible to "piggy back" meter information in XML sent in response to other gaming machine requests. 35 Examples of such piggy backs are shown in Figures 11 and 12, where meter information is incorporated into an XML document which has another purpose (such as sending 2970602_1 (GHMatters) P73858AU.2 - 14 general information to the gaming machine). In Figure 11, an example of a piggy back for a platform update message is given, while in Figure 12, an example of piggy back for a game meter update message is given. 5 That is, both platform and game meter updates can be piggy backed in the response for any request. In the case of a game meter, this may occur where a game round is ended. Game start and game end messages contain the ID attributes identifying the game in the external system. 10 Although not required, the embodiments described above may be implemented via an application programming interface (API), for use by a developer, and can be included within another software application, such as a gaming machine operating system or a gaming server 15 operating system. Generally, as program modules include routines, programs, objects, components, and data files that perform or assist in the performance of particular functions, it will be understood that a software application which 20 carries out method steps in accordance with an embodiment of the invention may be distributed across a plurality of routines, objects and components, which correspondingly may be located across a plurality of physical hardware devices. Such variations and modifications are within the 25 purview of those skilled in the art. 29706021 (GHMatters) P73858.AU.2

Claims (29)

1. A method of managing meters in a gaming system, 5 comprising the steps of, temporarily storing meter information in a cache of a gaming management module, and writing the meter information from the cache to a storage location on receipt of an instruction from the gaming system. 10

2. A method in accordance with claim 1, comprising, on receipt of the instruction from the gaming system, updating the cached meter information prior to writing the meter information to the storage location. 15

3. A method in accordance with claim 1 or 2, wherein the instruction is event information received from a device associated with the gaming system.

4. A method in accordance with claim 3, wherein the event information is the initiation of a game event 20 by a user.

5. A method in accordance with claim 3, wherein the event information is the addition of credit by a user.

6. A method in accordance with claim 3, 4 or 5, 25 comprising the further step of, requesting predefined meter information from the device, and writing the predefined information to the storage location.

7. A method in accordance with any one of the preceding claims, comprising the further step of deeming the 30 information as committed on the successful completion of the event.

8. A method in accordance with claim 7, comprising the further step of, on deeming the information as committed, returning a message to the system 35 reporting the successful storage of the meter information.

9. A method in accordance with any one of the preceding 2970502_1 (GHMatters) P73858AU.2 - 16 claims, wherein the meter information is information pertaining to a game provided by the system.

10. A method in accordance with any one of the preceding claims, whereby the meter information is information 5 pertaining to a parameter in the device.

11. A method in accordance with any one of the preceding claims, whereby the storage location is a database.

12. A method in accordance with any one of the preceding claims, whereby the meter information is provided in 10 an XML format.

13. A method in accordance with any one of the preceding claims, whereby the device is a gaming machine.

14. A system for managing meters in a gaming system, comprising a game management module including a cache 15 arranged to temporarily store meter information, and a write module arranged to write the meter information from the cache to a storage location on receipt of an instruction from the gaming system.

15. A system in accordance with claim 14, comprising an 20 update module arranged to, on receipt of the instruction from the gaming system, update the cached meter information.

16. A system in accordance with claim 14 or 15, wherein the instruction is event information received from a 25 device associated with the gaming system.

17. A system in accordance with claim 16, wherein the event information is the initiation of a game event by a user.

18. A system in accordance with claim 16, wherein the 30 event information is the addition of credit by a user.

19. A system in accordance with claim 16, 17 or 18, wherein the update module requests predefined meter information from the device. 35

20. A system in accordance with any one of claims 14 to 19, wherein the information is deemed as committed on the successful completion of the event. 2970602_1 (GHMatters) P73858.AU.2 - 17

21. A system in accordance with claim 20, wherein a return module, on deeming the information as committed, returns a message to the system reporting the successful storage of the meter information. 5

22. A system in accordance with any one of claims 14 to 21, wherein the meter information is information pertaining to a game provided by the system.

23. A system in accordance with any one of claims 14 to 22, wherein the meter information is information 10 pertaining to a parameter in the device.

24. A system in accordance with any one of claims 14 to 23, wherein the storage location is a database.

25. A system in accordance with any one of claims 14 to 24, wherein the meter information is provided in an 15 XML format.

26. A system in accordance with any one of claims 14 to 25, wherein the device is a gaming machine.

27. Computer program code which, when executed on a computing system, implements the method of any one of 20 claims 1 to 14.

28. A computer readable medium storing a computer program in accordance with claim 27.

29. A data signal comprising the program code of claim 27. 25 2970802_1 (GHManers) P73858 AU 2