Multi-functional peripheral device

Information

  • Patent Grant
  • 12100260
  • Patent Number
    12,100,260
  • Date Filed
    Wednesday, September 19, 2012
    12 years ago
  • Date Issued
    Tuesday, September 24, 2024
    2 months ago
Abstract
A system, apparatus, and method for electronically transferring funds using a multi-functional peripheral device. The multi-functional peripheral device may include a housing, a bezel coupled to an exterior of the housing, and at least one sensor device coupled to the bezel. The at least one sensor device can be configured to detect at least one sensory input.
Description
FIELD OF INVENTION

The present disclosure relates generally to multi-functional peripheral devices. More particularly, the present disclosure relates generally to using the multi-functional peripheral devices in a gaming environment. Even more particularly, the present disclosure relates generally to using the multi-functional peripheral devices in a gaming environment to transfer values such as funds and credits.


BACKGROUND OF INVENTION

Portable electronic devices represent an alternative means to desktop computers to allow users to more conveniently interact with a variety of multimedia services. For example, many portable electronic devices may be configured to allow for the user to interact with multimedia services, messaging services, internet browsing services, telephone services, and the like. Furthermore, the software of portable electronic devices may be configured to be updated so as to allow for the presentation of additional multimedia services or applications. Portable electronic devices may also be configured to have wireless transmission and receiving capabilities so as to permit communication with one or more other sources.


Gaming machines may comprise any number of peripheral devices associated with the act of playing a game of chance. For example, peripheral devices such as a display, bill acceptor, keypad, ticket printer, and user input switches may be used to play a game of chance. Gaming establishments are always looking for new ways and/or gaming options to attract players to increase profits. However, presenting new services on gaming machines may be costly, time-consuming, and generally undesirable for many casinos owners for numerous reasons such as regulatory requirements, maintenance, and the like.


SUMMARY

The disclosure describes a system, apparatus, and method for electronically transferring funds using a multi-functional peripheral device. The multi-functional peripheral device may include a housing, a bezel coupled to an exterior of the housing, and at least one sensor device coupled to the bezel. The at least one sensor device can be configured to detect at least one sensory input.


In one embodiment, a multi-functional peripheral device for use with a gaming device may have a housing, a bezel coupled to an exterior of the housing, at least one sensor device coupled to the bezel, a memory having at least one value transfer program configured to wirelessly transfer funds, and a processor configured to execute the at least one value transfer program in accordance with the at least one sensory input. The at least one sensor device can be configured to detect at least one sensory input. The at least one value transfer program can be configured to wirelessly transfer funds between a portable electronic device and the gaming device.


In one embodiment, a gaming machine for playing a game of chance can include a display configured to present a representation of the game of chance, an input device configured to receive an input used to play the game of chance, and a plurality of peripheral devices configured to perform at least one peripheral function associated with the game of chance. The plurality of peripheral devices may include at least one proximity sensor configured to detect at least one sensory input induced by a portable electronic device.


In one embodiment, a method for transferring values may include: detecting, by a value transfer device, presence of a portable electronic device via a sensory input from the portable electronic device; receiving a value amount; determining, after detecting the sensory input, whether the value amount is to be transferred to the portable electronic device; and transferring the value amount to the portable electronic device if the determining determines the fund amount is to be transferred to the portable electronic device.


In one embodiment, a method for transferring funds to play a game of chance on a portable electronic device may include: detecting, by a first value transfer device, presence of the portable electronic device via a sensory input from the portable electronic device; receiving a fund amount at the first value transfer device; transferring the fund amount to the portable electronic device after detecting the presence of the portable electronic device and receiving the fund amount; and playing a game of chance on the portable electronic device, using at least a portion of the fund amount transferred to the portable electronic device as a wager to play the game of chance.


In one embodiment, a value transfer system can include at least one portable electronic device configured to receive a value, at least one value transfer device, and a gaming server configured to transmit a plurality of gaming information to the at least one portable electronic device. Each of the at least one value transfer devices may include a multifunctional peripheral device having a housing, a bezel coupled to an exterior of the housing, at least one sensor device coupled to the bezel, a memory having at least one value transfer program configured to wirelessly transfer values, a wireless interface configured to communicate with the at least one portable electronic device, and a processor configured to execute the at least one value transfer program in accordance with the at least one sensory input. The at least one sensor device can be configured to detect at least one sensory input. The at least one value transfer program is configured to wirelessly transfer values between the at least one portable electronic device and a gaming device.





BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more example embodiments and, together with the description of example embodiments, serve to explain the principles and implementations.


In the drawings:



FIG. 1 illustrates an embodiment of a system for using a multi-functional peripheral device in a gaming environment.



FIGS. 2A and 2B illustrate example gaming machines.



FIGS. 3A and 3B illustrate example block diagrams of a multifunctional peripheral device.



FIGS. 4A-4B illustrate an embodiment of a multi-functional peripheral device.



FIG. 4C illustrates a block diagram of an exemplary multi-functional peripheral device for use with a value transfer device.



FIG. 4D illustrates a side view of an example multi-functional peripheral device.



FIG. 4E illustrates a side view of another example multi-functional device.



FIG. 5 illustrates an example block diagram of a portable electronic device.



FIGS. 6A-6G illustrate exemplary graphical user interfaces of a portable electronic device for communicating with a gaming machine.



FIG. 7A illustrates an example flow diagram of a method for transferring funds between a portable electronic device and a gaming device.



FIG. 7B illustrates a flow diagram of an example method for transferring funds to and from a portable electronic device.



FIG. 7C illustrates a flow diagram of an example method for transferring funds from a portable electronic device.



FIG. 7D illustrates a flow diagram of an example method for transferring funds to a value transfer device.



FIG. 8 illustrates an exemplary flow diagram of a method for transferring funds from or to a gaming device.



FIG. 9 illustrates an exemplary flow diagram of a method for transferring funds to a gaming device from a portable electronic device.



FIG. 10 illustrates a block diagram of example states of operation for the transfer of funds.



FIG. 11 illustrates an example fund transfer system.



FIG. 12 illustrates an example gaming environment.





DESCRIPTION

Embodiments are described herein in the context of a multi-functional peripheral device. The following detailed description is illustrative only and is not intended to be in any way limiting. Other embodiments will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts.


In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.


In accordance with one or more embodiments, the components, process steps, and/or data structures may be implemented using various types of operating systems, computing platforms, computer programs, and/or general purpose machines. In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein.


The disclosure describes a system, apparatus, and method for communicating information between a gaming device and a portable electronic device using a multi-functional peripheral device associated with the gaming device. The multi-functional peripheral device may include a sensor to detect sensory input from the user and/or the portable electronic device associated with the user to play a game of chance on the gaming device.



FIG. 1 illustrates an embodiment of a system for using a multi-functional peripheral device in a gaming environment. Although described with use in a gaming environment, this is not intended to be limiting as the multi-functional peripheral device may be used in other environments such as in grocery stores, banks, merchant stores, and the like. The system 100 may include a multi-functional peripheral device 102 associated with a gaming device 106. The multi-functional peripheral device 102 may have a multi-functional peripheral device processor 104 and at least one sensor device 116. The multi-functional peripheral device 102 may be configured to communicate with at least one portable electronic device 110 via wireless interface 108. The gaming device 106 may be configured to communicate with a gaming server 112 via network 114. Although illustrated with one gaming device 106 and one portable electronic device 110, this is not intended to be limiting as any number of gaming machines and portable electronic devices may be used.


Typically, the multi-functional peripheral device 102 serves as a peripheral device for gaming machine or device 106. The multi-functional peripheral device 102 can include a multi-functional peripheral device controller or processor 104 that is configured to control operation of the multi-functional peripheral device 102. In one embodiment, the multi-functional peripheral device 102 supports not only a base peripheral function but also one or more additional peripheral functions. The multi-functional peripheral device 102 can thus be used to replace an existing peripheral device and can serve to provide additional capabilities beyond that available in the existing peripheral device, as further described with reference to FIGS. 3A and 3B.


The multi-functional device 102 may have at least one sensor device 116 configured to receive and/or detect at least one sensory input by the at least one portable electronic device 110. The at least one sensory device 116 may be any known device configured to detect and/or receive a sensory input. For example, the at least one sensor device 116 may be an accelerometer, camera, touch screen display, microphone, touchpad, retina scanner, radio frequency identification reader, near-field magnetic reader, proximity sensor, infrared sensor, thermal sensor, switch, magnetic sensor, RF sensor, or any other device capable of receiving and detecting sensory input such as a vibration, displacement, or any other sensory input.


The sensory input may be any type of known sensory input such as an audio, visual, and/or physical contact received from a user. The type of sensory input received or detected may be based on the sensory device. For example, a user may physically contact the sensor device 116 via a tap, touch, or any other physical contact on a touchpad. The physical contact may initiated by the user (e.g. using a finger to tap the sensor device 116), physical object (e.g. pen, coin, and the like), and/or a remote device associated with the user. The remote device may, for example, be any portable computing device such as a cellular phone, portable media player, personal digital assistant (PDA), and the like. In another embodiment, the sensory input may be an audio input received by a microphone associated with the multi-functional peripheral device 102.


