Peripheral management device for virtual game interaction

Abstract
In one embodiment, a peripheral management device may have a controller configured to communicate with a gaming machine and a portable electronic device. The controller may be configured to: (i) receive a peripheral data packet from a gaming machine processor, the peripheral data packet including at least one command; (ii) determine whether to process the peripheral data packet on at least one peripheral device of the gaming machine or at least one virtual peripheral device of the portable electronic device; (iii) generate an instructional data packet for the at least one virtual peripheral device if the peripheral data packet is determined to be processed on the at least one virtual peripheral device; and (iv) transmit the instructional data packet to the portable electronic device.
Description
FIELD OF INVENTION

The present disclosure relates generally to gaming machines, and particularly to playing a gaming of chance on a gaming machine. More particularly, the present disclosure relates to using a portable electronic device to play a game of chance on a gaming machine.


BACKGROUND OF THE 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 device may be configured to be updated so as 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 relates to a system for communicating information between a gaming machine and a portable electronic device using a peripheral management device. In one embodiment, a peripheral management device may have a controller configured to communicate with a gaming machine and a portable electronic device. The controller may be configured to: (i) receive a peripheral data packet from a gaming machine processor, the peripheral data packet including at least one command; (ii) determine whether to process the peripheral data packet on at least one peripheral device of the gaming machine or at least one virtual peripheral device of the portable electronic device; (iii) generate an instructional data packet for the at least one virtual peripheral device if the peripheral data packet is determined to be processed on the at least one virtual peripheral device; and (iv) transmit the instructional data packet to the portable electronic device.


In another embodiment, a system for communicating information between a gaming machine and a portable electronic device may have: (i) a gaming machine including at least one gaming machine processor, the at least one gaming machine processor configured to communicate with at least one of a plurality of peripheral devices on the gaming machine; (ii) a portable electronic device including at least one controller, the at least one controller configured to control at least one virtual peripheral device of the portable electronic device; and (iii) a peripheral controller configured to communicate with the gaming machine and the portable electronic device. The peripheral controller may be configured to receive a peripheral data packet from the gaming machine processor, the peripheral data packet including at least one command, determine whether to process the peripheral data packet on the least one peripheral device or the at least one virtual peripheral device, generate an instructional data packet for the at least one virtual peripheral device if the peripheral data packet is determined to be processed on the at least one virtual peripheral device, and transmit the instructional data packet to the portable electronic device.


The above and other features will be presented in more detail in the following detailed description and the associated figures. Other aspects and advantages will become apparent from the following detailed description, taken in conjunction with the accompanying drawings.





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.



FIG. 1 illustrates one embodiment of a gaming system.



FIG. 2 illustrates a perspective view of an example gaming machine.



FIG. 3 illustrates an example block diagram of a gaming machine.



FIG. 4 illustrates an exemplary block diagram of a peripheral management device.



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



FIG. 6 illustrates an example flow diagram of a method for communicating information and/or data between a gaming machine and a portable electronic device.



FIGS. 7A-7J illustrate example graphical user interfaces of a portable electronic device used to communicate with a gaming machine.



FIG. 8 illustrates a flow diagram of a method for authenticating a user in accordance with one embodiment.



FIG. 9 illustrates an exemplary flow diagram of a method for communicating at least one user request to a gaming machine using a peripheral management device.



FIG. 10 illustrates an exemplary flow diagram of a method to transfer funds to a gaming machine from a portable electronic device.



FIGS. 11A-11D illustrate example graphical user interfaces of a portable electronic device.



FIG. 12 illustrates an exemplary flow diagram of a method to generate a receipt using a portable electronic device.



FIGS. 13A-13D illustrate example graphical user interfaces to generate a receipt using a portable electronic device.





DESCRIPTION

Embodiments are described herein in the context of a peripheral management device for virtual game interaction. 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.


A system, method, and apparatus for communicating information between a gaming machine and a portable electronic device using a peripheral management device are described. In one embodiment, a gaming machine is able to be augmented by a remote peripheral device. The remote peripheral device can wirelessly communicate with the gaming machine. For example, a portable computing device, such as a mobile phone, tablet computer, personal digital assistant, and the like, can function as an external peripheral device for the gaming machine. As a result, the gaming environment for a game of chance played on the gaming machine can be extended (at least in part) to a player's portable computing device. Such a gaming environment allows the portable computing device to serve as one or more of a display, input device, storage device, and the like.


In another embodiment, a peripheral management device may be used as an intermediary device between the gaming machine and the remote peripheral device to allow a player to play a game of chance on the gaming machine. The peripheral management device may receive peripheral bound data and be configured to determine where to transmit the peripheral bound data. In other words, the peripheral management device may be configured to determine whether to transmit the peripheral bound data to a remote virtual peripheral device on the portable electronic device or to local peripheral devices on the gaming machine.


In use, many players desire to play on multiple machines. However, the gaming machines must be neighboring machines such as a machine to the right and/or left of the player since the player must be near in order to press the input buttons and/or switches, insert money, and perform any other gaming function. By using a remote peripheral device, such as a portable electronic device, to play a gaming of chance on a gaming machine, the player may have the freedom to play other gaming machines and not just gaming machines neighboring the gaming machine the player desires to play. For example, the player may want to play a game of chance on gaming machine A as well as gaming machine B. However, gaming machine B may be four gaming machines away from gaming machine A. Thus, by using the remote peripheral device to play the gaming of chance on gaming machine A, the player can also play the gaming of chance on gaming machine B. This provides a player the freedom to play a game of chance on any gaming machine without having any physical limitations.



FIG. 1 illustrates one embodiment of a gaming system. System 100 includes at least one gaming machine 108 having a peripheral management device 110. Gaming machine 108 may be configured to communicate with a plurality of servers such as a player tracking server 102, authentication server 116, and a location server 104 via network 106. Although illustrated with three servers, this is not intended to be limiting as gaming machine 108 may be configured to communicate with any number of servers via network 106 such as an awards server, accounting server, financial server, games server, and the like. The gaming machine 108 may be connected to network 106 via any wired or wireless methods 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.11 technology, Near-Field Magnetic Network, radio frequency, and the like.


Gaming machine 108 may be configured to also communicate with peripheral management device 110 via any wired or wireless methods. Peripheral management device 110 may have a wireless interface 120 configured to communicate with a portable computing device or a portable electronic device 114. Peripheral management device 110 may be used as an intermediary device between the gaming machine 108 and the portable electronic device 114 to allow a player to play a game of chance on the gaming machine 108. The peripheral management device 110 may receive peripheral bound data (from the portable electronic device 114 and/or the gaming machine 108) and determine where to transmit the peripheral bound data. In other words, the peripheral management device 110 may be configured to determine whether to transmit the peripheral bound data to a remote virtual peripheral device on the portable electronic device 114 or to local peripheral devices on the gaming machine 108.


The peripheral management device 110 allows the gaming machine 108 to be augmented by a remote peripheral device, such as the portable electronic device 114. The remote peripheral device 114 can wirelessly communicate with the gaming machine 108. For example, a portable computing device 114, such as a mobile phone, can function as an external peripheral device for the gaming machine 108. As a result, the gaming environment for a game of chance played on the gaming machine 108 can be extended (at least in part) to a player's portable computing device 114. Such a gaming environment allows the portable computing device 114 to serve as one or more of a display, input device, storage device, and the like.


Portable electronic device 114 may be configured to communicate with gaming machine 108 via peripheral management device 110 to play a game of chance on the gaming machine. In one embodiment, portable electronic device 114 may communicate with peripheral management device 100 via wireless interface 120. Wireless interface 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.11 technology, radio frequency, and the like.


In use, the portable electronic device 114 may receive a user input request. The request may be any type of request, such as a request to transfer funds, print a receipt or ticket, dim the display, lower the volume on the speaker, spin a reel, cash out, double down, and the like. The portable electronic device 114 may transmit the user request to the peripheral management device 110 via wireless interface 120. Peripheral management device 110 may process the request (e.g. parse the user request) to determine what local peripheral device on the gaming machine 108 the user would like to access. Each remote virtual peripheral device on the portable electronic device 114 may be associated with a peripheral device on the gaming machine 108. Thus, for example, if the user request includes a request to dim a virtual display, the peripheral management device may determine that the virtual display is associated with the display (e.g. display 208 as illustrated in FIG. 2) on the gaming machine 108. As such, the user request may be processed to request access to the display on the gaming machine 108. In another example, the peripheral management device may parse the user request to determine that the user would like to lower the volume on the virtual speakers. The peripheral management device 110 may determine that the virtual speakers are associated with the speaker (e.g. speaker 214 illustrated in FIG. 2) on the gaming machine 108. Thus, the user request may be processed to request access to the speaker on the gaming machine 108.


The peripheral management device 110 may also modify, change, or edit the source and destination address of the user request. For example, the source address may be changed to the peripheral device associated with the virtual peripheral device and the destination address may be the gaming machine processor. Thus, the peripheral management device 110 may route the user request to a source destination as a local peripheral device. This permits for the seamless transfer of information or data to the gaming machine processor from the portable electronic device 114. In other words, peripheral management device acts as a context-sensitive smart router of data from a source device to a destination device, and is invisible to the gaming machine processor.


The processed funds transfer request may then be transmitted to the gaming machine 108. The gaming machine 108 may determine whether to transmit a command and/or an acknowledgement. For example, the gaming machine processor may determine that the user transferred a fund amount to play a game of chance on the gaming machine 108 which was received by the bill acceptor. The gaming machine 108 may then transmit commands and/or acknowledgements to at least one peripheral device of the gaming machine 108 to allow the user to play the game of chance. For example, the gaming machine 108 may transmit a command to the display to present the fund amount on the display. In another example, the gaming machine 108 may transmit an acknowledgment to the bill acceptor to display an acknowledgement message or fund amount on a display of the bill acceptor. In another embodiment, the gaming machine 108 may instruct the user input buttons or switches to activate and light up to indicate that the player may begin to play the game of chance.


The peripheral management device 110 may intercept the commands and/or acknowledgments from the gaming machine 108. The peripheral management device 110 may then process the intercepted commands and/or acknowledgements by parsing the commands and/or acknowledgement to determine where the commands and/or acknowledgments should be transmitted to. In other words, the peripheral management device 110 may process the intercepted commands and/or acknowledgements to determine which remote virtual peripheral device on the portable electronic device 114 the commands and/or acknowledgements should be transmitted to and to determine which local peripheral device on the gaming machine 108 the commands and/or acknowledgements should be transmitted to.


If the peripheral management device 110 determines that the commands and/or acknowledgements should be transmitted to the portable electronic device 114, then the commands and/or acknowledgements may be transmitted to the portable electronic device 114. For example, if the transmission is an acknowledgement acknowledging the transfer of funds, the peripheral management device 110 may determine that the acknowledgement may be transmitted to the portable electronic device 114 to inform the user of the successful transfer of funds. The acknowledgement may then be displayed on a display of the portable electronic device (e.g. display 1108 as illustrated in FIGS. 11A-11D).


