A portion of the disclosure of this patent document contains material, which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. Copyright 2015, WMS Gaming, Inc.
Embodiments of the inventive subject matter relate generally to wagering game systems and networks that, more particularly, control wagering game lighting content.
Wagering game machines, such as slot machines, video poker machines and the like, have been a cornerstone of the gaming industry for several years. Generally, the popularity of such machines depends on the likelihood (or perceived likelihood) of winning money at the machine and the intrinsic entertainment value of the machine relative to other available gaming options. Where the available gaming options include a number of competing wagering game machines and the expectation of winning at each machine is roughly the same (or believed to be the same), players are likely to be attracted to the most entertaining and exciting machines. Shrewd operators consequently strive to employ the most entertaining and exciting machines, features, and enhancements available because such machines attract frequent play and hence increase profitability to the operator. Therefore, there is a continuing need for wagering game machine manufacturers to continuously develop new games and gaming enhancements that will attract frequent play.
A gaming system that can perform operations to analyze, prioritize, and present different gaming effects competing for presentation on the same output device. For instance, the gaming system analyzes electronic information received via a network communication interface. The electronic information is associated with a first gaming effect and a second gaming effect provided for concurrent presentation via the output device. The gaming system further determines, based on analysis of the electronic information, that the first gaming effect has a higher priority than the second gaming effect for presentation via the output device. Based on the first gaming effect having the higher priority, the gaming system presents the first gaming effect via the output device before presentation of the second gaming effect. Furthermore the gaming system prevents, without user input, presentation of a first portion of the second gaming effect via the output device while the first gaming effect is being presented via the output device. The gaming system further electronically determines that a second portion of the second gaming effect is available for presentation via the output device after an ending point for the first gaming effect and causes the second portion of the second gaming effect to be presented via the output device after the ending point for the first gaming effect.
Embodiments are illustrated in the Figures of the accompanying drawings in which:
This description of the embodiments is divided into five sections. The first section provides an introduction to embodiments. The second section describes example operating environments while the third section describes example operations performed by some embodiments. The fourth section describes additional example operating environments while the fifth section presents some general comments.
This section provides an introduction to some embodiments.
Many computerized wagering game systems (e.g., wagering game machines) have a variety of sound and graphical elements designed to attract and keep a game player's attention, such as sound effects, music, and animation. These game presentation features often include a variety of music, sound effects, and voices presented to complement a visual (e.g., video, computer animated, mechanical, etc.) presentation of the wagering game on a display. Often multiple sources of gaming content provide visual and sound content during a wagering game. Game developers face challenges controlling content from various sources. Some embodiments of the present subject matter, however, describe examples of controlling wagering game lighting content from multiple sources in a wagering game network (e.g., a casino network).
Embodiments can be presented over any type of communications network (e.g., public or private) that provides access to wagering games, such as a website (e.g., via wide-area-networks, or WANs), a private gaming network (e.g., local-area-networks, or LANs), a file sharing networks, a social network, etc., or any combination of networks. Multiple users can be connected to the networks via computing devices. The multiple users can have accounts that subscribe to specific services, such as account-based wagering systems (e.g., account-based wagering game websites, account-based casino networks, etc.). In some embodiments herein a user may be referred to as a player (i.e., of wagering games), and a player may be referred to interchangeably as a player account. Account-based wagering systems utilize player accounts when transacting and performing activities, at the computer level, that are initiated by players. Therefore, a “player account” represents the player at a computerized level. The player account can perform actions via computerized instructions. For example, in some embodiments, a player account may be referred to as performing an action, controlling an item, communicating information, etc. Although a player, or person, may be activating a game control or device to perform the action, control the item, communicate the information, etc., the player account, at the computer level, can be associated with the player, and therefore any actions associated with the player can be associated with the player account. Therefore, for brevity, to avoid having to describe the interconnection between player and player account in every instance, a “player account” may be referred to herein in either context. Further, in some embodiments herein, the word “gaming” is used interchangeably with “gambling”.
The emotive lighting devices 190, 191 can include light emitting devices utilized to present lighting effects. The wagering game machines 160, 161 may be grouped together in a wagering-game-machine bank (“bank”) and the wagering game machines 160, 161 can include communications devices that allow the wagering game machines 160, 161 to communicate with each other to present synchronized bank content, including bank level emotive lighting displays. For example, the wagering game machines 160, 161 can be connected via a dedicated, bank-level, peer-to-peer lighting network. The emotive lighting devices 190, 191 (and their associated wagering game machines 160, 161) can be associated with the emotive light controllers 164, 165, which can receive emotive lighting communications from several sources. For instance, in one example, the emotive light controllers 164, 165 can receive one or more of the following:
The various commands (commands 101, 102, 103 and 104) may all simultaneously compete for use of the emotive lighting devices 190, 191. For instance, each of the commands 101, 102, 103 and 104 may include instructions for an emotive light device 197 (e.g., a single light emitting diode “LED,” a group of LEDs, an LED bar, etc.) to present a conflicting color, intensity level, blinking pattern, or other light presentation effect at a given time (e.g., t1).
Referring again to
This section describes example operating environments and networks and presents structural aspects of some embodiments. More specifically, this section includes discussion about wagering game system architectures.
The wagering game system architecture 200 can also include a wagering game server 250 configured to control wagering game content, provide random numbers, and communicate wagering game information, account information, and other information to and from a wagering game machine 260. The wagering game server 250 can include a content controller 251 configured to manage and control content for the presentation of content on the wagering game machine 260. For example, the content controller 251 can generate game results (e.g., win/loss values), including win amounts, for games played on the wagering game machine 260. The content controller 251 can communicate the game results to the wagering game machine 260. The content controller 251 can also generate random numbers and provide them to the wagering game machine 260 so that the wagering game machine 260 can generate game results. The wagering game server 250 can also include a content store 252 configured to contain content to present on the wagering game machine 260. The wagering game server 250 can also include an account manager 253 configured to control information related to player accounts. For example, the account manager 253 can communicate wager amounts, game results amounts (e.g., win amounts), bonus game amounts, etc., to the account server 270. The wagering game server 250 can also include a communication unit 254 configured to communicate information to the wagering game machine 260 and to communicate with other systems, devices and networks. The wagering game server 250 can also include a secondary game controller 255 configured to control secondary game communications, content, and other information.
The wagering game system architecture 200 can also include the wagering game machine 260 configured to present wagering games and receive and transmit information to control wagering game lighting content. The wagering game machine 260 can include a content controller 261 configured to manage and control content and presentation of content on the wagering game machine 260. The wagering game machine 260 can also include a content store 262 configured to contain content to present on the wagering game machine 260. The wagering game machine 260 can also include an emotive light controller 263 configured to control communications including emotive light presentation data. In some embodiments, the emotive light controller 263 can be external to the wagering game machine 260, such as attached to a cabinet associated with the wagering game machine 260. In other embodiments, the emotive light controller 263 can be detached from the wagering game machine 260 and can be a separate device that controls emotive lighting devices assigned to, proximate to, or in other ways associated with the wagering game machine 260. The wagering game machine 260 can also include a peer-to-peer synchronization controller 264 configured to control synchronization data between wagering game machines within a machine bank including synchronization of emotive light presentation data. The wagering game machine 260 can also include a status control module 265 configured to provide presentation status information to content control sources (e.g., wagering game servers, peer-to-peer content controllers, environmental control servers, emotive light controllers, etc.). The status information can provide information about events that affect the wagering game machine 260, or other devices or components associated with the wagering game machine 260. The events can indicate that presentation devices associated with the wagering game machine 260 are inactive, unavailable, or otherwise ineligible to receive content at a given time. The status control module 265, thus, can broadcast status information to all content controllers and other sources that need to know whether the wagering game machine 260, or presentation devices associated with the wagering game machine 260, are available to participate in a synchronized content presentation (e.g., a light show, a gaming effect, etc.).
The wagering game system architecture 200 can also include a casino network environmental control server 240 configured to control environmental light and sound presentation devices within a casino. The casino network environmental control server 240 can provide emotive lighting presentation data, including light presentation commands on emotive lighting devices on or near wagering game machines, as well as other devices within the casino such as spot lights, overhead emotive lighting, projectors, etc. The casino network environmental control server 240 may include a DMX512 (DMX) light controller, an AMX192 light controller, or other networked theatrical lighting controllers, servers, devices or systems. In some embodiments, the casino network environmental control server 240 can include, control, or in other ways be associated with casino network emotive lighting controllers, such as the casino network emotive light controller 140 in
The wagering game system architecture 200 can also include a secondary content server 280 configured to provide content and control information for secondary games and other secondary content available on a wagering game network (e.g., secondary wagering game content, promotions content, advertising content, player tracking content, web content, etc.). The secondary content server 280 can provide “secondary” content, or content for “secondary” games presented on the wagering game machine 260. “Secondary” in some embodiments can refer to an application's importance or priority of the data. In some embodiments, “secondary” can refer to a distinction, or separation, from a primary application (e.g., separate application files, separate content, separate states, separate functions, separate processes, separate programming sources, separate processor threads, separate data, separate control, separate domains, etc.). Nevertheless, in some embodiments, secondary content and control can be passed between applications (e.g., via application protocol interfaces), thus becoming, or falling under the control of, primary content or primary applications, and vice versa. The secondary content server 280 can include one or more different servers or devices including a secondary game server (e.g., a bonus game server, etc.), a network game server (e.g., a progressive game server, a big event server), an advertising server, a community game server, etc. The secondary content server 280 can provide and control content for community games, including networked games, social games, competitive games, or any other game that multiple players can participate in at the same time.
The wagering game system architecture 200 can also include a web server 290 configured to control and present an online website that hosts wagering games. The web server 290 can also be configured to present multiple wagering game applications on the wagering game machine 260 via a wagering game website, or other gaming-type venue accessible via the Internet. The web server 290 can host an online wagering website and social network. The web server 290 can include other devices, servers, mechanisms, etc., that provide functionality (e.g., controls, web pages, applications, etc.) that web users can use to connect to a social network and/or website and utilize social network and website features (e.g., communications mechanisms, applications, etc.).
Each component shown in the wagering game system architecture 200 is shown as a separate and distinct element connected via a communications network 222. However, some functions performed by one component could be performed by other components. For example, the wagering game server 250 can also be configured to perform functions of the emotive light controller 263, the peer-to-peer synchronization controller 264, and other network elements and/or system devices. Furthermore, the components shown may all be contained in one device, but some, or all, may be included in, or performed by multiple devices, as in the configurations shown in
The wagering game machines described herein (e.g., wagering game machine 260) can take any suitable form, such as floor standing models, handheld mobile units, bar-top models, workstation-type console models, surface computing machines, etc. Further, wagering game machines can be primarily dedicated for use in conducting wagering games, or can include non-dedicated devices, such as mobile phones, personal digital assistants, personal computers, etc.
In some embodiments, wagering game machines and wagering game servers work together such that wagering game machines can be operated as thin, thick, or intermediate clients. For example, one or more elements of game play may be controlled by the wagering game machine (client) or the wagering game servers (server). Game play elements can include executable game code, lookup tables, configuration files, game outcome, audio or visual representations of the game, game assets or the like. In a thin-client example, the wagering game server can perform functions such as determining game outcome or managing assets, while the wagering game machine can present a graphical representation of such outcome or asset modification to the user (e.g., player). In a thick-client example, the wagering game machines can determine game outcomes and communicate the outcomes to the wagering game server for recording or managing a player's account.
In some embodiments, either the wagering game machines (client) or the wagering game server(s) can provide functionality that is not directly related to game play. For example, account transactions and account rules may be managed centrally (e.g., by the wagering game server(s)) or locally (e.g., by the wagering game machines). Other functionality not directly related to game play may include power management, presentation of advertising, software or firmware updates, system quality or security checks, etc.
Furthermore, the wagering game system architecture 200 can be implemented as software, hardware, any combination thereof, or other forms of embodiments not listed. For example, any of the network components (e.g., the wagering game machines, servers, etc.) can include hardware and machine-readable media including instructions for performing the operations described herein. Machine-readable media includes any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine (e.g., a wagering game machine, computer, etc.). For example, tangible machine-readable media includes read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory machines, etc. Machine-readable media also includes any media suitable for transmitting software over a network.
This section describes operations associated with some embodiments. In the discussion below, some flow diagrams are described with reference to block diagrams presented herein. However, in some embodiments, the operations can be performed by logic not described in the block diagrams.
In certain embodiments, the operations can be performed by executing instructions residing on machine-readable media (e.g., software), while in other embodiments, the operations can be performed by hardware and/or other logic (e.g., firmware). In some embodiments, the operations can be performed in series, while in other embodiments, one or more of the operations can be performed in parallel. Moreover, some embodiments can perform more or less than all the operations shown in any flow diagram.
In some embodiments, the emotive light presentation data can control effects and/or light shows that relate to wagering game activities that occur on wagering game machines, across banks of machines, and across a casino network. Emotive light presentation data can be related to wagering game lighting effects, wagering game attract shows, betting or game results activity, celebratory effects, network game reveals, network game activity, tournament activity, game downloads, etc. In some embodiments, the emotive light presentation data can be related to wagering game effects. The following is a list of some example wagering game effects the system can activate according to some embodiments:
In some embodiments, the emotive light presentation data can be related to bank effects. The following is a list of some example bank effects the system can activate according to some embodiments:
In some embodiments, the system can leave out, or skip, one or more content presentation devices (“presentation devices”) from a bank-wide game effect because the presentation devices may be inactive, ineligible, unavailable, etc. for the bank-wide game effect (e.g., a bonus game, a reward, an attract, etc.). In some embodiments, the bank-wide game effect can be a multi-media presentation, including light, sounds, etc. The presentation devices may include wagering game machine displays, reels, emotive lighting devices, speakers, peripheral displays, etc. associated with the bank of wagering game machines. Each presentation device can have an identity (e.g., network address). The presentation devices can be configured to respond to content control data (e.g., lighting commands, sound commands, etc.) based on various factors (e.g., types of content presentation devices in a bank, current states of content presentation devices, etc.). The system can utilize the unique addresses to send different content control data, or no content control data, to inactive or ineligible presentation devices so that the content presentation devices are skipped, or left out, of the bank-wide game effect. Even though the system can leave a content presentation device out of a bank-wide game effect, the system can still monitor gaming activity and continuously evaluate whether presentation devices may become eligible or active. The system can then immediately incorporate the eligible or active presentation devices into the bank-wide game effect.
In one example, a game effect controller, (e.g., a bank light show controller, a peer-to-peer light controller, a wagering game application, a server-side application on wagering game server, etc.) can perform a bank effect, such as a span lighting effect (“span effect”), or some other type of gaming effect. The game effect controller can present the bank effect continuously across a bank of presentation devices associated with one, or more, wagering game machines (e.g., a bank of wagering game machines). The presentation devices, associated with the bank of wagering game machines, however, may be experiencing events that have, or can be categorized as a having, higher priorities than the priority for the bank effect. The game effect controller that controls the bank effect can receive presentation status information from all of the presentation devices within the bank (e.g., via queries to, or broadcasts from, presentation devices and/or presentation device controllers within the bank, via queries to, or broadcasts from, lighting content sources that send lighting data to the presentation devices, etc.). The presentation status information can indicate one or more events that affect a state of availability, of each of the presentation devices, to present at least some portion, or accompanying portion, of the bank effect. Using the presentation status information, the game effect controller determines which of the presentation devices may be receiving content presentation commands (e.g., lighting commands) or that are presenting content (e.g., lighting content) that is higher in priority, or importance, than the priority or importance of the bank effect. For instance, the presentation status information can include lighting data received at emotive light controllers for a bank of wagering game machines. The lighting data can include priority values for light show numbers. The game effect controller can compare the priority values for the light show numbers with a priority value for the bank effect. The game effect controller can then use the comparison data to determine which of the presentation devices in the bank are receiving higher priority content presentation commands, or are associated with other presentation devices that have higher presentation priorities, and are, thus, ineligible to activate the bank effect.
Further, the game effect controller can ascertain network addresses for ineligible presentation devices and generate a synchronized bank effect that skips the addresses of ineligible presentation devices. For example, the game effect controller can send the bank effect data to only eligible devices. In some examples, the bank effect can have a distinct content element that is presented at some portion, or during some time interval, of the bank effect. The distinct content element can be a visually distinct lighting element (e.g., a specific light pattern, a distinct color combination, a unique LED image, etc.) included in the presentation of the bank effect. For instance, a bank effect may include a lighting effect that looks like a snake, with a very long body and a head. The head of the snake may be a visually distinct lighting element from the body of the snake (i.e., the body of the snake can span across multiple emotive lighting devices and may look visually monotonous, but the head has a visually unique look that sets it apart from the body). The game effect controller can determine whether the visually distinct lighting element could potentially be left out of the bank effect if it were to send lighting data to an ineligible lighting device that would not present the lighting data when received (e.g., if the snake effect were sent to an ineligible emotive lighting device, the head of the snake may disappear from view because the ineligible emotive lighting device would be unavailable to present the snake effect). In some embodiments, the visually distinct lighting element may only be an interesting, notable, or unique part of a bank lighting effect. The bank lighting effect, thus, would only suffer aesthetically from omission of the visually distinct lighting element. In other embodiments, however, the visually distinct lighting element may be critical, necessary, revelatory, outcome determinate, or in some other way, convey an important purpose, or function, of the bank effect (e.g., the head of the snake stops at a wagering game machine, which indicates the winner of a community wagering game). In other words, the distinct content element reveals a gaming outcome, and, according to presentation rules for the gaming outcome, the distinct content element is required to be presented at all times during the bank gaming effect. In such as case, omission of the visually distinct lighting element would not only have an aesthetic consequence, but may actually defeat the purpose of presenting the bank effect if it were to be omitted. As a result, the game effect controller can ensure that ineligible presentation devices are omitted, or excluded, from participating as nodes in the bank lighting effect. For instance, the game effect controller can exclude the ineligible presentation devices from receiving transmissions of the bank lighting effect. For instance, the game effect controller can generate a transmission schedule that would entirely omit transmission of lighting data to ineligible presentation devices. The transmission schedule can be a control matrix that synchronizes the timing of transmissions of emotive lighting control data. In other words, the game effect controller can generate a transmission schedule that sends emotive lighting control transmission to only eligible presentation devices, treating the ineligible presentation devices as if they were non-existent. The game effect controller thus synchronizing the bank effect so that it does not omit the presentation of the visually distinct lighting element (e.g., does not omit the presentation of the snake's head). The game effect controller thus ensures a continuous, synchronized light effect pattern between only the eligible, participating nodes (e.g., eligible presentation devices) that would not omit the visually distinct content element from the synchronized bank effect for any period of time.
In some embodiments, as stated previously, the ineligible presentation devices may be ineligible because control data received at those presentation devices has higher priorities than the priority for the bank effect. However, other events, other than those that produce emotive lighting effects, can also provide priorities that would make the presentation device ineligible. The other events can include gaming events, maintenance events, marketing events, sound events, etc., that may not necessarily use emotive lighting devices associated with a wagering game machine, but may have priorities for the events that would trump the presentation of some, or all, emotive lighting. For example, a wagering game machine may present an advertisement on a wagering game machine display. The advertisement may have a high priority that prevents, or warrants the prevention of, some or all emotive lighting presentations that would distract from the advertisement's presentation. Thus, the presentation status information that the game effect controller receives from a presentation device in the bank can include game activity data, maintenance activity data, marketing activity data, sound data, etc. The game effect controller, thus, can manage priorities for all types of data and can determine subsets of presentation devices, within a bank, that are ineligible for a bank effect and can exclude the ineligible presentation devices from the bank effect. The game effect controller can also determine subsets of eligible presentation devices and include the eligible presentation devices in the bank effect.
In another example, some other events may accompany emotive lighting events, but may have priorities that make emotive lighting devices ineligible even if the emotive lighting devices are available to present the bank effect. For example, the game effect controller can evaluate sound effects that accompany the bank effect and determine whether the sounds effects are audibly distinct. For example, the bank effect can include sound effects that accompany an emotive lighting effect. The sound effects may be audibly distinct during a portion of the emotive lighting effect. For instance, a portion of the emotive lighting effect may not be visually distinct but the sound produced by an associated speaker, for example, for that portion of the emotive lighting effect, may be audibly distinct from other sound effects that accompany the emotive lighting effect. For example, an emotive light show may include audibly distinct sound elements that beep at given intervals on speakers within a bank of wagering game machines. Thus, if a speaker, or other sound production device, associated with an emotive lighting device, is unavailable to present the audibly distinct sound element, the game effect controller could exclude the emotive lighting device from receiving lighting data for the bank effect because the accompanying audio device is unavailable. Thus, even though the emotive lighting device associated with the speaker is eligible to present lighting content, the distinct content element is associated with the speakers, which are unavailable, and, thus, the game effect controller treats the emotive lighting device as ineligible.
Further, still referring to excluding ineligible presentation devices, in some embodiments, the system can send bank effect control data to ineligible presentation devices as well as to eligible presentation devices. The system can include exclusionary instructions in the bank effect control data. A content controller for an ineligible presentation device can evaluate the exclusionary instructions and determine to skip presentation of the bank effect based on the exclusionary instructions. For instance, the exclusionary instructions can include a priority value for the bank effect. The content controller for the ineligible device can receive the priority value, included in the bank effect control data, and determine whether the priority value for the bank effect control data is higher than a priority values for other game effect data (e.g., see processing block 306) also received by the content controller. If the other game effect data has a higher priority value, the content controller can present the higher priority data first, and ignore, or suspend, the presentation of the bank effect control data. In other embodiments, the system can include “pass” instructions in the exclusionary instructions. The pass instructions can instruct the content controller to ignore the bank effect control data, or pass presentation of the bank effect to a neighboring presentation node (e.g., a neighboring eligible presentation device in the bank of presentation devices). After time, the ineligible presentation device may become eligible (e.g., once a higher priority, game effect command completes its presentation on the ineligible presentation device). The content controller can, therefore, immediately begin presenting the bank effect on the presentation device because the content controller is already receiving the bank effect control data. Thus, in some embodiments, the content controller does not have to wait for the game effect controller to re-evaluate the availability of the presentation device or wait for the game effect control to begin sending bank effect control data because the content controller has been receiving the bank effect control data all along.
In some embodiments, the emotive light presentation data can be related to network lighting effects. The following is a list of some example purposes for which the system can activate network lighting effects according to some embodiments: complimentary awards, community games, secondary games, maintenance, casino-wide progressive games, network celebrations, network reveals, mystery reveals, casino-wide events, etc.
The flow 300 continues at processing block 304, where the system determines a first priority value for the first emotive light presentation data and determines a second priority value for the second emotive light presentation data. In some embodiments, the priority values (first priority value or second priority value) can be a bit in a command, an instruction, a parameter, etc., included in emotive light presentation data. In some embodiments, the system can provide configuration tools for an operator to indicate or assign priority values for different shows, different activities, etc. The system can store configured priority rules and make the priority rules accessible to all wagering game machines and their ELCs.
Returning to
Returning to
The flow 300 continues at processing block 306, where the system prioritizes the first emotive light presentation data and the second emotive light presentation data based on the first priority value and the second priority value. In some embodiments, the system can determine priorities that simultaneously conflict with light presentation on the emotive lighting device. The system can prioritize the conflicts by determining which priority value is more significant, or that transcends other values according to a priority order (e.g., which priority value is higher in value for an ordering scheme where higher priority value numbers indicate priorities that are more significant).
The flow 300 continues at processing block 308, where the system controls the first emotive light presentation data and the second emotive light presentation data based on prioritization of the first priority value and the second priority value. For example, the system can stop, pause, kill, or ignore lower priority commands in favor of higher priority commands. For example, the system may ignore lower priority lighting commands sent via one source (e.g., a DMX controller) in favor of higher priority lighting commands sent by another source (e.g., a bank controller, a wagering game server, a wagering game machine application, etc.). In some embodiments, the system can coordinate the proper timing for handing off use of an emotive lighting device at the end of one higher priority command and activate the emotive lighting device for next highest priority.
For instance, in
Returning to
The flow 700 continues at processing block 704, where the system determines lighting prominence values associated with each of the plurality of casino light shows.
The flow 700 continues at processing block 706, where the system determines a casino light show, from the plurality of casino light shows, that has the highest lighting prominence value.
The flow 700 continues at processing block 708, where the system determines at least one light effect characteristic for the casino light show assigned for presentation at the one location on the lighting device.
The flow 700 continues at processing block 710, where the system determines at least one additional light effect characteristic for at least one additional casino light show from the plurality of casino light shows that has a lower lighting prominence value than the highest lighting prominence value, where the at least one additional light effect characteristic is also assigned for presentation at the one location on the lighting device.
The flow 700 continues at processing block 712, where the system simultaneously presents the at least one light effect characteristic and the at least one additional light effect characteristic at the one location of the lighting device, according to the lighting prominence values, so that the at least one light effect characteristic and the at least one additional light effect characteristic combine together into a composite lighting effect, where the simultaneously presenting includes presenting the at least one light effect characteristic with greater prominence in the composite lighting effect than the at least one additional light effect characteristic.
Returning to
In other example, the system does not present multiple light presentation layers or elements with one having greater prominence. Instead, the system can computationally composite light characteristic values and prominence values to generate a composite lighting effect result, and use the composite lighting effect result to present a composite lighting effect. For instance, the system can pre-determine the composite lighting effect using a compositing algorithm, and applying the prominence values during the processing of the algorithm (e.g., passing in priority values and/or transparency values into the algorithm), to generate a computational (e.g., simulated, mathematical, etc.) composite lighting effect result (“composite result”) of the composite lighting effect. The system can then use the computational composite result to present the composite lighting effect on one lighting source. For instance, in
It should also be noted that players, as well as professionally trained casino light show operators, can configure the system. For example, players can configure the system with player preferences regarding show values and/or business rules. For example, players can specify priorities, lighting characteristics, transparency values, business rules, etc.
This section describes example operating environments, systems and networks, and presents structural aspects of some embodiments.
The CPU 1226 is also connected to an input/output (“I/O”) bus 1222, which can include any suitable bus technologies, such as an AGTL+ frontside bus and a PCI backside bus. The I/O bus 1222 is connected to a payout mechanism 1208, primary display 1210, secondary display 1212, value input device 1214, player input device 1216, information reader 1218, and storage unit 1230. The player input device 1216 can include the value input device 1214 to the extent the player input device 1216 is used to place wagers. The I/O bus 1222 is also connected to an external system interface 1224, which is connected to external systems (e.g., wagering game networks). The external system interface 1224 can include logic for exchanging information over wired and wireless networks (e.g., 802.11g transceiver, Bluetooth transceiver, Ethernet transceiver, etc.)
The I/O bus 1222 is also connected to a location unit 1238. The location unit 1238 can create player information that indicates the wagering game machine's location/movements in a casino. In some embodiments, the location unit 1238 includes a global positioning system (GPS) receiver that can determine the wagering game machine's location using GPS satellites. In other embodiments, the location unit 1238 can include a radio frequency identification (RFID) tag that can determine the wagering game machine's location using RFID readers positioned throughout a casino. Some embodiments can use GPS receiver and RFID tags in combination, while other embodiments can use other suitable methods for determining the wagering game machine's location. Although not shown in
In some embodiments, the wagering game machine 1206 can include additional peripheral devices and/or more than one of each component shown in
In some embodiments, the wagering game machine 1206 includes a gaming effect controller 1237. The gaming effect controller 1237 can process communications, commands, or other information, where the processing can control wagering game content and effects (e.g., light effects, sound effects, etc.).
Furthermore, any component of the wagering game machine 1206 can include hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein.
The wagering game machine 1300 comprises a housing 1312 and includes input devices, including value input devices 1318 and a player input device 1324. For output, the wagering game machine 1300 includes a primary display 1314 for displaying information about a basic wagering game. The primary display 1314 can also display information about a bonus wagering game and a progressive wagering game. The wagering game machine 1300 also includes a secondary display 1316 for displaying wagering game events, wagering game outcomes, and/or signage information. While some components of the wagering game machine 1300 are described herein, numerous other elements can exist and can be used in any number or combination to create varying forms of the wagering game machine 1300.
The value input devices 1318 can take any suitable form and can be located on the front of the housing 1312. The value input devices 1318 can receive currency and/or credits inserted by a player. The value input devices 1318 can include coin acceptors for receiving coin currency and bill acceptors for receiving paper currency. Furthermore, the value input devices 1318 can include ticket readers or barcode scanners for reading information stored on vouchers, cards, or other tangible portable storage devices. The vouchers or cards can authorize access to central accounts, which can transfer money to the wagering game machine 1300.
The player input device 1324 comprises a plurality of push buttons on a button panel 1326 for operating the wagering game machine 1300. In addition, or alternatively, the player input device 1324 can comprise a touch screen 1328 mounted over the primary display 1314 and/or secondary display 1316.
The various components of the wagering game machine 1300 can be connected directly to, or contained within, the housing 1312. Alternatively, some of the wagering game machine's components can be located outside of the housing 1312, while being communicatively coupled with the wagering game machine 1300 using any suitable wired or wireless communication technology.
The operation of the basic wagering game can be displayed to the player on the primary display 1314. The primary display 1314 can also display a bonus game associated with the basic wagering game. The primary display 1314 can include a cathode ray tube (CRT), a high resolution liquid crystal display (LCD), a plasma display, light emitting diodes (LEDs), or any other type of display suitable for use in the wagering game machine 1300. Alternatively, the primary display 1314 can include a number of mechanical reels to display the outcome. In
A player begins playing a basic wagering game by making a wager via the value input device 1318. The player can initiate play by using the player input device's buttons or touch screen 1328. The basic game can include arranging a plurality of symbols along a pay line 1332, which indicates one or more outcomes of the basic game. Such outcomes can be randomly selected in response to player input. At least one of the outcomes, which can include any variation or combination of symbols, can trigger a bonus game.
In some embodiments, the wagering game machine 1300 can also include an information reader 1352, which can include a card reader, ticket reader, bar code scanner, RFID transceiver, or computer readable storage medium interface. In some embodiments, the information reader 1352 can be used to award complimentary services, restore game assets, track player habits, etc.
The described embodiments may be provided as a computer program product, or software, that may include a machine-readable medium having stored thereon instructions, which may be used to program a computer system (or other electronic device(s)) to perform a process according to embodiments(s), whether presently described or not, because every conceivable variation is not enumerated herein. A machine readable medium includes any mechanism for storing or transmitting information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). The machine-readable medium may include, but is not limited to, magnetic storage medium (e.g., floppy diskette); optical storage medium (e.g., CD-ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; or other types of medium suitable for storing electronic instructions. In addition, embodiments may be embodied in an electrical, optical, acoustical or other form of propagated signal (e.g., carrier waves, infrared signals, digital signals, etc.), or wireline, wireless, or other communications medium.
This detailed description refers to specific examples in the drawings and illustrations. These examples are described in sufficient detail to enable those skilled in the art to practice the inventive subject matter. These examples also serve to illustrate how the inventive subject matter can be applied to various purposes or embodiments. Other embodiments are included within the inventive subject matter, as logical, mechanical, electrical, and other changes can be made to the example embodiments described herein. Features of various embodiments described herein, however essential to the example embodiments in which they are incorporated, do not limit the inventive subject matter as a whole, and any reference to the invention, its elements, operation, and application are not limiting as a whole, but serve only to define these example embodiments. This detailed description does not, therefore, limit embodiments, which are defined only by the appended claims. Each of the embodiments described herein are contemplated as falling within the inventive subject matter, which is set forth in the following claims.
This application is a continuation application of U.S. application Ser. No. 13/382,738, which is a National Stage Application of PCT/US10/41112 filed 6 Jul. 2010, which claims the priority benefit of U.S. Provisional Application Ser. No. 61/223,569 filed Jul. 7, 2009 and U.S. Provisional Application No. 61/261,306 filed Nov. 14, 2009. The Ser. No. 13/382,738 Application, the PCT/US10/41112 Application, the 61/223,569 Application, and the No. 61/261,306 Application are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5259613 | Marnell, II | Nov 1993 | A |
5483631 | Nagai et al. | Jan 1996 | A |
5633933 | Aziz | May 1997 | A |
6040831 | Nishida | Mar 2000 | A |
6081266 | Sciammaella | Jun 2000 | A |
6146273 | Olsen | Nov 2000 | A |
6217448 | Olsen | Apr 2001 | B1 |
6339796 | Gambino | Jan 2002 | B1 |
6647119 | Slezak | Nov 2003 | B1 |
6843723 | Joshi | Jan 2005 | B2 |
6927545 | Belliveau | Aug 2005 | B2 |
6939226 | Joshi | Sep 2005 | B1 |
6960136 | Joshi et al. | Nov 2005 | B2 |
6972528 | Shao et al. | Dec 2005 | B2 |
6974385 | Joshi et al. | Dec 2005 | B2 |
6991543 | Joshi | Jan 2006 | B2 |
6997803 | LeMay et al. | Feb 2006 | B2 |
7082572 | Pea et al. | Jul 2006 | B2 |
7112139 | Paz Barahona et al. | Sep 2006 | B2 |
7181370 | Furem et al. | Feb 2007 | B2 |
7228190 | Dowling et al. | Jun 2007 | B2 |
7269648 | Krishnan et al. | Sep 2007 | B1 |
7364508 | Loose et al. | Apr 2008 | B2 |
7367886 | Loose et al. | May 2008 | B2 |
7449839 | Chen et al. | Nov 2008 | B1 |
7479063 | Pryzby et al. | Jan 2009 | B2 |
7495671 | Chemel et al. | Feb 2009 | B2 |
7550931 | Lys et al. | Jun 2009 | B2 |
7666091 | Joshi et al. | Feb 2010 | B2 |
7682249 | Winans et al. | Mar 2010 | B2 |
7811170 | Winans et al. | Oct 2010 | B2 |
7867085 | Pryzby et al. | Jan 2011 | B2 |
7972214 | Kinsley et al. | Jul 2011 | B2 |
8079902 | Michaelson et al. | Dec 2011 | B2 |
8083587 | Okada | Dec 2011 | B2 |
8591315 | Gagner et al. | Nov 2013 | B2 |
8613667 | Brunell et al. | Dec 2013 | B2 |
8622830 | Radek et al. | Jan 2014 | B2 |
8814673 | Brunell et al. | Aug 2014 | B1 |
8827805 | Caporusso et al. | Sep 2014 | B1 |
8840464 | Brunell et al. | Sep 2014 | B1 |
8968088 | Brunell et al. | Mar 2015 | B2 |
9011247 | Gronkowski et al. | Apr 2015 | B2 |
9087429 | Brunell et al. | Jul 2015 | B2 |
20010021666 | Yoshida et al. | Sep 2001 | A1 |
20020010018 | Lemay et al. | Jan 2002 | A1 |
20020055978 | Joon-Boo et al. | May 2002 | A1 |
20020160826 | Gomez et al. | Oct 2002 | A1 |
20030002246 | Kerr | Jan 2003 | A1 |
20030007648 | Currell | Jan 2003 | A1 |
20030017865 | Beaulieu et al. | Jan 2003 | A1 |
20030130033 | Loose | Jul 2003 | A1 |
20030132722 | Chansky et al. | Jul 2003 | A1 |
20040072610 | White et al. | Apr 2004 | A1 |
20040142747 | Pryzby | Jul 2004 | A1 |
20040160199 | Morgan et al. | Aug 2004 | A1 |
20040178750 | Belliveau | Sep 2004 | A1 |
20040209692 | Schober et al. | Oct 2004 | A1 |
20050043090 | Pryzby et al. | Feb 2005 | A1 |
20050044500 | Orimoto et al. | Feb 2005 | A1 |
20050054440 | Anderson et al. | Mar 2005 | A1 |
20050077843 | Benditt | Apr 2005 | A1 |
20050116667 | Mueller et al. | Jun 2005 | A1 |
20050128751 | Roberge et al. | Jun 2005 | A1 |
20050153780 | Gauselmann | Jul 2005 | A1 |
20050164785 | Connelly | Jul 2005 | A1 |
20050164786 | Connelly | Jul 2005 | A1 |
20050164787 | Connelly | Jul 2005 | A1 |
20050164788 | Grabiec | Jul 2005 | A1 |
20050174473 | Morgan et al. | Aug 2005 | A1 |
20050200318 | Hunt et al. | Sep 2005 | A1 |
20050239545 | Rowe | Oct 2005 | A1 |
20050248299 | Chemel et al. | Nov 2005 | A1 |
20050275626 | Mueller et al. | Dec 2005 | A1 |
20050277469 | Pryzby et al. | Dec 2005 | A1 |
20050282631 | Bonney et al. | Dec 2005 | A1 |
20060009285 | Pryzby et al. | Jan 2006 | A1 |
20060022214 | Morgan et al. | Feb 2006 | A1 |
20060025211 | Wilday et al. | Feb 2006 | A1 |
20060046829 | White | Mar 2006 | A1 |
20060076908 | Morgan et al. | Apr 2006 | A1 |
20060244622 | Wray | Nov 2006 | A1 |
20060253781 | Pea et al. | Nov 2006 | A1 |
20070004510 | Underdahl et al. | Jan 2007 | A1 |
20070008711 | Kim | Jan 2007 | A1 |
20070032288 | Nelson et al. | Feb 2007 | A1 |
20070036368 | Hettinger et al. | Feb 2007 | A1 |
20070086754 | Lys et al. | Apr 2007 | A1 |
20070111776 | Griswold et al. | May 2007 | A1 |
20070189026 | Chemel et al. | Aug 2007 | A1 |
20070218970 | Patel et al. | Sep 2007 | A1 |
20070218974 | Patel et al. | Sep 2007 | A1 |
20070219000 | Aida | Sep 2007 | A1 |
20070291483 | Lys | Dec 2007 | A1 |
20070293304 | Loose et al. | Dec 2007 | A1 |
20080039213 | Cornell et al. | Feb 2008 | A1 |
20080070685 | Pryzby et al. | Mar 2008 | A1 |
20080094005 | Rabiner et al. | Apr 2008 | A1 |
20080113715 | Beadell et al. | May 2008 | A1 |
20080113796 | Beadell et al. | May 2008 | A1 |
20080113821 | Beadell et al. | May 2008 | A1 |
20080143267 | Neuman | Jun 2008 | A1 |
20080161108 | Dahl et al. | Jul 2008 | A1 |
20080176647 | Acres | Jul 2008 | A1 |
20080231203 | Budde et al. | Sep 2008 | A1 |
20080274793 | Selig et al. | Nov 2008 | A1 |
20080278946 | Tarter et al. | Nov 2008 | A1 |
20080288607 | Muchow | Nov 2008 | A1 |
20080309259 | Snijder et al. | Dec 2008 | A1 |
20090009997 | Sanfilippo et al. | Jan 2009 | A1 |
20090023485 | Ishihata et al. | Jan 2009 | A1 |
20090149242 | Woodard et al. | Jun 2009 | A1 |
20090170597 | Bone et al. | Jul 2009 | A1 |
20090197673 | Bone et al. | Aug 2009 | A1 |
20090203427 | Okada | Aug 2009 | A1 |
20090206773 | Chang | Aug 2009 | A1 |
20090270167 | Ajiro et al. | Oct 2009 | A1 |
20090298579 | Radek et al. | Dec 2009 | A1 |
20090318223 | Langridge et al. | Dec 2009 | A1 |
20100022298 | Kukita | Jan 2010 | A1 |
20100022305 | Yano | Jan 2010 | A1 |
20100029385 | Garvey et al. | Feb 2010 | A1 |
20100031186 | Tseng et al. | Feb 2010 | A1 |
20100075750 | Bleich et al. | Mar 2010 | A1 |
20100113136 | Joshi et al. | May 2010 | A1 |
20100171145 | Morgan et al. | Jul 2010 | A1 |
20100213876 | Adamson et al. | Aug 2010 | A1 |
20100234107 | Fujimoto et al. | Sep 2010 | A1 |
20100277079 | Van Der et al. | Nov 2010 | A1 |
20100309016 | Wendt et al. | Dec 2010 | A1 |
20100317437 | Berry et al. | Dec 2010 | A1 |
20110035404 | Morgan et al. | Feb 2011 | A1 |
20110045905 | Radek | Feb 2011 | A1 |
20110050101 | Bailey et al. | Mar 2011 | A1 |
20110070948 | Bainbridge et al. | Mar 2011 | A1 |
20110118018 | Toyoda | May 2011 | A1 |
20110118034 | Jaffe et al. | May 2011 | A1 |
20110190052 | Takeda et al. | Aug 2011 | A1 |
20120009995 | Osgood | Jan 2012 | A1 |
20120040738 | Lanning et al. | Feb 2012 | A1 |
20120115608 | Pfeifer et al. | May 2012 | A1 |
20120122571 | Desimone et al. | May 2012 | A1 |
20120129601 | Gronkowski et al. | May 2012 | A1 |
20120178523 | Greenberg et al. | Jul 2012 | A1 |
20120178528 | Brunell et al. | Jul 2012 | A1 |
20130005458 | Kosta et al. | Jan 2013 | A1 |
20130184078 | Brunell et al. | Jul 2013 | A1 |
20130310178 | Pryzby et al. | Nov 2013 | A1 |
20140073430 | Brunell et al. | Mar 2014 | A1 |
20140228121 | Berry et al. | Aug 2014 | A1 |
20140228122 | Berry et al. | Aug 2014 | A1 |
20140335956 | Brunell et al. | Nov 2014 | A1 |
20140378225 | Caporusso et al. | Dec 2014 | A1 |
Number | Date | Country |
---|---|---|
1439507 | Jul 2004 | EP |
2004086320 | Oct 2001 | WO |
2004014501 | Feb 2004 | WO |
2004075128 | Sep 2004 | WO |
2004075129 | Sep 2004 | WO |
WO2004075128 | Sep 2004 | WO |
2005113089 | Dec 2005 | WO |
2005114598 | Dec 2005 | WO |
2005114599 | Dec 2005 | WO |
2005117647 | Dec 2005 | WO |
2006017444 | Feb 2006 | WO |
2006017445 | Feb 2006 | WO |
2006033941 | Mar 2006 | WO |
2006039284 | Apr 2006 | WO |
2006039323 | Apr 2006 | WO |
2006125013 | Nov 2006 | WO |
2007022294 | Feb 2007 | WO |
2007022343 | Feb 2007 | WO |
2007061904 | May 2007 | WO |
2007133566 | Nov 2007 | WO |
2008057538 | May 2008 | WO |
2008063391 | May 2008 | WO |
2008137130 | Nov 2008 | WO |
2009054930 | Apr 2009 | WO |
2010048068 | Apr 2010 | WO |
2011005797 | Jan 2011 | WO |
2011005798 | Jan 2011 | WO |
2011014760 | Feb 2011 | WO |
20041110 | Aug 2005 | ZA |
Entry |
---|
“Coyote Moon”, IGT, 2005, 2 pages. |
“Elvis Little More Action”, 24Hr-Slots, Sep. 5, 2009, 4 pages. |
“PCT Application No. PCT/US10/41111 International Preliminary Report on Patentability”, Oct. 24, 2011, 13 pages. |
“PCT Application No. PCT/US10/41111 International Search Report”, Sep. 1, 2010, 12 pages. |
“PCT Application No. PCT/US10/41112 International Preliminary Report on Patentability”, Aug. 31, 2012, 4 pages. |
“PCT Application No. PCT/US10/41112 International Search Report”, Sep. 2, 2010, 11 pages. |
“PCT Application No. PCT/US10/43886 International Preliminary Report on Patentability”, May 3, 2012, 4 pages. |
“PCT Application No. PCT/US10/43886 International Search Report”, Sep. 16, 2010, 12 pages. |
“U.S. Appl. No. 12/797,756 Office Action”, Nov. 7, 2013, 7 Pages. |
“U.S. Appl. No. 12/860,467 Office Action”, Jan. 17, 2013, 16 pages. |
“U.S. Appl. No. 12/965,749 Final Office Action”, Dec. 15, 2014, 32 Pages. |
“U.S. Appl. No. 12/965,749 Final Office Action”, Apr. 22, 2013, 30 pages. |
“U.S. Appl. No. 12/965,749 Final Office Action”, Apr. 30, 2014, 40 Pages. |
“U.S. Appl. No. 12/965,749 Office Action”, Nov. 8, 2012, 30 pages. |
“U.S. Appl. No. 12/965,749 Office Action”, Dec. 17, 2013, 35 Pages. |
“U.S. Appl. No. 12/965,749 Office Action”, Sep. 4, 2014, 33 Pages. |
“U.S. Appl. No. 12/971,544 Final Office Action”, Mar. 14, 2013, 38 pages. |
“U.S. Appl. No. 12/971,544 Office Action”, Nov. 6, 2012, 43 pages. |
“U.S. Appl. No. 13/094,560 Final Office Action”, May 23, 2014, 9 Pages. |
“U.S. Appl. No. 13/094,560 Office Action”, Mar. 30, 2012, 13 pages. |
“U.S. Appl. No. 13/094,560 Office Action”, Dec. 6, 2013, 9 Pages. |
“U.S. Appl. No. 13/094,701 Final Office Action”, Nov. 28, 2012, 14 pages. |
“U.S. Appl. No. 13/094,701 Office Action”, Mar. 27, 2012, 26 pages. |
“U.S. Appl. No. 13/094,811 Final Office Action”, Dec. 24, 2013, 15 Pages. |
“U.S. Appl. No. 13/094,811 Office Action”, Apr. 3, 2012, 16 pages. |
“U.S. Appl. No. 13/094,811 Office Action”, Jun. 21, 2013, 19 pages. |
“U.S. Appl. No. 13/204,225 Final Office Action”, Sep. 25, 2013, 16 PAges. |
“U.S. Appl. No. 13/204,225 Office Action”, Jun. 22, 2012, 23 pages. |
“U.S. Appl. No. 13/204,225 Office Action”, Feb. 27, 2013, 19 pages. |
“U.S. Appl. No. 13/382,738 Final Office Action”, Mar. 12, 2014, 23 Pages. |
“U.S. Appl. No. 13/382,738 Final Office Action”, Jul. 8, 2014, 20 Pages. |
“U.S. Appl. No. 13/382,738 Office Action”, Feb. 7, 2013, 41 pages. |
“U.S. Appl. No. 13/382,738 Office Action”, Sep. 24, 2013, 24 Pages. |
“U.S. Appl. No. 13/382,783 Office Action”, Feb. 28, 2013, 26 pages. |
“U.S. Appl. No. 13/382,783 Final Office Action”, Oct. 4, 2013, 22 Pages. |
“U.S. Appl. No. 13/382,783 Office Action”, Apr. 16, 2014, 24 Pages. |
“U.S. Appl. No. 13/382,783 Office Action”, Jul. 25, 2013, 20 Pages. |
“U.S. Appl. No. 13/382,783 Office Action”, Sep. 24, 2014, 5 Pages. |
“U.S. Appl. No. 13/388,118 Final Office Action”, May 23, 2014, 11 Pages. |
“U.S. Appl. No. 13/388,118 Office Action”, Oct. 11, 2013, 9 Pages. |
“U.S. Appl. No. 14/080,272 Office Action”, Oct. 23, 2014, 5 Pages. |
Gusella, et al., “An Election Algorithm for a Distributed Clock Synchronization Program”, Berkley, Dec. 1985, 19 pages. |
NYPHINIX13, “Star Wars Cloud City Slot Bonus—IGT”, YouTube, Mar. 18, 2010, 1 page. |
Co-pending U.S. Appl. No. 12/965,749, filed Dec. 10, 2010, 48 Pages. |
Co-pending U.S. Appl. No. 12/971,544, filed Dec. 17, 2010, 46 Pages. |
Co-pending U.S. Appl. No. 12/860,467, filed Aug. 20, 2010, 49 Pages. |
Co-pending U.S. Appl. No. 12/797,756, filed Jun. 10, 2010, 63 Pages. |
Co-pending U.S. Appl. No. 14/080,272, filed Nov. 14, 2013, 39 Pages. |
Co-pending U.S. Appl. No. 13/109,427, filed May 17, 2011, 45 Pages. |
Co-pending U.S. Appl. No. 13/094,560, filed Apr. 26, 2011, 30 Pages. |
Co-pending U.S. Appl. No. 13/094,701, filed Apr. 26, 2011, 40 Pages. |
Co-pending U.S. Appl. No. 14/446,081, filed Jul. 29, 2014, 40 Pages. |
Co-pending U.S. Appl. No. 13/204,225, filed Aug. 5, 2011, 45 Pages. |
Co-pending U.S. Appl. No. 14/480,397, filed Sep. 8, 2014, 39 Pages. |
Co-pending U.S. Appl. No. 13/094,811, filed Apr. 26, 2011, 31 Pages. |
Co-pending U.S. Appl. No. 14/254,656, filed Apr. 16, 2014, 31 Pages. |
“U.S. Appl. No. 12/965,749 Office Action”, Mar. 18, 2015, 28 Pages. |
“U.S. Appl. No. 13/382,783 Final Office Action”, Feb. 20, 2015, 10 Pages. |
Co-pending U.S. Appl. No. 14/677,660, filed Apr. 2, 2015, 46 pages. |
Number | Date | Country | |
---|---|---|---|
20150148134 A1 | May 2015 | US |
Number | Date | Country | |
---|---|---|---|
61261306 | Nov 2009 | US | |
61223569 | Jul 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13382738 | US | |
Child | 14614089 | US |