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 2014, WMS Gaming, Inc.
Embodiments of the inventive subject matter relate generally to wagering game systems and networks that, more particularly, control wagering game system audio.
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.
Embodiments are illustrated in the Figures of the accompanying drawings in which:
This description of the embodiments is divided into six 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 embodiments while the fifth section describes additional example operating environments. The sixth section presents some general comments.
This section provides an introduction to some embodiments.
Many computerized wagering game systems 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 gaming applications run on a wagering game machine at the same time. The multiple gaming applications can compete for sound resources, fighting for the foreground. For example, a main, or primary, game application (“primary game”) can be running on a wagering game machine. At the same time a secondary game application (“secondary game”) can also be presented on the wagering game machine. The secondary game can be an application (e.g., a server-side game) that is independent of the first game. A secondary game server can present the secondary game on the wagering game machine. Both the primary game and the secondary game present sounds that compete for the player's attention. However, because the primary and secondary games were developed separately from each other, and their audio tracks were not mastered or mixed together, they may have competing sounds that clip or distort each other when played at the same time, potentially providing a confusing or unsatisfactory gaming sound experience for the player.
Some embodiments of the present subject matter describe examples of controlling wagering game system audio on a wagering game machine or other computerized system in a networked wagering venue (e.g., a casino, an online casino, a wagering game website, a wagering network, etc.). 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 also 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.”
Although
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 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 system audio, including prioritizing audio based on classes, or other categories. 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 a sound classifier 263 configured to determine sound characteristics and metadata for sound content, including sound classifications of wagering games and other applications associated with wagering games and gaming venues. The wagering game machine 260 can also include a submix engine 264 configured to compile sound from multiple playlists, or other sources, into a master playlist. The wagering game machine 260 can also include a sound prioritizer 265 configured to prioritize the presentation of sound content using sound characteristics including sound classifications and/or types.
The wagering game system architecture 200 can also include a marketing server 290 configured to utilize player data to determine marketing promotions that may be of interest to a player account. The marketing server 290 can also analyze player data and generate analytics for players, group players into demographics, integrate with third party marketing services and devices, etc. The marketing server 290 can also provide player data to third parties that can use the player data for marketing.
The wagering game system architecture 200 can also include a web server 280 configured to control and present an online website that hosts wagering games. The web server 280 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 280 can host an online wagering website and social network. The web server 280 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.).
The wagering game system architecture 200 can also include a secondary content server 240 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 240 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.
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 sound classifier 263, the submix engine 264, the sound prioritizer 265, 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., the 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 machines (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 machines 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 storage media including instructions for performing the operations described herein
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.
The flow 300 continues at processing block 304, where the system determines classes assigned to sound content activated contemporaneously from the plurality of playlists. The activated sound content can be scheduled to play, or playing, simultaneously, at a given time, during the gaming session. Sounds that are activated contemporaneously, and that play concurrently, have some degree of overlap in their audible presentation such that there exists a possibility that the sounds may compete for the same audible space or potentially conflict in their presentations. The sound classes can be types, categories, etc. of the sounds. Examples of classes may include general classifications of sounds, such as speech, special effects, music, etc., as well as wagering game specific classifications, such as jackpot sounds, reel spin sounds, game character sounds, money-in sounds, bonus game sounds, congratulatory sounds, etc. In some embodiments, the system can determine the class data from playlist commands and other information stored with the application and its assets. Each sound content item can have one or more classes assigned to it. The classes can relate to a group of sounds, such as a class that describes an entire type of application (e.g., main game, bonus game, advertisement, etc.), individual sounds produced by an application (e.g., music, speech, special effects, etc.), or other types of information. The classes can have pre-assigned values, or parameters, that were associated with gaming assets during post-production and mixing of the gaming content. In some embodiments, the system can also assign classes to applications that lack class data. In
The flow 300 continues at processing block 306, where the system compares the sound classes to prioritization rules. The prioritization rules have preset priorities that provide control information based on any given scenario, including current application activity occurring at the given time. The system compares the sound class values to values indicated in the rules. The values in the rules are associated with the current application activity and the rules also include possible responses to the activity. The system determines the current application activity that occurs for the applications by monitoring gaming events, or other types of events, that occur within the applications. The system can determine specific playlists, or specific portions of a playlist, that are associated with the current application activity. Any given application may have more than one playlist, or separate parts of the playlist, that pertain to the current application activity. The system can determine, from the plurality of playlists, sound content that is related to the current application activity. The system can determine, from the plurality of playlists, the sound classes that are associated with the sound content. The system can then refer to the priority rules and determine, from the priority rules, activity indicators that describe the application activity. For example, in
The flow 300 continues at processing block 308, where the system determines sound balancing priorities (“sound priorities”) for the sounds played by the plurality of playlists. The system can generate hierarchies, or levels, of priorities based on hierarchies or levels of classes (e.g., jackpot might be the highest level). In some embodiments, the system can take into consideration an applications own internal priorities and determine sound priorities using those internal priorities or modes. In other embodiments, however, the system can determine the sound priorities irrespective of an applications modes, internal priorities, etc. The system can have its own intelligence to determine the sound balancing priorities. For instance, in
The flow 300 continues at processing block 310, where the system dynamically balances the system sounds based on the sound balancing priorities. For instance, in
According to some embodiments, a wagering game system (“system”) can provide various example devices, operations, etc., to control wagering game system audio. The following non-exhaustive list enumerates some possible embodiments.
This section describes example operating environments, systems and networks, and presents structural aspects of some embodiments.
The memory unit 630 may also include an I/O scheduling policy unit 6 and I/O schedulers 6. The memory unit 630 can store data and/or instructions, and may comprise any suitable memory, such as a dynamic random access memory (DRAM), for example. The computer system 600 may also include one or more suitable integrated drive electronics (IDE) drive(s) 608 and/or other suitable storage devices. A graphics controller 604 controls the display of information on a display device 606, according to some embodiments.
The input/output controller hub (ICH) 624 provides an interface to I/O devices or peripheral components for the computer system 600. The ICH 624 may comprise any suitable interface controller to provide for any suitable communication link to the processor unit 602, memory unit 630 and/or to any suitable device or component in communication with the ICH 624. The ICH 624 can provide suitable arbitration and buffering for each interface.
For one embodiment, the ICH 624 provides an interface to the one or more IDE drives 608, such as a hard disk drive (HDD) or compact disc read only memory (CD ROM) drive, or to suitable universal serial bus (USB) devices through one or more USB ports 610. For one embodiment, the ICH 624 also provides an interface to a keyboard 612, selection device 614 (e.g., a mouse, trackball, touchpad, etc.), CD-ROM drive 618, and one or more suitable devices through one or more firewire ports 616. For one embodiment, the ICH 624 also provides a network interface 620 though which the computer system 600 can communicate with other computers and/or devices.
The computer system 600 may also include a machine-readable medium that stores a set of instructions (e.g., software) embodying any one, or all, of the methodologies for control wagering game system audio. Furthermore, software can reside, completely or at least partially, within the memory unit 630 and/or within the processor unit 602. The computer system 600 can also include a sound control module 637. The sound control module 637 can process communications, commands, or other information, to control wagering game system audio. Any component of the computer system 600 can be implemented as hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein.
The CPU 726 is also connected to an input/output (“I/O”) bus 722, which can include any suitable bus technologies, such as an AGTL+ frontside bus and a PCI backside bus. The I/O bus 722 is connected to a payout mechanism 708, primary display 710, secondary display 712, value input device 714, player input device 716, information reader 718, and storage unit 730. The player input device 716 can include the value input device 714 to the extent the player input device 716 is used to place wagers. The I/O bus 722 is also connected to an external system interface 724, which is connected to external systems (e.g., wagering game networks). The external system interface 724 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 722 is also connected to a location unit 738. The location unit 738 can create player information that indicates the wagering game machine's location/movements in a casino. In some embodiments, the location unit 738 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 738 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 706 can include additional peripheral devices and/or more than one of each component shown in
In some embodiments, the wagering game machine 706 includes a sound control module 737. The sound control module 737 can process communications, commands, or other information, where the processing can control wagering game system audio.
Furthermore, any component of the wagering game machine 706 can include hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein.
The mobile wagering game machine 800 includes several input/output devices. In particular, the mobile wagering game machine 800 includes buttons 820, audio jack 808, speaker 814, display 816, biometric device 806, wireless transmission devices (e.g., wireless communication units 812 and 824), microphone 818, and card reader 822. Additionally, the mobile wagering game machine can include tilt, orientation, ambient light, or other environmental sensors.
In some embodiments, the mobile wagering game machine 800 uses the biometric device 806 for authenticating players, whereas it uses the display 816 and the speaker 814 for presenting wagering game results and other information (e.g., credits, progressive jackpots, etc.). The mobile wagering game machine 800 can also present audio through the audio jack 808 or through a wireless link such as Bluetooth.
In some embodiments, the wireless communication unit 812 can include infrared wireless communications technology for receiving wagering game content while docked in a wager gaming station. The wireless communication unit 824 can include an 802.11G transceiver for connecting to and exchanging information with wireless access points. The wireless communication unit 824 can include a Bluetooth transceiver for exchanging information with other Bluetooth enabled devices.
In some embodiments, the mobile wagering game machine 800 is constructed from damage resistant materials, such as polymer plastics. Portions of the mobile wagering game machine 800 can be constructed from non-porous plastics which exhibit antimicrobial qualities. Also, the mobile wagering game machine 800 can be liquid resistant for easy cleaning and sanitization.
In some embodiments, the mobile wagering game machine 800 can also include an input/output (“I/O”) port 830 for connecting directly to another device, such as to a peripheral device, a secondary mobile machine, etc. Furthermore, any component of the mobile wagering game machine 800 can include hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein.
The wagering game machine 900 comprises a housing 912 and includes input devices, including value input devices 918 and a player input device 924. For output, the wagering game machine 900 includes a primary display 914 for displaying information about a basic wagering game. The primary display 914 can also display information about a bonus wagering game and a progressive wagering game. The wagering game machine 900 also includes a secondary display 916 for displaying wagering game events, wagering game outcomes, and/or signage information. While some components of the wagering game machine 900 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 900.
The value input devices 918 can take any suitable form and can be located on the front of the housing 912. The value input devices 918 can receive currency and/or credits inserted by a player. The value input devices 918 can include coin acceptors for receiving coin currency and bill acceptors for receiving paper currency. Furthermore, the value input devices 918 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 900.
The player input device 924 comprises a plurality of push buttons on a button panel 926 for operating the wagering game machine 900. In addition, or alternatively, the player input device 924 can comprise a touch screen 928 mounted over the primary display 914 and/or secondary display 916.
The various components of the wagering game machine 900 can be connected directly to, or contained within, the housing 912. Alternatively, some of the wagering game machine's components can be located outside of the housing 912, while being communicatively coupled with the wagering game machine 900 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 914. The primary display 914 can also display a bonus game associated with the basic wagering game. The primary display 914 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 900. Alternatively, the primary display 914 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 918. The player can initiate play by using the player input device's buttons or touch screen 928. The basic game can include arranging a plurality of symbols along a pay line 932, 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 900 can also include an information reader 952, 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 952 can be used to award complimentary services, restore game assets, track player habits, etc.
The wagering game table 1060 includes multiple player stations 1001, 1002, 1003, and 1004. Each player station may include one or more controls and devices (e.g., chairs 1015, 1016, 1017, 1018, speakers 1011, 1012, 1013, 1014, displays 1031, 1032, 1033, 1034, peripherals, etc.). The speakers 1011, 1012, 1013, 1014 produce audio respectively for the player stations 1001, 1002, 1003, 1004. In some embodiments, additional speakers 1071, 1072, 1073, 1074 may be positioned at each corner of the wagering game table 1060 instead of, or in addition to speakers 1011, 1012, 1013, 1014 that are centered, or nearly centered, at each of the player stations 1001, 1002, 1003, 1004. For instance, see
In some embodiments, a player at player station 1001 can play a primary, or “base,” wagering game from a wagering game application. The primary wagering game is different from a secondary, or “bonus,” game application. A secondary game application may be presented as a result of activity that occurs within the primary wagering game. The community game server 1050 may provide the community wagering game application as the secondary or bonus application. The primary wagering game application may be specific to only the player station 1001 (i.e., a wagering game controlled by a player at the player station 1001 and not controlled by any other player at any of the other player stations 1002, 1003, or 1004). For example, a player can play a slot application at the player station 1001. The player station 1001 can present the slot application at the display 1031. However, in some embodiments, a player can play the community wagering game with other players at the wagering game table 1060 (e.g., some or all of the player stations 1001, 1002, 1103, 1004 present the community wagering game on each of the monitors 1031, 1032, 1033, 1034). Each of the monitors 1031, 1032, 1033, 1034 can present a different perspective of the community wagering game to each of the respective player stations 1001, 1002, 1003, 1004. Each player at each of the stations 1001, 1002, 1003, 1004 may also have different identities (e.g., control different game characters, control different game objects, etc.) in the community wagering game. The wagering game application (e.g., slot game) and the community wagering game application can be separate and independent applications. For example, the community wagering game application may be a bonus wagering game application that launches and runs independent of individual wagering game applications running at any of the player stations 1001, 1002, 1003, or 1004. In some embodiments, each of the player stations 1001, 1002, 1003, and 1004 may be considered separate wagering game machines that are consolidated into the wagering game table 1060. Any of the player stations 1001, 1002, 1003, 1004, therefore, may include separate processors, separate memory stores, separate hardware, etc. In other embodiments, the wagering game table 1060 may have a single processor that controls all four player stations 1001, 1002, 1003, and 1004.
The community game server 1050 can control content in the community wagering game that is relevant to all player stations 1001, 1002, 1003, 1004 and can also control content in the same community wagering game that it relevant to only the player station 1001. For example, in the community game one of the players, such as a player associated with player station 1001, may perform an action (e.g., perform wagering or other game activity using control 1021) that causes an event 1007 to occur within the community wagering game. In some embodiments, the event 1007 is triggered by player input from the player station 1001, and not by player input from any of the other player stations 1002, 1003, 1004. In other embodiments, however, the event 1007 may relate only to the player station, even if the event 1007 is caused or triggered by input from group game activity or from additional player input from the other stations 1002, 1003, and 1004. As a result, the event 1007 for, or about, the player station 1001 may be referred to as a location-specific, or station-specific, event that is specific to (e.g., only relates to) the player station 1001, and for which only a player at the player station 1001 would be interested in hearing the sound effect for the station-specific event. For instance, one game character or actor may be assigned to a player account associated with the player station 1001. The one game character or actor may be controlled by the player seated at the player station 1001. The one game character or actor may perform activities within the community wagering game that are different from other characters or actors from other player accounts at the other player stations 1002, 1003, and 1004. The one game character or actor may trigger the event 1007 in the community wagering game application that is specific the player station 1001. The event may be, for example, an explosion effect that occurs in the community wagering game, but is specific for the player station 1001. As a result, a player at the player station 1001 would be interested in hearing a sound effect 1071 of the event 1007, but other players at the other player stations 1002, 1003, and 1004 would not be interested in hearing the sound effect 1071 (e.g., an explosion sound) for the event 1007. Thus, the community game server 1050 recognizes that the station-specific event 1007 is specific only for the player station 1001. The community game server 1050 selects a sound script(s) 1091 that plays a sound for the event 1007 so that the audio field 1047, which presents the sound effect 1071, is primarily directed toward the chair 1015 or a player seated in the chair 1015 (e.g., only comes from the speaker 1011). The sound script(s) 1091, or audio playlist, references sound files for sound effects, including a reference to the sound effect 1071 (e.g., explosion sounds) for the event 1007, and includes scripting that defines characteristics or settings of the sound effects 1071 (e.g., settings that define volume levels, treble levels, bass levels, audio balance levels, panning levels, etc.). The scripting may be one or many different types of scripting languages, such as XML, JavaScript, a proprietary script, etc. The sound script(s) 1091 may be a configuration file (e.g., an XML file, a txt file, etc.), a web file (e.g., a hypertext markup language (HTML) document), etc. In some embodiments, the sound script(s) 1091 is a setting, or record, in a database. In some embodiments, sound script(s) 1091 is stored on a machine-readable storage medium (e.g., stored in a memory location, stored on a disk, etc.).
In some embodiments, the sound script(s) 1091 includes scripting instructions that only play sound for the speaker 1011. For example, in
In other embodiments, instead of selecting one script that includes sound control instructions and/or settings for only the player station 1001, the community game server 1050 may use a single script that includes sound control settings for all speakers 1011, 1012, 1013, and 1014. For example, in
In yet other embodiments, the community game server 1050 may generate or detect parameter values for sound settings and pass the parameter values into the sound script(s) 1091 as parameters. For example in
In some embodiments, the system 1000 can play a station-specific sound and modify background sound settings for the specific station using a group of scripts that change audio track sound settings and play sounds according to the audio track sound settings. For example, in
Returning to
In other embodiments, the wagering game table 1060 may include seating configurations and/or shapes that are different from those shown in
Returning to
Further, in some embodiments, the system 1000 can further synchronize or modify base game sounds from a base game, such as a slot game being played at the player station 1001 concurrently, simultaneously, etc. with the sound effect 1071 for the event 1007 at the player station 1001. For example, the system 1000 can attenuate base game sounds at the same time that the sound effect 1071 plays for the event 1007.
Embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments of the inventive subject matter may take the form of a computer program product embodied in any tangible medium of expression having computer readable program code embodied in the medium. The described embodiments may be provided as a computer program product, or software, that may include a machine-readable storage 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 storage medium includes any mechanism that stores information in a form readable by a machine (e.g., a wagering game machine, computer, etc.). For example, machine-readable storage media includes read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media (e.g., CD-ROM), flash memory machines, erasable programmable memory (e.g., EPROM and EEPROM); etc. Some embodiments of the invention can also include machine-readable signal media, such as any media suitable for transmitting software over a network.
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, and claims priority benefit of, U.S. application Ser. No. 12/797,756 filed 10 Jun. 2010, which claims priority benefit of Provisional U.S. Application No. 61/187,134 filed 15 Jun. 2009. The Ser. No. 12/797,756 application and the 61/187,134 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 |
5977469 | Smith | Nov 1999 | A |
6040831 | Nishida | Mar 2000 | A |
6047073 | Norris | Apr 2000 | A |
6068552 | Walker et al. | May 2000 | A |
6081266 | Sciammaella | Jun 2000 | A |
6110041 | Walker et al. | Aug 2000 | A |
6146273 | Olsen | Nov 2000 | A |
6217448 | Olsen | Apr 2001 | B1 |
6254483 | Acres | Jul 2001 | B1 |
6293866 | Walker et al. | Sep 2001 | B1 |
6309301 | Sano | Oct 2001 | B1 |
6339796 | Gambino | Jan 2002 | B1 |
6342010 | Slifer | Jan 2002 | B1 |
6350199 | Williams et al. | Feb 2002 | B1 |
6520856 | Walker et al. | Feb 2003 | B1 |
6628939 | Paulsen | Sep 2003 | B2 |
6632093 | Rice et al. | Oct 2003 | B1 |
6647119 | Slezak | Nov 2003 | B1 |
6652378 | Cannon | Nov 2003 | B2 |
6656040 | Brosnan | Dec 2003 | B1 |
6749510 | Giobbi | Jun 2004 | B2 |
6769986 | Vancura | Aug 2004 | B2 |
6832957 | Falconer | Dec 2004 | B2 |
6848996 | Hecht et al. | Feb 2005 | B2 |
6860810 | Cannon et al. | Mar 2005 | B2 |
6927545 | Belliveau | Aug 2005 | B2 |
6843723 | Joshi | Sep 2005 | B2 |
6939226 | Joshi | Sep 2005 | B1 |
6960136 | Joshi et al. | Nov 2005 | B2 |
6968063 | Boyd | 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 |
7033276 | Walker et al. | Apr 2006 | B2 |
7040987 | Walker et al. | May 2006 | B2 |
7082572 | Pea et al. | Jul 2006 | B2 |
7112139 | Paz Barahona et al. | Sep 2006 | B2 |
7156735 | Brosnan et al. | Jan 2007 | B2 |
7169052 | Beaulieu et al. | Jan 2007 | B2 |
7181370 | Furem et al. | Feb 2007 | B2 |
7208669 | Wells et al. | Apr 2007 | B2 |
7228190 | Dowling et al. | Jun 2007 | B2 |
7269648 | Krishnan et al. | Sep 2007 | B1 |
7355112 | Laakso | Apr 2008 | B2 |
7364508 | Loose et al. | Apr 2008 | B2 |
7367886 | Loose et al. | May 2008 | B2 |
7449839 | Chen et al. | Sep 2008 | B1 |
7479063 | Pryzby et al. | Jan 2009 | B2 |
7495671 | Chemel et al. | Feb 2009 | B2 |
7550931 | Lys et al. | Jun 2009 | B2 |
7559838 | Walker et al. | Jul 2009 | B2 |
7594851 | Falconer | Sep 2009 | B2 |
7666091 | Joshi et al. | Feb 2010 | B2 |
7682249 | Winans et al. | Mar 2010 | B2 |
7722453 | Lark et al. | May 2010 | B2 |
7753789 | Walker et al. | Jul 2010 | B2 |
7798899 | Acres | Sep 2010 | B2 |
7806764 | Brosnan et al. | Oct 2010 | B2 |
7811170 | Winans et al. | Oct 2010 | B2 |
7867085 | Pryzby et al. | Jan 2011 | B2 |
7883413 | Paulsen | Feb 2011 | B2 |
7901291 | Hecht et al. | Mar 2011 | B2 |
7901294 | Walker | Mar 2011 | B2 |
7918728 | Nguyen et al. | Apr 2011 | B2 |
7918738 | Paulsen | Apr 2011 | B2 |
7951002 | Brosnan | May 2011 | B1 |
7972214 | Kinsley et al. | Jul 2011 | B2 |
8029363 | Radek et al. | Oct 2011 | B2 |
8079902 | Michaelson et al. | Dec 2011 | B2 |
8083587 | Okada | Dec 2011 | B2 |
8087988 | Nguyen et al. | Jan 2012 | B2 |
8100762 | Pryzby et al. | Jan 2012 | B2 |
8113517 | Canterbury et al. | Feb 2012 | B2 |
8167723 | Hill et al. | May 2012 | B1 |
8172682 | Acres et al. | May 2012 | B2 |
8184824 | Hettinger et al. | May 2012 | B2 |
8187073 | Beaulieu et al. | May 2012 | B2 |
8221245 | Walker et al. | Jul 2012 | B2 |
8231467 | Radek | Jul 2012 | B2 |
8282475 | Nguyen et al. | Oct 2012 | B2 |
8414372 | Cannon et al. | Apr 2013 | B2 |
8425332 | Walker et al. | Apr 2013 | B2 |
8435105 | Paulsen | May 2013 | B2 |
8506399 | Pryzby et al. | Aug 2013 | B2 |
8591315 | Gagner et al. | Nov 2013 | B2 |
8613667 | Brunell | Dec 2013 | B2 |
8622830 | Radek et al. | Jan 2014 | B2 |
8740701 | Berry | Jun 2014 | B2 |
8747223 | Pryzby | Jun 2014 | B2 |
8814673 | Brunell et al. | Aug 2014 | B1 |
8827805 | Caporusso | Sep 2014 | B1 |
8840464 | Brunell et al. | Sep 2014 | B1 |
8912727 | Brunell et al. | Dec 2014 | B1 |
9011247 | Gronkowski et al. | Apr 2015 | B2 |
9070249 | Radek | Jun 2015 | B2 |
9076289 | Radek | Jul 2015 | B2 |
9087429 | Brunell et al. | Jul 2015 | B2 |
9214062 | Pryzby et al. | Dec 2015 | B2 |
9367987 | Brunell et al. | Jun 2016 | B1 |
9520014 | Moshier | Dec 2016 | B1 |
9547952 | Brunell et al. | Jan 2017 | B2 |
20010021666 | Yoshida et al. | Sep 2001 | A1 |
20020055978 | Joon-Boo et al. | May 2002 | A1 |
20020077170 | Johnson et al. | Jun 2002 | A1 |
20020010018 | Lemay et al. | Jul 2002 | A1 |
20020142825 | Lark et al. | Oct 2002 | A1 |
20020142846 | Paulsen | Oct 2002 | A1 |
20020160826 | Gomez et al. | Oct 2002 | A1 |
20030007648 | Currell | Jan 2003 | A1 |
20030017865 | Beaulieu et al. | Jan 2003 | A1 |
20030002246 | Kerr | Feb 2003 | A1 |
20030064804 | Wilder | Apr 2003 | A1 |
20030064808 | Hecht et al. | Apr 2003 | A1 |
20030073489 | Hecht | Apr 2003 | A1 |
20030073490 | Hecht | Apr 2003 | A1 |
20030073491 | Hecht | Apr 2003 | A1 |
20030114214 | Barahona | Jun 2003 | A1 |
20030130033 | Loose | Jul 2003 | A1 |
20030132722 | Chansky et al. | Jul 2003 | A1 |
20040048657 | Gauselmann | Mar 2004 | A1 |
20040072610 | White et al. | Apr 2004 | A1 |
20040142747 | Pryzby | Jul 2004 | A1 |
20040160199 | Morgan et al. | Aug 2004 | A1 |
20040166932 | Lam et al. | Aug 2004 | A1 |
20040166940 | Rothschild | Aug 2004 | A1 |
20040178750 | Belliveau | Sep 2004 | A1 |
20040180712 | Forman et al. | Sep 2004 | A1 |
20040209692 | Schober et al. | Oct 2004 | A1 |
20050026686 | Blanco | Feb 2005 | A1 |
20050032575 | Goforth | Feb 2005 | A1 |
20050043090 | Pryzby et al. | Feb 2005 | A1 |
20050043092 | Gauselmann | Feb 2005 | A1 |
20050044500 | Orimoto et al. | Feb 2005 | A1 |
20050054440 | Anderson et al. | Mar 2005 | A1 |
20050054441 | Landrum | Mar 2005 | A1 |
20050054442 | Anderson | Mar 2005 | A1 |
20050077843 | Benditt | Apr 2005 | A1 |
20050116667 | Mueller et al. | Jun 2005 | A1 |
20050128751 | Roberge et al. | Jul 2005 | A1 |
20050153776 | Lemay et al. | Jul 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 |
20050170890 | Rowe et al. | Aug 2005 | A1 |
20050174473 | Morgan et al. | Aug 2005 | A1 |
20050200318 | Hunt et al. | Sep 2005 | A1 |
20050239545 | Rowe | Oct 2005 | A1 |
20050239546 | Hedrick et al. | 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 |
20060073881 | Pryzby et al. | Apr 2006 | A1 |
20060076908 | Morgan et al. | Apr 2006 | A1 |
20060178189 | Walker et al. | Aug 2006 | A1 |
20060244622 | Wray | Nov 2006 | A1 |
20060252522 | Walker et al. | Nov 2006 | A1 |
20060252523 | Walker et al. | Nov 2006 | A1 |
20060253781 | Pea et al. | Nov 2006 | A1 |
20060287037 | Thomas | Dec 2006 | A1 |
20060287081 | Osawa | Dec 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 |
20070155469 | Johnson | Jul 2007 | A1 |
20070155494 | Wells | Jul 2007 | A1 |
20070185909 | Klein | Aug 2007 | A1 |
20070189026 | Chemel et al. | Aug 2007 | A1 |
20070191108 | Brunet De Courssou et al. | Aug 2007 | A1 |
20070218970 | Patel et al. | Sep 2007 | A1 |
20070218974 | Patel et al. | Sep 2007 | A1 |
20070219000 | Aida | Sep 2007 | A1 |
20070243928 | Iddings | Oct 2007 | A1 |
20070291483 | Lys | Dec 2007 | A1 |
20070293304 | Loose et al. | Dec 2007 | A1 |
20080009347 | Radek | Jan 2008 | 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 |
20080139284 | Pryzby | Jun 2008 | A1 |
20080143267 | Neuman | Jun 2008 | A1 |
20080161108 | Dahl et al. | Jul 2008 | A1 |
20080176647 | Acres | Jul 2008 | A1 |
20080188291 | Bonney et al. | Aug 2008 | A1 |
20080194319 | Pryzby et al. | Aug 2008 | A1 |
20080214289 | Pryzby et al. | Sep 2008 | A1 |
20080231203 | Budde et al. | Sep 2008 | A1 |
20080234026 | Radek | 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 | Woodward et al. | Jun 2009 | A1 |
20090298579 | Radek 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 |
20090233705 | Lemay et al. | Sep 2009 | A1 |
20090270167 | Ajiro et al. | Oct 2009 | A1 |
20090318223 | Langridge et al. | Dec 2009 | A1 |
20100022298 | Kukita | Jan 2010 | A1 |
20100022305 | Yano | Jan 2010 | A1 |
20100029385 | Garvey | 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 |
20100248815 | Radek | Sep 2010 | A1 |
20100273555 | Beerhorst | Oct 2010 | A1 |
20100277079 | Van Der Veen et al. | Nov 2010 | A1 |
20100298040 | Joshi et al. | Nov 2010 | A1 |
20100309016 | Wendt et al. | Dec 2010 | A1 |
20100317437 | Berry | 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 |
20110092288 | Pryzby et al. | Apr 2011 | A1 |
20110118018 | Toyoda | May 2011 | A1 |
20110118034 | Jaffe et al. | May 2011 | A1 |
20110190052 | Takeda et al. | Aug 2011 | A1 |
20110201411 | Lesley et al. | Aug 2011 | A1 |
20120009995 | Osgood | Jan 2012 | A1 |
20120040738 | Lanning et al. | Feb 2012 | A1 |
20120115608 | Pfeifer | May 2012 | A1 |
20120129601 | Gronkowski et al. | May 2012 | A1 |
20120122571 | DeSimone et al. | Jul 2012 | A1 |
20120178523 | Greenberg et al. | Jul 2012 | A1 |
20120178528 | Brunell et al. | Jul 2012 | A1 |
20130005458 | Kosta et al. | Jan 2013 | A1 |
20130017885 | Englman et al. | Jan 2013 | A1 |
20130150163 | Radek et al. | Jun 2013 | A1 |
20130184078 | Brunell et al. | Jul 2013 | A1 |
20130310178 | Pryzby | Nov 2013 | A1 |
20140073430 | Brunell et al. | Mar 2014 | A1 |
20140228121 | Berry | Aug 2014 | A1 |
20140228122 | Berry et al. | Aug 2014 | A1 |
20140335956 | Brunell et al. | Nov 2014 | A1 |
20140378225 | Caporusso et al. | Dec 2014 | A1 |
20160292955 | Gronkowski et al. | Oct 2016 | A1 |
Number | Date | Country |
---|---|---|
1439507 | Jul 2004 | EA |
1439507 | Jul 2004 | EP |
WO-2004086320 | Oct 2001 | WO |
WO-2004014501 | Feb 2004 | WO |
WO-2004075128 | Sep 2004 | WO |
WO-2004075129 | Sep 2004 | WO |
WO-2005113089 | Dec 2005 | WO |
WO-2005114598 | Dec 2005 | WO |
WO-2005114599 | Dec 2005 | WO |
WO-2005117647 | Dec 2005 | WO |
WO-2006017444 | Feb 2006 | WO |
WO-2006017445 | Feb 2006 | WO |
WO-2006033941 | Mar 2006 | WO |
WO-2006039284 | Apr 2006 | WO |
WO-2006039323 | Apr 2006 | WO |
WO-2006125013 | Nov 2006 | WO |
WO-2007022294 | Feb 2007 | WO |
WO-2007022343 | Feb 2007 | WO |
WO-2007061904 | May 2007 | WO |
WO-2007133566 | Nov 2007 | WO |
WO-2008057538 | May 2008 | WO |
WO-2008063391 | May 2008 | WO |
WO-2008137130 | Nov 2008 | WO |
WO-2009054930 | Apr 2009 | WO |
WO-2010048068 | Apr 2010 | WO |
WO-2011005797 | Jan 2011 | WO |
WO-2011005798 | Jan 2011 | WO |
WO-2011014760 | Feb 2011 | WO |
20041110 | Aug 2005 | ZA |
Entry |
---|
“U.S. Appl. No. 12/965,749 Office Action”, dated Mar. 18, 2015, 28 Pages. |
“U.S. Appl. No. 13/094,560 Office Action”, dated Apr. 10, 2015, 11 Pages. |
Co-pending U.S. Appl. No. 14/677,660, filed Apr. 2, 2015, 46 pages. |
“U.S. Appl. No. 12/965,749 Office Action”, dated Sep. 4, 2014, 33 Pages. |
“U.S. Appl. No. 14/080,272 Office Action”, dated Oct. 23, 2014, 5 Pages. |
Co-pending U.S. Appl. No. 14/480,397, filed Sep. 8, 2014, 39 pages. |
“U.S. Appl. No. 12/965,749 Final Office Action”, dated Apr. 30, 2014, 40 Pages. |
“U.S. Appl. No. 13/094,560 Final Office Action”, dated May 23, 2014, 9 Pages. |
“U.S. Appl. No. 13/388,118 Final Office Action”, dated May 23, 2014, 11 Pages. |
“U.S. Appl. No. 12/965,749 Final Office Action”, dated Dec. 15, 2014, 32 Pages. |
Co-pending U.S. Appl. No. 14/446,081, filed Jul. 29, 2014, 40 pages. |
“U.S. Appl. No. 14/480,397 Office Action”, dated Aug. 4, 2016, 17 pages. |
U.S. Appl. No. 12/797,756, Dec. 16, 2010, filed Jun. 10, 2010, Berry, Robert G., et al. |
U.S. Appl. No. 12/860,467, Feb. 24, 2011, filed Aug. 20, 2010, Radek, Paul J. |
U.S. Appl. No. 12/965,749, filed Dec. 10, 2010, Brunell, Edward G., et al. |
U.S. Appl. No. 12/971,544, filed Dec. 17, 2010, Brunell, Edward G., et al. |
U.S. Appl. No. 13/094,701, filed Apr. 26, 2011, Brunell, Edward G., et al. |
U.S. Appl. No. 13/094,811, filed Apr. 26, 2011, Brunell, Edward G., et al. |
U.S. Appl. No. 13/109,427, filed May 17, 2011, Brunell, Ed et al. |
U.S. Appl. No. 13/204,225, filed Aug. 5, 2011, Caporusso, Vito M., et al. |
U.S. Appl. No. 13/094,560, filed Apr. 26, 2011, Brunell, Edward G., et al. |
U.S. Appl. No. 14/080,272, filed Nov. 14, 2013, Brunell, Edward G., et al. |
“Coyote Moon”, IGT http://web.archive.org/web/20131213220054/http://media.igt.com/marketing/Promotionalliterature/GamePromolit_111E3-29BC7.pdf 2005 , 2 pages. |
“Elvis Little More Action”, 24Hr-Slots http://www.24hr-slots.co.uk!WagerWorks/Eivis_ALMA.html Sep. 5, 2009 , 4 pages. |
“PCT Application No. PCT/US10/41111 International Preliminary Report on Patentability”, dated Oct. 24, 2011 , 13 pages. |
“PCT Application No. PCT/US10/41111 International Search Report”, dated Sep. 1, 2010 , 12 pages. |
“PCT Application No. PCT/US10/41112 International Preliminary Report on Patentability”, dated Aug. 31, 2012 , 4 pages. |
“PCT Application No. PCT/US10/41112 International Search Report”, dated Sep. 2, 2010 , 11 pages. |
“PCT Application No. PCT/US10/43886 International Preliminary Report on Patentability”, dated May 3, 2012 , 4 pages. |
“PCT Application No. PCT/US10/43886 International Search Report”, dated Sep. 16, 2010 , 12 pages. |
“U.S. Appl. No. 12/797,756 Office Action”, dated Nov. 7, 2013 , 7 Pages. |
“U.S. Appl. No. 12/860,467 Office Action”, dated Jan. 17, 2013 , 16 pages. |
“U.S. Appl. No. 12/965,749 Final Office Action”, dated Apr. 22, 2013 , 30 pages. |
“U.S. Appl. No. 12/965,749 Office Action”, dated Nov. 8, 2012 , 30 pages. |
“U.S. Appl. No. 12/965,749 Office Action”, dated Dec. 17, 2013 , 35 Pages. |
“U.S. Appl. No. 12/971,544 Final Office Action”, dated Mar. 14, 2013 , 38 pages. |
“U.S. Appl. No. 12/971,544 Office Action”, dated Nov. 6, 2012 , 43 pages. |
“U.S. Appl. No. 13/094,560 Office Action”, dated Mar. 30, 2012 , 13 pages. |
“U.S. Appl. No. 13/094,560 Office Action”, dated Dec. 6, 2013 , 9 Pages. |
“U.S. Appl. No. 13/094,701 Final Office Action”, dated Nov. 28, 2012 , 14 pages. |
“U.S. Appl. No. 13/094,701 Office Action”, dated Mar. 27, 2012 , 26 pages. |
“U.S. Appl. No. 13/094,811 Final Office Action”, dated Dec. 24, 2013 , 15 Pages. |
“U.S. Appl. No. 13/094,811 Office Action”, dated Apr. 3, 2012 , 16 pages. |
“U.S. Appl. No. 13/094,811 Office Action”, dated Jun. 21, 2013 , 19 pages. |
“U.S. Appl. No. 13/204,225 Final Office Action”, dated Sep. 25, 2013 , 16 Pages. |
“U.S. Appl. No. 13/204,225 Office Action”, dated Feb. 27, 2013 , 19 pages. |
“U.S. Appl. No. 13/204,225 Office Action”, dated Jun. 22, 2012 , 23 pages. |
“U.S. Appl. No. 13/382,738 Final Office Action”, dated Mar. 12, 2014 , 23 Pages. |
“U.S. Appl. No. 13/382,738 Office Action”, dated Sep. 24, 2013 , 24 Pages. |
“U.S. Appl. No. 13/382,738 Office Action”, dated Feb. 7, 2013 , 41 pages. |
“U.S. Appl. No. 13/382,783 Office Action”, dated Feb. 28, 2013 , 26 pages. |
“U.S. Appl. No. 13/382,783 Final Office Action”, dated Oct. 4, 2013 , 22 Pages. |
“U.S. Appl. No. 13/382,783 Office Action”, dated Jul. 25, 2013 , 20 Pages. |
“U.S. Appl. No. 13/388,118 Office Action”, dated Oct. 11, 2013 , 9 Pages. |
Gusella, Riccardo et al., “An Election Algorithm for a Distributed Clock Synchronization Program”, Berkley http://www.eecs.berkeley.edu/Pubs/TechRpts/1986/CSD-86-275.pdf Dec. 1985 , 19 pages. |
NYPHINIX13, , “Star Wars Cloud City Slot Bonus—IGT”, YouTube http://www.youtube.com/watch?v=wfYL9hjLxg4 Mar. 18, 2010 , 1 page. |
“U.S. Appl. No. 14/677,660 FAIIP Office Action”, dated Dec. 21, 2017, 7 pages. |
“U.S. Appl. No. 14/255,757 Office Action”, dated Jun. 15, 2017, 23 pages. |
“U.S. Appl. No. 14/677,660 FAIIP PreInterview Communication”, dated Sep. 5, 2017, 5 pages. |
Number | Date | Country | |
---|---|---|---|
20140228121 A1 | Aug 2014 | US |
Number | Date | Country | |
---|---|---|---|
61187134 | Jun 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12797756 | Jun 2010 | US |
Child | 14254656 | US |