If the peripheral management device 110 determines that the commands and/or acknowledgements should not be transmitted to the portable electronic device 114, the peripheral management device 110 may determine and identify whether the commands and/or acknowledgements may be transmitted to the at least one peripheral device on the gaming machine 108. For example, if the transmission is an acknowledgement acknowledging the transfer of funds, the peripheral management device 110 may determine that the acknowledgement may be transmitted to the user input buttons and/or switches. The user input buttons and/or switches of the gaming machine 108 may then light up to indicate to the player that he may play the game of chance. In another example, the peripheral management device 110 may determine that the acknowledgement may be transmitted to the display of the gaming machine 108 to indicate or display the amount of credits. Thus, if the peripheral management device 110 determines and identifies that the commands and/or acknowledgements should be transmitted to at least one peripheral device on the gaming machine 108, the commands and/or acknowledgements may be transmitted to the identified at least one peripheral device on the gaming machine 108.


In one embodiment, player tracking server 102 may be configured to collect player data as well as determine the location of a customer within a gaming environment. Player tracking sever 102 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 102 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 104, may be used to locate the location of the player in the gaming environment. Location server 104 may include a database containing the location of all gaming devices (stationary and mobile gaming devices) in the gaming environment. Furthermore, location server 104 may be configured to locate players within the gaming environment using any known wireless location methods such as global positioning systems (GPS), indoor WiFi triangulations, and the like. In one embodiment, location server 104 may be configured to locate the position of the player using the player's portable electronic device 114 and the location of the nearest gaming machine 108. In another embodiment, the location server 104 may be configured to locate the player in the gaming environment using only the player's portable electronic device 114.


The authentication sever 116 may be configured to authenticate or verify the player, gaming machine, and/or a portable electronic device via any known authentication means such as passwords and identification, biometric signatures, encryption keys, and the like. For example, to authenticate the player, the authentication server 116 may be configured to receive a username and password inputted via a player tracking keyboard (illustrated in FIG. 2B) on the gaming machine 108. The authentication server 116 may then compare the received username and password to a saved username and password stored in the authentication server 118. If the received and saved username and password are the same, then the player is authenticated.



FIG. 2 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 the 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 monitor 208, a secondary display 212, 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 bill acceptor 228. The gaming machine 200 may be configured to display a game of chance on monitor 208 and/or 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.


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, monitor 208 may be a touch screen display such that the user may input selections via display 208. Monitor 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 video display monitor 208 may include one or more display windows to allow for multiple games or multiple services to be provided simultaneously to a user.


The top box 210 may be designed to house a plurality of peripheral devices, including but not limited to the secondary display 212 and 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 video display monitor 208 and the secondary display 212. The plurality of auditory and visual effects may serve to enhance the user's 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 door 204 may include the ticket printer 216 configured to print an electronically-readable ticket 224, keypad 218 for entering player tracking information, the player tracking device 220, the coin tray 222, the coin acceptor 226, and the bill acceptor 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 bill acceptor 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 bill acceptor 228 may be configured to accept cash of a variety of currency or denomination as well as an electronically-readable ticket 224 having a cash value.


The secondary display 210, 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 210. 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), dynamic random access memory (DRAM)) on the gaming machine, 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. 3 illustrates an example block diagram of a gaming machine. The gaming machine 300 may have a gaming machine processor 302 configured to communicate with a peripheral management device 304 via any wired or wireless method and/or device. Peripheral management device 304 may be configured to communicate with portable electronic device 308 and each of the plurality of peripheral devices 306. Peripheral management device 304 may be configured to communicate with portable electronic device 308 via wireless interface 310 as discussed above. The plurality of peripheral devices 306 may be any peripheral device as discussed above with reference to FIG. 2. For example, the at least one button or switch 206, monitor 208, secondary display 212, speaker 214, ticket printer 216, keypad 218 for entering player tracking information, a player tracking device 220, a coin acceptor 226, and bill acceptor 228 may be peripheral device 306. Although illustrated with specific peripheral devices, this is not intended to be limiting as any other peripheral devices may be used on a gaming machine, such as an informational display, camera, microphone, accelerometer, touchscreen, and the like.



FIG. 4 illustrates an exemplary block diagram of a peripheral management device. Peripheral management device 400 may include a peripheral controller 402 configured to communicate with memory 404 and a wireless module 408. Wireless interface 408 may be configured to transmit and receive instructional data packets or peripheral bound data. Wireless interface 408 may be any module capable of wireless transmission such as 3G wireless technology, 4G wireless technology, Bluetooth, wireless universal serial bus (USB), wireless Ultra-wideband (UWB), WiMAX, near field communication, radio frequency, and the like. In one embodiment, wireless communication module 408 may be configured to transmit and receive peripheral bound data and/or information to and from a portable electronic device as well as a gaming machine processor.


Peripheral management device may be used as an intermediary device between the gaming machine and the remote peripheral device to allow a player to play a game of chance on the gaming machine. The peripheral management device may receive peripheral bound data (from the portable electronic device and/or the gaming machine processor) and determine where to transmit the peripheral bound data. In other words, the peripheral management device may be configured to determine whether to transmit the peripheral bound data to a remote virtual peripheral device on the portable electronic device or to local peripheral devices on the gaming machine.


The peripheral management device allows the gaming machine to be augmented by a remote peripheral device, such as the portable electronic device. The remote peripheral device can wirelessly communicate with the gaming machine. For example, a portable computing device, such as a mobile phone, can function as an external peripheral device for the gaming machine. As a result, the gaming environment for a game of chance played on the gaming machine can be extended (at least in part) to a player's portable computing device. Such a gaming environment allows the portable computing device to serve as one or more of a display, input device, storage device, and the like.


Memory 404 may be type of memory capable of storing data. Memory 408 may be any type of memory such as DRAM, NVRAM, and the like. Memory may have a peripheral database 410 configured to store peripheral device information. In one embodiment, the peripheral database 410 may store a table associating the remote virtual peripheral device on the portable electronic device to the local peripheral devices on the gaming machine. For example, the peripheral database 410 may associate the virtual “Cash Out” button of the portable electronic device to the “Cash Out” button on the gaming machine. In another embodiment, the peripheral database 410 may associate the virtual “Deal” button of the portable electronic device to the “Deal” button on the gaming machine.


In another embodiment, the peripheral database 410 may store a table associating a request or command from the portable electronic device to a local peripheral device on the gaming machine. For example, a request to transfer money from the portable electronic device may be associated with the bill acceptor of the gaming machine. In another example, a request to end a game session from the portable electronic device may be associated with a “Cash Out” button on the gaming machine.



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, personal digital assistant (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, microphone 510 configured to receive audio input, and 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, for example, FIGS. 7, 11, and 13). 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, processor may be configured to detect a user selection of at least one of the indicators from switches 506.


Each indicator may correspond to a virtual peripheral device, which may be associated with a peripheral device on the gaming machine. For example, user selection of the “Cash Out” indicator may be associated with a virtual cash out button on the portable electronic device, which may be associated with the “Cash Out” button on the gaming machine. In another embodiment a “Spin Reel” indicator may be associated with a virtual spin button on the portable electronic device, which may be associated with the “Spin” button on the gaming machine.


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, Ferroelectric Random Access Memory (FRAM), Electrically Erasable Programmable Read-Only Memory (E2PROM), and the like.


Wireless communication module 514 may be configured to transmit and receive instructional data packets or peripheral bound data. 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 and receive peripheral bound data and/or information to and from peripheral management device (e.g. peripheral management device 110 illustrated in FIG. 1).



FIG. 6 illustrates an example flow diagram of a method for communicating information and/or data between a gaming machine and a portable electronic device. The method 600 begins with the peripheral management device receiving a peripheral data packet from a gaming machine processor at 602. The peripheral data packet may include at least one command and/or acknowledgement. In one embodiment, the peripheral data packet may include at least one command and/or acknowledgement for at least one peripheral device of the gaming machine. For example, the peripheral data packet may include a command for the display (e.g. display 208, 212 as illustrated in FIG. 2) to display a credit amount which can allow the user to play a game of chance on the gaming machine. In another embodiment, the peripheral data packet may include a command for the user input buttons and/or switches (e.g. input buttons and/or switches 206 as illustrated in FIG. 2) to light up. In still another embodiment, the peripheral data packet may also include other data such as a source address, destination address, and user identification data such as a portable electronic device identifier, user password, user PIN, and the like. The portable electronic device identifier may be any set of words or numbers that are unique to the portable electronic device.


The peripheral management device may determine whether to transmit the peripheral data packet to at least one peripheral device of the gaming machine at 604. The peripheral management device may parse the peripheral data packet to determine or identify which peripheral device(s) the peripheral data packet should be transmitted to. In one embodiment, the peripheral management device may identify which peripheral device the peripheral data packet should be transmitted to by the destination address. In another embodiment, the peripheral management device may identify which peripheral device the peripheral data packet should be transmitted to by the command. For example, the command may be to indicate the amount of credits. Thus, the peripheral management device may determine that the amount of credits is to be displayed on the display of the gaming machine.


If the peripheral management device determines that the peripheral data packet should be transmitted to the peripheral device at 604, an instructional data packet may be generated for the at least one peripheral device of the gaming machine at 616. The instructional data packet may include the at least one command and/or acknowledgement from the gaming machine. In one embodiment, the instructional data packet may also include other data such as a source address, destination address, and any other identifying information such as a gaming machine identifier to identify the gaming machine.


The instructional data packet may be transmitted to the at least one peripheral device at 618. The peripheral management device may transmit the instructional data packet to the identified at least one peripheral devices. The peripheral management device may determine which of the at least one peripheral devices to transmit the instructional data packet to via the destination address, command, or any other identifying criteria in the peripheral data packet.


The peripheral management device may then determine whether to transmit the instructional data packet to at least one virtual peripheral device on a portable electronic device at 620. For example, if the peripheral data packet included an acknowledgement for the receipt of funds received by the player, the peripheral management device may determine that the acknowledgement should be transmitted to the virtual display of the portable electronic device to inform the player that the transfer of funds (as discussed with reference to FIGS. 10 and 11A-11D) was successful. In another example, if the peripheral management device determines that the peripheral data packet included a command for the user input buttons and/or switches to light up, the peripheral management device may determine not to transmit the instructional data packet to the portable electronic device at 620. In still another example, if the peripheral management device determines that the peripheral data packet included a command for the user input buttons and/or switches to light up, the peripheral management device may determine to still transmit the instructional data packet to the virtual user buttons or switches on the portable electronic device at 620.


If the peripheral management device determines not to transmit the peripheral data packet to at least one peripheral device of the gaming machine at 604, an instructional data packet may be generated for at least one virtual peripheral device on the portable electronic device at 608. The instructional data packet may include the at least one command and/or acknowledgement from the gaming machine. In one embodiment, the instructional data packet may also include other data such as a source address (e.g. gaming machine, peripheral management device, and the like), destination address (e.g. portable electronic device), and user identification data such as a portable electronic device identifier, user password, user PIN, and the like. The portable electronic device identifier may be any set of words or numbers that are unique to the portable electronic device.


