AU2008200338B2 - Transaction processing system and method - Google Patents
Transaction processing system and method Download PDFInfo
- Publication number
- AU2008200338B2 AU2008200338B2 AU2008200338A AU2008200338A AU2008200338B2 AU 2008200338 B2 AU2008200338 B2 AU 2008200338B2 AU 2008200338 A AU2008200338 A AU 2008200338A AU 2008200338 A AU2008200338 A AU 2008200338A AU 2008200338 B2 AU2008200338 B2 AU 2008200338B2
- Authority
- AU
- Australia
- Prior art keywords
- end database
- database server
- client
- data
- server
- 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.)
- Ceased
Links
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
- A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
- A63F13/30—Interconnection arrangements between game servers and game devices; Interconnection arrangements between game devices; Interconnection arrangements between game servers
- A63F13/35—Details of game servers
- A63F13/352—Details of game servers involving special game server arrangements, e.g. regional servers connected to a national server or a plurality of servers managing partitions of the game world
-
- 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
- A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
- A63F13/70—Game security or game management aspects
- A63F13/79—Game security or game management aspects involving player-related data, e.g. identities, accounts, preferences or play histories
-
- 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
- A63F2300/00—Features of games using an electronically generated display having two or more dimensions, e.g. on a television screen, showing representations related to the game
- A63F2300/50—Features of games using an electronically generated display having two or more dimensions, e.g. on a television screen, showing representations related to the game characterized by details of game servers
- A63F2300/51—Server architecture
- A63F2300/513—Server architecture server hierarchy, e.g. local, regional, national or dedicated for different tasks, e.g. authenticating, billing
-
- 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
- A63F2300/00—Features of games using an electronically generated display having two or more dimensions, e.g. on a television screen, showing representations related to the game
- A63F2300/50—Features of games using an electronically generated display having two or more dimensions, e.g. on a television screen, showing representations related to the game characterized by details of game servers
- A63F2300/55—Details of game data or player data management
- A63F2300/5546—Details of game data or player data management using player registration data, e.g. identification, account, preferences, game history
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- Computer Security & Cryptography (AREA)
- General Business, Economics & Management (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Pinball Game Machines (AREA)
Description
AUSTRALIA Patents Act 1990 COMPLETE SPECIFICATION Standard Patent Applicant(s) ACEI AB Invention Title: TRANSACTION PROCESSING SYSTEM AND METHOD The following statement is a full description of this invention, including the best method for performing it known to me/us: -2 Title TRANSACTION PROCESSING SYSTEM AND METHOD 5 Field The present invention relates to a transaction processing system and a transaction processing method. 10 Background to the Invention In the gaming industry, there is a move towards server based gaming systems where the majority of the gaming functions are implemented on a server and the gaming 15 machines played by players are clients of the server. For such implementations to be effective, transactions between the gaming machines (also known as gaming terminals) and the server need to be carried out in real 20 time. That is, without any delay that is apparent to the player. Where there are a larger number of gaming machines connecting to a server, the server can be exposed to high 25 loads and hence in a gaming system with a large number of gaming machines, the server may require significant CPU processing power, particularly in light of the fact that the relationship between increased load and CPU power is not linear. This can result in a high investment cost for 30 hardware. Accordingly, there is a need for an architecture suitable for a gaming system that is capable of handling high transaction loads. 35 N \Melboume\Cases\Patent\71000-71999\P71099.AU. I\Specis\P71099.AU CAP Spccification 2007-1-3.doc 23/01/08 - 3 Summary of the Invention In a first aspect, there is disclosed a transaction processing system comprising: 5 a back end database server storing a client data record of a client; and a front end database server in data communication with the back end database server, the front end database server arranged to retrieve data from the client data 10 record when the client connects to the front end database server and to thereafter process transactions related to the retrieved data, the front end database server further arranged to communicate data to the back end database server to update the client data record based on the 15 processed transactions. In an embodiment, the back end database server stores client data records for each of a plurality of clients. 20 In an embodiment, the transaction system comprises a plurality of front end database servers, each in data communication with the back end database server, the front end database servers arranged to share connection requests from clients amongst one another. 25 In an embodiment, the transaction system comprises at least one an application server arranged such that each client connects to a front end database server via the application server. 30 In an embodiment, the transaction system comprises a plurality of clients in data communication with the front end database server. 35 In an embodiment, each client is a gaming terminal. In an embodiment, the front end database server processes N:\Melboume\Cases\Patent\71000-7l999\P71099 AU. I\Specis\P71099.AU CAP Specification 2007-1-3.doc 23/01/08 - 4 transactions based on data communicated from the client. In an embodiment, the transaction system is further arranged to transfer responsibility for processing 5 transactions of a client from a failed front end database to another front end database server. In a second aspect there is disclosed a transaction processing method comprising: 10 retrieving data at a front end database server from a back end database server storing a data record for a client when the client connects to the front end database server ; processing transactions related to the retrieved is data at the front end database server; and communicating data from the front end database server to the back end database server required to update the client's data record based on the processed transactions. 20 In an embodiment, the transaction processing comprises processing transaction related to the retrieved data based on data communicated from the client. 25 Brief Description of the Drawings An embodiment of the invention will now be described in relation to the accompanying drawings in which: Figure 1 is a block diagram of a transaction 30 processing system; and Figure 2 is a flow chart of a transaction processing method. Detailed Description 35 Referring to the drawings there is shown a transaction processing system 100 and method for a database based N:\Melboume\Cases\Patent\71000-71999\P71099.AU I\Specis\P71099.AU CAP Specification 2007-1-3.doc 23/01/08 -5 gaming system that is designed to handle high loads in a real-time environment. The transaction processing system 100 has a back end 5 database server (BEDS) 110 that is the focal point of the system where all data needed by different nodes is shared. The back end database server 110 is also where all client data is stored. The gaming system 100 has a plurality (N) of front end database servers (FEDS) 120A-120E adapted to 10 receive connection requests from a plurality (M) of clients 130A-130G. Clients 130E and 130F are shown as connecting to front end database server 120D via an application server 125 to illustrate that depending on the embodiment, none, some or all of the clients 130A-130G may 15 connect to a front end database server 120 via an application server 125. When a front end database server 120 is started, it connects 210 to the back end database server 110. When a 20 front end database server 120 receives a connection request from a client, it either accepts the request or passes the client the identity of another front end database server 130 if this will achieve load balancing between the plurality of front end database servers 120. 25 Load balancing data is communicated between the front end database servers 120. If the front end database server 120 accepts the request, it requests client data 220 from the back end database 30 server 110. The back end database server 110 retrieves either the entire data record for the client from database 115 or a subset of data that is expected to be accessed frequently. The back end database server 110 then communicates the relevant data to the front end database 35 server 120. Examples of data that may be transferred to the front end database server include status, number of notes, number of coins in the coin acceptor, etc. N:\Melboume\Cases\Patent\71000-71999\P71099.AU \Specis\P71099 AU CAP Specification 2007-L-3 doc 23/01/08 - 6 Once the front end database server 120 accepts the request it will accept transaction requests from the client 130, for example, to update a current record of the credit 5 meter in the database. The front end database server 120 processes the request 230, updates the local version of the client data and waits 240 for further transactions. The front end database server 120 also starts a parallel 10 process 260-275 to update the client data stored in database 115 of back end server database. That is the front end data base server 120 sends update data to the back end database server 110 which updates 265 the database 115. 15 In this manner, the front end database server 120 is able to process the transaction requests in real-time while the back end server 110 is updated in near real-time. 20 When there are no more transactions, the front end database server 120 returns control of the data to the back end database server 120. This process involves determining that all data has been updated 270 so that the database 115 is synchronised to the data that has been 25 updated locally by the front end database server 120. A number of additional features provide additional robustness to the handling of transactions. Specifically, the system is designed such that when application servers 30 125 are employed, a client can fail over from one application server to another and hence that ownership of a client can be moved from one application server or front end database server 120 to another. If application servers are not employed the system is designed so that a client 35 can fail over from one front end database server 120 to another so that ownership of a client can be moved from one front end database server 120 to another. In addition, N.\Melboume\Cases\Patent\71000-71999\P71099.AU. l\Specis\P71099.AU CAP Specification 2007-1-3.doc 23/01/08 -7 an application server can be reconfigured to connect to a different front end database server 120. The system can employ "hot" or "cold" standby servers and the front end database servers 120 can fail over to their standby 5 configuration. The back end database server 110 can also fail over to its standby configuration. Alternatively, or in addition to employing standby services, the system can employ Real Application Clusters 10 which allow multiple instances on different nodes to access a shared database on a cluster system for load balancing. These and other modifications will be apparent to persons is skilled in the art and should be considered as falling within the scope of the invention described herein. In the claims which follow and in the preceding description of the invention, except where the context 20 requires otherwise due to express language or necessary implication, the word "comprise" or variations such as "comprises" or "comprising" is used in an inclusive sense, i.e. to specify the presence of the stated features but not to preclude the presence or addition of further 25 features in various embodiments of the invention. It is to be understood that, if any prior art publication is referred to herein, such reference does not constitute an admission that the publication forms a part of the 30 conmnon general knowledge in the art, in Australia or any other country. N.\Melboumc\Cascs\Patent\71000-7 999\P71099.AU I\Specis\P7I099 AU CAP Specification 2007.1 -3.doc 23/01/08
Claims (10)
1. A transaction processing system comprising: a back end database server storing a client data s record of a client; and a front end database server in data communication with the back end database server, the front end database server arranged to retrieve data from the client data record when the client connects to the front end database 10 server and to thereafter process transactions related to the retrieved data, the front end database server further arranged to communicate data to the back end database server to update the client data record based on the processed transactions. 15
2. A transaction system as claimed in claim 1, wherein the back end database server stores client data records for each of a plurality of clients. 20
3. A transaction system as claimed in claim 2, comprising a plurality of front end database servers, each in data communication with the back end database server, the front end database servers arranged to share connection requests from clients amongst one another. 25
4. A transaction system as claimed in any one of claims 1 to 3, comprising at least one an application server arranged such that each client connects to a front end database server via the application server. 30
5. A transaction system as claimed in any one of claims 1 to 4 comprising a plurality of clients in data communication with the front end database server. 35
6. A transaction system as claimed in claim 5, wherein each client is a gaming terminal. N \Melboune\Cases\Patent\71000-71999\P7]099.AU \Specis\P71099 AU CAP Spccification 2007-1-3.doc 23/01/08 -9
7. A transaction system as claimed in claim 5 or claim 6, wherein the front end database server processes transactions based on data communicated from the client. 5
8. A transaction system as claimed in claim 3, further arranged to transfer responsibility for processing transactions of a client from a failed front end database to another front end database server. 10
9. A transaction processing method comprising: retrieving data at a front end database server from a back end database server storing a data record for a client when the client connects to the front end database server ; 15 processing transactions related to the retrieved data at the front end database server; and communicating data from the front end database server to the back end database server required to update the client's data record based on the processed 20 transactions.
10. A transaction processing method as claimed in claim 9, comprising processing transaction related to the retrieved data based on data communicated from the client. 25 N:\Melboume\Cases\Patent\71000-71999\P71099.AU l\Specis\P7 l099.AU CAP Specification 2007-1-3.doc 23/01/08
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| AU2008200338A AU2008200338B2 (en) | 2007-02-01 | 2008-01-23 | Transaction processing system and method |
| AU2010202059A AU2010202059B2 (en) | 2007-02-01 | 2010-05-20 | Transaction processing system and method |
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| AU2007900476 | 2007-02-01 | ||
| AU2007900476A AU2007900476A0 (en) | 2007-02-01 | Transaction processing system and method | |
| AU2008200338A AU2008200338B2 (en) | 2007-02-01 | 2008-01-23 | Transaction processing system and method |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| AU2010202059A Division AU2010202059B2 (en) | 2007-02-01 | 2010-05-20 | Transaction processing system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| AU2008200338A1 AU2008200338A1 (en) | 2008-08-21 |
| AU2008200338B2 true AU2008200338B2 (en) | 2010-05-13 |
Family
ID=42261849
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| AU2008200338A Ceased AU2008200338B2 (en) | 2007-02-01 | 2008-01-23 | Transaction processing system and method |
| AU2010202059A Ceased AU2010202059B2 (en) | 2007-02-01 | 2010-05-20 | Transaction processing system and method |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| AU2010202059A Ceased AU2010202059B2 (en) | 2007-02-01 | 2010-05-20 | Transaction processing system and method |
Country Status (1)
| Country | Link |
|---|---|
| AU (2) | AU2008200338B2 (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1553511A1 (en) * | 2002-07-16 | 2005-07-13 | Konami Online, Inc. | Network service system and point commuting system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030177187A1 (en) * | 2000-11-27 | 2003-09-18 | Butterfly.Net. Inc. | Computing grid for massively multi-player online games and other multi-user immersive persistent-state and session-based applications |
| US20070010330A1 (en) * | 2005-01-04 | 2007-01-11 | Justin Cooper | System and method forming interactive gaming over a TV network |
-
2008
- 2008-01-23 AU AU2008200338A patent/AU2008200338B2/en not_active Ceased
-
2010
- 2010-05-20 AU AU2010202059A patent/AU2010202059B2/en not_active Ceased
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1553511A1 (en) * | 2002-07-16 | 2005-07-13 | Konami Online, Inc. | Network service system and point commuting system |
Also Published As
| Publication number | Publication date |
|---|---|
| AU2010202059A1 (en) | 2010-06-10 |
| AU2008200338A1 (en) | 2008-08-21 |
| AU2010202059B2 (en) | 2013-10-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6598077B2 (en) | System and method for dynamic content routing | |
| US20210109917A1 (en) | System and Method for Processing a Database Query | |
| US8170981B1 (en) | Computer method and system for combining OLTP database and OLAP database environments | |
| US7734608B2 (en) | System, method and computer program product for querying data relationships over a network | |
| JP4599581B2 (en) | Information distribution system, distribution request program, transfer program, distribution program, etc. | |
| AU2010202714B2 (en) | System and method for managing transfer of player rights | |
| CN102571991A (en) | Multistage-mapping-based large-scale multi-copy distributed storage system and application method thereof | |
| US20090012977A1 (en) | System for estimating cardinality in a database system | |
| CN106708826A (en) | Data processing method and apparatus, and data query method and apparatus | |
| US20030037149A1 (en) | Distributed and fault tolerant server system and method | |
| CN110830582B (en) | Cluster owner selection method and device based on server | |
| US9264519B1 (en) | Embedding application services in a distributed datastore | |
| EP1953655A2 (en) | Transaction processing system and method | |
| AU2008200338B2 (en) | Transaction processing system and method | |
| CN108712508A (en) | A kind of load-balancing method and device | |
| US20140304288A1 (en) | Method and system for data cache handling | |
| CN115330451A (en) | Dynamic adjustable and configurable real-time lottery drawing method and system supporting high concurrency | |
| AU2013266979A1 (en) | Transaction processing system and method | |
| KR100683238B1 (en) | Online game provision method and system | |
| CA2517211A1 (en) | System and method for searching and retrieving certificates | |
| US20110153565A1 (en) | Configuration information management device, distributed information management system and method | |
| CN107508699A (en) | Suitable for the strange land dual-active realization method and system of stock services | |
| JP5666186B2 (en) | Financial transaction system and server device thereof | |
| EP1913500A2 (en) | Transaction protection in a stateless architecture using commodity servers | |
| US10645186B2 (en) | Speculative caching in a content delivery network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FGA | Letters patent sealed or granted (standard patent) | ||
| HB | Alteration of name in register |
Owner name: VIDEOBET INTERACTIVE SWEDEN AB Free format text: FORMER NAME(S): ACEI AB |
|
| MK14 | Patent ceased section 143(a) (annual fees not paid) or expired |