Patent Grant
10249134
The present invention relates to reducing energy consumption in electronic devices, particularly to reducing energy consumption in gaming devices, and more particularly to reducing energy consumption in a network of gaming devices.
Energy consumption at gaming establishments has been increasing for many years. Gaming establishments generally prefer to maintain a bright and stimulating environment. However, many gaming devices in the gaming establishment are not used constantly during the course of a day. Those gaming devices may be wastefully running at full power because they are not being utilized or even viewed by patrons. Power expenditures for gaming devices unlikely to be used unnecessarily increases cost for a gaming establishment by using power to operate the gaming devices, power to cool the gaming establishment from the heat generated by the gaming devices, and wastes precious energy.
As the number of electronic gaming devices grow, gaming establishments consumed more energy. As energy costs rise, the increase in cost of operating gaming devices has risen. For example, if the total power consumption of an average gaming device is approximately 300 watts, at $0.10/kwh, it costs a gaming establishment around $300 per year to run the gaming device. For a gaming establishment with 3,000 gaming devices, the power costs could be approximately $900,000. Reducing the power consumption by 35% could save a gaming establishment over $300,000 per year in energy costs alone; Indirect savings would also include air conditioning.
The present disclosure relates to an apparatus, system, and method for reducing power consumption in gaming devices. A power consumption control system enables a gaming operator to reduce electrical power supply to a network of gaming devices and thereby power down the gaming devices. The power consumption control system can also be used in other system configurations such as an office lighting system.
In one embodiment, a gaming device may have a memory having a plurality of power management rules and a processor configured to receive a power status from at least one secondary gaming device, retrieve at least one power management rule from the memory, and adjust a power operating state of the primary and/or secondary gaming device based on the power status information received from the at least one secondary gaming device and the at least one power management rule, wherein the gaming device is one of a plurality of gaming devices coupled to a network, wherein the secondary gaming device is another one of the plurality of gaming devices, and wherein the gaming device and the secondary gaming device are proximately located in an establishment and within a predetermined zone within the establishment.
In one embodiment, a system for controlling power consumption in a plurality of gaming devices may have a first gaming device configured to: retrieve a first power control rule from a first memory; configure a power state of the first gaming device based on the first power control rule; and transmit the power state of the first gaming device to a second gaming device. The second gaming device may be configured to: receive the power state of the first gaming device; retrieve a second power control rule from a second memory; and configure a power state of the second gaming device based on the power state of the first gaming device and the second power control rule.
In one embodiment, a method for controlling power consumption in a primary gaming device includes receiving a power operating parameter from at least one secondary gaming device, retrieving, at the primary gaming device, at least one power control rule, and configuring a power operating state of the primary gaming device based on the power state from the at least one secondary gaming device and the at least one power control rule.
Other aspects and advantages of this disclosure will become apparent from the following description, taken in conjunction with the accompanying drawings, illustrated by way of examples, the principles of the disclosure. An embodiment may provide other hardware configured to perform the methods of the invention, as well as software stored in a machine-readable medium (e.g., a tangible storage medium) to control devices to perform these methods. These and other features will be presented in more detail in the following description and the associated figures.
The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more example embodiments and, together with the description of example embodiments, serve to explain the principles and implementations.
In the drawings:
Embodiments are described herein in the context of reduced power consumption in a gaming device. The following detailed description is illustrative only and is not intended to be in any way limiting. Other embodiments will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts.
In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application, regulatory, 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 this disclosure, 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 power consumption control system, apparatus, and method to reduce power consumed by a gaming device are described. The reduction of electrical power consumed by one gaming device may result in the reduction of power consumed in a network of gaming devices. Although described with the use of gaming devices, this is not intended to be limiting as the power control system can be used to reduce power consumption in other fields such as in office lights (as described with reference to
Gaming device 102a-102n may be configured to reduce power consumption automatically or manually. If configured manually, an administrator may manually set a power state for each individual gaming device 102a-102n. In another embodiment, power management rules may be manually configured for each gaming device 102a-102n. The power management rules may be any rule that allocates or controls power provided to each component or peripheral in a gaming device 102a-102n. By providing full power to all peripherals and components of a gaming device 102a-102n, the gaming device may operate in an “Awake” or “On” power state. However, by adjusting or eliminating power supplied to certain peripherals of the gaming device, power consumption of the gaming device may be reduced thereby reducing the overall power consumption in a network of gaming devices.
Power consumption of the gaming device may also be controlled or configured automatically. The gaming devices 102a-102n may communicate with each other, via 104, to set the power states of the other gaming devices. Gaming device 102a may retrieve a power management or power control rule based on the power status information received from gaming device at 102b. The power management rule may be obtained from a power management database such as the power management module and rules database 246 of
Gaming device 102a may determine whether it should change or reconfigure its power state. The determination to adjust its power state may be based upon, for example, the current power state of gaming device 102a. For example, if the current power state of gaming device 102a is an “On” power state, but it must now be configured to operate in a “Hibernate” power state based on the power reconfiguration instructions received from gaming device 102b in the transmitted power status information, gaming device 102a may configure itself to operate in the “Hibernate” power state. In another example, if the current power state of gaming device 102a is a “Hibernate” power state, but it must now reconfigure itself to a “Light Sleep” power state based on the power reconfiguration instructions received from gaming device 102b in the transmitted power status information, gaming device 102a may configure itself to operate in the “Light Sleep” power state. In another example, if the current operating state of gaming device 102a is a “Hibernate” power state and must continue to operate in a “Hibernate” power state based on the power reconfiguration instructions received from gaming device 102b in the received power status information, then gaming device 102a need not adjust its power state. By configuring the gaming device to different power states, the power consumption of each gaming device may be optimized.
Gaming device 102a may then transmit its power status information to a plurality of other gaming devices 102b-102n. For example, if a gaming device was configured to operate in a “Hibernate” power state, the power status information transmitted to the plurality of other gaming device 102n may inform, via 104, the other gaming device 102n that not much activity is occurring and include power reconfiguration instructions for the other gaming device 102n to reconfigure their power states to a “Hibernate” power state. In another example, if gaming device 102a was instructed to operate in an “On” power state due to activity detected on or near gaming device 102b, the power status information transmitted, via 104, to the plurality of other gaming device 102n may inform the other gaming device 102n that patrons are nearby and have power reconfiguration instructions for the other gaming device 102n to reconfigure their power states to an “On” power state. In one embodiment, gaming device 102a may simply forward and transmit, via 104, the power status information received from gaming device 102b.
Determining which gaming device(s) to transmit the power status information may be based upon a propagation pattern stored in a power management database of the gaming device 102a-102n (e.g. power management module and rules database 246 of
In one example, a gaming device 102a-102n may be configured to operate at an “Awake” or “On” power state. The “On” power state of the gaming device 102a-102n may supply power to substantially all the peripherals in a gaming device 102a-102n. The “On” power state may be the power state at which gaming devices 102a-102n consumes their greatest power. In another example, a gaming device 102a-102n may be configured to operate in an “Off” power state whereby power may be supplied to a few peripherals a gaming device, such as the gaming device processor, memory, and security peripherals. In still another example, a gaming device 102a-102n may be configured to operate in a “Light Sleep” power state whereby power is supplied to less than substantially all the gaming device peripherals such that the gaming device may quickly be configured back to an “On” power state with very little wait time.
In use, gaming device 102a may transmit, via 104, power status information or power operating parameters to each of the other gaming devices 102b-n. In another embodiment, gaming device 102b may be configured to monitor or “ping”, via 104, each of the other gaming devices 102a, 102n for power status information. The power status information or power operating parameter may include any pertinent information such as triggering events, power state, power reconfiguration instruction, detected activity in the gaming environment and the like. For example, the power status information or power operating parameter may inform the other gaming device of the power state at which it is operating at. In another example, the power status information or power operating parameter may include information that the one or more gaming devices nearby detected movement 100 feet away and to instruct the other gaming devices nearby to reconfigure its power state to a “Light Sleep” or a “Wake Up” state.
Many different types of games, including mechanical slot games, video slot games, video poker, video black jack, video pachinko and lottery, may be provided with gaming devices of this invention. In particular, the gaming device 200 may be operable to provide many different instances of wagering games of chance. The type of game may be differentiated according to themes, sounds, graphics, type of game (e.g., slot game vs. card game), denomination, number of paylines, maximum jackpot, progressive or non-progressive, bonus games, and the like. The gaming device 200 may be operable to allow a player to select a game of chance to play from a plurality of wager games available on the gaming device. For example, the gaming device may provide a menu with a list of the wagering games that are available for play on the gaming device and a player may be able to select at least one of the wagering games that one wishes to play.
The gaming device 200 may include a top box 212 on top of the main cabinet 216. The top box 212 may house a number of devices, which may be used to add features to a game being played on the gaming device 200, such as speakers 222a-n, a ticket printer 220 which prints bar-coded or other types of tickets 224, a key pad 226 for entering player tracking information, a florescent display 208 for displaying player tracking information, a card reader 230 for entering a magnetic striped card containing player tracking information, and a display monitor 228. The ticket printer 220 may be used to print tickets for a cashless ticketing system. Further, the top box 212 may house different or additional devices than shown in
Gaming device 200 is but one example from a wide range of gaming device designs on which the present invention may be implemented. For example, not all suitable gaming devices have top boxes or player tracking features. Further, some gaming devices have only a single game display—mechanical or video, while others are designed for bar tables and have displays that face upwards. As another example, a game may be generated on a host computer and may be displayed on a remote terminal or a remote gaming device.
Some gaming devices may have different features and/or additional circuitry that differentiates them from general-purpose computers (e.g., desktop personal computers (PCs) and laptops). Gaming devices are highly regulated to ensure fairness and, in many cases, gaming devices are operable to dispense monetary awards of multiple millions of dollars. Therefore, to satisfy security and regulatory requirements in a gaming environment, hardware and software architectures may be implemented in gaming devices that differ significantly from those of general-purpose computers. A description of gaming devices relative to general-purpose computing machines and some examples of the additional (or different) components and features found in gaming devices are described below.
It may appear that adapting PC technologies to the gaming industry would be a simple proposition because both PCs and gaming devices employ microprocessors that control a variety of devices. However, because of such reasons as 1) the regulatory requirements that are placed upon gaming devices, 2) the harsh environment in which gaming devices operate, 3) security requirements and 4) fault tolerance requirements, adapting PC technologies to a gaming device can be quite difficult. Further, techniques and methods for solving a problem in the PC industry, such as device compatibility and connectivity issues, might not be adequate in the gaming environment. For instance, a fault or a weakness tolerated in a PC, such as security holes in software or frequent crashes, may not be tolerated in a gaming device because in a gaming device these faults can lead to a direct loss of funds from the gaming device, such as stolen cash or loss of revenue when the gaming device is not operating properly.
For the purposes of illustration, a few differences between PC systems and gaming systems will be described. A first difference between gaming devices and common PC based computers systems is that gaming devices are designed to be gaming state-based systems. In a gaming state-based system, the system stores and maintains its current gaming state and previous transactions history in a non-volatile memory, such that, in the event of a power failure or other malfunction the gaming device will return to its current gaming state when the power is restored. For instance, if a player was shown an award for a game of chance and, before the award could be provided to the player the power failed, the gaming device, upon the restoration of power, would return to the gaming state where the award is indicated. As is well known in the field, PCs are generally not gaming state machines and a majority of data is usually lost when a malfunction occurs. This requirement affects the software and hardware design on a gaming device.
A second important difference between gaming devices and common PC based computer systems is that for regulation purposes, the software on the gaming device used to generate the game of chance and operate the gaming device has been designed to be static and monolithic to prevent cheating by the operator of the gaming device. For instance, one solution that has been employed in the gaming industry to prevent cheating and satisfy regulatory requirements has been to manufacture a gaming device that can use a proprietary processor running instructions to generate the game of chance from an EPROM or other form of non-volatile memory. The coding instructions on the EPROM are static (non-changeable) and must be approved by gaming regulators in a particular jurisdiction and installed in the presence of a person representing the gaming jurisdiction. Any changes to any part of the software required to generate the game of chance, such as adding a new device driver used by the master gaming controller to operate a device during generation of the game of chance can require a new EPROM to be burned, approved by the gaming jurisdiction and reinstalled on the gaming device in the presence of a gaming regulator. Regardless of whether the EPROM solution is used, to gain approval in most gaming jurisdictions, a gaming device must demonstrate sufficient safeguards that prevent an operator or player of a gaming device from manipulating hardware and software in a manner that gives them an unfair and in some cases an illegal advantage. The gaming device should have a means to determine if the code it will execute is valid. If the code is not valid, the gaming device must have a means to prevent the code from being executed. The code validation requirements in the gaming industry affect both hardware and software designs on gaming devices.
A third important difference between gaming devices and common PC based computer systems is the variety of devices available for a PC may be greater than on a gaming device, gaming devices still have unique device requirements that differ from a PC, such as device security requirements not usually addressed by PCs. For instance, monetary devices, such as coin dispensers, bill acceptors and ticket printers and computing devices that are used to govern the input and output of cash to a gaming device have security requirements that are not typically addressed in PCs. Therefore, many PC techniques and methods developed to facilitate device connectivity and device compatibility do not address the emphasis placed on security in the gaming industry.
To address some of the issues described above, a number of hardware, software, and firmware components and architectures are utilized in gaming devices that are not typically found in general purpose computing devices, such as PCs. These components and architectures, as described below in more detail, include but are not limited to watchdog timers, voltage monitoring systems, gaming state-based software architecture and supporting hardware, specialized communication interfaces, security monitoring (e.g., various optical and mechanical interlocks) and trusted memory.
A watchdog timer may be used by some gaming devices to provide a software failure detection mechanism. In a normal gaming device operating system, the operating software periodically accesses control registers in the watchdog timer subsystem to “re-trigger” the watchdog. Should the operating software fail to access the control registers within a preset timeframe, the watchdog timer will timeout and generate a system reset. Typical watchdog timer circuits contain a loadable timeout counter register to allow the operating software to set the timeout interval within a certain range of time. A differentiating feature of the some preferred circuits is that the operating software cannot completely disable the function of the watchdog timer. In other words, the watchdog timer always functions from the time power is applied to the board.
In one embodiment, a gaming device may use several power supply voltages to operate portions of the computer circuitry. These may be generated in a central power supply or locally on the computer board. If any of these voltages falls out of the tolerance limits of the circuitry they power, unpredictable operation of the computer may result. Though most modern general-purpose computers include voltage monitoring circuitry, these types of circuits only report voltage status to the operating software. Out-of-tolerance voltages can cause software malfunction, creating a potential uncontrolled condition in the gaming computer. Some gaming devices may have power supplies with tighter voltage margins than that required by the operating circuitry. In addition, the voltage monitoring circuitry may have two thresholds of control. The first threshold generates a software event that can be detected by the operating software and an error condition is generated. This threshold is triggered when a power supply voltage falls out of the tolerance range of the power supply, but is still within the operating range of the circuitry. The second threshold is set when a power supply voltage falls out of the operating tolerance of the circuitry. In this case, the circuitry generates a reset, halting operation of the computer.
Some gaming devices may include a gaming state machine. Different functions of a game (bet, play, result, stages in the graphical presentation, credit and the like) may be defined as a gaming state. When a game moves from one gaming state to another, critical data regarding the game software is stored in a custom non-volatile memory subsystem. This is critical to ensure the player's wager and credits are preserved and to minimize potential disputes in the event of a malfunction on the gaming device.
In general, a gaming device does not advance from a first gaming state to a second gaming state until critical information that allows the first gaming state to be reconstructed is stored. This feature allows the game to recover operation to the current gaming state of play in the event of a malfunction, loss of power, and the like that occurred just prior to the malfunction. After the gaming state of the gaming device is restored during the play of a game of chance, game play may resume and the game may be completed in a manner that is no different than if the malfunction had not occurred. Typically, battery-backed random-access memory (RAM) devices are used to preserve this critical data although other types of non-volatile memory devices may be employed. These memory devices are not used in typical general-purpose computers.
As described in the preceding paragraph, when a malfunction occurs during a game of chance, the gaming device may be restored to a gaming state in the game of chance just prior to when the malfunction occurred. The restored gaming state may include metering information and graphical information that was displayed on the gaming device in the gaming state prior to the malfunction. For example, when the malfunction occurs during the play of a card game after the cards have been dealt, the gaming device may be restored with the cards that were previously displayed as part of the card game. As another example, a bonus game may be triggered during the play of a game of chance where a player is required to make a number of selections on a display monitor. When a malfunction has occurred after the player has made one or more selections, the gaming device may be restored to a gaming state that shows the graphical presentation at the time just prior to the malfunction, including an indication of selections that have already been made by the player. In general, the gaming device may be restored to any gaming state in a plurality of gaming states that occur in the game of chance that occurs while the game of chance is played or to gaming states that occur between the play of a game of chance.
Game history information regarding previous games played such as an amount wagered, the outcome of the game and so forth may also be stored in a non-volatile memory device. The information stored in the non-volatile memory may be detailed enough to reconstruct a portion of the graphical presentation that was previously presented on the gaming device and the gaming state of the gaming device (e.g., credits) at the time the game of chance was played. The game history information may be utilized in the event of a dispute. For example, a player may decide that in a previous game of chance that they did not receive credit for an award that they believed they won. The game history information may be used to reconstruct the gaming state of the gaming device prior, during and/or after the disputed game to demonstrate whether the player was correct or not in their assertion.
The gaming devices of the present invention may alternatively be treated as peripheral devices to a casino communication controller and connected in a shared daisy chain fashion to a single serial interface. In both cases, the peripheral devices are preferably assigned device addresses. If so, the serial controller circuitry must implement a method to generate or detect unique device addresses. General-purpose computer serial ports are not able to do this.
Security monitoring circuits or security components may be configured to detect intrusion into a gaming device of the present invention by monitoring security switches attached to access doors in the slot machine cabinet. Preferably, access violations result in suspension of game play and can trigger additional security operations to preserve the current gaming state of game play. These circuits also function when power is off by use of a battery backup. In power-off operation, these circuits continue to monitor the access doors and peripherals of the slot machine. When power is restored, the gaming device can determine whether any security violations occurred while power was off, e.g., via software for reading status registers. This can trigger event log entries and further data authentication operations by the slot machine software.
Trusted memory devices are preferably included in the gaming device to ensure the authenticity of the software that may be stored on less secure memory subsystems, such as mass storage devices. Trusted memory devices and controlling circuitry are typically designed to not allow modification of the code and data stored in the memory device while the memory device is installed in the slot machine. The code and data stored in these devices may include authentication algorithms, random number generators, authentication keys, operating system kernels, and the like. The purpose of these trusted memory devices is to provide gaming regulatory authorities a root trusted authority within the computing environment of the slot machine that can be tracked and verified as original. This may be accomplished via removal of the trusted memory device from the slot machine computer and verification of the secure memory device contents in a separate third party verification device. Once the trusted memory device is verified as authentic, and based on the approval of the verification algorithms contained in the trusted device, the gaming device is allowed to verify the authenticity of additional code and data that may be located in the gaming computer assembly, such as code and data stored on hard disk drives.
Mass storage devices used in a general purpose computer typically allow code and data to be read from and written to the mass storage device. In a gaming device environment, modification of the gaming code stored on a mass storage device is strictly controlled and would only be allowed under specific maintenance type events with electronic and physical enablers required. Though this level of security could be provided by software, gaming devices that include mass storage devices preferably include hardware level mass storage data protection circuitry that operates at the circuit level to monitor attempts to modify data on the mass storage device and will generate both software and hardware error triggers should a data modification be attempted without the proper electronic and physical enablers being present.
Returning to the example of
During the course of a game, a player may be required to make a number of decisions, which affect the outcome of the game. For example, a player may vary his or her wager on a particular game, select a prize for a particular game selected from a prize server, or make game decisions that affect the outcome of a particular game. The player may make these choices using the player-switches 206, the display monitor 204 or using some other device which enables a player to input information into the gaming device. In some embodiments, the player may be able to access various game services such as concierge services and entertainment content services using the display monitor 204 and one more input devices.
During certain game events, the gaming device 200 may display visual and auditory effects that can be perceived by the player. These effects add to the excitement of a game, which makes a player more likely to continue playing. Auditory effects include various sounds that are projected by the speakers 222a-n. Visual effects include flashing lights, strobing lights or other patterns displayed from lights on the gaming device 200 or from lights behind the belly glass 211. After the player has completed a game, the player may receive game tokens from the coin tray 210 or a ticket 224 from the printer 220, which may be used for further games or to redeem a prize. Further, the player may receive a ticket 224 for food, merchandise, other items, or even free or discounted games from the printer 220.
Processor 242 may be configured to manage power supplied to at least one of the peripheral devices and/or components of the gaming device. By managing the power supply to the peripherals and/or components of the gaming device, the amount of power consumed by the gaming device may be reduced and used efficiently. The processor 242 may be configured to manage power supply to the gaming device based on the power management rules set forth in the power management module and rules database 246.
The power management module and rules database 246 comprise a controller, volatile memory such as DRAM, and non-volatile memory such as EPROM, EEPROM, NVRAM, and/or solid state drives. It is connected to the gaming device's peripherals and may be configured to store data in a database. It may also be connected to the gaming device's controller board. Although illustrated with specific examples, it will know be known that other implementations may be used. For instance, the power management module may be implemented entirely by software, a field programmable gate array (FPGA), a programmable logic device (PLD), a custom application-specific integrated circuit (ASIC), or some combinations of these.
The power management module and rules database 246 may store various power states 266. The power states 266 may include, for example, an “On” or “Awake”, “Off”, “Light Sleep”, and/or “Hibernate” power states. Each power state may be defined, for example, by the number of peripherals or components to which power is supplied or denied, the allocation of power to each peripheral or component, and any other criteria.
When configured to operate in an “On” power state, power may be supplied to substantially all gaming components and peripherals of the gaming device. As such, when configured to an “On” power state, the gaming device may consume the most power. When configured to operate in an “Off” power state, the gaming device 200 may be configured to limit or withhold power to substantially all components and peripheral devices of the gaming device except for a few essential components, such as the processor 242, security components 250, memory 244, and any other necessary components or peripheral devices. When operating in the “Off” power state, the gaming device may use the least amount of power.
When configured to operate in a “Light Sleep” power state, power may be supplied to substantially all gaming components and peripherals of the gaming device except for a few peripherals. In one embodiment, a limited amount of power may be supplied to the at least one display monitor and touch screen 240. That is, the duty cycle of the supplied power is reduced to less than 100%. For example, power may be supplied to the at least one display monitor and touch screen 240 in predetermined time intervals and at a high enough frequency or duty cycle (e.g., modulate the voltage pulse width to 80% at 60 Hz frequency for a display that normally refreshes at 120 Hz on full power) such that a player would not notice that the at least one display monitor and touch screen 240 was not receiving full power. As such, the display monitor and touch screen 240 may appear to be turned on, yet less power is supplied to the display monitor and touch screen 240. In another embodiment, a limited amount of power may be supplied to the plurality of player input switches or buttons 256. In still another embodiment, a limited amount of power may be supplied to both the at least one display monitor and touch screen 240, the plurality of player input switches or buttons 256, and the information panel 260. This may provide the appearance that the gaming device is fully functioning if a player wanted to play a wagering game on the gaming device. Additionally, it allows for the display or presentation of information that may lure the player to play the gaming device 200. For example, a poker themed gaming device may display information about an upcoming poker tournament on the information panel 260 to entice the player to play the gaming device. When operating in a “Light Sleep” power state, the gaming device may use less power than operating in an “On” power state, but more power than operating in an “Off” power state. Additionally, only a limited amount of power and time is required for the gaming device to be configured from the “Light Sleep” power state to be fully functioning in an “On” power state. For example, a gaming device operating in an “Off” power state may require approximately 10 minutes to reconfigure itself to an “On” power state (e.g., full O/S reboot and authentication of gaming software) whereas a gaming device operating in a “Light Sleep” power state may require approximately thirty seconds to reconfigure itself to an “On” power state.
Attenuating the duty cycle of the power supplied to the devices and peripherals often work very well without diminishing their performance. However, it may not be necessary in some cases. Many of today's advanced devices and peripherals such as displays, touch screens, printers, power supply, processors, fans, Wifi controller, Bluetooth controller, and the like have built-in processing power and intelligence to simply take high-level commands from a master controller (e.g., the gaming device's CPU board, the gaming device's power management controller, and the like.). In one example, the gaming device's controller can send a high-level command “Go To Sleep” to a smart printer to put it in a lower power mode. In one implementation, a hybrid approach can be taken by having both the power attenuation and high-level commands capabilities. In this implementation, the gaming device's power management controller can be designed to have both the hardware for a switching power supply connecting to duty-cycle controlled peripherals, and one or more communication buses (wired or wireless) connecting to smart peripherals and devices.
When configured to operate in a “Hibernate” power state, more power may be supplied to more gaming device peripherals and/or components than operating in the “Off” power state, but less power may be supplied to less gaming device peripherals and/or components than operating in the “Light Sleep” power state. In one embodiment, the gaming device may be configured to operate in the “Hibernate” power state if it is not used within a predetermined amount of time. As such, power to substantially all gaming device peripherals and components may be withheld to conserve energy. In one embodiment, power may be limited or withheld to substantially all components and peripheral devices of the gaming device except for a few essential components, such as the processor 242, security components 250, memory 244, and any other desired components or peripheral devices.
As previously discussed, some smart devices and peripherals can take high-level commands over a communication bus to change their power-operating mode. For instance, when operating in the “Hibernate” power state, the gaming device's power management controller and rules database 246 may send a command “Go To Sleep” to the Wifi controller to put it in a lower power mode.
Triggering events 264 may be stored in the power management module and rules database 246. The triggering events 264 may be any predefined triggering event such as motion detected by at least one of the activity monitoring device 252. The activity monitory device 252 may be any known detection device such as, but not limited to a motion sensor, a camera, a pressure sensor, a metal detector, and the like. The activity monitoring device 252 may be configured to detect activities proximate to the gaming device in the gaming environment, such as patrons walking in close proximity to the gaming device, detecting motion on the player input buttons or switches of the gaming device, detecting motion on the display of the gaming device, and any other type of motion or activity. As such, the triggering events 264 may include, but is not limited to, input from a player input button, a breach in a security component, non-activity for a predetermined time period (i.e. 30 minutes, 1 hour, 3 hours, and the like), detection of motion 100 feet away from the gaming device, detection of motion 25 feet away from the gaming device or a group of gaming devices, and the like.
Based on the triggering event 264, the gaming device may be configured to assume a particular power state 266. The particular power state 266 may be configured to manage power based on various power management rules 268. Although illustrated with specific examples, it will now be known that different power management rules 268 may be utilized. For example, when configured to assume a “Hibernate” power state, the gaming device may be configured to supply power to the security components 250, processor 242, and memory 244. In another example, when configured to assume a “Light Sleep” power state, the gaming device may be configured to supply power to the security components 250, processor 242, memory 244, display and touch screen 240, player input buttons 256, and information panel 260.
The power management module and rules database 246 may also store predefined propagation patterns 270. As discussed above in
Table 1 illustrates example data that may be stored in the power management module and rules database 246.
The power states may include, for example, an “On” or “Awake”, “Off”, “Light Sleep”, and/or “Hibernate” power states. Each power states may be defined, for example, by the number of peripherals or components to which power is supplied or denied, the allocation of power to each peripheral or component, and any other criteria.
When configured to operate in an “On” power state, power may be supplied to substantially all gaming components and peripherals of the gaming device. As such, when configured to an “On” power state, the gaming device may consume the most power. When configured to operate in an “Off” power state, the gaming device 200 may be configured to limit or withhold power to substantially all components and peripheral devices of the gaming device except for a few essential components, such as the processor, security components, and any other desired components or peripheral devices. When operating in the “Off” power state, the gaming device may use the least amount of power.
When configured to operate in a “Light Sleep” power state, power may be supplied to substantially all gaming components and peripherals of the gaming device except for a few peripherals. In one embodiment, a limited amount of power may be supplied to the at least one display monitor. For example, power may be supplied to the at least one display monitor in predetermined time intervals and at a high enough frequency or duty cycle (e.g., modulate the voltage pulse width to 80% at 60 Hz frequency for a display that normally refreshes at 120 Hz on full power) such that a player would not notice that at least one display monitor was not receiving full power. As such, the display monitor may appear to be turned on, yet less power is supplied to the display monitor. In another embodiment, a limited amount of power may be supplied to the plurality of player input switches or buttons. In still another embodiment, a limited amount of power may be supplied to both the at least one display monitor, the plurality of player input switches or buttons, and the information panel. This may provide the appearance that the gaming device is fully functioning if a player wanted to play a wagering game on the gaming device. Additionally, it allows for the display or presentation of information that may lure the player to play the gaming device. For example, a poker themed gaming device may display information about an upcoming poker tournament on the information panel to entice the player to play the gaming device. When operating in a “Light Sleep” power state, the gaming device may use less power than operating in an “On” power state, but more power than operating in an “Off” power state. Additionally, only a limited amount of power and time is required for the gaming device to be configured from the “Light Sleep” power state to be fully functioning in an “On” power state. For example, a gaming device operating in an “Off” power state may require approximately 10 minutes to reconfigure itself to an “On” power state (full operating system reboot and gaming software authentication) whereas a gaming device operating in a “Light Sleep” power state may require approximately 30 seconds to reconfigure itself to an “On” power state.
Attenuating the duty cycle of the power supplied to the devices and peripherals often work very well without diminishing their performance. However, it may not be necessary in some cases. Many of today's advanced devices and peripherals such as displays, touch screens, printers, power supply, processors, fans, Wifi controller, Bluetooth controller, and the like have built-in processing power and intelligence to simply take high-level commands from a master controller (e.g., the gaming device's CPU board, the gaming device's power management controller, and the like). In one example, the gaming device's controller can send a high-level command “Go To Sleep” to a smart printer to put it in a lower power mode. In one implementation, a hybrid approach can be taken by having both the power attenuation and high-level commands capabilities. In this implementation, the gaming device's power management controller can be designed to have both the hardware for a switching power supply connecting to duty-cycle controlled peripherals, and one or more communication buses (wired or wireless) connecting to smart peripherals and devices.
When configured to operate in a “Hibernate” power state, power may be supplied to more gaming device peripherals and/or components than operating in the “Off” power state, but substantially less gaming device peripherals and/or components than operating in the “Light Sleep” power state. In one embodiment, the gaming device may be configured to operate in the “Hibernate” power state if it is not used within a predetermined amount of time. As such, power to substantially all gaming device peripherals and components may be withheld to conserve energy. In one embodiment, power may be limited or withheld to substantially all components and peripheral devices of the gaming device except for a few essential components, such as the processor, security components, memory, and any other components or peripheral devices.
As previously discussed, some smart devices and peripherals can take high-level commands over a communication bus to change their power-operating mode. For instance, when operating in the “Hibernate” power state, the gaming device's power management controller and rules database 246 may send a command “Go To Sleep” to the Wifi controller to put it in a lower power mode.
Triggering events may be stored in the power management module and rules database. The triggering events may be any predefined triggering event such as motion detected by at least one of the activity monitoring devices. The activity monitory device may be any known detection device such as, but not limited to a motion sensor, a camera, a pressure sensor, a metal detector, and the like. The activity monitoring device may be configured to detect activities proximate to the gaming device in the gaming environment, such as patrons walking in close proximity to the gaming device, detecting motion on the player input buttons or switches of the gaming device, detecting motion on the display of the gaming device, and any other type of motion or activity. As such, the triggering events may include, but is not limited to, input from a player input button, a breach in a security component, non-activity for a predetermined time period (i.e. 30 minutes, 1 hour, 3 hours, and the like), detection of motion 100 feet away from the gaming device, detection of motion 25 feet away from the gaming device, and the like.
Based on the triggering event, the gaming device may be configured to assume a particular power state. The particular power state may be configured to manage power based on various power management rules. Although illustrated with specific examples, it will now be known that different power management rules may be utilized. For example, when configured to assume a “Hibernate” power state, the gaming device may be configured to supply power to the security components, processor, and memory. In another example, when configured to assume a “Light Sleep” power state, the gaming device may be configured to supply power to the security components, processor, memory, display, player input buttons, and information panel.
Based on the information received from the secondary gaming device at 302, the primary gaming device may obtain a power management or power control rule from a power management database (e.g. the power management module and rules database 246 of
If it is determined that the primary gaming device should adjust its power state at 306, the power state of the primary gaming device may be changed or configured at 308. The determination to adjust its power state may be based upon, for example, the current power state of the primary gaming device. For example, if the primary gaming device was operating at an “On” power state and must now change to a “Hibernate” power state based on the power status information received from the secondary gaming device, the primary gaming device may configure itself to operate in the “Hibernate” power state. In another example, if the primary gaming device was operating at a “Hibernate” power state and must now change to a “Light Sleep” power state based on the power status information received from the secondary gaming device, the primary gaming device may configure itself to operate in the “Light Sleep” power state. In another example, if the primary gaming device was operating at a “Hibernate” power state and, based on the power status information received from the secondary gaming device, must remain in the “Hibernate” power state, the primary gaming device need not adjust its power state at 306. By configuring the gaming device to different power states, the power consumption of the gaming device may be optimized and thus reduce operation costs.
Once the primary gaming device receives a power status information transmission from the secondary gaming device at 404, the primary gaming device may retrieve a power management or power control rule based on the power status information received from the secondary gaming device at 406. The power management rule may be obtained from a power management database such as the power management module and rules database 246 of
If it is determined that the primary gaming device should adjust its power state at 408, the power state of the primary gaming device may be changed or configured at 410. The determination to adjust its power state may be based upon, for example, the current power state of the primary gaming device. For example, if the current power state of the primary gaming device is an “On” power state, but it must now be configured to operate in a “Hibernate” power state based on the power reconfiguration instructions received from the secondary gaming device in the transmitted power status information, the primary gaming device may configure itself to operate in the “Hibernate” power state. In another example, if the current power state of the primary gaming device is a “Hibernate” power state, but it must now reconfigure itself to a “Light Sleep” power state based on the power reconfiguration instructions received from the secondary gaming device in the transmitted power status information, the primary gaming device may configure itself to operate in the “Light Sleep” power state. In another example, if the current operating state of the primary gaming device is a “Hibernate” power state and must continue to operate in a “Hibernate” power state based on the power reconfiguration instructions received from the secondary gaming device in the received power status information, then the primary gaming device need not adjust its power state at 408. By configuring the gaming device to different power states, the power consumption of the gaming device may be optimized and thus reduce operation costs.
The primary gaming device may then transmit its power status information to a plurality of other gaming devices at 412. For example, if the primary gaming device was configured to operate in a “Hibernate” power state, the power status information transmitted to the plurality of other gaming devices may inform the other gaming devices that not much activity is occurring and include power reconfiguration instructions for the other gaming devices to reconfigure their power states to a “Hibernate” power state. In another example, if the primary gaming device was instructed to operate in an “On” power state due to activity detected on the secondary gaming device, the power status information transmitted to the plurality of other gaming devices may inform the other gaming devices that patrons are nearby and have power reconfiguration instructions for the other gaming devices to reconfigure their power states to an “On” power state. In one embodiment, the primary gaming device may simply forward and transmit the power status information received from the secondary gaming device.
Determining where to transmit the power status information may be based upon a propagation pattern stored in a power management database of the primary gaming device (e.g. power management module and rules database 246 of
In one embodiment, the primary gaming device may receive a response from the secondary gaming device or the plurality of other gaming devices at 414. For example, the response may be a confirmation of receipt of the power status information transmitted from the primary gaming device. In another example, the response may be a confirmation that the secondary gaming device and/or the plurality of other gaming devices reconfigured their power states as instructed by the primary gaming device. In yet another example, the response may be that one of the other gaming devices has not detected any motion for several hours and will not reconfigure itself to an “On” power status as instructed by the primary gaming device.
The primary gaming device may retrieve a power management or power control rule at 504 based on the power status information received from the secondary gaming device. The power management rule may be obtained from a power management database such as the power management module and rules database 246 of
If it is determined that the primary gaming device should adjust its power state at 506, the power state of the primary gaming device may be changed or configured at 508. The determination to adjust its power state may be based upon, for example, the current power state of the primary gaming device. For example, if the current power state of the primary gaming device is an “On” power state, but it must now be configured to operate in a “Hibernate” power state based on the power reconfiguration instructions received from the secondary gaming device in the transmitted power status information, the primary gaming device may configure itself to operate in the “Hibernate” power state. In another example, if the current power state of the primary gaming device is a “Hibernate” power state, but it must now reconfigure itself to a “Light Sleep” power state based on the power reconfiguration instructions received from the secondary gaming device in the transmitted power status information, the primary gaming device may configure itself to operate in the “Light Sleep” power state. In another example, if the current operating state of the primary gaming device is a “Hibernate” power state and must continue to operate in a “Hibernate” power state based on the power reconfiguration instructions received from the secondary gaming device in the received power status information, then the primary gaming device need not adjust its power state at 408. By configuring the gaming device to different power states, the power consumption of the gaming device may be optimized and thus reduce operation costs.
A propagation pattern may be obtained or retrieved at 510. In one implementation, the propagation pattern may be obtained from the transmitting gaming device (e.g., the secondary gaming device). The propagation pattern may be stored in a power management database of the primary gaming device (e.g. power management module and rules database 246 of
Once the propagation pattern is obtained or retrieved at 510, the primary gaming device may determine the power state for each gaming device in the propagation pattern at 512. In one example, the primary gaming device may ping the other gaming devices for power status information. In another embodiment, the other gaming devices in the propagation pattern may be configured to transmit power status information to the primary gaming device at predefined time intervals, such as every hour. In yet another implementation, the primary gaming device (the source) may forward its power state to other gaming devices in the propagation pattern, and let the receiving gaming devices determine their own power setting according to their own rules.
Once the power state of each gaming device is determined at 512, the primary gaming device may transmit power reconfiguration instructions to the gaming devices that need to be reconfigured at 514. For example, the secondary gaming device may have instructed the primary gaming device to reconfigure itself to an “On” power state because the second gaming device detected patrons in close proximity to the bank of gaming devices (e.g. within approximately 100-200 feet away from the bank of gaming devices). Thus, the primary gaming device may transmit a power reconfiguration instruction to any other gaming devices that are not already in an “On” power state. In another example, the secondary gaming device may have instructed the primary gaming device to reconfigure itself to a “Light Sleep” power state because the second gaming device detected no activity for 30 minutes. Thus, the primary gaming device may transmit a power reconfiguration instruction to any other gaming devices in the propagation pattern that are not in a “Light Sleep” power state.
In one embodiment, the boundary gaming devices 604 may be configured to not respond to any power reconfiguration instructions received in a power status information. This may prevent boundary gaming devices 604 from shutting down and/or have an appearance of being turned off. Since the boundary gaming devices 604 are exposed to patrons walking along the walkway 606, they are more likely to be played compared to the other gaming devices 602 and need to constantly be maintained in an “On” power state.
As illustrated in
The power status information may include any pertinent information such as triggering events, power state as discussed above, power reconfiguration instruction, detected activity in the gaming environment, and the like. For example, the power status information may inform the primary gaming device 602′ the power state at which the secondary gaming device 602″ is operating at. In another example, the power status information may include information that the secondary gaming device 602″ detected patron 650 movement 100 feet away (or in close proximity to the secondary gaming device 602″) and include power reconfiguration instructions instructing the primary gaming device 602′ to reconfigure its power state to a “Light Sleep” state.
The primary gaming device 602′ may retrieve a power management or power control rule based on the power status information received from the secondary gaming device 602″. The power management rule may be obtained from a power management database such as the power management module and rules database 246 of
If it is determined that the primary gaming device 602′ should adjust its power state, the power state of the primary gaming device 602′ may be changed or reconfigured. The determination to adjust its power state may be based upon, for example, the current power state of the primary gaming device 602′. For example, if the current power state of the primary gaming device 602′ is an “On” power state, but it must now be configured to operate in a “Hibernate” power state based on the power reconfiguration instructions received from the secondary gaming device 602″ in the transmitted power status information, the primary gaming device 602′ may configure itself to operate in the “Hibernate” power state. In another example, if the current power state of the primary gaming device 602′ is a “Hibernate” power state, but it must now reconfigure itself to a “Light Sleep” power state based on the power reconfiguration instructions received from the secondary gaming device 602″ in the transmitted power status information, the primary gaming device 602′ may configure itself to operate in the “Light Sleep” power state. In another example, if the current operating state of the primary gaming device 602′ is a “Hibernate” power state and must continue to operate in a “Hibernate” power state based on the power reconfiguration instructions received from the secondary gaming device 602″ in the received power status information, then the primary gaming device 602′ need not adjust its power state. By configuring the gaming device to different power states, the power consumption of the gaming device may be optimized, thus reduce operating costs.
The primary gaming device 602′ may have a propagation pattern stored in a power management database (such as the power management module and rules database 246 of
Once the propagation pattern is obtained or retrieved, the primary gaming device 602′ may transmit its power status information to a plurality of other gaming devices 602′″ in the propagation pattern as illustrated in
In another embodiment, the primary gaming device 602′ may determine the power state for each of the other gaming devices 602′″ in the propagation pattern B. In one example, the primary gaming device 602′ may ping the other gaming devices 602′″ for power status information. In another embodiment, the other gaming devices 602′ in the propagation pattern B may be configured to transmit power status information to the primary gaming device 602′ at predefined time intervals, such as every ten minutes, every hour, and the like.
Once the power states of each gaming device 602′ is determined, the primary gaming device 602′ may transmit power reconfiguration instructions to the other gaming devices 602′″ that need to be reconfigured. For example, the secondary gaming device 602″ may have instructed the primary gaming device 602′ to reconfigure itself to an “On” power state because the second gaming device 602″ detected patrons in close proximity to the bank of gaming devices B (e.g. within approximately 100-200 feet away from the bank of gaming devices). Thus, the primary gaming device 602′ may transmit a power reconfiguration instruction to any other gaming devices 602′″ that are not in an “On” power state. In another example, the secondary gaming device 602″ may have instructed the primary gaming device 602′ to reconfigure itself to a “Light Sleep” power state because the second gaming device 602″ detected no activity for 30 minutes. Thus, the primary gaming device 602′ may transmit a power reconfiguration instruction to any other gaming devices 602′″ in the propagation pattern B that are not in a “Light Sleep” power state.
Lighting devices 702a-n may be lighting used for any number of applications such as lights attached to an interior or exterior of an establishment building, touchier lights in the offices, desk lamps, and the like. Additionally, each lighting device may have at least one bulb, at least one light emitting diode, or any other number and type of lighting emitting device. The establishment may be any establishment utilizing lighting device such as an office building, casino, grocery store, mall, and the like. In one embodiment, lighting devices 702a-n may communicate with each other and the establishment server 706 via network 704 in a wireless manner. In another embodiment, lighting devices 702a-n may communicate with each other and the establishment server 706 via network 704 using any known wired technique such as an Ethernet connection and the like.
Establishment server 706 may have a memory 708 including a power management database 710. The power management database 710 may be configured to store various data. Although illustrated with the power management database 710 stored in the establishment server 706, the power management database 710 may also be stored in the lighting devices 702a-702n (not shown). Additionally, although illustrated with specific examples, that other data may be stored in the power management database 710. The power management database 710 may store various power states. The power states may include, for example, an “On” or “Awake”, “Off”, “Light Sleep”, and/or “Hibernate” power states. Each power state may be defined, for example, by triggering events, allocation of power to each lighting device (e.g. power management rules), and any other criteria.
When configured to operate in an “On” power state, full power may be supplied to the lighting device. As such, when configured to an “On” power state, the lighting device may consume the most power. When configured to operate in an “Off” power state, no power may be supplied to the lighting device. Thus, when operating in the “Off” power state, the lighting device uses the least amount of power.
When configured to operate in a “Light Sleep” power state, a predefined amount of power may be supplied to the lighting device. For example, the lighting device may be configured to receive or use half the voltage and/or current. Thus, the lighting device may operate at half the power than when operating in the “On” power state. To a player, the lighting device may appear to be dimmed. When operating in a “Light Sleep” power state, the lighting device may use less power than operating in an “On” power state, but more power than operating in an “Off” power state. Additionally, only a limited amount of power and time is required for the lighting device to be configured from the “Light Sleep” power state to be fully functioning in an “On” power state. For example, a lighting device operating in an “Off” power state may require approximately 10 seconds to reconfigure itself to an “On” power state whereas a lighting device operating in a “Light Sleep” power state may require approximately 0.5-2 seconds to reconfigure itself to an “On” power state.
When configured to operate in a “Hibernate” power state, more power may be supplied to the lighting device than when operating in the “Off” power state, but less power than operating in the “Light Sleep” power state. In one embodiment, the lighting device may be provided with ¼ of the amount of power than operating in the “On” power state to conserve energy. The lighting device may be configured to operate in the “Hibernate” power state if it is not used within a predetermined amount of time. When operating in the “Hibernate” power state, the lighting device may also appeared to be dimmed similar to operating in the “Light Sleep” power state. However, the lighting device will appear to be more dimmed when operating in the “Hibernate” power state than in the “Light Sleep” power state.
Triggering events may also be stored in the power management database 710. The triggering events may be any predefined triggering event such as motion detected by at least one activity monitoring device 718a-n, a predetermined lighting schedule, lighting regulation compliance, and the like. The activity monitory device 718a-n may be any known detection device such as, but not limited to a motion sensor, a camera, a pressure sensor, a metal detector, and the like. The activity monitoring device 718a-n may be configured to detect activities proximate to the lighting device in the establishment, such as patrons walking in close proximity to the lighting device, detecting motion of a door, detecting pressure on the floor around the lighting device, detecting motion on a switch for the lighting device, and any other type of motion or activity. As such, the triggering events may include, but is not limited to, input from a player switch, non-activity for a predetermined time period (i.e. 30 minutes, 1 hour, 3 hours, and the like), detection of motion 100 feet away from the lighting device, detection of motion 25 feet away from the lighting device, and the like. Based on the triggering event, the establishment server may configure the lighting devices 702a-n to assume or operate in a particular power state.
Power management rules may also be stored in the power management database 710. Power management rules may be any power rules allocating the amount of power to the lighting devices 702a-n based on the triggering event. For example, if the triggering event was input from a player switch detected by the activity monitoring device 718a, the power management rule may instruct the lighting device 702a to operate in an “On” power state. In another example, if the triggering event was the detection of motion within 100 feet of the lighting device 702b by activity monitoring device 718b, then the power management rule may instruct the lighting device 702b to operate in a “Light Sleep” power state.
The power management database may also store predefined propagation patterns similar to the propagation patterns discussed above with reference to
In one embodiment, in use, the establishment server 706 may receive power status information from each of the lighting device 702a-n. Based on the power status information received from each lighting device 702a-n, the establishment server 706 may transmit a response including power reconfiguration instructions instructing lighting device 702a to power itself to a certain power state as discussed above. The response may also include instructions to propagate and transmit the power reconfiguration instruction to other lighting devices 702b-n.
In another embodiment, lighting device 702a may be configured to control power to itself and to the other lighting devices 702b-n. For example, lighting device 702a may determine that activity monitoring device 718a did not detect any motion for 30 minutes and based on the power management rules, needs to reconfigure itself to a “Light Sleep” power state. Lighting device 702a may then, based on the predefined propagation pattern, transmit a power status information to a neighboring lighting device 702b. The power status information transmitted to the neighboring lighting device 702b may include information that no activity was detected for 30 minutes and power reconfiguration instructions to configure lighting device 702b to a “Light Sleep” power state. In one embodiment, the power status information may also include propagation instructions for lighting device 702b to transmit the power reconfiguration instructions to other lighting devices 702n in the propagation pattern.
As illustrated in
In another embodiment, lighting device 802′ may automatically reconfigure their power states. Light devices 802′ may retrieve or determine a power control rule (stored in a power management rules database 710 in
Referring now to
As discussed above, activity monitory device 812 may be any known presence or proximity detection device 812. For instance, when player 850 steps into location 804n, pressure may be detected on the presence detection device 812 from the weight of the player 850. The detection of pressure may be transmitted to lighting device 810. In one embodiment, power status information may be transmitted to the officer server. In another embodiment, the lighting device 810 may retrieve power control rules to determine which state it should be operating at. For example, the power control rule may instruct the lighting device 810 to operate in an “On” power state if pressure was detected at the pressure detection device 812.
In another embodiment, lighting device 804n may transmit a power status information to lighting device 802 including information that the player entered office 804n and to instruct the lighting device 802 to configure itself to an “Off” power state. In another embodiment, lighting device 804n may transmit a power status information to establishment server including information that the player entered office 804n and that it configured itself to an “On” power state. In response to the power status information received from lighting device 810, the establishment server may transmit power reconfiguration instructions to the other lighting devices 802, 802′, 802″ to operate in an “Off” power state.
It will be apparent to one skilled in the art that the present description may be practiced without some or all of the specific details described herein. The preceding examples, illustrations, and contexts should not be taken as definitive or limiting either in scope or setting. Although these embodiments are described in sufficient detail to enable one skilled in the art to practice the described embodiments, these examples, illustrations, and contexts are not limiting, and other embodiments may be used and changes may be made without departing from the spirit and scope of the disclosure. For example, although the descriptions above described a network of gaming devices and office lighting devices, this is not intended to be limiting, as the invention may be used in other types of environments and devices such as air conditioning systems, lighting display systems in a department store or warehouse, networked computers in an office building, street lights, and the like.
While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein. For example, the power management database may include the quantity of power to be supplied to each peripheral, component, and/or device based upon the power state.
This application is a continuation of U.S. application Ser. No. 13/557,063, filed Jul. 24, 2012, and entitled “OPTIMIZED POWER CONSUMPTION IN A GAMING DEVICE,” which is hereby incorporated herein by reference.
| 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 |
| 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 | Beni 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 |
| 7243104 | Bill | Jul 2007 | B2 |
| 7247098 | Bradford et al. | Jul 2007 | B1 |
| 7259718 | Patterson et al. | Aug 2007 | B2 |
| 7275989 | Moody | Oct 2007 | B2 |
| 7285047 | Gielb et al. | Oct 2007 | B2 |
| 7311608 | Danieli | Dec 2007 | B1 |
| 7314408 | Cannon et al. | Jan 2008 | B2 |
| 7316615 | Soltys et al. | Jan 2008 | B2 |
| 7316619 | Nelson | Jan 2008 | B2 |
| 7318775 | Brosnan et al. | Jan 2008 | B2 |
| 7326116 | O'Donovan et al. | Feb 2008 | B2 |
| 7330108 | Thomas | Feb 2008 | B2 |
| 7346358 | Wood et al. | Mar 2008 | B2 |
| 7355112 | Laakso | Apr 2008 | B2 |
| 7384338 | Rothschild et al. | Jun 2008 | B2 |
| 7387571 | Walker et al. | Jun 2008 | B2 |
| 7393278 | Gerson et al. | Jul 2008 | B2 |
| 7396990 | Lu et al. | Jul 2008 | B2 |
| 7415426 | Williams et al. | Aug 2008 | B2 |
| 7425177 | Rodgers et al. | Sep 2008 | B2 |
| 7427234 | Soltys et al. | Sep 2008 | B2 |
| 7427236 | Kaminkow et al. | Sep 2008 | B2 |
| 7427708 | Ohmura | Sep 2008 | B2 |
| 7431650 | Kessman | Oct 2008 | B2 |
| 7448949 | Kaminkow et al. | Nov 2008 | B2 |
| 7500913 | Baerlocher | Mar 2009 | B2 |
| 7510474 | Carter | Mar 2009 | B2 |
| 7513828 | Nguyen et al. | Apr 2009 | B2 |
| 7519838 | Suurballe | Apr 2009 | B1 |
| 7559838 | Walker et al. | Jul 2009 | B2 |
| 7563167 | Walker et al. | Jul 2009 | B2 |
| 7572183 | Olivas et al. | Aug 2009 | B2 |
| 7585222 | Muir | Sep 2009 | B2 |
| 7602298 | Thomas | Oct 2009 | B2 |
| 7607174 | Kashchenko et al. | Oct 2009 | B1 |
| 7611409 | Muir et al. | Nov 2009 | B2 |
| 7637810 | Amaitis et al. | Dec 2009 | B2 |
| 7644861 | Alderucci et al. | Jan 2010 | B2 |
| 7653757 | Fernald et al. | Jan 2010 | B1 |
| 7693306 | Huber | Apr 2010 | B2 |
| 7699703 | Muir et al. | Apr 2010 | B2 |
| 7722453 | Lark et al. | May 2010 | B2 |
| 7758423 | Foster et al. | Jul 2010 | B2 |
| 7771271 | Walker et al. | Aug 2010 | B2 |
| 7780529 | Rowe et al. | Aug 2010 | B2 |
| 7780531 | Englman et al. | Aug 2010 | B2 |
| 7785192 | Canterbury et al. | Aug 2010 | B2 |
| 7811172 | Asher et al. | Oct 2010 | B2 |
| 7819749 | Fish | Oct 2010 | B1 |
| 7822688 | Labron | Oct 2010 | B2 |
| 7828652 | Nguyen et al. | Nov 2010 | B2 |
| 7828654 | Carter | Nov 2010 | B2 |
| 7828661 | Fish | Nov 2010 | B1 |
| 7850528 | Wells | Dec 2010 | B2 |
| 7874919 | Paulsen et al. | Jan 2011 | B2 |
| 7877798 | Saunders et al. | Jan 2011 | B2 |
| 7883413 | Paulsen | Feb 2011 | B2 |
| 7892097 | Muir et al. | Feb 2011 | B2 |
| 7909692 | Nguyen et al. | Mar 2011 | B2 |
| 7909699 | Parrott et al. | Mar 2011 | B2 |
| 7918728 | Nguyen et al. | Apr 2011 | B2 |
| 7927211 | Rowe et al. | Apr 2011 | B2 |
| 7927212 | Hedrick et al. | Apr 2011 | B2 |
| 7951008 | Wolf et al. | May 2011 | B2 |
| 8057298 | Nguyen et al. | Nov 2011 | B2 |
| 8057303 | Rasmussen | Nov 2011 | B2 |
| 8087988 | Nguyen et al. | Jan 2012 | B2 |
| 8117608 | Slettehaugh | Feb 2012 | B1 |
| 8133113 | Nguyen | Mar 2012 | B2 |
| 8182326 | Speers et al. | May 2012 | B2 |
| 8210927 | Hedrick | Jul 2012 | B2 |
| 8221245 | Walker | Jul 2012 | B2 |
| 8226459 | Barrett | Jul 2012 | B2 |
| 8226474 | Nguyen et al. | Jul 2012 | B2 |
| 8231456 | Zielinski | Jul 2012 | B2 |
| 8235803 | Loose et al. | Aug 2012 | B2 |
| 8282475 | Nguyen et al. | Oct 2012 | B2 |
| 8323099 | Durham | 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 |
| 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 | Nguyen | Nov 2016 | B2 |
| 9486704 | Nguyen | 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 |
| 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 |
| 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 |
| 20020167536 | Valdes et al. | Nov 2002 | A1 |
| 20020183105 | Cannon et al. | Dec 2002 | A1 |
| 20030001338 | Bennett et al. | 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 |
| 20040127277 | Walker | Jul 2004 | A1 |
| 20040127290 | Walker et al. | Jul 2004 | A1 |
| 20040137987 | Nguyen et al. | Jul 2004 | A1 |
| 20040147308 | Walker et al. | Jul 2004 | A1 |
| 20040152508 | Lind | Aug 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 |
| 20050137014 | Vetelaninen | Jun 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 |
| 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 |
| 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 |
| 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 |
| 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 | Kelly et al. | Dec 2008 | A1 |
| 20080305865 | Kelly et al. | Dec 2008 | A1 |
| 20080305866 | Kelly et al. | Dec 2008 | A1 |
| 20080311994 | Amaitas et al. | Dec 2008 | A1 |
| 20080318669 | Buchholz | Dec 2008 | A1 |
| 20080318686 | Crowder et al. | Dec 2008 | A1 |
| 20090005165 | Arezina et al. | Jan 2009 | A1 |
| 20090011822 | Englman | Jan 2009 | A1 |
| 20090029766 | Lutnick et al. | Jan 2009 | A1 |
| 20090054149 | Brosnan et al. | Feb 2009 | A1 |
| 20090077396 | Tsai et al. | Mar 2009 | A1 |
| 20090088258 | Saunders et al. | 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 |
| 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 |
| 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 |
| 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 | Rader et al. | Aug 2010 | A1 |
| 20100197385 | Aoki et al. | Aug 2010 | A1 |
| 20100203955 | Sylla | Aug 2010 | A1 |
| 20100203963 | Allen | Aug 2010 | A1 |
| 20100227662 | Speers et al. | Sep 2010 | A1 |
| 20100227670 | Arezina et al. | Sep 2010 | A1 |
| 20100227671 | Laaroussi | Sep 2010 | A1 |
| 20100227687 | Speers 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 | Speers 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 |
| 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 |
| 20120028718 | Barclay et al. | Feb 2012 | A1 |
| 20120034968 | Watkins et al. | Feb 2012 | A1 |
| 20120046110 | Amaitis | 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 |
| 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 |
| 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 |
| 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 |
| 20170206734 | Nguyen | Jul 2017 | A1 |
| 20170228979 | Nguyen | Aug 2017 | A1 |
| 20170243440 | Nguyen | Aug 2017 | A1 |
| 20170337770 | Nguyen | Nov 2017 | A1 |
| 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 |
| Entry |
|---|
| 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 Octobber 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,171, dated Jun. 6, 2016. |
| Office Action for U.S. Appl. No. 13/843,192, dated Jun. 9, 2016. |
| 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. |
| Notice of Allowance for U.S. Appl. No. 13843,192, dated Aug. 10, 2016. |
| 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. |
| 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. |
| Number | Date | Country | |
|---|---|---|---|
| 20160240044 A1 | Aug 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13557063 | Jul 2012 | US |
| Child | 15138086 | US |