The instructional data packet may be encrypted at 610. The instructional data packet may be generated at 608 and/or 616. The instructional data packet 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 portable electronic device may then be authenticated at 612 to ensure that the instructional data packet is transmitted to the proper portable electronic device. Any known authentication methods may be used such as authentication algorithms, random number generators, authentication keys, and the like. In one embodiment, the peripheral management device may request user information (e.g. portable electronic device identifier, password, PIN, and the like) from the portable electronic device. The peripheral management device may then authenticate the portable electronic device by comparing or matching the requested user information with user information in the peripheral data packet. The portable electronic device may be authenticated if the requested user information matches the user information in the peripheral data packet. Once authenticated, the encrypted instructional data packet may be transmitted to the authenticated portable electronic device at 614 via any known wired or wireless methods or devices such as a universal serial bus, Ethernet, SATA, Fire Wire, 3G wireless technology, 4G wireless technology, Bluetooth, wireless USB, wireless UWB, WiMAX, near field communication, radio frequency, and the like.



FIGS. 7A-7J illustrate example graphical user interfaces of a portable electronic device used to communicate with a gaming machine. FIG. 7A illustrates one embodiment of the graphical user interface of the portable electronic device 700. The portable electronic device 700 may be configured to display at least one indicator 750 on a display 701 of the portable electronic device 700. The indicators 705 may be any type of indicator configured to receive a user input command. Additionally, the display may be any type of known 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, if the user would like to look at a calendar, the user may press the “Calendar” indicator 752. The portable electronic device 700 may detect the user selection of the “Calendar” indicator 752 and display a calendar on the display 701. In another example, the user may want to access the Internet. Thus, the user may press the “Web” indicator 754. The portable electronic device 700 may detect the user selection of the “Web” indicator 754 and display a search engine on the display 701. In still another example, the player may want to play a game of chance on a gaming machine. Thus, the user may press the “Connect To Gaming Machine” indicator 766. The portable electronic device 700 may detect the user selection of the “Connect To Gaming Machine” indicator 766 and display a game menu as illustrated in FIG. 7J.



FIG. 7B illustrates another embodiment of the graphical user interface of the portable electronic device 700. If display 701 is not a touch screen display, at least one user input buttons or switches 705 may be used to navigate the graphical user interface. For example, a user may select or navigate the at least one of the indicators by using the at least one user input buttons or switches 705 to move a cursor (or any other similar type of indicator) right, left, up, or down on the display. However, the use of the illustrated user input buttons or switches 705 is for exemplary purposes and not intended to be limiting as any type of device to navigate a graphical user interface may be used such as a keyboard, joystick, and the like.



FIG. 7C illustrates one example of the graphical user interface presenting a welcome screen. The welcome screen 707 may display any type of welcome message (e.g. using text, images, designs, audio, and the like) to the user. This provides for a friendly and welcoming gaming environment for the players. The display 701 may also present a “Returning User” 708 indicator and a “New User” indicator 710. Thus, if the user has an existing player tracking account with the casino, then the “Returning User” indicator 708 may be selected. If the user does not have an existing account with the casino then the “New User” indicator 710 may be selected. If the “Returning User” indicator 708 is selected, then the graphical user interface may be updated to present a returning user login screen as illustrated in FIG. 7D. Alternatively, if the “New User” indicator 710 is selected, then the graphical user interface may be updated to present an account set up screen as illustrated in FIG. 7G.


Referring now to FIG. 7D, if the user is a returning user that has an existing player tracking account with the casino and the portable electronic device 700 detected that the “Returning User” indicator 708 was selected, the graphical user interface may be updated to present a login screen on the display 701. In one embodiment, the login screen may be configured to display one or more user-enterable fields. By way of example, the one or more user-enterable fields may include a user ID box 714 and a password box 716. A keyboard 718 may also be presented on the display 701. The keyboard 718 may be configured to assist the user with inputting a unique username in the user ID box 714 and a password in the password box 716. As illustrated, the unique username 715 illustrated in FIG. 7D is “Will_Gamble” 715. Additionally, although the password 717 is illustrated as not displayed, this is not intended to be limiting as the password may be displayed to the user.


After the user ID box 714 and the password box 716 have both received a username 715 and password 717, respectively, the user may select to confirm or enter the username 715 and password 717 by pressing the “Enter” indicator 720 or cancel the entered username 715 and password 717 by pressing the “Cancel” indicator 722. By pressing the “Cancel” indicator 722, the portable electronic device 700 may remove the contents of the user-enterable fields. In other words, pressing the “Cancel” indicator 722 may result in the removal of the username 715 in the user ID box 714 and password 717 in the password box 716.


By pressing the “Enter” indicator 720, the user's password and ID may be transmitted from the portable electronic device 700 to the peripheral management device (e.g. peripheral management device 110 (FIG. 1), 304 (FIG. 3), 400 (FIG. 4)) for processing. Once transmitted to the peripheral management device, the display 701 may indicate to the user that the user identification and password is being authenticated as illustrated in FIG. 7E. For example, the portable electronic device 700 may display an “Authenticating Your User ID and Password” message 738 on the display 701.


Referring to FIG. 7F, if the user's password and ID are authenticated (as described in detail with reference to FIG. 8), the portable electronic device may display a successful message on the display 701. As illustrated, a message 742 such as “Welcome Will_Gamble! Your User ID and Password Have Been Verified”742 may be displayed on display 701.


If the user does not have an existing account at the gaming establishment, the user may be prompted to set up an account. FIG. 7G illustrates one example of the graphical user interface of an account setup screen 724. The account setup screen may be configured to display one or more user-enterable fields 726, 728. By way of example, the account setup screen 724 may have a user ID box 726 and a password box 728 for the user to input personal information to set up a player tracking account. The graphical user interface may also present an alphabetical/numerical keyboard 730 configured to assist a user to input a unique ID or username in the user ID box 726 and a password in the password box 728. As illustrated, the unique username 727 is “Will_Gamble” 715.


After the user ID box 726 and the password box 728 have both received an ID or username 727 and password 729, respectively, the user may select to confirm or enter the username 727 and password 729 by pressing the “Enter” indicator 732 or cancel the entered username 727 and password 729 by pressing the “Cancel” indicator 734. By pressing the “Cancel” indicator 734, the portable electronic device 700 may remove the contents of the user-enterable fields. In other words, pressing the “Cancel” indicator 734 may result in the removal of the username 727 in the user ID box 726 and password 729 in the password box 728.


By pressing the “Enter” indicator 732, the user's password 729 and ID or username 727 may be transmitted from the portable electronic device 700 to the peripheral management device (e.g. peripheral management device 110 (FIG. 1), 304 (FIG. 3), 400 (FIG. 4)) for processing. Once a player tracking account has been created for the user, the portable electronic device 700 may present a successful message to the user as illustrated in FIG. 7H. The portable electronic device 700 may present a message, for example, “Welcome Will_Gamble! Your Account Has Been Created!” 782. Although not illustrated, it will now be known that any other personal user information may be requested to create a player tracking account such as address, phone number, electronic mail address, emergency contact information, driver's license number, and the like.



FIG. 7I illustrates an example graphical user interface displaying a casino menu. The casino menu may be presented on the display 701 after successful authentication of the user and/or successful creation of a player tracking account. The display 701 may present a plurality of indicators 784. In one embodiment, each indicator may represent a service provided by the gaming establishment (e.g. a casino), such as reserving a room 764, playing in a tournament 770, restaurant reservations 768, and the like. In another embodiment, at least one indicator may connect the portable electronic device to a gaming machine 766 if the player would like to play a game of chance. In still another embodiment, the user may access his player tracking account by pressing the “Account” indicator 774. Although illustrated with specific indicators, this is for exemplary purposes only as other gaming establishment functions may be presented.



FIG. 7J illustrates an example graphical user interface displaying a gaming menu. If the user selects the “Connect To Gaming Machine” indicator 766 illustrated in FIG. 7I, the portable electronic device 700 may display a gaming menu 756. The gaming menu may have a plurality of gaming function indicators. As illustrated, the gaming function indicators may represent virtual user input buttons for a video blackjack game of chance. For example, the indicators may be “Stand” 790, “Hit” 792, “Double Down” 794, “Deal” 796, and the like. Each virtual user input button may be associated with or correspond to a peripheral device on the gaming machine. For example, the “Stand” indicator 790 may correspond to a virtual stand button on the portable electronic device 700, which in turn corresponds to the stand button on the gaming machine (not shown). Thus, if the user would like to stand on a dealt hand, the user may depress the “Stand” indicator 790 on the portable electronic device 700.


The indicators may also relate to other gaming functions. For example, a user may decrease or increase the volume on a gaming machine by pressing the “Speaker” indicator 758. In another embodiment, the user may adjust the brightness of the display by pressing the “Display” indicator 760. If the user would like to increase his bet, he may press the “Increase Bet” indicator 764. Although illustrated with specific indicators, this is for exemplary purposes only as other game play functions may be presented such as spinning a reel, decrease bet, and the like.



FIG. 8 illustrates a flow diagram of a method for authenticating a user in accordance with one embodiment. The method 800 begins with the peripheral management device receiving a user request to access a gaming machine from a portable electronic device at 802. In one embodiment, the user request may include a username, password, and request to play a game of chance on the gaming machine. The gaming machine may be identified by any known methods such as infrared, 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, which may then be transmitted with the user request. In another embodiment, the user may scan a bar code on the gaming machine into the portable electronic device, which may be transmitted with the user request.


The peripheral management device may process the user request at 803. To process the user request, in one embodiment, the peripheral management device may parse the information in the user request such as the username, password, gaming machine identifier, and access request to determine that the user request needs to be authenticated. The peripheral management device may also change the source and destination address of the user request. For example, the source address may be changed to the peripheral device associated with the virtual peripheral device and the destination address may be the gaming machine processor. In other words, the peripheral management device may associate the user request with the virtual player tracking device, which may correspond to or be associated with the player tracking device on the gaming machine.


The peripheral management device may then transmit an authentication request to the gaming machine processor at 804. The authentication request may include a request to authenticate the player and include the username and password received from the portable electronic device. Additionally, since the source address may be changed, the gaming machine processor may believe that the request was transmitted from a peripheral device on the gaming machine and not from the peripheral management device or portable electronic device. Continuing with the example above, the gaming machine may believe that the authentication request resulted from player input at the player tracking device—i.e. that the player input the username and password using a keypad (e.g. keypad 218 as illustrated in FIG. 2) on the player tracking device. Thus, the gaming machine would not suspect that the user requested was transmitted from the portable electronic device.


The gaming machine processor may then transmit the username and password to the authentication server (e.g. authentication server 116 illustrated in FIG. 1) at 808. However, 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 102 illustrated in FIG. 1).


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 at 808. If there is no match at 810, the authentication server may transmit an error message to the gaming machine processor at 814. If there is a match at 810, the authentication server may transmit a successful message to the gaming machine processor at 812. 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, the gaming machine processor may transmit the successful message to a display on the gaming machine (e.g. display 208, 212 illustrated in FIG. 2) at 816. In another embodiment, the gaming machine processor may transmit the successful message to a display on the player tracking device (e.g. player tracking device 220 as illustrated in FIG. 2). Thus, the display used to inform the user that the authentication was successful is not intended to be limiting as any known means to transmit the information to the player may be used. The peripheral management device may intercept the successful message at 818 and transmit the successful message to the portable electronic device at 820. The successful message may be similar to the example graphical user interface illustrated in FIG. 7F.



