Amusement and premiums network

Description of equivalent WO 0038089 A2

J

00021

AMUSEMENT AND PREMIUMS NETWORK

FIELD OF THE INVENTION

0005This invention relates to the field of data communications, and in particular to a method and a system for on-line global distribution and redemption of loyalty points and coupons, control of directed advertising and control of parameters related to various operations, activity software, etc. BACKGROUND TO THE INVENTION

0006Electronic transaction processing and awarding of loyalty points by bank card issuers, airlines, etc. have come into widespread use. For example, retailers commonly use card swipe terminals which read information stored on a magnetic stripe carried by the card. The information is received by telephone line at an administration office, where a computer checks the credit of the customer identified by the information from a database, and provides an authorization number or denial of the transaction. Because credit is to be provided by the issuer of the card, such as a bank, the transaction is associated specifically with and is controlled by the issuer of the credit card.

0007As another example, when a debit card of a customer is swiped, a transaction value is keyed in by the retailer, and a PIN number is additionally keyed in by a user. The bank account of the user, the identity of which having been previously stored in association with the PIN number and card number, is accessed, and the transaction value is debited from the bank account of the customer. This amount (less a transaction charge) is credited to the bank account of the merchant identified when the debit card reader dials an administration office which is in association with the bank. In this case as well, the transaction is associated specifically with and is controlled by the issuer of the debit card.

0008It is common that some credit card issuers record loyalty points, for example a point for each dollar purchased on the credit card. These points are accumulated by the credit card issuer to the credit of the credit card user, and can be redeemed for merchandise or services typically advertised in a catalogue. In some cases, loyalty points are awarded by a vendor such as an airline, wherein the loyalty points can be used for airline travel with that airline. The vendor retains its own database of loyalty points accumulated against particular customers which have joined the loyalty point program.

0009In addition, identity cards rather than credit cards are sometimes used in the awarding of airline miles based on purchases from certain vendors. In this case as well, the card issuer retains a single database of airline points against customers.

0010In all such cases, the card issuer or the vendor (e.g. the airline) retains a simple database to keep track of the value of points accumulated or retained after redemption. There is a single authority which has issued the card, and tie-ins of a single card with a limited number (often only one, and in some cases a large number) of merchants. For example, a card issuer may have a tie-in with several merchants to provide a discount on merchandise or services. In such a case, no loyalty points tied to a particular merchant are awarded to the customer for patronizing the merchant, but loyalty points are awarded based on use of the card per se. Further, the systems are not capable of dispensing or redeeming premiums or loyalty points "on-the-spot" for certain actions taken by customers, for example for patronizing certain merchants. Thus in this case as well, a single loyalty point database is associated with the card issuer, but not with the merchants. A merchant has no way of knowing whether a particular customer repeatedly purchases from that merchant.

0011In other words, such systems provide and record loyalty points related to use of a card, or to a single merchant, or to a single program (such as airline points) , but do not provide loyalty points that can be traded between merchants or programs, and do not give incentive to patronize particular merchants as distinct from incentive to use a single card. The airline points programs which are not associated with a particular credit card also require the use of a single card, and loyalty points cannot be traded between merchants.

0012The systems are also not capable of accumulating prize values or loyalty points won on games played on game terminals, nor of dispensing prizes to players, e.g. loyalty points, premiums or plays on the games.

0013The systems are not capable of displaying advertising directed to specific customers who have identified themselves or have been identified at a terminal or to classes of such customers, nor of tracking what advertising has been displayed to particular customers, nor for controlling what advertising should be shown to such identified customers or classes of customers.

0014Neither are the systems capable of allowing the loyalty points won or otherwise acquired to be used as a medium of exchange between member merchants, e.g. exchanging points won playing a video game for premiums which can be redeemed for goods or services by various merchants.

0015SUMMARY OF THE INVENTION The present invention is an integrated on-line system which can accumulate and decrement exchange values associated with any customer from any merchant which has authorized access to the system or by an administrator or by plural authorized administrators. The system provides means for the awarded exchange values for any transaction to be controlled by an administrator or by authorized plural administrators, and can in addition be varied by location of the customer, by customer activity, by time and/or date, and by past history of either the activity itself or of the actions of the customer or of changing demographics of the customer.

0016In addition, the system provides means for the administrator to vary the characteristics of a software program the customer, merchant, etc. is interacting with, so that loyalty points, advertisements, premiums, scores, game difficulty, characteristics of a game and reward brackets, pricing by currency and/or loyalty point exchange, etc. can be controlled and varied. The program can involve scoring of sporting events, scoring of school tests, operate applications such as email, etc. or it can be a video game such as one operating in a system of the type described in U.S. patent 5,083,271 issued January 21, 1992, or on a personal or public computer (public PC) . A user interface to the program can be displayed on a video terminal which can be one of the games described in the aforenoted U.S. patent, or on a personal or public computer, a display type or video telephone, a network computer interacting and communicating via a private network, the internet, cable or the equivalent, a telephone line, etc. The advertisement can be shown in one or more frames (windows) which share the display with a game frame, or can occupy the entire display area. The advertisement can be directed to a particular player, or to a class of customer to which the player belongs, and/or can be scheduled based on time and/or date and/or location at which it is to be presented. The advertisement can be changed based on various criteria, such as the location of the display, how many times the advertisement has been run, how many times the advertisement has been directed to the customer or class of customer at a particular display or display location or at a class of locations or at plural particular or classes of locations or based on advertisements which have been shown to the customer in the past. Loyalty points (i.e. exchange values, which can include coupons, etc.) can be awarded based on an activity of the customer at least partly on the basis of his exposure to certain advertisements which may be displayed on the aforenoted displays .

0017Game programs can be changed and varied as to degree of difficulty and currency or exchange value price to participate, competition brackets can be set up and varied, thresholds for prizes can be established and varied, prize and premium values can be accumulated for various activities such as plays, purchases, loyalty, and/or timing, customers or players can be authorized or disqualified, advertising can be directed to certain customers or classes of customers, premiums can be accumulated and dispensed and prizes awarded across any kind of commercial or non-commercial activity with controllable interchangeability, preferably from an administration terminal.

0018As an example, a customer can receive a coupon at a gasbar (or can read an announcement in a newspaper) containing a question to be answered, and if answered correctly at a terminal used in the system of the present invention, a prize (e.g. a coupon for $1000 off the price of a purchase, or the awarding of loyalty points which can be exchanged for merchandise or service at participating or at all merchants) can be awarded by the system, and the accounts of the customer, merchants and administrator incremented or decremented as required.

0019The present invention thus provides for the first time an efficient way of combining loyalty point and premiums of any (rather than restricted) merchants, allows interchange of loyalty points, and at the same time gathers activity information and/or demographic information about the customers of those merchants as an effective commercial measurement tool, and so that advertising may be targeted and efficiently delivered to those exact customers which can best benefit from the advertising and those exact customers desired by the advertisers.

0020By the use of the term merchants, included are merchants not only of merchandise, but also of services including the services of play of various games and contests.

0021In this specification, the term customer and subscriber will be used synonymously, since a customer which has been registered into the system becomes a subscriber, and it is the registered customer which can accumulate loyalty points. In accordance with an embodiment of the present invention, a system for controlling a medium of exchange comprises:

0022(a) plural terminals at various locations for detecting the presence of a person and of an activity carried out by the person, and for providing signals indicative of the identity of the person and of the activity,

0023(b) a first database for storing predetermined exchange values for the activity,

0024(c) a second database for storing separate medium of exchange accounts for various persons (which can include either or both of customers and merchants) ,

0025(d) apparatus for detecting said signals, for accessing the first database and for crediting an exchange value related to the activity to an account of a person carrying out the activity or on whose behalf the activity was carried out, in the second database, and

0026(e) an administration terminal in communication with the first database for generating and downloading to the first database parameters indicative of the predetermined exchange values for various activities, from time to time.

0027In accordance with another embodiment, a system for controlling a medium of exchange comprises:

0028(a) terminals for determining the presence of a person, and of an activity carried out by the person,

0029(b) display apparatus located adjacent to the terminal, (c) a regional server in communication with the terminals and display apparatus,

0030(d) a first database accessible by the regional server, (e) a support server in communication with the regional server,

0031(f) an administration terminal on which control parameters can be input, (g) apparatus for receiving control parameters relating to medium of exchange values for activities carried out by the person from the administration terminal and for downloading the control parameters to the support server, (h) apparatus for transferring those control parameters which relate to media of exchange functions controlled by the regional server, to the first database, and

0032(i) apparatus for transferring those control parameters which relate to functions carried out at the display apparatus and the terminals, from the first database to control apparatus for the display apparatus, whereby the presence and activity of said person can be determined and messages can be controlled to be presented on the display apparatus directed to the identified person of class of person, and exchange values credited to the person.

0033In accordance with another embodiment, a system for controlling a medium of exchange comprises: (a) plural terminals at various locations for detecting the presence of a person and of an activity carried out by the person, and for providing signals indicative of at least the activity,

0034(b) a first database for storing predetermined demographic information related to the activity,

0035(c) apparatus for detecting the signals, for accessing the first database and for storing data related to the activity in a record related to a class of persons carrying out the activity, in the second database, and (e) an administration terminal in communication with the first database for receiving the stored data, and for generating and downloading to the first database parameters controlling the provision of offers to persons of the same class from time to time.

0036In accordance with another embodiment, a system for controlling a medium of exchange comprises: (a) plural terminals at various locations for detecting the presence of a person and of an activity carried out by the person, and for providing signals indicative of at least the activity,

0037(b) a first database for storing predetermined demographic information related to the activity,

0038(c) apparatus for detecting said signals, for accessing the first database and for storing data related to the activity in a record related to a class of persons carrying out the activity, in the second database, (e) an administration terminal in communication with the first database for receiving the stored data, and for generating and downloading to the first database parameters for controlling the provision of advertising, for display on display apparatus which is part of the terminal or is adjacent the terminal, to the person or to persons of the same class, or for controlling the printing of premiums on a printer which is part of the terminal or is adjacent the terminal, from time to time. BRIEF DESCRIPTION OF THE DRAWINGS A better understanding of the invention will be obtained by a consideration of the detailed description below, in conjunction with the following drawings, in which: Figure 1 is a block diagram of a preferred embodiment of a system on which the present invention can be implemented,

0039Figure 2 is a flow chart of call initialization and loyalty point or coupon data interchange,

0040Figure 3 is a histogram of player scores against number of plays,

0041Figure 4 is an illustration of a database format for specifying advertisements to be played under various circumstances, and

0042Figure 5 is an illustration of an exclusion code signal . DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

0043U.S. Patent 5,083,271 is incorporated herein by reference. This patent describes plural game arcades which are in communication with a central computer, or with one of plural regional computers which communicate with a central computer. The regional computers receive game score data and compute tournament winners, downloading both winner information and advertising to local games at the game arcades.

0044Turning to Figure 1, in place of the regional computers, regional servers 1A, 1B...1N, etc. are used. Each regional server is located at a separate regional data center, although for convenience of illustration they are all shown in this Figure in data center 3.

0045Each regional server has a memory containing a corresponding database 5A, 5B...5N coupled to it. In the aforenoted patent, the corresponding memory stores not only score data, but also values of money on deposit to be credited against the playing of a game, and handicaps of players and/or games. If an activity other than playing a game is to be rewarded, the user activity can J

004611 similarly be handicapped (for example, awarding of variable numbers of points for use of a particular long distance telephone supplier) . In accordance with an embodiment of the invention, the databases 5A, 5B...5N also store specialized data relating to parameters used in a game or activity, such as difficulty levels, points to be awarded for certain game activities, and other functions to be described in more detail below, as well as parameters and content relating to advertising, premiums, loyalty points, etc.

0047The data to be stored in databases 5A..5N is loaded by a decision support server 7, from data stored in a database 9 with which it communicates.

0048Validation and redemption terminals 11 are in communication with the regional servers 1A..1N. Each of the terminals 11 is comprised of a card reader 13 and preferably a bar code reader 14, smart card reader, or the equivalent, coupled to a printer 15. The card reader is preferably also a card writer for writing the magnetic stripe on a card and/or for updating, debiting or crediting one or more values stored on a smart card (a card which carries a processor or the equivalent and a memory) . The term card reader is used in a general sense, since it can include a keypad or keyboard which can be used by the customer and/or merchant. The customer can also or alternatively be identified by a voice identifier, an eye iris reader, a fingerprint reader, a palmprint reader, a keyed-in identity code such as a PIN number, etc. The printer is used to print receipts and coupons, preferably including a bar code or the equivalent. The card reader can be based on the type made by Verifone Corp. for swiping cards and dialing a credit or debit card administration office. 1

004912

0050A terminal 11 should be located at the premises of each associated merchant authorized to use the system, and can be located at one or plural arcades 17 or other single or multi-terminal system. A system, which can be, but is not limited to arcade 17 which is similar to the system described in the aforenoted patent is in communication with a corresponding server, in a manner as will be described later. However, rather than each game 19 communicating directly with a regional server via its own interface, it is preferred that it communicate with a regional server through a master game 21, via shell software which uses a particular communication protocol which can encrypt data. This will be described in more detail later. A database 23 is also coupled to the master game 21.

0051A computer 25, referred to below as a public PC 25, can be in communication with an associated regional server 1A..1N. Preferably a card reader 13, bar code reader 14 and printer 15 are coupled to the computer, as well as a display 27, keyboard 28, game controls (e.g. a joystick, mouse, trackball, pedals, etc.) a CD ROM player 29, and a DVD (digital versatile disk) player 31.

0052An administration office 41 contains a computer terminal 43 preferably operating in a Windows^tm software environment, with a display 45. Rather than a Windows'™ software environment, any type of operating system can be used, such as one which will operate under control of applets downloaded from the internet or any other network, Macintosh, OS/2, etc. The terminal 43 includes a database and a processor for controlling parameters of software used in the system, and can communicate with the decision support server 7 as will be described below. J

005313

0054In operation, games, advertising and parameters relating to loyalty points and/or coupons are downloaded under control of the decision support server 7 to database 9, then are distributed to regional servers 1A..1N, then are downloaded to database 23. Alternatively the games, parameters and/or advertising are stored at the arcade 17 on local mass storage devices such as hard disk drives, digital versatile disks (DVDs) or CD ROMs (or can be stored in a semiconductor or any other form of mass storage memory) , and are enabled from data stored in the decision support server 7 and preferably downloaded to the database 23. The games, parameters and/or advertising can be provided via applet if desired. In the description below, and only for this example, the games and advertising will be described as being stored on DVDs (in database 23) at the arcade. The database will be considered for this example to be a combination of the local mass storage and semiconductor memory, but it should be understood that the data can alternatively be downloaded from database 5A to 5N coupled to the regional server, and stored for use as needed in the database 23.

0055It is preferred that the games themselves should be written within a shell, with software "hooks" between the games and shell. The shell should be responsible for starting and stopping the game, altering its parameters, controlling the display of the game that is to be played, and communicating both with other games and with the regional server 1A..1N. It is preferred that each of the games should communicate with the regional server only under control of the master game 21. The software operated by the master game 21 should in addition be designed to communicate with each of the games of the j

005614 arcade, and with a designated regional server using a communications manager program, in accordance with a predetermined protocol.

0057Customer accounts are retained in the database 9, and are preferably comprised of the following fields:

00581. Account data (customer name and PIN),

00592. Balance of account (in currency), both current balance and pending balance (the latter being the expected balance after an ongoing transaction has been completed) ,

00603. The identity and value of coupons and premiums allocated to the customer,

00614. The balance value of loyalty points associated with the customer, e.g. as incremented or decremented by a device such as by an input device at a merchant location (for example by inputting via a keypad connected to the card reader 13 at a validation and redemption terminal 11) or by an administrator via terminal 43 at the administration location 41, or by operating an automatic terminal such as a coin telephone having a swipe card reader in administrative communication with regional server 1A to IN, a game machine, etc.,

00625. Game ratings, such as skill level of the customer for variously played games, handicap values of the customer for variously played games, profiles (e.g. how much time is allocated to the player to complete various games) ,

00636. Viewing history of advertising (e.g. a record of the most recent time that the customer has viewed a particular advertisement) ,

00647. Images displayed for this customer,

00658. The identities of identification cards issued to the player, J

006615

00679. Merchandise orders, e.g. the identity and loyalty point, premium or currency cost of merchandise that has been ordered, the date ordered, the date the order was sent to the supplier, the date the order was shipped, etc.,

006810. The game play history, e.g. for each game played, the rank achieved, number of players in a game or tournament, etc.,

006911. Data regarding membership of the customer in competitions or teams,

007012. Records of payments of fees made by the customer, and

007113. Records of customer premiums and/or prizes awarded (which can be used e.g. for tax computation) The administrator characterizes each game and activity relating to merchant products and services with certain parameters, and downloads these parameters from terminal 43 to server 7. For example;, the administrator establishes game formulae for each game, loyalty points (or none) for playing each game, for patronizing particular merchants, etc.

0072When a customer is issued an identity (ID) card, a PIN number is issued in a well known manner, and information re its issuance is uploaded from a validation terminal 11 to the associated regional server 1A to IN. A record in the database 9 relating to this customer is established by server 7. The record is seeded by the parameters provided by the administration terminal to the server 7. For example, upon first initiation of the record, a number of loyalty points can be deposited to the customer, and recorded in the database in field 4. The customer then pays currency to play say, 5 video games. The payment value is entered by swiping the J

007316

0074ID card in a local card reader in the arcade, and by then entering the PIN number of the customer and the number of games to be played, or a currency amount into a local keypad. This amount is stored (deposited) in database field 1 (see the above field list) of database 9, after uploading from the arcade 17 via master game 21.

