Patent Grant
11967201
The described embodiments relate generally to gaming systems, such as gaming systems deployed in a casino enterprise. More particularly, apparatus and method for moving value on and off of an electronic gaming machine are described.
An electronic gaming machine (EGM) that is configured to provide a wager-based game can be likened to a combination of an automatic teller machine and a home gaming console. The automatic teller machine aspect relates to the cash handling capabilities of the EGM which allow it to securely receive, store and dispense cash or an indicia of credit redeemable for cash. The home gaming console aspect relates to the game generation capabilities of the EGM, which allow it to generate and display games that are entertaining to a user of the EGM.
To provide cash handling capabilities, a common configuration for an EGM, such as a video slot machine or mechanical slot machine, is to include a bill validator and a ticket printer. The bill validator is configured to accept and validate cash currency and ticket vouchers where the ticket vouchers are bearer instruments redeemable for cash or game play on an EGM. Accepted cash or ticket vouchers can be converted to credits that are used to make wagers on the EGM. The accepted tickets are stored within a cash box secured within a locked EGM cabinet. When a player wishes to leave and has credits remaining on the EGM, the credits are converted to a cash value and are output as a ticket voucher via the printer where the cash value is typically printed on the ticket. The printed ticket voucher can be used to add credits to another EGM or the printed ticket voucher can be redeemed for its cash value.
Significant labor costs result from using a bill validator and a ticket printer on an EGM. The labor costs involve periodically removing a cash box including received tickets and cash from the EGM and replacing it with an empty one, counting the cash and tickets removed from the EGM and refilling the ticket stacks on the EGM. Other cash handling configurations also involve similar labor costs. For instance, EGMs can include coin acceptors and coin dispensers. The use of these devices requires periodically removing coins or adding coins to the EGM. Then, the coins retrieved from each EGM are counted on an EGM by EGM basis.
For security purposes, a technician and one or more security providers are typically involved in operations where cash is removed from an EGM. The security providers make sure the cash is retrieved and transported without theft. Further, since removing cash requires the EGM cabinet to be opened, the security providers observe the operation to make sure that tampering doesn't occur with the EGM hardware. An individual might wish to tamper with an EGM to get it to award jackpots, receive cash or dispense cash in an unintended manner. The removed cash is transported to a secure area where additional individuals are involved in counting and recording the various sums of cash and/or ticket vouchers removed from each EGM. The cash amounts removed from each EGM are reconciled with other information sources, such as from hard meters on the EGM or records from a server that generates and validates ticket vouchers. The reconciliation process is important for ensuring the earnings from the EGM are properly taxed.
Gaming enterprises operating electronic gaming machines are always looking for ways of reducing labor costs. In view of the above, new methods of cash handling are desired that reduce the labor costs associated with operating EGMs.
A gaming system compatible with patron-controlled portable electronic devices, such as smart phones and tablet computers, is described. The gaming system can include gaming devices, such as electronic gaming machines and system servers. The portable electronic devices can be configured to store and transmit virtual ticket voucher information to an EGM or a redemption kiosk and receive a virtual ticket voucher issued from the EGM. The EGM can include one or more wireless interfaces and can be configured to communicate using one more different wireless communication protocols. The wireless interface communication interfaces and wireless communication protocol capabilities can enable communications with the portable electronic devices. In a particular embodiment, the EGM can include a wireless interface compatible with a near-field wireless communication protocol.
In a particular embodiment, an EGM can be configured to redeem and issue both virtual ticket vouchers and printed ticket vouchers. The virtual ticket vouchers can be redeemed on other EGMs for credits used to place wagers on a game of chance generated or can be redeemed at a redemption kiosk for cash. The virtual ticket vouchers can be stored on a patron-controlled portable electronic device. In one embodiment, the virtual ticket vouchers can be compatible with existing cashless voucher handling systems that provide for the issuance and redemption of printed ticket vouchers. Thus, the cashless voucher handling system can be configured to provide for the validation, redemption and issuance of both printed ticket vouchers and virtual ticket vouchers.
On aspect of the embodiments described herein is related to computer readable medium for tangibly storing a computer program used by a processor on a portable electronic device. The computer readable medium can include 1) computer code for communicating with a wager-based electronic gaming machine (EGM) via a wireless interface on the portable electronic; 2) computer code for storing a virtual ticket voucher wherein the virtual ticket voucher is a bearer instrument redeemable only once for cash or wagering credits on the EGM; 3) computer code for receiving the virtual ticket voucher from the EGM via the wireless ticket interface; 4) computer code for rendering an image of at least a front side of the virtual ticket voucher to a display wherein the image is rendered in a format similar to a printed ticket voucher issued by the EGM; and 5) computer code for sending the virtual ticket voucher to the EGM via the wireless interface.
Another aspect of the embodiments described herein is related to a method on a server. The method can be generally characterized as including a method in a server including a processor, a memory and a network interface. The method can be generally characterized as including 1) establishing communications with a portable electronic device via the network interface; 2) receiving a request from the portable electronic device to generate a virtual ticket voucher redeemable for game play at a casino; 3) receiving an electronic payment for the virtual ticket voucher; 4) sending a request a remote server at the casino to send a ticket validation number including a value of the virtual ticket voucher; 5) receiving the ticket validation number; 6) generating the virtual ticket voucher; 7) sending the virtual ticket voucher to the portable electronic device and 8) notifying the remote server that the virtual ticket voucher has been generated.
The embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:
In the following paper, numerous specific details are set forth to provide a thorough understanding of the concepts underlying the described embodiments. It will be apparent, however, to one skilled in the art that the described embodiments may be practiced without some or all of these specific details. In other instances, well known process steps have not been described in detail in order to avoid unnecessarily obscuring the underlying concepts.
A gaming system compatible with portable electronic devices controlled by users of the gaming system is described. In one embodiment, the portable electronic devices can be configured to store and transmit virtual ticket voucher information to an EGM or a redemption kiosk and receive virtual ticket voucher information associated with a virtual ticket voucher issued from the EGM. The virtual ticket vouchers can be redeemed on the EGM for credits used to place wagers on a game of chance or can be redeemed for cash at a redemption kiosk. The EGM can be configured to issue virtual ticket vouchers to transfer credits from the EGM. In one embodiment, the virtual ticket vouchers can be made compatible with existing cashless handling systems that provide for the issuance and redemption of printed ticket vouchers with little modification to the existing cashless handling system. Thus, the cashless system can be configured to provide for the validation, redemption and issuance of both printed ticket vouchers and virtual ticket vouchers.
With respect to the following figures, methods and apparatus that allow a cashless system to include virtual ticket vouchers is described. In particular, with respect to
External Interface and EGM-Portable Device Interactions
On the EGM, the communication with the portable electronic device can occur through a wireless or a wired interface. In various embodiments, for the purposes of communicating with a portable electronic device, the EGM 2 can configured with a single wireless interface but no wired interfaces, multiple wireless interfaces but no wired interfaces, a single wired interface but no wireless interfaces, multiple wired interfaces but no wireless interfaces or a combination of wireless and wired interfaces. Thus, the communication interfaces described with respect to
In a particular embodiment, one or more of the wired or wireless interfaces can be dedicated to operator functions and may only recognize particular devices carried by an operator. For instance, a wireless interface can be dedicated to allowing an operator perform maintenance functions, such as receiving diagnostic information from the EGM. In another example, a wireless interface can be dedicated towards performing operator functions, such as placing the EGM in a dispute resolution mode, a hand-pay mode or a W-2 (tax requirement) mode. Again, the EGM can be configured to recognize particular operator registered devices via this interface. In yet another example, a wireless interface can dedicated only to premium customers. Via the dedicated wireless interface and their portable electronic device, a premium customer may be able to access to certain functions on the EGM that are not available to other customers.
As will be discussed in more detail below, one or more of the wireless or wired interface can be used for transactions involving cash handling on the EGM 2. An interface can be dedicated for this purpose. For instance, a dedicated cash handling interface can be configured only to receive information associated with cash handling. In other embodiments, a wired or wireless interface on the EGM can be used for cash handling transactions with the portable electronic device as well as more general communications, such as transferring information that can be used in a loyalty program or a social media application.
As follows, the EGM 2 is briefly described and then cash handling interactions involving a portable electronic device 34, the EGM 2 and gaming system server 10 are discussed. Additional details of the EGM are described with respect to
The EGM 2 can include a number of devices used in cash handling transactions. The cash handling devices can include 1) a bill acceptor 22 configured to accept cash and/or ticket vouchers, a printer 38 configured to generate printed ticket vouchers and 3) a card reader 36 which can be configured to read a magnetic striped card or a smart card. The magnetic striped card or the smart card can be used to transfer funds, such as funds stored on a debit card. Further, the card reader 36 can be used to read account information associated with a loyalty program account.
In a particular embodiment, a wireless interface 18 can be configured to receive information, such as information associated with a virtual ticket voucher, from a portable electronic device 34. As an example, the wireless interface 18 can be configured to implement a near field communication (NFC) protocol. The NFC protocol is designed with a communication range of 4 cm or less. NFC operates at 13.56 MHz on ISO/IEC 18000-3 air interface and at rates ranging from 106 kbit/s to 848 kbit/s. NFC can involve an initiator and a target. The initiator actively generates an RF field that can power a passive target. This enables NFC targets to take very simple form factors such as tags, stickers, key fobs, or cards that do not require batteries. NFC peer-to-peer communication is of course possible, where both devices are powered. For instance, the electronic device 34 and EGM 2 can be configured to implement a peer-to-peer communication.
Wireless interface 18 can be also used to accept information from a digital wallet application, such an E-wallet application. E-wallets can store passwords, credit card numbers, email contacts and identification data like driver's license or social security numbers. In some instances, an E-wallet can be linked to a bank account. In the embodiments described herein, an E-wallet application can be used to transfer “cash” electronically to an EGM that can be used for wagers. When funds are received electronically, such as via an E-wallet transaction, the EGM 2 can be configured to store an electronic record of the transaction in a manner similar to cash transactions involving physical currency.
As is discussed in more detail with respect to
In particular embodiments, the portable electronic device 34 can be configured with an application that manages virtual ticket vouchers that are redeemable for game play. On the gaming system side, the virtual ticket vouchers can be generated in a manner similar to printed ticket vouchers. With printed ticket voucher, a gaming system server, such as 10, can be configured to generate and store a validation number associated with a particular amount of cash or credits. The validation number and the amount associated with the validation number can be stored in a ticket voucher database. The validation number and the amount associated with the validation are stored so that when the ticket voucher is later presented for redemption it can be validated. The validation can be performed by the gaming system server or another device in the gaming system.
Next, the gaming system server can send information that allows the validation number to be located in the ticket voucher database to the EGM 2. Via the printer 38, the information that allows the ticket voucher to be located in the ticket voucher database and the amount associated with the ticket voucher can be printed on a blank ticket voucher and then output. The information can be printed in different formats, such as in a text format and/or in a symbol format, such as a bar-code. Later, to redeem the ticket, information stored on the printed ticket voucher can be read and parsed at an EGM, a redemption kiosk or a cashier station. The information read from the ticket can be compared to information stored in server 10 when the ticket voucher was created. If the server determines information matches and the ticket voucher hasn't be previously redeemed, then the ticket voucher can be redeemed for cash or additional game play.
Similar to a printed ticket voucher, to generate a virtual ticket voucher, the EGM 2 can send a request to server 10 to generate a unique identification number for a cash amount to be transferred off of the EGM 2. Alternatively, the EGM 2 or some other device can generate the unique identification number that is sent to sever 2. The gaming system server can store the identification number and the cash amount associated with the ticket as well as the unique information associated with the EGM 2. The unique EGM information can be later used for reconciliation purposes. Then, the unique identification number can be sent to the EGM 2.
As described above, the virtual ticket vouchers and printed ticket vouchers can be generated in the same manner and with little modification to an existing cashless system. However, there are some possible differences as described as follows. One difference can be that the server 10 is configured to record whether the ticket voucher is issued as a printed ticket or a virtual ticket. Printed ticket vouchers can include an identification number, such as xx-xxxxxx-xx. The identification number can be modified to indicate whether it is associated with a virtual ticket voucher or a printed ticket voucher. For instance, 01-xxxxxx-xx can be used for printed ticket vouchers while 02-xxxxxx-xx can be used for virtual ticket vouchers.
A determination of whether the ticket voucher is generated as a virtual ticket voucher or printed ticket voucher can occur on the EGM 2. A default position of the EGM 2 can be to generate a printed ticket voucher if a requested virtual ticket voucher is not successfully generated. For instance, as is described in more detail below, can request a virtual ticket voucher accidently, cancel it and request a printed ticket voucher. Thus, an indication of whether the requested virtual ticket voucher is issued as virtual ticket or a printed ticket voucher can be received at the server in an acknowledgement the EGM 2 and the server can change the format in which the ticket voucher has been issued if it has changed.
Denoting whether the ticket voucher is a printed or a virtual ticket voucher can be important for record keeping purposes. In the case of a redeemed printed ticket voucher, it is expected that there will be a corresponding piece of paper when the ticket is redeemed. For virtual printed tickets, there may not be such a record. For instance, when a printed ticket is redeemed at an EGM, it is expected that when the cash box is subsequently removed from the EGM, the cash box includes the printed ticket. The presence or non-presence of the printed ticket can be identified in a soft count when the cash in the cash box is counted.
A soft count is one process for counting banknotes in a casino or bank. The soft count rooms are usually among the most secure places due to the large amounts of cash that can be on hand at any one time. The counting is usually done by accounting professionals called soft counters, using computer spreadsheets. Typically, a soft count room contains a large table upon which the currency to be counted is placed, known as the “count table”. Count room personnel manually organize the currency so that it can be easily counted by hand or by a counting machine. Most modern count rooms are equipped with high-speed computerized machines that perform the counting process.
In a particular embodiment, the cash box on the EGM 2 can be equipped with a memory. Virtual ticket voucher information can be loaded to the memory as virtual ticket voucher information tickets are redeemed at the EGM 2. The bill acceptor or the EGM 2 can be configured to transfer this information to the memory. The memory may also include a record of the printed ticket vouchers received into the cash box. Further, it can include a combined transaction list including cash transactions, printed ticketed transaction and virtual ticket transactions in the order in which they were generated. When the cash box is removed and the bills and printed ticket vouchers are counted, the memory on the cash box can be interrogated for virtual ticket voucher information and other transaction information, if it is stored, as part of the soft count process. Thus, the cash box can have a complete record of cash and ticket vouchers accepted at the EGM 2 where a portion of the ticket vouchers can be printed ticket vouchers and a portion of the ticket vouchers can be virtual ticket vouchers stored electronically.
If desired, equivalent printed vouchers can be generated from the virtual ticket voucher information to be used as part of the soft count process from the information stored in the cash box. For instance, the cash box can be connected to a printer where sheets including one or of the virtual ticket vouchers can be generated. For example, 4 ticket vouchers per sheet or 8 ticket vouchers per sheet can be generated. The virtual ticket vouchers can be output in a format similar to a printed ticket voucher, such as including a bar-code and other information normally included on a printed ticket. The printed sheets including virtual ticket information can be stored for some time period for auditing purposes.
In one embodiment, the virtual ticket voucher can be created in response to receiving an input from the E-cash out button 26. After the E-cash out button activation is detected, if credits remain on the EGM 2, the EGM 2 can be configured to send the request for the unique validation number and cash amount for the voucher to server 10 via connection 12. In response, the EGM 2 can receive the unique validation number from the server 10. Based upon the information received from the server, the EGM can generate a virtual ticket voucher.
In one embodiment, an image of the virtual ticket voucher can be generated and output to a display on the EGM 2, such as 14 and 16. As an example, an image of a virtual ticket voucher 40 is shown. The front of the virtual ticket voucher can be displayed or the front and back of the virtual ticket voucher can be displayed. In one embodiment, a virtual ticket voucher that is displayed can be formatted in the same manner as a printed ticket voucher, such that it looks like a printed ticket voucher. For instance, the front of the printed ticket voucher might include a bar-code, a cash value, a location where it was issued, a unique identification number. The back of the ticket can include a disclaimer such as,
To prevent someone from taking a picture of the displayed image and converting it to a virtual ticket voucher and trying to redeem, a portion of information needed to redeem the virtual ticket voucher may not be displayed. For instance, a second unique validation number can be transmitted from the EGM 2 to the portable electronic device 34 that is needed to redeem the ticket. This second unique validation number may not be rendered in the image of the virtual ticket voucher displayed on the EGM 2. Besides, ticket information, such as a second unique validation number, data can be sent to the portable electronic device that allows an image of virtual ticket voucher rendered on EGM 2 to also be rendered on the user's portable electronic device.
The format of the images of the virtual ticket voucher can vary from gaming enterprise to gaming enterprise and can further vary from location to location within the gaming enterprise. Further, the format of the virtual ticket images can vary from EGM 2 to EGM 2 within a location if the print capabilities in each EGM are different such that it affects the format of the printed ticket voucher that is output. In other embodiments, the generated virtual ticket voucher image displayed on EGM 2 can be different from printed ticket vouchers. For instance, the system can be configured to allow a user to select a custom format for their virtual ticket vouchers. The EGM 2 can be configured to generate and display a custom formatted virtual ticket voucher to the display.
In one embodiment, the custom format virtual ticket voucher information can be stored on their portable electronic device 34 and transmitted to the EGM 2, such as via a wireless or wired communication connect between device 34 and EGM 2. As another example, the custom format virtual ticket voucher information can be stored in a loyalty program account on a gaming system server. This information can be retrieved when the user provides loyalty program account information to the EGM 2. In another embodiment, the images of the virtual ticket vouchers that are displayed on the EGM 2 can be a standard format, such as to match the format of the printed ticket vouchers issued at the EGM 2. The virtual ticket voucher information can be transmitted to the user's portable electronic device. Then, via an application running on the user's portable electronic device 34, the user can select a custom format to display the virtual ticket voucher. In yet other embodiments, the images of the virtual ticket voucher can be selected to match a theme of the game or reflect a theme associated with a calendar event, such as a holiday them.
In alternate embodiments, an image of the virtual ticket voucher doesn't have to be displayed. For instance, a message might be output to display 16 of “please retrieve your virtual ticket voucher for X dollars” but an image of the virtual ticket voucher may not be generated. In another example, a bezel 20 around interface 18 may light-up in a particular color and/or flash with a particular light pattern to indicate the virtual ticket voucher is ready. In other embodiments, a combination of a message, an image of the virtual ticket voucher and/or a lighted bezel can be used. For instance, a formatted virtual ticket voucher can be output can be output to display 16 with a message and the bezel 20 can change state to indicate that the virtual ticket voucher is ready.
When the virtual ticket voucher is ready, the EGM 2 can indicate it is ready to transfer the virtual voucher, such as via changing bezel state 20. In response, when a NFC protocol is used, the portable electronic device 34 can be brought in proximity to even in contact with the outer surface of interface 18. In one embodiment, for security purposes, a virtual ticket voucher application executed on the portable electronic 34 may have to be active for a transaction to take place, i.e., for the portable electronic device 34 to receive virtual ticket voucher information from the EGM 2. Similarly, as is described in more detail below, the virtual ticket voucher may have to be active on the portable electronic device 34 to transmit virtual ticket voucher information stored on the portable electronic device 34 to the EGM 2.
If another wireless protocol with a longer range is utilized or a wired connection is utilized, it may not be necessary for the portable electronic device to be placed in close proximity to interface 18. In response to receiving virtual ticket voucher information from the EGM 2, information about the virtual ticket voucher can be output on the display 32 of the portable electronic device 32. The information that is output to display 32 can be selected to match the format of information output to display 16 on the EGM 2. For instance, if a virtual ticket voucher image is output to display 16, then the virtual voucher image can also appear on the user's device after the transfer of information. With virtual ticket voucher information simultaneously output on both displays, the user can compare the images on the display 32 and the EGM 2 to visually confirm the successful transfer.
When the virtual ticket voucher is ready and the interface 18 and optionally the bezel 20 have been activated, the EGM 2 may begin a countdown timer. If a successful transfer is not made to a portable electronic device, such as 34, within the time period associated with the countdown timer, the EGM 2 can convert the virtual ticket voucher transaction to a printed ticket voucher transaction and generate a printed ticket that is output via the printer 38. If the type of voucher (virtual or printed) is indicated by the identification number on the ticket, then the EGM 2 can be configured to alter the identification number that is printed on the printed ticket voucher so that it now reflects a number that is consistent with a printed ticket voucher. In addition, the EGM 2 can contact the server 10 to notify in the change in format and number for the voucher and the server 10 can store this information. In one embodiment, a cancel button can be provided on the EGM 2 that switches a cash out transaction from a virtual ticket voucher to a printed ticket voucher.
A virtual ticket voucher transaction may time out or a user may wish to cancel a virtual ticket voucher for a number a reasons. For instance, the user may cancel because they realize they have forgotten or lost their phone. In another example, the user may have requested a virtual ticket transaction accidently, such as by hitting the E-cash out button instead of the cash out button. In another example, their portable electronic device 34 may have run out of charge or may not be functioning properly. In yet another example, the interface 18 may not be functioning properly, the user's portable electronic device may not be functioning properly or a combination of problems with the interface 18 or the user's portable electronic device may prevent the transaction from occurring.
After the virtual ticket voucher is transferred to the user's portable electronic device, an application executing on the portable electronic device can be executed that allows the user to manage their virtual ticket vouchers. For instance, as mentioned above, the application may allow the user to customize the appearance of the virtual ticket voucher in the application. In another example, the application can be configured to keep track of when printed ticket vouchers have been received and an expiration date of the ticket. The application can be configured to notify the user if a virtual ticket voucher is nearing its expiration date. In yet another example, the application can be configured to exchange information with an E-wallet application or can include E-wallet functionality. In a further example, virtual ticket voucher information can be stored in the “cloud,” i.e. remote distributed storage, and the application can be configured to access and retrieve virtual ticket voucher information stored in the “cloud.” Further details of this application are described with respect to
When information is transferred wirelessly between the EGM 2 and the portable electronic device, the EGM 2 can be configured to receive and store unique device identification information associated with portable electronic device. Further, the portable electronic device can be configured to receive and store information associated with the EGM 2. The EGM 2 can be configured to associate the unique device identification information with the virtual ticket voucher that was issued. The unique portable device identification information can be stored on the EGM 2 and also sent to a validation server, such as server 10, where it can also be associated with the virtual ticket voucher information that was generated.
In one embodiment, as a requirement or optionally if the user desires, the unique portable device identification information can be used in the redemption of the virtual ticket voucher. When the virtual ticket voucher is presented at a redemption device, such as EGM 2, the unique identification information associated with the portable electronic device and the unique identification information associated with the virtual ticket voucher can be received at the redemption device and transmitted to a validation device, such as server 10. Then, the validation device can compare the received virtual ticket voucher information and portable electronic device identification information to the virtual ticket voucher information and portable device information stored when the virtual ticket voucher was issued. If unique player identification information is known, such as information associated with a loyalty program, then this information can also be included in the validation process.
When the information matches, then the validation device can send a message to the redemption device to redeem the virtual ticket voucher at the amount associated with the virtual ticket voucher. If the portable electronic device information matches and the virtual ticket voucher has already been redeemed, then the validation device can send a message to the redemption device including this information. In response, the redemption device can display a message, such as ticket previously redeemed. If the portable device information doesn't match but the virtual ticket voucher information matches, the validation device can send a message to the redemption device regarding this state. In response, in one embodiment, the redemption device can display a message, such as “Virtual ticket voucher is invalid” or “Device information is invalid go to the cashier station to redeem the ticket.” At the cashier station, the user may have to present identification information to redeem the virtual ticket voucher that is stored on the portable electronic device with unique device identification information that doesn't match the portable electronic device to which the ticket voucher was issued. If the virtual ticket voucher information doesn't match any of the records on the validation device, then the validation device can send a message indicating this state to the redemption device. In response, the redemption device can display a message, such as “ticket voucher invalid.”
The portable electronic device information received that is gathered during an issuance of a virtual ticket voucher or the redemption of a virtual ticket voucher can be used in a dispute resolution process. A patron may decide that an amount of a virtual ticket voucher transmitted from the EGM 2 to the portable electronic device 34 is incorrect or an amount of a virtual ticket voucher transmitted from the portable electronic device 34 to the EGM 2 is incorrect. In response, the player may request the presence of an operator. The operator can place the EGM 2 in a dispute resolution mode where a record of virtual vouchers issued from the EGM 2 or accepted on the EGM 2 can be accessed.
The dispute resolution mode may allow information regarding virtual ticket vouchers issued or accepted at the EGM 2 to be retrieved from memory and displayed on the EGM 2. The operator may be able scroll the ticket voucher records in order of acceptance or issuance. In one embodiment, a player may be able to couple their portable electronic device 34 to the interface 18. In response, the EGM 2 can be configured to search the stored ticket voucher records and display information regarding any virtual ticket vouchers issued to the portable electronic device 34 or received from the portable electronic device 34. In one embodiment, the EGM 2 can be configured to reissue a virtual ticket voucher to the portable electronic device, such as if the player convinces the operator that the information regarding a virtual ticket voucher issued to the portable electronic device has been lost for some reason.
In other embodiments, virtual ticket voucher information can be accessed via a secondary device, such as a player tracking unit or via a “service window” on the EGM 2. For instance, an electronic log of virtual voucher activity and/or virtual cash activities can be stored on a remote host which can be accessible via a service window on the EGM 2. Further details of service windows applications are described below with respect to
As described above, the redemption of virtual ticket voucher stored on a portable electronic device, such as 34, can involve transferring virtual ticket voucher information from the portable electronic device 34 to a redemption device, such as EGM 2. On EGM 2, the cash value associated with the virtual ticket voucher can be converted to credits where the credits can be used for wagers on a game of chance. In one embodiment, the virtual ticket voucher transfer from device 34 to EGM 2 can be initiated when the EGM 2 detects an actuation of the E-cash-in button 24.
In a particular embodiment, restricted credits can be transferred to the EGM 2 via a virtual ticket voucher. For instance, restricted credits can be transferred to the EGM 2 that are available for wagers but can't be redeemed for cash. In other embodiments, a virtual ticket voucher can be redeemed to unlock a feature on the EGM 2, such as a particular bonus mode. In yet other embodiments, a virtual ticket voucher can be used to transfer information associated with persistent gaming, such as progress or achievements a player has previously obtained playing a game. In other embodiments, a virtual ticket voucher can be used to 1) transfer tax information associated with an EGM pay out, such as a W2G receipt, 2) report metering information associated with the EGM 2 and 3) report diagnostic information associated with the EGM 2, such as when the EGM is not functioning properly.
In response to detecting the actuation of button 24, the EGM 2 can change the state of interface 18 so that it is enabled to receive an information transfer from a portable electronic device, such as 34. Further, the change in state of the interface 18 can be indicated by a change in state of a status indicator associated with interface 18. For instance, a bezel 20 surrounding the interface 18 can be lit up with a particular color and/or light pattern to indicate the interface 18 is ready to receive virtual ticket voucher information. Further, if enabled, a sound pattern can be emitted from the status indicator to indicate it is ready to receive virtual ticket voucher information from a portable electronic device.
In a particular embodiment, when interface 18 is activated a countdown time can be started. If the countdown timer reaches a termination value, such a zero, before a communication is established with a portable electronic device, then the interface 18 can be turned off and the status indicator associated with interface 18 can be changed to indicate it is not ready to receive information. For instance, the bezel 20 surrounding the interface can be lit up with a particular light patter and/or color to indicate a transition state. In addition, the status indicator can be configured to indicate the transition from an on state to and off state is about to occur. For instance, the bezel 20 can change to a particular color and flash at an increasing rate before the interface 18 is turned off. A particular sound pattern can also be emitted to indicate the transition.
In other embodiments, the interface 18 can be configured to support an active communication session between the portable electronic device and the interface 18. For instance, interface 18 can support NFC communications and Bluetooth™ communications. A user can tap a NFC and Bluetooth™ enabled device to the interface 18. The tap can transmit, via NFC, data which allows a Bluetooth™ communication pairing to be set up between the portable electronic device and the EGM 2. The communication pairing can utilize encrypted communications. The status indicator 19 can be used to indicate whether the communication pairing is active or not between the portable electronic device and the EGM 2.
In one embodiment, the application that allows the transfer of the virtual ticket voucher from the portable electronic device to the EGM 2 may have to be active on the portable electronic device 34 before a transfer can occur. Further, a secondary authentication method, such as entering a PIN correctly, may be required on the portable electronic device 34 before the transfer is allowed to occur. In one embodiment, the use of a secondary authentication method can be triggered based upon an amount of the ticket voucher that is to be redeemed such that vouchers above a certain amount require a secondary authentication while vouchers below a certain amount do not require a secondary authentication.
During the redemption process, an image of the virtual ticket voucher that is to be redeemed can be displayed on the display 32 of the portable electronic device 34. When the virtual ticket voucher information is successfully transmitted to EGM 2, it can be displayed on the EGM 2, such as in an image of a ticket voucher 40. Then, the user can compare the virtual ticket voucher information displayed on the display 32 to the virtual ticket voucher information displayed on display 16 or some other display on the EGM 2.
In one embodiment, an image data associated with a virtual ticket voucher and/or formatting information can be transmitted from the portable electronic device 34 to the EGM 2 so that the image rendered on the EGM 2 appears similar to the image rendered on portable electronic device 34. As an example, as described above, an application running on portable electronic device 34 can be configured to allow a user to customize the appearance of virtual ticket vouchers displayed on their device. Thus, some of the custom formatting information related to the virtual ticket voucher appearance can be transferred from the portable electronic device to the EGM.
In another embodiment, the image rendered of a virtual ticket voucher can be a standard format that is not affected by formatting information received from the portable electronic. As described above, the only front of the virtual ticket voucher or the front and back of the virtual ticket voucher can be rendered on a display on the EGM 2. In addition as described above, an image of the virtual ticket voucher doesn't have to be rendered on the EGM 2. For instance, when a virtual ticket voucher is accepted, the EGM 2 can be configured to display a message such as “virtual ticket voucher for x dollars received” where “x” is the amount associated with the ticket.
After the virtual ticket voucher is successfully received, the EGM 2 can send received virtual ticket information to a validation device, such as gaming system server 10. The validation device can determine whether the information associated with the virtual ticket voucher is associated with a valid virtual ticket voucher that hasn't already been redeemed. When the information is valid, the validation device can send a message to the redemption device, such as EGM 2, to redeem the virtual ticket voucher for an amount that the validation server determines is associated with the virtual ticket voucher.
The redemption device can receive the message from the validation device and in response, redeem the ticket in some manner For instance, in the case of the EGM 2, the ticket can be redeemed for credits. As another example, a redemption kiosk, in response to receiving a validation message can dispense the cash amount associated with the virtual ticket voucher. After redeeming the virtual ticket voucher, the redemption device can send a message to the validation device indicating it has successfully redeemed the virtual ticket voucher. In response, the validation device can store information indicating the virtual ticket voucher has been redeemed. Thus, if the person controlling the portable electronic device attempts to redeem the virtual ticket voucher again, the validation device can be configured to indicate the transaction is invalid because the virtual ticket voucher has been previously redeemed. The redemption device, such as EGM 2, can be configured to store information regarding the virtual ticket voucher that has been received and optionally unique device identification information from the portable electronic device that transmitted the virtual ticket voucher information to the redemption device. The redemption device can also be configured to send the portable electronic device information to a remote device, such as server 10.
There are a number of potential advantages of providing virtual ticket voucher functionality on an EGM. In the case of virtual ticket voucher issuance, one advantage is that the stack of blank tickets used to generate printed ticket vouchers may have to be refilled less frequently. This reduces the material costs associated with purchasing tickets and the labor costs associated with refilling the blank ticket stack because the rate at which printed tickets are generated is reduced. Further, it is better for the environment since less paper is used. In the case of virtual ticket voucher redemption, one advantage is that the cash box associated with the bill/ticket acceptor may fill up more slowly. Thus, the labor costs associated with removing and replacing a full cash box can be reduced since the cash box will fill up more slowly. Further, the soft count process can be simplified reducing labor costs because less printed tickets need to be handled during the soft count process.
Internal Device Control
Next details of internal configurations of an EGM configured to redeem and/or issue virtual ticket vouchers are described. With respect to
The EGM 2 is coupled to a validation server 68 and an accounting server 70 via a network interface 56. The validation server 68 can be configured to 1) generate validation numbers for printed and virtual ticket vouchers issued at EGM 2 and 2) validate virtual ticket and printed ticket vouchers received at the EGM 2. The validation server 68 can be part of a cashless system. The accounting server 70 can be configured to receive accounting information, such as coin-in/coin-out, from the EGM 2. The accounting server 70 can be part of a loyalty program system where members can earn points redeemable for comps based upon their game play. In one embodiment, the network interface 56 can be a smart interface board (SMIB) associated with a player tracking system.
The virtual ticket voucher processing, involving such steps as validation, redemption and issuance of virtual ticket vouchers described above with respect to
Virtual ticket voucher information can be transmitted and received via the wireless interface 18. In one embodiment, the wireless interface 18 can be integrated into the cabinet of the EGM 2 (e.g., see
In the embodiments where the wireless interface is embedded in a secondary device, such as a printer or a player tracking unit, the game controller 50 can optionally communicate via the wireless interface and send control commands to control the wireless interface via a secondary controller, such as printer controller or a player tracking controller. For instance, the game controller 50 can detect an actuation of the E-cash out button 26 and then send a command to the secondary device including the wireless interface to turn on the wireless interface. In the secondary device, a secondary device controller can simple forward the command to the wireless interface 18, which can be configured to respond to the command from the game controller 50. In another example, the secondary device controller can be configured to interpret the command received by the game controller 50 where the command received by the game controller can be at a high level and not understood by the wireless interface 18. From the high-level command received from the game controller 50, the secondary device controller can generate a low-level command understood by the wireless interface 18 that is incorporated in the secondary device.
In other embodiments, a secondary device can include virtual ticket voucher processing logic executed by a secondary controller. For instance, the printer 38 can include a printer controller capable of executing virtual ticket voucher processing logic and printed ticket logic and a wireless interface (Other examples of secondary devices with this capability can include but are not limited to a player tracking unit, a card reader or a bill validator). The game controller 50 can be configured to detect an actuation of the E-cash out button 26. In response, the game controller 50 can send a high-level message to the printer 38, such as “generate a virtual ticket voucher of a particular amount.” In response to receiving the command from the game controller 50, the printer controller can generate low-level commands to control various devices on the printer that allow the high-level command to be implemented. For instance, the printer controller can generate commands that 1) turn-on the wireless interface on the printer and change a status of a status indicator for the wireless interface on the printer to indicate it is “on,” 2) receive device information from a portable electronic device and then construct and send a message that allows a virtual ticket voucher to be sent to the portable electronic device and 3) send an acknowledgement to the game controller when the virtual ticket voucher has been received. The acknowledgement can include unique identifier information associated with the portable electronic device that received the virtual ticket voucher.
The game controller 50 can be configured to logically recognize a secondary device with multiple functions as separate devices according to the functions. The game controller 50 can recognize the devices during a device enumeration process. For example, a card reader with card reader functions and a capability to accept virtual ticket vouchers can present itself to the game controller 50 as a card reader 50 and a bill validator that accept virtual ticket vouchers. In this example, the game controller 50 may have already enumerated a first bill validator that accepts only cash and printed tickets. Thus, after the enumeration process, the game controller can logically be configured to control a card reader, a first bill validator that accepts cash and printed tickets and a second bill validator that accepts virtual ticket vouchers.
In yet other embodiments, the virtual ticketing voucher processing logic executed on a secondary device can be transparent to the game control controller 50. For example, the game controller 50 may be simply configured to send a “print ticket voucher” command and the secondary controller can be configured to issue the ticket voucher as a virtual ticket voucher. For instance, a card reader with this capability can receive the “print ticket voucher” command and issue a virtual ticket voucher. The card reader can be configured to communicate with a remote host to receive ticket validation numbers to associate with the virtual ticket voucher and report the issuance of the virtual ticket voucher to the remote host. If the card reader is not able to issue the virtual ticket voucher and a printer is present, the card reader can forward the command to the printer to have it issue a printed ticket voucher.
If the game controller 50 doesn't receive an acknowledgement within some time period, the game controller 50 can send a command to the printer to cancel the virtual ticket voucher transaction and generate a printed voucher for the amount. In response, the printer controller can turn-off the wireless interface and change the status indicator for the wireless interface to indicate it is no longer on. Then, the printer controller can control various print devices used to issue a printed ticket voucher.
Returning to
The interface 18 can be configured to send information formatted in one or more different wireless communication protocols. For instance, as described above, the EGM 2 via the wireless interface 18 can be configured to communicate information formatted in a NFC compatible protocol. Although not shown, a wired connection can be used to receive virtual ticket voucher information as well as other types of information from a wired interface coupled to a portable electronic device. The communication protocol used for the wired communication connection can vary depending on the wired connection that is utilized. In one embodiment, it can be USB. In a particular embodiment, the physical connection can be a micro USB compatible connection.
In other embodiments embodiment, an NFC interface on an EGM 2 can be used to set-up a higher speed communication between the EGM 2 and another NFC enabled device such as smart phone. The higher speed communications can occur via wireless interface 18 or another wireless interface on the EGM 2. The higher speed communication rates can be used for expanded content sharing. For instance, a NFC and Bluetooth enabled EGM can be tapped by an NFC and Bluetooth enabled smart phone to instantiate Bluetooth pairing between the devices. Instantiating pairing between a gaming device and an NFC enabled device, such as a smartphone, in this manner can save time related to searching, waiting, and entering codes. In another example, a gaming device can be configured as an NFC enabled router, such as a router supporting a Wi-Fi communication standard. Tapping an NFC enabled device to an NFC enabled and Wi-Fi enabled gaming device can be used to establish a Wi-Fi connection between the two devices.
As described above, the NFC communication can be used to exchange information to allow pairing to be established between a user-controlled device and the EGM 2. For instance, Bluetooth™ pairing occurs when two Bluetooth devices agree to communicate with each other and establish a connection. In order to pair two Bluetooth wireless devices, a password (passkey) is exchanged between the two devices. The Passkey is a code shared by both Bluetooth devices, which proves that both users have agreed to pair with each other. After the passkey code is exchanged, an encrypted communication can be set up between the pair devices. In Wi-Fi paring, every pairing can be set up with WPA2 encryption or another type of encryption scheme to keep the transfer private. Wi-Fi Direct is an example of a protocol that can be used to establish point-to-point communications between two Wi-Fi devices. The protocol allows for a Wi-Fi device pair directly with another without having to first join a local network. The method makes it possible to share media from a phone, play multiplayer games or otherwise communicate directly, even when no router exists. Via pairing between the EGM 2 and a portable electronic device, a portable electronic device may be able to utilize some of the functionality of secondary devices residing on the EGM 2. For instance, it may be possible for a player to print something from their portable electronic device using the printer 38 on the EGM 2 when it is paired to the EGM 2.
The game controller 50 can be used to control a status of the wireless interface 18, such as an “on” status where it is operable to receive wirelessly transmitted information from a portable electronic device or an “off” status where it is not operable to receive information. In particular embodiments, the game controller 50 can be configured to turn on the wireless interface in response to detecting an actuation of an E-cash in button 24 or an E-cash out button 26 (The actuation of the buttons can generate a signal which is received by the controller 50). In various embodiments, the E-cash in button or the E-cash out button can be integrated into a player input panel on the EGM cabinet. Further, the E-cash in button 24 and/or the E-cash out button 26 can be integrated into a secondary device, such as on the printer 38, the bill validator/voucher acceptor 22, a card reader (not shown) or a player tracking unit (not shown).
The status of the wireless interface 18 and upcoming changes in status to the wireless interface 18 can be indicated by an interface status device 19. The interface status device 19 can include components, such as lights and/or audio devices. The game controller 50 can be configured to control the interface status device 19 in a way that indicates the state of the wireless interface 18, such as on, off and about to change from on to off. As noted above, the control can be direct or via an intermediary device, such as a secondary controller.
Metering
For accounting and regulatory purposes, the game controller 50 can be configured to update and maintain a variety of hard and soft meters on the EGM. The hard and soft meters can be affected by transactions involving virtual ticket vouchers. A hard meter can be an electro-mechanical device, like an odometer, with a display that advances to display a quantity. Usually, a hard meter is not resettable. Government regulations, which can vary from jurisdiction to jurisdiction, often require hard meters to be read on a regular basis, such as monthly. Examples of hard meters 84 can include coins-in 84a, coins-out 84b, coins-dropped 84c, jackpots-paid 84d and cancelled credit meter 84e. Other hard meters can be implemented and these are provided for the purposes of illustration only.
The game controller 50 can be configured to update the coins-in meter 84a in response to value-in transactions. For example, the coins-in meter 84a can accumulate all value-in transaction on the EGM 2, such as from coin, bills, credit, token, paper token, printed ticket vouchers and virtual ticket voucher transactions. Thus, when a virtual ticket voucher is accepted on the EGM 2, the coins-in meter 84a can be updated by some amount depending on the value of the virtual ticket voucher. Devices, such as but not limited to the wireless interface 18, the bill validator/voucher acceptor 22 and a coin acceptor (not shown) can be used in performing a value-in transaction. In addition, via the network interface 56, the game controller 50 can be configured to receive a transfer of value, such as credits, to the EGM 2, from a remote device such as a bonusing server.
The game controller 50 can be configured to update the coins-out meter 84b in response to value-out transactions for the player. The coins-out meter 84b can be configured accumulate all value-out transactions from the EGM 2, such as from outgoing coin, bills, token, credit, paper token, hopper ticket, printed ticket voucher and virtual ticket voucher transactions, paid out for a) awards and b) credits from awards that are wagered. Thus, when a virtual ticket voucher is issued from the EGM 2, the coins-out meter 84b can be updated by some amount depending on the value of the virtual ticket voucher. Devices, such as but not limited to a coin-hopper (not shown), wireless interface 18 and printer 38 can generate the value-out transactions. The coins-out meter 84b may include credits that are accumulated on the jackpots-paid meter 84d.
The game controller 50 can be configured to update the coins-dropped meter 84b in response to value-out transactions for the casino. The coins-dropped meter 84d can accumulate 1) all coins and tokens that have been diverted into a drop bucket and 2) bills, paper tokens, printed ticket vouchers and virtual ticket vouchers accepted by the EGM 2. Thus, coins-dropped meter 84d can be advanced when a virtual ticket voucher is accepted at the EGM 2.
The jackpots-paid meter 84d can reflect any single event award that is not paid out by the EGM 2. For example, depending on the amount of the jackpot, the EGM 2 may not be configured to dispense coins, issue a printed ticket voucher or issue a virtual ticket voucher above a certain value. In this situation, the payment of the jackpot amount can be handled by some other means, such as check from the casino. The jackpots-paid meter 84d may also include credits accumulated on the canceled credit meter. The canceled credit meter 84e can accumulate credits paid by means other than payouts from the devices on the EGM 2, such as the hopper, printer, bill hopper, wireless interface or jackpot payouts if the device has such credit provisions.
The game controller 50 can be configured to maintain a number of soft meters. The soft meters can be electronic equivalents to the hard meters where data is stored in a digital format. The soft meters can be designed to be maintained at all times even when the EGM 2 is not supplied with power. One type of memory that can be used for storing soft meter data is a non-volatile memory, such as a battery backed RAM. It may be possible to reset the soft meters. For instance, the non-volatile memory storing the soft meter data can be cleared to reset the soft meters. However, before it is implemented, this process may require approval from a gaming regulator. Further, the EGM 2 can be designed such that an error condition on the EGM 2, such as a power failure, doesn't cause the soft meters stored in non-volatile memory to be erased.
The EGM 2 can be configured to maintain soft meters that duplicate all or a portion of the quantities accumulated by the hard meters 84. For instance, the game controller 50 can maintain a soft coin-in meter 62. When duplicate values are accumulated on the soft and hard meters, the values accumulated over a particular time period on each type of meter should match. As described above, the soft meters that duplicate of the hard meters can be affected when virtual ticket vouchers are redeemed for credit on the EGM 2 or when virtual ticket vouchers are issued. For instance, the coin-in soft meter 62 and coins-dropped soft meter (not shown) can be updated in response to the successful redemption of a virtual ticket voucher. As another example, the coin-out soft meter (not shown) can be updated in response to a successful acceptance of virtual ticket voucher.
The game controller 50 can include an operator mode 58 where values of the soft meters can be read. The operator mode 58 includes the software logic that allows values of the soft meters to be gathered and then output. For instance, in operator mode, the game controller 50 can display the values of various soft meters to the main display. In some embodiments, the game controller 58 can be configured to periodically send values of the soft meters to a remote device, such as accounting server 70. In another embodiment, the soft meter values can be displayed via a secondary device. For instance, a player tracking unit with a display and a smart interface board (SMIB), coupled to the game controller 50 can be configured to retrieve soft meter data from the game controller 50 and display it to the player tracking display. As another example, a SMIB coupled to the game controller 50 can be used to store and report soft meter values to a remote device.
The EGM 2 can accumulate other quantities in the soft meters that are not accumulated by the hard meters 84. For instance, in one embodiment, the game controller 50 can maintain a voucher-in soft meter 64. The voucher-in soft meter 64 can record a total number of validated printed ticket vouchers and validated virtual ticket vouchers redeemed the EGM 2. Thus, the voucher-in soft meter 64 can be incremented by 1 each time a printed or virtual ticket voucher is redeemed. The voucher-out soft meter 66 can record a total number of printed ticket vouchers and virtual ticket vouchers issued from the EGM 2. Thus, voucher-out soft meter 66 can be incremented by 1 each time a printed ticket voucher or a virtual ticket voucher is issued from the EGM 2.
As another example, the game controller 50 can maintain a virtual ticket voucher-in soft meter 80 and a virtual ticket voucher-out soft meter 82. The virtual ticket voucher out meter can be advanced by 1 each time a virtual ticket voucher is issued from the EGM 2. The virtual ticket in meter can be advanced by 1 each time virtual ticket voucher is accepted by the EGM 2. Other soft meters (not shown) can include a total value of virtual ticket vouchers issued, a total value of virtual ticket vouchers and printed ticket vouchers issued, a total value of virtual ticket vouchers successfully redeemed and a total value of the virtual ticket vouchers and a printed ticket vouchers successfully redeemed. Thus, as virtual ticket vouchers are successfully redeemed and virtual ticket vouchers are successfully issued, these four soft meters can be incremented depending on values associated with each of the virtual ticket vouchers issued or redeemed. The game controller 50 can also report soft meter values including each time a soft meter is incremented to a remote device for cross validation accounting purposes.
Dispute Resolution
At certain times, a player can dispute a transaction that has occurred on an EGM. For instance, a player can dispute that the EGM 2 issued a virtual ticket voucher that didn't accurately reflect the credits that were on the EGM 2 at the time the virtual ticket voucher was issued. In another embodiment, the player can dispute that the credits associated with a virtual ticket voucher accepted at the EGM 2 were not properly credited to the EGM. In one embodiment, to allow for disputes involving virtual ticket vouchers, an operator activated dispute resolution mode can be provided on the game controller.
In one embodiment, to help with dispute resolution, the game controller 50 can maintain a virtual ticket voucher received stack 60 and a virtual ticket voucher issued stack 61. The virtual ticket voucher received stack 60 can include an electronic log of information associated with virtual ticket vouchers, such as time received, amount associated with the voucher, virtual ticket voucher number, when the virtual ticket voucher was issued, etc. In addition, the virtual ticket voucher received stack 60 can include images of virtual ticket vouchers redeemed and validated on the EGM 2. As described above, in one embodiment, when a virtual ticket voucher is received, the game controller 50 can be configured to render an image of the received voucher. Thus, the image that is rendered can also be saved to the virtual ticket stack 60. The virtual ticket voucher images can be saved with the time that they are received.
When placed in dispute resolution mode, the game controller 50 can be configured to display one or more of the saved virtual ticket voucher images at a time to a display, such as a main display on the EGM 2. In one embodiment, a virtual ticket voucher image is saved when the virtual ticket voucher is accepted. In another embodiment, an image of the virtual ticket voucher can be rendered on the fly based upon virtual ticket voucher information saved to an electronic log, such as a ticket format, ticket number, ticket amount, etc. The dispute resolution mode can provide an interface that allows the operator to scroll through the virtual ticket voucher received stack 60, such as in the order that the virtual ticket vouchers were received. In another embodiment, the dispute resolution mode can be configured to display virtual ticket voucher information, such as the amounts associated with each virtual ticket voucher received, in a non-image format. A benefit of displaying the information in an image format is that the customer may recognize the image of the voucher which can aid the dispute resolution process.
In another embodiment, data used to render a virtual ticket voucher can be saved. For example, if a standard format is used to render the virtual ticket received vouchers, the saved data may be the unique data associated with each virtual ticket voucher, such as an amount, ticket number, etc. As described above, a standard format to render the “virtual ticket vouchers received” can be selected so that it matches the format of printed ticket vouchers that are received. Thus, in the display resolution mode, the game controller 50 can be configured to render one or more virtual ticket vouchers in the “virtual ticket voucher received stack” 60 on the fly using the code for rendering the images of the virtual ticket vouchers and the virtual ticket voucher data stored in stack 60.
As described above, the format of the data associated with the virtual ticket vouchers and printed ticket vouchers can be the same. An advantage of using the same format is that the virtual ticket vouchers can be compatible with an existing cashless system providing redemption and issuance of printed ticket vouchers. The difference being that the electronic data for the virtual ticket vouchers remains in electronic form while the electronic data for the printed ticket vouchers is sent to a printer and added to a printed ticket. In the case of the received ticket vouchers, the data for the virtual ticket voucher is received electronically while printed ticket voucher data is read by some device (for instance, a bar-code scanner can read a bar code printed on the ticket, which can be used to reference ticket information stored a remote server). After data is read from the printed ticket voucher and the printed ticket voucher is redeemed, the received printed ticket voucher can stored to a bill voucher/stack, such as 54. Typically, the bill/voucher stack 54 is in a cash box secured within a main cabinet of the EGM 2.
In one embodiment, the game controller 50 can maintain a ticket voucher received stack, which includes ticket voucher data for ticket vouchers received in a virtual ticket format or received in a printed ticket format. The time at which each of the tickets is received can be stored in the stack so that the ticket voucher data can be retrieved in a time sequential order. In dispute resolution mode, the ticket voucher data for the printed ticket vouchers can be retrieved and rendered in the same way that virtual ticket voucher data is retrieved and rendered. The virtual ticket vouchers and the printed ticket vouchers can be rendered slightly differently, such as different color, to allow the format in which each type of ticket vouchers was received to be distinguished.
The issued virtual ticket voucher issued stack 61 can be maintained and accessed in the manner similar to the virtual ticket voucher issued stack 60. For instance, images of issued virtual ticket vouchers that have been rendered can be saved to memory or the virtual ticket voucher data of the issued vouchers can be saved to memory and later used to render images of virtual ticket vouchers that can be output to a display device. In one embodiment, an electronic ticket voucher issued stack can be maintained. The electronic ticket voucher issued stack can include ticket voucher data for ticket vouchers issued in a printed ticket voucher format or a virtual ticket voucher format. The game controller 50 can be configured to retrieve the ticket voucher data from the stack and render images of virtual ticket vouchers or printed ticket vouchers using the data. The rendered ticket voucher images can be output to a display device.
Retrofit
Next, with respect to
In another embodiment, as described with respect to
As described above, a printer and/or bill validator can be configured with virtual ticket functions where the game controller is aware of the functionality. For instance, the game controller can be configured to command the printer to print a virtual ticket voucher to issue a virtual ticket voucher and expect an acknowledgement that the virtual ticket voucher has been issued from the printer. For a retrofit of an EGM where the game controller was designed without virtual ticket voucher functionality, the game controller may not have the capability to issue commands associated with virtual ticket vouchers or receive and parse acknowledgements associated with virtual ticket vouchers from a secondary device, such as a printer with virtual ticket voucher functionality. Thus, as is described in more detail below, the interactions between a retrofit device and a game controller, such as a retrofit printer with virtual ticket voucher functionality, can be different than in the instance of a printer with virtual ticket voucher functionality where the game controller is configured to utilize the virtual ticket functionality.
The retrofit device 52 can be configured to accept virtual ticket vouchers, issue virtual ticket vouchers or combinations thereof. Further, it can be configured to maintain soft meters, such as the v-ticket-in meter 80 and the v-ticket-out meter 82 and other meters as described above. Thus, the retrofit device 52 can include a processor and memory for updating the software meters and a non-volatile memory for storing the soft meter values. The retrofit device 52 can be configured to report soft meter values to a remote device via a wired or wire communication interface associated with the retrofit device 52 or available on the EGM 2. Like the soft meters maintained in the game controller 50, the soft meters maintained by the retrofit device can be configured to be generally non-resettable. However, the retrofit device 52 can be configured to reset the soft meters after approval is received from a gaming regulator. For instance, the reset of the soft meters on the retrofit device 52 can be performed in the presence of a gaming regulator.
The retrofit device 52 can be configured to update a set of hard meters 86 separate from the hard meters 84 maintained by the game controller 50. For instance, the retrofit device 52 can be configured to update hard meter equivalents for one or more of the soft meters it maintains. In particular components, the hard meters can be integrated into the retrofit device 52. Like the embodiment described in
Further, as is described in more detail below, the retrofit device 52 can be configured with device emulation 77. The device emulation 77 can allow the retrofit device 52 to respond to game controller 50 as if it were another device on the EGM 2, such as the printer 38 and/or the bill validator 22. The user interface provided on the retrofit device can be different from either of the devices it is emulating. For instance, retrofit device that emulates a printer 38 and/or the bill validator may not include a slot for issuing ticket voucher or a slot for accepting ticket vouchers. Further, the retrofit device can include additional interface devices, such as a display, touch screen, graphical user interface, engraved or printed instructions or buttons, that aren't found on a typical bill validator or printer.
Next some details of the operation of the retrofit device are described. The E-cash in button and the E-cash out button 26 can be located somewhere on the player interface. For instance, an existing player input panel can be replaced with a retrofit player input panel that includes the E-cash in button 24 and the E-cash out button 26. In other embodiments, existing buttons on a player interface panel can be reprogrammed to provide these functions. In addition, the retrofit player input panel can include the wireless interface 18 and an expose a portion of the status indicator 19.
When the retrofit device 52 detects the E-cash in button 24 has been actuated, it can place itself in a state where it is ready to receive information associated with a virtual ticket voucher. For instance, it can activate wireless interface 18 so that it is ready to receive virtual ticket information from a portable electronic device and change a state of the status indicator 19 to indicate it is ready. If the status indicator includes a display than a message can be output to the display indicating the retrofit device is ready to receive virtual ticket voucher information. If the wireless interface is only left active for some time period, then the retrofit device 52 can initiate a countdown as was described above with respect to the EGM 2 to determine when to deactivate the wireless interface.
After the retrofit device 52 receives or recognizes the virtual ticket voucher information, the retrofit device, via the device emulation 77, can respond to the game controller 50 as if it were bill validator 22 that has accepted a printed ticket voucher. Towards this end, the retrofit device communications can be interposed on the communication link between the bill validator 22 and the game controller 50. Interposing the retrofit device on this communication link can involve inserting an adapter at one of the communication endpoints (i.e., at the bill validator or the game controller end) that routes the communications between the bill validator 22 and the game controller through the retrofit device.
When the retrofit device is activated to receive a virtual ticket voucher, such as after an actuation of the E-cash in button 24 is detected, it can notify the game controller in the same way as the bill validator 22 notifies the game controller 50 when a printed ticket has been detected as being inserted. After the virtual ticket voucher information is received, the retrofit device 52 can notify the game controller 50 on the bill validator communication link in the same manner as if information has been read from a printed ticket voucher. During this process, commands/acknowledgements sent from the game controller 50 to the bill validator 22 can be blocked from reaching the bill validator and instead can be processed and responded to by the retrofit device 52. If the virtual ticket voucher is validated, the game controller 50 will update its soft meters and hard meters as if a printed ticket voucher of some amount had been received by the bill validator. As described above, in a non-retrofit embodiment, the game controller 50 can be configured to update hard and/or soft meters associated with virtual ticket vouchers, such as a number of virtual ticket vouchers accepted and a value of the virtual ticket vouchers accepted.
If the virtual ticket voucher information is not validated and the game controller 50 sends a command to the bill acceptor 22 to reject a printed ticket (send it back out the ticket slot), then, the retrofit device 52 can receive the command and respond to the game controller 50 as if it has rejected a printed ticket. In one embodiment, the retrofit device 52 may have access to an interface, such as a display, that allows it to display a message that indicates the virtual ticket voucher is invalid. In another embodiment, the retrofit device 52 can be configured to change a state of the status indicator 19 to indicate the rejection of virtual ticket voucher. For instance, if so equipped, a light associated with the status indicator can flash red when the virtual ticket voucher is not accepted. In a bill validator, a physical ejection of the printed ticket voucher is used to indicate the printed ticket voucher has been ejected. In addition or alternatively, a rejection message or rejection indication can sent to a portable electronic device and the message or some indicator that the ticket voucher has been rejected can be output to the portable electronic device.
If the retrofit device 52 detects that the bill validator is initiating a transaction, such as when it has received a printed ticket voucher or a bill, it can allow communications between the game controller 50 and bill validator 22 to pass through. If the retrofit device 52 detects an actuation of the E-cash in button 24 before the transaction between the bill validator 22 and the game controller 50 is completed, the retrofit device 52 can be configured to ignore and not respond to the signal or the retrofit device 52 can be configured to wait to respond to the signal until it determines the transaction between the bill validator 22 and the game controller 50 is completed. For instance, a state of the wireless interface 18 and it associated status indicator 19 may not be changed until the transaction between the game controller 50 and the bill validator is completed. This sequence can occur if a user wishes to deposit credits via a printed ticket voucher and then deposit credits via a virtual ticket voucher.
Next, cash out transactions are described using the retrofit device 52. The E-cash out button 26 can be coupled to the retrofit device 52 and the game controller 50 via the communication path for the cash out button 30. Thus, when either the E-cash out button 26 or the cash out button 30 is actuated, the game controller can receive and process the signal as if the cash out button 30 has been actuated, i.e., the game controller 50 is not configured to distinguish that the signal was generated from the E-cash out button 26 or the cash out button 30. Then, when a signal is received from either button, the game controller 50 can respond in the same manner as if the cash out button has been activated. The game controller 50 can contact the validation server to receive ticket voucher information, such as a unique validation number for the ticket voucher that is to be issued. Then, the game controller 50 can generate and send instructions to the printer 38 to print a ticket voucher including the unique validation number.
The retrofit device 52 can be interposed on the communication path between the printer 38 and the game controller 50, such as in the manner described with respect to the bill validator. The retrofit device can be embodied physically as a separate device or logically within an existing device. The retrofit device 52 can receive the print instructions, activate the wireless interface 18 and change the status indicator 19. If a portable electronic device is detected and the virtual ticket voucher is transferred to the portable electronic device within some time period, the retrofit device 52 can respond to the game controller 50 as if it were the printer 38 and it had issued a printed ticket. If the retrofit device 52 doesn't issue the virtual ticket voucher within the time period, it can change the status of the wireless interface 18 and the status indicator 19 and release the initial print command to the printer 38 so that transaction is now processed as printed ticket. It can then allow subsequent communications between the printer 38 and the game controller 50 to pass through the retrofit device 52 so that the printed ticket voucher transaction can be completed.
When the retrofit device 52 receives a print voucher command from the game controller 50 and an actuation of the E-cash out button hasn't been detected, then the retrofit device 52 can be configured to allow communications between the game controller 50 and the printer 38 to pass through the retrofit device 52 until the printed ticket transaction is complete. In this example, the print voucher command can be initiated when a signal from an actuation of a cash-out button on the EGM 2 is detected. If the retrofit device detects an actuation of the E-cash out button 26 after the cash-out transaction has been initiated via the cash-out button, then the retrofit device 52 can be configured to ignore the E-cash out button because a printed voucher transaction has already been initiated. In alternate embodiments, the printer 38 and/or the bill validator can be removed from the EGM 2. In these embodiments, the retrofit device 52 can be configured to emulate the printer 38 and/or the bill validator to issue and/or receive only virtual ticket vouchers.
In one embodiment, the retrofit device 52 can be configured to report its virtual ticket voucher activity to a remote device, such as the validation server 68 or the accounting server 70. For instance, the retrofit device 68 can be configured to communicate which of the printed ticket voucher transactions initiated by the game controller 50 were actually completed as virtual ticket voucher transactions. Similarly, the retrofit device 52 can be configured to communicate to a remote device which ones of the redeemed ticket vouchers reported as being received in the bill validator 22 by the game controller 50 were actually virtual ticket vouchers. Similarly, if the retrofit device 52 is configured to accept virtual currency, such as via an e-wallet application, the retrofit device 52 can be configured to communicate to a remote device when virtual currency is accepted. This information would be useful for the soft count process since the virtual ticket vouchers or the virtual currency won't be in the cash box when the bills and printed tickets in the cash box are counted.
The retrofit device 52 can communicate with a remote device via the game controller 50 and the network interface 56 if the game controller 50 is configured to allow pass through communications from a device, such as 52. In another example, the retrofit device can be directly coupled to the network interface 56 if the network interface 56 allows for such communications and initiate communications through the network interface 56. In yet another embodiment, the retrofit device 52 can include its own communication interface, such as wireless communication interface, that allows it communicate with server 68 or 70 via some other communication pathway.
In
In another embodiment, the functions of the retrofit device can be incorporated into a player tracking unit. If desired, the wireless interface 18, the status indicator, the E-cash in button and/or the E-cash out button can be integrated into the player tracking interface. The cabinet of the EGM 2 includes an aperture that can be filled by the player tracking interface so that the features of the player tracking interface are accessible to a player. This feature can allow the player tracking unit with virtual ticket voucher in and virtual ticket voucher out capabilities to replace and fit in the space occupied by an existing player tracking unit without these capabilities.
As another example, the printer 38 or the bill validator 22 can be configured with the retrofit device functions. If the printer 38 is incorporated with all of the retrofit device functions, then the printer 38 can be configured to determine whether a ticket voucher is to be issued as virtual ticket voucher or a printed ticket voucher but respond to the game controller 50 as if all of the transactions were printed ticket vouchers. Thus, the existing connection between the game controller 50 and printer 38 may not have to be modified. However, to perform virtual ticket-in functions, the printer 38 can be interposed between the communication channel between the game controller 50 and the bill validator. As described above for the retrofit device, the printer 38 can be configured to block certain communications to the bill validator 22 and in some instances respond to the gaming controller 50 as if it were a bill validator.
In yet another example, if the bill validator 22 is incorporated with all of the retrofit device functions, then the bill validator can be configured to determine whether an accepted ticket voucher is a virtual ticket voucher or a printed ticket voucher but respond to the game controller 50 as if all of the transactions were printed ticket vouchers. The existing connection between the game controller 50 and bill validator may not have to be modified. However, to perform virtual ticket out functions, the bill validator can be interposed between the communication channel between the game controller 50 and the printer 38. As described above for the retrofit device, the bill validator can be configured to block certain communications to the printer 22 and in some instances respond to the gaming controller 50 as if it were a printer.
In yet other embodiments, the E-cash in button 24 and/or the E-cash out button 26 functions can be embodied on a portable electronic device. As an example, the EGM 2 can be configured to establish communications with the portable electronic device. After communications are established with the portable electronic device, an application executing on the portable electronic device can generate a touch screen button to initiate an E-cash in transaction or an E-cash out transaction. When portable electronic device detects one of the buttons has been selected, a message requesting the EGM 2 to initiate an E-cash in transaction or an E-cash out transaction can be sent to the EGM 2. The message can be received by the game controller or another device with a secondary controller, such as a player tracking unit, bill validator, printer or card reader, configured to respond to the message. In response to receiving the message and E-cash in transaction and/or an E-cash out transaction can be generated.
Thus, in particular embodiments, the EGM 2 may or may not include the E-cash in button 24 or the E-cash out button 26. In addition, the EGM 2 can include E-cash in button 24 and/or an E-cash out button 26 and can also be configured to receive a message from a portable electronic device requesting an E-cash in transaction or an E-cash out transaction. In this embodiment, the EGM 2 can initiate the E-cash in transaction in response to an actuation of the E-cash in button 24 or in response to receiving a message from a portable electronic device or some other remote device requesting the E-cash in transaction. Similarly, the EGM 2 can initiate the E-cash out transaction in response to an actuation of the E-cash out button 26 or in response to receiving a message from a portable electronic device or some other remote device requesting the E-cash out transaction.
In one embodiment, the remote device requesting the E-cash in or E-cash out transaction can be a remote server. The remote server can open up a “service window” on the EGM 2 that includes a touch screen button to initiate an E-cash in transaction or an E-cash out transaction. The remote server can receive an indication that the E-cash in button or the E-cash out button has been selected. In response, the remote server can send a message to the EGM 2 requesting an E-cash in transaction or an E-cash out transaction. In response, the gaming controller or a secondary controller on the EGM 2 that receives the request message can initiate the E-cash in transaction or the E-cash out transaction involving a portable electronic device.
Next embodiments are described where some of the retrofit device functions are split between secondary devices on an EGM, such as a bill validator and a printer.
In
In
In one embodiment, the bill validator 108 can include one or more of a wireless interface 106, a status indicator (not shown) and the E-cash in button 24, built into the face of the bill validator including the slot for receiving bills. Alternatively, the bill validator 108 can be configured to receive a message from a portable electronic device or a remote server requesting an E-cash in transaction and may not include an E-cash in button 24. In this embodiment, the bill validator 108 can establish a communication session with the portable electronic device and/or a remote server and then receive the message requesting the E-cash in transaction from one of the devices.
The bill validator 108 can be configured to activate the wireless interface 106 and process information received via the wireless interface. Further, it can be configured to control the status indicator to indicate changes in state of the wireless interface 106, such as if the wireless interface is turned on or off. In a non-retrofit embodiment, when the E-cash in button 24 is included on the bill validator and it is actuated, the bill validator 108 can be configured to report the initiation of virtual ticket in transaction to the game controller rather than reporting it as a printed ticket-in transaction.
In
The printer 102 can include an operator mode 91 that allows the printer 102 to be interrogated for information, such as for its soft meter values associated with the virtual ticket vouchers that have been issued. As described above, the printer can include a non-volatile memory for maintaining the soft meters, such as battery-backed RAM, Flash or NV-RAM technologies. In one embodiment, via the output interface 92, this information can be displayed to a remote device, such as portable electronic device carried by an operator or to a display device coupled to the EGM 2. In a non-retrofit embodiment, this information can be reported to the game controller 50 and maintained as soft meters by the game controller 50. Thus, the operator mode 91 for displaying soft meter values may not be needed with a non-retrofit printer device but could be included as a back-up to the game controller 50.
In yet another embodiment, the printer 102 can include one or more of a wireless interface 91, a status indicator (not shown) and the E-cash out button 26, built into the face of the printer 102 including the slot for ejecting tickets that forms a portion of the EGM exterior. The printer can be configured to activate the wireless interface 90 and process information received via the wireless interface. Further, it can be configured to control the status indicator to indicate changes in state of the wireless interface 90, such as if the wireless interface is turned on or off. As described above, if the E-cash out button is included in the printer interface then the printer can be coupled to the communication channel associated with the cash out button, such that a cash-out signal is sent to the controller 50. The printer 102 can be configured to generate this signal. In response, the controller 50 can initiate a cash-out sequence where it is responding as if a printed ticket voucher is being generated. In non-retrofit embodiments where the controller 50 includes virtual ticket out functionality, the printer 102 can notify the game controller 50 that the E-cash out button 26 has been actuated and in response the game controller 50 can initiate and E-cash out transaction.
In the example described above, the bill validator 108 and the printer 102 each include separate wireless interfaces. If a NFC compatible interface was used, then as part of a virtual ticket in transaction, a portable electronic device might need to be placed near or in contact with the bill validator interface. In addition, as part of a virtual ticket out transaction, the portable electronic device might need to be placed near or in contact with the printer interface. Having to place the portable electronic device in different locations for each type of transaction reduces the required interfaces, thus, in one embodiment, two devices, such as a printer and a bill validator with virtual ticket out and ticket in capabilities can share a wireless interface and status indicator. However, it may be more intuitive for a user to place their device near a cash-in device for a cash-in transaction and near a cash-out device for a cash-out transaction. Thus, in some embodiments, separate wireless interfaces may be maintained.
In this embodiment, provisions may need to be made in regards to sharing control of the interface and status indicator. For instance, the wireless interface can communicate its status, i.e., whether it is in use or not. The bill validator and printer can be configured to respond to the case where the interface is being utilized by the other device and it wishes to initiate a transaction. For instance, after a virtual ticket out transaction is initiated on the printer 102, the printer might start controlling the shared interface. If the E-cash in button was pressed, the bill validator can attempt to control the interface but receive an indication from the wireless interface that it is busy. In response to the bill validator receiving an indication that wireless interface is busy, the bill validator can be configured to ignore the virtual ticket in request. In another example, it can be configured to hold the transaction in abeyance and continue to check the status of the wireless interface. When it detects the status of the wireless interface is inactive (i.e., the printer is not controlling the interface), it can initiate the virtual ticket in transaction on the wireless interface.
In other embodiments, only one of the devices and its associated functions can be included. For instance, an EGM can be configured with a retrofit printer device that can issue virtual ticket vouchers or printed ticket vouchers but is only able to accept printed ticket vouchers and thus, doesn't include a bill validator with the functions described above. In another example, the EGM can be configured with a retrofit bill validator that can receive virtual ticket vouchers or printed ticket vouchers but is only able to issue printed ticket vouchers and thus, doesn't include a printer with the functions described above.
Virtual Ticket Management
With respect to the
The portable electronic device 202 can include a processor, a memory and a network interface 220. In addition, the portable electronic device can include a number of I/O interfaces 222. The I/O interfaces 222 can include visual and audio interfaces, such as displays, speakers, cameras, microphones, a touchscreen and an audio jack. The I/O interfaces 222 allow a user to interact with the portable electronic device including receiving video images and audio content associated with different applications executed on the portable electronic device. Further, the I/O interfaces 222 can include wired and/or wireless interfaces that allow the portable electronic device to communicate with other devices directly or via a network connection. Further, the portable electronic device 202 can include various a GPS receivers and various sensors, such as an accelerometer. The GPS receiver can be used for applications requiring a location. The accelerometer can be used to detect a movement of the device, which in some instances can used to generate control commands. As an example, the portable electronic device 202 can be a smartphone or a tablet computer, such as an iPhone™ or an iPad™ by Apple™.
As described above, the portable electronic device 202 can be used with virtual ticket vouchers. In particular, a virtual ticket voucher stored on the portable electronic device 202 can be transmitted to an EGM and validated to allow credit associated with the virtual ticket voucher to be deposited on the EGM. Also, a virtual ticket voucher generated by an EGM can be transmitted to the portable electronic device 202 to allow cash or credits to be transferred from the EGM to the portable electronic device. The virtual ticket voucher received by the portable electronic device from the EGM can later be used for game play on other EGMs, can be redeemed for cash at a cashier station or at a redemption kiosk, or can be converted into a virtual cash form compatible with an E-Wallet application.
In one embodiment, the portable electronic device 202 can be configured to execute a voucher management application 218 for managing virtual ticket vouchers. The voucher management application 218 can be downloaded from a remote device, such as server 200. A voucher management download application 215 on server 200 can be configured to download voucher management applications compatible with different operating systems, such as iOS™ by Apple™, Android™ by Google™, Windows 7 by Microsoft™ or QNX RTOS by RIM™. The different operating systems can be utilized by different types of portable electronic devices.
In other embodiments, the portable electronic device 202 can be implemented more simply. For instance, a smart card or an appropriately configured memory stick can be used to send virtual ticket vouchers to an EGM and receive virtual ticket vouchers from the EGM. For instance, a wired or wireless interface can be provided on the EGM to communicate with the memory stick. The EGM can detect the memory stick and display its contents related to virtual ticket vouchers to a display. On the display, such as a touch screen display, the user may be able to drag virtual ticket vouchers to a particular area associated with the EGM, such as a box rendered on the display, to redeem the vouchers and drag virtual ticket vouchers from an area associated with the EGM to an area associated with the memory stick to store the virtual ticket voucher to the memory stick.
The virtual ticket voucher management application can be configured to store virtual ticket voucher information 212 associated with unredeemed and redeemed virtual ticket vouchers. In one embodiment, the application 218 can be configured to manage account data associated with a loyalty program. Further, the application 218 can include voucher templates 214 that allow a user to customize the appearance of a virtual ticket voucher displayed on the portable electronic device 202. For instance, as described above, a virtual ticket voucher can be rendered in the format of a printed ticket voucher where via the voucher templates 214, the user can customize the rendered appearance of virtual ticket vouchers stored on the portable electronic device 202. In one embodiment, the ticket customization templates can be downloaded from a remote host, such as web-site affiliated with a casino or a gaming machine manufacturer.
In addition, the application 218 can provide a voucher interface 216. The voucher interface 216 can be configured to allow a user to organize, display and redeem their virtual ticket vouchers and manage loyalty program information. A few examples of an interface associated with the virtual ticket voucher management application are described with respect to
In other embodiments, the virtual ticket management application 218 can be configured to communicate with a remote device, such as server 200, to receive other additional virtual ticket voucher services. For instance, server 200 can be configured to provide downloads including updates of the voucher management application 218 to remote devices, such as device 200. In one embodiment, the server 200 can include logic 208 that allows a virtual ticket voucher to be issued and transmitted to a portable electronic device 202. To perform this transaction, the server 200 can be configured to 1) contact a validation server that is utilized by one or more casino locations to receive unique voucher information, 2) construct a valid virtual ticket voucher, 3) confirm payment for the virtual ticket voucher, 4) transmit the virtual ticket voucher to the portable electronic device and 5) notify the validation server that the virtual ticket voucher has been issued. In addition, the server 200 can be configured to send device information associated with the portable electronic device 202, such as unique device information. In one embodiment, as described above, the validation server may require the unique device information to validate the virtual ticket voucher.
A restriction with the virtual ticket voucher issued by server 200 can be that the virtual ticket voucher has to be redeemed at the casino for which is valid. As will be described in more detail as follows, the server 200 can be configured to redeem the virtual ticket vouchers issued at a gaming property, such as a casino. In one embodiment, the server 200 may not validate tickets issued from the server 200. Another restriction can be the server 200 may not issue virtual tickets above a certain value, such as above $100 dollars.
Another type of virtual ticket voucher that can be purchased is a virtual ticket voucher redeemable for promotional credits. Promotional credits can be played on an EGM but can't be redeemed for cash. However, awards earned from wagers using the promotional credits can be redeemed for cash. As an example, the server 200 can be configured to allow a purchase $100 dollars worth of promotional credits for $50 dollars. This type of offer can offered in a group fashion, such as purchase $100 dollars worth of promotional credits for $50 if 50 people sign-up for the deal. The purchase of the promotional credits can be handled by the promotion application 204. To allow redemption of promotional credits, the server 200 can be configured to contact a validation server at a gaming property to receive a unique validation number that allows the promotional credits to be redeemed at the gaming property.
The server 200 can provide incentives to purchase a virtual ticket voucher that can redeemed for cash at a casino. For instance, as described in the previous paragraph, if a cash value virtual ticket vouchers is purchase for a certain value, the server 200 can be configured to issue a second virtual ticket voucher for promotional credits. As other incentives, the server 200 can be configured to issue virtual ticket vouchers that can be redeemed for discounts for services at a casino property, such as a discount at restaurant, a discount at a spa, a discount at a gaming property store or a discount on lodging. The amount of incentives provided with a purchase of virtual ticket voucher can be related to the value of the virtual ticket voucher purchased. In one embodiment, to receive a virtual ticket voucher redeemable for an incentive, such as a discount for lodging, a user may have to provide identification information. When identification information is provided, the redemption of the virtual ticket voucher redeemable for an incentive may be limited to a particular person associated with the identification information. The server 200 can store a record of the identification information associated with each virtual ticket voucher.
In other embodiments, the server 200 can be configured to provide virtual ticket voucher redemption 206. The server 200 can be configured to establish contact with a remote device, such as portable electronic device 202 and receive virtual ticket voucher information associated with a virtual ticket voucher stored on the portable electronic device that was transferred to the portable electronic device at a gaming property. After receiving the virtual ticket voucher information from the portable electronic device, the server 200 can be configured to contact a validation server 200 at the gaming property, transmit the virtual ticket voucher information and receive a confirmation in regards to whether the virtual ticket voucher is valid and hasn't been previously redeemed.
If the virtual ticket voucher is validated, then server 200 can be configured to provide the redemption value of the virtual ticket voucher to a user and notify a validation server that the virtual ticket voucher has been redeemed. For instance, the server 200 can be configured to mail a check for the value of the virtual ticket. In another embodiment, the server can be configured to make an electronic funds transfer to an account specified by a user, such as PayPal™ account, a regular bank account or some other account accessible to the user.
In another embodiment, the user can have an account on server 200 where virtual ticket vouchers can be stored. The account can be set up to automatically redeem and transfer funds associated with the redeemed virtual ticket vouchers to a user's bank account. For instance, the account can be set-up to perform this action automatically 30 days after a virtual ticket voucher has been issued. In another embodiment, a voucher management application executed on a user's mobile device or a home computer can be configured to carry out this process (e.g., contact the server 200, request a redemption of a virtual ticket voucher and a transfer of funds to a user's bank account when the ticket is valid).
To encourage user's to redeem their virtual ticket vouchers at the gaming property where they were issued, limits can be set on when a virtual ticket voucher can be redeemed. For instance, on server 200, a virtual ticket voucher may not redeemable until it is close to its expiration date, such as week from expiring. Thus, a user would have to wait unit the virtual ticket voucher was about to expire to redeem on-line or else travel to the gaming property where it was issued to have it redeemed. In another example, the server 200 may not be configured to redeem virtual ticket vouchers over a certain amount, such as over $100 dollars.
In one embodiment, rather than redeeming virtual ticket vouchers, the server 200 can be configured to provide an extension of the expiration date. Thus, if a virtual ticket voucher was about to expire, via a portable electronic device, the user can send the virtual ticket voucher information to the server 200 and request and expiration date extension. In response, the server 200 can contact a validation server at a gaming property and request an extension. If granted, the validation server can transmit the new expiration date to the server 200 and then the server 200 can notify the user associated with the portable electronic device 202 of the new expiration date.
Next, a few details of a voucher management application executable on a portable electronic device, such as 202, are discussed.
In one embodiment, the voucher management application can be configured to display information associated with one or more virtual ticket vouchers. As previously described, the virtual ticket voucher information can be rendered in the format of printed ticket voucher. In one embodiment, the virtual ticket voucher can be rendered in a format that is consistent with the gaming property from which it was issued. In another embodiment, voucher management application can be configured with options, such as voucher format templates, that allow a user to customize the appearance of the virtual ticket vouchers rendered on the display of the portable electronic device. In some instances, all or a portion information can be transferred to a gaming device, such as an EGM. When virtual ticket voucher information is transferred to the EGM, the EGM can be configured to render an image of the virtual ticket voucher on one of its displays using the user-selected format parameters for the virtual ticket voucher.
If multiple virtual ticket vouchers are rendered on a display of the portable electronic device simultaneously, the size of each rendered voucher may be reduced and information associated with the rendered voucher may be difficult to see. Towards this end, the voucher management application can be configured to render information associated with rendered voucher, such as value amount, in a larger format than other information rendered in the image of the virtual ticket voucher. This data can be rendered separately from the image of the virtual ticket voucher, such as below the virtual ticket voucher. Further, the information can be rendered as plain text, such as in a spread sheet format, without image data. The voucher management application can include a feature that allows a user to select a format for displaying the data or can be configured to switch formats depending on the amount of data that needs to be displayed.
In one embodiment, a bar-code or other optically formatted image data (e.g., QR code) rendered in an image of a virtual ticket voucher can be used to redeem a virtual ticket voucher. For instance, at a cashier station a user can present their portable electronic device while it is displaying the bar-code. The cashier can scan the bar-code and the information can be sent to a remote server for validation purposes. If the virtual ticket voucher is valid, then the cashier can provide the value associated with the virtual ticket voucher to the person that presented the portable electronic device.
In a particular embodiment, the voucher management application can include print capabilities that allow an image of a virtual ticket voucher to be printed out via a standard printer. In some instances, electronic gaming machines or other redemption devices can be configured to accept virtual ticket vouchers printed in this manner. A user may wish to print out a record of a previously redeemed ticket. For instance, the user can print out a ticket associated with a large payout as a souvenir. If desired, a water mark or some other indication can be added to a redeemed ticket when it is printed to indicate it has already been redeemed.
In another embodiment, the voucher management application can be configured to upload the image of the virtual ticket voucher to be uploaded to a social media site. The voucher management application can be configured to generate the image so that it is non-redeemable, i.e., a portion of the information needed to redeem the voucher is removed or obscured from the rendered image. The information is removed to prevent someone from copying and redeeming a posted image of the virtual ticket voucher.
The voucher management application can be configured to manage virtual vouchers from multiple locations. The application can be configured to group the vouchers according to location. As shown in
The voucher application can be configured to allow the user to optionally share their loyalty program information during the virtual ticket voucher transaction. For instance, if the user actuates the share button, then their loyalty program information can be uploaded to a redemption device, such as an EGM, during the virtual ticket voucher transaction. If the share button is not selected, then the virtual ticket voucher transaction can occur anonymously.
In some instances, the redemption device, such as an EGM, can be configured to require secondary authentication of a virtual ticket voucher. In another example, this feature can be built into the virtual voucher management application. For instance, as shown in interface 232 in
In one embodiment, a second authentication may only be required for transactions above a certain amount, such as $25 dollars. If multiple virtual ticket vouchers are simultaneously redeemed, then the total amount of the transaction based on the value of all of the virtual ticket vouchers being redeemed during the transaction may have to be over a certain amount before secondary authentication is required. An advantage of requiring secondary authentication is that if the portable electronic device is lost or stolen another person may not be able to redeem the virtual ticket vouchers. The voucher management application can be configured to allow a user to back-up their virtual ticket voucher information on another device controlled by the user or a remote storage device in the “cloud.” Thus, using the back-up data, it may be possible for the user to recover and redeem their virtual ticket vouchers if a portable electronic device storing the virtual ticket vouchers is lost or stolen.
In another embodiment, the voucher management application can be configured to convert a physically printed ticket voucher to a virtual ticket voucher. For instance, on a device with a camera, an image can be taken of the printed ticket voucher. The application can be configured to parse information from the printed ticket voucher to create a virtual ticket voucher. Later, the virtual ticket voucher associated with printed ticket voucher can be redeemed for cash or additional game play on a gaming device.
The user can save the printed ticket voucher if desired. If the printed ticket voucher is redeemed before the virtual ticket voucher copy, then a later attempt to redeem the virtual ticket voucher copy will not work because the host system will already have a record that the ticket voucher has been redeemed. If the virtual ticket voucher copy is redeemed before the printed ticket voucher, then a later attempt to redeem the printed ticket voucher will not work because the host system will already have a record that the ticket voucher is redeemed.
In particular embodiments, a gaming device can be configured to issue both a printed ticket voucher and a virtual ticket voucher. The user receiving the printed ticket voucher and the virtual ticket voucher (stored to a device) can then choose which format to use when redeeming the ticket voucher. As an example, a retrofit device or a secondary device on an EGM, such as a card reader, player tracking unit, bill validator or printer, can be configured to issue a virtual ticket voucher when a printed ticket voucher is issued. Thus, the printed ticket voucher can issue normally in response to a cash out request. In addition, the retrofit device or the secondary device can be configured to issue a virtual ticket voucher and communicate the virtual ticket voucher information to a user's portable electronic device.
In yet other embodiment, the voucher management application can be configured to receive an image of a check. Software exists that allows an image of a check to be scanned or a user to take a picture of a check then have the check electronically deposited into a bank account. At a redemption station, rather than receiving cash for a redeemed virtual ticket voucher or a printed ticket voucher, an electronic image or images of a check that can be electronically deposited into a user's bank account can be received via the voucher management application on the user's device. Then, the check can be deposited into the user's bank account. This approach may be preferable to a user than receiving a large amount of cash.
Methods for Managing Virtual Ticket Vouchers on an EGM
Next with respect to
In 304, in response, the EGM can initiate a virtual ticket voucher redemption transaction. In one embodiment, the EGM can be configured to activate an interface, such as a wireless interface enabling wireless communications and change the status of a status indicator to indicate the wireless interface is ready to receive virtual ticket voucher information from a portable electronic device. Then, the EGM can initiate a countdown timer. If the virtual ticket voucher information associated with the transaction within a specific time period, then the EGM can be configured to cancel the transaction. If a wireless interface and a status indicator are used, then the states of these devices can be changed. For instance, the wireless interface can be turned off and the state of the status indicator can be changed to indicate the wireless interface is inactive.
In particular embodiments, the wireless communications can be carried out using a wireless protocol, such as NFC, Bluetooth™ or Wi-Fi™. In one embodiment, a combination of wireless protocols can be used. For instance, an NFC communication can be used to set up a device pairing between the EGM and a portable electronic device that uses Bluetooth™ or Wi-Fi™ compatible communications.
In another embodiment, a wireless interface and status interface may not be used. Instead, via an application executing on a portable electronic device and a previously established communication connection between the EGM and the portable electronic device, the application can begin a transfer of virtual ticket voucher information to the EGM in response to receiving a selection initiating the transfer of virtual ticket voucher information. The selection can be made on an interface associated with the application that is generated on the portable electronic device. In 306, the EGM can receive virtual ticket voucher information from the portable electronic device. If the EGM includes a NFC compatible wireless interface and the portable electronic device is NFC enabled, then the portable electronic device has to be brought into range of the NFC compatible wireless interface, such as within 4 cm or less from the interface to enable the transaction.
In one embodiment, in 308, the EGM can be configured to output a portion of the virtual ticket voucher information to the display. The output of the virtual ticket voucher information can provide an indication that the virtual ticket voucher information has been received by the EGM 2. In a particular embodiment, the EGM 2 can be configured to render an image of a ticket voucher to the display including all or a portion the virtual ticket voucher information. The image can be rendered such that the image is similar in format to a printed ticket voucher. The application executing on the portable electronic device can include options, such as a number of ticket voucher templates, which allow a user to customize the appearance of virtual ticket vouchers rendered on the portable electronic device. In one embodiment, some of the custom appearance information selected by the user can be transferred from the portable electronic device to the EGM to affect an appearance of an image rendered and displayed on the EGM of the virtual ticket voucher. In another embodiment, the virtual ticket voucher appearance information can be retrieved from a loyalty program account when a user provides information, such a loyalty program account number. The information retrieved from the loyalty program account can be used to modify the appearance of virtual ticket vouchers rendered on a display of the EGM.
In 310, the EGM can send virtual ticket voucher information to a remote server for validation purposes. In one embodiment, the virtual ticket voucher information can include unique identification information associated with the portable electronic device. In 312, the EGM can receive an indication from the remote server that the virtual ticket voucher is valid for a particular value amount. In response, the EGM can redeem the virtual ticket voucher for an amount of credits equivalent to the value amount. The EGM can notify the remote device that the virtual ticket voucher has been redeemed and optionally notify the portable electronic device. If the EGM receives an indication from the remote server that the virtual ticket voucher is no longer valid, then the EGM can generate and output a notification message that indicates the virtual ticket voucher is invalid. The notification message can include one or more of 1) outputting a text message to a display on the EGM, 2) changing a state of a status indicator, such as a light array, 3) outputting a sound to an audio device on the EGM and 4) sending a message for output on the portable electronic device.
In 314, the EGM can be configured to store virtual ticket voucher information. In one embodiment, the EGM can store a rendered image of the virtual ticket voucher. In another embodiment, the EGM can update a memory coupled to a cash box with the virtual ticket voucher information. In 316, hard and soft meters affected by the redemption of the virtual ticket voucher can be updated including soft meters for accumulating a number of virtual ticket voucher accepted and a value of the virtual ticket vouchers accepted. In 318, the EGM can display the amount of credits or currency redeemed.
In 320, the EGM can generate a change voucher. If a value of the virtual ticket voucher redeemed results in a fraction of credit based upon a denomination used on the EGM, such as 75 cents remaining on a dollar denomination machine, then the EGM can issue a change voucher. The change voucher is typically issued in a currency amount equivalent to some fraction of a credit. In one embodiment, the EGM can issue a printed ticket voucher for the change amount. In another embodiment the EGM can issue a virtual ticket voucher for the change amount. Details of issuing virtual ticket vouchers are described as follows with respect to
In 322, the EGM can enter into an operator mode. In one embodiment, the EGM can enter into an operator mode in response to an operator inserting an operator key. In 322, in operator mode, the EGM can be configured to display virtual ticket voucher information. For instance, the EGM can be configured to output values for soft meters associated with the virtual ticket vouchers. In another example, the EGM can be configured to display virtual ticket voucher information associated with virtual ticket vouchers accepted by the EGM. In one embodiment, the EGM can be configured to render images of the virtual ticket vouchers and/or printed ticket vouchers received at the EGM. The rendered images can be used for dispute resolution purposes. In particular embodiment, the EGM can be configured to receive portable device identification information, locate virtual ticket vouchers received from the portable electronic and display the virtual ticket voucher information to a display on the EGM or to a display on a portable electronic device carried by the operator.
In 406, the EGM can request virtual ticket voucher information from the remote server. The request can include an amount for the virtual ticket voucher. The virtual ticket voucher information can include a unique ticket validation number and a ticket number. The ticket number can indicate that the ticket voucher is a virtual ticket voucher as opposed to a printed ticket voucher. In 408, the EGM can generate the virtual ticket voucher. In 410, the EGM can transmit virtual ticket information to the portable electronic device and receive information from the portable electronic device, such as device identification information. In one embodiment, if a near field communication interface is used, the transmission can require a user to bring the portable electronic device within a threshold distance of the interface for the transmission to take place. In 412, the EGM can send information received from the portable electronic device to the remote server, such as a portable device identification number. The device information can be associated with the virtual ticket voucher information stored on the remote device. In one embodiment, the device information can be used later in the redemption of the virtual ticket voucher. For instance, unless the correct device information associated with the virtual ticket voucher is received, the remote server won't validate the virtual ticket voucher.
In 414, the EGM can determine the countdown timer has expired and the virtual ticket voucher transaction is not been completed. In response, in 416, the EGM can generate a printed ticket voucher with a value amount the same as the virtual ticket voucher. The EGM may change the ticket number to indicate that a printed ticket voucher is being issued. In addition, the EGM can also notify the remote server that the ticket voucher was issued as printed ticket voucher and not a virtual ticket number. The remote server can change the ticket number associated with the printed ticket voucher to reflect the ticket voucher is a printed ticket voucher. In 418, the EGM can update various soft and/or hard meters depending on the type of ticket voucher issued (virtual or printed) and the value of the ticket voucher.
In 420, the EGM can enter an operator mode, such as for the purposes of reading the soft meters or for dispute resolution. In 422, the EGM can be configured to display virtual ticket voucher information associated with previously issued virtual ticket vouchers. In one embodiment, the EGM can be configured to display both virtual ticket information and printed ticket voucher information for previously issued ticket vouchers. The information can include device information, such as unique device identification information associated with a portable electronic device that received the virtual ticket voucher. In one embodiment, images of the virtual ticket vouchers that are formatted like a printed ticket voucher can be rendered to the display.
Next additional details of EGMs and gaming systems are described with respect to
Some gaming devices, such as 652, 654 and 656, can be configured with a player interface that allows at least 1) selections, such as a wager amount, associated with a wager-based game to be made and 2) an outcome of the wager-based game to be displayed. As an example, gaming devices, 652, 654 and 656, include player interfaces, 652a, 654a and 656a, respectively. Typically, gaming devices with a player interface are located in publically accessible areas, such as a casino floor. On the other hand, some gaming devices, such as server 602, can be located in publically inaccessible areas, such is in a back-room of a casino or even off-site from the casino. Gaming devices located in publically inaccessible areas may not include a player interface. For instance, server 602 does not include a player interface. However, server 602 includes an administrator interface 635 that allows functions associated with the server 602 to be adjusted.
An example configuration of a gaming device is described with respect to gaming device 604. The gaming device 604 can include 1) a game controller 606 for controlling a wager-based game played on the gaming device and 2) a player interface 608 for receiving inputs associated with the wager-based game and for displaying an outcome to the wager-based game. In more detail, the game controller 606 can include a) one or more processors, such as 626, b) memory for holding software executed by the one or more processors, such as 628, c) a power-hit tolerant memory, such as 630, d) one or more trusted memories, such as 632, e) a random number generator and f) a plurality of software applications, 610. The other gaming devices, including table gaming device 652, mobile gaming device 654, slot-type gaming device 656 and server 602, can each include a game controller with all or a portion of the components described with respect to game controller 606.
In particular embodiments, the gaming device can utilize a “state” machine architecture. In a “state” machine architecture critical information in each state is identified and queued for storage to a persistent memory. The architecture doesn't advance to the next state from a current state until all the critical information that is queued for storage for the current state is stored to the persistent memory. Thus, if an error condition occurs between two states, such as a power failure, the gaming device implementing the state machine can likely be restored to its last state prior to the occurrence of the error condition using the critical information associated with its last state stored in the persistent memory. This feature is often called a “roll back” of the gaming device. Examples of critical information can include but are not limited to an outcome determined for a wager-based game, a wager amount made on the wager-based game, an award amount associated with the outcome, credits available on the gaming device and a deposit of credits to the gaming device.
The power-hit tolerant memory 630 can be used as a persistent memory for critical data, such as critical data associated with maintaining a “state” machine on the gaming device. One characteristic of a power-hit tolerant memory 630 is a fast data transfer time. Thus, in the event of a power-failure, which might be indicated by a sudden power fluctuation, the critical data can be quickly loaded from volatile memory, such as RAM associated with the processor 626, into the power-hit tolerant memory 630 and saved.
In one embodiment, the gaming device 605 can be configured to detect power fluctuations and in response, trigger a transfer of critical data from RAM to the power-hit tolerant memory 630. One example of a power-hit tolerant memory 630 is a battery-backed RAM. The battery supplies power to the normally volatile RAM so that in the event of a power failure data is not lost. Thus, a battery-backed RAM is also often referred to as a non-volatile RAM or NV-RAM. An advantage of a battery-backed RAM is that the fast data transfer times associated with a volatile RAM can be obtained.
The trusted memory 632 is typically a read-only memory of some type that may be designed to be unalterable. An EPROM or EEPROM are two types of memory that can be used as a trusted memory 632. The gaming device 604 can include one or more trusted memories. Other types of memories, such as Flash memory, can also be utilized as an unalterable memory and the example of an EPROM or EEPROM is provided for purposes of illustration only.
Prior to installation the contents of a trusted memory, such as 632, can be verified. For instance, a unique identifier, such as a hash value, can be generated on the contents of the memory and then compared to an accepted hash value for the contents of the memory. The memory may not be installed if the generated and accepted hash values do not match. After installation, the gaming device can be configured to check the contents of the trusted memory. For instance, a unique identifier, such as a hash value, can be generated on contents of the trusted memory and compared to an expected value for the unique identifier. If the generated value of the unique identifier and the expected value of the unique identifier don't match, then an error condition can be generated on the gaming device 604. In one embodiment, the error condition can result in the gaming device entering a tilt state where game play is temporarily disabled on the gaming device.
Sometimes verification of software executed on the gaming device 604 can be performed by a regulatory body, such as a government agency. Often software used by a game controller, such as 606, can be highly regulated, where only software approved by a regulatory body is allowed to be executed by the game controller 606. In one embodiment, the trusted memory 632 can store authentication programs and/or authentication data for authenticating the contents of various memories on the gaming device 604. For instance, the trusted memory 632 can store an authentication program that can be used to verify the contents of a mass storage device, such as 620, which can include software executed by the game controller 606.
The random number generator (RNG) 634 can be used to generate random numbers that can be used to determine outcomes for a game of chance played on the gaming device. For instance, for a mechanical or video slot reel type of game, the RNG, in conjunction with a paytable that lists the possible outcomes for a game of chance and the associated awards for each outcome, can be used to generate random numbers for determining reel positions that display the randomly determined outcomes to the wager-based game. In other example, the RNG might be used to randomly select cards for a card game. Typically, as described above, the outcomes generated on a gaming device, such as 604, are considered critical data. Thus, generated outcomes can be stored to the power-hit tolerant memory 630.
Not all gaming devices may be configured to generate their own game outcomes and thus, may not use an RNG for this purpose. In some embodiments, game outcomes can be generated on a remote device, such as server 602, and then transmitted to the gaming device 604 where the outcome and an associated award can be displayed to the player via the player interface 608. For instance, outcomes to a slot-type game or a card game can be generated on server 602 and transmitted to the gaming device 604.
In other embodiments, the gaming device 604 can be used to play central determination games, such as bingo and lottery games. In a central determination game, a pool of game outcomes can be generated and then, particular game outcomes can be selected as needed (e.g., in response to a player requesting to play the central determination game) from the pool of previously generated outcomes. For instance, a pool of game outcomes for a central determination game can be generated and stored on server 602. Next, in response to a request to play the central determination game on gaming device 604, one of the outcomes from the pool can be downloaded to the gaming device 604. A game presentation including the downloaded outcome can be displayed on the gaming device 604.
In other embodiments, thin client type gaming devices, such as mobile gaming devices used to play wager-based video card or video slot games, may be configured to receive at least game outcomes from a remote device and not use an RNG to generate game outcomes locally. The game outcomes can be generated remotely in response to inputs made on the mobile device, such as an input indicating a wager amount and/or an input to initiate the game. This information can be sent from the mobile device to a remote device, such as from mobile gaming device 654 to server 602. After receiving the game outcome from the remote device, a game presentation for the game outcomes generated remotely can be generated and displayed on the mobile device. In some instances, the game presentation can also be generated remotely and then streamed for display to the mobile device.
The game controller 606 can be configured to utilize and execute many different types of software applications 610. Typically, the software applications utilized by the game controller 606 can be highly regulated and may undergo a lengthy approval process before a regulatory body allows the software applications to be utilized on a gaming device deployed in the field, such as in a casino. One type of software application the game controller can utilize is an Operating System (OS). The OS can allow various programs to be loaded for execution by the processor 626, such as programs for implementing a state machine on the gaming device 606. Further, the OS can be used to monitor resource utilization on the gaming device 606. For instance, certain applications, such as applications associated with game outcome generation and game presentation that are executed by the OS can be given higher priority to resources, such as the processor 626 and memory 628, than other applications that can be executing simultaneously on the gaming device.
As previously described, the gaming device 604 can execute software for determining the outcome of a wager-based game and generating a presentation of the determined game outcome including displaying an award for the game. As part of the game outcome presentation one or more of 1) electro-mechanical devices, such as reels or wheels, can be actuated, 2) video content can be output to video displays, 3) sounds can be output to audio devices, 4) haptic responses can be actuated on haptic devices or 5) combinations thereof, can be generated under control of the game controller 606. The peripheral devices used to generate components of the game outcome presentation can be associated with the player interface 608 where the types of devices that are utilized for the player interface 608 can vary from device to device.
To play a game, various inputs can be required. For instance, via input devices coupled to the gaming device 604, a wager amount can be specified, a game can be initiated or a selection of a game choice associated with the play of the game can be made. The software 610 executed by the game controller 606 can be configured to interpret various signals from the input devices, such as signals received from a touch screen controller or input buttons, and affect the game played on the gaming device in accordance with the received input signals. The input devices can also be part of the player interface 608 provided with the gaming device, such as 604.
In other embodiments, the gaming software 610 executed by the game controller 606 can include applications that allow a game history including the results of a number of past games to be stored, such as the previous 10 or 100 games played on the gaming device 604. The game history can be stored to a persistent memory including but not limited to the power-hit tolerant memory 630. The gaming controller 606 can configured to provide a menu (typically, only operator accessible), that allows the results of a past game to be displayed via the player interface 608. The output from the history menu can include a re-creation of the game presentation associated with a past game outcome, such as a video representation of card hand associated with a video poker game, a video representation of a reel configuration associated with a video slot game, and/or raw data associated with the past game result, such as an award amount, an amount wagered, etc. The history menu can be used for dispute resolution purposes, such as if a player complains that they have not been properly awarded for a game previously played on the gaming device 604.
The reporting software can be used by the game controller 606 to report events that have occurred on the gaming device 604 to remote device, such as server 602. For instance, in one embodiment, the game controller 606 can be configured to report error conditions that have been detected on the gaming device 604, such as if a device has malfunctioned or needs attention. For instance, the reporting software can be used to send a message from the gaming device 604 to the server 602 indicating that a printer on the gaming device needs a refill of tickets. In another embodiment, the gaming controller 606 can be configured to report security events that may have occurred on the gaming device 604, such as but not limited to if a door is opened, a latch is activated or an interior portion of the gaming device 604 has been accessed.
In yet other embodiments, the game controller 606 can be configured to report gaming activity and associated events that has been generated on the gaming device, such as a deposit of cash or an indicia of credit, at the gaming device, a generation of game outcome including an associated award amount and a dispensation of cash or an indicia of credit from the gaming device 604. As part of a loyalty program, the gaming activity can be associated with a particular player. The reporting software can include player tracking elements that allow the gaming activity of a particular player to be reported to a remote device, such as server 602.
The game controller 606 can execute the authentication software to verify the authenticity of data and/or software programs executed on the gaming device 604. For instance, the authentication software can be used to verify the authenticity of data and/or software applications when they are first downloaded to the gaming device 604. Further, the authentication software can be used to periodically verify the authenticity of data and/or software applications currently residing on the gaming device, such as software applications stored on one of the memories coupled to the gaming device 604 including applications loaded into the memory 628 for execution by the processor 626.
The communication software executed by the game controller 606 can be used to communicate with a variety of devices remote to the gaming device 604. For instance, the communication software can be used to communicate with one or more of a) servers remote to the device, such as 602, b) other gaming devices, such as table gaming device 652, mobile gaming device 654 and slot-type gaming device 656 and c) mobile devices carried by casino personnel or players in the vicinity of the gaming device 604. Via the communication software, the game controller can be configured to communicate via many different communication protocols. For instance, different wireless and/or wired communication protocols can be implemented. Further, proprietary or non-proprietary gaming specific protocols can be implemented. For instance, gaming specific non-proprietary communication protocols, such as G2S (game to system), GDS (gaming device standard) and S2S (system to system) communication protocols provided by the Gaming Standards Association (GSA), Fremont, Calif., can be implemented on the gaming devices described herein.
The gaming device 604 can communicate with one or more remote devices via one or more network interfaces, such as 612. For instance, via network interfaces 612 and the network 601, the gaming device 604 can communicate with other gaming devices, such as server 602 and/or gaming devices, 652, 654 and 656. The network interfaces can provide wired or wireless communications pathways for the gaming device 604. Some gaming devices may not include a network interface or can be configured to operate in a stand-alone mode where the network interface is not connected to a network.
In other embodiments, a mobile device interface or interfaces, such as 614, can be provided for communicating with a mobile device, such as a cell phone or a tablet computer carried by players or casino personnel temporarily in the vicinity of the gaming device 604. A wireless communication protocol, such as Bluetooth™ and a Wi-Fi compatible standard, can be used for communicating with the mobile devices via the mobile device interfaces 614. In one embodiment, the mobile device interface can implement a short range communication protocol, such as a near-field communication (NFC) protocol used for mobile wallet applications. NFC is typically used for communication distances of 4 cm or less. In addition, a wired communication interface, such as a docking station, can be integrated into the gaming device, such as 604. The wired communication interface can be configured to provide communications between the gaming device 604 and the mobile device and/or providing power to the mobile device.
Near field communication, or NFC, allows for simplified transactions, data exchange, and connections with a touch. Formed in 2004, the Near Field Communication Forum (NFC Forum) promotes sharing, pairing, and transactions between NFC devices and develops and certifies device compliance with NFC standards. NFC's short range helps keep encrypted identity documents private. Thus, a smartphone or tablet with an NFC chip can make a credit card/debit card payment to a gaming device or serve as keycard or ID card for a loyalty program. Further, an NFC device can act a hotel room key. The user of an NFC device as a hotel room keys and/or a player tracking card instrument may allow fast VIP check-in and reduce staffing requirements.
NFC devices can read NFC tags on a gaming device 604 to get more information about the gaming device including an audio or video presentation. For instance, a tap of an NFC enabled device to a gaming device can be used to instantly share a contact, photo, song, application, video, or website link In another example, an NFC enabled device can be used to transfer funds to the gaming device or enter the player in a multi-player tournament. As another example, an NFC enabled device can be used to receive information from a gaming device that can be used in a persistent gaming application or a social media application.
Further, NFC enabled signage can include NFC tags that allow a patron to learn more information about the content advertised in the signage. The NFC enabled signage can be part of a gaming system. For instance, a sign advertising a show available at the casino can be configured to transfer information about the show, show times and ticketing information via an NFC tag. As another example, a sign showing jackpot information, such as progressive jackpot information, can be used to transfer information about the jackpot, such as the last time the jackpot was won and where it was won.
In one embodiment, an NFC interface on a gaming device can be used to set-up a higher speed communication between the gaming device and another NFC enabled device such as smart phone. The higher speed communication rates can be used for expanded content sharing. For instance, a NFC and Bluetooth enabled gaming device can be tapped by an NFC and Bluetooth enabled smart phone for instant Bluetooth pairing between the devices. Instant Bluetooth pairing between a gaming device and an NFC enabled device, such as a smartphone, can save searching, waiting, and entering codes. In another example, a gaming device can be configured as an NFC enabled router, such as a router supporting a Wi-Fi communication standard. Tapping an NFC enabled device to an NFC enabled and Wi-Fi enabled gaming device can be used to establish a Wi-Fi connection between the two devices.
The gaming device 604 can include one or more each of value input devices 616 and value output device 618. The value input devices 616 can be used to deposit cash or indicia of credit onto the gaming device. The cash or indicia of credit can be used to make wagers on games played on the gaming device 604. Examples of value input devices 616 include but are not limited to a magnetic-striped card or smart card reader, a bill and/or ticket acceptor, a network interface for downloading credits from a remote source, a wireless communication interface for reading credit data from nearby devices and a coin acceptor. A few examples of value input devices are shown in
The value output devices can be used to dispense cash or indicia of credit from the gaming device 604. Typically, the indicia of credit can be exchanged for cash. For instance, the indicia of credit can be exchanged at a cashier station or at a redemption station. Examples of value output devices can include a network interface for transferring credits into a remote account, a wireless communication interface that can be used with a mobile device implementing mobile wallet application, a coin hopper for dispensing coins or tokens, a bill dispenser, a card writer, a printer for printing tickets or cards redeemable for cash or credits. Another type of value output device is a merchandise dispenser, which can be configured to dispense merchandise with a tangible value from a gaming device. A few examples of value output devices are shown in
The combination of value input devices 616 and value output devices 618 can vary from device to device. In some embodiments, a gaming device 604 may not include a value input device or a value output device. For instance, a thin-client gaming device used in a mobile gaming application may not include a value input device and a value output device. Instead, a remote account can be used to maintain the credits won or lost from playing wager-based games via the mobile device. The mobile device can be used to access the account and affect the account balance via game play initiated on the mobile device. Credits can be deposited or withdrawn from the remote account via some mechanism other than via the mobile device interface.
In yet other embodiments, the gaming device 604 can include one or more secondary controllers 619. The secondary controllers can be associated with various peripheral devices coupled to the gaming device, such as the value input devices and value output devices described in the preceding paragraphs. As another example, the secondary controllers can be associated with peripheral devices associated with the player interface 608, such as input devices, video displays, electro-mechanical displays and a player tracking unit. In some embodiments, the secondary controllers can receives instructions and/or data from and provide responses to the game controller 606. The secondary controller can be configured to interpret the instructions and/or data from the game controller 606 and control a particular device according to the received instructions and/or data. For instance, a print controller may receive a print command with a number of parameters, such as a credit amount and in response print a ticket redeemable for the credit amount. In another example, a touch screen controller can detect touch inputs and send information to the game controller 606 characterizing the touch input.
In a particular embodiment, a secondary controller can be used to control a number of peripheral devices independently of the game controller 606. For instance, a player tracking unit can include one or more of a video display, a touch screen, card reader, network interface or input buttons. A player tracking controller can control these devices to provide player tracking services and bonusing on the gaming device 604. In alternate embodiments, the game controller 604 can control these devices to perform player tracking functions. An advantage of performing player tracking functions via a secondary controller, such as a player tracking controller, is that since the player tracking functions don't involve controlling the wager-based game, the software on the player tracking unit can be developed modified via a less lengthy and regulatory intensive process than is required for software executed by the game controller 606, which does control the wager-based game. In general, using a secondary controller, certain functions of the gaming device 604 that are not subject to as much regulatory scrutiny as the game play functions can be decoupled from the game controller 606 and implemented on the secondary controller instead. An advantage of this approach, like for the player tracking controller, is that software approval process for the software executed by the secondary controller can be less intensive than the process needed to get software approved for the game controller.
A mass storage unit(s) 620, such as a device including a hard drive, optical disk drive, flash memory or some other memory storage technology can be used to store applications and data used and/or generated by the gaming device 604. For instance, a mass storage unit, such as 620, can be used to store gaming applications executed by the game controller 606 where the gaming device 604 can be configured to receive downloads of game applications from remote devices, such as server 602. In one embodiment, the game controller 606 can include its own dedicated mass storage unit. In another embodiment, critical data, such as game history data stored in the power-hit tolerant memory 630 can be moved from the power-hit tolerant memory 630 to the mass storage unit 620 at periodic intervals for archival purposes and to free up space in the power-hit tolerant memory 630.
The gaming device 604 can include security circuitry 622, such as security sensors and circuitry for monitoring the sensors. The security circuitry 622 can be configured to operate while the gaming device is receiving direct power and operational to provide game play as well as when the gaming device is uncoupled from direct power, such as during shipping or in the event of a power failure. The gaming device 604 can be equipped with one or more secure enclosures, which can include locks for limiting access to the enclosures. One or more sensors can be located within the secure enclosures or coupled to the locks. The sensors can be configured to generate signals that can be used to determine whether secure enclosures have been accessed, locks have been actuated or the gaming device 604, such as a mobile device has been moved to an unauthorized area. The security monitoring circuitry can be configured to generate, store and/or transmit error events when the security events, such as accessing the interior of the gaming device, have occurred. The error events may cause the game controller 606 to place itself in a “safe” mode where no game play is allowed until the error event is cleared.
The server 602 can be configured to provide one or more functions to gaming devices or other servers in a gaming system 600. The server 602 is shown performing a number of different functions. However, in various embodiments, the functions can be divided among multiple servers where each server can communicate with a different combination of gaming devices. For instance, player interface support 636 and gaming device software 638 can be provided on a first server, progressives can be provided on a second server, loyalty program functions 640 and accounting 648 can be provided on a third server, linked gaming 644 can be provided on a fourth server, cashless functions 646 can be provided on a fifth server and security functions 650 can be provided on a sixth server. In this example, each server can communicate with a different combination of gaming devices because each of the functions provided by the servers may not be provided to every gaming device in the gaming system 600. For instance, the server 602 can be configured to provide progressive gaming functions to gaming devices 604, 652 and 656 but not gaming device 654. Thus, the server 602 may not communicate with the mobile gaming device 654 if progressive functions are not enabled on the mobile gaming device at a particular time.
Typically, each server can include an administrator interface that allows the functions of a server, such as 602, to be configured and maintained. Each server 602 can include a processor and memory. In some embodiments, the servers, such as 602, can include a game controller with components, such as but not limited to a power-hit tolerant memory 630, a trusted memory 632 and an RNG 634 described with respect to gaming device 604. The servers can include one or more network interfaces on which wired or wireless communication protocols can be implemented. Next, some possible functions provided by the server 602 are described. These functions are described for the purposes of illustration only and are not meant to be limiting.
The player interface support 636 can be used to serve content to gaming devices, such as 604, 652, 654 and 656, remote to the server. The content can include video and audio content that can be output on one of the player interfaces, such as 608, 652a, 654a and 656a. Further, the content can be configured to utilize unique features of a particular player interface, such as video displays, wheels or reels, if the particular player interface is so equipped.
In one embodiment, via the player interface support, content can be output to all or a portion of a primary video display that is used to output wager-based game outcomes on a player interface associated with a gaming device. For instance, a portion of the primary display can be allocated to providing a “service window” on the primary video display where the content in the service window is provided from a server remote to the gaming device. In particular embodiments, the content delivered from the server to a gaming device as part of the player interface support 636 can be affected by inputs made on the gaming device. For instance, the service window can be generated on a touch screen display where inputs received via the service window can be sent back to server 602. In response, to the received inputs, the server 602 can adjust the content that is displayed on the remote gaming device that generated the inputs.
The “service window” application can be generated by software code that is executed independently of other game controller software in a secure “sandbox.” Via the sandbox, an executable can be given limited access to various resources on an EGM, such as a portion of the CPU resources and memory available on a game controller. The memory can be isolated from the memory used by other processes, such as game processes executed by the game controller.
As described above, a service window application can be allowed to control, send and/or receive data from secondary devices on a gaming device, such as a video display, a touch screen power interfaces or communication interfaces. A service window application allowed to utilize a communication interface, such as a wireless communication interface, can be configured to communicate with a portable electronic device via the communication interface. Thus, a service window application can be configured to implement attract features as described above independently of a game controller on an EGM. Further details of utilizing a service window on a gaming device on an EGM are described in U.S. patent application Ser. No. 12/209,608, by Weber et al., filed Sep. 12, 2008, titled “Gaming Machine with Externally Controlled Content Display,” which is incorporated herein by reference in its entirety and for all purposes.
In another embodiment, via the video display, the service window application can be configured to output data in an optical image format, such as a 1-D/2-D bar-code or a QR code. The optically formatted data can be captured by a camera on the portable electronic device. For instance, a receipt indicating the acceptance of a virtual ticket voucher or virtual currency on the gaming device can be displayed in the service window in a QR code format and transferred to a user's portable electronic device via an image capture device on their portable electronic device. In another embodiment, virtual ticket voucher information can be transferred to a portable electronic device as optically formatted image data.
If a player's identity is known, then the player interface support 636 can be used to provide custom content to a remote gaming device, such as 604. For instance, a player can provide identification information, such as information indicating their membership in a loyalty program, during their utilization of a gaming device. The custom content can be selected to meet the identified player's interests. In one embodiment, the player's identity and interests can be managed via a loyalty program, such as via a loyalty program account associated with loyalty function 640. The custom content can include notifications, advertising and specific offers that are determined to be likely of interest to a particular player.
The gaming device software function 638 can be used to provide downloads of software for the game controller and/or second controllers associated with peripheral devices on a gaming device. For instance, the gaming device software 638 may allow an operator and/or a player to select a new game for play on a gaming device. In response to the game selection, the gaming device software function 638 can be used to download game software that allows a game controller to generate the selected game. In another example, in response to determining that a new counterfeit bill is being accepted by bill acceptors in the gaming system 600, the gaming device software function 638 can be used to download a new detection algorithm to the bill acceptors that allow the counterfeit bill to be detected.
The progressive gaming function 642 can be used to implement progressive game play on one or more gaming devices. In progressive game play, a portion of wagers associated with the play of a progressive game is allocated to a progressive jackpot. A group of gaming devices can be configured to support play of the progressive game and contribute to the progressive jackpot. In various embodiments, the gaming devices contributing to a progressive jackpot may be a group of gaming devices collocated near one another, such as a bank of gaming machines on a casino floor, a group of gaming devices distributed throughout a single casino, or group of gaming devices distributed throughout multiple casinos (e.g., a wide area progressive). The progressive gaming function 642 can be used to receive the jackpot contributions from each of the gaming devices participating in the progressive game, determine a current jackpot and notify participating gaming devices of the current progressive jackpot amount, which can be displayed on the participating gaming devices if desired.
The loyalty function 640 can be used to implement a loyalty program within a casino enterprise. The loyalty function 640 can be used to receive information regarding activities within a casino enterprise including gaming and non-gaming activities and associate the activities with particular individuals. The particular individuals can be known or may be anonymous. The loyalty function 640 can used to store a record of the activities associated with the particular individuals as well as preferences of the individuals if known. Based upon the information stored with the loyalty function 640 comps (e.g., free or discounted services including game play), promotions and custom contents can be served to the particular individuals.
The linked gaming function 644 can be used to used provide game play activities involving player participating as a group via multiple gaming devices. An example, a group of player might be competing against one another as part of a slot tournament. In another example, a group of players might be working together in attempt to win a bonus that can be shared among the players.
The cashless function 646 can enable the redemption and the dispensation of cashless instruments on a gaming device. For instance, via the cashless function, printed tickets, serving as a cashless instrument, can be used to transfer credits from one gaming device to another gaming device. Further, the printed tickets can be redeemed for cash. The cashless function can be used to generate identifying information that can be stored to a cashless instrument, such as a printed ticket, that allows the instrument to later be authenticated. After authentication, the cashless instrument can be used for additional game play or redeemed for cash.
The accounting function can receive transactional information from various gaming devices within the gaming system 600. The transactional information can relate to value deposited on each gaming device and value dispensed from each gaming device. The transactional information, which can be received in real-time, can be used to assess the performance of each gaming device as well as an overall performance of the gaming system. Further, the transactional information can be used for tax and auditing purposes.
The security function 650 can be used to combat fraud and crime in a casino enterprise. The security function 650 can be configured to receive notification of a security event that has occurred on a gaming device, such as an attempt at illegal access. Further, the security function 650 can receive transactional data that can be used to identify if gaming devices are being utilized in a fraudulent or unauthorized manner The security function 650 can be configured to receive, store and analyze data from multiple sources including detection apparatus located on a gaming device and detection apparatus, such as cameras, distributed throughout a casino. In response to detecting a security event, the security function 650 can be configured to notify casino personnel of the event. For instance, if a security event is detected at a gaming device, a security department can be notified. Depending on the security event, one or more team members of the security department can be dispatched to the vicinity of the gaming device. Next, a perspective diagram of a slot-type gaming device that can include all or a portion of the components described with respect to gaming device 604 is described.
Many different configurations are possible between thick and thin clients. For instance, a thick-client device, such as 700, deployed in a central determination configuration, may receive game outcomes from a remote server but still provide cash handling capabilities. Further, the peripheral devices can vary from gaming device to gaming device. For instance, the gaming device 700 can be configured with electro-mechanical reels to display a game outcome instead of a video display, such as 710. Thus, the features of gaming device 700 are described for the purposes of illustration only and are not meant to be limiting.
The gaming device 700 can include a main cabinet 702. The main cabinet 702 can provide a secure enclosure that prevents tampering with the device components, such as a game controller (not shown) located within the interior of the main cabinet and cash handing devices including a coin acceptor 720, a ticket printer 726 and a bill acceptor 718. The main cabinet can include an access mechanism, such as door 704, which allows an interior of the gaming device 700 to be accessed. The actuation of the door 704 can be controlled by a locking mechanism, such as lock 716. The lock 716, the door 704 and the interior of the main cabinet 702 can be monitored with security sensors for detecting whether the interior has been accessed. For instance, a light sensor can be provided to detect a change in light-level in response to the door 704 being opened.
The interior of the main cabinet 700 can include additional secure enclosure, which can also be fitted with locking mechanisms. For instance, the game controller, such as game controller 606, shown in
A top box 706 can be mounted to the top of the main cabinet 702. A number of peripheral devices can be coupled to the top box 706. In
The candle device 714 can include a number of lighting elements. The lighting elements can be lit in different patterns to draw attention to the gaming device. For instance, one lighting pattern may indicate that service is needed at the gaming device 700 while another light pattern may indicate that a player has requested a drink The candle device 714 is typically placed at the top of gaming device 700 to increase its visibility. Other peripheral devices, including custom bonus devices, such as reels or wheels, can be included in a top box 706 and the example in
The gaming device 700 provides a player interface that allows the play of a game, such as wager-based game. In this embodiment, the player interface includes 1) a primary video display 710 for outputting video images associated with the game play, 2) audio devices, such as 722, for outputting audio content associated with game play and possibly casino operations, 3) an input panel 712 for at least providing game play related inputs and 4) a secondary video display 708 for outputting video content related to the game play (e.g., bonus material) and/or the casino enterprise (e.g., advertising). In particular embodiments, one or both of the video displays, 708 and 710, can be equipped with a touch screen sensor and associated touch screen controller, for detecting touch inputs, such as touch inputs associated with the play of a game or a service window output to the display device.
The input panel 712 can include a number of electro-mechanical input buttons, such as 730, and/or touch sensitive surfaces. For instance, the input panel can include a touch screen equipped video display to provide a touch sensitive surface. In some embodiments, the functions of the electro-mechanical input buttons can be dynamically reconfigurable. For instance, the function of the electro-mechanical input buttons may be changed depending on the game that is being played on the gaming device. To indicate function changes, the input buttons can each include a configurable display, such as an e-ink or a video display for indicating the function of button. The output of the configurable display can be adjusted to account for a change in the function of the button.
The gaming device 700 includes a card reader 728, a printer 726, a coin acceptor 720, a bill and/or ticket acceptor 720 and a coin hopper (not shown) for dispensing coins to a coin tray 732. These devices can provide value input/output capabilities on the gaming device 700. For instance, the printer 726 can be used to print out tickets redeemable for cash or additional game play. The tickets generated by printer 726 as well as printers on other gaming devices can be inserted into bill and ticket acceptor 718 to possibly add credits to the gaming device 700. After the ticket is authenticated, credits associated with the ticket can be transferred to the gaming device 700.
The device 718 can also be used to accept cash bills. After the cash bill is authenticated, it can be converted to credits on the gaming device and used for wager-based game play. The coin acceptor 720 can be configured to accept coins that are legal tender or tokens, such as tokens issued by a casino enterprise. A coin hopper (not shown) can be used to dispense coins that are legal tender or tokens into the coin tray 732.
The various aspects, embodiments, implementations or features of the described embodiments can be used separately or in any combination. Various aspects of the described embodiments can be implemented by software, hardware or a combination of hardware and software. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape and optical data storage devices. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art that the specific details are not required in order to practice the invention. Thus, the foregoing descriptions of specific embodiments of the present invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed. It will be apparent to one of ordinary skill in the art that many modifications and variations are possible in view of the above teachings.
The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents.
While the embodiments have been described in terms of several particular embodiments, there are alterations, permutations, and equivalents, which fall within the scope of these general concepts. It should also be noted that there are many alternative ways of implementing the methods and apparatuses of the present embodiments. It is therefore intended that the following appended claims be interpreted as including all such alterations, permutations, and equivalents as fall within the true spirit and scope of the described embodiments.
This application is a continuation of, claims priority to and the benefit of U.S. patent application Ser. No. 16/414,264, filed on May 16, 2019, which is a continuation of, claims priority to and the benefit of U.S. patent application Ser. No. 13/231,275, filed on Sep. 13, 2011, now U.S. Pat. No. 10,297,105, which is a continuation-in-part of, claims priority to and the benefit of U.S. patent application Ser. No. 13/229,536, filed on Sep. 9, 2011, now U.S. Pat. No. 10,121,318, the entire contents of which are each incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3662105 | Parks | May 1972 | A |
| 4071689 | Talmage | Jan 1978 | A |
| 4072930 | Lucero | Feb 1978 | A |
| 4283709 | Lucero | Aug 1981 | A |
| 4339709 | Brihier | Jul 1982 | A |
| 4339798 | Hedges | Jul 1982 | A |
| 4553222 | Kurland | Nov 1985 | A |
| 4856787 | Itkis | Aug 1989 | A |
| 5038022 | Lucero | Aug 1991 | A |
| 5042809 | Richardson | Aug 1991 | A |
| 5048831 | Sides | Sep 1991 | A |
| 5179517 | Sarbin | Jan 1993 | A |
| 5221838 | Gutman | Jun 1993 | A |
| 5371345 | Lestrange | Dec 1994 | A |
| 5429361 | Raven | Jul 1995 | A |
| 5457306 | Lucero | Oct 1995 | A |
| 5470079 | Lestrange | Nov 1995 | A |
| 5483049 | Schulze, Jr. | Jan 1996 | A |
| 5559312 | Lucero | Sep 1996 | A |
| 5618045 | Kagan | Apr 1997 | A |
| 5643086 | Alcorn | Jul 1997 | A |
| 5655961 | Acres | Aug 1997 | A |
| 5676231 | Legras | Oct 1997 | A |
| 5702304 | Acres | Dec 1997 | A |
| 5718632 | Hayashi | Feb 1998 | A |
| 5741183 | Acres | Apr 1998 | A |
| 5759102 | Pease | Jun 1998 | A |
| 5761647 | Boushy | Jun 1998 | A |
| 5768382 | Schneier | Jun 1998 | A |
| 5769716 | Saffari | Jun 1998 | A |
| 5770533 | Franchi | Jun 1998 | A |
| 5779545 | Berg | Jul 1998 | A |
| 5788573 | Baerlocher | Aug 1998 | A |
| 5795228 | Trumbull | Aug 1998 | A |
| 5796389 | Bertram | Aug 1998 | A |
| 5797085 | Beuk | Aug 1998 | A |
| 5809482 | Strisower | Sep 1998 | A |
| 5811772 | Lucero | Sep 1998 | A |
| 5816918 | Kelly | Oct 1998 | A |
| 5818019 | Irwin, Jr. | Oct 1998 | A |
| 5833536 | Davids | Nov 1998 | A |
| 5833540 | Miodunski | Nov 1998 | A |
| 5836819 | Ugawa | Nov 1998 | A |
| 5851148 | Brune | Dec 1998 | A |
| 5871398 | Schneier | Feb 1999 | A |
| D406612 | Johnson | Mar 1999 | S |
| 5885158 | Torango | Mar 1999 | A |
| 5919091 | Bell | Jul 1999 | A |
| 5951397 | Dickinson | Sep 1999 | A |
| 5952640 | Lucero | Sep 1999 | A |
| 5954583 | Green | Sep 1999 | A |
| 5957776 | Hoehne | Sep 1999 | A |
| 5959277 | Lucero | Sep 1999 | A |
| 5967896 | Jorasch | Oct 1999 | A |
| 5971271 | Wynn | Oct 1999 | A |
| 5984779 | Bridgeman | Nov 1999 | A |
| 5999808 | Ladue | Dec 1999 | A |
| 6001016 | Walker | Dec 1999 | A |
| 6003013 | Boushy et al. | Dec 1999 | A |
| 6003651 | Waller | Dec 1999 | A |
| 6010404 | Walker | Jan 2000 | A |
| 6012832 | Saunders | Jan 2000 | A |
| 6012983 | Walker | Jan 2000 | A |
| 6019283 | Lucero | Feb 2000 | A |
| 6038666 | Hsu | Mar 2000 | A |
| 6048269 | Burns | Apr 2000 | A |
| 6050895 | Luciano, Jr. | Apr 2000 | A |
| 6062981 | Luciano | May 2000 | A |
| 6068552 | Walker | May 2000 | A |
| 6077163 | Walker | Jun 2000 | A |
| 6089975 | Dunn | Jul 2000 | A |
| 6099408 | Schneier | Aug 2000 | A |
| 6104815 | Alcorn | Aug 2000 | A |
| 6106396 | Alcorn | Aug 2000 | A |
| 6110041 | Walker et al. | Aug 2000 | A |
| 6113492 | Walker | Sep 2000 | A |
| 6113493 | Walker | Sep 2000 | A |
| 6113495 | Walker | Sep 2000 | A |
| 6135884 | Hedrick | Oct 2000 | A |
| 6135887 | Pease | Oct 2000 | A |
| 6139431 | Walker | Oct 2000 | A |
| 6141711 | Shah | Oct 2000 | A |
| 6142369 | Jonstromer | Nov 2000 | A |
| 6149522 | Alcorn | Nov 2000 | A |
| 6161059 | Tedesco | Dec 2000 | A |
| 6162121 | Morro | Dec 2000 | A |
| 6162122 | Acres | Dec 2000 | A |
| 6174234 | Seibert, Jr. | Jan 2001 | B1 |
| 6182221 | Hsu | Jan 2001 | B1 |
| 6183362 | Boushy | Feb 2001 | B1 |
| 6190256 | Walker | Feb 2001 | B1 |
| 6206283 | Bansal | Mar 2001 | B1 |
| 6210279 | Dickinson | Apr 2001 | B1 |
| 6223166 | Kay | Apr 2001 | B1 |
| 6227972 | Walker | May 2001 | B1 |
| 6244958 | Acres | Jun 2001 | B1 |
| 6247643 | Lucero | Jun 2001 | B1 |
| 6253119 | Dabrowski | Jun 2001 | B1 |
| 6264560 | Goldberg | Jul 2001 | B1 |
| 6264561 | Saffari | Jul 2001 | B1 |
| 6267671 | Hogan | Jul 2001 | B1 |
| 6270410 | Demar | Aug 2001 | B1 |
| 6280328 | Holch | Aug 2001 | B1 |
| 6285868 | Ladue | Sep 2001 | B1 |
| 6293866 | Walker | Sep 2001 | B1 |
| 6302790 | Brossard | Oct 2001 | B1 |
| 6307956 | Black | Oct 2001 | B1 |
| 6319125 | Acres | Nov 2001 | B1 |
| 6341353 | Herman | Jan 2002 | B1 |
| 6368216 | Hedrick | Apr 2002 | B1 |
| 6371852 | Acres | Apr 2002 | B1 |
| 6378073 | Davis | Apr 2002 | B1 |
| 6379246 | Dabrowski | Apr 2002 | B1 |
| 6383076 | Tiedeken | May 2002 | B1 |
| 6409595 | Uihlein | Jun 2002 | B1 |
| 6409602 | Wiltshire | Jun 2002 | B1 |
| 6443843 | Walker | Sep 2002 | B1 |
| 6450885 | Schneier | Sep 2002 | B2 |
| 6488585 | Wells | Dec 2002 | B1 |
| 6496928 | Deo | Dec 2002 | B1 |
| 6530835 | Walker | Mar 2003 | B1 |
| 6561903 | Walker | May 2003 | B2 |
| 6581161 | Byford | Jun 2003 | B1 |
| 6582310 | Walker | Jun 2003 | B1 |
| 6585598 | Nguyen | Jul 2003 | B2 |
| 6628939 | Paulsen | Sep 2003 | B2 |
| 6634550 | Walker et al. | Oct 2003 | B1 |
| 6645075 | Gatto et al. | Nov 2003 | B1 |
| 6648761 | Izawa et al. | Nov 2003 | B1 |
| 6676522 | Rowe et al. | Jan 2004 | B2 |
| 6682421 | Rowe | Jan 2004 | B1 |
| 6685567 | Cockerille | Feb 2004 | B2 |
| 6702670 | Jasper | Mar 2004 | B2 |
| 6739975 | Nguyen | May 2004 | B2 |
| 6758393 | Luciano | Jul 2004 | B1 |
| 6800029 | Rowe | Oct 2004 | B2 |
| 6846238 | Wells | Jan 2005 | B2 |
| 6852031 | Rowe | Feb 2005 | B1 |
| 6869362 | Walker | Mar 2005 | B2 |
| 6880079 | Kefford | Apr 2005 | B2 |
| 6896618 | Benoy | May 2005 | B2 |
| 6905411 | Nguyen et al. | Jun 2005 | B2 |
| 6969319 | Rowe et al. | Nov 2005 | B2 |
| 7004388 | Kohta | Feb 2006 | B2 |
| 7004837 | Crowder et al. | Feb 2006 | B1 |
| 7153210 | Yamagishi | Dec 2006 | B2 |
| 7167724 | Yamagishi | Jan 2007 | B2 |
| 7275991 | Burns | Oct 2007 | B2 |
| 7331520 | Silva | Feb 2008 | B2 |
| 7335106 | Johnson | Feb 2008 | B2 |
| 7337330 | Gatto | Feb 2008 | B2 |
| 7341522 | Yamagishi | Mar 2008 | B2 |
| 7416485 | Walker et al. | Aug 2008 | B2 |
| 7419428 | Rowe | Sep 2008 | B2 |
| 7467999 | Walker et al. | Dec 2008 | B2 |
| 7477889 | Kim | Jan 2009 | B2 |
| 7510474 | Carter, Sr. | Mar 2009 | B2 |
| 7545522 | Lou | Jun 2009 | B1 |
| 7552341 | Chen | Jun 2009 | B2 |
| 7594855 | Meyerhofer | Sep 2009 | B2 |
| 7611409 | Muir et al. | Nov 2009 | B2 |
| 7644861 | Alderucci | Jan 2010 | B2 |
| 7693306 | Huber | Apr 2010 | B2 |
| 7699703 | Muir | Apr 2010 | B2 |
| 7753789 | Walker et al. | Jul 2010 | B2 |
| 7758420 | Saffari | Jul 2010 | B2 |
| 7771271 | Walker et al. | Aug 2010 | B2 |
| 7785193 | Paulsen | Aug 2010 | B2 |
| 7846017 | Walker et al. | Dec 2010 | B2 |
| 7850522 | Walker et al. | Dec 2010 | B2 |
| 7883417 | Bruzzese | Feb 2011 | B2 |
| 7950996 | Nguyen | May 2011 | B2 |
| 7988550 | White | Aug 2011 | B2 |
| 7997972 | Nguyen et al. | Aug 2011 | B2 |
| 8016666 | Angell et al. | Sep 2011 | B2 |
| 8023133 | Kaneko | Sep 2011 | B2 |
| 8038527 | Walker et al. | Oct 2011 | B2 |
| 8057303 | Rasmussen et al. | Nov 2011 | B2 |
| 8079904 | Griswold | Dec 2011 | B2 |
| 8096872 | Walker et al. | Jan 2012 | B2 |
| 8118668 | Gagner et al. | Feb 2012 | B2 |
| 8144356 | Meyerhofer | Mar 2012 | B2 |
| 8157642 | Paulsen | Apr 2012 | B2 |
| 8192276 | Walker et al. | Jun 2012 | B2 |
| 8219129 | Brown | Jul 2012 | B2 |
| 8220019 | Stearns et al. | Jul 2012 | B2 |
| 8282465 | Giobbi | Oct 2012 | B2 |
| 8282490 | Arezina | Oct 2012 | B2 |
| 8286856 | Meyerhofer | Oct 2012 | B2 |
| 8290876 | Powell | Oct 2012 | B1 |
| 8393955 | Arezina et al. | Mar 2013 | B2 |
| 8419548 | Gagner et al. | Apr 2013 | B2 |
| 8469800 | Lemay et al. | Jun 2013 | B2 |
| 8512144 | Johnson et al. | Aug 2013 | B2 |
| 8550903 | Lyons | Oct 2013 | B2 |
| 8597108 | Nguyen | Dec 2013 | B2 |
| 8597111 | Lemay et al. | Dec 2013 | B2 |
| 8602875 | Nguyen | Dec 2013 | B2 |
| 8608569 | Carrico | Dec 2013 | B2 |
| 8613659 | Nelson | Dec 2013 | B2 |
| 8613668 | Nelson et al. | Dec 2013 | B2 |
| 8622836 | Nelson et al. | Jan 2014 | B2 |
| 8721434 | Nelson et al. | May 2014 | B2 |
| 8734236 | Arezina et al. | May 2014 | B2 |
| 8827813 | Lemay et al. | Sep 2014 | B2 |
| 8827814 | Lemay et al. | Sep 2014 | B2 |
| 8876595 | Nelson et al. | Nov 2014 | B2 |
| 8932140 | Gagner et al. | Jan 2015 | B2 |
| 8956222 | Lemay et al. | Feb 2015 | B2 |
| 9011236 | Nelson et al. | Apr 2015 | B2 |
| 9142097 | Rowe | Sep 2015 | B2 |
| 9552693 | Reeves | Jan 2017 | B1 |
| 9824536 | Shorrock et al. | Nov 2017 | B2 |
| 9916735 | Chun | Mar 2018 | B2 |
| 20010039204 | Tanskanen | Nov 2001 | A1 |
| 20010044337 | Rowe | Nov 2001 | A1 |
| 20020020603 | Jones | Feb 2002 | A1 |
| 20020060246 | Gobburu | May 2002 | A1 |
| 20020061778 | Acres | May 2002 | A1 |
| 20020077182 | Swanberg | Jun 2002 | A1 |
| 20020082070 | Macke et al. | Jun 2002 | A1 |
| 20020087641 | Levosky | Jul 2002 | A1 |
| 20020090986 | Cote | Jul 2002 | A1 |
| 20020094869 | Harkham | Jul 2002 | A1 |
| 20020107066 | Seelig | Aug 2002 | A1 |
| 20020111206 | Van Baltz | Aug 2002 | A1 |
| 20020111209 | Walker | Aug 2002 | A1 |
| 20020145035 | Jones | Oct 2002 | A1 |
| 20020147047 | Letovsky | Oct 2002 | A1 |
| 20020147049 | Carter, Sr. | Oct 2002 | A1 |
| 20020163570 | Phillips | Nov 2002 | A1 |
| 20020169623 | Call et al. | Nov 2002 | A1 |
| 20020183046 | Joyce et al. | Dec 2002 | A1 |
| 20020196342 | Walker | Dec 2002 | A1 |
| 20030003988 | Walker | Jan 2003 | A1 |
| 20030008707 | Walker | Jan 2003 | A1 |
| 20030027632 | Sines | Feb 2003 | A1 |
| 20030032485 | Cockerille | Feb 2003 | A1 |
| 20030045354 | Giobbi | Mar 2003 | A1 |
| 20030054868 | Paulsen et al. | Mar 2003 | A1 |
| 20030054881 | Hedrick | Mar 2003 | A1 |
| 20030064805 | Wells | Apr 2003 | A1 |
| 20030074259 | Slyman, Jr. | Apr 2003 | A1 |
| 20030083126 | Paulsen | May 2003 | A1 |
| 20030083943 | Adams | May 2003 | A1 |
| 20030092477 | Luciano et al. | May 2003 | A1 |
| 20030104865 | Itkis | Jun 2003 | A1 |
| 20030141359 | Dymovsky | Jul 2003 | A1 |
| 20030144052 | Walker | Jul 2003 | A1 |
| 20030148812 | Paulsen | Aug 2003 | A1 |
| 20030162591 | Nguyen et al. | Aug 2003 | A1 |
| 20030171145 | Rowe | Sep 2003 | A1 |
| 20030172037 | Jung et al. | Sep 2003 | A1 |
| 20030176213 | Lemay et al. | Sep 2003 | A1 |
| 20030186739 | Paulsen et al. | Oct 2003 | A1 |
| 20030199321 | Williams | Oct 2003 | A1 |
| 20030203756 | Jackson | Oct 2003 | A1 |
| 20030209599 | Gatto | Nov 2003 | A1 |
| 20030224852 | Walker | Dec 2003 | A1 |
| 20030228900 | Yamagishi | Dec 2003 | A1 |
| 20030233276 | Pearlman | Dec 2003 | A1 |
| 20040014514 | Yacenda | Jan 2004 | A1 |
| 20040016797 | Jones | Jan 2004 | A1 |
| 20040023721 | Giobbi | Feb 2004 | A1 |
| 20040039635 | Linde et al. | Feb 2004 | A1 |
| 20040043814 | Angell | Mar 2004 | A1 |
| 20040082384 | Walker et al. | Apr 2004 | A1 |
| 20040085293 | Soper | May 2004 | A1 |
| 20040106454 | Walker | Jun 2004 | A1 |
| 20040127277 | Walker | Jul 2004 | A1 |
| 20040129773 | Lute, Jr. | Jul 2004 | A1 |
| 20040147309 | Chamberlain et al. | Jul 2004 | A1 |
| 20040147314 | Lemay | Jul 2004 | A1 |
| 20040185935 | Yamagishi | Sep 2004 | A1 |
| 20040190042 | Ferlitsch | Sep 2004 | A1 |
| 20040192434 | Walker | Sep 2004 | A1 |
| 20040199284 | Hara | Oct 2004 | A1 |
| 20040209690 | Bruzzese | Oct 2004 | A1 |
| 20040225565 | Selman | Nov 2004 | A1 |
| 20040259640 | Gentles | Dec 2004 | A1 |
| 20040266395 | Pailles | Dec 2004 | A1 |
| 20050014554 | Walker | Jan 2005 | A1 |
| 20050020354 | Nguyen | Jan 2005 | A1 |
| 20050049049 | Griswold et al. | Mar 2005 | A1 |
| 20050054438 | Rothschild | Mar 2005 | A1 |
| 20050059482 | Hedrick et al. | Mar 2005 | A1 |
| 20050059485 | Paulsen | Mar 2005 | A1 |
| 20050070257 | Saarinen et al. | Mar 2005 | A1 |
| 20050076242 | Breuer | Apr 2005 | A1 |
| 20050101383 | Wells | May 2005 | A1 |
| 20050130728 | Nguyen | Jun 2005 | A1 |
| 20050227770 | Papulov | Oct 2005 | A1 |
| 20050240484 | Yan et al. | Oct 2005 | A1 |
| 20050255911 | Nguyen | Nov 2005 | A1 |
| 20050266919 | Rowe et al. | Dec 2005 | A1 |
| 20050287852 | Sugawara | Dec 2005 | A1 |
| 20060018450 | Sandberg-Diment | Jan 2006 | A1 |
| 20060025206 | Walker | Feb 2006 | A1 |
| 20060025222 | Sekine | Feb 2006 | A1 |
| 20060035707 | Nguyen | Feb 2006 | A1 |
| 20060040741 | Griswold | Feb 2006 | A1 |
| 20060046823 | Kaminkow | Mar 2006 | A1 |
| 20060046834 | Sekine | Mar 2006 | A1 |
| 20060046842 | Mattice | Mar 2006 | A1 |
| 20060046855 | Nguyen | Mar 2006 | A1 |
| 20060049624 | Brosnan et al. | Mar 2006 | A1 |
| 20060079315 | Okada | Apr 2006 | A1 |
| 20060079333 | Morrow | Apr 2006 | A1 |
| 20060089174 | Twerdahl | Apr 2006 | A1 |
| 20060135255 | Roth | Jun 2006 | A1 |
| 20060160621 | Rowe | Jul 2006 | A1 |
| 20060165060 | Dua | Jul 2006 | A1 |
| 20060166732 | Lechner | Jul 2006 | A1 |
| 20060166741 | Boyd et al. | Jul 2006 | A1 |
| 20060173781 | Donner | Aug 2006 | A1 |
| 20060189382 | Muir | Aug 2006 | A1 |
| 20060223627 | Nozaki | Oct 2006 | A1 |
| 20060226598 | Walker et al. | Oct 2006 | A1 |
| 20060246981 | Walker | Nov 2006 | A1 |
| 20060247037 | Park | Nov 2006 | A1 |
| 20060266598 | Baumgartner | Nov 2006 | A1 |
| 20060271433 | Hughes | Nov 2006 | A1 |
| 20060279781 | Kaneko | Dec 2006 | A1 |
| 20060281541 | Nguyen et al. | Dec 2006 | A1 |
| 20060281554 | Gatto | Dec 2006 | A1 |
| 20060287072 | Walker | Dec 2006 | A1 |
| 20060287098 | Morrow et al. | Dec 2006 | A1 |
| 20060293929 | Wu | Dec 2006 | A1 |
| 20070017979 | Wu et al. | Jan 2007 | A1 |
| 20070021198 | Muir | Jan 2007 | A1 |
| 20070060302 | Fabbri | Mar 2007 | A1 |
| 20070060372 | Yamagishi | Mar 2007 | A1 |
| 20070077981 | Hungate et al. | Apr 2007 | A1 |
| 20070117608 | Roper et al. | May 2007 | A1 |
| 20070117623 | Nelson | May 2007 | A1 |
| 20070129136 | Walker et al. | Jun 2007 | A1 |
| 20070129150 | Crowder | Jun 2007 | A1 |
| 20070129151 | Crowder | Jun 2007 | A1 |
| 20070155469 | Johnson | Jul 2007 | A1 |
| 20070159301 | Hirt | Jul 2007 | A1 |
| 20070174809 | Brown | Jul 2007 | A1 |
| 20070190494 | Rosenberg | Aug 2007 | A1 |
| 20070202941 | Miltenberger et al. | Aug 2007 | A1 |
| 20070218971 | Berube | Sep 2007 | A1 |
| 20070218985 | Okada | Sep 2007 | A1 |
| 20070218991 | Okada | Sep 2007 | A1 |
| 20070238505 | Okada | Oct 2007 | A1 |
| 20080026816 | Sammon | Jan 2008 | A1 |
| 20080026823 | Wolf | Jan 2008 | A1 |
| 20080026844 | Wells | Jan 2008 | A1 |
| 20080039189 | Walker et al. | Feb 2008 | A1 |
| 20080039190 | Walker | Feb 2008 | A1 |
| 20080070671 | Okada | Mar 2008 | A1 |
| 20080076528 | Nguyen | Mar 2008 | A1 |
| 20080076572 | Nguyen et al. | Mar 2008 | A1 |
| 20080085753 | Okada | Apr 2008 | A1 |
| 20080091616 | Helwin | Apr 2008 | A1 |
| 20080123026 | Kwag | May 2008 | A1 |
| 20080139306 | Lutnick | Jun 2008 | A1 |
| 20080166997 | Sun et al. | Jul 2008 | A1 |
| 20080182644 | Lutnick | Jul 2008 | A1 |
| 20080200251 | Alderucci | Aug 2008 | A1 |
| 20080207296 | Lutnick | Aug 2008 | A1 |
| 20080207307 | Cunningham, II | Aug 2008 | A1 |
| 20080213026 | Grabiec et al. | Sep 2008 | A1 |
| 20080234028 | Meyer | Sep 2008 | A1 |
| 20080261682 | Phillips | Oct 2008 | A1 |
| 20080268934 | Mattice et al. | Oct 2008 | A1 |
| 20080270302 | Beenau et al. | Oct 2008 | A1 |
| 20080274792 | Walker et al. | Nov 2008 | A1 |
| 20080293483 | Pick | Nov 2008 | A1 |
| 20080300061 | Zheng | Dec 2008 | A1 |
| 20080305860 | Linner | Dec 2008 | A1 |
| 20080305862 | Walker | Dec 2008 | A1 |
| 20080305873 | Zheng | Dec 2008 | A1 |
| 20080311971 | Dean | Dec 2008 | A1 |
| 20080318655 | Davies | Dec 2008 | A1 |
| 20090011821 | Griswold | Jan 2009 | A1 |
| 20090023490 | Moshal | Jan 2009 | A1 |
| 20090054149 | Brosnan et al. | Feb 2009 | A1 |
| 20090098943 | Weber et al. | Apr 2009 | A1 |
| 20090124350 | Iddings | May 2009 | A1 |
| 20090125429 | Takayama | May 2009 | A1 |
| 20090131134 | Baerlocher | May 2009 | A1 |
| 20090182634 | Park | Jul 2009 | A1 |
| 20090186680 | Napolitano | Jul 2009 | A1 |
| 20090197684 | Arezina | Aug 2009 | A1 |
| 20090227317 | Spangler | Sep 2009 | A1 |
| 20090233715 | Ergen | Sep 2009 | A1 |
| 20090234773 | Hasson | Sep 2009 | A1 |
| 20090275397 | Van Baltz et al. | Nov 2009 | A1 |
| 20090320106 | Jones et al. | Dec 2009 | A1 |
| 20100012715 | Williams | Jan 2010 | A1 |
| 20100016075 | Thomas | Jan 2010 | A1 |
| 20100036772 | Arceneaux | Feb 2010 | A1 |
| 20100048297 | Dasgupta | Feb 2010 | A1 |
| 20100062840 | Herrmann | Mar 2010 | A1 |
| 20100069160 | Barrett | Mar 2010 | A1 |
| 20100082444 | Lin | Apr 2010 | A1 |
| 20100082491 | Rosenblatt | Apr 2010 | A1 |
| 20100087241 | Nguyen | Apr 2010 | A1 |
| 20100087249 | Rowe | Apr 2010 | A1 |
| 20100093421 | Nyman | Apr 2010 | A1 |
| 20100093429 | Mattice | Apr 2010 | A1 |
| 20100113061 | Holcman | May 2010 | A1 |
| 20100113124 | Amirsadri | May 2010 | A1 |
| 20100113161 | Walker | May 2010 | A1 |
| 20100125509 | Kranzley | May 2010 | A1 |
| 20100173691 | Wolfe | Jul 2010 | A1 |
| 20100174650 | Nonaka | Jul 2010 | A1 |
| 20100178986 | Davis et al. | Jul 2010 | A1 |
| 20100219234 | Forbes | Sep 2010 | A1 |
| 20100227670 | Arezina et al. | Sep 2010 | A1 |
| 20100234099 | Rasmussen et al. | Sep 2010 | A1 |
| 20100250359 | Gillenson | Sep 2010 | A1 |
| 20100250441 | Coppinger | Sep 2010 | A1 |
| 20100250787 | Miyata | Sep 2010 | A1 |
| 20100304848 | Detlefsen | Dec 2010 | A1 |
| 20100323785 | Motyl | Dec 2010 | A1 |
| 20100323789 | Gabriele | Dec 2010 | A1 |
| 20100331079 | Bytnar et al. | Dec 2010 | A1 |
| 20110015976 | Lempel et al. | Jan 2011 | A1 |
| 20110028199 | Luciano et al. | Feb 2011 | A1 |
| 20110065496 | Gagner | Mar 2011 | A1 |
| 20110065497 | Patterson, Jr. | Mar 2011 | A1 |
| 20110076963 | Hatano | Mar 2011 | A1 |
| 20110086691 | Luciano et al. | Apr 2011 | A1 |
| 20110086696 | MacEwan | Apr 2011 | A1 |
| 20110098104 | Meyerhofer | Apr 2011 | A1 |
| 20110112920 | Mestre | May 2011 | A1 |
| 20110118008 | Taylor | May 2011 | A1 |
| 20110119098 | Miller | May 2011 | A1 |
| 20110124353 | Huda | May 2011 | A1 |
| 20110136576 | Kammler | Jun 2011 | A1 |
| 20110191152 | Schwartz | Aug 2011 | A1 |
| 20110207531 | Gagner | Aug 2011 | A1 |
| 20110208418 | Looney et al. | Aug 2011 | A1 |
| 20110213652 | Gillen | Sep 2011 | A1 |
| 20110231238 | Khan | Sep 2011 | A1 |
| 20110231268 | Ungos | Sep 2011 | A1 |
| 20110242565 | Armstrong | Oct 2011 | A1 |
| 20110251962 | Hruska | Oct 2011 | A1 |
| 20110287823 | Guinn et al. | Nov 2011 | A1 |
| 20110295668 | Charania | Dec 2011 | A1 |
| 20110306400 | Nguyen | Dec 2011 | A1 |
| 20110306401 | Nguyen | Dec 2011 | A1 |
| 20110314153 | Bathiche | Dec 2011 | A1 |
| 20120015735 | Abouchar | Jan 2012 | A1 |
| 20120036017 | Hasson | Feb 2012 | A1 |
| 20120046110 | Amaitis | Feb 2012 | A1 |
| 20120054833 | Albisu | Mar 2012 | A1 |
| 20120066048 | Foust et al. | Mar 2012 | A1 |
| 20120084131 | Bergel et al. | Apr 2012 | A1 |
| 20120122584 | Nguyen | May 2012 | A1 |
| 20120122585 | Nguyen | May 2012 | A1 |
| 20120129611 | Rasmussen et al. | May 2012 | A1 |
| 20120136712 | Chang | May 2012 | A1 |
| 20120142403 | Prather | Jun 2012 | A1 |
| 20120149561 | Ribi et al. | Jun 2012 | A1 |
| 20120187184 | Challa | Jul 2012 | A1 |
| 20120187187 | Duff et al. | Jul 2012 | A1 |
| 20120203620 | Dobyns | Aug 2012 | A1 |
| 20120221474 | Eicher et al. | Aug 2012 | A1 |
| 20120252556 | Doyle | Oct 2012 | A1 |
| 20120290336 | Rosenblatt et al. | Nov 2012 | A1 |
| 20130006738 | Horvitz | Jan 2013 | A1 |
| 20130013389 | Vitti et al. | Jan 2013 | A1 |
| 20130017884 | Price | Jan 2013 | A1 |
| 20130023339 | Davis | Jan 2013 | A1 |
| 20130053133 | Schueller | Feb 2013 | A1 |
| 20130053136 | Lemay | Feb 2013 | A1 |
| 20130053148 | Nelson et al. | Feb 2013 | A1 |
| 20130065668 | Lemay et al. | Mar 2013 | A1 |
| 20130065678 | Nelson et al. | Mar 2013 | A1 |
| 20130065686 | Lemay et al. | Mar 2013 | A1 |
| 20130130777 | Lemay et al. | May 2013 | A1 |
| 20130130778 | Anderson et al. | May 2013 | A1 |
| 20130130779 | Gagner | May 2013 | A1 |
| 20130137509 | Weber et al. | May 2013 | A1 |
| 20130137510 | Weber et al. | May 2013 | A1 |
| 20130137516 | Griswold et al. | May 2013 | A1 |
| 20130252713 | Nelson et al. | Sep 2013 | A1 |
| 20130273889 | Lobmaier | Oct 2013 | A1 |
| 20130324237 | Adiraju et al. | Dec 2013 | A1 |
| 20140045586 | Allen et al. | Feb 2014 | A1 |
| 20140087849 | Page | Mar 2014 | A1 |
| 20140221099 | Johnson et al. | Aug 2014 | A1 |
| 20140344043 | Hennessy | Nov 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 1 895 483 | Mar 2008 | EP |
| WO 2007142980 | Dec 2007 | WO |
| WO 2009026320 | Feb 2009 | WO |
| Entry |
|---|
| Canadian Examiner's Report for Canadian Patent Application No. 3,091,507 dated Jul. 26, 2022 (4 pages). |
| Canadian Examiner's Report for Canadian Patent Application No. 3,091,507 dated Oct. 19, 2021 (4 pages). |
| U.S. Appl. No. 13/156,903, filed Jun. 9, 2011. |
| U.S. Appl. No. 13/157,166, filed Jun. 9, 2011. |
| U.S. Appl. No. 13/217,105, filed Aug. 24, 2011. |
| U.S. Appl. No. 13/217,110, filed Aug. 24, 2011. |
| U.S. Appl. No. 13/220,430, filed Aug. 29, 2011. |
| U.S. Appl. No. 13/333,659, filed Dec. 21, 2011. |
| U.S. Appl. No. 13/333,669, filed Dec. 21, 2011. |
| U.S. Appl. No. 13/333,679, filed Dec. 21, 2011. |
| U.S. Appl. No. 13/299,199, filed Nov. 17, 2011. |
| U.S. Appl. No. 13/333,623, filed Dec. 21, 2011. |
| U.S. Appl. No. 13/229,494, filed Sep. 9, 2011. |
| U.S. Appl. No. 13/229,507, filed Sep. 9, 2011. |
| U.S. Appl. No. 13/229,536, filed Sep. 9, 2011. |
| U.S. Appl. No. 13/308,213, filed Nov. 30, 2011. |
| U.S. Appl. No. 13/335,652, filed Dec. 22, 2011. |
| U.S. Appl. No. 13/306,911, filed Nov. 29, 2011. |
| U.S. Appl. No. 13/361,601, filed Jan. 30, 2012. |
| U.S. Appl. No. 13/335,613, filed Dec. 22, 2011. |
| U.S. Appl. No. 13/426/479, filed Mar. 21, 2011. |
| U.S. Office Action for U.S. Appl. No. 13/229,536, dated Jan. 29, 2013, 15 pages. |
| Canadian Office Action for Canadian Patent Application No. 2,790,437 dated Jan. 6, 2020 (3 pages). |
| Canadian Examiner's Report for Canadian Patent Application No. 3,091,507 dated May 17, 2023 (5 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20220044518 A1 | Feb 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16414264 | May 2019 | US |
| Child | 17509943 | US | |
| Parent | 13231275 | Sep 2011 | US |
| Child | 16414264 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13229536 | Sep 2011 | US |
| Child | 13231275 | US |