FIG. 9 illustrates an exemplary flow diagram of a method for communicating at least one user request to a gaming machine using a peripheral management device. The method 900 may begin by receiving, at or by the portable electronic device, a user request to access at least one virtual peripheral device at 902. The portable electronic device may generate the user request based upon user selection of an indicator. The indicators may be similar to, for example, the indicators illustrated in FIG. 7J. For example, the indicators may be a request to spin a reel, bet the minimum bet, decrease the volume in the speaker, dim the display, and the like.


The user request may then be transmitted from the portable electronic device to a peripheral management device at 904. The user request may be transmitted by any know wired or wireless means such as universal serial bus, Ethernet, SATA, Fire Wire, 3G wires technology, 4G wireless technology, Fire Wire, Bluetooth, wireless USB, wireless UWB, WiMAX, near field communication, radio frequency, and the like. The peripheral management device may process the user request at 906. In other words, the peripheral management device may parse the user request to determine what peripheral device on the gaming machine the user would like to access. Each virtual peripheral device on the portable electronic device may be associated with a peripheral device on the gaming machine. Thus, for example, if the user request includes a request to dim a virtual display, the peripheral management device may determine that the virtual display is associated with the display (e.g. display 208 as illustrated in FIG. 2) on the gaming machine. As such, the user request may be processed to request access to the display on the gaming machine. In another example, the peripheral management device may parse the user request to determine that the user would like to lower the volume on the virtual speakers. The peripheral management device may determine that the virtual speakers are associated with the speaker (e.g. speaker 214 illustrated in FIG. 2) on the gaming machine. Thus, the user request may be processed to request access to the speaker on the gaming machine. In still another example, the peripheral management device may parse the user request to determine that the user would like stop playing the game of chance and selected the “Cash Out” indicator (e.g. “Cash Out” indicator 788). Thus, the peripheral management device may associate the virtual “Cash Out” indicator with the cash out button (e.g. button 206 illustrated in FIG. 2) of the gaming machine and the user request may be processed to indicate the user would like to redeem the remaining credits on the gaming machine.


The peripheral management device may also modify, change, or edit the source and destination address of the user request. For example, the source address may be changed to the peripheral device associated with the virtual peripheral device and the destination address may be the gaming machine processor. In other words, the peripheral management device may associate the user request with the virtual cash out button (i.e. “Cash Out” indicator 788 as illustrated in FIG. 7I), which may correspond to or be associated with the cash out button (e.g. buttons 206 as illustrated in FIG. 2) on the gaming machine.


Once the user request is processed at 906, the peripheral management device may transmit the processed user request to the gaming machine processor at 908. The gaming machine processor may process the user request at 910 to generate a command and/or acknowledgement. For example, if the user request included a request to dim the display, the gaming machine processor may process the processed user request to include a dim command to be transmitted to the display. In another example, if the user request included a request to lower the volume, the gaming machine processor may transmit the user request to include volume command to be transmitted to the speakers on the gaming machine. In still another example, if the user request included a request to cash out, the gaming machine processor may transmit a print ticket command to be transmitted to the printer.


The command and/or acknowledgment may be transmitted to the corresponding peripheral device via the peripheral management device at 912. For example, the print ticket command may be transmitted from the gaming machine processor to the printer on the gaming machine. In another example, the volume command may be transmitted from the gaming machine processor to the speaker on the gaming machine.


Example 1

The following examples are intended to be for exemplary purposes only and not intended to be limiting as many other possibilities and uses are possible and contemplated.



FIG. 10 illustrates an exemplary flow diagram of a method to transfer funds to a gaming machine from a portable electronic device. The method 1000 may begin by the portable electronic device receiving at least one funds transfer request to transfer funds at 1002. The at least one funds transfer request may be requested by a user to permit the user to play a game of chance on a gaming machine. In one embodiment, the at least one funds transfer request may be physically initiated by the user pressing a “Funds Transfer” indicator (e.g. “Funds Transfer” indicator 780 illustrated in FIG. 7J) presented on a display of the portable electronic device. In another embodiment, the at least one funds transfer request 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 “money transfer”, “funds transfer”, “cash in”, and the like.


The funds transfer request may be transmitted from the portable electronic device to the peripheral controller (e.g. peripheral controller 402 illustrated in FIG. 4) at 1004. In one embodiment, the funds transfer request may be encrypted by the portable electronic device prior to being transferred. Any known encryption methods may be used such as AES, MAC, HMAC, SHA-2 and the like. The funds transfer request may include any necessary information or data to facilitate the 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.


The peripheral controller may process the at least one funds transfer request at 1006. The peripheral controller may process the at least one funds transfer request by parsing the information in the funds transfer request to determine which peripheral device, on the gaming machine, the user would like to access. Each virtual peripheral device on the portable electronic device may be associated with a peripheral device on the gaming machine. Thus, the peripheral controller may determine that the user would like to transfer a specific amount of funds to the gaming machine via the virtual bill acceptor, which may be associated with the bill acceptor on the gaming machine. The user request may then be processed as a request for the bill acceptor on the gaming machine. Additionally, processing the at least one funds transfer request may include modifying the funds transfer request to reflect the proper source address and destination address. For example, the funds transfer request may be modified to reflect the source address as the bill acceptor and the destination address as the gaming machine processor. This permits for the seamless transfer of information or data to the gaming machine processor from the portable electronic device. In other words, peripheral management device is invisible to the gaming machine processor.


The processed funds transfer request may then be transmitted to the gaming machine processor (e.g. gaming machine processor 302 as illustrated in FIG. 3) at 1008 for the gaming machine processor to process at 1010. For example, the gaming machine processor may determine that the user transferred the fund amount to play a game of chance which was received by the bill acceptor. The gaming machine processor may then transmit commands and/or acknowledgements to at least one peripheral device of the gaming machine at 1012 to allow the user to play the game of chance. For example, the gaming machine may transmit a command to the display to present the fund amount on the display. In another example, the gaming machine may transmit an acknowledgment to the bill acceptor to display an acknowledgement message or fund amount on a display of the bill acceptor. In another embodiment, the gaming machine may instruct the user input buttons or switches to activate and light up to indicate that the player may begin to play the game of chance.


The peripheral controller may intercept the commands and/or acknowledgments at 1014 and process the intercepted commands and/or acknowledgments at 1016. The peripheral controller may process the intercepted commands and/or acknowledgements by parsing the commands and/or acknowledgement to determine where the commands and/or acknowledgments should be transmitted to. In other words, the peripheral controller may process the intercepted commands and/or acknowledgements to determine which virtual peripheral device on the portable electronic device the commands and/or acknowledgements should be transmitted to and to determine which peripheral device on the gaming machine the commands and/or acknowledgements should be transmitted to.


If the peripheral controller determines that the commands and/or acknowledgements should be transmitted to the portable electronic device at 1018, then the commands and/or acknowledgements may be transmitted to the portable electronic device at 1020. For example, if the transmission is an acknowledgement acknowledging the transfer of funds, the peripheral controller may determine that the acknowledgement may be transmitted to the portable electronic device to inform the user of the successful transfer of funds. The acknowledgement may then be displayed on a display of the portable electronic device (e.g. display 1102 as illustrated in FIGS. 11A-11D).


If the peripheral controller determines that the commands and/or acknowledgements should not be transmitted to the portable electronic device at 1018 or subsequent to the transmission of the commands and/or acknowledgements to the portable electronic device at 1020, the peripheral controller may determine and identify whether the commands and/or acknowledgements may be transmitted to the at least one peripheral device on the gaming machine at 1022. For example, if the transmission is an acknowledgement acknowledging the transfer of funds, the peripheral controller may determine that the acknowledgement may be transmitted to the user input buttons and/or switches. The user input buttons and/or switches may then light up to indicate to the player that he may play the game of chance. In another example, the peripheral controller may determine that the acknowledgement may be transmitted to the display of the gaming machine to indicate or display the amount of credits. Thus, if the peripheral controller determines and identifies that the commands and/or acknowledgements should be transmitted to at least one peripheral device on the gaming machine at 1022, the commands and/or acknowledgements may be transmitted to the identified at least one peripheral device on the gaming machine at 1024.



FIGS. 11A-11D illustrate example graphical user interfaces of a portable electronic device. FIG. 11A illustrates one example graphical user interface presenting gaming functions to play video black jack. The graphical user interface may have a plurality of indicators 1154 presented on a display 1102 of the portable electronic device 1100. Each plurality of indicator 1154 may represent any gaming function such as “Hit” 1150, “Stand” 1152, “Min. Bet” 1156, and the like. Although illustrated with specific game play functions, this is not intended to be limiting as any type of gaming function to play a game of chance on the gaming machine may be represented such as a “Play Bonus” indicator, “Spin Wheel” indicator, and the like. Each indicator may represent a virtual peripheral device that is associated with and/or corresponding to at least one peripheral device of the gaming machine. For example, the “Hit” indicator 1156 may be associated with a virtual “hit” button, which may be associated with a “Hit” button on the gaming machine. In another embodiment, the “Transfer Funds” indicator 1160 may correspond to a virtual bill acceptor, which may be associated with the bill acceptor on the gaming machine.


If the portable electronic device 1100 detects a user-selection of the “Transfer Funds” indicator, a funds transfer screen may be displayed on the display 1101 of the portable electronic device 1100 as illustrated in FIG. 11B. The portable electronic device 1100 may display a user-enterable field 1100 on display 1108. The user-enterable field 1100 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 “1100.00” as illustrated in FIG. 11B. In another example, the user may enter a credit amount, such as credit accumulated in his player tracking account. The user-enterable field 1100 may be populated using a numerical keypad 1112, joystick, or any other user-input buttons or switches.


In one embodiment, the user may obtain funds from a third party server using the portable electronic device 1100 prior to selection of the “Transfer Funds” indicator. For example, the user may request an advance of funds from a credit card server. In another embodiment, the user may request a debit from a bank account server. Any known methods to obtain funds are contemplated and may be used to obtain funds to play the game of chance on the gaming machine.


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



FIG. 11C illustrates an example graphical user interface indicating that the funds transfer request is processed and transmitted to the gaming machine. In one embodiment, as illustrated, a “Sending Your User Request To The Gaming Machine” message may be displayed on the display 1108 of the portable electronic device 1100 to inform the user of the transmission. 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 (e.g. obtained from location server 104 illustrated in FIG. 1), location information of the gaming device (e.g. obtained from location server 104 illustrated in FIG. 1), 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.



FIG. 11D illustrates an exemplary graphical user interface representing completion of the funds transfer. Upon receipt of the funds transfer request received from the portable electronic, the peripheral management device may process the funds transfer request. In other words, the peripheral management 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) gaming machine to transfer funds to, and any other necessary information to facilitate the transfer of funds to the gaming machine.