0075The customer then goes to the game and swipes his card in a card reader associated with the game. The request to initiate the game is sent to the game from the card reader, and value of the game play is sent to the decision support server 7. Server 7 addresses database 9, and selects the record of the customer from the card number read and provisionally decrements the amount on deposit, storing the resulting pending balance. If the game is not played (e.g. if there is a power outage), the pending balance is again incremented back to the previous balance after a predetermined amount of time. By using a central decision support server 7 and database 9 to store the customer accounts, the customer can be provided with service at any location which communicates with any regional server. A duplicate account is established and retained in the regional support server database 5A..5N, the records being mutually updated (synchronized) from time to time. At the time of establishment of the record in database e.g. 5A, the server 7 would also store values in the remaining fields of the record. For example, it would store an advertisement value, to be described in more detail below, in field 6, indicating that no ads have been presented to the customer.

0076After the customer has swiped his card at a game, and thus identifies himself, the local database provides a data message to a the local system which enables the 17 selected game. If it is the first time the customer has identified himself to the local system, the regional server e.g. 1A sends a data message which enables the selected game. It also enables a DVD to run an advertisement to the game via its shell, which overlays the game in a window, or is presented prior to or with the initial, intermediate or final screens of the game. For example, the initial screen can be a "welcome to a new player" screen, with an advertisement relating to one or another of the associated merchants. The advertisements to be run are pre-established at the administration terminal 43.

0077The fact of running a particular advertisement and of the customer being located at a particular game (determined from his ID card) is then stored in the 10^th field of the record. When the game has been completed, the score is uploaded to the regional server and the rank of the player is established and is stored in the 10^th field. The number of plays of the player of that game, and of other games, are also stored in the 10^th field. On the basis of this, depending on the administrator, loyalty points, coupons or premiums can be provided to the customer.

0078For example, if the customer has achieved a particular score, a predetermined number of loyalty points can be awarded, and added to those in the balance in the 4^th field of the database record. A printer 15 can dispense a coupon to the customer e.g. for a discount on a food item at a fast food outlet, the serial number and value of which is recorded in the 3^rd field of the record. The printout can also record the score and the game that was played. 18

0079The identity of the advertisement which was run is recorded in the 6^th field of the record.

0080The customer in achieving a particular amount of expertise can be handicapped by the software in the regional server 1A, and the handicap value recorded in the 5^th field of the record, the rank achieved recorded in the 10^th field, and all of this information can be printed on the same ticket as the coupon, or another ticket.

0081Now assume that the player attends a different arcade, and wishes to play a game. He will swipe his ID card in the local card reader, press a button to command the start of or the identity of the game if necessary, and his identity, a command to play a game and the cost to play is uploaded to the associated regional server, say server IB. Server IB searches its database 5B for a record of the identified customer, and doesn't find it. It then sends an inquiry to the server 7, which sends an inquiry to each of the other regional servers. Server 1A responds, and provides an indication to server IB that the customer record is stored in a database associated with server 1A.

0082Server 1A then sends the record of the customer to server IB via server 7. Server IB checks whether the second field has sufficient balance to pay for the game. On the indication that it does, a provisional decrement is done as described earlier, and server IB sends a signal to the master game of the arcade to enable the game.

0083The server IB also checks the ad view history and image last viewed, and enables the DVD at the arcade to run the next advertisement in the predetermined sequence of advertisements to the game to be played, via the game shell. The entire process is repeated as described earlier.

0084In the event the customer has used the local system before, and his identity data, etc. is stored in the local database, the above process can be carried out using the data stored in the local database, rather than using the data stored in the server.

0085The score can result in loyalty points or premiums being awarded to the player, which are stored in the account of the player.

0086Assume now that the customer wishes to redeem loyalty points or premiums. The customer can visit a validation and redemption terminal, which can be at the location of a merchant, a public PC, or at an arcade. The ID card of the customer is read, and an attendant types in a request on a local keyboard such as 28 to obtain the number of loyalty points, or the identities of coupons or premiums held by the customer. This request is uploaded to the regional server, which reads the database e.g. 5A and accesses the record of the customer identified by the card (and PIN number, if desired) . On verification by the regional server, the data stored in the fields of the information requested by the attendant are then downloaded to the local terminal, such as computer 25, and is displayed on display 27.

0087The customer can ask for redemption of the value of the coupon. For example, if the validation and redemption center is at a fast food outlet, and the coupon is for a discount on a hamburger from the fast food outlet, the merchant can sell the hamburger at the required discount, take the coupon from the customer, and key in the coupon on a keypad or read a barcode or magnetic stripe or the equivalent carried by the coupon, J

008820 to identify it and record it as having been redeemed. The local computer or the equivalent then uploads this data to the regional server 1A, which records that the coupon has been rendered. While this transaction is going on, there could be a display adjacent the redemption equipment. The regional server, in learning of the presence of the customer at that location from the ID card swipe, can then look up the advertisement viewing history from the 6^th field of the customer's record in the database, and send a control signal to the computer or the equivalent at the redemption center, to enable a local DVD 31 to run the next advertisement in a predetermined sequence to the display which is adjacent the customer. Loyalty points can be awarded to the identified customer based on viewing a particular advertisement, and stored in the database as described earlier.

0089In a similar manner, loyalty points can be redeemed. The customer can attend a redemption center which can be a merchant, or a special catalog store.

0090After swiping the ID card of the customer and keying in a request to display the number of loyalty points accrued to the customer, the regional server e.g. 1A accesses the record of the customer using his ID and PIN number in database e.g. 5A, and downloads the information to a local display. Following redemption of a particular number of loyalty points for the merchandise or services requested, the 4^th field of the record of the customer is decremented by the value of the loyalty points redeemed. It should be noted that the system is global, in that any merchant can have a redemption terminal. Upon redeeming loyalty points which have been accrued by the customer by playing games, viewing advertisements, or J

009121 using services of other merchants, etc., the redeeming merchant can be owed a certain value based on the redemption. This value or the equivalent in loyalty points, can be stored (credited) in a database 5A related to the merchant. When a customer purchases goods from that merchant, a certain number of loyalty points can be awarded the customer, and the balance debited from the balance of the merchant. Administrator service fees in the form of loyalty points can be accrued to an account of the administrator for each transaction. In this manner, loyalty points become a medium of exchange for the customer, the merchants and the administrator. Loyalty points or a monetary amount can be decremented from an account of each merchant for each play of its advertisement.

0092At the end of a predetermined period, for example quarterly, yearly, etc., the administrator and merchants can settle the accounts, e.g. collecting a prescribed monetary value for negative balances of merchant loyalty point accounts, and paying a prescribed monetary value for positive balances of merchant loyalty point accounts.

0093Loyalty points can also be redeemed by the customer for any merchandise or service at any merchant location or venue at which a service terminal is located, or for game play at an arcade.

0094Two types of data interchange are preferably used in the system: synchronous and asynchronous. In synchronous interchanges, the client initiates a connection to a server, sends a request, and await a reply, in a manner similar to credit card authorizations in retail stores. An example of this type of interchange in the present invention is the validation of a prize receipt. Asynchronous interchanges are used for database J

009522 synchronization. They allow events that have been queued by clients to be sent to servers, and allow servers to add or update information in a client's database.

0096Four modes of communication between clients and servers are preferred to be used:

0097- Queries from clients to servers for specific information,

0098- Events being transmitted from clients to servers, - Record and file system synchronization transmitted from servers to clients, and

0099- Interactive on-line traffic, allowing on-line services in which processing is done in real-time by the server, or through a proxy process on the server. Because of the short duration and unpredictability of query calls, they are preferably implemented with a point-of-sale, packet type transaction type network, with dial-in connections from various client locations using a global toll-free number. The remaining types of calls are more predictable in nature and duration, typically lasting one or more minutes, and preferably use full duplex stream-oriented communications. This can be implemented using a dedicated or non-dedicated dial-up line between client and server, using TCP/IP ports (internet or intranet) . Thus each server can initiate two types of connections to client servers: asynchronous dial-in to the transaction network at relatively low speeds (e.g. 2400 baud or higher) for short duration queries, or via a dial-in PPP connection (e.g. 28.8 kbaud or higher) or ISDN to perform sockets-based communication.

0100The data transmission protocol used is preferred to be bi-directional full-duplex asynchronous 23 communication using X.25-based packet switching, but other communications technologies, e.g. ADSL can be used, as they become widely available. Prior to application to the network, the event data should be packetized, inserted into variable length telecommunication packets, compressed and encrypted using the encryption key of the location. Other fields in the telecommunication packet need not be compressed or encrypted. The received packets should be decrypted, decompressed, and extracted from the telecommunication packets.

0101The transmissions are preferably initiated from the transmitting entity (dial-in) rather than being polled. The calls can be normal (e.g. to pass data re start, game plays, alarms, meters, etc. to and from the client, stored in a queue at that location for subsequent transmission), urgent (e.g. such as customer information when a card is swiped), and receipt validation (e.g. to verify calls used by validation terminals) .

0102Terminals communicating within a single location can use lObaseT twisted pair wiring and 802.3 (Ethernet*™) standard for data link management, or higher speed Ethernet or other technologies, as they become available. The regional servers can accept connections from either the point-of-sale transaction network or from a TCP/IP internet/intranet connection (using Berkeley sockets) . The same application-layer protocols operate over each connection, with the possible exception of synchronization, which can operate only over TCP/IP connections, if desired. The four types of packets referred to above can have a number of subtypes, as follows: Packet Possible Subtypes Type:

0103Control Acknowledgment (ACK) Negative Acknowledgment (NAK)

0104Context Negotiation Ping

0105Ping Response Open Query Link

0106Close Query Link Open IP Link

0107Close IP Link Link Status Request

0108Link Status Response Suspend Processing

0109Suspend Processing Response Resume Processing

0110Resume Processing Response Synchronize

0111Synchronize Response

0112Query Test Test Response

0113Receipt Validation Receipt Validation Response Subscriber Information Subscriber Information Response Account Withdrawal Account Withdrawal Response Account Deposit Account Deposit Response Subscriber Account Data Subscriber Account Data Response

0114Request Winning Redemption Play Winning Redemption Play Response Subscriber ID Request Subscriber ID Response Credit/Debit Request Credit/Debit Response Save State Request Save State Response Restore State Request Restore State Response New Subscriber Card Request New Subscriber Card Response Reserve Merchandise Reserve Merchandise Response Purchase Merchandise Purchase Merchandise Response Release Merchandise Release Merchandise Response Subscriber Ranking Request Subscriber Ranking Response

0115Event Alarm Tournament Play

0116Redemption Play Meter Readings

0117Ad Statistics Service Accesses

0118Down Times New Subscriber

0119New Team Issued Coupons

0120Loyalty Point Awards

0121SynchronInventory Table Download ization File Initial Download File Next Download

0122File Initial Upload File Next Upload

0123When a call is connected over the point of sale network or either of the TCP/IP ports , the client and server exchange context negotiation packets to configure the session communications as shown in Figure 2 . When both parties have acknowledged the context negotiation, data packets can begin .

0124The client sends a context negotiation packet with the settings it wishes to use for the call ( including the encryption and compression parameters) . This packet also tells the server what type of call this is ( e . g . events , 25 queries, etc.). The server examines the context negotiation packet and determines whether the values are acceptable. If so, it sends a context negotiation packet with the same settings to the client. The client acknowledges this packet to the server, and the call is considered to be established.

0125If the server cannot use the context provided by the client, it sends its own context negotiation packet back to the client with its preferred settings (e.g. a "lower" standard for compression or encryption) . If the client agrees with these settings, it sends an acknowledgement to the server, and the call is considered to be established.

0126The contents of the context packet are sent uncompressed, but encrypted using the terminal's 16 byte license key and a TEA encryption algorithm. The terminal cannot operate unless the license key entered at the machine matches the key entered through the server administrative application. If a device receives a context packet for an encryption method it can perform, it can NAK (unacknowlege) the packet. The server should retransmit session key packets, working from best to worst encryption (retrying a number of times in case of communications faults) until the client returns an acknowledgement. If the client never acknowledges the packet, the server should close the connection. Likewise, if the server never acknowledges the packet from the client, the client can close the connection. The client is free to retry with a new socket on the same call .

0127When a connection is established over the asynchronous point of sale link, the client may immediately begin transmitting data packets to the server. Then a PPP connection is established, the client should create a socket connection to one of the TCP ports listed above. Packets can then be sent over this socket connection. Multiple socket connections can be opened to allow parallel processing of synchronization, event and query traffic.

0128Query exchanges preferably occur in lockstep over a single connection. When a terminal issues a query, it waits on the same connection for a matching query response to arrive. The terminal then processes the query response, sends an acknowledgement, then closes the connection or continues with other query exchanges.

0129If a query initiates the download of table and/or file information to the client, the downloads should take place before the server sends the query response. When the query response is received at the client, it can assume that all downloads are complete.

0130Event transfer from clients to servers follows a lockstep acknowledgement cycle in which the client sends event packets and the server sends acknowledgement or nonacknowledgement packets in response. Events should remain in the client's event queue until an acknowledgement has been received from the server. When all events have been sent and acknowledged, the client can close the connection.

0131When a client makes a synchronization call, the client and server begin by exchanging inventory packets. The client sends an inventory of all data currently loaded, and the server sends an inventory of what the client should have (including table records and files) . The client should use the server's inventory to delete all records and files that are not present at the 27 server. The server should use the client's inventory to build a set of table and file download packets to send new information to the client.

0132Once the inventories have been exchanged, the server should begin sending table and file download packets. The client should respond to these with either an acknowledgment or nonacknowledgement packet. When the server has sent all records, it should send a table download packet with 0 records to indicate the end of data. The client is free to close the connection at this point.

0133All packets should be framed with a consistent header and trailer, to allow the protocol processor in the receiving server or terminal to distinguish between different versions of requests. A preferred packet is as follows:

0134Offset: Field

0135Size: DESCRIPTION

01360 byte Packet type - the following values are defined:

01370x80 = Control packets

01380x81 = Query packets

01390x82 = Event packets

01400x83 = Synchronization packets

0141Note that the high bit is used to distinguish these packets from earlier version packets.

01421 byte Subtype - the following values are defined: Control packets:

01430 = Acknowledgement

01441 = Negative Acknowledgement

01452 = Context Negotiation

01463 = Ping

01474 = Ping Response

01485 = Open Query Link

01496 = Close Query Link

01507 = Open IP Link

01518 = Close IP Link 9 = Request Link Status

015210 = Link Status Response

015311 = Suspend Processing

015412 = Suspend Processing Response

015513 = Resume Processing

015614 = Resume Processing Response

015715 = Synchronize

015816 = Synchronize Response Query packets:

01590 = Test

01601 = Test Response

01612 = Receipt Validation

01623 = Receipt Validation Response

01634 = Customer Information

01645 = Customer Information Response

01656 = Account Withdrawal

01667 = Account Withdrawal Response

01678 = Account Deposit

01689 = Account Deposit Response

016910 = Customer Account Data Request

017011 = Customer Account Data Response

017112 = Winning Redemption

017213 = Winning Redemption Response

017314 = Customer ID Request

017415 = Customer ID Response

017516 = Credit Debit Request

017617 = Credit Debit Response

017718 = Save State Request

017819 = Save State Response

017920 = Restore State Request

018021 = Restore State Response

018122 = New Customer Card Request

018223 = New Customer Card Response

018324 = Reserve Merchandise

018425 = Reserve Merchandise Response

018526 = Purchase Merchandise

018627 = Purchase Merchandise Response

018728 = Release Merchandise

018829 = Release Merchandise Response

018930 = Customer Ranking Request 31 = Customer Ranking Response

0190Event packets:

01910 = Alarm

01921 = Tournament Play

01932 = Redemption Play

01943 = Meter Readings

01954 = Ad Statistics

01965 = Service Accesses

01976 = Down Times

01987 = New Customer i

019929

02008 = New Team

02019 = Issued Coupons

020210 = Loyalty Point Awards Synchronization packets:

02030 = Inventory

02041 = Table Download

02052 = File Initial Download

02063 = File Next Download

02074 = File Initial Upload

02085 = File Next Upload

02092 2 bytes Packet size (in bytes, including the type, subtype, size and CRC fields) , LSB first 4 N bytes Data (see individual packet descriptions for format) 4+N 2 bytes CRC of packet

0210Acknowledgement packets indicate the successful receipt of information. The total size of the framed packet will be 6 bytes

0211Field Size: Description:

02121 byte Packet Type = 0x80

02131 byte Packet Subtype = 0x00

02142 bytes Packet size = 6 2 bytes CRC

0215Negative Acknowledgement (NAK)

0216Negative Acknowledgement packets indicate that a transmission was unsuccessful or that the receiver encountered an error processing the data. The total size of the framed packet will be 7 bytes.

0217Field Size: Description:

02181 byte Packet Type = 0x80

02191 byte Packet Subtype = 0x01

02202 bytes Packet Size = 7

02211 byte Failure Code

02220 Generic failure

02231 System error

02242 Allocation failure

02253 Invalid request

02264 Communications error

02272 bytes CRC Context Negotiation

0228Context Negotiation packets have the following data structure

0229Field Size: Description:

02301 byte Packet Type = 0x80

02311 byte Packet Subtype = 0x02

02322 bytes Packet Size = 40+

02334 bytes Location ID (LSB first)

02346 bytes Terminal ID

0235[BEGIN ENCRYPTED AREA]

023616 bytes License Key

02371 byte Connection type

02381 byte Encryption type

02391 byte Transmission Sequencing

02402 bytes Key Length (in bytes, LSB first) N bytes Key Data