In general, the sensory input may need to be in close proximity to the sensory device for transmission. For example, a user's voice may be in close to the microphone in order for the sensory input (i.e. user's voice) to be received by the microphone. In another example, a user's touch may need to physically contact the touchpad, a tap may need to vibrate an accelerometer, a player gesture may need to be in the camera's focus in order to be received by the camera, and the like. This type of proximity sensing may be desired for secured transactions (e.g., pairing a portable electronic device to the gaming device, logging in to a player's account, fund or value transfer, authentication, and the like).


The sensor device 116 may detect the sensory input and transmit a notification of the sensory input to the multi-functional peripheral device processor 104. In one embodiment, multi-functional peripheral device 102 may also receive a transmission from the at least one portable electronic device 110 via wireless interface 108. Wireless interface 108 may be any known wireless methods or device such as a 3G wireless technology, 4G wireless technology, Bluetooth, Wireless USB, Near-field magnetic, Fire Wire, WiMax, IEEE 802.11x technology, radio frequency, and the like.


The transmission may be contextual based and associated with or correspond to the sensory input received by the multi-functional peripheral device 102. For example, if the sensory input was received in the context of playing a game of chance on the gaming machine, the transmission may correspond to an action to play the gamine of chance, such as cashing out, dealing, playing a maximum bet, redeeming a game promotional voucher, and the like. In another example, if the sensory input was received in the context of transferring fund or value, the transmission may be a confirmation to transfer the funds to the gaming machine. In still another embodiment, if the sensory input was received in the context of gaming establishment services, the transmission may be a reservation request for a table in a restaurant, a seat in a tournament, or a request to buy tickets to watch a movie. The value in this case may be the fund transferred (e.g., cash or credit), a redemption of a promotional coupon for a discount, and the like. In general, value can be defined as funds, credits, player points, discounts, upgrade of services, digital merchandise (e.g., a song, a movie ticket, an entry into a lottery game, a game virtual asset, a free spin on a slot machine, and the like), promotional credits, or anything of benefit to the player.


Gaming server may 112 may be configured to communicate with player tracking server 124, location server 132, and authentication server 130. In one embodiment, player tracking server 124 may be configured to collect player data as well as determine a location of a customer within a gaming environment. Player tracking sever 124 may have a database configured to store player tracking information such as name, games the player likes to play, accumulated and used points, number of wins and losses, and the like. Player tracking server 124 may also be configured to store the location of all gaming machines within the gaming environment such that if a player inputs their player tracking card in a gaming machine, the player's gaming activities as well as the location of the player may be tracked.


In another embodiment, if the player is an anonymous player, location server 132, may be used to locate the location of the player in the gaming environment and assign an arbitrary identification (ID) to the anonymous player. Whether the player is an anonymous player or a player having a player tracking account, the location server 132 may include a database containing the location of all gaming devices (stationary and mobile gaming devices) in the gaming environment. Location server 132 may locate players within the gaming environment using any known wireless location methods such as global positioning systems (GPS), indoor Wi-Fi triangulations, and the like. In one embodiment, location server 132 may be configured to locate the position of the player using a portable electronic device of the player 110 and the location of the nearest gaming device 106. In another embodiment, the location server 132 may be configured to locate the player in the gaming environment using only the portable electronic device of the player 110.


Authentication server 130 may be used to authenticate and/or verify the player, gaming device 106, the digital content being transferred, and/or the at least one portable electronic device 110. Any known authentication methods may be used, such as public-private key authentication algorithms, random number generators, authentication keys, and the like, as further discussed below.


In one embodiment, authentication server 130 may have a memory (not shown) having a location verification program configured to conduct verification and/or authorization for gaming and non-gaming activities, such as to authorize a fund or value transfer request based upon the location of the gaming devices. Memory may also have a rules database configured to store a plurality of local jurisdictional gaming rules. Authentication server 132 may be configured to communicate with location server 132 to obtain the location of all gaming devices (stationary and mobile gaming devices) in the gaming environment. Based upon the location of the gaming devices, authentication server 132 may determine if the tracked location of the portable electronic device and the multi-functional peripheral device conflict with at least one of the plurality of jurisdictional gaming rules. If authentication server 132 determines that the tracked location of the portable electronic device and the multi-functional peripheral device conflicts with at least one of the plurality of jurisdictional gaming rules, the fund or value transfer request (or any other request) may be disallowed. If authentication server 132 determines that the tracked location of the portable electronic device and the multi-functional peripheral device do not conflict with at least one of the plurality of jurisdictional gaming rules, the funds transfer request (or any other request) may be allowed. For example, some local state rules may only allow the maximum transfer of $100.00 to a gaming machine. Authentication server 132 may receive a fund or value transfer request for $150.00. Since the funds transfer request is greater than the $100 maximum transfer limit, authentication server 132 may disallow the funds transfer request.


Gaming device 106, gaming server 112, and/or multi-functional peripheral device 102 may also be configured to communicate with a third party server 120. Third party server 120 may be any server necessary to carry out, assist, or perform the at least one request received by the portable electronic device such as a banking server, merchant server, credit card server, advertisement server, and the like. For example, if the request received by the multi-functional peripheral device 102 is a request to transfer funds from the player's bank account to the gaming device 106, the third party server 120 may be the player's banking server. In another example, if the request received by the multi-functional peripheral device 102 is a request to charge $100 to the a credit card of the player, the third party server 120 may be a credit card server. In still another example, if the request received by the multi-functional peripheral device 102 is a request to debit a merchant card, such as a gift card, the third party server 120 may be a merchant server.



FIG. 2A illustrates a perspective view of an example gaming machine. The gaming machine 200 may include a main cabinet 202. The main cabinet 202 may include a main door 204, which may be configured to open to provide access to an interior of the gaming machine. The main door 204 may have a plurality of peripheral devices. The plurality of peripheral devices may include at least one button or switch 206 configured to receive player input or command, a display 208, a secondary display 212, a speaker 214, a ticket printer 216, a keypad 218 for entering player tracking information, a player tracking device 220, a coin acceptor 226, and a multi-functional peripheral device 228 including at least one sensor device 213. The gaming machine 200 may be configured to display a game of chance on the display 208 and/or the secondary display 212. The game of chance may be any game of chance, including but not limited to, video poker, video blackjack, video keno, video slot games, and any other theme. Although illustrated as a stationary physical slot machine, a gaming device can also be a portable electronic device such as a smart phone, a tablet computer, PDA, a laptop computer, a handheld media player, a table game, and the like.


Player inputs may be detected from the at least one button or switch 206. When selected, the gaming machine may detect the input and transmit the input to the gaming machine processor. For example, the button 206 may be used to increase or decrease a betting amount. In another embodiment, the display 208 may be a touch screen display such that the user may input selections via the display 208. The display 208 may be, for example, one of a cathode ray tube, high resolution flat-panel liquid crystal display (“LCD”), a plasma display, a light-emitting diode (“LED”) display, or any other monitor and/or display configured to present information and/or allow the user to play a game of chance. The display 208 may include one or more display windows to allow for multiple games or multiple services to be provided simultaneously to a user.


A top box 210 may be designed to house a plurality of peripheral devices, including but not limited to the secondary display 212 and the speakers 214. During certain gaming events, the gaming machine 200 may be configured to display a plurality of visual and auditory effects that are perceivable by the user. Such visual effects may be displayed via the display 208 and the secondary display 212. The plurality of auditory and visual effects may serve to enhance user experience during game play. The secondary display 212 may be, for example, a cathode ray tube, high resolution flat-panel LCD, a plasma display, an LED display, or any other monitor and/or display configured to present information and/or allow the user to play a game of chance. The secondary display 212 may be configured to present a bonus game, services, video player, tournaments, move times, or any other information. Audio effects may be presented via the speakers 214.


The main cabinet 202 may include the ticket printer 216 configured to print an electronically-readable ticket 224, the keypad 218 for entering player tracking information, the player tracking device 220, the coin tray 222, the coin acceptor 226, and the multi-functional peripheral device 228. Following a completion of a gaming session, the ticket printer 216 may be configured to print an electronically-readable ticket 224. The electronically-readable ticket 224 provides one means of dispensing currency to the player when they are ready to “cash out”. The electronically-readable ticket 224 may also include information relating to the gaming session, including a cash-out amount, a validation number, a gaming venue, a print date and time, gaming machine identification (ID) number, or any other relevant content.


The surface of the electronically-readable ticket 224 may also include a bar code. When the electronically-readable ticket 224 is inserted into a gaming machine, the bar code may be read and processed by another gaming machine so as to derive relevant content related to a prior gaming session. The electronically-readable ticket 224 may be either accepted by the multi-functional peripheral device 228 so as to add previously accumulated credits of another gaming machine to the existing credits or the electronically-readable ticket 224 may be exchanged for cash.


The multi-functional peripheral device 228 may be configured to perform a plurality of gaming and non-gaming functions. In one embodiment, the multi-functional peripheral device 228 may be configured to control and command and/or request the printer to print the electronically-readable ticket 224. In one example, the multi-functional device 228 may include a printer to print the electrically-readable ticket. In another embodiment, the multi-functional peripheral device 228 may be configured to accept cash of a variety of currency or denomination as well as the electronically-readable ticket 224 having a cash value. In another example, the multi-functional device may be used to authenticate the user, conduct social networking functions, act as a wireless communication gateway with portable electronic devices, transfer funds, redeeming a voucher, and other gaming or non-gaming activities or functions.


The multi-functional peripheral device 228 may have at least one sensor device 213. The at least one sensor device 213 can be any device that can detect a sensory input from a user. The at least one sensor device may be an accelerometer, a camera, a microphone, a touchpad, a switch, a touch screen, radio frequency identification reader, a thermal sensor, an IR detector, near-field magnetic reader, and the like. The at least one sensor device 213 may be configured to communicate with a processor of the multi-functional peripheral device 228. In one example, the sensory input may be a predefined user action that may be associated with a gaming or non-gaming function. For example, a sensory input for one tap on a touch pad may be associated with a request to transfer funds. In another example, a sensory input for two taps on a touch pad may be associated with a “Hit” request while playing a video black jack game of chance. In still another example, a sensory input of one tap detected by an accelerometer may be associated with a confirmation to cash out of the gaming machine. It will now be known that many other combinations and/or predefined actions may be possible and are contemplated.


The secondary display 212, the keypad 218, and the player tracking device 220 may, in conjunction, comprise a player tracking service to provide for the accurate recording of information obtained during the gaming session. The player tracking service may display information relevant to the player's preferences as based on the recorded information on the secondary display 212. The player tracking service may be initiated when a magnetic striped card containing player tracking information is inserted into the player tracking device 220 and a personal identification number (PIN) is entered using the keypad 218. During the player tracking session, commands made by the player may be recorded such as in a memory (e.g. non-volatile random access memory (NVRAM), flash memory, dynamic random access memory (“DRAM”)) on the gaming machine, a player tracking server, or in any other data storage device. For example, during the player tracking session, the player tracking software may monitor the amount of time and activity that the player spends at a particular gaming machine, derive timely and accurate marketing information, and subsequently present commercialization opportunities based on that player's gaming preferences.



FIG. 2B illustrates an example block diagram of a gaming device. The gaming device 240 can have a processor 242 configured to communicate with a multi-functional peripheral device 244, a memory 250, a printer 252, and a display 256. Although illustrated with specific components, this is not intended to be limiting as any other components may be used, such as an informational display, secondary display, progressive meters, human interface devices, camera, microphone, player tracking device, bill acceptor, and the like.


The multi-functional peripheral device 244 may have at least one sensor device 254. The at least one sensor device 254 can be any device that can detect a sensory input from a user. The at least one sensor device may be an accelerometer, a camera, a microphone, a touchpad, a touch screen, radio frequency identification reader, near-field magnetic reader, fingerprint reader, and the like. The at least one sensor device 254 may be configured to communicate with a processor of the multi-functional peripheral device 244. In one example, the sensory input may be a predefined user action that may be associated with a gaming or non-gaming function. For example, a sensory input for one tap on a touch pad may be associated with a request to transfer funds. In another example, a sensory input for two taps on a touch pad may be associated with a “Hit” request while playing a video black jack game of chance. In still another example, a sensory input of one tap detected by an accelerometer may be associated with a confirmation to cash out of the gaming machine. It will now be known that many other combinations and/or predefined actions may be possible and are contemplated.


Display 256 may be a touch screen display such that the user may input selections via display 256. Display 256 may be display 212 or 208 as illustrated in FIG. 2A. Display 256 may be any type of display configured to present or display information, data, a game of chance, or the like. For example, display 256 may be one of a cathode ray tube, high resolution flat-panel liquid crystal display (“LCD”), a plasma display, a light-emitting diode (“LED”) display, or any other monitor and/or display configured to present information and/or allow the user to play a game of chance. The display 256 may include one or more display windows to allow for multiple games or multiple services to be provided simultaneously to a user.


Memory 250 may be type of memory capable of storing data such as game data, game play information, paytables, and the like. Memory 250 may be any type of memory such as dynamic random access memory (DRAM), flash memory, non-volatile random access memory (NVRAM), and the like. Printer 252 may be any type of printer capable of providing receipts, electronically-readable tickets, and the like.



FIGS. 3A and 3B illustrate example block diagrams of a multifunctional peripheral device. Referring to FIG. 3A, typically, the multi-functional peripheral device 300 serves as a peripheral device for a gaming machine. The multi-functional peripheral device 300 can include a peripheral controller 302 that is configured to control operation of the multi-functional peripheral device 300. The peripheral controller 302 can be coupled to a peripheral hardware A 304 and a peripheral function A 306. The peripheral controller 302 can also be coupled to a peripheral hardware B 308 and a peripheral function B 310. In one implementation, the multi-functional peripheral device 300 supports two primary functions, such as a first primary function and a second primary function. The peripheral hardware A 304 and the peripheral function A 306 can be used by the first primary function, while the peripheral hardware B 308 and the peripheral function B 310 can be used by the second primary function.


The gaming machine can include one or more integrated single function peripherals, such as a bill acceptor, a player tracking peripheral, a voucher printer, camera, touch screen, sensory input device (e.g., motion sensor, accelerometer, and the like), user input devices (e.g., buttons and switches), and any other single function peripheral devices. In the multi-functional peripheral device 300, the multiple functions can be consolidated in a single peripheral device. In the multi-functional peripheral device 300, the peripheral device is able to include functionality to operate as two or more function peripherals. As one example, the multi-functional peripheral 300 can provide player tracking and a camera (e.g., for user detection, user authentication, user input, such as gesture recognition, and other gaming or non-gaming functions). As another example, the multi-functional peripheral 300 can provide bill acceptance capabilities and a sensory input device (e.g., accelerometer, camera, touchpad, and the like). In yet another embodiment, the multi-functional peripheral 300 can provide credit/debit/cash card reading and electronic signature capability. In still another embodiment, the multi-functional peripheral device 300 can provide bill acceptance capabilities and voucher printing.


In one embodiment, the multi-functional peripheral device 300 can serve as a peripheral that is added to the gaming machine. The multi-function peripheral device 300 can also replace a legacy peripheral device such as the prevalent single-function bill acceptor, player tracking unit, printer, and any other peripheral device. The multi-functional peripheral device 300 can be integrated with the gaming machine or can be external but connected to the gaming machine via any wired or wireless methods such as such as universal serial bus, Ethernet, Serial Advanced Technology Attachment (SATA), 3rd Generation (“3G”) wireless technology, 4th Generation (“4G”) wireless technology, Fire Wire, Worldwide Interoperability for Microwave Access (“WiMax”), IEEE 802.11x technology, Near-Field Magnetic Network, radio frequency, and the like.


As previously noted, the multi-functional peripheral device 300 can be a peripheral for the gaming machine. The multi-functional peripheral device 300 can be either a new peripheral device or a replacement peripheral device. When the multi-functional peripheral device 300 is a replacement peripheral device, the multi-functional peripheral device 300 typically includes not only the peripheral function of a peripheral device being replaced but also a least one new peripheral function. Although discussed with use in the gaming machine, this is not intended to be limiting as the multi-functional peripheral device 300 may be used in other technologies and fields such as a banking machine, drink and snack machines, and the like.



FIG. 3B is a block diagram of a multi-functional peripheral device 320 according to another embodiment. Typically, the multi-functional peripheral device 320 serves as a peripheral device for a gaming machine. The multi-functional peripheral device 320 can include a peripheral controller 322 that is configured to control operation of the multi-functional peripheral device 320. The peripheral controller 322 can be coupled to a base peripheral hardware 324 and 326, and a base peripheral function(s) 328. In one implementation, the multi-functional peripheral device 320 supports not only a base peripheral function but also one or more additional peripheral functions. To support at least one additional function, the multi-functional peripheral device 320 can also include an additional peripheral hardware 330 and 332, and an additional peripheral function(s) 334. The peripheral controller 322 can also be coupled to the additional peripheral hardware 330, the additional peripheral hardware 332, and to the additional peripheral function(s) 334.


The multi-functional peripheral device 320 can thus be used to replace an existing peripheral device. Here, the base peripheral hardware 324 and 326 and the base peripheral function(s) 328 can serve to enable the multi-functional peripheral device 320 to in effect provide (at least) the same capabilities as the existing peripheral device. Moreover, the additional peripheral hardware 330 and 332 and the additional peripheral function(s) 334 can serve to provide the multi-functional peripheral device 320 with additional capabilities beyond that available in the existing peripheral device. In one implementation, the multi-functional peripheral device 320 can have the same form factor as the existing peripheral device so that the multi-functional peripheral device 320 is conveniently able to be swapped for the existing peripheral device.



FIGS. 4A-4B illustrate an embodiment of a multi-functional peripheral device. FIG. 4A illustrates a perspective view of an example multi-functional peripheral device. In one embodiment, as illustrated, the multi-functional peripheral device 400 may be a bill acceptor. The multi-functional peripheral device 400 may be encased in a housing 406 to encase at least one sensory device such as an accelerometer 414, a camera 412, and a value receiving device 404. The multi-functional peripheral device 400 may also have at least one display 408 to display information and data to the user. Although illustrated with three sensor devices, this is not intended to be limiting as any number and/or types of sensor device may be used such as a microphone, touchpad, retina scanner, radio frequency identification reader, thermal sensor, near-field magnetic reader, or any other device capable of receiving and detecting sensory input. For instance, the touchpad could be integrated to give the bill acceptor electronic signature capturing capability.


The at least one display 408 may be any type of display configured to present or display information, data, instructions, successful or error notifications, transferred fund amounts, and the like. The at least one display 408 may be one of a cathode ray tube, high resolution flat-panel LCD, a plasma display, an LED display, touch screen, or any other similar type of display. In one example, the at least one display 408 may present gaming and non-gaming related events and promotions offered by a gaming establishment such as future contests, tournaments, restaurant specials, discounts at stores, and the like. The at least one display 408 may further include a touch screen to capture player inputs.


Value receiving device 404 may be configured to accept multiple forms of credit and values. For example, value receiving device 404 may be configured to accept monetary bills of varying currency, types, and denominations, credit cards, cash cards, electronically-readable tickets, paper vouchers, digital vouchers (e.g., digital version of the paper voucher presented on a portable electronic device's display, a digital file, a script, and the like), an RFID tag, and the like. In one embodiment, value receiving device 404 may include a scanner (e.g. scanner 434 as illustrated in FIG. 4B) to detect the currency, credit card, and/or tickets. In another embodiment, value receiving device 404 may include a card reader to read smartcards, magnetic stripe cards, RFID cards, near-field magnetic cards, and the like. In yet another embodiment, value receiving device 404 may include one or more RF transceivers to receive digital transmissions that represent digital vouchers that contain all the data needed to complete the transaction (e.g., transaction identification (ID), casino ID, amount of credit, time, expiration date, value of voucher, player ID, and the like).


The camera 412 may be any device capable of capture images and video. In one embodiment, the camera 412 may allow the multi-functional device 400 to authenticate a user or portable electronic device, scan the barcode of a paper voucher, scan a barcode displayed on the portable electronic device, assist a player to play a game of chance on the gaming device, conduct video conferencing, and perform other gaming or non-gaming functions. For example, the camera 412 may be a smart camera configured to conduct facial recognition of the player for authentication and/or verification purposes. For example, the camera 412 may take a picture of the player, which is transmitted to authentication server (e.g. authentication server 130 as illustrated in FIG. 1) from multi-functional peripheral device 400. Authentication server may then compare the picture with other pictures in its database for a match.


In another example, the camera 412 may be used to assist the user to play a gaming of chance on the gaming machine. Camera 412 may detect user gestures which represent and/or are associated with at least one gaming function to play the game of chance. In one example, in a video black jack game, the user may move his hands horizontally to “Stand” or move his hands vertically to “Hit”. The camera 412 may detect such sensory inputs and transmit them to the multi-functional peripheral device 400 for processing.


An accelerometer 414 may be configured to detect sensory input. The accelerometer 414 may be any device used to detect movement, displacement, and the like such as a piezoelectric accelerometer, shear mode accelerometer, thermal accelerometer, bulk micro-machined capacitive accelerometer, capacitive spring mass base accelerometer, and the like. The accelerometer 414 may be configured to detect the sensory input and transmit notification of the input to the multi-functional peripheral device 400 for processing. In one example, the accelerometer 414 may be configured to assist the user with a transfer of funds to or from the gaming machine as further described in detail with reference to FIGS. 6-9.


In another example, accelerometer 414 may be configured to assist the user in playing a gaming of chance on the gaming machine. For example, accelerometer 414 may detect user gestures which represent and/or are associated with at least one gaming function to play the game of chance. In one example, in a video black jack game, the user may tap the accelerometer once to “Hit”, twice to “Stand”, and three times to “Double Down”. The accelerometer 414 may detect such sensory inputs and transmit them to the multi-functional peripheral device for processing.



FIG. 4B Illustrates a block diagram of the multi-functional peripheral device illustrated in FIG. 4A. The multi-functional peripheral device 420 may have a processor 422 configured to communicate with at least one sensory device such as an accelerometer 414, a camera 412, and a scanner 434. Scanner 434 may be used in conjunction with value receiving device 404 illustrated in FIG. 4A.


The multi-functional peripheral device 420 may also have a wireless interface 430 configured to communicate with remote computing devices such as a portable electronic device (e.g. portable electronic device 110 illustrated in FIG. 1 and portable electronic device 500 illustrated in FIG. 5). Wireless interface 430 may be any known wireless methods or device such as a 3G wireless technology, 4G wireless technology, Bluetooth, Wireless USB, Near-field magnetic, Fire Wire, WiMax, IEEE 802.11x technology, radio frequency, and the like.


Multi-functional peripheral device 420 may also have a memory 424 storing a database 432. Memory 324 may be any memory configured to store information or data such as non-volatile random access memory (NVRAM), dynamic random access memory (DRAM), Ferroelectric Random Access Memory (FRAM), Electrically Erasable Programmable Read-Only Memory (E2PROM), flash memory, a disk drive, and the like.


Database 432 may be configured to store data and software programs such as a funds transfer program 450, a sensory association program 452, and the like. Funds transfer program 450 may be configured to assist with the transfer of funds from or to the gaming machine by a portable electronic device as further described with reference to FIGS. 6-9. Sensory association program 452 may be configured to associate sensory input received by the at least one sensor device to a gaming or non-gaming function based on the context in which the sensory input is detected. For example, the multi-functional peripheral device may, simultaneously or in conjunction with the detection of the sensory input, receive a funds transfer request from the portable electronic device. Thus, a sensory input detection of one tap (e.g. an accelerometer associated with the multi-functional peripheral device may detect movement of one tap) may be associated with an initiation to transfer funds to a gaming machine in the context of a transfer of funds. In another example, a sensory input detection of two taps (e.g. a touch pad associated with the multi-functional peripheral device may detect movement of two taps) may be associated with an initiation to transfer funds from a gaming machine in the context of a transfer of funds—in other words, the player has completed playing the game of chance and would like to cash out his credits from the gaming machine. In another example, the multi-functional peripheral device 420 may detect that the portable electronic device is being used as a remote device to play a game of video black jack on a gaming machine. If the processor 422 receives notification of a sensory input for two taps (e.g. the accelerometer 414 associated with the portable electronic device 420 may detect movement of two taps), the two taps may be associated with a “Hit” request in the context of playing a game of video black jack. Processor 422 may then prepare and transmit a hit request to the gaming machine.



FIG. 4C illustrates a block diagram of another exemplary multi-functional peripheral device. The multi-functional peripheral device 460 may be used with another device, such as a value transfer device. The value transfer device may be a gaming machine, an automatic teller machine, a kiosk, a portable electronic device, or the like. The multi-functional peripheral device 460 can be any device that performs two or more peripheral functions. Examples of peripheral functions may include currency acceptance, ticket printing, player tracking functions, and the like. The multi-functional peripheral device can have a processor 462 configured to communicate with a wireless interface 470, a sensor device 464, and a memory 466. In one embodiment, the processor 462 may be configured to communicate with the value transfer device. In another embodiment, the processor 462 may be configured to communicate with a server, such as a gaming server, an authentication server, a TITO server, a player tracking server or any other server external to the multi-functional peripheral device and the value transfer device.


The wireless interface 470 can be configured to wirelessly communicate with other devices such as portable electronic devices, portable game playing devices, gaming devices, and the like. In one embodiment, the wireless interface 470 may be configured to wirelessly communicate with the value transfer device. In another embodiment, the wireless interface 462 may be configured to wirelessly communicate with the server. The wireless interface 470 can use any wireless communication technology such as IEEE 802.11x, Bluetooth, cellular technology such as 3G and 4G, radio frequency, near-field magnetics, and the like.


The sensor device 464 may be configured to monitor for a sensory input and transmit a signal. The sensor device 464 may include a sensor and a circuit mounted to a carrier. The carrier can pertain to a substrate such as a circuit board. The sensor can be configured to detect a sensory input. In one embodiment, the sensor may be an accelerometer configured to detect sensory inputs, such as vibrations, accelerations and other movement. The circuit may consist of electronic components such as resistors, capacitors, microchips and the like. The circuit may be configured to communicate with the sensor and be configured to process and generate a signal following detection of the sensory input by the sensor. The circuit can also be configured to transmit the signal to the processor 462.


The memory 466 may be any type of memory configured to store information or data such as non-volatile random access memory (NVRAM), dynamic random access memory (DRAM), ferroelectric random access memory (FRAM), electrically erasable programmable read-only memory (E2PROM), flash memory, hard disk, and the like. The memory 466 can store at least one software module 468. The software module 468 may include a value transfer program configured to assist with the transfer of funds between a portable electronic device and the value transfer device.


In one embodiment, the value transfer program may be configured to authenticate the portable electronic device, a physical voucher (e.g., paper voucher), or a digital voucher (e.g., a file) being transferred to/from the portable electronic device. However, the authentication may be conducted by any other device such as the value transfer device, the gaming machine, a third party server, or any other device or server. The value transfer program may be configured to initiate a fund transfer, direct funds to be transferred to at least one final destination, and perform other such actions in the transfer of funds.



FIG. 4D illustrates a side view of an example multi-functional peripheral device. The multi-functional peripheral device 472 is illustrated as a bill acceptor, but this is not intended to be limiting as the multi-functional peripheral 472 device can be any device that performs two or more peripheral functions. For example, the multi-functional peripheral device 472 may accept currency, print tickets and receipts, perform player tracking functions, and the like. The multi-functional peripheral device 472 can operate as an external or internal peripheral device to a value transfer device, such as a gaming machine, an automatic teller machine, a kiosk, a portable electronic device, or the like. The multi-functional peripheral device 472 may include a housing 474, a display 476 and a bezel 478. Processor 490, memory 488, and wireless interface 494, may be contained or housed within housing 474.


In one embodiment, bezel 478 may have a visual or audio element configured to draw attention to the multi-functional peripheral device 472. In one embodiment, the visual element can be graphics, text, or other similar indicia to draw the player's attention to the multi-functional peripheral device 472. In another embodiment, the visual element can be a light source. For example, the bezel 478 can contain blinking light emitting diodes that attract casino visitors to a slot machine. If the multi-functional peripheral device 472 has bill acceptor functionality, the bezel 478 may control and guide entry of bills, coins, cards, tickets and the like into the multi-functional peripheral device 472. In another embodiment, the audio element may be speakers configured to emit music, advertisements, random sounds, and the like.


The bezel 478 can be coupled to a front side of the housing 474 with adhesive, bonding agent, screws, bolts, nails or any other attachment means. The bezel 478 may be formed or made from plastic, metal, or other materials.


The sensor device 480 may be configured to monitor and receive a sensory input and transmit a signal associated with the sensory input. The sensor device 480 can be coupled to the bezel 478 with adhesive, bonding agent, screws, bolts, nails or any other materials commonly used for attachment. Although the sensor device 480 is illustrated as being coupled to the bottom surface 491 of the bezel 478, this is not intended to be limiting as the sensor device 480 can be coupled to any surface of the bezel 478 or other surfaces of the housing 474.


The sensor device 480 may include a carrier 484, a sensor 482, and a circuit 486. The carrier 484 can be a circuit board or any similar medium upon which the sensor 482 and the circuit 486 can be mounted to. The sensor 482 may be in communication with the circuit 486. The sensor 482 may be configured to detect or receive the sensory input from, for example, a portable electronic device. The sensor 482 can include one or more accelerometers, cameras, microphones, touchpads, retina scanners, radio frequency identification readers, near-field magnetic readers, or any other type of sensors. In one embodiment, the sensor 482 may be an accelerometer and the sensory input may be accelerations or vibrations. The circuit 486 may consist of electronic components such as resistors, capacitors, microchips and the like. The circuit 486 may be configured to generate a signal following detection of the sensory input by the sensor 482. The circuit 486 can also be configured to transmit the signal to the processor 490.


The memory 488 can store at least one software module. The memory 488 may be any type of memory configured to store information or data such as an NVRAM, DRAM, FRAM, E2PROM, flash memory, hard disk, and the like. In one embodiment, the software module may include a fund transfer program configured to assist with the transfer of funds between the portable electronic device and any device housing the multi-functional peripheral device 472 such as a gaming machine, an automatic teller machine, another portable electronic device, or a kiosk.


In one embodiment, the fund transfer program may be configured to authenticate the portable electronic device. However, the authentication may be conducted by any other device such as the value transfer device, a gaming machine, a third party server, or any other device or server. The fund transfer program may be configured to initiate a fund transfer, direct funds to be transferred to at least one final destination, and perform other such actions in the transfer of funds.


The wireless interface 494 can be configured to wirelessly communicate with other devices such as portable electronic devices, portable game playing devices, value transfer devices, gaming devices, and the like. The wireless interface 494 can use any wireless communication technology such as IEEE 802.11x, Bluetooth, cellular technology such as 3G and 4G, radio frequency, near-field magnetics, and the like. In one embodiment, the wireless interface 494 can be disposed within the housing 474 and configured for direct communication with the processor 490. In another embodiment, the wireless interface 494′ may be disposed within the sensor device 480.


The multi-functional peripheral device 472 can have an input/output interface 492 configured to facilitate communication with other devices.



FIG. 4E illustrates a side view of another example multi-functional device. The multi-functional peripheral device 494 is illustrated as a bill acceptor, but this is not intended to be limiting as the multi-functional peripheral 472 device can be any device that performs two or more peripheral functions. The multi-functional peripheral device 494 may include a housing 474, a display 476, a bezel 478, a sensor device 481, a memory 488, a processor 490, and an input/output interface 492 s.


In this embodiment, similar to FIG. 4D, sensor device 481 can be positioned or housed within the bezel 478. In one embodiment, the bezel 478 can include a cavity within which the sensor device 480 resides. In another embodiment, the sensor device 480 may be integrated into the bezel 478. For example, the sensor device 480 can be placed within a mold. Liquid plastic or metal material may then be poured into the mold to encase the sensor device 480. The liquid plastic material can then harden to form the bezel 478 around the sensor device 480. In yet another embodiment, various components of the sensor device 480, such as the sensor 482, the circuit 486, and the carrier 484, may be separately disposed within the bezel 478.



FIG. 5 illustrates an example block diagram of a portable electronic device. The portable electronic device 500 may be any type of portable computing device. For example, portable electronic device 500 may be a cellular phone, portable media player, PDA, netbook, portable computer, electronic reader, and the like. Portable electronic device 500 may have a processor 504, display 502, memory 508, at least one user button or switch 506, sensor device 510 configured to receive any type of sensory input, a wireless communication module 514. Although illustrated with specific components, this is not intended to be limiting as portable electronic device 500 may have other components such as an antenna, power source, speaker, camera, and the like.


Display 502 may be any type of display such as a touch screen display, LCD, plasma display, LED display, or any other monitor and/or display configured to present information and/or allow the user to play a game of chance. For example, display 502 may be configured to display a plurality of indicators (as discussed and illustrated in FIGS. 6A-6G). Each indicator may be associated with or correspond to one or more applications stored in the memory 508. Selection of one of the plurality of indicators may initiate the one or more applications. In one embodiment, display 502 may include a touch screen sensor such that the processor may be configured to detect a user selection of at least one of the indicators. In another embodiment, selection of one of the plurality of indicators may be made using switches 506.


Wireless communication module 514 may be configured to transmit and receive information or data from multi-functional peripheral device. Wireless communication module 514 may be any module capable of wireless transmission such as 3G wireless technology, 4G wireless technology, Bluetooth, wireless USB, wireless UWB), WiMAX, near field communication, radio frequency, and the like. In one embodiment, wireless communication module 514 may be configured to transmit gaming and non-gaming requests to the multi-functional peripheral device (e.g. multi-functional peripheral device 102 illustrated in FIG. 1 or multi-functional peripheral device 244 illustrated in FIG. 2B). For example, the portable electronic device may transmit a funds transfer request to transfer funds to the gaming machine to allow the player to play a game of chance on the gaming machine. In another embodiment, the portable electronic device may transmit a cash-out request to print an electronically-readable ticket on the printer of the gaming machine. In still another embodiment, the portable electronic device may transmit a reservation request to reserve a table at a restaurant at the gaming establishment.


The sensor device 510 can be any device that can detect a sensory input from a user. The at least one sensor device may be an accelerometer, a camera, a microphone, a touchpad, a touch screen, radio frequency identification reader, near-field magnetic reader, and the like. The sensor device 510 may be configured to communicate with the portable electronic device processor 504. In one example, the sensory input may be a predefined user action that may be associated with a gaming or non-gaming function. For example, a sensory input for one tap on a touch pad may be associated with a request to transfer funds. In another example, a sensory input for two taps on a touch pad may be associated with a “Hit” request while playing a video black jack game of chance. In still another example, a sensory input of one tap detected by an accelerometer may be associated with a confirmation to cash out of the gaming machine. It will now be known that many other combinations and/or predefined actions may be possible and are contemplated.


Portable electronic device 500 may have a memory 508 configured to store any type of information, data, and/or software to play a game of chance on a gaming machine and/or perform any other gaming functions such as checking a player tracking account, transferring funds to play the game of chance, and the like. Memory 508 may be any type of memory such as DRAM, NVRAM, Ferro-electric Random Access Memory (FRAM), Flash memory, Electrically Erasable Programmable Read-Only Memory (E2PROM), and the like.


In use, when processor 504 receives a notification of a sensory input from sensory device 510, processor 504 may determine what the user is requesting based on the associated function of the sensory input received. The sensory input may be a predefined user action that may be associated with a gaming or non-gaming function and may be context based. In one embodiment, processor 504 may be configured to communicate with memory 508, which may include a sensory database 512, to determine the function of the sensory input. In another embodiment, processor 504 may be configured to communicate directly with sensory database 512. Sensory database 512 may be configured to store information such as the type of sensory input detected, the function associated with the sensory input, and the context for which the sensory input was provided. For example, the user may have selected a “Transfer Funds” indicator on the portable electronic device. Thus, if the processor receives notification of a sensory input for one tap (e.g. the accelerometer associated with the portable electronic device 500 may detect movement of one tap), the one tap may be associated with an initiation to transfer funds to a gaming machine in the context of a transfer of funds. Processor 504 may then prepare and transmit a funds transfer request to the multi-functional peripheral device. The funds transfer request may include any information necessary to facilitate a transfer of funds such as a portable electronic device identifier, destination address (e.g. which gaming machine to transfer the funds to), amount of funds to be transferred, and the like.


In another example, portable electronic device 500 may be used as a remote device to play a game of video black jack on a gaming machine. If the processor receives notification of a sensory input for two taps (e.g. the accelerometer associated with the portable electronic device 500 may detect movement of two taps), the two taps may be associated with a “Hit” request in the context of playing a game of video black jack. Processor 504 may then prepare and transmit a hit request to the multi-functional peripheral device.



FIGS. 6A-6G illustrate exemplary graphical user interfaces of a portable electronic device for communicating with a gaming machine. FIG. 6A illustrates an exemplary user selectable menu displaying a plurality of indicators 604 on a display 602 of the portable electronic device 600. Each of the plurality of indicators 604 may correspond to an associated software application stored in a database (e.g. database 512 as illustrated in FIG. 5) of the portable electronic device 600. The portable electronic device 600 may initiate a software application when a user selection of a corresponding indicator 604 is detected. For example, a user may select the “Casino Money Transfer” indicator 606, which may be detected by the portable electronic device processor. The portable electronic device processor may associate the selection of the “Casino Money Transfer” indicator 606 to a funds transfer program on the portable electronic program and initiate the funds transfer program.



FIG. 6B illustrates an exemplary initial graphical user interface for a funds transfer program. The user of the portable electronic device may be prompted to select whether to transfer funds from the portable electronic device to the gaming device or to transfer funds from the gaming device to the portable electronic device. In one embodiment, a “Transfer Money To Gaming Device” indicator 614 and a “Transfer Money From Gaming Device” indicator 616 may be presented on the display 602 of the portable electronic device 600. In another embodiment, the portable electronic device may simply present a question, such as, “Transfer Funds To Gaming Machine?” and display a “Yes” or “No” indicator.


Upon selection of the “Transfer Money To Gaming Device” indicator 614, the user may be prompted to input a fund amount, as illustrated in FIG. 6C. The portable electronic device 600 may display a user-enterable field 624 on display 602. The user-enterable field 624 may prompt the user to enter a fund amount, credit amount, or any other information necessary to complete a transfer of funds to the gaming machine. For example, the fund amount may be a specific monetary amount, such as “$100.00” as illustrated in FIG. 6C. In another example, the user may enter a credit amount, such as credit accumulated in his player tracking account. The user-enterable field 624 may be populated using a numerical keypad 628, joystick, or any other user-input buttons or switches. In another embodiment, the fund amount may be a predefined or preset amount. For example, the preset amount maybe $20 and is the default value for each user action. Thus, the use may use one tap for a $20.00 transfer request to the gaming device, two taps for a $40 transfer request, and so on.


In one example, the user may confirm the amount inputted in the user-enterable field 624 by selecting a “Confirm” indicator 630. In another example, the user may cancel the selection by selecting the “Cancel” indicator 632. Selecting the “Cancel” indicator 632 may result in removal of the amounts entered in the user-selectable field 624. On the other hand, selection of the “Confirm” indicator 630 may result in the generation of a funds transfer request by the portable electronic device.


Referring now to FIG. 6D, an exemplary illustration of a graphical user interface to initiate money transfer. The portable electronic device 600 may display instructions on the display 602 to instruct the user how to initiate the transfer of funds to the gaming device. In one embodiment, the portable electronic device 600 may instruct the user to tap the portable electronic device on a sensor device (e.g. sensor device 116 as illustrated in FIG. 1 and sensor device 254 as illustrated in FIG. 2B). For example, the instructions may be to “Please Tap To Sensor Device To Initiate Money Transfer”. In another embodiment, portable electronic device 600 may instruct the user to orally confirm transfer of funds to a microphone of the multi-functional peripheral device. For example, the instructions 644 may be to “Please Confirm Transfer By Saying ‘Initiate Money Transfer’ Into The Microphone”.



FIG. 6E illustrates an example transfer of funds by contacting, with a portable electronic device, a sensor device associated with the multi-functional peripheral device. As illustrated, the portable electronic device 600 may physically contact a sensor device 654 proximate to the bill acceptor 622. The sensor device 654 may be any known device configured to detect and/or receive a sensory input. For example, the sensor device 654 may be an accelerometer, camera, microphone, touchpad, retina scanner, radio frequency identification reader, near-field magnetic reader, or any other device capable of receiving and detecting sensory input.


As illustrated, in another embodiment, the sensor device may be a touchpad 652 located on the gaming machine 612. Thus, to initiate the transfer of funds, the user may physically tap or contact the touchpad 652 with the portable electronic device 600.


Subsequent to physically contacting the sensor device 654, the portable electronic device may transmit a transfer funds request to the multi-functional peripheral device. The funds transfer request may include any information and requests to facilitate transfer of funds to the gaming machine. For example, the funds transfer request may include a unique user identification (ID), password, fund amount, funding source such as bank routing and checking account number and/or player tracking account number, and any other information or data necessary to facilitate the transfer of funds. In another embodiment, the funds transfer request may include location information of the portable electronic device, location information of the gaming device, time stamp data, and any other data or information that may be used to authenticate and/or verify the portable electronic device and the gaming device to ensure that the funds are transferred to the proper gaming device as further discussed with reference to FIG. 8.



FIG. 6F illustrates an example graphical user interface indicating that contact with the sensor device as successful. In one embodiment, successful contact with the sensor device may be based upon receipt of a successful message by the portable electronic device 600 from the multi-functional peripheral device. In another embodiment, successful contact with the sensor device may be based upon successful transmission of the funds transfer request from the portable electronic device 600 to the multi-functional peripheral device. In one example, the message 664 may inform the user that the user action was successfully performed, the sensor device detected the sensory input, and that the multi-functional peripheral device is processing the funds transfer request.


If contact was not successful (e.g. the sensor device did not detect a sensory input), the portable electronic device 600 may display an unsuccessful message (not shown). For example, a “Please Try Again” message may be displayed on the display 602 of the portable electronic device 600. In another embodiment, if the sensor device associated with the multi-functional peripheral device does not detect a sensory input within a predetermined amount of time (e.g. after 30 seconds, 1 minute, or any other predetermined time period), the portable electronic device 600 may display an unsuccessful message.



FIG. 6G illustrates an exemplary graphical user interface representing the completion of the funds transfer. Upon receipt of the funds transfer request received from the portable electronic, the multi-functional peripheral device may process the funds transfer request. In other words, the multi-functional peripheral device may parse the funds transfer request to determine at least one of (i) the fund amount; (ii) the source of the funds; (iii) unique user ID and password; (iv) sufficient funds to transfer the fund amount; (v) location of the transaction, and any other necessary information to facilitate the transfer of funds from or to the gaming machine. For example, the multi-functional peripheral device may determine that the user would like to debit $100 from his Credit Union checking account. The multi-functional peripheral device may transmit a debit request to the Credit Union server (e.g. third-party server 120 as illustrated in FIG. 1). The debit request may include the fund amount, user ID and password, bank routing and checking account number, and any other necessary information or data. If there are sufficient funds in the user's checking account, the Credit Union may debit the user's checking account by the fund amount and transmit the fund amount to the multi-functional peripheral device.


In another embodiment, the multi-functional peripheral device may determine that the user would like to charge $100 to his credit card. The multi-functional peripheral device may transmit a charge request to the credit card server (e.g. third-party server 120 as illustrated in FIG. 1). The charge request may include the fund amount, user ID and password, credit card number, security code, zip code, and any other necessary information or data. If the user's credit limit is not exceeded, the user's account may be charged the fund amount and the fund amount may be transmitted to the multi-functional peripheral device.


In still another embodiment, the multi-functional peripheral device may determine that the user would like to debit player credits from the user's player tracking account. The multi-functional peripheral device may transmit a debit credit request to the player tracking server (e.g. player tracking server 124 as illustrated in FIG. 1). The debit credit request may include the fund amount, user ID and password, player tracking number, and any other necessary information or data. If the user has sufficient credit in his player tracking account, the user's account may be debited the credit amount and the credit amount may be transmitted to the multi-functional peripheral device.


If the multi-functional peripheral device receives a fund amount from a third-party server, a successful acknowledgement may be transmitted to the portable electronic device as illustrated in FIG. 6G. In one example, the portable electronic device 600 may present a message 674 such as “Congratulations: You have successfully transferred $100.00.”. Optionally, the user may be able to print a receipt recoding the transfer of funds. For example, the user may select the “Print Receipt” indicator 680 to create a virtual receipt. The portable electronic device 600 may then display the virtual receipt (not shown) on the display 602 and digitally store the virtual receipt in a memory of the portable electronic device 600.


According to one embodiment, the amount of funds or credits received by the multi-functional peripheral device may also be displayed on a display of the gaming device as credits for use in playing a game of chance on the gaming machine. The multi-functional peripheral device may transmit a funds notification to the gaming machine processor to notify the gaming machine that the user has transferred funds to the gaming machine. The gaming machine processor may then display the credit amount on the display of the gaming device.



FIG. 7A illustrates an example flow diagram of a method for transferring funds between a portable electronic device and a gaming device. The method 700 initially begins with determining whether a sensory input is detected or received by the multi-functional peripheral device at 702. If no sensory input is detected or received, then the multi-functional peripheral device may continue to wait for the sensory input.


The sensory input may be detected or received by at least one sensor device associated with the multi-functional peripheral device. The sensory device may be any known device configured to detect and/or receive a sensory input. For example, the at least one sensor device may be an accelerometer, camera, microphone, touchpad, retina scanner, radio frequency identification reader, near-field magnetic reader, or any other device capable of receiving and detecting sensory input. The type of sensory input received or detected may be based on the sensory device. For example, a user may physically contact the sensor device via a tap, touch, or any other physical contact on a touchpad. The physical contact may initiated by the user (e.g. using a finger to tap the sensor device), physical object (e.g. pen, coin, and the like), and/or a remote device associated with the user. The remote device may, for example, be any portable computing device such as a cellular phone, portable media player, PDA, and the like. In another embodiment, the sensory input may be an audio input received by a microphone associated with the multi-functional peripheral device.


Based upon the sensory input received as well as the context in which the sensory input is detected, a function may be associated with the sensory input. For example, as illustrated in FIG. 7, a determination is made as to whether funds should be transferred to or from a gaming machine at 704. This determination may, in part, be made based upon the context. For example, the multi-functional peripheral device may, simultaneously or in conjunction with the detection of the sensory input, receive a funds transfer request from the portable electronic device. Thus, a sensory input detection of one tap (e.g. an accelerometer associated with the multi-functional peripheral device may detect movement of one tap) may be associated with an initiation to transfer funds to a gaming machine in the context of a transfer of funds. In another example, a sensory input detection of two taps (e.g. a touch pad associated with the multi-functional peripheral device may detect movement of two taps) may be associated with an initiation to transfer funds from a gaming machine in the context of a transfer of funds—in other words, the player has completed playing the game of chance and would like to cash out his credits from the gaming machine.


If it is determined that funds are to be transferred at 704, the multi-functional peripheral device may activate a funds transfer program at 706. The funds transfer program may be any program configured to facilitate a transfer of funds to or from a gaming machine. In one embodiment, the program stored in a memory of the multi-functional peripheral device (e.g. memory 424 as illustrated in FIG. 4B). When activated, the multi-functional peripheral device may parse or process a funds transfer request from the portable electronic device to determine at least one of (i) the fund amount; (ii) the source of the funds; (iii) unique user ID and password; (iv) sufficient funds to transfer the fund amount; (v) location of the transaction, and any other necessary information to facilitate the transfer of funds from or to the gaming device. For example, the multi-functional peripheral device may determine that the user would like to debit $100 from his Credit Union checking account. The multi-functional peripheral device may transmit a debit request to the Credit Union server (e.g. third-party server 120 as illustrated in FIG. 1). The debit request may include the fund amount, user ID and password, bank routing and checking account number, and any other necessary information or data. If there are sufficient funds in the user's checking account, the Credit Union may debit the user's checking account by the fund amount and transmit the fund amount to the multi-functional peripheral device.


In another embodiment, the multi-functional peripheral device may determine that the user would like to charge $100 to his credit card. The multi-functional peripheral device may transmit a charge request to the credit card server (e.g. third-party server 120 as illustrated in FIG. 1). The charge request may include the fund amount, user ID and password, credit card number, security code, zip code, and any other necessary information or data. If the user's credit limit is not exceeded, the user's account may be charged the fund amount and the fund amount may be transmitted to the multi-functional peripheral device.


In still another embodiment, the multi-functional peripheral device may determine that the user would like to debit player credits from the user's player tracking account. The multi-functional peripheral device may transmit a debit credit request to the player tracking server (e.g. player tracking server 124 as illustrated in FIG. 1). The debit credit request may include the fund amount, user ID and password, player tracking number, and any other necessary information or data. If the user has sufficient credit in his player tracking account, the user's account may be debited the credit amount and the credit amount may be transmitted to the multi-functional peripheral device.


Although the communication to the external fund source was described above as being initiated by the multi-functional peripheral device, in another embodiment, the fund transfer request can also be made by the portable electronic device directly to the fund source via its own communication link. For example, the portable electronic device can directly contact a bank (e.g. third-party server 120 as illustrated in FIG. 1) to request a secured virtual check to be transferred to the gaming device 200 or transferred from the gaming device 200 for deposit to the bank account.



FIG. 7B illustrates a flow diagram of an example method for transferring funds or other values to and from a portable electronic device. The portable electronic device can be a cellular phone, smartphone, portable media player, tablet computer, laptop computer, PDA, and the like. The method 720 may be performed by any machine configured to communicate with a multi-functional peripheral device. In one example, the machine may be a value transfer device.


The method 720 may begin by determining whether a sensory input is detected at 722. The sensory input may be detected by a sensor of a sensor device of the multi-functional peripheral device. In one embodiment, the sensory input may be generated through physical contact using a portable electronic device (PED). For example, the sensory input can be vibrations, accelerations, or other movements detected by the sensor. The physical contact may be performed at a variety of locations on the machine. For example, the user may directly bump, tap, touch, or otherwise physically contact the sensor device. In another embodiment, a bezel coupled to the multi-functional peripheral device, the multi-functional peripheral device, or the value transfer device may be configured to detect a physical contact from, for example, a portable electronic device.


In another embodiment, the sensory input may be generated by the PED and detected by the sensor without physical contact. Example technologies for contactless or wireless sensory input detection include: near field communication (NFC), radio frequency identification (RFID), Bluetooth, barcode, and the like. In one embodiment, determining whether a sensory input is detected may include detecting whether a PED is located proximate the sensor. This may include receiving a request to authenticate the PED if it is detected that the PED is within a satisfactory distance to trigger the transaction. In another embodiment, determining whether a sensory input is detected may include establishing communication between the multi-functional peripheral device and the PED manually by the player. In this example, the player may wish to transfer money or other values stored on a PED to a casino kiosk. The player can press a touch screen of the PED, then press a touch screen on the casino kiosk, to initiate a money or value transfer function on an electronic fund management application running on the PED. The sequential selection between the touch screen of the PED and the casino kiosk signifies the player's intent to pair the two chosen devices. The time window between the selections implies the proximity of the two devices thereby minimizing ambiguities with other nearby devices. This manual approach is equivalent to detecting a sensory input and can be used to trigger the next action in the process. The electronic fund management application may assist the user with transferring funds, storing funds, print a paper voucher, viewing a balance and other functions associated with electronic fund management. If no sensory input is detected at 722, the value transfer device may continue to wait for the sensory input.


If a sensory input is detected at 722, transfer parameters are determined at 724. In one embodiment, the determination may be performed by the multi-functional peripheral device. Transfer parameters may include data such as the fund or value quantity or amount to be transferred, location of the sensory input or funds, a transfer destination (e.g. such as to transfer to a PED or another device such as a gaming machine), type or classification of fund or value (e.g. money, credits, tokens, ticket vouchers, promotional game credits, digital assets, player points, or any other form of currency or value), and any other desired information. The location can indicate a machine or device where the funds reside.


In one example, a player playing a slot machine in a casino may decide to cash out. The player may push the “cash out” button on the slot machine. A processor of the multi-functional peripheral device can receive the request to cash out which may also include the cash out amount remaining in the gaming machine, location or identification of the gaming machine, and/or location or identification of the PED to transfer the funds to.


In one embodiment, the transfer quantity or amount can be all or a portion of the funds. The processor can determine the transfer quantity from a transfer quantity input. The transfer quantity input may be a percentage or fractional amount of the funds, such as 100%, 50%, ¾, 1/10, or any other percentage or fractional determination. For example, the player may want to allocate ¼ of the funds for slot play. They player can make a transfer quantity input of “¼” using the electronic fund management application. Thus, ¼ of the total funds can be transferred. In one embodiment, the electronic fund management application may present a plurality of buttons configured to represent different proportions. For example, the electronic fund management application can display buttons configured to represent ¼, ½, ¾, and all. In another embodiment, the electronic fund management application may present a dropdown menu having options for different proportions. In yet another embodiment, the electronic fund management application may have a slider. For example, the player can use the touch screen and slide an indicator of the slider to the appropriate proportion to be transferred.


The transfer quantity input can also be a numerical value, such as $105.24, 3 credits, 21,954 tokens, 500 loyalty points, or any specific amount or quantity. The user can perform the transfer quantity input on the portable electronic device or the value transfer device. For example, the player may want to transfer $300.50 from a tablet computer to a video poker machine. The player may use a touch screen input mechanism of the tablet computer to enter “$300.50” into the electronic fund management application of the tablet computer. The electronic fund management application can transmit a fund transfer request of “$300.50” to the processor of the multi-functional peripheral device of the video poker machine.


To determine a location to transfer the funds, in one embodiment, the transfer destination may be the multi-functional peripheral device. For example, the player may want to transfer virtual tokens from a portable media player to an electronic horseracing themed gaming machine. Upon detecting a sensory input, a transfer signal may be transmitted from the portable media player to the multi-functional peripheral device of the electronic horseracing themed gaming machine. The multi-functional peripheral device may receive the transfer signal and determine that the user would like to transfer the virtual tokens to play a game of chance on the electronic horseracing machine.


In another embodiment, a plurality of transfer destinations may be displayed on a menu presented on a display of the machine or value transfer device. A graphical user interface can prompt the player to select at least one transfer destination, which may include a portable electronic device, portable media player, laptop, cellular phone, bank, or any other location or device.


In yet another embodiment, the processor may automatically determine the transfer destination. For example, the player may want to transfer tokens from a portable media player to the electronic horseracing machine. Upon detecting a sensory input (i.e. physical contact), such as a bump from the portable media player, the processor of the multi-functional peripheral device may establish a communication session with the portable media player and the electronic horseracing machine. If the location of the fund amount to be transferred has been determined to be the portable media player, the processor of the multi-functional peripheral device may automatically determine the electronic horseracing machine as the transfer destination.


A determination of whether to initiate transfer of the fund amount may be made at 726. For example, the processor of the multi-functional peripheral device can determine whether to initiate transfer of the fund amount. In one embodiment, the multi-functional peripheral device may initiate transfer of the fund amount upon receipt of a confirmation request from the user using the PED or the value transfer device. For example, a confirmation dialogue may appear in a graphical user interface of the portable electronic device such as: “Please Confirm Transfer Of Funds”. A “YES” and “NO” indicator may also be displayed on the display for the user to select. Upon detection of selection of the “YES” indicator, receipt of the confirmation request is received and the multi-functional peripheral device may transfer the fund amount at 728.


In another embodiment, initiation of the transfer of the fund amount can be based upon verification of at least one transfer parameter. For example, one transfer parameter may be a determination of whether there are funds to be transferred at the fund location (e.g. funds in a gaming machine, funds in a bank account, or funds from another device). If it is determined that there are no funds at the fund location, the transfer of funds will not be initiated. In another example, if the fund amount at the fund location is less than the transfer amount requested to be transferred, the transfer of funds will not be initiated. In still another example, no funds will be transferred if it is determined that the destination machine or device is unavailable (e.g. outside of communications range, powered down, not accepting fund transfers, or the like).


If it is determined the transfer of the fund amount is to be initiated at 726, the fund amount can be transferred from or to the portable electronic device at 728. If it is determined that the transfer destination is the portable electronic device (e.g. based on the transfer parameters determined at 724), the transfer amount can be transmitted to the portable electronic device. If it is determined that the transfer destination is a value transfer device (e.g. based on the transfer parameters determined at 724), the transfer amount can be transmitted to the value transfer device.



FIG. 7C illustrates a flow diagram of an example method for transferring funds from a portable electronic device. A method 740 for transferring funds from a portable electronic device can be performed by a portable electronic device, such as a cellular phone, smartphone, portable media player, tablet computer, laptop computer, PDA, or any other PED configured to play a game of chance.


The method 740 may begin by determining whether to transfer funds out of a portable electronic device at 742. In one embodiment, the determination can be based upon a user transfer out request. For example, a user may generate and initiate the transfer out request using an electronic fund management application on the portable electronic device. In another embodiment, the determination may be based on a value transfer device detecting the presence of the portable electronic device. For example, the value transfer device may be configured to detect the presence of portable electronic devices proximate its vicinity. Once detected, the value transfer device may transmit a response signal (i.e. an initiation signal) to the portable electronic device. A processor of the portable electronic device may automatically determine, from the response signal, that funds are to be transferred out of the portable electronic device.


If it is determined that funds are to be transferred out of the portable electronic device at 742, a fund transfer amount may be identified at 744. Identifying the fund transfer amount may include selecting a source, determining what the fund or value type is (e.g. cash or voucher), and the like. Selecting the source can include, but is not limited to, selecting a source fund type and/or a source account as the portable electronic device may store more than one fund type and include more than one account of funds. The fund or value types may include money of different currencies, credits, tokens, ticket vouchers, promotional game credits, digital assets, player points and the like. In one embodiment, the account of funds can be accounts for different gaming environments (as illustrated further in FIG. 12), such as casinos, shopping centers, cruise boats, and the like. For example, the portable electronic device may have a casino 1 account, a casino 2 account, and a riverboat casino A account. In another embodiment, the account of funds can be accounts for different transaction types. For example, the portable electronic device may have a gaming account and a shopping account. In yet another embodiment, the account of funds may be accounts for different transaction types from different gaming environments. For example, the user may have a casino A slot machine account, a casino A food and drink account, and a casino B gaming account.


In one embodiment, the user may select the source of the funds. For example, the portable electronic device may have a graphical user interface configured to present at least one source option. The at least one source option representing, but not limited to, any source fund types and any source accounts stored on the portable electronic device. The user can select the source using any input mechanism of the portable electronic device, such as a button, key, touch screen, microphone, or the like.


In another embodiment, a default source may be used. For example, the value transfer device may only accept funds from certain accounts or sources with certain characteristics. For example, the value transfer device may only accept credits, such as in a casino gaming environment.


Identifying the fund transfer amount at 744 may also include determining or authenticating a quantity. The quantity can be all or a portion of the plurality of funds. In one embodiment, the quantity can be determined from a quantity input. In one embodiment, the transfer quantity or amount can be all or a portion of the funds. The processor can determine the transfer quantity from a transfer quantity input. The transfer quantity input may be a percentage or fractional amount of the funds, such as 100%, 50%, ¾, 1/10, or any other percentage or fractional determination. For example, the player may want to allocate ¼ of the funds for slot play. The player can make a transfer quantity input of “¼” using the electronic fund management application. Thus, ¼ of the total funds can be transferred. In one embodiment, the electronic fund management application may present a plurality of buttons configured to represent different proportions. For example, the electronic fund management application can display buttons configured to represent ¼, ½, ¾, and all. In another embodiment, the electronic fund management application may present a dropdown menu having options for different proportions. In yet another embodiment, the electronic fund management application may have a slider. For example, the player can use the touch screen and slide an indicator of the slider to the appropriate proportion to be transferred.


A determination of whether the portable electronic device is authenticated with the value transfer device may be made at 746. In other words, a determination is made as to whether the portable electronic device was previously authenticated by the value transfer device. In one embodiment, the value transfer device may authenticate or validate the portable electronic device by confirmation of a password, biometric identifier, personal identification number(s), user names, or any other authentication or validation methods. Once authenticated, the value transfer device may transmit an authentication signal to the portable electronic device. In another embodiment, the value transfer device may be configured to automatically authenticate the portable electronic device based upon an identifier, such as a MAC address, confirming validity of a key file (which may or may not be encrypted) stored on the user device, hashing and comparing contents of the key file to a record maintained by the value transfer device or any server configured to communicate with the value transfer device, or any other commonly used methods of verifying the validity of a data file. In yet another embodiment, the value transfer device may authenticate the portable electronic device using a unique address, such as a short code or a web link.


In one embodiment, either in lieu of or in addition to the portable electronic device authentication at 746, the authentication of the information being transferred may be authenticated. Authentication of documents, messages and data normally involves technologies related to digital signatures, digital certificates, digital watermarking, and cryptography to ensure privacy of the transaction, to verify that the data or message being sent has not been altered or corrupted, and that it did come from the claimed sender. For example, a casino promotional voucher for $20 of free play on of a new video poker game being redeemed may be authenticated to ensure it was issued by the casino, is for $20, is being redeemed by the intended player, being applied to the allowed game type, and it has not been previously redeemed or expired.


If it is not determined that the portable electronic device was authenticated with the value transfer device at 746, a determination of whether the method for transferring funds should time out at 754. In one embodiment, the method 740 can time out if the portable electronic device is not authenticated with the value transfer device before a predetermined time. The predetermined time may begin counting down upon identification of the fund transfer amount, determining funds are to be transferred out of the portable electronic device, and/or detection of the presence of the portable electronic device by the value transfer device. If it is determined that the method 740 for transferring funds should not time out at 754, the determination of whether the portable electronic device has been authenticated with the value transfer device at 746 continues.


If it is determined that the method 740 should time out at 754, an error message may be displayed at 756. The error message may include any combination of text, graphics, or other indicia indicating an error has occurred. For example, the error message can be a large red stop sign accompanied by text stating, “Authentication has time out.” The error message may also include text, graphics, or other indicia indicating at least one option for addressing the error. In one embodiment, the error message can be displayed on a display of the portable electronic device. In another embodiment, the error message can be displayed on a display of the value transfer device. The method 740 may end upon display of the error message.


If it is determined that the portable electronic device is authenticated with the value transfer device at 746, a fund transfer request may be transmitted to the value transfer device at 748. The fund transfer request may be a request to transfer funds to the value transfer device and based upon at least one fund transfer parameter. In one embodiment, the fund transfer request can be transmitted using any wireless communication technology such as IEEE 802.11x, Bluetooth, cellular technology such as 3G and 4G, radio frequency, near-field magnetics, and other similar methods. In another embodiment, the fund transfer request can be transmitted using wired communication technology, such as Ethernet cables, USB, Firewire, serial cables, and other similar methods. The at least one fund transfer parameter may have a plurality of criteria such as which communications device to use to transfer the fund, the location or account to which the funds are to be transferred, which type of encryption to use to protect the fund transfer, any information from the fund transfer amount identified at 744, or any other criteria necessary to facilitate the fund transfer.


The portable electronic device may receive a confirmation message from the value transfer device at 749 to confirm that the user would like to transfer the funds out of the portable electronic device. The confirmation message may be displayed on a display of the portable electronic device, valued transfer device, or any other device. In one example, the message displayed may be a “Please confirm transfer of funds” with a “YES” and “NO” indicator.


A determination of whether the confirmation is accepted is made at 750. If the user, does not want to transfer the funs, the “NO” indicator may be selected and method 740 may end. If the user would like to confirm the fund transfer, the user may select the “YES” indicator” and the funds may then be transferred based upon at least one of the fund transfer parameters. The value transfer device may prepare and/or initiate the fund transfer.


A transfer success message may be transmitted to and displayed on a display at 752. Once the transfer of funds is completed, the value transfer device may transmit the success message to the portable electronic device to inform the user that the transfer was successful and completed. The message may include any combination of text, graphics, or other indicia indicating the fund transfer was successful. For example, the transfer success message can be a “thumbs up” graphic accompanied by text stating, “Transfer Successful.” In one embodiment, the transfer success message can be displayed on a display of the portable electronic device. In another embodiment, the transfer success message can be displayed on a display of the value transfer device. The method 740 may end upon display of the confirmation message.



FIG. 7D illustrates a flow diagram of an example method for transferring funds to a value transfer device. A method 760 for transferring funds to a value transfer device may be performed in a gaming environment. The method 760 for transferring funds to a value transfer device may begin by detecting a presence of a portable electronic device at 762. If the presence of the portable electronic device is not detected at 762, the method 260 may await detection of the presence of the portable electronic device.


The value transfer device may detect the presence of the portable electronic device in various ways. In one embodiment, the value transfer device may detect the presence of the portable electronic device through physical contact. For example, the value transfer device may have a sensor configured to detect physical contact from the portable electronic device. The physical contact may be any contact such as a bump, tap, touch, slide, or any other physical contact that may be detected by the value transfer device.


In another example, the value transfer device may have a multi-functional peripheral device (as illustrated in FIG. 4C, 4D, 4E) with a sensor configured to detect physical contact. The sensor can be an accelerometer configured to detect vibrations, accelerations, or other movements. The vibrations, accelerations, or other movements can occur when a user bumps, taps, touches, or otherwise physically contacts the portable electronic device to any portion of the value transfer device.


In another embodiment, the value transfer device may detect the presence of the portable electronic device using contactless communications technology when the portable electronic device is in close proximity to the value transfer device. Example contactless communications technologies include NFC, RFID, Bluetooth, wireless Ethernet and the like. In an embodiment, close proximity may depend upon industry and/or technology standards for the particular contactless communications technology utilized by the value transfer device. In another embodiment, close proximity may be determined by a proximity setting of the value transfer device. For example, a slot machine or the value transfer device may have a memory storing a proximity setting of three (3) inches. The slot machine or value transfer device may detect any portable electronic device within three (3) inches of any portion of the slot machine.


In yet another embodiment, detection may be performed by a gaming environment device. The gaming environment device may detect the presence of the portable electronic device through physical contact or contactless communications technology. The gaming environment device can be any machine or device capable of detecting the presence of the portable electronic device. For example, the portable electronic device can be a server configured to detect the presence of the portable electronic device through IEEE 802.11x Ethernet technology using at least one wireless access point. In an example, the gaming environment device can be an information terminal, having an accelerometer, in a wall of a casino.


If the presence of the portable electronic device is detected at 762, a determination of whether the portable electronic device is authenticated is made at 764. If the portable electronic device is not authenticated at 764, the method 760 may end. In one embodiment, the processor of the value transfer device may determine whether the portable electronic device has been authenticated. Authentication may authorize and establish communication between the value transfer device and the portable electronic device. In one embodiment, the value transfer device may authenticate the portable electronic device by confirming validity of a password, biometric identifier, personal identification number(s), or the like. In another embodiment, the value transfer device may be configured to authenticate the portable electronic device based upon an identifier, such as a MAC address, confirming validity of a key file (which may or may not be encrypted) stored on the user device, hashing and comparing contents of the key file to a record maintained by the value transfer device or any server configured to communicate with the value transfer device, or any other commonly used methods of verifying the validity of a data file. In yet another embodiment, the value transfer device may authenticate the portable electronic device using a unique address, such as a short code or a web link.


In another embodiment, the gaming environment device may determine whether the portable electronic device has been authenticated. The gaming environment device may authenticate the portable electronic device using an identifier, data file, unique address, or any other common methods for authentication. Authentication may authorize and establish communication between the portable electronic device and a gaming environment network. The gaming environment network may be configured to allow communication between the gaming environment device, the portable electronic device, and at least one value transfer device.


If the portable electronic device is authenticated at 764, a fund transfer request can be received at 766. The fund transfer request can be received at the value transfer device to which the funds are to be transferred to or at the gaming environment device. In one embodiment, the fund transfer request can be received using any wireless communication technology such as IEEE 802.11x, Bluetooth, cellular technology such as 3G and 4G, radio frequency, near-field magnetics, and the like. In another embodiment, the fund transfer request can be received using wired communication technology, such as Ethernet cables, USB, Firewire, serial cables, and the like. The fund transfer request may include at least one fund transfer parameter to configure a fund transfer. In one example, the at least one fund transfer parameter may indicate which communications device to use for the fund transfer if the value transfer device has more than one communications device. In another example, the at least one fund transfer parameter may indicate which type of encryption to use to protect the fund transfer.


The fund transfer from the portable electronic device to the value transfer device may be initiated at 768. Initiation of the fund transfer can start the movement of funds from the portable electronic device to the value transfer device. The fund transfer can use any wireless communication technology such as IEEE 802.11x, Bluetooth, cellular technology such as 3G and 4G, radio frequency, near-field magnetics, and the like. Initiation may include preparing the fund transfer, entirely or in part, based upon the at least one fund transfer parameter from the fund transfer request. In one embodiment, initiation of the fund transfer may be performed by the processor of the value transfer device. In another embodiment, initiation of the fund transfer may be performed by the gaming environment device. The gaming environment device can be configured to direct the transfer from the portable electronic device to the value transfer device.


A determination of whether the fund transfer is completed may be made at 770. The determination of whether the fund transfer has completed may be performed by the value transfer device or the gaming environment device. In one example, it may be determined the fund transfer is not complete because funds are still moving from the portable electronic device to the value transfer device. In another example, it may be determined the fund transfer is not complete because of an error. Examples of errors may include, but are not limited to, hardware communication failure, the portable electronic device moving out of range, insufficient funds, and the like.


If the fund transfer is not complete at 770, a determination of whether a predetermined transfer time has elapsed may be made at 776. The predetermined transfer time may be any time limit necessary to transfer the funds. In one example, the transfer time may be approximately between one to five minutes. If the transfer time has elapsed at 776, a fund transfer cancellation notification may be transmitted to the portable electronic device at 778. The fund transfer cancellation notification may include any combination of text, graphics, or other indicia indicating to the user that the fund transfer was not successful.


Once the fund transfer is complete at 770, a confirmation message may be transmitted or sent to the portable electronic device at 772. The confirmation message can confirm that the fund transfer is completed. In one embodiment, the value transfer device may generate and transmit the confirmation message to the portable electronic device. In another embodiment, the gaming environment device may generate and transmit the confirmation message to the portable electronic device. Upon receiving the confirmation message, the portable electronic device may display a transfer success message. The transfer success message may include any combination of text, graphics, or other indicia indicating to the user that the fund transfer was successful.


The funds may be transmitted to the final destination at 774. The user may direct the transferred funds to the final destination using a destination input. The user may perform the destination input on the portable electronic device, the value transfer device, or the gaming environment device. In one embodiment, the final destination may be a tangible representation, such as a voucher, ticket, or currency. For example, the value transfer device may have a printer. The user may perform the destination input directing the value transfer device to print a voucher for the transferred funds. In another embodiment, the final destination may be an account with the gaming environment, a financial institution, or the like.



FIG. 8 illustrates an exemplary flow diagram of a method for transferring funds from or to a gaming device. The method 800 may begin with initiating, at a portable electronic device, a user request to transfer funds at 802. In one embodiment, the user request to transfer funds may be initiated by detecting a user selection of an associated indicator. For example, the portable electronic device may detect user selection of a “Cash Out” indicator, “Money Transfer” indicator (e.g., “Money Transfer” indicator 606 as illustrated in FIG. 6A) or any other similar indicator. In another embodiment, the user request to transfer funds may be an audio command. The audio command may be any audio command received and recognizable by the portable electronic device as an instruction or command to transfer funds. For example, the audio command may include words such as “cash out”, “transfer funds”, and the like.


The portable electronic device may receive funds transfer data for the requested funds transfer at 804. The funds transfer data may include any information, requests, and data to facilitate the transfer of funds. For example, the funds transfer data may include: (i) a request to transfer funds to the gaming machine; (ii) request to cash out and transfer funds from the gaming machine; (iii) fund amount to transfer to the gaming machine; (iv) source of the funds to transfer to the gaming machine; (v) unique user ID and password; (vi) whether to transfer receipt of the funds to the gaming machine or the portable electronic device; (vii) location of the transaction, and any other necessary information to facilitate the transfer of funds from or to the gaming machine.


In one embodiment, a message to “Tap” a sensor device (e.g. sensor device 116 as illustrated in FIG. 1 and sensor device 254 as illustrated in FIG. 2B) associated with the multi-functional peripheral device may be displayed on a display of the portable electronic device at 806. The portable electronic device may display instructions on the display to instruct the user how to initiate the transfer of funds to the gaming device. For example, the instructions may be to “Please Tap To Sensor Device To Initiate Money Transfer”. In another embodiment, portable electronic device may instruct the user to orally confirm transfer of funds to a microphone of the multi-functional peripheral device rather than tap a sensor device. For example, the instructions 644 may be to “Please Confirm Transfer By Saying ‘Initiate Money Transfer’ Into The Microphone”.


The multi-functional peripheral device may determine whether to request associated data from the portable electronic device at 808. In one embodiment, the associated data may be encrypted using any known encryption method such as Advanced Encryption Standard (AES), Message Authentication Code (MAC), Hash based Message Authentication Code (HMAC), SHA-2, and the like. The associated data may be any information or data necessary to complete a transfer of funds to the gaming machine such as: (i) the fund amount; (ii) the source of the funds; (iii) unique user ID and password; (iv) account information (e.g. bank routing number, checking account number, credit card number, and the like); (v) destination address (e.g. gaming machine identification to ensure funds are transferred to the proper gaming machine); (vi) location of the transaction, and any other necessary information to facilitate the transfer of funds to the gaming device. The gaming machine may be identified by any known methods such as MAC address, IP address, unique gaming machine identification, bar code on the gaming machine, location information for the gaming machine, and the like. For example, the user may manually input the unique gaming machine identification in the portable electronic device. In another embodiment, the user may scan a bar code on the gaming machine into the portable electronic device.


Thus, the determination may be based on whether the funds transfer request is requested from the gaming machine or to the gaming machine. In other words, if the funds transfer request is to transfer funds to the portable electronic device (i.e. the player would like to cash out of the gaming machine), then the multi-functional peripheral device need not obtain associated data. However, if the funds transfer request is to transfer funds to the gaming machine (i.e. the player would like to play a game of chance on the gaming machine), then the multi-functional peripheral device will need associated data to facilitate the transfer of funds.


If the multi-functional peripheral device receives associated data at 808, the multi-functional peripheral device may authenticate the user at 810. In one embodiment, the multi-functional peripheral device may authenticate the user by transmitting the username and password to the authentication server (e.g. authentication server 130 illustrated in FIG. 1). In another embodiment, an authentication request may be transmitted to the gaming machine to transmit the username and password to the authentication server. It will now be known that any server configured to authenticate and/or verify a user may be used, such as the player tracking server (e.g. player tracking server 124 illustrated in FIG. 1). Additionally, although username and password credentials are illustrated in the authentication process, any other type of credentials or criteria maybe used. For example, biometrics such as facial features, fingerprints, voice prints, and the like, may be used.


In one embodiment, verification the location of the gaming device and/or the location of the user's portable electronic device may be required as additional parameters for a complete authorization of the transaction. Location data may be obtained automatically without user interaction or input using various location determining technology such as global positioning systems (GPS), triangulation and trilateration with cellular towers, Wi-Fi access points locationing, radio frequency (RF) fingerprinting, and the like. For instance, Wi-Fi based location appliances, such as the Cisco Wireless Location Appliance™ manufactured by Cisco Systems, Inc. (San Jose, California, US), may be used as a location tracking system to determine the location of the portable electronic device and the gaming devices inside a casino.


It is common for the local gaming control jurisdiction to have rules regarding where gaming can take place and the maximum funds that can be transferred in a transaction. Location data of the gaming device, inferred by the location of the multi-functional peripheral device housed inside its cabinet, is desirable to verify that the gaming device is in a location where gaming is allowed, such as a casino. Similarly, location data of the portable electronic device is desirable to verify that the user initiating the funds transfer request is indeed near the verified location of an approved gaming device. Other transaction requirements such as fund transfer amount can also be verified as not to exceed allowable amount.


The authentication server may compare the received username and password to a previously submitted and/or saved username and password stored in a database of the authentication server. If there is no match, the authentication server may transmit an error message to the gaming machine and/or the multi-functional peripheral device, which in turn may transmit an error notification to the portable electronic device for display on a display of the portable electronic device at 818.


If there is a match, the authentication server may transmit a successful message to the gaming machine and/or multi-functional peripheral device. In one embodiment, the multi-functional peripheral device may then transmit the associated data to the gaming machine at 812 to process the funds transfer request. In another embodiment, the multi-functional device may process the funds transfer request and transmit the associated data to a third party server (e.g. third-party server 120 as illustrated in FIG. 1) or the gaming server (e.g. gaming server 112 as illustrated in FIG. 1). The multi-functional device may parse the funds transfer request to determine at least one of (i) the fund amount; (ii) the source of the funds; (iii) unique user ID and password; (iv) sufficient funds to transfer the fund amount, (v) location of the transaction, and any other necessary information to facilitate the transfer of funds from or to the gaming machine. For example, the multi-functional peripheral device may determine that the user would like to debit $100 from his Credit Union checking account. The multi-functional peripheral device may transmit a debit request to the Credit Union server (e.g. third-party server 120 as illustrated in FIG. 1). The debit request may include the fund amount, user ID and password, bank routing and checking account number, and any other necessary information or data. If there are sufficient funds in the user's checking account, the Credit Union may debit the user's checking account by the fund amount and transmit the fund amount to the multi-functional peripheral device.


In another embodiment, the multi-functional peripheral device may determine that the user would like to charge $100 to his credit card. The multi-functional peripheral device may transmit a charge request to the credit card server (e.g. third-party server 120 as illustrated in FIG. 1). The charge request may include the fund amount, user ID and password, credit card number, security code, zip code, and any other necessary information or data. If the user's credit limit is not exceeded, the user's account may be charged the fund amount and the fund amount may be transmitted to the multi-functional peripheral device.


In still another embodiment, the multi-functional peripheral device may determine that the user would like to debit player credits from the user's player tracking account. The multi-functional peripheral device may transmit a debit credit request to the player tracking server (e.g. player tracking server 124 as illustrated in FIG. 1). The debit credit request may include the fund amount, user ID and password, player tracking number, and any other necessary information or data. If the user has sufficient credit in his player tracking account, the user's account may be debited the credit amount and the credit amount may be transmitted to the multi-functional peripheral device.


If the multi-functional peripheral device receives a fund amount acknowledgement at 814 from the third-party server or the gaming server, a successful acknowledgement may be transmitted to the portable electronic device for display on a display of the portable electronic device at 816. In one example, the portable electronic device 600 may present a message such as “Congratulations: You have successfully transferred $100.00”. Additionally, the multi-functional peripheral device may also send a digital receipt of the transaction record to the portable electronic device as well as storing a copy in its own memory for accounting, auditing, dispute resolution, and verification purposes. In one embodiment, the amount of funds or credits received by the multi-functional peripheral device may also be displayed on a display of the gaming device as credits for use in playing a game of chance on the gaming machine. The multi-functional peripheral device may transmit a funds notification to the gaming machine processor to notify the gaming machine that the user has transferred funds to the gaming machine. The gaming machine processor may then display the credit amount on the display of the gaming device.


If the multi-functional peripheral device does not receive associated data at 808, in one embodiment, the multi-functional peripheral device may transmit a cash out request to the gaming machine and wait for a cash out acknowledgement and/or confirmation from the gaming machine at 814. If the multi-functional peripheral device does not receive a cash out acknowledgement at 814, an error notification may be transmitted to the portable electronic device for display on a display of the electronic device at 818.


If the multi-functional peripheral device receives a cash out acknowledgement at 814, in one embodiment, the multi-functional peripheral device may inform the portable electronic device of the successful transfer of funds to the portable electronic device at 816 and print an electronically-readable ticket on a printer associated with the multi-functional peripheral device. In another embodiment, the multi-functional peripheral device may inform the portable electronic device of the successful transfer of funds to the portable electronic device at 816 and transmit a digital ticket to the portable electronic device. The virtual digital ticket may be presented on the display and/or saved in a memory associated with the portable electronic device. In one embodiment, the virtual digital ticket may be encrypted using any known encryption method such as AES, MAC, HMAC, SHA-2, and the like.



FIG. 9 illustrates an exemplary flow diagram of a method for transferring funds to a gaming device from a portable electronic device. The method 900 may begin with determining whether a sensory input is detected or received by a multi-functional peripheral device at 830. If no sensory input is detected or received, then the multi-functional peripheral device may continue to wait for a sensory input.


The sensory input may be detected or received by a sensor device associated with the multi-functional peripheral device. The sensory device may be any known device configured to detect and/or receive a sensory input. For example, the sensor device may be an accelerometer, camera, microphone, touchpad, retina scanner, radio frequency identification reader, near-field magnetic reader, or any other device capable of receiving and detecting sensory input.


The sensory input may be any type of known sensory input such as an audio, visual, and/or physical contact received from a user. The type of sensory input received or detected may be based on the sensory device. For example, a user may physically contact the sensor device via a tap, touch, or any other physical contact on a touchpad. The physical contact may initiated by the user (e.g. using a finger to tap the sensor device), physical object (e.g. pen, coin, and the like), and/or a remote device associated with the user. The remote device may, for example, be any portable computing device such as a cellular phone, portable media player, PDA, and the like. In another embodiment, the sensory input may be an audio input received by a microphone associated with the multi-functional peripheral device.


If the multi-functional peripheral device detects a sensory input at 830, the multi-functional peripheral device may request associated data from the portable electronic device at 832. The associated data may be any information or data necessary to complete a transfer of funds to the gaming machine such as: (i) the fund amount; (ii) the source of the funds; (iii) unique user ID and password; (iv) account information (e.g. bank routing number, checking account number, credit card number, and the like); (v) destination address (e.g. gaming machine identification to ensure funds are transferred to the proper gaming machine); (vi) location of the transaction, and any other necessary information to facilitate the transfer of funds to the gaming device. The gaming machine may be identified by any known methods such as MAC address, IP address, unique gaming machine identification, bar code on the gaming machine, location information for the gaming machine, and the like. For example, the user may manually input the unique gaming machine identification in the portable electronic device. In another embodiment, the user may scan a bar code on the gaming machine into the portable electronic device.


In one embodiment, verification the location of the gaming device and/or the location of the user's portable electronic device maybe required as additional parameters for a complete authorization of the transaction. Location data may be obtained automatically without needing the user inputs by various locationing technology such as GPS, triangulation and trilateration with cellular towers, Wi-Fi access points locationing, RF fingerprinting, and the like. For instance, Wi-Fi based location appliances, such as the Cisco Wireless Location Appliance™ manufactured by Cisco Systems, Inc. (San Jose, California, US), may be used as a location tracking system to determine the location of the portable electronic device and the gaming devices inside a casino.


It is common for the local gaming control jurisdiction to have rules regarding where gaming can take place and the maximum funds that can be transferred in a transaction. Location data of the gaming device, inferred by the location of the multi-functional peripheral device housed inside its cabinet, is desirable to verify that the gaming device is in a location where gaming is allowed, such as a casino. Similarly, location data of the portable electronic device is desirable to verify that the user initiating the funds transfer request is indeed near the verified location of an approved gaming device. Other transaction requirements such as fund transfer amount can also be verified as not to exceed allowable amount.


Once the multi-functional peripheral device receives the associated data at 834, the multi-functional peripheral device may process the associated data to determine whether funds are to be transferred at 836. In one embodiment, the associated data may be encrypted using any known encryption method such as AES, MAC, HMAC, SHA-2, and the like. The multi-functional peripheral device may parse the associated data for a unique user ID, password, fund amount, funding source (e.g. a bank routing and checking account number, player tracking account number, credit card number, and the like), transaction location, and any other information or data necessary to facilitate the transfer of funds.


If the multi-functional peripheral device determines that funds are to be transferred to the gaming device at 836, the multi-functional peripheral device may initiate a funds transfer at 838. On the other hand, if the multi-functional peripheral device determines that funds are not to be transferred to the gaming device 836, the multi-functional peripheral device may perform other processing functions at 846. Other processing functions may, for example, be determining whether the received sensory input is associated with playing a game of chance, social networking, or any other non-gaming functions. For example, a visual sensory input received by a camera may be used to play a game of chance. The camera may detect user gestures to represent user actions such as hit, stand, double down, and the like. In another example, a visual sensory input may be received by the camera to allow the player to video conference with friends within this social network.


If the funds transfer is completed at 840, the gaming device may display a funds transfer result on a display (e.g., display 208 as illustrated in FIG. 2A, display 256 as illustrated in FIG. 2B) of the gaming device at 842. The gaming device may display the additional funds transferred to the gaming machine as credits to allow the player to play the game of chance.


A funds transfer notification may be transmitted to the portable electronic device at 844 to inform the user of the successful transfer of funds. In one embodiment, the portable electronic device may display a successful funds transfer notification informing the user of the completion of the transfer of funds as well as the total amount of credits that are on the gaming machine. Additionally, the multi-function peripheral device may also send a digital receipt of the transaction record to the portable electronic device as well as storing a copy in its own memory for accounting, auditing, dispute resolution, and verification purposes.



FIG. 10 illustrates a block diagram of example states of operation for the transfer of funds. States of operation for fund transfer may occur in a gaming environment (e.g. as illustrated in FIG. 12) and may be performed using a fund transfer system (e.g. as illustrated in FIG. 11).


During a transfer of funds to a portable electronic device state 1002, a user may transfer funds from a value transfer device to a portable electronic device, as described, for example in detail with reference to FIG. 7D. The portable electronic device can be any portable electronic device configured to play a game of chance, such as a cellular phone, smartphone, portable media player, tablet computer, laptop computer, PDA, or the like. During the transfer of funds to a portable electronic device state 1002, the value transfer device may detect a sensory input from the portable electronic device. A fund amount to be transferred can be determined as well as any other transfer criteria. The fund amount can be transferred to the portable electronic device.


In one embodiment, the value transfer device can be a gaming machine, such as a slot machine, video poker machine, and any other machine configured to play a game of chance. The gaming machine may have a multi-functional peripheral device. If the value transfer device is a gaming machine, the transfer of funds to a portable electronic device state 1002 may occur in a gaming section of the gaming environment. The gaming section may be a portion of the gaming environment authorized for gaming machines configured to play a game of chance.


In another embodiment, the value transfer device can be a non-gaming machine, such as a kiosk, a portable electronic device, information terminal, automatic teller machine, or the like. The non-gaming machine can have the multi-functional peripheral device. If the value transfer device is a non-gaming machine, the transfer of funds to a portable electronic device state 1002 can occur in the gaming section or a non-gaming section of the gaming environment. For example, on a cruise ship, a plurality of slot machines may reside in a casino, while a plurality of kiosks may reside both within the cruise ship and other non-gaming areas of the cruise ship.


The transferred fund amount may be used to play a game of chance at state 1004. The user may play a game of chance with the funds transferred to the portable electronic device. In one embodiment, the user can play the game of chance on the portable electronic device via a representation on the portable electronic device. The representation can be a game terminal application configured to receive a plurality of game data generated by the gaming machine. In another example, the representation may be configured to receive the plurality of game data generated by a gaming server.


The user may perform at least one gaming input using an input mechanism (e.g. buttons, joystick, keyboard, and the like) of the portable electronic device. The portable electronic device may transmit the input to the gaming machine or the gaming server for execution. In another embodiment, the user can play the game of chance on the portable electronic device using a game of chance program. The game of chance program may be configured to generate the plurality of game data and execute the at least one gaming input on the portable electronic device. If the user plays the game of chance on the portable electronic device, game of chance using the transfer fund amount at state 1004 may occur in the gaming section or the non-gaming section.


In yet another embodiment, the user can play the game of chance on a gaming machine. For example, after transferring funds to the portable electronic device, the user may walk around the gaming environment to locate a gaming machine of interest. Upon locating the gaming machine of interest, the user may transfer the funds to the gaming machine of interest during a transfer of funds out the portable electronic device at state 1006. The user may transfer the funds from the portable electronic device to the gaming machine of interest.


During the transfer the funds out of the portable electronic device at state 1006, the funds may be transferred to a value transfer device. The value transfer device may detect a presence of the portable electronic device and authenticate the portable electronic device. The value transfer device can then receive a fund transfer request. The value transfer device may initiate transfer of the funds to the value transfer device to play a game of chance on the gaming machine.



FIG. 11 illustrates an example fund transfer system 1100. The fund transfer system 1100 can be used in a gaming environment (e.g., the gaming environment described and illustrated in FIG. 12). States of operation for a fund transfer (e.g., as described and illustrated in FIG. 10) may be performed via the fund transfer system 1100. The fund transfer system 1100 may include a gaming server 1102, at least one value transfer device 1104a-b, a multi-functional peripheral device 1106, a portable electronic device 1108, and a network 1110. Although FIG. 11 is illustrated with one portable electronic device, one multi-functional peripheral device, and one gaming server, this is not intended to be limiting as there may be any number of portable electronic devices, multi-functional peripheral devices, and servers. For example, value transfer device 1104b may also have a multi-functional peripheral device.


Network 1110 can be configured to provide and allow communication between the gaming server 1102, the at least one value transfer device 1104a-b, the multi-functional peripheral device 1106 (as illustrated in FIGS. 4C, 4D, 4E), and the portable electronic device 1108. The network 1110 can use any combination of wireless and wired communications technology such as IEEE 802.11x, cellular technology such as 3G and 4G, radio frequency, Ethernet cabling, and the like.


The gaming server 1102 can be configured to communicate with other servers, such as a player tracking server, authentication server, TITO server, social networking server, and the like. In one embodiment, if the at least one value transfer device 1104a-b is a gaming machine, the gaming server 1102 may transmit game of chance software to the at least one value transfer device 1104a-b for execution by the at least one value transfer device 1104a-b.


In one embodiment, the gaming server 1102 may facilitate playing a game of chance on the portable electronic device 1108. The gaming server 1102 may facilitate playing the game of chance on the portable electronic device 1108 by generating a plurality of game data for the game of chance. The plurality of game data can be presented to a player using a graphical user interface of the portable electronic device 1108. In an embodiment, the gaming server 1102 may transmit the plurality of game data to the portable electronic device 1108 via the network 1110. In another embodiment, the gaming server 1102 can transmit the plurality of game data to one of the at least one value transfer devices 1104a. The one of the at least one value transfer devices 1104a may be operative with the multi-functional peripheral device 1106. The multi-functional peripheral devices 1106 can wireless transmit the plurality of game data to the portable electronic device 1108.


The at least one value transfer device 1104a-b can transfer funds to and from the portable electronic device 1108. The at least one value transfer device 1104a-b can transfer funds by detecting a sensory input from the portable electronic device 1108, identifying a fund amount to be transferred, and initiating transfer of funds. The at least one value transfer device 1104a-b can be a gaming machine, automatic teller machine, kiosk, another portable electronic device, information terminal, or any other primary machine from which funds can be transferred to and from the portable electronic device 1108. If the at least one value transfer device 1104a-b is a gaming machine, the game of chance can be played on the gaming machine. In one embodiment, the at least one value transfer device 1104a may be operative with the multi-functional peripheral device 1106. In another embodiment, the multi-functional peripheral device 1106 can be integrated into the at least one value transfer device 1104b. The multi-functional peripheral device 1106 may be the multi-functional peripheral device as described and illustrated in FIGS. 4C, 4D, and 4E.


The portable electronic device 110 can be a cellular phone, smartphone, portable media player, tablet computer, laptop computer, PDA, or the like. The portable electronic device 1108 can have a processor, a display, an input device and a PED memory. The processor may be configured to communicate with the multi-functional peripheral device 1106, the at least one value transfer device 1104a-b, and the gaming server 1102. The display can be any display technology commonly used in portable electronic devices, such as LCD, OLED, AMOLED, and the like. The input device may be any mechanism commonly used to make inputs, such as a button, key, touch screen, microphone, and the like.


The PED memory may be configured to store a PED software module. The PED software module may include a fund management application configured to facilitate transfer of funds. The PED software module can include a game application. In one embodiment, the game application may generate the plurality of game data for the game of chance. In another embodiment, the game application may present the plurality of game data received from the gaming server 1102. Any programs or application of the PED software module, including the fund management application and the game application, may be presented on the display of the portable electronic device 1108 using a graphical user interface.


In one embodiment, where the gaming server 1102 generates the plurality of game data, the player may play the game of chance by performing at least one game input using the input device of the portable electronic device which can be transmitted to the gaming server 1102, for execution, over the network 1110. In another embodiment, where the portable electronic device 1108 generates the plurality of game data, the at least one game input can be processed and executed by the processor of the portable electronic device.



FIG. 12 illustrates an example gaming environment. Although the gaming environment 1200 is illustrated as a ship, this is not intended to be limiting as the gaming environment 1200 can be any environment where a game of chance may be played, such as a casino, race track, restaurant, shopping center, airport, fair ground, and the like.


The gaming environment 1200 may have at least one gaming section 1204 and at least one non-gaming section 1202. The gaming section 1204 may be a portion of the gaming environment 1200 authorized to house gaming machines configured to play a game of chance. The non-gaming section 1202 can be any portion of the gaming environment where no gaming machines are housed.


As illustrated, the gaming environment may be a cruise ship. The gaming section 1204 may be a specific area whereby a plurality of gaming machines is housed. The non-gaming section 1202 may be the remaining areas of the cruise ship such as a dining area (e.g., such as a restaurant, a bar 1214, a cafeteria, and the like); the cabins or rooms; an entertainment area; or recreation areas (e.g., pool 1212, gym, basketball court, and the like).


The gaming environment 1200 may have a plurality of value transfer devices 1206a-c. The value transfer device 1206a-c may be a gaming machine, automatic teller machine, kiosk, another portable electronic device, information terminal, and the like. The value transfer devices 1206a-c may be configured to transfer funds to and from of the gaming machines and/or portable electronic devices as described above.


The at least one gaming machines may be located in the gaming section 1204 and configured to transfer funds to and from the portable electronic device as well as allow the user to play a game of chance. The at least one automatic teller machine, the at least one kiosk, the at least one other portable electronic device, and the at least one information terminal can be located in the gaming section 1204 and the non-gaming section 1202 and configured to transfer funds to and from the portable electronic device.


Users of the gaming environment 1200 can transfer funds to and from the portable electronic device. In one embodiment, the users can transfer funds to and from the portable electronic device using a value transfer device 1206a-b of the gaming section 1204. For example, a user 1208a can transfer funds to or from a smartphone using an information terminal 1206b of the cruise casino. In another example, a user 1208c may transfer funds to or from a netbook computer of the user 1208c using a slot machine 1206a of the cruise casino. In another embodiment, the plurality of users can transfer funds to and from the portable electronic device us a value transfer device 1206c of the non-gaming section 1202. For example, a user 1208b can transfer funds to or from a personal digital assistant using an automatic teller machine 1206c positioned at or near the bar 1214, the non-gaming section 1202 of the cruise ship gaming environment.


Users of the gaming environment 1200 can play a game of chance. In one embodiment, the plurality of users can play the game of chance on the at least one gaming machine 1206a. If the game of chance is played on the at least one gaming machine, the game of chance can be played in the gaming section 1204. For example, a user 1210a can be playing video poker with funds transferred to a laptop of the user 12010a at a video poker machine in the cruise casino. In another embodiment, the plurality of users can play the game of chance on the portable electronic device. If the game of chance is played on the portable electronic device, the game of chance can be played in the gaming section 1204 or the non-gaming section 1202. For example, a user 1210b can play a Wheel of Fortune game of chance on a portable media player while on the cruise casino. Gaming data for the Wheel of Fortune game of chance may be generated on the portable electronic device of the user 1210b. Gaming data for the Wheel of fortune game of chance may also be generated on a Wheel of Fortune gaming machine and streamed to the portable electronic device of user 1210b. In another example, user 1210c can play a blackjack game of chance on a tablet computer while the user 1210c is sitting in the pool 1212, the non-gaming section 1202 of the cruise boat gaming environment.


Additional details on peripheral devices for gaming machines are provided in U.S. patent application Ser. No. 12/945,889, entitled “PERIPHERAL MANAGEMENT DEVICE FOR VIRTUAL GAME INTERACTION,” filed Nov. 14, 2010, and hereby incorporated herein by reference.


While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein. For example, although illustrated with use in a gaming environment, this is not intended to be limiting as other uses are contemplated, such as in a banking machine, snack or drink machine at an educational environment, grocery store, gas station and the like.

Claims
  • 1. A gaming device, comprising: a display screen configured to display a representation of a game of chance;a housing;a bezel coupled to an exterior of the housing;a sensor device coupled to the bezel, the sensor device comprising an accelerometer, a near field magnetic reader, or a Bluetooth sensor, the sensor device being configured to detect a sensory input induced by a debit instrument;a wireless communication device;memory circuitry storing a cashable credit value available to play a game of chance on the gaming device, and a proximity setting defining a threshold distance; andprocessing circuitry configured to: determine whether the sensory input indicates that the debit instrument is in close proximity to the gaming device,wherein determining whether the sensory input indicates that the debit instrument is in close proximity to the gaming device comprises accessing the proximity setting stored in the memory circuitry, and determining whether the sensory input indicates the debit instrument is within the threshold distance of the gaming device defined by the proximity setting stored in the memory circuitry,in response to the sensory input indicating that the debit instrument is in close proximity to the gaming device, establish a wireless connection between the debit instrument and the gaming device using the wireless communication device,receive from the debit instrument, by the wireless connection, a request to electronically transfer the cashable credit value from the gaming device to a wagering account associated with the debit instrument, as well as a transfer parameter identifying the wagering account, andprocess the request to electronically transfer the cashable credit value from the gaming device to the wagering account.
  • 2. The gaming device of claim 1, wherein the sensor device comprises the Bluetooth sensor.
  • 3. The gaming device of claim 1, wherein the debit instrument comprises a device with which a patron can initiate an electronic transfer of funds to the gaming device.
  • 4. The gaming device of claim 1, wherein the threshold distance is within three inches of the gaming device.
  • 5. The gaming device of claim 1, wherein the bezel comprises a slot configured to accept a bill, a coin, a card, or a ticket.
  • 6. The gaming device of claim 5, wherein the bezel comprises a light source.
  • 7. The gaming device of claim 6, wherein the sensor device is positioned within a cavity of the bezel.
  • 8. A method for electronically transferring funds from a gaming device, the method comprising: receiving, by a slot of a bezel of the gaming device, a cash value input of a bill, a coin, or a ticket having a cash value;in response to receiving the cash value input, increasing a cashable credit value available to play a game of chance on the gaming device;receiving, by a sensor device of the gaming device that is coupled to the bezel, a sensory input from a debit instrument, the sensor device comprising an accelerometer, a near field magnetic reader, or a Bluetooth sensor;determining, using processing circuitry of the gaming device, whether the sensory input indicates that the debit instrument is in close proximity to the gaming device,wherein determining whether the sensory input indicates that the debit instrument is in close proximity to the gaming device comprises accessing a proximity setting stored in memory circuitry of the gaming device, and determining whether the sensory input indicates the debit instrument is within a threshold distance of the gaming device, the proximity setting indicating the threshold distance;in response to determining the sensory input indicates that the debit instrument is in close proximity to the gaming device, establishing a wireless connection between the debit instrument and the gaming device;receiving from the debit instrument, at the gaming device, by the wireless connection, a request to electronically transfer the cashable credit value from the gaming device to a wagering account associated with the debit instrument, as well as a transfer parameter identifying the wagering account; andprocessing the request by the processing circuitry of the gaming device to electronically transfer the cashable credit value from the gaming device to the wagering account.
  • 9. The method of claim 8, wherein the wireless connection is established by a wireless communication device of the gaming device.
  • 10. The method of claim 8, wherein the threshold distance is within three inches of the gaming device.
  • 11. The method of claim 8, wherein the debit instrument comprises a device with which a patron can initiate an electronic transfer of funds to the gaming device.
  • 12. The method of claim 8, wherein the sensor device comprises the Bluetooth sensor.
  • 13. The method of claim 8, wherein the sensor device is positioned within a cavity of the bezel.
  • 14. A method for initiating an electronic fund transfer from a gaming device by a debit instrument, the method comprising: providing, by the debit instrument, a sensory input to a sensor of the gaming device, the sensory input also being received by a sensor device of the debit instrument;establishing a wireless connection between the debit instrument and the gaming device using a wireless communication module of the debit instrument;determining a function associated with the sensory input via processing circuitry of the debit instrument, wherein determining the function comprises accessing, via the processing circuitry, a sensory database of the debit instrument, the sensory database storing at least one sensory input and at least one sensory associated function, the at least one sensory input comprising the sensory input, and the at least one sensory associated function comprising an electronic transfer function;in response to determining the function associated with the sensory input is the electronic transfer function, sending an electronic transfer request from the debit instrument to the gaming device through the wireless connection, the electronic transfer request indicating that a cashable credit value available to play a game of chance on the gaming device should be transferred to a wagering account associated with the debit instrument; andaccessing, at the debit instrument, the cashable credit value in the wagering account.
  • 15. The method of claim 14, further comprising sending one or more transfer parameters from the debit instrument to the gaming device through the wireless connection, the one or more transfer parameters identifying the wagering account, or comprising credentials of a patron associated with the wagering account and the debit instrument.
  • 16. The method of claim 14, wherein the debit instrument comprises a device with which a patron can initiate the electronic fund transfer of funds to the gaming device or initiate an electronic debit.
  • 17. The method of claim 14, wherein the sensory input indicates that the debit instrument is proximate to the gaming device.
  • 18. The method of claim 14, wherein the sensor comprises an accelerometer, a near field magnetic reader, or a Bluetooth sensor.
  • 19. The method of claim 18, wherein the sensor comprises the Bluetooth sensor.
  • 20. The method of claim 14, wherein the game of chance comprises a first game of chance, and the method further comprises playing a second game of chance on the debit instrument using the cashable credit value in the wagering account.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is continuation-in-part of U.S. patent application Ser. No. 12/945,888, filed Nov. 14, 2010, and entitled “MULTI-FUNCTIONAL PERIPHERAL DEVICE”, which is hereby incorporated herein by reference for all purposes.

US Referenced Citations (658)
Number Name Date Kind
2033638 Koppl Mar 1936 A
2062923 Nagy Dec 1936 A
4741539 Sutton et al. May 1988 A
4948138 Pease et al. Aug 1990 A
4969183 Reese Nov 1990 A
5067712 Georgilas Nov 1991 A
5275400 Weingardt Jan 1994 A
5429361 Raven et al. Jul 1995 A
5489103 Okamoto Feb 1996 A
5618232 Martin Apr 1997 A
5630757 Gagin May 1997 A
5655961 Acres et al. Aug 1997 A
5704835 Dietz, II Jan 1998 A
5727786 Weingardt Mar 1998 A
5833537 Barrie Nov 1998 A
5842921 Mindes Dec 1998 A
5919091 Bell et al. Jul 1999 A
5947820 Morro et al. Sep 1999 A
5997401 Crawford Dec 1999 A
6001016 Walker et al. Dec 1999 A
6039648 Guinn et al. Mar 2000 A
6059289 Vancura May 2000 A
6089977 Bennett Jul 2000 A
6095920 Sudahiro Aug 2000 A
6110041 Walker et al. Aug 2000 A
6142872 Walker et al. Nov 2000 A
6146271 Kadici Nov 2000 A
6146273 Olsen Nov 2000 A
6165071 Weiss Dec 2000 A
6231445 Acres May 2001 B1
6244958 Acres Jun 2001 B1
6270412 Crawford et al. Aug 2001 B1
6290600 Glasson Sep 2001 B1
6293866 Walker et al. Sep 2001 B1
6353390 Beri et al. Mar 2002 B1
6364768 Acres et al. Apr 2002 B1
6404884 Marwell et al. Jun 2002 B1
6416406 Duhamel Jul 2002 B1
6416409 Jordan Jul 2002 B1
6443452 Brune Sep 2002 B1
6491584 Graham et al. Dec 2002 B2
6500067 Luciano Dec 2002 B1
6505095 Kolls Jan 2003 B1
6508710 Paravia et al. Jan 2003 B1
6561900 Baerlocker et al. May 2003 B1
6592457 Frohm et al. Jul 2003 B1
6612574 Cole et al. Sep 2003 B1
6620046 Rowe Sep 2003 B2
6641477 Dietz, II Nov 2003 B1
6645078 Mattice Nov 2003 B1
6675152 Prasad Jan 2004 B1
6699128 Beadell Mar 2004 B1
6719630 Seelig et al. Apr 2004 B1
6749510 Globbi Jun 2004 B2
6758757 Luciano, Jr. et al. Jul 2004 B2
6773345 Walker et al. Aug 2004 B2
6778820 Tendler Aug 2004 B2
6780111 Cannon et al. Aug 2004 B2
6799032 McDonnell et al. Sep 2004 B2
6800027 Giobbi et al. Oct 2004 B2
6804763 Stockdale et al. Oct 2004 B1
6811486 Luciano, Jr. Nov 2004 B1
6843725 Nelson Jan 2005 B2
6846238 Wells Jan 2005 B2
6848995 Walker et al. Feb 2005 B1
6852029 Baltz et al. Feb 2005 B2
6869361 Sharpless et al. Mar 2005 B2
6875106 Weiss et al. Apr 2005 B2
6884170 Rowe Apr 2005 B2
6884172 Lloyd et al. Apr 2005 B1
6902484 Idaka Jun 2005 B2
6908390 Nguyen et al. Jun 2005 B2
6913532 Bearlocher et al. Jul 2005 B2
6923721 Luciano et al. Aug 2005 B2
6935958 Nelson Aug 2005 B2
6949022 Showers Sep 2005 B1
6955600 Glavich et al. Oct 2005 B2
6971956 Rowe et al. Dec 2005 B2
6984174 Cannon et al. Jan 2006 B2
6997803 LeMay et al. Feb 2006 B2
7018292 Tracy et al. Mar 2006 B2
7032115 Kashani Apr 2006 B2
7033276 Walker et al. Apr 2006 B2
7035626 Luciano Apr 2006 B1
7037195 Schneider et al. May 2006 B2
7048628 Schneider May 2006 B2
7048630 Berg et al. May 2006 B2
7063617 Brosnan et al. Jun 2006 B2
7076329 Kolls Jul 2006 B1
7089264 Guido et al. Aug 2006 B1
7094148 Bearlocher et al. Aug 2006 B2
7105736 Laakso Sep 2006 B2
7111141 Nelson Sep 2006 B2
7144321 Mayeroff Dec 2006 B2
7152783 Charrin Dec 2006 B2
7169041 Tessmer et al. Jan 2007 B2
7169052 Beaulieu et al. Jan 2007 B2
7175523 Gilmore et al. Feb 2007 B2
7181228 Boesch Feb 2007 B2
7182690 Giobbi et al. Feb 2007 B2
7198571 LeMay Apr 2007 B2
RE39644 Alcorn et al. May 2007 E
7217191 Allen et al. May 2007 B2
7243104 Bill Jul 2007 B2
7247098 Bradford et al. Jul 2007 B1
7259718 Patterson et al. Aug 2007 B2
7275989 Moody Oct 2007 B2
7285047 Gielb et al. Oct 2007 B2
7311608 Danieli Dec 2007 B1
7314408 Cannon et al. Jan 2008 B2
7316615 Soltys et al. Jan 2008 B2
7316619 Nelson Jan 2008 B2
7318775 Brosnan et al. Jan 2008 B2
7326116 O'Donovan et al. Feb 2008 B2
7330108 Thomas Feb 2008 B2
7346358 Wood et al. Mar 2008 B2
7355112 Laakso Apr 2008 B2
7384338 Rothschild et al. Jun 2008 B2
7387571 Walker et al. Jun 2008 B2
7393278 Gerson et al. Jul 2008 B2
7396990 Lu et al. Jul 2008 B2
7415426 Williams et al. Aug 2008 B2
7425177 Rodgers et al. Sep 2008 B2
7427234 Soltys et al. Sep 2008 B2
7427236 Kaminkow et al. Sep 2008 B2
7427708 Ohmura Sep 2008 B2
7431650 Kessman Oct 2008 B2
7448949 Kaminkow et al. Nov 2008 B2
7500913 Baerlocher Mar 2009 B2
7510474 Carter Mar 2009 B2
7513828 Nguyen et al. Apr 2009 B2
7519838 Suurballe Apr 2009 B1
7559838 Walker et al. Jul 2009 B2
7563167 Walker et al. Jul 2009 B2
7572183 Olivas et al. Aug 2009 B2
7585222 Muir Sep 2009 B2
7602298 Thomas Oct 2009 B2
7607174 Kashchenko et al. Oct 2009 B1
7611409 Muir et al. Nov 2009 B2
7637810 Amaitis et al. Dec 2009 B2
7644861 Alderucci et al. Jan 2010 B2
7653757 Fernald et al. Jan 2010 B1
7693306 Huber Apr 2010 B2
7699703 Muir et al. Apr 2010 B2
7722453 Lark et al. May 2010 B2
7742996 Kwan Jun 2010 B1
7758423 Foster et al. Jul 2010 B2
7771271 Walker et al. Aug 2010 B2
7780529 Rowe et al. Aug 2010 B2
7780531 Englman et al. Aug 2010 B2
7785192 Canterbury et al. Aug 2010 B2
7811172 Asher et al. Oct 2010 B2
7819749 Fish Oct 2010 B1
7822688 Labron Oct 2010 B2
7828652 Nguyen et al. Nov 2010 B2
7828654 Carter Nov 2010 B2
7828661 Fish Nov 2010 B1
7850528 Wells Dec 2010 B2
7874919 Paulsen et al. Jan 2011 B2
7877798 Saunders et al. Jan 2011 B2
7883413 Paulsen Feb 2011 B2
7892097 Muir et al. Feb 2011 B2
7909692 Nguyen et al. Mar 2011 B2
7909699 Parrott et al. Mar 2011 B2
7918728 Nguyen et al. Apr 2011 B2
7927211 Rowe et al. Apr 2011 B2
7927212 Hedrick et al. Apr 2011 B2
7951008 Wolf et al. May 2011 B2
8057298 Nguyen et al. Nov 2011 B2
8057303 Rasmussen Nov 2011 B2
8087988 Nguyen et al. Jan 2012 B2
8117608 Slettehaugh Feb 2012 B1
8133113 Nguyen Mar 2012 B2
8182326 Speers et al. May 2012 B2
8210927 Hedrick Jul 2012 B2
8221245 Walker Jul 2012 B2
8226459 Barrett Jul 2012 B2
8226474 Nguyen et al. Jul 2012 B2
8231456 Zielinski Jul 2012 B2
8235803 Loose et al. Aug 2012 B2
8276010 Vavilala Sep 2012 B2
8282475 Nguyen et al. Oct 2012 B2
8323099 Durham et al. Dec 2012 B2
8337290 Nguyen et al. Dec 2012 B2
8342946 Amaitis Jan 2013 B2
8393948 Allen et al. Mar 2013 B2
8403758 Homik Mar 2013 B2
8430745 Agarwal et al. Apr 2013 B2
8461958 Saenz Jun 2013 B2
8465368 Hardy et al. Jun 2013 B2
8469813 Joshi Jun 2013 B2
8529345 Nguyen Sep 2013 B2
8597108 Nguyen Dec 2013 B2
8602875 Nguyen Dec 2013 B2
8613655 Kisenwether Dec 2013 B2
8613659 Nelson et al. Dec 2013 B2
8678901 Kelly Mar 2014 B1
8696470 Nguyen Apr 2014 B2
8745417 Huang et al. Jun 2014 B2
8821255 Friedman Sep 2014 B1
8834254 Buchholz et al. Sep 2014 B2
8858323 Nguyen et al. Oct 2014 B2
8864586 Nguyen Oct 2014 B2
8942995 Kerr Jan 2015 B1
9039507 Allen et al. May 2015 B2
9235952 Nguyen Jan 2016 B2
9292996 Davis et al. Mar 2016 B2
9325203 Nguyen Apr 2016 B2
9466171 Hornik Oct 2016 B2
9483901 Nguyen Nov 2016 B2
9486697 Nguyen Nov 2016 B2
9486704 Nguyen Nov 2016 B2
9530277 Nelson et al. Dec 2016 B2
9576425 Nguyen Feb 2017 B2
9626826 Nguyen Apr 2017 B2
9666015 Acres May 2017 B2
9666021 Nguyen May 2017 B2
9672686 Nguyen Jun 2017 B2
9741205 Nguyen Aug 2017 B2
9811973 Nguyen Nov 2017 B2
9814970 Nguyen Nov 2017 B2
9842462 Nguyen Dec 2017 B2
9875606 Nguyen Jan 2018 B2
9875609 Nguyen Jan 2018 B2
9981180 Koyanagi et al. May 2018 B2
10068429 Gagner et al. Sep 2018 B2
10115270 Gagner et al. Oct 2018 B2
10140816 Nguyen Nov 2018 B2
10325447 Malek Jun 2019 B2
10421010 Nguyen Sep 2019 B2
10438446 Nguyen Oct 2019 B2
10445978 Nguyen Oct 2019 B2
10818133 Nguyen Oct 2020 B2
20010004607 Olsen Jun 2001 A1
20010016516 Takatsuka Aug 2001 A1
20010024971 Brossard Sep 2001 A1
20010025272 Mori Sep 2001 A1
20010031659 Perrie Oct 2001 A1
20010047291 Garahi Nov 2001 A1
20020006822 Krintzman Jan 2002 A1
20020042295 Walker et al. Apr 2002 A1
20020043759 Vancura Apr 2002 A1
20020045474 Singer Apr 2002 A1
20020107065 Rowe Aug 2002 A1
20020107799 Hoshino Aug 2002 A1
20020111210 Luciano, Jr. et al. Aug 2002 A1
20020111213 McEntee et al. Aug 2002 A1
20020113369 Weingardt Aug 2002 A1
20020116615 Nguyen et al. Aug 2002 A1
20020133418 Hammond et al. Sep 2002 A1
20020137217 Rowe et al. Sep 2002 A1
20020142825 Lark et al. Oct 2002 A1
20020145051 Charrin Oct 2002 A1
20020147047 Letovsky et al. Oct 2002 A1
20020147049 Carter, Sr. Oct 2002 A1
20020151366 Walker et al. Oct 2002 A1
20020152120 Howington Oct 2002 A1
20020167536 Valdes et al. Nov 2002 A1
20020177483 Cannon Nov 2002 A1
20020183105 Cannon et al. Dec 2002 A1
20030001338 Bennett et al. Jan 2003 A1
20030003996 Nguyen Jan 2003 A1
20030004871 Rowe et al. Jan 2003 A1
20030008696 Abecassis et al. Jan 2003 A1
20030013531 Rowe Jan 2003 A1
20030027635 Walker et al. Feb 2003 A1
20030064805 Wells Apr 2003 A1
20030064807 Walker et al. Apr 2003 A1
20030078094 Gatto Apr 2003 A1
20030092480 White et al. May 2003 A1
20030100361 Sharpless et al. May 2003 A1
20030103965 Jung Jun 2003 A1
20030104860 Cannon et al. Jun 2003 A1
20030104865 Itkis et al. Jun 2003 A1
20030119579 Walker Jun 2003 A1
20030125100 Cannon Jul 2003 A1
20030148809 Nelson Aug 2003 A1
20030162588 Brosnan et al. Aug 2003 A1
20030195024 Slattery Oct 2003 A1
20030199295 Vancura Oct 2003 A1
20030224852 Walker et al. Dec 2003 A1
20030224854 Joao Dec 2003 A1
20040002386 Wolfe et al. Jan 2004 A1
20040005919 Walker et al. Jan 2004 A1
20040023709 Beaulieu et al. Feb 2004 A1
20040023716 Gauselmann Feb 2004 A1
20040038736 Bryant Feb 2004 A1
20040048650 Mierau et al. Mar 2004 A1
20040068460 Feeley Apr 2004 A1
20040082384 Walker Apr 2004 A1
20040082385 Silva et al. Apr 2004 A1
20040094624 Fernandes May 2004 A1
20040106449 Walker et al. Jun 2004 A1
20040137987 Nguyen et al. Jun 2004 A1
20040127277 Walker Jul 2004 A1
20040127290 Walker et al. Jul 2004 A1
20040142744 Atkinson Jul 2004 A1
20040147308 Walker et al. Jul 2004 A1
20040152508 Lind Aug 2004 A1
20040199631 Natsume Oct 2004 A1
20040214622 Atkinson Oct 2004 A1
20040224753 Odonovan et al. Nov 2004 A1
20040229671 Stronach Nov 2004 A1
20040256803 Ko Dec 2004 A1
20040259633 Gentles et al. Dec 2004 A1
20050003890 Hedrick et al. Jan 2005 A1
20050004980 Vadjinia Jan 2005 A1
20050026696 Hashimoto et al. Feb 2005 A1
20050033651 Kogan Feb 2005 A1
20050043996 Silver Feb 2005 A1
20050049037 Anderson Mar 2005 A1
20050054446 Kammler Mar 2005 A1
20050101376 Walker et al. May 2005 A1
20050101383 Wells May 2005 A1
20050130728 Nguyen et al. Jun 2005 A1
20050130731 Englman Jun 2005 A1
20050137014 Vetelaninen Jun 2005 A1
20050143169 Nguyen Jun 2005 A1
20050167921 Finocchio Aug 2005 A1
20050170883 Muskin et al. Aug 2005 A1
20050181865 Luciano Aug 2005 A1
20050181870 Nguyen et al. Aug 2005 A1
20050181875 Hoehne Aug 2005 A1
20050187020 Amaitis et al. Aug 2005 A1
20050202865 Kim Sep 2005 A1
20050202875 Murphy et al. Sep 2005 A1
20050208993 Yoshizawa Sep 2005 A1
20050209002 Blythe et al. Sep 2005 A1
20050221881 Lannert Oct 2005 A1
20050223219 Gatto et al. Oct 2005 A1
20050239546 Hedrick Oct 2005 A1
20050255919 Nelson Nov 2005 A1
20050273635 Wilcox et al. Dec 2005 A1
20050277471 Russell et al. Dec 2005 A1
20050282637 Gatto et al. Dec 2005 A1
20060009283 Englman et al. Jan 2006 A1
20060036874 Cockerille Feb 2006 A1
20060046822 Kaminkow et al. Mar 2006 A1
20060046830 Webb Mar 2006 A1
20060046849 Kovacs Mar 2006 A1
20060068893 Jaffe et al. Mar 2006 A1
20060068897 Sanford Mar 2006 A1
20060073869 LeMay et al. Apr 2006 A1
20060073888 Nguyen Apr 2006 A1
20060073897 Englman et al. Apr 2006 A1
20060079317 Flemming et al. Apr 2006 A1
20060121972 Walker Jun 2006 A1
20060126529 Hardy Jun 2006 A1
20060148551 Walker et al. Jul 2006 A1
20060148560 Arezina Jul 2006 A1
20060189382 Muir et al. Aug 2006 A1
20060217170 Roireau Sep 2006 A1
20060217193 Walker et al. Sep 2006 A1
20060247028 Brosnan et al. Nov 2006 A1
20060247035 Rowe et al. Nov 2006 A1
20060252530 Oberberger et al. Nov 2006 A1
20060253481 Guido et al. Nov 2006 A1
20060256135 Aoyama Nov 2006 A1
20060281525 Borissov Dec 2006 A1
20060281541 Nguyen et al. Dec 2006 A1
20060287106 Jensen Dec 2006 A1
20070004510 Underdahl et al. Jan 2007 A1
20070026935 Wolf et al. Feb 2007 A1
20070026942 Kinsley Feb 2007 A1
20070054739 Amaitis et al. Mar 2007 A1
20070060254 Muir Mar 2007 A1
20070060306 Amaitis et al. Mar 2007 A1
20070060319 Block et al. Mar 2007 A1
20070060358 Amaitas et al. Mar 2007 A1
20070077981 Hungate et al. Apr 2007 A1
20070087833 Feeney et al. Apr 2007 A1
20070087834 Moser et al. Apr 2007 A1
20070093299 Bergeron Apr 2007 A1
20070129123 Eryou et al. Jun 2007 A1
20070129148 Van Luchene Jun 2007 A1
20070149279 Norden et al. Jun 2007 A1
20070149286 Bemmel Jun 2007 A1
20070159301 Hirt et al. Jul 2007 A1
20070161402 Ng et al. Jul 2007 A1
20070184896 Dickerson Aug 2007 A1
20070184904 Lee Aug 2007 A1
20070191109 Crowder et al. Aug 2007 A1
20070207852 Nelson et al. Sep 2007 A1
20070207854 Wolf et al. Sep 2007 A1
20070235521 Mateen Oct 2007 A1
20070238505 Okada Oct 2007 A1
20070241187 Alderucci et al. Oct 2007 A1
20070248036 Nevalainen Oct 2007 A1
20070257430 Hardy et al. Nov 2007 A1
20070259713 Fiden et al. Nov 2007 A1
20070259716 Mattice Nov 2007 A1
20070259717 Mattice et al. Nov 2007 A1
20070265984 Santhana Nov 2007 A1
20070270213 Nguyen et al. Nov 2007 A1
20070275777 Walker et al. Nov 2007 A1
20070275779 Amaitis et al. Nov 2007 A1
20070281782 Amaitis et al. Dec 2007 A1
20070281785 Amaitas et al. Dec 2007 A1
20070298858 Toneguzzo Dec 2007 A1
20070298873 Nguyen et al. Dec 2007 A1
20080013906 Matsuo Jan 2008 A1
20080015032 Bradford Jan 2008 A1
20080020824 Cuddy et al. Jan 2008 A1
20080020845 Low Jan 2008 A1
20080032787 Low et al. Feb 2008 A1
20080070652 Nguyen et al. Mar 2008 A1
20080070681 Marks et al. Mar 2008 A1
20080076505 Nguyen Mar 2008 A1
20080076506 Nguyen et al. Mar 2008 A1
20080076548 Paulsen Mar 2008 A1
20080076572 Nguyen et al. Mar 2008 A1
20080096650 Baerlocher Apr 2008 A1
20080102916 Kovacs May 2008 A1
20080102935 Finnimore May 2008 A1
20080102956 Burman et al. May 2008 A1
20080102957 Burnman et al. May 2008 A1
20080108401 Baerlocker et al. May 2008 A1
20080113772 Burrill et al. May 2008 A1
20080119267 Denlay May 2008 A1
20080126529 Kim et al. May 2008 A1
20080139274 Baerlocher Jun 2008 A1
20080139306 Lutnick Jun 2008 A1
20080146321 Parente Jun 2008 A1
20080146344 Rowe et al. Jun 2008 A1
20080150902 Edpalm et al. Jun 2008 A1
20080153583 Huntley et al. Jun 2008 A1
20080161110 Campbell Jul 2008 A1
20080167106 Lutnick et al. Jul 2008 A1
20080167118 Kroeckel Jul 2008 A1
20080182667 Davis et al. Jul 2008 A1
20080200251 Alderucci Aug 2008 A1
20080207296 Lutnick Aug 2008 A1
20080207307 Cunningham, II et al. Aug 2008 A1
20080167130 Koreckel Sep 2008 A1
20080214258 Brosnan et al. Sep 2008 A1
20080214310 Brunet de Courssou Sep 2008 A1
20080215319 Lu Sep 2008 A1
20080234047 Nguyen Sep 2008 A1
20080238610 Rosenbereg Oct 2008 A1
20080248849 Lutnick Oct 2008 A1
20080248865 Tedesco Oct 2008 A1
20080252419 Batchelor Oct 2008 A1
20080254878 Sauders et al. Oct 2008 A1
20080254881 Lutnick et al. Oct 2008 A1
20080254883 Patel et al. Oct 2008 A1
20080254891 Sauders et al. Oct 2008 A1
20080254892 Sauders et al. Oct 2008 A1
20080254897 Sauders et al. Oct 2008 A1
20080263173 Weber et al. Oct 2008 A1
20080268959 Bryson Oct 2008 A1
20080300058 Sum et al. Dec 2008 A1
20080305864 Kelly et al. Dec 2008 A1
20080305865 Kelly et al. Dec 2008 A1
20080305866 Kelly et al. Dec 2008 A1
20080311994 Amaitas et al. Dec 2008 A1
20080318669 Buchholz Dec 2008 A1
20080318686 Crowder et al. Dec 2008 A1
20090005165 Arezina et al. Jan 2009 A1
20090011822 Englman Jan 2009 A1
20090017906 Jackson Jan 2009 A1
20090021381 Higuchi Jan 2009 A1
20090029766 Lutnick et al. Jan 2009 A1
20090042611 Aigner Feb 2009 A1
20090054149 Brosnan et al. Feb 2009 A1
20090061985 Inamura Mar 2009 A1
20090061990 Schwartz Mar 2009 A1
20090069063 Thomas Mar 2009 A1
20090077396 Tsai et al. Mar 2009 A1
20090088258 Saunders Apr 2009 A1
20090098925 Gagner et al. Apr 2009 A1
20090104977 Zielinski Apr 2009 A1
20090104983 Okada Apr 2009 A1
20090118002 Lyons May 2009 A1
20090118013 Finnimore et al. May 2009 A1
20090118022 Lyons et al. May 2009 A1
20090124366 Aoki et al. May 2009 A1
20090124390 Seelig et al. May 2009 A1
20090131146 Arezina et al. May 2009 A1
20090131151 Harris et al. May 2009 A1
20090131155 Hollibaugh May 2009 A1
20090132163 Ashley et al. May 2009 A1
20090137255 Ashley et al. May 2009 A1
20090138133 Buchholz et al. May 2009 A1
20090143141 Wells Jun 2009 A1
20090149245 Fabbri Jun 2009 A1
20090149261 Chen et al. Jun 2009 A1
20090153342 Thorn Jun 2009 A1
20090156303 Kiely et al. Jun 2009 A1
20090163272 Baker Jun 2009 A1
20090176578 Herrmann et al. Jul 2009 A1
20090191962 Hardy et al. Jul 2009 A1
20090197684 Arezina et al. Aug 2009 A1
20090216547 Canora et al. Aug 2009 A1
20090219901 Bull et al. Sep 2009 A1
20090221342 Katz et al. Sep 2009 A1
20090227302 Abe Sep 2009 A1
20090239666 Hall et al. Sep 2009 A1
20090264190 Davis et al. Oct 2009 A1
20090270166 Thukral Oct 2009 A1
20090270170 Patton Oct 2009 A1
20090271287 Halpern Oct 2009 A1
20090275402 Backover Nov 2009 A1
20090275410 Kisenwether et al. Nov 2009 A1
20090275411 Kisenwether et al. Nov 2009 A1
20090280910 Gagner Nov 2009 A1
20090282469 Lynch Nov 2009 A1
20090298468 Hsu Dec 2009 A1
20100002897 Keady Jan 2010 A1
20100004058 Acres Jan 2010 A1
20100007496 Orlassino Jan 2010 A1
20100016069 Herrmann Jan 2010 A1
20100049738 Mathur et al. Feb 2010 A1
20100056248 Acres Mar 2010 A1
20100062833 Mattice et al. Mar 2010 A1
20100062840 Herrmann et al. Mar 2010 A1
20100079237 Falk Apr 2010 A1
20100081501 Carpenter et al. Apr 2010 A1
20100081509 Burke Apr 2010 A1
20100099499 Amaitis et al. Apr 2010 A1
20100105454 Weber et al. Apr 2010 A1
20100106612 Gupta Apr 2010 A1
20100115591 Kane-Esrig May 2010 A1
20100120486 DeWaal May 2010 A1
20100124967 Lutnick et al. May 2010 A1
20100130276 Fiden May 2010 A1
20100160035 Herrmann Jun 2010 A1
20100160043 Fujimoto et al. Jun 2010 A1
20100178977 Kim et al. Jul 2010 A1
20100184509 Sylla Jul 2010 A1
20100197383 Rad et al. Aug 2010 A1
20100197385 Aoki et al. Aug 2010 A1
20100203955 Sylla Aug 2010 A1
20100203957 Enzminger Aug 2010 A1
20100203963 Allen Aug 2010 A1
20100224681 Triplett Sep 2010 A1
20100227662 Speers et al. Sep 2010 A1
20100227670 Arezina Sep 2010 A1
20100227671 Laaroussi Sep 2010 A1
20100227687 Speers et al. Sep 2010 A1
20100234091 Baerlocher et al. Sep 2010 A1
20100278345 Alsina Nov 2010 A1
20100279764 Allen et al. Nov 2010 A1
20100323780 Acres Dec 2010 A1
20100325703 Etchegoyen Dec 2010 A1
20110009181 Speers et al. Jan 2011 A1
20110039615 Acres Feb 2011 A1
20110053679 Canterbury et al. Mar 2011 A1
20110065492 Acres Mar 2011 A1
20110076941 Taveau Mar 2011 A1
20110086696 MacEwan Apr 2011 A1
20110105216 Cohen May 2011 A1
20110111827 Nicely et al. May 2011 A1
20110111843 Nicely et al. May 2011 A1
20110111860 Nguyen May 2011 A1
20110117991 Belger May 2011 A1
20110118010 Brune May 2011 A1
20110159966 Gura et al. Jun 2011 A1
20110183732 Block Jul 2011 A1
20110183749 Allen Jul 2011 A1
20110189981 Faith Aug 2011 A1
20110207525 Allen Aug 2011 A1
20110212711 Scott Sep 2011 A1
20110212767 Barclay et al. Sep 2011 A1
20110223993 Allen et al. Sep 2011 A1
20110244952 Schueller Oct 2011 A1
20110263318 Agarwal et al. Oct 2011 A1
20110269548 Barclay et al. Nov 2011 A1
20110275443 Cole Nov 2011 A1
20110306400 Nguyen Dec 2011 A1
20110306426 Novak et al. Dec 2011 A1
20120004037 Hill Jan 2012 A1
20120015709 Bennett et al. Jan 2012 A1
20120028703 Anderson et al. Feb 2012 A1
20120028718 Barclay Feb 2012 A1
20120034968 Watkins et al. Feb 2012 A1
20120046110 Amaitis Feb 2012 A1
20120228718 Barclay et al. Feb 2012 A1
20120094769 Nguyen et al. Apr 2012 A1
20120100908 Wells Apr 2012 A1
20120108319 Caputo et al. May 2012 A1
20120122561 Hedrick May 2012 A1
20120122567 Gangadharan et al. May 2012 A1
20120122584 Nguyen May 2012 A1
20120122590 Nguyen May 2012 A1
20120172130 Acres Jul 2012 A1
20120184362 Barclay et al. Jul 2012 A1
20120184363 Barclay et al. Jul 2012 A1
20120185398 Weis Jul 2012 A1
20120190426 Acres Jul 2012 A1
20120194448 Rothkopf Aug 2012 A1
20120208618 Frerking Aug 2012 A1
20120231885 Speer, II Sep 2012 A1
20120239566 Everett Sep 2012 A1
20120322563 Nguyen et al. Dec 2012 A1
20120330740 Pennington et al. Dec 2012 A1
20130005433 Holch Jan 2013 A1
20130005443 Kosta Jan 2013 A1
20130005453 Nguyen et al. Jan 2013 A1
20130059650 Sylla et al. Mar 2013 A1
20130065668 LeMay Mar 2013 A1
20130281188 Guinn Mar 2013 A1
20130103965 Golembeski Apr 2013 A1
20130104193 Gatto et al. Apr 2013 A1
20130130766 Harris et al. May 2013 A1
20130132745 Schoening et al. May 2013 A1
20130165210 Nelson Jun 2013 A1
20130185559 Morel Jul 2013 A1
20130196756 Nguyen Aug 2013 A1
20130196776 Nguyen Aug 2013 A1
20130205919 Bousack Aug 2013 A1
20130210513 Nguyen Aug 2013 A1
20130210514 Nguyen Aug 2013 A1
20130210530 Nguyen Aug 2013 A1
20130225279 Patceg Aug 2013 A1
20130225282 Williams et al. Aug 2013 A1
20130252730 Joshi Sep 2013 A1
20130281187 Skelton Oct 2013 A1
20130316808 Nelson Nov 2013 A1
20130337878 Shepherd Dec 2013 A1
20130337889 Gagner Dec 2013 A1
20140006129 Heath Jan 2014 A1
20140057716 Massing et al. Feb 2014 A1
20140087862 Burke Mar 2014 A1
20140094295 Nguyen Apr 2014 A1
20140094316 Nguyen Apr 2014 A1
20140121005 Nelson May 2014 A1
20140179431 Nguyen Jun 2014 A1
20140274306 Crawford Sep 2014 A1
20140274309 Nguyen Sep 2014 A1
20140274319 Nguyen Sep 2014 A1
20140274320 Nguyen Sep 2014 A1
20140274342 Nguyen Sep 2014 A1
20140274357 Nguyen Sep 2014 A1
20140274360 Nguyen Sep 2014 A1
20140274367 Nguyen Sep 2014 A1
20140274388 Nguyen Sep 2014 A1
20150089595 Telles Mar 2015 A1
20150133223 Carter May 2015 A1
20150143543 Phegade Aug 2015 A1
20160125695 Nguyen May 2016 A1
20160277891 Dvortsov Sep 2016 A1
20170016819 Barwicz Jan 2017 A1
20170116819 Nguyen Apr 2017 A1
20170116823 Nguyen Apr 2017 A1
20170144071 Nguyen May 2017 A1
20170148259 Nguyen May 2017 A1
20170148261 Nguyen May 2017 A1
20170148263 Nguyen May 2017 A1
20170206734 Nguyen Jul 2017 A1
20170228979 Nguyen Aug 2017 A1
20170243440 Nguyen Aug 2017 A1
20170337770 Nguyen Nov 2017 A1
20180144581 Nguyen May 2018 A1
20190005773 Nguyen Jan 2019 A1
20190122490 Nguyen Apr 2019 A1
20190122492 Nguyen Apr 2019 A1
20190213829 Nguyen Jul 2019 A1
20200372753 Nguyen Nov 2020 A1
Non-Patent Literature Citations (99)
Entry
Office Action for U.S. Appl. No. 12/945,888, mailed Jan. 22, 2016.
Final OA for U.S. Appl. No. 12/945,888, mailed Jun. 28, 2016.
Office Action for U.S. Appl. No. 12/945,888, mailed Feb. 28, 2017.
Office Action for U.S. Appl. No. 12/945,888, mailed Sep. 1, 2017.
Notice of Allowance for U.S. Appl. No. 15/402,945, mailed May 25, 2018.
Office Action for U.S. Appl. No. 15/495,973, mailed Jun. 4, 2018.
Notice of Allowance for U.S. Appl. No. 15/427,291 mailed Jun. 18, 2018.
Notice of Allowance for U.S. Appl. No. 15/271,488, mailed Jun. 19, 2018.
Notice of Allowance for U.S. Appl. No. 15/480,295, mailed Jun. 20, 2018.
Office Action for U.S. Appl. No. 14/963,106, mailed Jun. 22, 2018.
Office Action for U.S. Appl. No. 14/993,055, mailed Jun. 22, 2018.
Final Office Action for U.S. Appl. No. 15/427,307, mailed Jul. 9, 2018.
Notice of Allowance for U.S. Appl. No. 13/633,118, mailed Aug. 3, 2018.
Office Action for U.S. Appl. No. 15/671,133, mailed Aug. 9, 2018.
Office Action for U.S. Appl. No. 15/427,308, mailed Aug. 15, 2018.
Office Action for U.S. Appl. No. 15/798,363, mailed Aug. 29, 2018.
Office Action for U.S. Appl. No. 15/428,922 mailed Sep. 17, 2018.
Office Action for U.S. Appl. No. 15/495,975, mailed Sep. 21, 2018.
Notice of Allowance for U.S. Appl. No. 15/271,488, mailed Sep. 24, 2018.
Notice of Allowance for U.S. Appl. No. 15/876,095, mailed Sep. 24, 2018.
Office Action for U.S. Appl. No. 13/622,702, mailed Oct. 3, 2018.
Office Action for U.S. Appl. No. 15/293,751, mailed Apr. 6, 2017.
Notice of Allowance for U.S. Appl. No. 13/801,171, mailed Oct. 31, 2018.
Final Office Action for U.S. Appl. No. 15/835,448, mailed Nov. 2, 2018.
Final Office Action for U.S. Appl. No. 15/480,295, mailed Nov. 7, 2018.
Final Office Action for U.S. Appl. No. 14/963,106, mailed Dec. 14, 2018.
Final Office Action for U.S. Appl. No. 14/993,055, mailed Dec. 14, 2018.
Office Action for U.S. Appl. No. 16/162,358, mailed Dec. 31, 2018.
Office Action for U.S. Appl. No. 14/017,159, mailed Jan. 11, 2019.
Office Action for U.S. Appl. No. 15/426,898, mailed Jan. 11, 2019.
Final Office Action for U.S. Appl. No. 15/495,973, mailed Jan. 11, 2019.
Office Action for U.S. Appl. No. 14/216,986, mailed Jan. 14, 2019.
Office Action for U.S. Appl. No. 15/427,307, mailed Jan. 18, 2019.
Final Office Action for U.S. Appl. No. 15/798,363, mailed Feb. 4, 2019.
Office Action for U.S. Appl. No. 16/125,614, mailed Feb. 25, 2019.
Final Office Action for U.S. Appl. No. 15/495,975, mailed Apr. 18, 2019.
Office Action for U.S. Appl. No. 15/671,133, mailed May 1, 2019.
Notice of Allowance for U.S. Appl. No. 14/216,986, mailed May 17, 2019.
Notice of Allowance for U.S. Appl. No. 14/518,909, mailed May 17, 2019.
Office Action for U.S. Appl. No. 12/797,616, mailed Jun. 5, 2019.
Office Action for U.S. Appl. No. 15/427,308, mailed Jun. 14, 2019.
Office Action for U.S. Appl. No. 15/811,654, mailed Jun. 14, 2019.
Office Action for U.S. Appl. No. 15/674,480, mailed Jun. 20, 2019.
Notice of Allowance for U.S. Appl. No. 15/835,448, mailed Jul. 3, 2019.
Final Office Action for U.S. Appl. No. 16/162,358, mailed Jul. 11, 2019.
Office Action for U.S. Appl. No. 16/190,050, mailed Sep. 19, 2019.
Office Action for U.S. Appl. No. 14/017,150, mailed Oct. 9, 2019.
Final Office Action for U.S. Appl. No. 15/671,133, mailed Oct. 18, 2019.
Office Action for U.S. Appl. No. 15/835,448 mailed Oct. 12, 2019.
Notice of Allowance for U.S. Appl. No. 15/495,975, amiled Oct. 23, 2019.
Notice of Allowance for U.S. Appl. No. 14/993,005, mailed Nov. 27, 2019.
Final Office Action for U.S. Appl. No. 15/427,308, mailed Nov. 27, 2019.
Office Action for U.S. Appl. No. 15/798,363, mailed Jan. 8, 2020.
Office Action for U.S. Appl. No. 15/835,448, mailed Mar. 5, 2020.
Office Action for U.S. Appl. No. 15/495,975, mailed Mar. 17, 2020.
Office Action for U.S. Appl. No. 16/248,759, mailed Apr. 1, 2020.
Final Office Action for U.S. Appl. No. 14/017,150, mailed Apr. 17, 2020.
Notice of Allowance for U.S. Appl. No. 15/798,363, mailed May 12, 2020.
Office Action for U.S. Appl. No. 16/357,316, mailed May 21, 2020.
Office Action for U.S. Appl. No. 16/190,050, mailed Jun. 1, 2020.
Office Action for U.S. Appl. No. 15/674,480, mailed Jun. 5, 2020.
Notice of Allowance for U.S. Appl. No. 15/480,295, mailed Jun. 15, 2020.
Office Action for U.S. Appl. No. 13/622,702, mailed Jun. 22, 2020.
Office Action for U.S. Appl. No. 15/811,654, mailed Jun. 26, 2020.
Office Action for U.S. Appl. No. 16/579,754, mailed Jul. 22, 2020.
Office Action for U.S. Appl. No. 16/219,940, mailed Jul. 22, 2020.
Office Action for U.S. Appl. No. 16/559,553, mailed Sep. 11, 2020.
Office Action for U.S. Appl. No. 16/794,212, mailed Sep. 11, 2020.
Restriction Requirement for U.S. Appl. No. 16/600,395, mailed Sep. 18, 2020.
Final Office Action for U.S. Appl. No. 16/248,759, mailed Oct. 6, 2020.
Final Office Action for U.S. Appl. No. 15/671,133, mailed Oct. 7, 2020.
Final Office Action for U.S. Appl. No. 16/357,316, mailed Oct. 8, 2020.
Final Office Action for U.S. Appl. No. 16/183,632, mailed Oct. 9, 2020.
Office Action for U.S. Appl. No. 16/590,347, mailed Oct. 13, 2020.
Office Action for U.S. Appl. No. 16/449,717, mailed Nov. 9, 2020.
Final Office Action for U.S. Appl. No. 13/622,702, mailed Nov. 30, 2020.
Final Office Action for U.S. Appl. No. 15/674,480, mailed Dec. 7, 2020.
Office Action for U.S. Appl. No. 16/168,813, mailed Dec. 8, 2020.
Office Action for U.S. Appl. No. 16/600,395, mailed Dec. 22, 2020.
“Professional Casino Slot Machine”, Posted at www.vbtutor.net/VB.Sample/vbslot2.htm on Oct. 20, 2009.
Final Office Action for U.S. Appl. No. 16/559,553, mailed Jan. 21, 2021.
Final Office Action for U.S. Appl. No. 16/449,717, mailed Jan. 29, 2021.
Notice of Allowance for U.S. Appl. No. 15/811,654, mailed Feb. 3, 2021.
Notice of Allowance for U.S. Appl. No. 14/017,150, mailed Feb. 5, 2021.
Final Office Action for U.S. Appl. No. 16/794,212, mailed Feb. 17, 2021.
Office Action for U.S. Appl. No. 16/351,416, mailed Feb. 23, 2021.
Office Action for U.S. Appl. No. 16/559,553, mailed Jun. 1, 2021.
Final Office Action for U.S. Appl. No. 16/219,940, dated Mar. 26, 2021.
Office Action (Final Rejection) dated Apr. 15, 2022 for U.S. Appl. No. 16/916,001 (pp. 1-17).
Office Action (Non-Final Rejection) dated May 9, 2022 for U.S. Appl. No. 16/183,632 (pp. 1-29).
Office Action for U.S. Appl. No. 15/674,480, dated Mar. 25, 2021.
Office Action for U.S. Appl. No. 16/183,632, dated May 4, 2021.
Office Action (Final Rejection) dated Jun. 17, 2022 for U.S. Appl. No. 16/219,940 (pp. 1-25).
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Jul. 25, 2022 for U.S. Appl. No. 16/916,001 (pp. 1-9).
Office Action (Final Rejection) dated Jan. 25, 2023 for U.S. Appl. No. 16/183,632 (pp. 1-33).
Office Action (Non-Final Rejection) dated Jan. 31, 2023 for U.S. Appl. No. 16/219,940 (pp. 1-24).
Office Action (Non-Final Rejection) dated Sep. 8, 2023 for U.S. Appl. No. 16/183,632 (pp. 1-30).
Office Action (Final Rejection) dated Oct. 10, 2023 for U.S. Appl. No. 16/219,940 (pp. 1-18).
Office Action (Non-Final Rejection) dated Jan. 31, 2024 for U.S. Appl. No. 16/219,940 (pp. 1-18).
Related Publications (2)
Number Date Country
20140080578 A1 Mar 2014 US
20180053374 A9 Feb 2018 US
Continuation in Parts (1)
Number Date Country
Parent 12945888 Nov 2010 US
Child 13622702 US