The peripheral controller may also process the at least one funds transfer request by parsing the information in the funds transfer request to determine which peripheral device, on the gaming machine, the user would like to access. Each virtual peripheral device on the portable electronic device may be associated with a peripheral device on the gaming machine. Thus, the peripheral controller may determine that the user would like to transfer a specific amount of funds to the gaming machine via the virtual bill acceptor, which may be associated with the bill acceptor on the gaming machine. The user request may then be processed as a request for the bill acceptor on the gaming machine. Additionally, processing the at least one funds transfer request may include modifying the funds transfer request to reflect the proper source address and destination address. For example, the funds transfer request may be modified to reflect the source address as the bill acceptor and the destination address as the gaming machine processor. This permits for the seamless transfer of information or data to the gaming machine processor from the portable electronic device. In other words, peripheral management device may be invisible to the gaming machine processor.


The processed funds transfer request may then be transmitted to the gaming machine processor (e.g. gaming machine processor 302 as illustrated in FIG. 3) for the gaming machine processor to process. For example, the gaming machine processor may determine that the user transferred the fund amount to play a game of chance which was received by the bill acceptor. The gaming machine processor may then transmit commands and/or acknowledgements to at least one peripheral device of the gaming machine to allow the user to play the game of chance. For example, the gaming machine may transmit a command to the display to present the fund amount on the display. In another example, the gaming machine may transmit an acknowledgment to the bill acceptor to display an acknowledgement message or fund amount on a display of the bill acceptor. In another embodiment, the gaming machine may instruct the user input buttons or switches to activate and light up to indicate that the player may begin to play the game of chance.


The peripheral controller may intercept the commands and/or acknowledgments and process the intercepted commands and/or acknowledgments. The peripheral controller may process the intercepted commands and/or acknowledgements by parsing the commands and/or acknowledgement to determine where the commands and/or acknowledgments should be transmitted to. In other words, the peripheral controller may process the intercepted commands and/or acknowledgements to determine which virtual peripheral device on the portable electronic device the commands and/or acknowledgements should be transmitted to and to determine which peripheral device on the gaming machine the commands and/or acknowledgements should be transmitted to.


For example, if the transmission is an acknowledgement acknowledging the transfer of funds, the peripheral controller may determine that the acknowledgement may be transmitted to the portable electronic device to inform the user of the successful transfer of funds. The acknowledgement may then be displayed on a display of the portable electronic device as illustrated in FIG. 11D.


In one example, the portable electronic device 1100 may present a successful message 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 1118 to create a virtual receipt. The portable electronic device 1100 may then display the virtual receipt (not shown) on the display 1108 and digitally store the virtual receipt in a memory of the portable electronic device 1100.


Example 2


FIG. 12 illustrates an exemplary flow diagram of a method to generate a receipt using a portable electronic device. The method 1200 may begin by the portable electronic device receiving a print ticket request to print a ticket at 1202 by the user. For example, the player may have completed a game of chance on the gaming machine and may want to cash out the remaining credits. In one embodiment, the print ticket request may be physically initiated by the user pressing a “Cash Out” indicator (e.g., “Cash Out” indicator 788 illustrated in FIG. 7J) presented on a display of the portable electronic device. In another embodiment, the print ticket request 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 print a ticket. For example, the audio command may include words such as “end game”, “print receipt”, “cash out”, and the like.


The print ticket request may be transmitted from the portable electronic device to a peripheral controller (e.g. peripheral controller 402 illustrated in FIG. 4) at 1204. In one embodiment, the print ticket request may be encrypted by the portable electronic device prior to being transferred. Any known encryption methods may be used such as AES, MAC, HMAC, SHA-2 and the like. The print ticket request may include any necessary information or data to facilitate the printing of a ticket, such as a portable electronic device identifier, destination address (e.g. which gaming machine to cash out of), physical location of the gaming machine, and the like.


The peripheral controller may process the print ticket request at 1206. The peripheral controller may process the print ticket request by parsing the information in the print ticket request to determine which peripheral device is associated with the print ticket request. Each virtual peripheral device on the portable electronic device may be associated with a peripheral device on the gaming machine. Thus, the peripheral controller may determine that the user would like to cash out of the gaming machine by detecting an input from the “Cash Out” indicator. The “Cash Out” indicator may be associated with the “Cash Out” button or switch on the gaming machine. Additionally, the peripheral controller may process the print ticket request by modifying the print ticket request to reflect the proper source address and destination address. For example, the print ticket request may be modified to reflect the source address as the cash out button and the destination address as the gaming machine processor. This permits for the seamless transfer of information or data to the gaming machine processor from the portable electronic device. In other words, peripheral management device is invisible to the gaming machine.


The processed print ticket request may then be transmitted to the gaming machine processor (e.g. gaming machine processor 302 as illustrated in FIG. 3) at 1208 for a gaming machine processor to process at 1210. For example, from the source address, the gaming machine processor may determine that the user pressed the “Cash Out” button on the gaming machine. The gaming machine processor may then transmit a print command to the printer to print an electronic ticket at 1212.


The peripheral controller may intercept the print command at 1214 and process the print command at 1216. The peripheral controller may process the print command by parsing the command to determine where the command it should be transmitted to. In other words, the peripheral controller may process the print command to determine which virtual peripheral device on the portable electronic device the command should be transmitted to and to determine which peripheral device on the gaming machine the command should be transmitted to. This determination may be based upon the destination address of the print command, the command itself, or any other identifying criteria. For example, the peripheral controller may determine that a print command should be transmitted to a printer and not a display. In another example, the destination address of the print command may be the printer on the gaming machine.


If the peripheral controller determines that the command should be transmitted to the portable electronic device at 1218, then the command may be transmitted to the portable electronic device at 1220. For example, the peripheral controller may determine that the print command can be transmitted to a virtual printer of the portable electronic device to print a virtual ticket on the portable electronic device. Thus, the print command may be transmitted to the virtual printer of the portable electronic device at 1220.


Alternatively, the peripheral controller may determine that the ticket should be printed on the printer of the gaming machine and determine not to transmit the print command to the portable electronic device at 1218. The peripheral controller may then transmit the print command to the printer of the gaming machine at 1224.



FIGS. 13A-13D illustrate example graphical user interfaces to generate a receipt using a portable electronic device. Referring to FIG. 13A, the portable electronic device 1300 may receive a print ticket request to print a ticket by the user. For example, the player may have completed a game of chance on the gaming machine and may want to cash out the remaining credits. In one embodiment, the print ticket request may be physically initiated by the user pressing a “Cash Out” indicator 1304 presented on a display 1302 of the portable electronic device 1300. In another embodiment, the print ticket request may be an audio command. The audio command may be any audio command received and recognizable by the portable electronic device 1300 as an instruction or command to print a ticket. For example, the audio command may include words such as “end game”, “print receipt”, “cash out”, and the like.


The portable electronic device 1300 may display a confirmation request to the user as illustrated in FIG. 13B. The user may be prompted to confirm the print ticket request by sending a confirmation message such as “Would You Like To Cash Out?” 1306. The user may confirm the request by selecting to “Yes” indicator 1308 or cancel the request by selecting the “No” indicator 1310.


If the user confirms the request by selecting the “Yes” indicator 1308, a confirmation of transfer of the print request may be displayed as illustrated in FIG. 13C. For example, a message such as “Sending Your User Request To The Gaming Machine” message may be displayed on the display 1302 of the portable electronic device 1300 to inform the user of the transmission.


The print ticket request may be transmitted from the portable electronic device 1300 to a peripheral controller (e.g. peripheral controller 402 illustrated in FIG. 4). In one embodiment, the print ticket request may be encrypted by the portable electronic device 1300 prior to being transferred. Any known encryption methods may be used such as AES, MAC, HMAC, SHA-2 and the like. The print ticket request may include any necessary information or data to facilitate the printing of a ticket, such as a portable electronic device identifier, destination address (e.g. which gaming machine to cash out of), physical location of the gaming machine, and the like.


The peripheral controller may process the print ticket request by parsing the information in the print ticket request to determine which peripheral device is associated with the print ticket request. Each virtual peripheral device on the portable electronic device may be associated with a peripheral device on the gaming machine. Thus, the peripheral controller may determine that the user would like to cash out of the gaming machine by detecting an input from the “Cash Out” indicator 1304. The “Cash Out” indicator 1304 may be associated with a “Cash Out” button or switch on the gaming machine. Additionally, the peripheral controller may process the print ticket request by modifying the print ticket request to reflect the proper source address and destination address. For example, the print ticket request may be modified to reflect the source address as the cash out button and the destination address as the gaming machine processor. This permits for the seamless transfer of information or data to the gaming machine processor from the portable electronic device. In other words, peripheral management device is invisible to the gaming machine.


The processed print ticket request may then be transmitted to the gaming machine processor (e.g. gaming machine processor 302 as illustrated in FIG. 3) for the gaming machine processor to process. For example, from the source address, the gaming machine processor may determine that the user pressed the “Cash Out” button on the gaming machine. The gaming machine processor may then transmit a print command to the printer to print an electronic ticket.


The peripheral controller may intercept the print command and process the print command. The peripheral controller may process the print command by parsing the command to determine where the command it should be transmitted to. In other words, the peripheral controller may process the print command to determine which virtual peripheral device on the portable electronic device the command should be transmitted to and to determine which peripheral device on the gaming machine the command should be transmitted to. In one embodiment, the peripheral controller may determine that the original print ticket request was generated at the portable electronic device 1300 and the command should therefore be transferred to the portable electronic device 1300. In another embodiment, the peripheral controller may determine that it is in communication with the portable electronic device 1300 and automatically transmit the command to the portable electronic device 1300. The print command may be transmitted to a virtual printer of the portable electronic device to print a virtual ticket on the portable electronic device as illustrated in FIG. 13D. In one embodiment, the virtual ticket 1320 may be presented on the display 1302. In another embodiment, the virtual ticket may be saved in a memory on the portable electronic device 1300 by pressing the “Save” indicator 1324.


Additional details on peripheral devices for gaming machines are provided in U.S. patent application Ser. No. 12/945,888, entitled “MULTI-FUNCTION PERIPHERAL DEVICE,” 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.