0241(Pad encrypted area to even 8 byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0242Location ID will be 0 in packets from the client. It will be filled in with packets from the server with the location ID configured for the terminal ID from the client, or 0 if the terminal is not configured in any location. Terminals that are not configured in any location can still access the server for some limited functions. However, if the licensing information is not correct, the server will never send a Context Negotiation packet to the client. The license key is a value entered through the user interface at the terminal, and entered by the operator when configuring the machine in the administrative application. It is used to encrypt the encrypted area of the Context Negotiation packet. When the packet is received, the receiving node decrypts the encrypted area with its stored license key, then compares that key with the decrypted version from the packet. If the two do not match, the machine is not licensed 31 correctly and the Context Negotiation will not succeed until this is corrected. At the terminal, a message indicating incorrect license information should be displayed or printed. At the server, the event will be logged for reporting and/or alarming.

0243The connection type will be one of the packet type codes (0x80 through 0x83) indicating the type of connection being made. This will indicate to the server which protocol processor to launch for the connection. Note that if more than one type of activity needs to occur on one connection, the client can send a Context Negotiation packet during the call to renegotiate the call type (and other parameters of the connection as well) . When this occurs, all in-progress operations are completed, then renegotiation occurs.

0244The Encryption type field will be one of the following values:

0245Value Description

02460 No encryption 1 XOR of key and plain text

02472 Earlier Protocol Version encryption

02483 TEA (see Appendix A for algorithm)

4 IDEA

5 RSA

0251Transmission sequencing will be one of the values below:

0252Value Description

02530 Lockstep (send packet, wait for Ack, send next packet)

0254The contents of the key data will depend on the encryption type, as shown here: j

025532

0256Encryption

0257Type Key Length and Key Data

02580 data will be included 1 Key length will be 0, and no

02592 Key length and key data can vary

02603 Key length and key data can vary

02614 Key length is 16, key data can vary

02625 Key length is 5, key data can vary Key length and key data can vary

0263For connections between terminals within a single location, or between processes on a single terminal, the terminal ID and location ID are both set to 0. The contents of the packet will not be encrypted and should have the following values:

0264Encryption type = 0

0265Transmission Sequencing = 0

0266Key length = 0 This type of connection is only valid on LAN segments or between processes on a single machine.

0267The license key field will be filled by the terminal's license key. This allows the server process to enforce unique license keys and prevent services from establishing their own connections to the server without their own valid license keys. Ping

0268Ping packets are used to test communications to the server. The total size of the framed packet will be 6 bytes.

0269Field Size Description

02701 byte Packet Type = 0x80

02711 byte Packet Subtype = 0x03

02722 bytes Packet Size = 6 2 bytes CRC

0273Upon receipt of a Ping packet, the server will immediately generate a Ping Response packet and send it to the client. This does not require any database or file system access, and can be used to test the basic connection between client and server processes. Ping Response Ping Response packets are sent in reply to a Ping packet. The total size of the framed packet will be 6 bytes

0274Field Size: Description:

02751 byte Packet Type = 0x80 1 byte Packet Subtype = 0x04

02762 bytes Packet Size = 6 2 bytes CRC

0277Open Query Link A request that a link to the server be created that is capable of supporting query traffic (or increases the reference count of an existing link) . The total size of the framed packet will be 6 bytes. Field Size: Description: 1 byte Packet Type = 0x80

02781 byte Packet Subtype - 0x05

02792 bytes Packet size = 6 2 bytes CRC

0280This operation is intended for use between slave and master terminals within a location or between processes on a single terminal. On receipt of this packet, the recipient should establish a connection to the server suitable for query traffic. This may mean forwarding a similar request to the next higher server in the hierarchy.

0281If there is already a link established, its reference count is incremented. Close Query Link A request that a link to the server established by an Open Query Link request be closed (or the reference J

028234 count of the link be decremented) . The total size of the framed packet will be 6 bytes.

0283Field Size: Description:

02841 byte Packet Type = 0x80 1 byte Packet Subtype = 0x06

02852 bytes Packet Size = 6 2 bytes CRC

0286Open IP Link A request that a link to the server be created that is capable of supporting IP traffic (or increases the reference count of an existing link) . The total size of the framed packet will be 6 bytes. Field Size: Description: 1 byte Packet Type = 0x80

02871 byte Packet Subtype = 0x07

02882 bytes Packet Size = 6 2 bytes CRC

0289This operation is intended for use between slave and master terminals within a location or between processes on a single terminal. On receipt of this packet, the recipient should establish a connection to the server suitable for all types of traffic. This may mean forwarding a similar request to the next higher server in the hierarchy.

0290If there is already a capable link established, its reference count is incremented. Close IP Link A request that a link to the server established by an Open IP Link request be closed (or the reference count of the link be decremented) . The total size of the framed packet will be 6 bytes. 3

029135

0292Field Size: Description:

02931 byte Packet Type = 0x80

02941 byte Packet Subtype = 0x08

02952 bytes Packet Size = 6 2 bytes CRC

0296Request Link Status

0297A request for the current link status. The total size of the framed packet will be 6 bytes. Field Size: Description:

02981 byte Packet Type = 0x80

02991 byte Packet Subtype = 0x09

03002 bytes Packet Size = 6 2 bytes CRC

0301When a server receives this request, it should respond with the status of the link to the main ADMIN server group. This may mean forwarding a similar request to the next higher server in the hierarchy. Link Status

0302Returns the current link status. Sent in response to a Request Link Status packet. The total size of the framed packet will be 6 bytes.

0303Field Size: Description:

03041 byte Packet Type = 0x80

03051 byte Packet Subtype = OxOA

03062 bytes Packet Size = 7 1 byte Link Status Low order nibble is current link status:

03070x00 Link state unknown (indicates an error)

03080x01 Link is idle

03090x02 Connecting asynchronous

03100x03 Connecting asynchronous, IP request pending

03110x04 Connecting IP

03120x05 Connected asynchronous

03130x06 Connected asynchronous, IP request pending

03140x07 Connected IP High order nibble is modem state (if applicable)

03150x00 Modem idle (or no modem in link)

03160x10 Modem is dialing

03170x20 Modem is waiting for answer

03180x30 Modem is connected 0x40 Modem is authenticating High bit indicates processing is suspended 0x80 Processing suspended 1 byte Query status High bit is one if a query is in progress

0319Bits 0-6 indicate the percentage complete

03201 byte Event status

0321High bit is one if an event exchange is in progress Bits 0-6 indicate the percentage complete 1 byte Synchronization status

0322High bit is one if a database synchronization is in progress Bits 0-6 indicate the percentage complete

03232 bytes CRC

0324The fields in the response packet relating to query, event and synchronization status are relevant only when the server process is running on a master terminal within a location. All other servers will return 0 for these three fields. Suspend Processing

0325Requests that the communications process on the master terminal suspend any activity that could impact system performance. This prevents service degradation to ensure fair tournament play. The total size of the framed packet will be 10 bytes.

0326Field Size: Description:

03271 byte Packet Type = 0x80 1 byte Packet Subtype = OxOB

03282 bytes Packet Size = 10

03294 bytes Time-out (seconds)

03302 bytes CRC

0331Suspend Processing Response

0332Sent by the communications process on a master terminal in response to a Suspend Processing request packet, indicating that the processing will be suspended as soon as possible. The client can use Get

0333Link Status to determine when processing has been suspended. The total size of the framed packet will be 6 bytes.

0334Field Size: Description:

03351 byte Packet Type = 0x80 1 byte Packet Subtype = OxOC

03362 bytes Packet Size = 6 2 bytes CRC

0337Resume Processing

0338Informs the communications process on a master terminal that normal processing can be resumed. This should be performed after a time-critical operation has completed, and should balance each Suspend Processing packet. The total size of the framed packet will be 6 bytes ,

0339Field Size: Description:

03401 byte Packet Type = 0x80

03411 byte Packet Subtype = OxOD 2 bytes Packet Size = 6

03422 bytes CRC

0343Resume Processing Response Sent by the communications process on a master terminal in response to a Resume Processing request packet, indicating that normal processing will be resumed. The total size of the framed packet will be bytes . Field Size: Description:

03441 byte Packet Type = 0x80

03451 byte Packet Subtype = OxOE

03462 bytes Packet Size = 6 2 bytes CRC

0347Synchronize

0348Requests that the communications process on a master terminal initiate a synchronization with its 38 server. Different levels of synchronization can be requested in the flags field. Note that the communications process should perform a full synchronization on startup and again every few hours automatically (depending on the dialing interval configured for the location) . The total size of the framed packet will be 7 bytes. Field Size: Description:

03491 byte Packet Type = 0x80 1 byte Packet Subtype = OxOF

03502 bytes Packet Size = 7

03511 byte Flags

0352Defined bits include:

03530x01 Scan file system and update W_CONTENT_CACHE table

03540x02 Synchronize the database with the server 0x04 Synchronize subscriber records in cache OxFF Do full synchronization

03552 bytes CRC

0356Synchronize Response

0357Sent by the communications process on the master terminal in response to a Synchronize packet, indicating that the process will begin the synchronization as soon as possible. The total size of the framed packet will be 6 bytes.

0358Field Size: Description: 1 byte Packet Type = 0x80

03591 byte Packet Subtype = 0x10

03602 bytes Packet Size = 6 2 bytes CRC

0361Receipt Validation

0362Receipt validation packets are traditionally sent by validation terminals, but can be sent by any authorized ADMIN terminal. Receipt IDs are printed on all receipts or coupons generated at ADMIN terminals. j

036339

0364The receipt ID is printed in two formats - a bar-code symbol using the Code 39 symbology, and a 15-digit numerical string, printed in 5 groups of 3 digits.

0365This packet is also used to redeem receipts and loyalty points the subscriber has on account. This is typically done by game terminals, following a Subscriber Account Information query to gather the current account information.

0366Receipt validation packets have the following data structure:

0367Field Size: Description:

03681 byte Packet Type = 0x81

03691 byte Packet Subtype = 0x02 2 bytes Packet Size = 30

0370[BEGIN ENCRYPTED AREA] 6 bytes Validating Terminal ID

03711 byte Receipt ID length (10 or 15) N bytes Receipt ID (Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

03722 bytes CRC

0373The length of the receipt data governs its format. The formats supported, and their lengths, are shown here :

0374Lengt : Format:

037510 10 Code-39 Bar-code symbols, as read from the printed receipt

037614 4-byte value representing the loyalty program ID

03774-byte value representing the number of points being redeemed

03784-byte value representing the subscriber ID

03792-byte value representing the PIN 15 15 decimal digits, as printed on the receipt 16 10 Code-39 Bar-code symbols, as read from the printed coupon

03804-byte value representing the subscriber ID

03812-byte value representing the PIN 21 15 digit receipt ID of coupon being redeemed

03824-byte value representing the subscriber ID

03832-byte value representing the PIN 40

0384The receipt ID should appear in the packet in the same order as entered or scanned from the receipt. For numeric IDs, send the ASCII code for each digit. For bar-code format, send the ASCII codes for the bar-code symbols as defined in the Code 39 bar-code symbology. Receipt Validation Response

0385When the server receives a Receipt Validation query, it will attempt to validate the receipt ID in the packet, and will return this response packet with the results.

0386Receipt validation response packets have the following data structure:

0387Field Size: Description:

03881 byte Packet Type = 0x81 1 byte Packet Subtype = 0x03

03892 bytes Packet Size = 14 or 22 [BEGIN ENCRYPTED AREA]

03901 byte Status indicator

03910 = Coupon valid-payment authorized 1 = Coupon not found on server

03922 = System error

03933 = Coupon already redeemed

03944 = Insufficient loyalty points

03955 = Invalid loyalty program 6 = Subscriber not found

03967 = Invalid PIN

03978 = Subscriber account frozen 15 bytes Authorization code (only present if status=0) (Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

03982 bytes CRC

0399The authorization code will be an ASCII string consisting of digits only. It will always contain 15 digits.

0400Subscriber Information

0401Subscriber information queries are sent by clients when a subscriber logs on to a terminal and that subscriber' s information is not in the local database cache. This query will cause table and file downloads between the query and the response.

0402Subscriber information request packets have the following data structure: Field Size: Description:

04031 byte Packet Type = 0x81

04041 byte Packet Subtype = 0x04

04052 bytes Packet Size = 38 [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID requesting the information

04061 byte Card type used in the request

04071 = NANI card

04082 = Credit card

04093 = Debit card 4 = Name

04105 = Name and SSN 16 bytes Card data

04112 bytes PIN

0412(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0413If the card type is 1 (ADMIN Cards), the card data should be filled with the 10-digit ID read from the NANI card followed by 6 spaces. If the card type is 2 or 3 (Credit or Debit card) , the card data field should be the data read from the PAN field on the card stripe (either track or track 2) .

0414If the card type is 4 (Name) , the card data field should be filled with 14 characters of the player's name followed by 2 spaces.

0415If the card type is 5 (Name and SSN) , the card data field should be filled with 10 characters of the player' s name followed by a 4-byte representation of the players SSN (treated as an integer, stored LSB first), followed by 2 spaces. This is the only case in which non-ASCII data is stored in the card data field. Subscriber Information Response

0416When the server received a request for subscriber information, it will collect the information about the subscriber (if found) into table and file download packets, and transmit them to the client. When all downloads are complete, this response packet will be sent to the client. If there is an error or if the subscriber is not found in the server's database, this response will be transmitted right away. Subscriber information response packets have the following data structure:

0417Field Size: Description:

04181 byte Packet Type = 0x81

04191 byte Packet Subtype = 0x05 2 bytes Packet Size = 14 or 22 [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID requesting the information

04201 byte Status Indicator

04210 = Information found - subscriber valid

04221 = Information not found

04232 = System error

04243 = Invalid PIN

04254 bytes Subscriber ID (only present if status = 0)

0426(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

04272 bytes CRC

0428If status is 0 or 3, this packet will be preceded by a one or more table and/or file download packets containing the subscriber information. When the response packet is received, all subscriber data will have been downloaded to the terminal. Responses with status codes 1 or 2 will be returned right away. Account Withdrawal

0429This query is sent by clients when a subscriber requests a withdrawal of money currently on account. Account withdrawal packets have the following data structure: 43

0430Field Size: Description:

04311 byte Packet Type = 0x81

04321 byte Packet Subtype = 0x06

04332 bytes Packet Size = 22 [BEGIN ENCRYPTED AREA]

04346 bytes Terminal ID requesting the transaction 4 bytes Subscriber ID

04352 bytes PIN number entered by subscriber 4 bytes Amount to be withdrawn (in US cents) (Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0436The server will enforce limits on the maximum and minimum amounts for which a withdrawal can be made. Account Withdrawal Response

0437When an account withdrawal request is made, the server will attempt to perform the withdrawal, then will send this response packet to the client with the results. Account withdrawal response packets have the following data structure:

0438Field Size: Description:

04391 byte Packet Type = 0x81

04401 byte Packet Subtype = 0x07 2 bytes Packet Size = 22 or 38 [BEGIN ENCRYPTED AREA]

04416 bytes Terminal ID performing the withdrawal 4 bytes Subscriber ID

04421 byte Status indicator 0 = Withdrawal authorized

04431 = Insufficient funds

04442 = Subscriber not found on server

04453 = Invalid PIN

04464 = Account frozen 5 = System error

04476 = Invalid amount 15 bytes Authorization ID for withdrawal (only present if status = 0) 4 bytes New account balance, in US cents (only present if status = 0)

0448(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

04492 bytes CRC j

045044

0451Account Deposit

0452This query is sent by the clients when a subscriber requests a deposit of money to his or her own ADMIN account. Account deposit packets have the following data structure:

0453Field Size: Description:

04541 byte Packet Type = 0x81

04551 byte Packet Subtype = 0x08 2 bytes Packet Size = 22

0456[BEGIN ENCRYPTED AREA]

04576 bytes Terminal ID requesting the transaction

04584 bytes Subscriber ID

04592 bytes PIN number entered by subscriber 4 bytes Amount to be deposited (in US cents) [END ENCRYPTED AREA] 2 bytes CRC

0460Account Deposit Response

0461When an account deposit request is made, the server will attempt to perform the deposit, then will send this response packet to the client with the results.

0462Account deposit response packets have the following data structure: Field Size: Description:

04631 byte Packet Type = 0x81

04641 byte Packet Subtype = 0x09

04652 bytes Packet Size = 22 or 38 [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID performing the withdrawal 4 bytes Subscriber ID 1 byte Status indicator

04660 = Deposit accepted

04671 = Account limit exceeded 2 = Subscriber not found on server

04683 = Invalid PIN

04694 = Account frozen

04705 = System error

04716 = Invalid amount 15 bytes Authorization ID for deposit (only present if status = 0) 4 bytes New account balance, in US cents (only present if status = 0) 45

0472(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0473Subscriber Account Data Request This query is sent by clients when a subscriber requests a full report on his or her current account status.

0474Subscriber account data request packets have the following data structure: Field Size: Description:

04751 byte Packet Type = 0x81

04761 byte Packet Subtype = OxOA

04772 bytes Packet Size = 22 [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID

04784 bytes Subscriber ID

04792 bytes PIN

0480(Pad encrypted area to even 8-byte boundary with zeros)

0481[END ENCRYPTED AREA] 2 bytes CRC

0482Subscriber Account Data Response

0483When the server received an account data request, it collects the information about the subscriber's account and sends this response packet. Subscriber account data response packets have the following data structure:

0484Field Size: Description:

04851 byte Packet Type = 0x81 1 byte Packet Subtype = OxOB 2 bytes Packet Size = 22 or 38+ [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID 4 bytes Subscriber ID

04861 byte Status Indicator 0 = Success

04871 = Account Frozen

04882 = Subscriber not found

04893 = Invalid PIN

04904 = System error 4 bytes Account balance (in US cents) (on success)

04914 bytes Amount withdrawn pending confirmation (in US cents) (on success)

04922 bytes Number of outstanding orders (on success)

04936 bytes Order ID (on success) 40 bytes Item name (on success) i

049446

04954 bytes Date and time order received (on success) 4 bytes Date and time order sent to supplier (on success) 4 bytes Expected ship date and time (on success) 4 bytes Date and time order shipped (on success) 4 bytes Date and time order canceled (on success) 2 bytes Number of coupons (on success) 4 bytes Coupon ID (on success) 40 bytes Description (on success) 6 bytes Receipt ID (on success)

04964 bytes Face value (on success) 4 bytes Expiration date (on success) 2 bytes Number of loyalty programs (on success) 4 bytes Loyalty program ID (on success) 40 bytes Loyalty program name (on success)

049720 bytes Loyalty point label (on success) 4 bytes Number of points (on success) (Pad encrypted are to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0498Winning Redemption Play

0499When a redemption game has been played that awards a prize, and the prize has a limited number of units available (a non-zero value for the NUM_REMAINING field in the database) , or that wins a prize that includes a pool amount, the terminal should immediately issue this query to update its local prize information.

0500This packet permits prize pools to be maintained across several locations, without the chance that more prizes that are available will be given out. It also allows the server to update the local pool value so players can see pool contributions from multiple locations.

0501Winning redemption play packets have the following data structure:

0502Field Size: Description:

05031 byte Packet Type = 0x81

05041 byte Packet Subtype = OxOC

05052 bytes Packet Size = 38+ [BEGIN ENCRYPTED AREA]

05064 bytes Subscriber ID playing the redemption game (LSB first) 6 bytes Terminal ID on which the redemption game was played i

050747

05084 bytes Service ID on which redemption game was played

0509(LSB first) 1 byte Player Station (8 bit flags, position 0 = station 1, etc.) 1 byte Active Stations (8 bit flags, position 0 = station 1, etc.) 4 bytes Start Date and Time (UTC format, LSB first) 4 bytes End Date and Time (UTC format, LSB first) 1 byte Flags 0x01 Equipment failed during game

05100x02 Score is invalid 1 byte Number of statistics (n) [BEGIN REPEATING LIST]

05114 bytes Statistic ID (LSB first) 4 bytes Statistic Value (LSB first)

0512[END REPEATING LIST]

05131 byte Number of redemption games entered with the play

0514(m) [BEGIN REPEATING LIST] 4 bytes Redemption ID (LSB first)

05152 bytes Par level beaten (LSB first) 4 bytes Par score beaten (LSB first) 4 bytes Derived score achieved by subscriber (LSB first) 4 bytes Prize ID awarded (LSB first)

0516[END REPEATING LIST]

0517(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

05182 bytes CRC The subscriber ID may be 0 if the redemption game is unidentified. Winning Redemption Play Response

0519When a winning redemption play query is received at the server, it will adjust the number of the awarded prizes remaining (if that number is limited) , and/or it will calculate the pool amount to award to the player based on the current value of the collective prize pool. (If the par level has an associated pool amount) . It will send this response packet back to the terminal, indicating the amount of the pool the player should be awarded and updating the pool value and number of prizes remaining as appropriate.

0520Winning redemption play response packets have the following data structure: 48

0521Field Size: Description:

05221 byte Packet Type = 0x81

05231 byte Packet Subtype = OxOD

05242 bytes Packet Size = 14+ [BEGIN ENCRYPTED AREA]

05254 bytes Current pool value (LSB first)

05261 byte Number of par levels being updated (n)

0527[BEGIN REPEATING LIST]

05284 bytes Redemption ID being updated (LSB first)

05292 bytes Par level being updated (LSB first) 4 bytes New pool value (after award) (LSB first) 4 bytes Pool amount to award (LSB first) 4 bytes Number of prizes remaining (LSB first) [END REPEATING LIST]

0530(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0531Subscriber ID Request

0532A subscriber ID request is used when a terminal needs to register a new player who does not have a NANI card. It generates a unique, unassigned subscriber ID that the player's card data can be associated with.

0533Subscriber ID request packets have no data. The packet header is sufficient to convey the request.

0534Field Size: Description:

05351 byte Packet Type = 0x81 1 byte Packet Subtype = OxOE

05362 bytes Packet Size = 6 2 bytes CRC

0537Subscriber ID Response

0538Upon completion, this request will have registered this ID as "allocated but unassigned". When the player registers, the terminal should send in a New Subscriber Event to assign the ID to the player.

0539Subscriber ID response packets have the following data structure: Field Size: Description:

05401 byte Packet Type = 0x81

05411 byte Packet Subtype = OxOF 49

05422 bytes Packet Size = 14 [BEGIN ENCRYPTED AREA]

05431 byte Status Code

05440 = Success 1 = Failure

05454 bytes Subscriber ID (only present on success) (Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

05462 bytes CRC Credit/Debit Request

0547This request is issued by a terminal when a player presents a credit or debit card and requests that money be transferred on to the terminal for play, or into the player's account. Credit/debit request packets have the following data structure:

0548Field Size: Description:

05491 byte Packet Type = 0x81

05501 byte Packet Subtype = 0x10 2 bytes Packet Size = 46

0551[BEGIN ENCRYPTED AREA]

05526 bytes Terminal ID requesting the transaction

05534 bytes Subscriber ID

05542 bytes PIN (LSB first) 1 byte Card format (FC from track 1 stripe)

055516 bytes Card data (PAN code from track 1 stripe) 4 bytes Expiration date (4 bytes of addition data from track 1 stripe) 2 bytes Debit PIN (LSB first, zero for credit cards)

05564 bytes Amount to be withdrawn (in US cents, LSB first)

05571 byte Disposition

05580 = Place in subscriber account 1 = Credit local terminal

0559(pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

05602 bytes CRC

0561The card format, card data and expiration date fields should all appear exactly as read from the magnetic stripe on the card. The PIN should be entered by the player for debit cards only. 50

0562Save State Request

0563This request is used when a player wants to save the state of a game or other service (including the user interface shell) for later restoration (on this or another terminal) .

0564Save State request packets have the following data structure:

0565Field Size: Description:

05661 byte Packet Type = 0x81 1 byte Packet Subtype = 0x12

05672 bytes Packet Size = 46 [BEGIN ENCRYPTED AREA]

05686 bytes Terminal ID on which the state is being saved 4 bytes Subscriber ID 2 bytes PIN 4 bytes Service ID

05691 byte Slot Number

057020 bytes Save State Name (Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

05712 bytes CRC

0572This packet is sent to the server to obtain a File ID. That file ID can then be used to upload the save state file to the server. Restore State Request

0573This request is issued when a player wants to restore a state that was saved previously on this or another terminal. The server will return the File ID of the save state file, and if the download flag indicates a download is required, it will download the save state file between the request and the response.

0574Restore State request packets have the following data structure: Field Size: Description:

05751 byte Packet Type = 0x81

05761 byte Packet Subtype = 0x14

05772 bytes Packet Size = 30 [BEGIN ENCRYPTED AREA] = 17 y

057851

05796 bytes Terminal ID on which the state is being restored

05804 bytes Subscriber ID

05812 bytes PIN 4 bytes Service ID

05821 byte Slot number

05831 byte Download flag

05840 = Do not download the save state file 1 = Download the file if it exists

0585(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

05862 bytes CRC

0587Even if the file exists on the local machine, this request should be made before the player is allowed to load it, to assure the player is authenticated as the owner of the data, and also to verify the File ID of the save state file as stored in the SUBSCRIBER_SAVE_STATE table. Restore State Response

0588When the server received a restore state request, it will search for the saved state data, validate the integrity of the file, and return the file ID to the client. If the client requested a download of the file, the file will be transmitted before the response is returned.

0589Restore State response packets have the following data structure:

0590Field Size: Description: 1 byte Packet Type = 0x81

05911 byte Packet Subtype = 0x15

05922 bytes Packet Size = 14 [BEGIN ENCRYPTED AREA]

05931 byte Status Indicator 0 = Permission to use save state granted

05941 = Requested save state not found on server

05952 = Subscriber not found on server

05963 = Invalid PIN 4 = Service not found on server

05975 = Account frozen

05986 = System error 4 bytes File ID (only present if status = 0) (Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC New Subscriber Card Request

0599This request is used to associate a new card number with an existing subscriber. This allows players to use multiple cards (including their name or name/SSN combination) to identify themselves to the network. This request will succeed only if the new card ID is unique throughout the entire ADMIN network.

0600New Subscriber Card request packets have the following data structure:

0601Field Size: Description: 1 byte Packet Type = 0x81

06021 byte Packet Subtype = 0x16

06032 bytes Packet Size = 38 [BEGIN ENCRYPTED AREA]

06046 bytes Terminal ID 4 bytes Subscriber ID 2 bytes PIN

06051 byte Card Type

06061 = ADMIN card

06072 = Credit card 3 = Debit card

06084 = Name

06095 = Name and SSN 16 bytes Card Data

0610(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

06112 bytes CRC

0612New Subscriber Card Response

0613When a new subscriber card request is received by the server, it will validate the uniqueness of the card data and create a new card record for the subscriber, returning the result in this packet.

0614New Subscriber Card response packets have the following data structure:

0615Field Size: Description: 1 byte Packet Type = 0x81

06161 byte Packet Subtype = 0x17 2 bytes Packet Size = 22 [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID 4 bytes Subscriber ID 1 byte Status indicator

06170 = Card added successfully

06181 = Card is registered to another subscriber

06192 = Subscriber not found on server 3 = Invalid PIN

06204 = Card already registered to this subscriber

06215 = Account frozen

06226 = System error (Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0623Reserve Merchandise

0624Reserve merchandise request packets are used to reserve an item of merchandise. The requester can specify attribute values for the item, which the server will try to match.

0625Reserve merchandise request packets have the following data structure: Field Size: Description:

06261 byte Packet Type = 0x81

06271 byte Packet Subtype = 0x18

06282 bytes Packet Size = 38+ [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID

06294 bytes Subscriber ID

06302 bytes PIN

06314 bytes Item ID to reserve

06324 bytes Quantity to reserve 4 bytes Price offered

06331 byte Number of attributes

06341 byte Attribute ID

06352 bytes Attribute data size Variable Attribute data (Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

06362 bytes CRC J

063754

0638Reserve Merchandise Response

0639Reserve Merchandise response packets indicate to the requester whether the reservation was successful, and if so, what the actual attribute values of the reserved item is. If the requested quantity could not be met, the largest quantity that could be reserved is returned.

0640Reserve Merchandise response packets have the following data structure: Field Size: Description:

06411 byte Packet Type = 0x81

06421 byte Packet Subtype = 0x19

06432 bytes Packet Size = 38+ [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID

06444 bytes Subscriber ID

06454 bytes Item ID being reserved

06461 byte Status code

06470 Reservation successful 1 No items remain in inventory

06482 Invalid request

06493 System error

06504 bytes Quantity reserved (on success) 4 bytes Price of reserved items (on success) 6 bytes Reservation ID (on success)

06511 byte Number of attributes

06521 byte Attribute ID

06532 bytes Attribute data size Variable Attribute data (Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

06542 bytes CRC

0655Purchase Merchandise

0656Purchase merchandise request packets are used to purchase merchandise that was previously reserved with a Reserve merchandise query. The requester can specify attribute values for the item, which the server will try to match.

0657Purchase merchandise request packets have the following data structure: J

065855

0659Field Size: Description:

06601 byte Packet Type = 0x81

06611 byte Packet Subtype = OxlA

06622 bytes Packet Size = 30+ [BEGIN ENCRYPTED AREA]

06636 bytes Terminal ID 4 bytes Subscriber ID 2 bytes PIN

06646 bytes Reservation ID (on success) 4 bytes Purchase price

0665(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0666Purchase Merchandise Response Purchase Merchandise response packets verify to the requester that the purchase has been processed by the server and that the money should be deducted from the player's funds (either account fees or cash).

0667Purchase merchandise response packets have the following data structure:

0668Field Size: Description:

06691 byte Packet Type = 0x81

06701 byte Packet Subtype = OxlB

06712 bytes Packet Size = 22 or 30 [BEGIN ENCRYPTED AREA]

06726 bytes Terminal ID 4 bytes Subscriber ID

06731 byte Status code

06740 Purchase successful 1 No items remain in inventory

06752 Invalid request

06763 System error 6 bytes Order ID (on success)

0677(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

06782 bytes CRC

0679Release Merchandise

0680Release merchandise request packets are used to release merchandise that was previously reserved with a Reserve merchandise query. The requester can specify attribute values for the item, which the server will try to match. j

068156

0682Purchase merchandise request packets have the following data structure:

0683Field Size: Description:

06841 byte Packet Type = 0x81 1 byte Packet Subtype = OxlC

06852 bytes Packet Size = 30 [BEGIN ENCRYPTED AREA]

06866 bytes Terminal ID 4 bytes Subscriber ID 2 bytes PIN

06876 bytes Reservation ID (on success)

0688(Pad encrypted area to even 8-byte boundary with zeros)

0689[END ENCRYPTED AREA]

06902 bytes CRC Release Merchandise Response

0691Release merchandise response packets verify to the requester that reserved merchandise has been released.

0692Purchase merchandise response packets have the following data structure: Field Size: Description:

06931 byte Packet Type = 0x81

06941 byte Packet Subtype = OxlD

06952 bytes Packet Size = 30 [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID

06964 bytes Subscriber ID 6 bytes Reservation ID

06971 byte Status code

06980 Release successful 1 Invalid request

06992 System error (Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

07002 bytes CRC Subscriber Ranking Request

0701A request for a subscriber' s current ranking in one or more tournament brackets. This can be used to request ranking in brackets that have ended and are beyond their posting period. Subscriber ranking request packets have the following data structure: J

070257

0703Field Size: Description:

07041 byte Packet Type = 0x81

07051 byte Packet Subtype = OxlD

07062 bytes Packet Size = 30+ [BEGIN ENCRYPTED AREA]

07076 bytes Terminal ID 4 bytes Subscriber ID 2 bytes PIN

07081 byte Number of tournament brackets 4 bytes Tournament ID

07091 byte Bracket ID

0710(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

07112 bytes CRC Subscriber Ranking Response

0712The response to the subscriber ranking request packet. This packet contains the subscriber's current position and ranking score in each of the requested tournament brackets that the subscriber has participated in. If the subscriber has not yet played in one of the requested brackets, or the bracket is not found on the server, it will not be included in the list.

0713Subscriber ranking response packets have the following data structure:

0714Field Size: Description:

07151 byte Packet Type = 0x81

07161 byte Packet Subtype = OxlE

07172 bytes Packet Size = 22 [BEGIN ENCRYPTED AREA]

07181 byte Status

07190 = Query succeeded

07201 = Account frozen

07212 = Subscriber not found 3 = Invalid PIN

07224 = System error 4 bytes Subscriber ID 1 byte Number of tournament brackets 4 bytes Tournament ID 1 byte Bracket ID

07232 bytes Rank 4 bytes Score

07244 bytes Score Date and Time (Pad encrypted area to even 8-byte boundary with zeros) 58

0725[END ENCRYPTED AREA] 2 bytes CRC

0726Event Packets

0727Event packets are transmitted on sockets connected to the Event services IP port, or over an asynchronous POS network connection. In either case, they use a transmit-ack lockstep exchange. The client transmits an event packet, the server responds with an Ack. If the server does not respond within 1 second, the client resends the event packet up to 5 times, then fails and moves on to its next event. If the server sends a Nak, the packet should be resent right away. These timeouts may need to be tuned for Internet-based transmission. The entire data portion of the event packet is encrypted using the encryption parameters negotiated for the connection. Alarm

0728Alarm event packets have the following data structure: Field Size: Description:

07291 byte Packet Type = 0x82

07301 byte Packet Subtype = 0x00

07312 bytes Packet Size [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID of the machine reporting the alarm 2 bytes Alarm code being reported (LSB first) .

0732Currently defined values are shown below. 4 bytes Time the alarm was reported (UTC format, LSB first)

07331 byte Flag indicating whether the alarm was handled by the terminal

0734(1 if the terminal handled the alarm with a local handler) 2 bytes Alarm data size (LSB first)

0735Variable Alarm data. The content of this field depends on the alarm type. The formats for each defined alarm code are shown below. (Pad data portion of packet to even 8-byte boundary with zeros)

0736[END ENCRYPTED AREA] 2 bytes CRC

0737Alarm

0738Code: Meaning: Data:

07391 Hard reset (power up) None

07402 Soft reset None

07413 Hardware failure ASCII diagnostic message (optional)

07424 Firmware failure ASCII diagnostic message (optional)

07435 Bill acceptor full None

07446 Coin jam None

07457 Bill jam None

07468 Network disabled None

074712 Game time-out None

074813 Hard drive full None

074918 Printer error None

075019 Printer paper low None

075122 Cable disconnected ASCII diagnostic message (optional)

075223 Security alarm Binary position of switch positions (use

075332 bits)

075424 Enabled by technician Technician ID enabling terminal

075525 Disabled by technician Technician ID disabling terminal

075626 Immediate call requested None

075727 Queue entry aged None

075829 Serial number changed None

0759Alarm events are queued to the server as soon as they are detected. Alarms of the following types are considered critical and should be transmitted right away:

0760Hardware failure Firmware failure Bill acceptor full Coin jam Bill jam Printer error

0761Cable disconnected Security alarm Immediate call request

0762Tournament Play

0763Tournament play event packets have the following data structure:

0764Field Size: Description:

07651 byte Packet Type = 0x82

07661 byte Packet Subtype = 0x01

07672 bytes Packet Size 60

0768[BEGIN ENCRYPTED AREA]

07694 bytes Subscriber ID playing the tournament game

0770(LSB first) 6 bytes Terminal ID on which the tournament game was played

07714 bytes Service ID on which tournament game was played (LSB first) 1 byte Player Station (8 bit flags, position 0 = station 1, etc.) 1 byte Active Station (8 bit flags, position 0 = station 1, etc.) 4 bytes Start Date and Time (UTC format, LSB first) 4 bytes End Date and Time (UTC format, LSB first) 1 byte Flags 0x01 Equipment failed during game 0x02 Score is invalid 0x04 Player should be disqualified 1 byte Number of statistics (n)

07724 bytes Statistic ID (LSB first) 4 bytes Statistic Value (LSB first)

07731 byte Number of tournament games entered with the play (m)

07744 bytes Tournament ID entered (LSB first) 1 byte Bracket ID entered

07754 bytes Derived score achieved by subscriber (LSB first)

0776(Pad data portion of packet to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

07772 bytes CRC Redemption Play

0778Redemption play event packets have the following data structure:

0779Field Size: Description:

07801 byte Packet Type = 0x82 1 byte Packet Subtype = 0x02

07812 bytes Packet Size [BEGIN ENCRYPTED AREA]

07824 bytes Subscriber ID playing redemption game (LSB first) 6 bytes Terminal ID on which redemption game was played 4 bytes Service ID on which redemption game was played (LSB first) §

078361

07841 byte Player Station (8 bit flags, position 0 = station 1, etc.) 1 byte Active Stations (8 bit flags, position 0 = station 1, etc.) 4 bytes Start Date and Time (UTC format, LSB first) 4 bytes End Date and Time (UTC format, LSB first) 1 byte Flags

07850x01 Equipment failed during game 0x02 Score is invalid

07861 byte Number of statistics (n)

07874 bytes Statistic ID (LSB first) 4 bytes Statistic Value (LSB first) 1 byte Number of redemption games entered with the play (m) 4 bytes Redemption ID (LSB first) 2 bytes Par level beaten (LSB first) 4 bytes Par score beaten (LSB first) 4 bytes Derived score achieved by subscriber

0788(LSB first) 4 bytes Pool amount awarded (LSB first)

0789(Pad data portion of packet to even 8-byte boundary with zeros)

0790[END ENCRYPTED AREA]

07912 bytes CRC

0792Meter Readings

0793Meter readings event packets have the following data structure:

0794Field Size: Description:

07951 byte Packet Type = 0x82

07961 byte Packet Subtype = 0x03

07972 bytes Packet Size [BEGIN ENCRYPTED AREA]

07986 bytes Terminal ID on which the meters were collected 4 bytes The date and time meters were collected (in UTC format, LSB first) 2 bytes Number of terminal meters included (LSB first) (n) 4 bytes Terminal Meter ID (LSB first) 4 bytes Terminal Meter Value (LSB first) 2 bytes Number of service meters (LSB first) (m) 4 bytes Service ID of the meter (LSB first) 4 bytes Meter ID of the meter (LSB first) 4 bytes Meter Value of the meter (LSB first) (Pad data portion of packet to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0799Terminal manufacturers should support as many of the following pre-defined terminal meter IDs as possible, as well as any additional meters available:

0800Meter ID: Meaning: 1 Left slot coins in

08012 Right slot coins in

08023 3^rd slot coins in

08034 4^th slot coins in

08045 Paid credits 6 Total collection (in cents)

08057 Service credits

08068 Total plays

08079 Total uptime (minutes) 10 Number of hard resets 11 Number of soft resets

0808Terminal meters should never reset to zero. They should accumulate in 32-bit fields over the lifetime of the terminal. Relative values will be computed between two consecutive readings at the database. Ad Statistics

0809Ad statistics event packets have the following data structure:

0810Field Size: Description:

08111 byte Packet Type = 0x82 1 byte Packet Subtype = 0x04

08122 bytes Packet Size [BEGIN ENCRYPTED AREA]

08136 bytes Terminal ID on which the statistics were collected 4 bytes The date and time statistics were collected

0814(in UTC format, LSB first) 2 bytes Number of unidentified ads (n) 4 bytes Target ID (LSB first) 4 bytes Number of plays

08152 bytes Number of identified ad exposures (LSB first) (m) 4 bytes Target ID (LSB first) 4 bytes Subscriber ID (LSB first) J

081663

08174 bytes Date and time the ad was played (UTC format, LSB first)

0818(Pad data portion of packet to even 8-byte boundary with zeros)

0819[END ENCRYPTED AREA] 2 bytes CRC

0820Ad statistics are accumulated on each terminal and queued at midnight each night (or whenever the terminal detects the current day has changed, in case it is powered off at midnight) . The packet reports all ad plays for the day. As soon as this packet is queued, the ad play records can be deleted from the terminal, and a new day's record keeping begun. The queued entry must not be deleted until successfully received at the server and acknowledged. Service Accesses

0821Service accesses event packets have the following data structure: Field Size: Description:

08221 byte Packet Type = 0x82

08231 byte Packet Subtype = 0x05

08242 bytes Packet Size [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID on which the statistics were collected 4 bytes The date and time statistics were collected

0825(in UTC format, LSB first) 2 bytes Number of service accesses being reported (LSB first) (n)

08264 bytes Service ID being accessed (LSB first) 1 byte Profile used

08274 bytes Start date and time of access (UTC format, LSB first) 4 bytes End date and time of access (UTC format,

0828LSB first) 4 bytes Subscriber ID (LSB first) 4 bytes Cash funds used (LSB first) 4 bytes Account funds used (LSB first)

0829(Pad data portion of packet to even 8-byte boundary with zeros ) [END ENCRYPTED AREA] J

083064

08312 bytes CRC

0832This packet tracks all accesses to any service on the terminal. Each time a player plays a game or engages in a session in any other service, the data should be stored. This packet should be generated each evening at midnight for the day's service accesses (or whenever the terminal detects the current day has changed) .

0833Down Time Down time event packets have the following data structure:

0834Field Size: Description:

08351 byte Packet Type = 0x82

08361 byte Packet Subtype = 0x06 2 bytes Packet Size

0837[BEGIN ENCRYPTED AREA]

08386 bytes Terminal ID on which the down times are being reported 4 bytes The date and time down times were reported (in UTC format, LSB first)

08392 bytes Number of down times being reported (LSB first) (n) 4 bytes Technician ID responsible for the down time (LSB first) 4 bytes Start date and time of down time (UTC format, LSB first) 4 bytes End date and time of down time (UTC format, LSB first)

0840• • • (Pad data portion of packet to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0841This packet tracks all down times experienced by a terminal. Games should periodically update some nonvolatile timestamp while they are running, and then test this value on powerup to see how long the power outage was, and report this as down time. When a technician administratively takes the game down through a service menu, this is also logged in this packet. J

084265

0843This packet should be generated each evening at midnight for the day's down times (or whenever the terminal detects the current day has changed) . New Subscriber New subscriber event packets have the following data structure:

0844Field Size: Description:

08451 byte Packet Type = 0x82

08461 byte Packet Subtype = 0x07 2 bytes Packet Size

0847[BEGIN ENCRYPTED AREA]

08486 bytes Terminal ID on which the subscriber registered 4 bytes Subscriber ID being registered (LSB first) 26 bytes Alias entered by the subscriber

084926 bytes Street address entered by the subscriber 10 bytes Postal code entered by the subscriber 10 bytes Phone number entered by the subscriber 20 bytes First name entered by subscriber 20 bytes Last name entered by subscriber

08502 bytes Middle initial entered by subscriber 1 byte Birth day entered by subscriber

08511 byte Birth month entered by subscriber

08522 bytes Birth year entered by subscriber (LSB first)

08531 byte Gender entered by subscriber (0 = male,

08541 = female) 9 bytes SSN entered by subscriber

08552 bytes PIN entered by the subscriber 1 byte Number of cards to register

08561 byte Card Type

08571 = ADMIN card

08582 = Credit card

08593 = Debit card 4 = Name

08605 = Name and SSN 16 bytes Card Data

0861(Pad data portion of packet to even 8-byte boundary with zeros)

0862[END ENCRYPTED AREA] 2 bytes CRC

0863New subscriber events are queued when players register a new card. They are queued at the time the data is entered, but do not need to be sent right away. However, if the player subsequently plays any games that generate queue entries, the terminal must ensure that this event is transmitted to the server before any game plays for that player. This is to ensure that the server has established an account for the player before attaching a game play to it.

0864Any of the registered cards that are included in the packet that already exist on the server or fail for some other reason will be skipped, but the subscriber will be created regardless. A card of type "NANI Card" with a card ID equal to the value of the subscriber ID will be created automatically. New Team

0865New team event packets have the following data structure:

0866Field Size: Description:

08671 byte Packet Type = 0x82

08681 byte Packet Subtype = 0x08

08692 bytes Packet Size [BEGIN ENCRYPTED AREA]

08706 bytes Terminal ID on which the subscriber registered 4 bytes Subscriber ID of team being registered (LSB first) 26 bytes Alias entered by the team 2 bytes PIN entered for team 1 byte Number of members 4 bytes Subscriber ID 1 byte Flags

0871(Pad data portion of packet to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0872New team events are queued when teams register. They are queued at the time the data is entered, but do not need to be sent right away. However, if the team subsequently plays any games that generate queue J

087367 entries, the terminal must ensure that this event is transmitted to the server before any game plays for that team. This is to ensure that the server has established an account for the team before attaching a game play to it. Issued Coupons

0874Issued coupons event packets have the following data structure:

0875Field Size: Description: 1 byte Packet Type = 0x82

08761 byte Packet Subtype = 0x09

08772 bytes Packet Size [BEGIN ENCRYPTED AREA]

08786 bytes Terminal ID on which the down times are being reported

08792 bytes Number of coupons being reported (LSB first) (n) 4 bytes Coupon ID issued (LSB first) 4 bytes Subscriber ID coupon was issued to (LSB first)

08804 bytes Date and time coupon was issued (UTC format, LSB first) 6 bytes Receipt ID 1 byte Flags

0881(Pad data portion of packet to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC This packet tracks all coupons issued by a terminal. This packet should be generated each night at midnight for the day's coupons (or whenever the terminal detects the current day has changed) . Loyalty Point Awards Loyalty point award event packets have the following data structure:

0882Field Size: Description:

08831 byte Packet Type = 0x82 1 byte Packet Subtype = OxOA 2 bytes Packet Size [BEGIN ENCRYPTED AREA] 6 bytes Terminal ID on which the awards are being reported 2 bytes Number of awards being reported (LSB first) (n) 4 bytes Subscriber ID receiving the award (LSB first) 4 bytes Loyalty Program ID (LSB first) 2 bytes Number of points awarded (LSB first) 4 bytes Date and time the award was made (UTC format, LSB first)

0884(Pad data portion of packet to even 8-byte boundary with zeros) [END ENCRYPTED AREA] 2 bytes CRC

0885This packet tracks all loyalty points awarded by a terminal. This packet should be generated each evening at midnight for the day's awards (or whenever the terminal detects the current day has changed) . Synchronization Packets

0886Inventory

0887Inventory packets have the following data structure:

0888Field Size: Description:

08891 byte Packet Type = 0x83 1 byte Packet Subtype = 0x00

08902 bytes Packet Size [BEGIN ENCRYPTED AREA]

08916 bytes Terminal ID issuing the request (or 0 for server inventories) 2 bytes System software version (LSB first) 2 bytes Number of records (LSB first) (n) 1 byte Table ID the record belongs to 4 bytes Record ID 2 bytes Number of files (LSB first) (m) 4 bytes File ID (LSB first)

08922 bytes Number of content objects (LSB first) (m) 4 bytes Content ID (LSB first)

0893(Pad encrypted area to even multiple of 8 bytes) [END ENCRYPTED AREA] 2 bytes CRC J

089469

0895Data is guaranteed to be in order of ascending table ID, but not necessarily in order of ascending record ID within each table ID. Table Download Downloaded table records are inserted directly into the database, using the record ID as a key. Any existing records with the same record ID are overwritten. A table download packet with 0 records is used to indicate no more data. Table download packets have the following data structure:

0896Field Size: Description:

08971 byte Packet Type = 0x83 1 byte Packet Subtype = 0x01 2 bytes Packet Size [BEGIN ENCRYPTED AREA]

08981 byte Table ID being downloaded

08992 bytes Number of records (LSB first) (n)

09006 bytes Record ID of a record in the table (LSB first)

09012 bytes Record data size (in bytes, LSB first) Variable Record data

0902(Pad encrypted area to even multiple of 8 bytes) [END ENCRYPTED AREA] 2 bytes CRC

0903File Initial Download

0904File Initial Download packets have the following data structure: Field Size: Description:

09051 byte Packet Type = 0x83

09061 byte Packet Subtype = 0x02

09072 bytes Packet Size [BEGIN ENCRYPTED AREA] 4 bytes File ID being downloaded (LBS first) 4 bytes Total file size (LSB first) 4 bytes File flags (compression info, permissions, etc. - TBD) 2 bytes Number of segments (LSB first) 1 byte Path length

0908Variable pathname on local machine (Pad encrypted area to even multiple of 8-bytes) J

090970

0910[END ENCRYPTED AREA] 2 bytes CRC

0911File Next Download

0912File Next Download packets have the following data structure:

0913Field Size: Description:

09141 byte Packet Type = 0x83

09151 byte Packet Subtype = 0x03

09162 bytes Packet Size [BEGIN ENCRYPTED AREA]

09174 bytes File ID being downloaded (LBS first) 2 bytes Segment number (LSB first) 2 bytes Segment data size (LSB first) Variable Segment data (Pad encrypted area to even multiple of 8-bytes) [END ENCRYPTED AREA] 2 bytes CRC

0918File Initial Upload

0919File Initial Upload packets have the following data structure:

0920Field Size: Description:

09211 byte Packet Type = 0x83

09221 byte Packet Subtype = 0x04

09232 bytes Packet Size [BEGIN ENCRYPTED AREA]

09244 bytes File ID being uploaded (LBS first)

09254 bytes Total file size (LSB first)

09264 bytes File flags (compression info, permissions, etc. - TBD) 2 bytes Number of Segments (LSB first)

09271 byte Filename length

0928Variable Filename

0929(Pad encrypted area to even multiple of 8-bytes)

0930[END ENCRYPTED AREA] 2 bytes CRC

0931Retrieve File

0932A request to transfer a file to a client if the client's version of the file is missing or out of date. Retrieve file request packets have the following data structure:

0933Field Size: Description:

09341 byte Packet Type = 0x81 J

093571

09361 byte Packet Subtype = OxlF

09372 bytes Packet Size = 22 [BEGIN ENCRYPTED AREA]

09381 byte File Type 0 = Content

09391 = Service file 4 bytes File ID 4 bytes Current file size 4 bytes Current file modification date 2 bytes Current file CRC

0940(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

09412 bytes CRC

0942Retrieve File Response This packet is sent to the client immediately if the requested file is up to date, or does not exist, or after a series of file download packets if the file needs to be downloaded.

0943Retrieve file request packets have the following data structure:

0944Field Size: Description:

09451 byte Packet Type = 0x81

09461 byte Packet Subtype = 0x20

09472 bytes Packet Size = 22 [BEGIN ENCRYPTED AREA]

09481 byte Status

09490 = File downloaded successfully

09501 = Current file is up to date

09512 = Error downloading 3 = File not found

09524 = System error 4 bytes File ID 4 bytes Current file size 4 bytes Current file modification date 2 bytes Current file CRC

0953(Pad encrypted area to even 8-byte boundary with zeros) [END ENCRYPTED AREA]

09542 bytes CRC

0955For the synchronization function, assuming that the inventory of a customer is being downloaded, e.g. from a database associated with a regional server to a database associated with an arcade, public PC or J

095672 validation and redemption terminal, the packets can add a field (e.g. 4 bytes) which identifies the customer.

0957The administration terminal 43 contains a database which specifies the entire system, in subdatabases which can be specified as classes. The content of the complete database, or the content of each subdatabase can be specified by a single administration entity, or any can be specified by authorized suppliers. In the latter case, the content of the subdatabases can be filled by communication between the terminal 43 and suppliers' terminals, using the system shown in Figure 1.

0958Subdatabases are preferred to relate to the following: Suppliers Locations

0959Game Machines Game Software

0960Redemptions Tournaments

0961Merchandise Categories Pricing Prizes Alarms Schedules Manufacturers

0962Customers Technicians

0963Advertising Content

0964Coupons Loyalty Programs

0965Promotions Services Profile Descriptor (e.g. VALs)

0966VAL™ is a standard profile descriptor which has been adopted by some companies. VALs or class systems used by other companies can be stored and used in addition to or as a replacement for the demographic classification described herein.

0967Game Software is an example of the above. A field of the above can be the identification of a game which is located on a CD ROM, hard disk drive, DVD or J

096873 mass semiconductor or other storage means at a game location. Another field can be an algorithm which controls the parameters of the game. Another field can store score brackets which a player must reach in order to win a prize. Another field can store timing information which can be used to modify the brackets. Other fields can be filled with other data required for the game .

0969The other subdatabases can be similarly filled with data to specify the operation of each parameter of the system. For example, a merchant can specify a premium related to the merchant's store as a prize to the player of a game at an arcade nearby to the store. A field in the prize or coupon subdatabase can point to the game or games for which the premium or coupon is to be distributed, another can specify a score bracket to be achieved (which can be >0) by the player in order to win the premium or coupon, etc.

0970Once the database has been completed to a required level, the subdatabases are downloaded to the decision support server 7, which stores it in its database 9. The decision support server then downloads the data as related to the various peripheral terminals to the associated regional servers, which in turn stores required data in their respective databases 5A to 5N, and downloads the data related to the respective terminals to those of concern.

0971As a further example, regional server 5A downloads initialization parameters to the master games 21 in the arcades in which authorized game machines are located which can communicate with the regional server 5A. It also downloads initialization parameters to the software at the public PCs with which it can J

097274 communicate, which have been authorized at the administration location.

0973For example, the initialization parameters may initialize or authorize operation of particular video games, with particular score brackets, at the arcade 17 and at the public PC. The initialization parameters may also initialize a program at the public PC which controls acceptance of payments, and/or acceptance of orders for merchandise, and/or redemption of premiums, etc., and also controls transmission of data to the regional server which updates the account of the customer in currency or other media of exchange such as loyalty points, etc.

0974Table 1 which is attached at the end of this specification describes preferred subdatabases to be established initially at the administration terminal, which specify games, software, advertisements and other matters, and their parameters, which are downloaded to the terminals in a manner as described above. Each of the subdatabases is headed by a table name, and each of the fields describes the content of the field; its content and use are self evident from the name chosen.

0975It was noted above that parameters can be downloaded for the operation of a game. The shell of a game can have a requirement for score formulae to be inserted. The score formulae can be determined at the administration terminal, and downloaded as noted earlier, as one or more parameters of the game.

0976For example, consider the Pacman^tm game. Key graphical elements of the game are. dots, fruits, ghosts, and the game requires a scope. These elements can be used in formulae; for example the dots can be J

097775 given a statistic S00, the fruits a statistic SOI, the ghosts a statistic S02 and the scope a statistic S03. A formula can be determined, e.g. (S00 + 5) * S03 to determine an output score for dots, for example. The formulae can be modified by a player rating, the player having been identified by his ID card that has been swiped. The formulae can be modified by the time of day, the number of games played in a certain time interval, the score brackets achieved by players in a certain time interval, etc.

0978Indeed, a game can be refreshed by formulae which change the object of a game. An easy game can be made more difficult or different based on the formulae for a particular player profile. Loyalty points, coupons or other prizes can be awarded based on different formulae. These can be specified by different suppliers' terminals interacting with the administration terminal, or solely at the administration terminal. Prizes can be awarded based on a history of plays at a particular location. Par level and score brackets can be automatically adjusted. With reference to Figure 3, a histogram is shown of scores of a game against the number of plays achieving the scores. Within the region A, the top 10% of scores occur.

0979Within the region B, the next 20% of scores occur, and within the region C, the next 30% of scores occur. A supplier determines, through the administration terminal, that the best prizes should be awarded for the scores in region A, the next best prizes for the scores in region B, and the lowest prize for the scores in region C. The software can store the scores, and supply the scores to the game shell software to adjust the regions A, B and C, depending on how well and how many players play, and the history of prize redemptions at the particular game location, as specified by parameters input at the administration terminal. This can consist of adding the scores together, and if there have been prize redemptions in excess of a predetermined number established at the administration terminal, skewing the scores, or multiplying the scores, by a number or game handicap value. This process of skewing, in effect varies the shape and placement of the curve shown in Figure 4, and provides an automatic par or bracket adjustment for the game. The software can also keep track of a player's score on a particular game and store it in the player's database, and can forbid the awarding of a prize to the player for a particular game within a certain time interval or within a certain arcade. This will stop a good player from collecting too many prizes or too large a prize on a single machine if the number of players is low, or if the player monopolizes a game. A key aspect of the system is to control the advertising shown to specific subscribers. Advertising can be shown in "slots", e.g. frames on a video game or public PC display. The administrator can specify advertisement types as indicated in the matrix of Figure 4 as "Ad Target Types to Play", i.e. types of ads for specific matched demographic player types. The first column in the matrix specifies "When To Play" . For example, when no player is present, advertisement types "0x00" followed by "Location Attract", followed by "Terminal Attract (for this J

098077 terminal's ID or a broadcast ID)" are specified. When an unidentified player is present (e.g. by detecting a body using an infrared detector) , but no service has been selected, an additional advertisement "0x01" is run immediately following advertisement "0x00". The entire matrix is filled out at an administrative location and is stored at the administration terminal 43 database, and once complete, it is downloaded to the decision support server 7, and stored in its database 9. It is then downloaded to the regional server, where it is stored in database 5A, and is downloaded to the master game 21, where it is stored in database 23.

0981The master game 21 then controls the local DVD or CD ROM in accordance with the local condition (when to play) , to run the advertisements identified in the matrix.

0982One of the parameters that can be used in an advertisement subdatabase is a demographic limit. For example, a field parameter can specify that playing of an advertisement for a toy doll can be logically nulled in the event that the location of the game, or the location of the identified player, is in a bar. This information can be downloaded with the initialization data for an advertisement and/or for a player.

0983Once playing is initialized, the advertisement specified in the database matrix or the equivalent stored at the database 23 of the master game 21 is indicated to the game shell to be loaded from the DVD or CD ROM. The game shell inserts the advertisement into a time slot and window (or full screen) on the game (or public PC or other form of) display. Unless the presence of a player, identified or not, has been detected (e.g. detected by an infrared detector, by swiping of a player's card in a card reader, by detection of a bar code of a coupon or premium by a bar code reader at a validation and redemption center, or by detection of a personal characteristic such as handwriting, voice, fingerprint, palmprint, iris, etc.) once display of the advertisement has been completed, the master game (or public PC) software accesses the database matrix or the equivalent and causes the next advertisement to run via the shell and be displayed.

0984In the event the presence of a subscriber, or of an identified subscriber, is detected, the master game (or public PC) software accesses the advertisement matrix in the database 23, and determines that a different schedule of advertisements should be run. It then indicates which is the first of the advertisements in this schedule, and causes it to run via the shell, as described above.

0985It will be recognized that a player will typically interrupt an attraction mode advertisement by indicating that he wishes to play a game, e.g. by swiping his card in the card reader of a game, or by depositing coins in the coin acceptor of the game and keying in an identification code. The game software will then indicate this to the master game, which stores an indication in the indicated subscriber's database the identity of the last complete advertisement that the subscriber has seen. This is stored in the table "SUBSCRIBER_AD", under "AD_ID" (See Table 1 located at the end of this specification) .

0986When the subscriber is next indicated as being present at a viewable location, and is not playing a game, the next advertisement in the sequence indicated on the J

098779 matrix is controlled by the master game or public PC to be displayed.

0988It will be noted from Table 1 that the record: table = "Ad_Target" contains fields which specify the minimum and maximum daily exposures, and the minimum and total daily exposures of an advertisement. These values can be based on sales of the advertisement, and are specified by the administrator.

0989Considering the tables of the database relating to the advertising, in the table AD,

0990- the first field RECORD_ID stores the record number,

0991- the field AD_ID stores the identity of the advertisement,

0992- the field CONTENT_ID identifies the file(s) that make up the advertisement (video clips, audio, image, etc.),

0993- the field PRECEDING_AD_ID identifies the advertisement to be run immediately preceding this one,

0994- the field NEXT_AD_ID identifies the advertisement to be run immediately following this one, - the field MAX_VIEWS_PER_PERSON specifies the maximum number of times the present advertisement should be shown to an identified subscriber,

0995- the field FLAGS can be used to for various purposes, such as inhibiting a specified ad from playing e.g. inhibiting plays from bars, casinos, arcades, general audiences, men, women, male teens, female teens, etc.

0996With the above detailed explanation of the first table, the remaining tables (records) and fields are believed to be self-explanatory from the names given to the tables and to each of the fields.

0997It should also be noted that advertisements can be selected based on an algorithm. For example, a random number (e.g. between 0 and 9, say 5) can be 80 obtained from a random number generator. That random number 5 can identify e.g. a video or slide advertisement to be run. Following running, that random number can be added to another predetermined number (e.g. 3), to identify the next advertisement to be run, e.g. advertisement number 8. Following running of advertisement number 8, that number can be added to another predetermined number (e.g. 7), to identify the next advertisement to be run, e.g. advertisement number 15, etc. The selection of which advertisement to run can cycle back to the beginning, or once a predetermined highest number has been reached, another random number can be selected and the process started again. It may be seen that the identity of advertisements that are selected for playing have been filtered through a schedule of particular advertisements. It is preferred that they should also be filtered by exclusions, for unsuitable advertisements. For example, cigarette advertisements or advertisements containing unsuitable subject matter can be excluded from certain locations, and competitor's products can be excluded from certain locations. These exclusions (URCs) can be stored in the table = ADJJRC.

0998The field RECORD_ID in this table stores the record identity. The field AD_ID stores the identity of the advertisement against which the URC is to be applied. The URC can be comprised of a data field illustrated in Figure 5.

0999The numeric value indicates the URC restriction code number. The bit in the flag indicates IS or NO, depending on whether it is set or not. The code (e.g. J

100081 the number 1, 2, etc.) indicates the restriction. For example, the code 1 can mean "underage". Thus for example, if the advertisement indicated in the field AD_ID in the table AD_URC is unsuitable for a person under the age of 19, the flag is set (i.e. indicates IS) . If an underage person such as age 17 years (as can be indicated by his identity on e.g. the swipe card and his age statistic taken when the subscriber is first registered) is indicated as being at a particular location by him swiping his card at a validation and redemption center, a public PC or at a game in an arcade, for example, the advertisement is filtered through the URC, and is not shown for a time period. The time period can be a predetermined interval, or until a game played by the subscriber has been terminated, or can last for a time following termination of the game.

1001It will be recognized that rather than advertisements, messages of any type can be provided for presentation to a person, and the URCs described above are equally applicable against such messages. In this specification, the term advertisements should thus be construed to include messages of any type, and presented in any way, such as by still picture, video, audio, etc. The term display should also be construed to include any form of presentation, including audio, video, tactile, odor dispersion, etc.

1002A customer may attend a validation or redemption terminal location at the location of a merchant, or at an arcade, or at the location a public PC, and wish to enter credits, or wish to be registered in the system. Entering of credits can be effected by an attendant keying in relevant information to a terminal, J

100382 sufficient to identify the person, e.g. name and address, etc., or the customer can perform the same function via an automatic terminal such as a card vending machine which provides instructions how to proceed. If there are no credits to be entered, the customer should choose a PIN number, which is recorded in a hidden manner (such as in a magnetic stripe or in the memory of a "smart card" carried on the card) , and the card is dispensed or personally given to the customer. If a currency credit is to be posted, the customer will pay the attendant or deposit money into the card vending machine, which is recorded against the identity of the customer. The data entered into the terminal is then uploaded to the regional server e.g. 1A, and is stored in its associated database 5A. The customer now will undertake certain activities, such as purchasing goods or services from any of the merchants registered in the system, or play games at the arcade. If the customer plays games at the arcade, and wishes to use the credit balance in his account to play, he will swipe his card in a card reader at the game, which identifies him and the value to be debited from his balance. If he wishes to purchase goods or services against his credit, or purchase a different service offered at the public PC (e.g. purchase printing or communication services) his card will be swiped in a card reader at the location of the merchant where he wishes to purchase the goods or services or at the public PC. In any such case, the identity of the customer, the location of the customer, the identity of the merchant, game or public PC, and the amount of the debit will be uploaded into and stored in the database J

100483

10055A after being recorded at the location (e.g. in database 23 if the transaction occurred at the arcade) .

1006The administrator had already entered into its database using terminal 43 loyalty point values for certain activities, which had been downloaded and stored at database 9, and then loaded to databases 5A..5N. Therefore for each activity undertaken by the customer for which loyalty points are to be awarded, they are credited to the customer's account stored in the customer's database of the regional server. These loyalty points can then be used as a form of scrip by the customer, apart from, or with cash deposits.

1007In addition, the administrator can specify and store records in the aforenoted databases that premium coupons should be dispensed for the customer at the determined location of the customer via a local printer, for defined activities undertaken by the customer.

1008Loyalty points, game credits for future play and/or coupons can also be awarded to the account of the customer and/or dispensed when predetermined scores or score brackets are achieved on the games (whether due to individual play or in tournaments) by the identified customer player. The amounts of the loyalty points, game credits or coupons can be varied by time, by location, by number of players having played the game or tournament within a certain time interval or within certain clock times, by number of players, by demographic of the player, by difficulty of the game, by game handicap, etc. All such variations can be established at the administration location by means of a matrix (or form) to be filled in, such as shown in Table I attached J

100984 hereto and forming part of this specification, and stored in the databases as described above. Indeed, the administrator can indicate a conversion of loyalty points to currency, for redemption or for use to purchase goods of particular ones or of any goods or services provided by member merchants.

1010When a customer wishes to redeem a coupon, the customer presents it to a merchant, public pc operator, public pc, etc., its bar code is read by a bar code reader at a validation and redemption terminal, and the customer's identification is read from his card by a card reader, at the validation and redemption terminal. The identification (and value, if desired for greater security) of the coupon is uploaded to the regional server, and the database is accessed using the identification of the customer. The identity of the coupon is then checked in the customer's record, and if the coupon had been validly recorded, a message is sent to the validation and redemption terminal acknowledging the validity of the transaction. An acknowledgement is entered into the terminal and is uploaded to the regional server, which either marks the coupon record as having been used, or deletes it from the customer's record. In either case, information of the awarding, and subsequently of the redemption of the coupon, is entered to database 9 via the decision support server, to provide a statistical report to terminal 43 either immediately or from time to time as to volumes and identities of services used by the customer or by groups of customers, by demographics, etc. and coupons and loyalty points awarded and redeemed, and the identity of the merchant or terminal performing the redemption. J

101185

1012These statistics provide a good measure for the administrator to be able to use for reporting and/or advertising of the benefits of the system to prospective merchants and others which may wish to advertise on the system or which may wish to include their goods, services and locations as part of the system. In addition, it provides the information to the administrator for settling the merchants' accounts, as described earlier. The loyalty points thus have been used as a medium of exchange separate from currency.

1013It should be noted that while the description herein is to a client-server type system which communicate in a particular manner, the equivalent function and structure of the invention could also be realized by persons skilled in the art understanding this invention via one or more browsers which interface one or more web pages, either via the internet or on one or more intranets which are either self-contained or which communicate via the internet or via private network.

1014A person understanding this invention may now conceive of alternate embodiments and enhancements using the principles described herein. All such embodiments and enhancements are considered to be within the spirit and scope of this invention as defined in the claims appended hereto. TABLE 1

1015# initdb.ini #

1016# NOTES:

1017# 1. Database name cannot exceed 23 characters

1018# 2. Allowed data type are LONG, SHORT, BIN, VARBIN

1019# 3. Table names cannot exceed 23 characters

1020# 4. Field names cannot exceed 23 characters

1021# 5. Arrays of SHORT and LONG are not supported (set size = 1)

1022# 6. Variable binary fields as primary keys is not supported

1023# 7. Each table can have only one variable binary field

1024# 8. Variable binary field must be last field in table

1025# 9. Variable binary field must be preceded by SHORT size field

1026# 10. File created will be database name with ".db" appended

1027# 11. Tables cannot exceed 32 fields

1028DATABASE = nani

1029TABLE = AD

1030FIELD = RECORD ID BIN 6 PK

1031FIELD = AD ID LONG 1

1032FIELD = CONTENT ID LONG 1

1033FIELD = PRECEDING AD ID LONG 1

1034FIELD = NEXT AD ID LONG 1

1035FIELD = MAX VIEWS PEP _PERSON SHORT 1

1036FIELD = FLAGS BIN 1

1037TABLE = AD SCHEDULE

1038FIELD = RECORD ID BIN 6 PK

1039FIELD = AD ID LONG 1

1040FIELD = TERMINAL ID BIN . 6

1041FIELD = SCHEDULE ID LONG 1

1042FIELD = FLAGS BIN 1

1043TABLE _= AD TARGET

1044FIELD = RECORD ID : BIN : 6 PK

1045FIELD = TARGET ID : LONG : 1

1046FIELD = AD ID : LONG : 1

1047FIELD = TARGET TYPE : BIN : 1

1048FIELD = TARGET EVENT ID : LONG : 1

1049FIELD = TARGET SERVICE ID : LONG : 1

1050FIELD = SLOT : BIN : 1 FIELD = PRIORITY BIN : 1

1051FIELD = MIN DAILY EXPOSURES SHORT : 1

1052FIELD = MAX DAILY EXPOSURES SHORT : 1

1053FIELD = MIN TOTAL EXPOSURES LONG : 1

1054FIELD = MAX TOTAL EXPOSURES LONG : 1

1055FIELD = FLAGS BIN : 1

1056TABLE = AD TARGET DEMOGRAPHIC

1057FIELD = RECORD ID BIN 6 PK

1058FIELD = TARGET ID LONG : 1

1059FIELD = DEMOGRAPHIC LONG : 1

1060FIELD = FLAGS BIN 1

1061TABLE = AD TARGET PROMOTION

1062FIELD = RECORD ID BIN : 6 PK

1063FIELD = TARGET ID LONG 1

1064FIELD = PROMOTION ID LONG 1

1065FIELD = FLAGS BIN 1

1066TABLE = AD URC

1067FIELD = RECORD ID BIN 6 PK

1068FIELD = AD ID LONG 1

1069FIELD = URC LONG 1

1070FIELD = FLAGS BIN 1

1071TABLE = ALARM HANDLER

1072FIELD = RECORD ID BIN 6 PK

1073FIELD = HANDLER ID LONG 1

1074FIELD = ALARM CODE BIN 1

1075FIELD = PRIORITY BIN 1

1076FIELD = PROCESS TYPE BIN 1

1077FIELD = FLAGS BIN 1

1078FIELD = PROCESS DATA SIZE SHORT 1

1079FIELD = PROCESS_DATA VARBIN 1

1080TABLE = BRACKET

1081FIELD = RECORD ID BIN 6 PK

1082FIELD = TOURNAMENT ID : LONG . 1

1083FIELD = BRACKET ID BIN 1

1084FIELD = SHORT NAME . BIN 28

1085FIELD = NAME : BIN : 72

1086FIELD = START DATE TIME : LONG : 1

1087FIELD = END DATE TIME : LONG : 1

1088FIELD = SCORE POSTING _TIME : LONG : 1

1089FIELD = ENTRY PRICE : LONG : 1

1090FIELD = PREPAID PLAYS : SHORT : 1

1091FIELD = MIN GAMES PER PLAYER : SHORT : 1

1092FIELD = MAX GAMES PER^" PLAYER : SHORT : 1

1093FIELD = MIN GAMES PER ^"TEAM : SHORT : 1

1094FIELD = MAX GAMES PER^" TEAM : SHORT : 1 FIELD = LEADERBOARD ID : LONG 1

1095FIELD = SPONSER : BIN : 40

1096FIELD = ICON : LONG : 1

1097FIELD = SPLASH SCREEN : LONG 1

1098FIELD = FLAGS BIN 1

1099FIELD = RANKING_ALGORITHM : BIN : 1

1100TABLE = BRACKET ADVANCE

1101FIELD = RECORD ID BIN 6 PK

1102FIELD = TOURNAMENT ID LONG 1

1103FIELD = BRACKET ID BIN 1

1104FIELD = ADVANCE TYPE BIN 1

1105FIELD = FROM TOURNAMENT ID LONG 1

1106FIELD = FROM BRACKET ID BIN 1

1107FIELD = FROM LOW LONG 1

1108FIELD = TO HIGH LONG 1

1109FIELD = SERVICE ID LONG 1

1110FIELD = PROFILE BIN 1

1111FIELD = FLAGS BIN 1

1112TABLE = BRACKET MEMBERSHIP

1113FIELD = RECORD ID BIN 6 PK

1114FIELD = TOURNAMENT ID LONG 1

1115FIELD = BRACKET ID BIN 1

1116FIELD = SUBSCRIBER ID LONG 1

1117FIELD = FLAGS BIN 1

1118TABLE = BRACKET PRIZE

1119FIELD = RECORD ID BIN 6 PK

1120FIELD = TOURNAMENT ID LONG : 1

1121FIELD = BRACKET ID BIN 1

1122FIELD = PRIZE ITEM ID LONG . 1

1123FIELD = PRIZE PERCENT OF POOL BIN . 1

1124FIELD = WINNING PLACE : BIN : 1

1125FIELD = PLACE NAME BIN : 20

1126FIELD = NUM WINNERS LONG : 1

1127FIELD = EXPIRATION DATE : LONG : 1

1128FIELD = FLAGS : BIN : 1

1129TABLE = BRACKET PROMOTION

1130FIELD = RECORD ID : BIN : 6 PK

1131FIELD = TOURNAMENT ID : LONG : 1

1132FIELD = BRACKET ID BIN : 1

1133FIELD = PROMOTION ID : LONG : 1

1134FIELD = FLAGS : BIN : 1

1135FIELD = MIN_RANK : SHORT : 1

1136TABLE = BRACKET RULE SCREEN

1137FIELD = RECORD ID : BIN : 6 PK

1138FIELD = TOURNAMENT ID : LONG : 1 FIELD = BRACKET ID BIN 1

1139FIELD = SERVICE ID LONG 1

1140FIELD = SCREEN INDEX BIN 1

1141FIELD = CONTENT ID LONG 1

1142FIELD = FLAGS BIN 1

1143TABLE = BRACKET SCHEDULE

1144FIELD = RECORD ID BIN 6 PK

1145FIELD = TOURNAMENT ID LONG 1

1146FIELD = BRACKET ID BIN 1

1147FIELD = TERMINAL ID BIN 6

1148FIELD = SCHEDULE ID LONG 1

1149FIELD = FLAGS BIN 1

1150FIELD = NUM_LOCAL_LEADERS SHORT 1

1151TABLE = BRACKET SERVICE

1152FIELD = RECORD ID BIN 6 PK

1153FIELD = TOURNAMENT ID LONG 1

1154FIELD = BRACKET ID BIN 1

1155FIELD = SERVICE ID LONG 1

1156FIELD = PROFILE BIN 1

1157FIELD = PRICING ID LONG 1

1158FIELD = FLAGS BIN 1

1159FIELD = MIN RATING ALLOWED BIN 1

1160FIELD = MAX_RATING_ALLOWED BIN 1

1161TABLE = CATALOG CATEGORY

1162FIELD = RECORD ID BIN 6 PK

1163FIELD = CATEGORY ID LONG 1

1164FIELD = CATEGORY NAME BIN 40

1165FIELD = PARENT CATEGORY ID LONG 1

1166FIELD = ICON LONG 1

1167FIELD = FLAGS BIN 1

1168TABLE = CATALOG CATEGORY URC

1169FIELD = RECORD ID ^• BIN 6 PK

1170FIELD = CATEGORY ID LONG 1

1171FIELD = URC . LONG 1

1172FIELD = FLAGS : BIN : 1

1173TABLE = CONTENT

1174FIELD = RECORD ID : BIN : 6 PK

1175FIELD = CONTENT ID : LONG : 1

1176FIELD = FORMAT : BIN 1

1177FIELD = DURATION MS : LONG : 1

1178FIELD = PATHNAME : BIN : 60

1179FIELD = FILE SIZE : LONG . 1

1180FIELD = CRC : SHORT : 1

1181FIELD = FILE TIMESTAMP : LONG : 1

1182FIELD = FLAGS : BIN : 1 TABLE = COUPON

1183FIELD = RECORD ID BIN : 6

1184FIELD = COUPON-ID LONG : 1

1185FIELD = DESCRIPTION BIN : 40

1186FIELD = CONTENT ID LONG : 1

1187FIELD = UPC SYMBOL BIN : 12

1188FIELD = FACE VALUE LONG : 1

1189FIELD = MAX ISSUED PER _PLAYER SHORT : 1

1190FIELD = FLAGS BIN : 1

1191TABLE = COUPON ITEM SCHEDULE

1192FIELD = RECORD ID BIN 6 PK

1193FIELD = COUPON ID LONG : 1

1194FIELD = ITEM ID LONG 1

1195FIELD = TERMINAL ID BIN 6

1196FIELD = SCHEDULE ID LONG : 1

1197FIELD = COUPON CASH VALUE LONG 1

1198FIELD = COUPON PRICE LONG 1

1199FIELD = NUM ITEMS PER ( DOUPON SHORT 1

1200FIELD = MAX REDEEMED SHORT 1

1201FIELD = FLAGS BIN 1

1202TABLE = COUPON SERVICE _SCHEDULE

1203FIELD = RECORD ID BIN 6 PK

FIELD — COUPON ID LONG 1

1205FIELD = SERVICE ID LONG 1

1206FIELD = TERMINAL ID BIN 6

1207FIELD = SCHEDULE ID LONG 1

1208FIELD = COUPON CASH VALUE . LONG 1

1209FIELD = COUPON PRICE LONG 1

1210FIELD = NUM PLAYS PER < COUPON SHORT 1

1211FIELD = MAX REDEEMED SHORT 1

1212FIELD = FLAGS . BIN : 1

1213TABLE = FILE INFO

1214FIELD = RECORD ID : BIN : 6 PK

1215FIELD = FILE ID : LONG : 1

1216FIELD = FILESET ID : LONG : 1

1217FIELD = PATHNAME : BIN : 60

1218FIELD = FILE SIZE : LONG : 1

1219FIELD = CRC : SHORT : 1

1220FIELD = FILE TIMESTAMP : LONG : 1

1221FIELD = FLAGS : BIN : 1

1222TABLE = ITEM

1223FIELD = RECORD ID : BIN : 6 PK

1224FIELD = ITEM ID : LONG : 1

1225FIELD = CATEGORY ID : LONG : 1

1226FIELD = ITEM NAME : BIN : 40

1227FIELD — MIN PRICE : LONG : 1 FIELD = MAX PRICE LONG 1

1228FIELD = ICON LONG 1

1229FIELD = FLAGS BIN 1

1230FIELD = ITEM COST LONG 1

1231FIELD = RETAIL PRICE LONG 1

1232FIELD = QUANTITY ON HAND LONG 1

1233FIELD = MIN QUANTITY ON HAND LONG 1

1234FIELD = DISTRIBUTION_LOCATION BIN 40

1235TABLE = ITEM ATTRIBUTE

1236FIELD = RECORD ID BIN 6 PK

1237FIELD = ITEM ID LONG 1

1238FIELD = ATTRIBUTE ID BIN 1

1239FIELD = ATTRIBUTE NAME BIN 40

1240FIELD = DATA TYPE BIN 1

1241FIELD = MINIMUM LONG 1

1242FIELD = MAXIMUM LONG 1

1243FIELD = FLAGS BIN 1

1244TABLE = ITEM ATTRIBUTE VALUE

1245FIELD = RECORD ID BIN 6 PK

1246FIELD = ITEM ID LONG 1

1247FIELD = ATTRIBUTE ID BIN 1

1248FIELD = VALUE INDEX BIN 1

1249FIELD = VALUE TEXT BIN 30

1250FIELD = FLAGS BIN . 1

1251TABLE = ITEM PROMOTION

1252FIELD = RECORD ID BIN 6 PK

1253FIELD = ITEM ID LONG : 1

1254FIELD = PROMOTION ID LONG 1

1255FIELD = FLAGS BIN 1

1256TABLE = ITEM SCHEDULE

1257FIELD = RECORD ID BIN 6 PK

1258FIELD = ITEM ID LONG : 1

1259FIELD = TERMINAL ID BIN : 6

1260FIELD = SCHEDULE ID LONG 1

1261FIELD = FLAGS BIN 1

1262TABLE = ITEM SCREEN

1263FIELD = RECORD ID BIN 6 PK

1264FIELD = ITEM ID LONG 1

1265FIELD = SCREEN INDEX BIN : 1

1266FIELD = CONTENT ID ^■ LONG : 1

1267FIELD = FLAGS BIN . 1

1268TABLE = ITEM URC

1269FIELD = RECORD ID BIN ^• 6 PK

1270FIELD = ITEM ID LONG : 1 FIELD = URC : LONG : 1

1271FIELD = FLAGS : BIN : 1

1272TABLE = LEADERBOARD

1273FIELD = RECORD ID : BIN : 6 PK

1274FIELD = LEADERBOARD ID : LONG : 1

1275FIELD = LEADERBOARD DATE TIME : LONG : 1

1276FIELD = FLAGS : BIN : 1

1277FIELD = MAX_LEADERS : SHORT : 1

1278TABLE = LEADERBOARD LEADER

1279FIELD = RECORD ID : BIN : 6 PK

1280FIELD = LEADERBOARD ID : LONG : 1

1281FIELD = SUBSCRIBER ID LONG : 1

1282FIELD = ALIAS : BIN : 26

1283FIELD = LOCATION NAME : BIN : 26

1284FIELD = LOCATION CITY STATE BIN : 26

1285FIELD = PRIZE NAME BIN 26

1286FIELD = SCORE LONG 1

1287FIELD = SCORE DATE TIME LONG 1

1288FIELD = FLAGS BIN 1

1289TABLE = LEADERBOARD RANKING

1290FIELD = RECORD ID BIN 6 PK

1291FIELD = LEADERBOARD ID LONG 1

1292FIELD = RANK SHORT 1

1293FIELD = SUBSCRIBER ID LONG 1

1294FIELD = FLAGS BIN 1

1295TABLE = LOCATION

1296FIELD = RECORD ID BIN 6 PK

1297FIELD = LOCATION ID . LONG : 1

1298FIELD = SHORT NAME BIN 26

1299FIELD = NAME BIN : 72

1300FIELD = SHORT CITY STATE : BIN : 26

1301FIELD = CITY STATE : BIN : 72

1302FIELD = TIME ZONE : BIN : 1

1303FIELD = MAX DAILY PAYOUT : LONG : 1

1304FIELD = DIALIN INTERVAL : LONG : 1

1305FIELD = LANGUAGE CODE : SHORT : 1

1306FIELD = COUNTRY CODE : SHORT : 1

1307FIELD = FLAGS : BIN : 1

1308FIELD = TOKEN_PRICE : LONG : 1

1309TABLE = LOCATION ATTRACT SCREEN

1310FIELD = RECORD ID : BIN : 6 PK

1311FIELD = LOCATION ID : LONG : 1

1312FIELD = SCREEN INDEX : BIN : 1

1313FIELD = CONTENT ID : LONG : 1

1314FIELD -= FLAGS : BIN : 1 TABLE = LOCATION COUPON SCHED

1315FIELD = RECORD ID : BIN : 6 PK

1316FIELD = LOCATION ID : LONG : 1

1317FIELD = COUPON ID : LONG : 1

1318FIELD = SCHEDULE ID : LONG : 1

1319FIELD = COUPON PRICE : LONG : 1

1320FIELD = FLAGS : BIN : 1

1321TABLE = LOCATION LOYALTY SCHED

1322FIELD = RECORD ID : BIN : 6 PK

1323FIELD = LOCATION ID : LONG : 1

1324FIELD = LOYALTY PROGRAM ID LONG 1

1325FIELD = SCHEDULE ID : LONG : 1

1326FIELD = POINT PRICE : LONG : 1

1327FIELD = FLAGS BIN 1

1328TABLE = LOCATION URC

1329FIELD = RECORD ID BIN 6 PK

1330FIELD = LOCATION ID LONG 1

1331FIELD = URC LONG 1

1332FIELD = FLAGS BIN 1

1333TABLE = LOYALTY PROGRAM

1334FIELD = RECORD ID BIN 6

1335FIELD = LOYALTY PROGRAM ID LONG 1

1336FIELD = NAME BIN 40

1337FIELD = POINT LABEL BIN 20

1338FIELD = FLAGS BIN 1

1339TABLE = LOYALTY ITEM SCHED

1340FIELD = RECORD ID BIN 6 PK

FIELD — LOYALTY PROGRAM ID LONG 1

1342FIELD = ITEM ID LONG 1

1343FIELD = TERMINAL ID BIN 6

1344FIELD = SCHEDULE ID LONG 1

1345FIELD = POINT CASH VALUE LONG 1

1346FIELD = POINT PRICE LONG : 1

1347FIELD = POINT PER ITEM SHORT 1

1348FIELD = ITEMS PER POINT SHORT 1

1349FIELD = MAX USED PER ITEM : SHORT : 1

1350FIELD = FLAGS . BIN : 1

1351TABLE = LOYALTY SERVICE SCHED

1352FIELD = RECORD ID : BIN : 6 PK

1353FIELD = LOYALTY PROGRAM ID : LONG : 1

1354FIELD = SERVICE ID : LONG : 1

1355FIELD = TERMINAL ID : BIN : 6

1356FIELD = SCHEDULE ID : LONG : 1

1357FIELD = POINT CASH VALUE : LONG : 1

1358FIELD = POINT PRICE : LONG : 1 FIELD = POINTS PER PLAY SHORT 1

1359FIELD = PLAYS PER POINT SHORT : 1

1360FIELD = MAX USED PER PLAY SHORT 1

1361FIELD = FLAGS BIN 1

1362TABLE = PRICING

1363FIELD = RECORD ID BIN 6 : PK

1364FIELD = PRICING ID LONG 1

1365FIELD = PRICE TO START LONG 1

1366FIELD = PRICE TO CONTINUE LONG 1

1367FIELD = START DURATION LONG 1

1368FIELD = CONTINUE DURATION LONG 1

1369FIELD = FLAGS BIN 1

1370TABLE = PROMOTION

1371FIELD = RECORD ID BIN 6 : PK

1372FIELD = PROMOTION ID LONG 1

1373FIELD = FLAGS BIN 1

1374TABLE = PROMOTION COUPON

1375FIELD = RECORD ID BIN 6 : PK

1376FIELD = PROMOTION ID LONG 1

1377FIELD = COUPON ID TO AWARD LONG 1

1378FIELD = FLAGS BIN 1

1379TABLE = PROMOTION LOYALTY

1380FIELD = RECORD ID BIN 6 : PK

1381FIELD = PROMOTION ID LONG 1

1382FIELD = LOYALTY PROGRAM ID LONG 1

1383FIELD = NUM POINTS TO AWARD SHORT 1

1384FIELD = FLAGS BIN 1

1385TABLE = REDEMPTION

1386FIELD = RECORD ID BIN 6 : PK

1387FIELD = REDEMPTION ID LONG 1

1388FIELD = FLAGS BIN 1

1389FIELD = MIN RATING ALLOWED BIN 1

1390FIELD = MAX RATING ALLOWED . BIN 1

1391FIELD = SERVICE ID LONG 1

1392FIELD = PROFILE BIN 1

1393FIELD = SHORT NAME ^• BIN : 28

1394FIELD = NAME BIN 72

1395FIELD = PRICING ID LONG . 1

1396FIELD = START DATE TIME : LONG : 1

1397FIELD = END DATE TIME : LONG : 1

1398FIELD = SPONSER : BIN : 40

1399FIELD = ICON : LONG 1

1400FIELD = SPLASH SCREEN : LONG : 1

1401FIELD = PERCENT MONEY TO POOL : BIN : 1

1402FIELD = CURRENT POOL VALUE : LONG : 1 FIELD = VALUE OF AVAIL PRIZES : LONG 1

1403FIELD = PLAYS TO DATE : LONG : 1

1404FIELD = LAST_UPDATE_DATE_TIME : LONG : 1

1405TABLE = REDEMPTION PAR LEVEL

1406FIELD = RECORD ID BIN 6 PK

1407FIELD = REDEMPTION ID : LONG 1

1408FIELD = PAR LEVEL BIN 1

1409FIELD = PAR SCORE LONG 1

1410FIELD = TARGET PAY PERCENT BIN 1

1411FIELD = PRIZE ITEM ID LONG 1

1412FIELD = PERCENT OF POOL APPLIED BIN 1

1413FIELD = EXPIRATION DATE LONG 1

1414FIELD = NUM REMAINING LONG 1

1415FIELD = MIN WIN INTERVAL LONG 1

1416FIELD = FLAGS BIN 1

1417FIELD = MIN_PRIOR_PLAYS LONG 1

1418TABLE = REDEMPTION PROMOTION

1419FIELD = RECORD ID BIN 6 PK

1420FIELD = REDEMPTION ID LONG 1

1421FIELD = PROMOTION ID LONG 1

1422FIELD = FLAGS BIN 1

1423FIELD = PAR_LEVEL BIN 1

1424TABLE = REDEMPTION RULE SCREEN

1425FIELD = RECORD ID BIN 6 PK

1426FIELD = REDEMPTION ID LONG 1

1427FIELD = SCREEN INDEX BIN 1

1428FIELD = CONTENT ID LONG 1

1429FIELD = FLAGS BIN 1

1430TABLE = REDEMPTION SCHEDULE

1431FIELD = RECORD ID . BIN : 6 PK

1432FIELD = REDEMPTION ID LONG : 1

1433FIELD = TERMINAL ID . BIN : 6

1434FIELD = SCHEDULE ID : LONG : 1

1435FIELD = FLAGS : BIN : 1

1436TABLE = REDEMPTION URC

1437FIELD = RECORD ID : BIN : 6 PK

1438FIELD = REDEMPTION ID : LONG : 1

1439FIELD = URC : LONG : 1

1440FIELD = FLAGS : BIN : 1

1441TABLE = SCHEDULE

1442FIELD = RECORD ID : BIN : 6 PK

1443FIELD = SCHEDULE ID : LONG : 1

1444FIELD = START DATE TIME : LONG : 1

1445FIELD = END DATE TIME : LONG : 1 FIELD = WEEKDAYS BIN 1

1446FIELD = START TIME OF DAY LONG 1

1447FIELD = END TIME OF DAY LONG 1

1448FIELD = FLAGS BIN 1

1449TABLE = SERVICE

1450FIELD = RECORD ID BIN 6 PK

1451FIELD = SERVICE ID LONG 1

1452FIELD = SERVICE TYPE BIN 1

1453FIELD = FLAGS BIN 1

1454FIELD = SHORT NAME BIN 30

1455FIELD = NAME BIN 72

1456FIELD = ICON LONG 1

1457FIELD = ATTRACT SCREEN LONG 1

1458FIELD = SW CAPABILITIES BIN 10

1459FIELD = HW REQUIREMENTS BIN 10

1460FIELD = FILESET ID LONG 1

1461FIELD = EXECUTABLE_FILE_ID LONG 1

1462TABLE = SERVICE PROFILE

1463FIELD = RECORD ID BIN 6 PK

1464FIELD = SERVICE ID LONG 1

1465FIELD = PROFILE BIN 1

1466FIELD = PROFILE NAME BIN 40

1467FIELD = FLAGS BIN 1

1468FIELD = SCORE FORMULA LENGTH SHORT 1

1469FIELD = SCORE_FORMULA VARBIN 1

1470TABLE = SERVICE PROFILE SETTING

1471FIELD = RECORD ID BIN 6 PK

1472FIELD = SERVICE ID LONG 1

1473FIELD = PROFILE BIN 1

1474FIELD = SETTING ID LONG 1

1475FIELD = SETTING VALUE LONG 1

1476FIELD = FLAGS BIN 1

1477TABLE = SERVICE PROMOTION

1478FIELD = RECORD ID BIN 6 PK

1479FIELD = SERVICE ID LONG 1

1480FIELD = PROMOTION ID LONG . 1

1481FIELD = FLAGS . BIN : 1

1482TABLE = SERVICE RATING

1483FIELD = RECORD ID : BIN : 6 PK

1484FIELD = SERVICE ID : LONG : 1

1485FIELD = RATING BIN : 1

1486FIELD = DESCRIPTION . BIN : 26

1487FIELD = FLAGS : BIN : 1 TABLE = SERVICE SCHEDULE

1488FIELD = RECORD ID : BIN : 6 PK

1489FIELD = SERVICE ID : LONG : 1

1490FIELD = TERMINAL ID : BIN : 6

1491FIELD = SCHEDULE ID : LONG : 1

1492FIELD = PROFILE BIN : 1

1493FIELD = PRICING ID : LONG : 1

1494FIELD = FLAGS : BIN : 1

TABLE - SERVICE SETTING

1496FIELD = RECORD ID BIN 6 PK

1497FIELD = SERVICE ID LONG 1

1498FIELD = SETTING ID LONG 1

1499FIELD = SETTING NAME BIN : 32

1500FIELD = TYPE BIN 1

1501FIELD = FLAGS BIN 1

1502TABLE = SERVICE SLOT

1503FIELD = RECORD ID BIN 6 PK

1504FIELD = SERVICE ID LONG 1

1505FIELD = SLOT BIN 1

1506FIELD = SCHEDULE ID LONG 1

1507FIELD = NUM AD PLAYS BIN 1

1508FIELD = FLAGS BIN 1

1509TABLE = SERVICE STATISTIC

1510FIELD = RECORD ID BIN 6 PK

1511FIELD = SERVICE ID LONG 1

1512FIELD = STATISTIC ID LONG 1

1513FIELD = STATISTIC NAME BIN . 20

1514FIELD = LOWER LIMIT . LONG : 1

1515FIELD = UPPER LIMIT LONG 1

1516FIELD = FLAGS BIN 1

1517TABLE = SERVICE TERMINAL

1518FIELD = RECORD ID : BIN : 6 PK

1519FIELD = SERVICE ID : LONG : 1

1520FIELD = TERMINAL ID BIN : 6

1521FIELD = LICENSE KEY BIN : 16

1522FIELD = FILESET ID ^• LONG : 1

1523FIELD = FLAGS : BIN : 1

1524TABLE = SERVICE TYPE

1525FIELD = RECORD ID : BIN : 6 PK

1526FIELD = TYPE : BIN : 1

1527FIELD = PARENT TYPE : BIN : 1

1528FIELD = TYPE NAME : BIN : 16

1529FIELD = FLAGS : BIN : 1 TABLE = SERVICE URC

1530FIELD = RECORD ID BIN : 6 PK

1531FIELD = SERVICE ID LONG 1

1532FIELD = URC LONG 1

1533FIELD = FLAGS BIN : 1

1534TABLE = SUBSCRIBER

1535FIELD = RECORD ID BIN 6 PK

1536FIELD = SUBSCRIBER ID LONG 1

1537FIELD = ALIAS BIN 26

1538FIELD = FIRST NAME BIN 20

1539FIELD = LAST NAME BIN 20

1540FIELD = MIDDLE INITIAL BIN 2

1541FIELD = STREET ADDRESS BIN 40

1542FIELD = POSTAL CODE BIN 10

1543FIELD = PHONE NUMBER BIN 10

1544FIELD = BIRTH DAY BIN 1

1545FIELD = BIRTH MONTH BIN 1

1546FIELD = BIRTH YEAR SHORT 1

1547FIELD = GENDER BIN 1

1548FIELD = FLAGS BIN 1

1549FIELD = DEMOGRAPHIC LONG 1

1550FIELD = LAST_UPDATE_DATE_TIME LONG 1

1551TABLE = SUBSCRIBER AD

1552FIELD = RECORD ID BIN 6 PK

1553FIELD = SUBSCRIBER ID LONG 1

1554FIELD = AD ID LONG 1

1555FIELD = VIEW DATE TIME LONG 1

1556FIELD = FLAGS BIN 1

1557TABLE = SUBSCRIBER AVATAR

1558FIELD = RECORD ID . BIN 6 PK

1559FIELD = SUBSCRIBER ID LONG 1

1560FIELD = AVATAR TYPE BIN 1

1561FIELD = CONTENT ID . LONG 1

1562FIELD = FLAGS : BIN : 1

1563TABLE = SUBSCRIBER BRACKET

1564FIELD = RECORD ID : BIN 6 PK

1565FIELD = SUBSCRIBER ID : LONG : 1

1566FIELD = TOURNAMENT ID . LONG 1

1567FIELD = BRACKET ID : BIN 1

1568FIELD = GAMES PLAYED : SHORT : 1

1569FIELD = FLAGS : BIN : 1

1570FIELD = RANK : LONG 1

1571FIELD = RANK DATE TIME : LONG . 1

1572FIELD = RANK SCORE : LONG : 1

1573FIELD = AVERAGE SCORE : LONG : 1 TABLE = SUBSCRIBER CARD

1574FIELD = RECORD ID : BIN : 6 PK

1575FIELD = SUBSCRIBER ID : LONG : 1

1576FIELD = CARD TYPE BIN : 1

1577FIELD = CARD DATA : BIN : 16

1578FIELD = FLAGS : BIN : 1

1579TABLE = SUBSCRIBER RATING

1580FIELD = RECORD ID BIN : 6 PK

1581FIELD = SUBSCRIBER ID LONG : 1

1582FIELD = SERVICE ID : LONG : 1

1583FIELD = PROFILE BIN : 1

1584FIELD = RATING BIN : 1

1585FIELD = HANDICAP LONG 1

1586FIELD = PLAYS TO QUALIFY BIN 1

1587FIELD = FLAGS BIN : 1

1588TABLE = SUBSCRIBER SAVE STATE

1589FIELD = RECORD ID BIN 6 PK

1590FIELD = SUBSCRIBER ID LONG 1

1591FIELD = SERVICE ID LONG 1

1592FIELD = SLOT NUMBER BIN 1

1593FIELD = PROFILE BIN 1

1594FIELD = SAVE STATE NAME BIN 20

1595FIELD = DATA FILE ID LONG 1

1596FIELD = FLAGS BIN 1

1597TABLE = SUBSCRIBER URC

1598FIELD = RECORD ID BIN 6 PK

1599FIELD = SUBSCRIBER ID LONG 1

1600FIELD = URC LONG 1

1601FIELD = FLAGS BIN 1

1602TABLE = TEAM MEMBER

1603FIELD = RECORD ID . BIN . 6 PK

1604FIELD = TEAM SUBSCRIBER ID : LONG : 1

1605FIELD = SUBSCRIBER ID LONG 1

1606FIELD = FLAGS . BIN : 1

1607TABLE = TECHNICIAN

1608FIELD = RECORD ID : BIN : 6 PK

1609FIELD = TECHNICIAN ID : LONG : 1

1610FIELD = NAME : BIN : 26

1611FIELD = PIN : SHORT : 1

1612FIELD = FLAGS : BIN : 1

1613TABLE = TECHNICIAN TERMINAL

1614FIELD = RECORD ID : BIN : 6 PK

1615FIELD = TECHNICIAN ID : LONG : 1

1616FIELD = TERMINAL ID : BIN : 6 FIELD = AUTHORIZATION FLAGS BIN

1617TABLE = TERMINAL

1618FIELD = RECORD ID BIN : 6 PK

1619FIELD = TERMINAL ID BIN 6

1620FIELD = LOCATION ID LONG 1

1621FIELD = LAN ADDRESS BIN 4

1622FIELD = FLAGS BIN : 1

1623FIELD = SERIAL NUMBER BIN 20

1624FIELD = HW CAPABILITIES BIN 10

1625FIELD = ATTRACT SCREEN LONG 1

1626FIELD = SYSTEM_FILESET_ID LONG 1

1627TABLE = TOURNAMENT

1628FIELD = RECORD ID BIN 6 PK

1629FIELD = TOURNAMENT ID LONG 1

1630FIELD = SHORT NAME BIN 28

1631FIELD = NAME BIN 72

1632FIELD = START DATE TIME LONG 1

1633FIELD = END DATE TIME LONG 1

1634FIELD = TOURNAMENT SCOPE BIN 1

1635FIELD = FLAGS BIN 1

1636FIELD = SPONSER BIN 40

1637FIELD = ICON LONG 1

1638FIELD = SPLASH SCREEN LONG 1

1639FIELD = PERCENT MONEY TO POOL BIN 1

1640FIELD = CURRENT POOL VALUE LONG 1

1641FIELD = PLAYS TO DATE LONG 1

1642FIELD = LAST_UPDATE_DATE_TIME : LONG . 1

1643TABLE = TOURNAMENT URC

1644FIELD = RECORD ID BIN 6 PK

1645FIELD = TOURNAMENT ID : LONG . 1

1646FIELD = URC : LONG : 1

1647FIELD = FLAGS : BIN : 1

1648TABLE = URC VALUE

1649FIELD = RECORD ID : BIN : 6 PK

1650FIELD = URC : LONG : 1

1651FIELD = RESTRICTED STRING : BIN : 30

1652FIELD = FLAGS : BIN : 1

1653# Working tables - not replicated from EDS server

1654TABLE W_AD_EXPOSURE FIELD RECORD_ID LONG 1 PK FIELD TARGET_ID LONG 1 FIELD SUBSCRIBER_ID LONG 1 FIELD PLAY DATE TIME LONG 1 TABLE = W AD EXPOSURE COUNTS

1655FIELD = RECORD ID LONG : 1 PK

1656FIELD = TARGET ID LONG 1

1657FIELD = TOTAL PLAYS TODAY SHORT : 1

1658FIELD = TOTAL_PLAYS_TO_DATE LONG : 1

1659TABLE = W CONTENT CACHE

1660FIELD = RECORD ID LONG 1 PK

1661FIELD = CONTENT ID LONG 1

1662FIELD = LOCAL PATH SIZE SHORT 1

1663FIELD — LOCAL_PATH VARBIN 1

1664TABLE ₌ W COUPONS ISSUED

1665FIELD = RECORD ID LONG 1 PK

1666FIELD = COUPON ID LONG 1

1667FIELD = RECEIPT ID BIN 6

1668FIELD = TERMINAL ID BIN 6

1669FIELD = SUBSCRIBER ID LONG 1

1670FIELD = ISSUE DATE TIME LONG 1

1671FIELD = FLAGS BIN 1

1672TABLE = W DOWN TIME

1673FIELD = RECORD ID LONG 1 PK

1674FIELD = START DATE TIME LONG 1

1675FIELD = END DATE TIME LONG 1

1676FIELD = TECHNICIAN_ID LONG 1

1677TABLE = W FILE CACHE

1678FIELD = RECORD ID LONG 1 PK

1679FIELD = FILE ID LONG 1

1680FIELD = LOCAL PATH SIZE SHORT 1

1681FIELD = LOCAL_PATH : VARBIN 1

1682TABLE = W LEADERBOARD

1683FIELD = RECORD ID : LONG : 1 PK

1684FIELD = LEADERBOARD ID LONG . 1

1685FIELD = LEADERBOARD DATE TIME : LONG : 1

1686FIELD = FLAGS : BIN : 1

1687FIELD = MAX_LEADERS SHORT 1

1688TABLE = W LEADERBOARD LEADER

1689FIELD = RECORD ID : LONG : 1 PK

1690FIELD = LEADERBOARD ID . LONG . 1

1691FIELD = SUBSCRIBER ID ; LONG : 1

1692FIELD = ALIAS : BIN : 26

1693FIELD = LOCATION NAME : BIN : 26

1694FIELD = LOCATION CITY STATE : BIN : 26

1695FIELD = PRIZE NAME : BIN : 26

1696FIELD = SCORE : LONG : 1 FIELD = SCORE DATE TIME LONG

1697TABLE = W LEADERBOARD RANKING

1698FIELD = RECORD ID LONG : 1 PK

1699FIELD = LEADERBOARD ID LONG 1

1700FIELD = RANK : SHORT : 1

1701FIELD ⁼⁼ SUBSCRIBER_ID LONG : 1

1702TABLE ₌ W LOCAL LEADERBOARD

1703FIELD = RECORD ID LONG : 1 PK

1704FIELD = LEADERBOARD ID LONG : 1

1705FIELD = LEADERBOARD DATE TIME LONG 1

1706FIELD = MAX_LEADERS SHORT 1

1707TABLE = W LOCAL LEADER

1708FIELD = RECORD ID LONG 1 PK

1709FIELD = LEADERBOARD ID LONG 1

1710FIELD = RANK SHORT 1

1711FIELD = SUBSCRIBER ID LONG 1

1712FIELD = ALIAS BIN 26

1713FIELD = SCORE LONG 1

1714FIELD = SCORE_DATE_TIME LONG 1

1715TABLE = W LOYALTY POINT AWARDS

1716FIELD = RECORD ID LONG 1 PK

1717FIELD = SUBSCRIBER ID LONG 1

1718FIELD = LOYALTY PROGRAM ID LONG 1

1719FIELD = POINTS AWARDED SHORT 1

1720FIELD = AWARD_DATE_TIME LONG 1

1721TABLE = W QUEUE

1722FIELD = RECORD ID LONG 1 PK

1723FIELD = TERMINAL ID BIN 6

1724FIELD = AGE SHORT 1

1725FIELD = QUEUE TIME LONG 1

1726FIELD = EVENT TYPE . BIN 1

1727FIELD = EVENT DATA SIZE : SHORT : 1

1728FIELD = EVENT_DATA VARBIN 1

1729TABLE = W REDEMPTION HISTORY

1730FIELD = RECORD ID : LONG : 1 PK

1731FIELD = REDEMPTION ID . LONG . 1

1732FIELD = TIMESTAMP : LONG : 1

1733FIELD = SCORE : LONG : 1

1734FIELD = PAR LEVEL PAID : BIN : 1

1735FIELD = SUBSCRIBER ID . LONG . 1

1736FIELD = CASH AMOUNT PAID : LONG : 1

1737TABLE = W REDEMPTION LOCAL POOL FIELD = RECORD ID LONG 1 PK

1738FIELD = REDEMPTION ID LONG 1

1739FIELD = LOCAL_POOL_VALUE LONG 1

1740TABLE = W REDEMPTION PAR LEVEL

1741FIELD = RECORD ID LONG 1 PK

1742FIELD = REDEMPTION ID LONG 1

1743FIELD = PAR LEVEL BIN 1

1744FIELD = ADJUSTED_PAR_ SCORE LONG 1

1745TABLE = W SERVICE ACCESSES

1746FIELD = RECORD ID LONG 1 PK

1747FIELD = SERVICE ID LONG 1

1748FIELD = PROFILE BIN 1

1749FIELD = START DATE TIME LONG 1

1750FIELD = END DATE TIME LONG 1

1751FIELD = SUBSCRIBER ID LONG 1

1752FIELD = CASH FUNDS USED LONG 1

1753FIELD = ACCOUNT_FUNDS_USED LONG 1

1754TABLE = W SERVICE LEADERBOARD .

FIELD — RECORD ID . LONG . 1 PK

1756FIELD = SERVICE ID LONG 1

1757FIELD = PROFILE BIN 1

1758FIELD = LEADERBOARD_ID LONG : 1

1759TABLE = W TOURNAMENT LOCAL POOL

1760FIELD = RECORD ID : LONG : 1 PK

1761FIELD = TOURNAMENT ID : LONG : 1

1762FIELD = LOCAL POOL VALUE LONG 1