EP3516635B1

Bill validation and cash dispensing device, system and method for use in a casino context

Abstract

This record has no abstract on file.

EP3516635B1, drawing sheet 1
Sheet 1 of 10

Term

10.5 yearsleft in the term

Expires 7 April 2037.

  1. Priority and filed
  2. Granted
  3. Today
  4. Expires

5 claims: 1 independent, 4 dependent

  1. 1
    A system (100, 400) for providing premium features to a player of an electronic gaming machine (102, 402) configured to provide at least one gaming experience to the player in a casino environment; the system (100, 400) comprising:a peripheral controller (104) communicatively coupled to the electronic gaming machine (102, 402);a printer (106) that has a primary printer port (110) communicatively coupled with the electronic gaming machine (102, 402) to configure the printer to provide at least one basic printing service to the player and a secondary printer port (111) communicatively coupled with a printer driver application to configure the printer (106) to provide at least one premium printing service to the player;a validator (108) that has a primary validator port (112) communicatively coupled with the electronic gaming machine (102, 402) to configure the validator (108) to provide at least one basic validation service to the player and a secondary validator port (113) communicatively coupled with a validator driver application to configure the validator (108) to provide at least one premium validation service to the player;a casino management system server (404b) configured to manage granting and redeeming of player points;an Enhanced Services system server (404a) configured to license and manage the providing of the at least one premium printing service and the at least one premium validation service to the player;a validator enablement protocol invoked responsive to communications between the validator (108) and the Enhanced Services system server, the validator enablement protocol comprising: - a "BlobRequired" message (602) being communicated from the validator (108) to the validator driver application, - periodically thereafter, the validator (108) sending a "BlobReady" message, where the "BlobReady" status indicates that the validator (108) needs to exchange a data blob with the Enhanced Services system server, - the validator driver application determining whether a current, valid blob is available, and if a valid blob is available, transmitting the valid blob to the validator (108) in a message (604), - the validator (108) then transmitting the blob per message (606) to the validator driver application whenever use of a premium feature is to be provided, - the validator driver application then appending to the blob message (606) information that uniquely identifies the validator (108) providing the blob and communicating this modified message (608) to the Enhanced Services application executing on the Enhanced Services system server, - the Enhanced Services application then determining whether the received modified message (608) identifies a validator (108) that is then currently licensed to provide the requested premium feature(s), and if so, communicating an acknowledgement message (610) from the Enhanced Services application to the validator driver application, - the validator driver application then communicating a "Xmit Blob" message (612) to the validator (108), the "Xmit Blob" message (612) includes a blob received from the Enhanced Services application and a second blob provided by the validator driver application itself, those two blobs representing two levels of authorizations required to enable premium features on the validator (108) with a first of such levels of authorization being provided by the Enhanced Services application and the second of such levels of authorization being provided by the validator driver application, and - the validator (108) communicating an acknowledgement message (614) to the validator driver application and periodically thereafter communicating an "idle" status message (616) to the validator driver application, where the "idle" message indicates that the validator (108) is enabled and ready to accept tickets;a first network (116, 406) communicatively interconnecting each of the peripheral controller (104), the casino management system server (404b) and the Enhanced Services system server (404a);at least one third party server (410a - 410n) providing a premium feature;and at least one second network (130, 408) communicatively interconnecting at least one of the casino management system server (404b) and the Enhanced Services system server (404a) with the at least one third party server (410a - 410n);wherein a casino exclusively utilizes the first network (116, 406) to physically and logically close the first network (116, 406) by firewalls and closed data ports or to seal it partially to wholly to the transmission and/or reception of external data communications.