Claims
  • 1. A gaming machine, comprising: a player tracking device configured to receive player data pertaining to a player; anda peripheral management device, the peripheral management device including at least a controller configured to communicate with a portable electronic device, the peripheral management device configured to: receive a peripheral data packet to be processed;determine whether to process the peripheral data packet on at least one peripheral device of a plurality of peripheral devices of the gaming machine or at least one virtual peripheral device of a plurality of virtual peripheral devices of the portable electronic device, the determination of whether to process the peripheral data packet at the at least one peripheral device or the at least one virtual peripheral device will process the peripheral data packet based on whether the portable electronic device is connected to the gaming machine;generate an instructional data packet for the at least one virtual peripheral device if the peripheral data packet is determined to be processed on the at least one virtual peripheral device; andtransmit the instructional data packet to the portable electronic device if the peripheral data packet is determined to be processed on the at least one virtual peripheral device,wherein the at least one virtual peripheral device has a counterpart peripheral device on the gaming machine, and at least another of the plurality of virtual peripheral devices besides the at least one virtual peripheral device has another counterpart peripheral device on the gaming machine,wherein requests directed to the at least one virtual peripheral device are processed at the at least one virtual peripheral device, with the at least one virtual peripheral device interacting with the gaming machine in a manner as would the counterpart peripheral device, andwherein the player tracking device is one of the plurality of the peripheral devices.
  • 2. The gaming machine of claim 1, wherein the peripheral management device includes a wireless communication module, and wherein the instructional data packet is transmitted to the portable electronic device via the wireless communication module.
  • 3. The gaming machine of claim 1, wherein the at least one peripheral device includes an accelerometer for a peripheral input.
  • 4. A gaming machine as recited in claim 1, wherein the gaming machine is configured to: receive location information for the portable electronic device; anddeem the portable electronic device authorized for use with the gaming device based on the location information.
  • 5. A gaming machine as recited in claim 1, wherein the counterpart peripheral device comprises a player tracking device, and the at least one virtual peripheral device comprises a virtual player tracking device.
  • 6. A gaming machine as recited in claim 1, wherein the counterpart peripheral device comprises a touch screen or button, and the at least one virtual peripheral device comprises a virtual printer for presenting a virtual ticket.
  • 7. A gaming machine as recited in claim 1, wherein the counterpart peripheral device is one of a bill acceptor, a card reader, a bar code reader, or a camera.
  • 8. A gaming machine, comprising: a gaming machine processor configured to operate the gaming machine to provide a game of chance to a user of the gaming machine;a user input device configured to receive one or more user inputs from the user for use with the game of chance;a display device configured to present gaming information pertaining to the game of chance;a wireless interface configured to support wireless communication with at least one external virtual peripheral device of a plurality of external virtual peripheral devices that are associated with at least one portable computing device;at least one internal peripheral device of a plurality of internal peripheral devices, the at least one internal peripheral device being configured to provide at least one internal peripheral function for the gaming device; anda peripheral management device operatively connected to the gaming processor, the at least one internal peripheral device and the wireless interface, the peripheral management device being configured to receive peripheral bound data, perform a determination whether the peripheral bound data is to be processed by the at least one internal peripheral device or the at least one external virtual peripheral device, and provide the peripheral bound data to the at least one internal peripheral device or the at least one external virtual peripheral device in accordance with the determination,wherein at least one of the plurality of external virtual peripheral devices has a counterpart peripheral device of the plurality of internal peripheral devices of the gaming machine, and at least another of the external virtual peripheral devices besides the at least one virtual peripheral device has another counterpart peripheral device of the plurality of internal peripheral devices of the gaming machine, andwherein requests directed to the at least one of the plurality of external virtual peripheral devices are processed at the at least one of the plurality of external virtual peripheral devices, with the at least one of the plurality of external virtual peripheral devices interacting with the gaming machine in a manner as would the counterpart peripheral device of the plurality of internal peripheral devices of the gaming machine.
  • 9. The gaming machine as recited in claim 8, wherein the at least one internal peripheral device includes an accelerometer to detect an input.
  • 10. The gaming machine, comprising: a gaming machine processor; anda peripheral management device coupled to the gaming machine processor, the peripheral management device including at least a controller configured to communicate with a portable electronic device,wherein the peripheral management device is configured to: receive a peripheral data packet to be processed from the gaming machine processor or the portable electronic device, the peripheral data packet including at least one command;determine whether to process the peripheral data packet on at least one peripheral device of a plurality of peripheral devices of the gaming machine or at least one virtual peripheral device of a plurality of virtual peripheral devices of the portable electronic device;determine which of the at least one virtual peripheral device of the plurality of virtual peripheral devices that will process the peripheral data packet based on the at least one command if the peripheral data packet is determined to be processed on the at least one virtual peripheral device of the plurality of virtual peripheral devices;generate an instructional data packet for the determined at least one virtual peripheral device that will process the peripheral data packet if the peripheral data packet is determined to be processed on the at least one virtual peripheral device of the plurality of virtual peripheral devices; andtransmit the instructional data packet to the portable electronic device if the peripheral data packet is determined to be processed on the at least one virtual peripheral device of the plurality of virtual peripheral devices,wherein at least one of the plurality of virtual peripheral devices has a corresponding peripheral device of the plurality of peripheral devices of the gaming machine, and at least another of the plurality of virtual peripheral devices besides the at least one virtual peripheral device has another corresponding peripheral device of the plurality of peripheral devices of the gaming machine, andwherein requests directed to the at least one virtual peripheral device are processed at the at least one virtual peripheral device, with the at least one virtual peripheral device interacting with the gaming machine in a manner as would the corresponding peripheral device.
  • 11. The gaming machine of claim 10, wherein the peripheral management device includes a wireless communication module, and wherein the instructional data packet is transmitted to the portable electronic device via the wireless communication module.
  • 12. The gaming machine of claim 10, wherein the at least one peripheral device includes an accelerometer to detect an input.
  • 13. The gaming machine of claim 10, wherein the gaming machine is a slot machine.
  • 14. The gaming machine as recited in claim 10, wherein the at least one virtual peripheral device has a graphical user interface displayed by the portable electronic device, andwherein the at least one command pertains to information to be included in the graphic user interface displayed by the portable electronic device.
  • 15. The gaming machine as recited in claim 10, wherein the at least one command pertains to a funds transfer.
  • 16. A gaming machine as recited in claim 15, wherein the peripheral management device is configured to: receive a first location data of the gaming machine from a location server;obtain a second location data of the portable electronic device; andauthenticate the portable electronic device if the first location data is substantially proximate to the second location data.
  • 17. A gaming machine as recited in claim 10, wherein the at least one peripheral device is one of a bill acceptor, a card reader, a bar code reader, or a camera.
  • 18. A gaming machine as recited in claim 10, wherein the at least one virtual peripheral device comprises a virtual printer for presenting a virtual ticket.
  • 19. A gaming machine as recited in claim 10, wherein the corresponding peripheral device of the plurality of peripheral devices of the gaming machine comprises a touch screen or button.
  • 20. A gaming machine as recited in claim 1, wherein the gaming machine is configured to: determine whether the portable electronic device is proximate to the gaming machine; anddeem the portable electronic device authorized for use with the gaming machine if the portable electronic device is determined to be proximate to the gaming machine.
CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No. 12/945,889, filed Nov. 14, 2010, and entitled “PERIPHERAL MANAGEMENT DEVICE FOR VIRTUAL GAME INTERACTION,” which is hereby incorporated herein by reference, which is hereby incorporated herein by reference.

US Referenced Citations (553)
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
5067712 Georgilas Nov 1991 A
5429361 Raven et al. Jul 1995 A
5489103 Okamoto Feb 1996 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
6146273 Olsen Nov 2000 A
6165071 Weiss Dec 2000 A
6231445 Acres May 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
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
6719630 Seelig et al. Apr 2004 B1
6749510 Giobbi 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
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 Konami Apr 2010 B2
7699703 Muir et al. Apr 2010 B2
7722453 Lark et al. May 2010 B2
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 Speer 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
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
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
8696470 Nguyen Apr 2014 B2
8745417 Huang et al. Jun 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 Chung Nov 2016 B2
9486704 Chung Nov 2016 B2
9576425 Nguyen Feb 2017 B2
9626826 Nguyen Apr 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
10140816 Nguyen Nov 2018 B2
20010004607 Olsen Jun 2001 A1
20010016516 Takatsuka Aug 2001 A1
20010024971 Brossard Sep 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
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
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
20030008696 Abecassis et al. Jan 2003 A1
20030027635 Walker et al. Feb 2003 A1
20030064805 Wells Apr 2003 A1
20030064807 Walker et al. Apr 2003 A1
20030092480 White et al. May 2003 A1
20030100361 Sharpless et al. May 2003 A1
20030103965 Jung et al. Jun 2003 A1
20030104860 Cannon et al. Jun 2003 A1
20030104865 Itkis et al. Jun 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
20040082385 Silva et al. Apr 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
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
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
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
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
20050202875 Murphy et al. 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
20060073869 LeMay et al. Apr 2006 A1
20060073897 Englman et al. Apr 2006 A1
20060079317 Flemming et al. Apr 2006 A1
20060126529 Hardy Jun 2006 A1
20060148551 Walker et al. 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
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
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
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
20070259717 Mattice et al. 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
20070298873 Nguyen et al. Dec 2007 A1
20080015032 Bradford et al. Jan 2008 A1
20080020824 Cuddy et al. 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
20080102956 Burman et al. May 2008 A1
20080102957 Burnman et al. May 2008 A1
20080113772 Burrill et al. May 2008 A1
20080119267 Denlay May 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
20080182667 Davis et al. Jul 2008 A1
20080200251 Alderucci Aug 2008 A1
20080207307 Cunningham, II et al. Aug 2008 A1
20080214258 Brosnan et al. Sep 2008 A1
20080215319 Lu Sep 2008 A1
20080234047 Nguyen Sep 2008 A1
20080238610 Rosenbereg Oct 2008 A1
20080248849 Lutnick Oct 2008 A1
20080248865 Cole 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
20080300058 Sum et al. Dec 2008 A1
20080305864 Kellye 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
20090029766 Lutnick et al. Jan 2009 A1
20090054149 Brosnan et al. Feb 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
20090131151 Harris et al. May 2009 A1
20090132163 Ashley et al. May 2009 A1
20090137255 Ashley et al. May 2009 A1
20090138133 Buchholz et al. May 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
20090271287 Halpern Oct 2009 A1
20090275410 Kisenwether et al. Nov 2009 A1
20090275411 Kisenwether et al. Nov 2009 A1
20090280910 Gagner et al. Nov 2009 A1
20090282469 Lynch Nov 2009 A1
20090298468 Hsu Dec 2009 A1
20100002897 Keady Jan 2010 A1
20100004058 Acres 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
20100106612 Gupta Apr 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
20100197383 Rad et al. Aug 2010 A1
20100197385 Aoki et al. Aug 2010 A1
20100203955 Sylla Aug 2010 A1
20100203963 Allen Aug 2010 A1
20100227662 Speer et al. Sep 2010 A1
20100227670 Arezina et al. Sep 2010 A1
20100227671 Laaroussi Sep 2010 A1
20100227687 Speer et al. Sep 2010 A1
20100234091 Baerlocher et al. Sep 2010 A1
20100279764 Allen et al. Nov 2010 A1
20100323780 Acres Dec 2010 A1
20100325703 Etchegoyen Dec 2010 A1
20110009181 Speer et al. Jan 2011 A1
20110039615 Acres Feb 2011 A1
20110065492 Acres Mar 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
20110118010 Brune May 2011 A1
20110159966 Gura et al. Jun 2011 A1
20110183732 Block Jul 2011 A1
20110183749 Allen Jul 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
20110263318 Agarwal et al. Oct 2011 A1
20110269548 Barclay et al. Nov 2011 A1
20110306400 Nguyen Dec 2011 A1
20110306426 Novak et al. Dec 2011 A1
20120015709 Bennett et al. Jan 2012 A1
20120028703 Anderson et al. 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
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
20130104193 Gatto et al. Apr 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
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
20130316808 Nelson Nov 2013 A1
20130337878 Shepherd 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
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
20170154497 Nguyen Jun 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
Foreign Referenced Citations (11)
Number Date Country
2033638 May 1980 GB
2062923 May 1981 GB
2096376 Oct 1982 GB
2097570 Nov 1982 GB
2335524 Sep 1999 GB
12005000454 May 2007 PH
WO 05073933 Aug 2005 WO
WO 2008027621 Mar 2008 WO
WO 2009026309 Feb 2009 WO
WO 2009062148 May 2009 WO
WO 2010017252 Feb 2010 WO
Non-Patent Literature Citations (238)
Entry
Notice of Allowance for U.S. Appl. No. 13/632,828, dated Dec. 16, 2016.
Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 19, 2016.
Notice of Allowance for U.S. Appl. No. 14/211,536, dated Dec. 28, 2016.
Notice of Allowance for U.S. Appl. No. 13/801,256, dated Jan. 20, 2017.
Office Action for U.S. Appl. No. 13/800,917, dated Feb. 3, 2017.
Final Office Action for U.S. Appl. No. 12/797,616, dated Feb. 10, 2017.
Office Action for U.S. Appl. No. 12/945,888, dated Feb. 28, 2017.
Final Office Action for U.S. Appl. No. 14/189,948, dated Mar. 17, 2017.
Office Action for U.S. Appl. No. 15/400,840, dated Mar. 10, 2017.
Notice of Allowance for U.S. Appl. No. 13/801,121, dated Mar. 29, 2017.
Office Action for U.S. Appl. No. 15/270,333, dated Mar. 30, 2017.
Office Action for U.S. Appl. No. 15/402,945, dated Apr. 5, 2017.
Office Action for U.S. Appl. No. 15/271,488, dated Apr. 19, 2017.
Final Office Action for U.S. Appl. No. 14/217,066, dated Apr. 21, 2017.
Office Action for U.S. Appl. No. 14/216,986 dated Apr. 26, 2017.
Office Action for U.S. Appl. No. 13/801,171, dated Jun. 14, 2017.
Office Action for U.S. Appl. No. 14/017,159, dated Jun. 29, 2017.
Notice of Allowance for U.S. Appl. No. 15/270,333, dated Jul. 5, 2017.
Final Office Action for U.S. Appl. No. 13/800,917, dated Jul. 13, 2017.
Notice of Allowance for U.S. Appl. No. 13/801,234, dated Jul. 5, 2017.
Notice of Allowance for U.S. Appl. No. 14/217,066, dated Jul. 14, 2017.
Final Office Action for U.S. Appl. No. 14/518,909, dated Jul. 19, 2017.
Final Office Action for U.S. Appl. No. 13/801,121, dated Sep. 15, 2016.
Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 17, 2015.
Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 19, 2016.
Notice of Allowance for U.S. Appl. No. 15/293,751, dated Aug. 4, 2017.
Advisory Action for U.S. Appl. No. 14/189,948, dated Jul. 28, 2017.
Final OA for U.S. Appl. No. 13/801,256, dated Aug. 15, 2014.
Final OA for U.S. Appl. No. 13/801,256, dated Feb. 18, 2015.
Advisory Action for U.S. Appl. No. 13/801,256, dated Dec. 5, 2014.
Office Action for U.S. Appl. No. 13/801,256, dated Jan. 12, 2016.
Final Office Action for U.S. Appl. No. 13/801,256, dated Aug. 16, 2016.
Office Action for U.S. Appl. No. 13/801,256, dated Aug. 18, 2017.
Office Action for U.S. Appl. No. 13/622,702, dated Aug. 31, 2017.
Office Action for U.S. Appl. No. 12/945,888, dated Sep. 1, 2017.
Office Action for U.S. Appl. No. 14/017,150, dated Sep. 7, 2017.
Notice of Allowance for U.S. Appl. No. 14/189,948, dated Sep. 13, 2017.
Office Action for U.S. Appl. No. 15/138,086, dated Oct. 19, 2017.
Notice of Allowance for U.S. Appl. No. 15/402,945 dated Nov. 21, 2017.
Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 13, 2017.
Final Office Action for U.S. Appl. No. 15/271,488, dated Dec. 21, 2017.
Office Action for U.S. Appl. No. 15/671,133, dated Dec. 22, 2017.
Final Office Action for U.S. Appl. No. 14/216,986, dated Dec. 26, 2017.
Restriction Requirement for U.S. Appl. No. 15/427,307, dated Jan. 17, 2018.
Office Action for U.S. Appl. No. 15/798,363, dated Jan. 26, 2018.
Office Action for U.S. Appl. No. 15/427,291, dated Jan. 29, 2018.
Final Office Action for U.S. Appl. No. 14/017,159, dated Feb. 1, 2018.
Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 22, 2018.
Office Action for U.S. Appl. No. 15/811,654, dated Feb. 22, 2018.
Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 27, 2018.
Final Office Action for U.S. Appl. No. 15/427,308, dated Mar. 19, 2018.
Office Action for U.S. Appl. No. 15/876,095, dated Apr. 3, 2018.
Office Action for U.S. Appl. No. 15/835,448, dated Apr. 4, 2018.
Office Action for U.S. Appl. No. 15/427,307, dated Apr. 9, 2018.
Office Action for U.S. Appl. No. 14/216,986, dated Apr. 6, 2018.
Office Action for U.S. Appl. No. 15/426,898 dated Apr. 16, 2018.
Notice of Allowance for U.S. Appl. No. 15/402,945, dated May 25, 2018.
Office Action for U.S. Appl. No. 15/428,922 dated Sep. 17, 2018.
Office Action for U.S. Appl. No. 15/495,975, dated Sep. 21, 2018.
Notice of Allowance for U.S. Appl. No. 15/271,488, dated Sep. 24, 2018.
Notice of Allowance for U.S. Appl. No. 15/876,095, dated Sep. 24, 2018.
Office Action for U.S. Appl. No. 13/622,702, dated Oct. 3, 2018.
Office Action for U.S. Appl. No. 15/293,751, dated Apr. 6, 2017.
Notice of Allowance for U.S. Appl. No. 13/801,171, dated Oct. 31, 2018.
Final Office Action for U.S. Appl. No. 15/835,448, dated Nov. 2, 2018.
Final Office Action for U.S. Appl. No. 15/480,295, dated Nov. 7, 2018.
Final Office Action for U.S. Appl. No. 14/963,106, dated Dec. 14, 2018.
Office Action for U.S. Appl. No. 16/162,358, dated Dec. 31, 2018.
Office Action for U.S. Appl. No. 14/017,159, dated Jan. 11, 2019.
Office Action for U.S. Appl. No. 15/426,898, dated Jan. 11, 2019.
Final Office Action for U.S. Appl. No. 15/495,973, dated Jan. 11, 2019.
Office Action for U.S. Appl. No. 14/216,986, dated Jan. 14, 2019.
Office Action for U.S. Appl. No. 15/427,307, dated Jan. 18, 2019.
Final Office Action for U.S. Appl. No. 15/798,363, dated Feb. 4, 2019.
Office Action for U.S. Appl. No. 16/125,614, dated Feb. 25, 2019.
Final OA for U.S. Appl. No. 12/945,888, dated Jun. 28, 2016.
Notice of Allowance for U.S. Appl. No. 13/833,953, dated Jul. 6, 2016.
Final Office Action for U.S. Appl. No. 13/801,171, dated May 21, 2014.
Final Office Action for U.S. Appl. No. 13/801,234, dated May 22, 2014.
Office Action for U.S. Appl. No. 14/211,536, dated Jul. 13, 2016.
Notice of Allowance for U.S. Appl. No. 13/801,076, dated Jul. 11, 2016.
Office Action for U.S. Appl. No. 13/296,182, dated Jul. 20, 2016.
Restriction Requirement for U.S. Appl. No. 13/296,182, dated Oct. 12, 2012.
Advisory Action for U.S. Appl. No. 13/296,182, dated May 8, 2014.
Office Action for U.S. Appl. No. 13/296,182, dated Dec. 23, 2015.
Advisory Action for U.S. Appl. No. 13/843,192, dated May 8, 2014.
Office Action for U.S. Appl. No. 14/217,066, dated Dec. 22, 2016.
Final Office Action for U.S. Appl. No. 14/216,986, dated Sep. 23, 2016.
Office Action for U.S. Appl. No. 14/017,159, dated Sep. 23, 2016.
Office Action for U.S. Appl. No. 13/632,743, dated Sep. 23, 2016.
Final Office Action for U.S. Appl. No. 13/801,234, dated Oct. 14, 2016.
Final Office Action for U.S. Appl. No. 13/843,087, dated Oct. 13, 2016.
Final Office Action for U.S. Appl. No. 13/622,702, dated Oct. 13, 2016.
Office Action for U.S. Appl. No. 14/189,948, dated Nov. 7, 2016.
Final Office Action for U.S. Appl. No. 14/211,536, dated Mar. 14, 2014.
Notice of Allowance for U.S. Appl. No. 13/833,116, dated Oct. 11, 2016.
Notice of Allowance for U.S. Appl. No. 13/801,271, dated Dec. 2, 2016.
Notice of Allowance for U.S. Appl. No. 12/797,610, dated Dec. 7, 2016.
Office Action for U.S. Appl. No. 15/495,973, dated Jun. 4, 2018.
Notice of Allowance for U.S. Appl. No. 15/427,291 dated Jun. 18, 2018.
Notice of Allowance for U.S. Appl. No. 15/271,488, dated Jun. 19, 2018.
Notice of Allowance for U.S. Appl. No. 15/480,295, dated Jun. 20, 2018.
Office Action for U.S. Appl. No. 14/963,106, dated Jun. 22, 2018.
Final Office Action for U.S. Appl. No. 15/427,307, dated Jul. 9, 2018.
Notice of Allowance for U.S. Appl. No. 13/633,118, dated Aug. 3, 2018.
Office Action for U.S. Appl. No. 15/671,133, dated Aug. 9, 2018.
Office Action for U.S. Appl. No. 15/427,308, dated Aug. 15, 2018.
Office Action for U.S. Appl. No. 15/798,363, dated Aug. 29, 2018.
Benston, Liz, “Harrahs Launches iPhone App; Caesars Bypasses Check-in,” Las Vegas Sun, Las Vegas, NV. Jan. 8, 2010.
Finnegan, Amanda, “Casinos Connecting with Customers via iPhone Apps”, May 27, 2010, Las Vegas Sun, Las Vegas, NV.
Gaming Today Staff, “Slots showcased at 2009 National Indian Gaming Assoc.”, GamingToday.com, Apr. 14, 2009.
Green, Marian,“Testing Texting Casino Journal”, Mar. 2, 2009.
Hasan, Ragib, et al., “A Survey of Peer-to-Peer Storage Techniques for Distributed File Systems”, National Center for Supercomputing Applications, Department of Computer Science, University of Ilinois at Urbana Champain, Jun. 27, 2005.
Jones, Trahern, “Telecon-equipped drones could revolutionize wireless market”, azcentral.com, http://www.azcentral.com/business/news/articles/20130424telecom-equipped-drones-could-revolutionize-wireless-market.html, downloaded Jul. 2, 2013, 2 pages.
Yancey, Kitty Bean, “Navigate Around Vegas with New iPhone Apps”, USA Today, Jun. 3, 2010.
iAPS, Daily Systems LLC, 2010.
U.S. Appl. No. 12/945,888, filed Nov. 14, 2010.
U.S. Appl. No. 12/945,889, filed Nov. 14, 2010.
U.S. Appl. No. 13/622,702, filed Sep. 19, 2012.
U.S. Appl. No. 13/800,917, filed Mar. 13, 2013.
U.S. Appl. No. 13/296,182, filed Nov. 15, 2011.
U.S. Appl. No. 13/801,234, filed Mar. 13, 2013.
U.S. Appl. No. 13/801,171, filed Mar. 13, 2013.
U.S. Appl. No. 13/843,192, filed Mar. 15, 2013.
U.S. Appl. No. 13/843,087, filed Mar. 15, 2013.
U.S. Appl. No. 13/632,743, filed Oct. 1, 2012.
U.S. Appl. No. 13/632,828, filed Oct. 1, 2012.
U.S. Appl. No. 13/833,953, filed Mar. 15, 2013.
U.S. Appl. No. 12/619,672, filed Nov. 16, 2009.
U.S. Appl. No. 13/801,121, filed Mar. 13, 2013.
U.S. Appl. No. 12/581,115, filed Oct. 17, 2009.
U.S. Appl. No. 13/801,076, filed Mar. 13, 2013.
U.S. Appl. No. 13/617,717, filed Nov. 12, 2009.
U.S. Appl. No. 13/633,118, filed Oct. 1, 2012.
U.S. Appl. No. 12/797,610, filed Jun. 10, 2010.
U.S. Appl. No. 13/801,256, filed Mar. 13, 2013.
U.S. Appl. No. 12/757,968, filed Apr. 9, 2010.
U.S. Appl. No. 12/797,616, filed Jun. 10, 2010.
U.S. Appl. No. 13/557,063, filed Jul. 24, 2012.
U.S. Appl. No. 13/833,116, filed Mar. 15, 2013.
U.S. Appl. No. 13/801,271, filed Mar. 13, 2011.
Office Action for U.S. Appl. No. 12/945,888 dated Apr. 10, 2012.
Final Office Action for U.S. Appl. No. 12/945,888 dated Sep. 21, 2012.
Advisory Action for U.S. Appl. No. 12/945,888 dated Jan. 30, 2013.
Office Action for U.S. Appl. No. 12/581,115 dated Dec. 20, 2011.
Final Office Action for U.S. Appl. No. 12/581,115 dated Sep. 13, 2012.
Notice of Allowance for U.S. Appl. No. 12/581,115 dated May 24, 2013.
Office Action for U.S. Appl. No. 12/619,672 dated Dec. 20, 2011.
Final Office Action for U.S. Appl. No. 12/619,672 dated Nov. 6, 2012.
Office Action for U.S. Appl. No. 12/619,672 dated Mar. 7, 2013.
Office Action for U.S. Appl. No. 12/617,717 dated Oct. 4, 2011.
Office Action for U.S. Appl. No. 12/617,717 dated Apr. 4, 2012.
Advisory Action for U.S. Appl. No. 12/617,717 dated Jun. 12, 2011.
Office Action for U.S. Appl. No. 12/617,717 dated Jun. 17, 2013.
Office Action for U.S. Appl. No. 12/797,610 dated Dec. 8, 2011.
Final Office Action for U.S. Appl. No. 12/797,610 dated Jun. 6, 2012.
Office Action for U.S. Appl. No. 12/797,610 dated Feb. 26, 2013.
Office Action for U.S. Appl. No. 12/757,968, dated May 9, 2012.
Final Office Action for U.S. Appl. No. 12/757,968, dated Nov. 29, 2012.
Office Action for U.S. Appl. No. 12/757,968, dated Apr. 25, 2013.
Office Action for U.S. Appl. No. 12/797,616 dated Mar. 15, 2012.
Final Office Action for U.S. Appl. No. 12/797,616 dated Oct. 13, 2012.
Office Action for U.S. Appl. No. 12/797,616 dated Feb. 13, 2013.
Final Office Action for U.S. Appl. No. 12/797,616 dated May 8, 2013.
Office Action for U.S. Appl. No. 13/296,182 dated Dec. 5, 2012.
Brochure, 5000 Ft. Inc., 1 page, Nov. 2010.
Frontier Fortune game, email notification, MGM Resorts Intl., Aug. 9, 2013.
“Getting Back in the Game: Geolocation Can Ensure Compliance with New iGaming Regulations”, White Paper, Quova, Inc., 2010.
Notice of Allowance of U.S. Appl. No. 12/619,672, dated Aug. 23, 2013.
Office Action for U.S. Appl. No. 13/633,118, dated Sep. 20, 2013.
Office Action for U.S. Appl. No. 13/801,256, dated Jul. 2, 2013.
Notice of Allowance for U.S. Appl. No. 12/619,672, dated Oct. 3, 2013.
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Oct. 11, 2013.
Final Office Action for U.S. Appl. No. 12/797,610, dated Jul. 10, 2013.
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Dec. 18, 2013.
Office Action for U.S. Appl. No. 12/945,889, dated Dec. 18, 2013.
Office Action for U.S. Appl. No. 13/632,828, dated Jul. 30, 2013.
Restriction Requirement for U.S. Appl. No. 13/801,256, dated Dec. 30, 2013.
Office Action for U.S. Appl. No. 13/801,171, dated Dec. 26, 2013.
Office Action for U.S. Appl. No. 13/801,234, dated Jan. 10, 2014.
Final Office Action for U.S. Appl. No. 13/296,182, dated Feb. 12, 2014.
Office Action for U.S. Appl. No. 12/617,717, dated Feb. 25, 2014.
Office Action for U.S. Appl. No. 13/801,076, dated Mar. 28, 2014.
Final Office Action for U.S. Appl. No. 13/633,118, dated Apr. 3, 2014.
Office Action for U.S. Appl. No. 13/843,192, dated Apr. 3, 2014.
Office Action for U.S. Appl. No. 13/632,743, dated Apr. 10, 2014.
Office Action for U.S. Appl. No. 13/801,121, dated Apr. 11, 2014.
Final Office Action for U.S. Appl. No. 12/945,889, dated Jun. 30, 2014.
Notice of Allowance for U.S. Appl. No. 12/617,717, dated Jul. 14, 2014.
Office Action for U.S. Appl. No. 13/801,121, dated Sep. 24, 2014.
Office Action for U.S. Appl. No. 13/801,171, dated Sep. 22, 2014.
Office Action for U.S. Appl. No. 13/801,234, dated Oct. 1, 2014.
Office Action for U.S. Appl. No. 13/801,271, dated Oct. 31, 2014.
Final Office Action for U.S. Appl. No. 13/843,192, dated Oct. 21, 2014.
Office Action for U.S. Appl. No. 13/632,743, dated Oct. 23, 2014.
Office Action for U.S. Appl. No. 12/945,889, dated Oct. 23, 2014.
Office Action for U.S. Appl. No. 13/632,828, dated Nov. 7, 2014.
Office Action fpr U.S. Appl. No. 12/797,610, dated Dec. 15, 2014.
Final Office Action for U.S. Appl. No. 12/945,889, dated Feb. 12, 2015.
Final Office Action for U.S. Appl. No. 13/801,171, dated Mar. 16, 2015.
Office Action for U.S. Appl. No. 13/833,116, dated Mar. 27, 2015.
Office Action for U.S. Appl. No. 13/632,828, dated Apr. 10, 2015.
Final Office Action for U.S. Appl. No. 13/801,121, dated Apr. 21, 2015.
Final Office Action for U.S. Appl. No. 13/557,063, dated Apr. 28, 2015.
Office Action for U.S. Appl. No. 13/296,182, dated Jun. 5, 2015.
Office Action for U.S. Appl. No. 13/843,192, dated Jun. 19, 2015.
Office Action for U.S. Appl. No. 12/797,610, dated Jul. 14, 2015.
Final Office Action for U.S. Appl. No. 13/833,953, dated Jul. 17, 2015.
Notice of Allowance for U.S. Appl. No. 12/945,889, dated Jul. 22, 2015.
Office Action for U.S. Appl. No. 12/797,616, dated Aug. 10, 2015.
Final Office Action for U.S. Appl. No. 13/801,234, dated Aug. 14, 2015.
Final Office Action for U.S. Appl. No. 13/833,116, dated Sep. 24, 2015.
Office Action for U.S. Appl. No. 13/801,121, dated Oct. 2, 2015.
Office Action for U.S. Appl. No. 14/017,150, dated Oct. 7, 2015.
Office Action for U.S. Appl. No. 14/017,159, dated Oct. 7, 2015.
Office Action for U.S. Appl. No. 13/801,271 dated Oct. 19, 2015.
Office Action for U.S. Appl. No. 14/211,536 dated Oct. 19, 2015.
Final Office Action for U.S. Appl. No. 13/632,828, dated Oct. 22, 2015.
Office Action for U.S. Appl. No. 14/217,066, dated Dec. 17, 2015.
Notice of Allowance for U.S. Appl. No. 13/557,063, dated Dec. 23, 2015.
Final Office Action for U.S. Appl. No. 13/843,192, dated Dec. 30, 2015.
Office Action for U.S. Appl. No. 13/801,076, dated Jan. 11, 2016.
Office Action for U.S. Appl. No. 12/945,888, dated Jan. 22, 2016.
Final Office Action for U.S. Appl. No. 12/797,616, dated Jun. 12, 2016.
Office Action for U.S. Appl. No. 13/800,917, dated Feb. 25, 2016.
Advisory Action for U.S. Appl. No. 13/632,828, dated Feb. 25, 2016.
Office Action for U.S. Appl. No. 13/801,234, dated Mar. 8, 2016.
Office Action for U.S. Appl. No. 14/216,986, dated Mar. 9, 2016.
Final Office Action for U.S. Appl. No. 13/801,271, dated Mar. 11, 2016.
Office Action for U.S. Appl. No. 13/622,702, dated Sep. 19, 2012.
Final Office Action for U.S. Appl. No. 13/633,118, dated Mar. 24, 2016.
Final Office Action for U.S. Appl. No. 14/189,948, dated Apr. 6, 2016.
Final Office Action for U.S. Appl. No. 12/797,610, dated Apr. 21, 2016.
Final Office Action for U.S. Appl. No. 14/017,150, dated Apr. 26, 2016.
Final Office Action for U.S. Appl. No. 13/801,121, dated May 11, 2016.
Final Office Action for U.S. Appl. No. 14/017,159, dated Jun. 6, 2016.
Office Action for U.S. Appl. No. 13/801,719, dated Jun. 6, 2016.
Office Action for U.S. Appl. No. 13/843,192, dated Jun. 9, 2016.
Related Publications (1)
Number Date Country
20160125695 A1 May 2016 US
Continuations (1)
Number Date Country
Parent 12945889 Nov 2010 US
Child 14993055 US