Patent Grant
10339757
A portion of the disclosure of this patent document contains material that 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, to providing secondary game 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.
In an effort to develop new games and gaming enhancements, one or more manufacturers have developed technology to present secondary content simultaneously with presentation of wagering games. While the secondary content can add to the entertainment value of a wagering game machine, it can also present certain challenges. For example, if a primary wagering game and the secondary content are controlled by separate sources, then coordination of content can be challenging.
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 operations performed by some embodiments while the third section describes additional example embodiments. The fourth section describes example operating environments while the fifth section presents some general comments.
For purposes of the present detailed description, 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.”
Furthermore, for purposes of the present detailed description, the terms “wagering games,” “gambling,” “slot game,” “casino game,” and the like include games in which a player places at risk a sum of money or other representation of value, whether or not redeemable for cash, on an event with an uncertain outcome, including without limitation those having some element of skill. In some embodiments, the wagering game may involve wagers of real money, as found with typical land-based or online casino games. In other embodiments, the wagering game may additionally, or alternatively, involve wagers of non-cash values, such as virtual currency, and therefore may be considered a social or casual game, such as would be typically available on a social networking web site, other web sites, across computer networks, or applications on mobile devices (e.g., phones, tablets, etc.). When provided in a social or casual game format, the wagering game may closely resemble a traditional casino game, or it may take another form that more closely resembles other types of social/casual games.
Further, some embodiments of the inventive subject matter describe examples of providing secondary betting (also referred to as secondary wagering) via an associated mobile device in a network wagering venue (e.g., an online casino, a wagering game website, a wagering network, etc.) using a communication network. Embodiments can be presented over any type of communications network that provides access to wagering games, such as a public network (e.g., a public wide-area-network, such as the Internet), a private network (e.g., a private local-area-network gaming network), a peer-to-peer network, 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 utilize specific services, such as account-based wagering services (e.g., account-based wagering game websites, account-based casino networks, etc.).
This section provides an introduction to some embodiments.
Wagering games are expanding in popularity. Wagering game enthusiasts expect continuous innovations to the wagering game experience. As such, wagering game companies are interested in creating and providing innovative wagering games and gaming features to the demanding public. As mentioned previously, some wagering game manufacturers have developed ways to present primary wagering game content and secondary content. Some embodiments of the inventive subject matter include providing secondary content via a mobile device. The secondary content provides a way to make one or more secondary bets (also referred to as secondary wagers) on the primary wagering game content. In some examples, the secondary content is independent from the primary wagering game content (e.g., the secondary content originates from and/or is controlled by a different content source, a different content provider, a different content manufacturer, etc. than that of the primary wagering game content).
In some examples, a secondary content controller is communicatively coupled to a wagering game machine. The secondary content controller can be independent of (e.g., function independently from) the wagering game machine. For example, the secondary content controller may not be native to the original manufacturing of the wagering game machine or may be an add-on to the wagering game machine. For instance, the secondary content controller can be inserted into an expansion slot of the wagering game machine. The secondary content controller includes wireless communication capabilities, such as a Bluetooth beacon. The secondary content controller can pair a mobile device to the wagering game machine. The secondary content controller can further determine appropriate times to pair the mobile device, such as only when the wagering game machine is being used (e.g., when a wagering game session (“gaming session”) has been initiated, when the wagering game machine has been funded, etc.).
When paired, the mobile device can present content to make a secondary bet on the primary wagering game content. In some examples, the secondary content controller can determine when primary wagering game content on the wagering game machine is in a state that would permit secondary wagering. For example, the secondary content controller can determine whether the primary wagering game content is in a playing state that pertains to options for a secondary bet presented on the mobile device. The secondary content can, via the paired connection with the mobile device, prevent or enable secondary betting based on the state of the primary wagering game content.
In some examples, the secondary content controller can detect and/or intercept certain communications made by the wagering game machine pertinent to the primary wagering game content. In some instances, the secondary content controller can function as a proxy for the communications. For example, the secondary content controller can, as the proxy, obtain funds from a monetary balance associated with the primary wagering game content. The secondary content controller can use the funds to fund the one or more secondary bets related to the secondary content. In some instances, the secondary content controller can, as the proxy, detect events that occur in the primary wagering game to determine whether the one or more secondary bets having winning outcomes. In some instances, the secondary content controller can, as the proxy, add the winnings of the one or more secondary bets to the monetary balance associated with the primary wagering game content. Further, the secondary content controller, as the proxy, can communicate information to an accounting system to ensure that using some of the funds associated with the primary wagering game content complies with given accounting protocols and rules required by the accounting system for the primary wagering game content.
The mobile device 130 is configured to present secondary content 103 from which a secondary bet can be made on whether certain events will occur via the primary content 102. The mobile device 130 controls and presents the secondary content 103 on a display 131 of the mobile device 130 at the same time that the primary content 102 is presented on the display 163 of the wagering game machine 160. In some embodiments, the secondary content 103 is independent of the primary content 102. For instance, the primary content 102 may come from a different source and/or a different content provider than for the secondary content 103 (e.g., the primary content controller 161 controls game content provided by a first game provider while the mobile device 130 controls content provided by a different game provider). In some embodiments, the mobile device 130 operates independently from the primary content controller 161. For instance, the mobile device 130 can have separate hardware, software, firmware, or a combination thereof, from that of the primary content controller 161. Further, the mobile device 130 can use separate processors and separate memory devices than those used by the wagering game machine 160 and/or the primary content controller 161. Further, the mobile device 130 can run a betting application that is separate and independent from a wagering game application run by the primary content controller 161.
The wagering game machine 160 can include a secondary content controller 162 configured to communicate with internal components and devices of the wagering game machine 160. In some instances, the secondary content controller 162 is configured to perform certain functions associated with secondary content 103 (e.g., with secondary content presented via the wagering game machine 160, with the secondary content 103 presented via the mobile device 130, etc.). For example, the secondary content controller 162 can take funds from a gaming session used for the primary content 102 (e.g., from a credit meter 120) to pay for the secondary bet.
The secondary content controller 162 is also configured to communicate with devices external to the wagering game machine 160, such as the mobile device 130. For instance, the secondary content controller 162 can include a wireless beacon that detects when the mobile device 130 is within a given distance (i.e., proximity range). The secondary content controller 162 can detect a request to pair with the mobile device 130, such as via a Bluetooth pairing procedure. The secondary content controller 162 can determine whether the primary content 102 is in a state that would permit pairing. For example, the secondary content controller 162 can determine whether a gaming session has been initiated. For instance, the secondary content controller 162 can determine whether the credit meter 120 is funded. In another instance, the secondary content controller 162 can determine whether a player has logged into the wagering game machine 160 using an account-based-wagering (ABW) player account. After pairing with the mobile device 130, the secondary content controller 162 can initiate a secondary betting session for the mobile device 130 separate from the gaming session associated with the primary content 102.
Once paired, the mobile device 130 presents, via the display 131, the secondary content 103. In some embodiments, a mobile application (“app”) of the mobile device 130 presents the secondary content 103 via a betting interface 190. The betting interface 190 presents options to make a secondary bet on the primary content 102. For example, the betting options respond to user input (e.g., selection of user interface objects), which specify a secondary bet, or “side bet” on whether certain events will occur via the primary content 102. For example, the betting interface 190 includes a bet type control 105 from which a user can select a type of side bet (e.g., a proposition bet, a matching bet, etc.). The betting interface 190 also includes a game selection control 107 by which a user can select a game presented via the wagering game machine 160. In some embodiments, the game selection control 107 automatically selects the Zeus slot game if the wagering game machine 160 only offers one wagering game. Furthermore, the mobile device 130 can present an indicator graphic 109. The indicator graphic 109 specifies the primary content 102 (e.g., the indicator graphic 109 is matched with the indicator graphic 104 of the primary content 102). In some embodiments, the secondary content controller 162 provides the information about the primary content 102 through a wireless connection made with the mobile device 130.
The betting interface 190 further includes a bet parameters section 111. The bet parameters section 111 includes a bet control 115, which signifies a type of event that could potentially occur during play of the primary content 102, such as occurrence of a certain symbol 117. A bet control 113 can be selected by the user to specify how many instances of the symbol 117 should appear in the primary content 102 for the secondary bet. A bet control 119 can be used to specify how the symbol 117 should appear (e.g., in a payline, in a primary game, in a bonus game, in a tournament, etc.) A bet control 121 can be used to specify a number of playing rounds by which the secondary bet should occur (e.g., within a given number of spins, within a short period of time, etc.). The secondary bet specified in the bet parameters section 111 indicates that the user of the mobile device bets that five of the symbols 117 will occur in a single payline of the Zeus game within the next 10 spins of the reels 108. A bet meter 123 indicates the cost required to make a specific secondary bet. A bet control 125 can be selected to place the secondary bet. An additional control 127 is configured to make an additional secondary bet, if desired. In some instances, the secondary content controller 162 is configured to take credits from the credit meter 120 (associated with the primary content 102) to pay for the secondary bet. In other words, when the bet control 125 is selected, the secondary content controller 162 determines whether it is authorized to take funds from the gaming session for the primary content 102 (such as by taking sufficient credits specified in the credit meter 120) or whether it must fund the secondary bet in another way (such as by pulling the funds from a player account independent from the gaming session for the primary content 102).
The secondary bet specified in the bet parameters section 111 is just one example of a secondary bet. For instance, the secondary bet type control 105 signifies that the secondary bet is a proposition bet. A proposition bet is a side bet made regarding either the occurrence or non-occurrence, during a game (usually a gambling game), of an event in the game. In some instances, the event does not directly affecting the game's outcome. In other instances the event may be related to an outcome of the game. For example, the proposition bet may be that a given event will occur which is also an event specified in a pay table for the primary content 102. In other examples, the given event may not be specified in a pay table for the primary content 102, but may nonetheless potentially occur during the primary game presented via the primary content 102. In other examples, secondary bet type control 105 may specify other types of bets, such as a “matching” bet, which either mirrors or substantially “matches” a bet made by the player of the primary content 102. For a “matching” type of bet, the bet parameters section 111 may be blank, and the secondary bet would merely match the betting of a player of the wagering game machine 160. In other examples, for a “matching” type of bet, the bet parameters section 111 may include controls by which the user can select a multiplier of the bets made by a player of the wagering game machine 160.
In some embodiments, the secondary content controller 162 is configured to determine whether the primary content 102 is available for secondary betting. For example, the secondary content controller 162 can determine whether the primary content 102 is in an active playing state that could result in a primary game event that is available as one of the betting options of the secondary content 103. If the primary content 102 is in an active playing state (e.g., the reels 108 are spinning), then the secondary content controller 162 can prevent secondary betting via the mobile device 130 until the primary content 102 is in a non-active playing state. For instance, the secondary content controller 162 can send messages to the mobile device 130 (via the pairing) to indicate when the primary content 102 is in an active playing state and when the primary content 102 is in a non-active playing state or idle state. The mobile device 130 can enable and/or disable betting options via the secondary content 103 based on the messages provided by the secondary content controller 162.
Further, in some embodiments, the secondary content controller 162 is configured to detect whether the certain events associated with the secondary bet occur via the primary content 102. If, according to the occurrence of the events for the primary content 102, the secondary bet wins, then the secondary content controller 162 is configured to apply the winnings back to the source from whence the funds for the secondary bet originated. For example, if the secondary content controller 162 is authorized to access funds from the gaming session for the primary content 102, then the secondary content controller 162 can add the winnings back to the credit meter 120. In another instance, if the secondary content controller 162 took funds from a wagering game player account, then the secondary content controller 162 can add the winnings back to the wagering game player account. Further, in some embodiments, if funds for the bet were taken from the credit meter 120, winnings could be returned to the wagering game player account, or vice versa.
Although
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 storage 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, or accompanying conceptual diagram.
In
In some embodiments, the system 300 is configured to associate the mobile device 330 with the wagering game machine 330. For example, in
In some examples, the casino accounting system 340 is a casino accounting host configured to communicate with the wagering game machine 360 to send, and receive, financial data (e.g., accounting data) for financial transactions related to wagering games presented on the wagering game machine 360. In some embodiments, the casino accounting system 340 is incorporated into, or directly connected to, the wagering game machine 360. For instance, the casino accounting system 340 may be contained entirely within the cabinet or casing for the wagering game machine 360. The casino accounting system 340 may be embedded into the wagering game machine 360, included on the motherboard of the wagering game machine 360, attached as a daughterboard, plugged into a backplane or riser card expansion slot of the motherboard of the wagering game machine 360, etc. In other embodiments, however, the casino accounting system 340 may be separate from the wagering game machine 360. For example, the casino accounting system 340 may be incorporated into a server separate from the wagering game machine 360.
In some embodiments, the secondary content controller 362 is contained within the wagering game machine 360. For example, the secondary content controller 362 may be contained entirely within a cabinet or casing for the wagering game machine 360. In some embodiments, the secondary content controller 362 may be embedded into the wagering game machine 360 as an embedded system, a Slot Machine Interface Board (SMIB), a single board computer, a single board smart interface, a system host board, etc. In some embodiments, the secondary content controller 362 may be included on a motherboard of the wagering game machine 360 or attached as a daughterboard. In some embodiments, the secondary content controller 362 may be plugged into a backplane or riser card expansion slot of a motherboard of the wagering game machine 360. Examples of expansion slots may include an Industry Standard Architecture (ISA) expansion slot, a Conventional Peripheral Component Interconnect (PCI) expansion slot, a PCI eXtended (PCI-X) expansion slot, a PCI Express (PCI-e) expansion slot, and so forth. In some embodiments, the secondary content controller 362 is connected via a serial link to the primary game controller 361.
In some embodiments, the secondary content controller 362 is independent from the primary content controller 361, the casino accounting system 340, and/or other elements of the wagering game machine 360 that were originally incorporated into the wagering game machine 360 by a manufacturer of the wagering game machine 360. For example, in some embodiments, the secondary content controller 362 may be incorporated into a part of the wagering game machine 360 after the wagering game machine 360 has been manufactured and/or shipped to a casino. In some embodiments, the secondary content controller 362 is incorporated into a device separate from the wagering game machine 360. The separate device can be communicatively coupled to the wagering game machine 360, such as via a wired connection or a wireless link.
In some embodiments, the secondary content controller 362 is dedicated for communications using the Slot Accounting System (SAS) protocol commercially available from International Game Technology (IGT) of Las Vegas, Nev. Therefore, in some examples, the secondary content controller 362 communicates with the primary content controller 361 using the SAS protocol. The secondary content controller 362 can intercept SAS communications made by the primary content controller 361 to one or more internal components of the wagering game machine 360 and/or to one or more devices external to the wagering game machine 360, such as to the casino accounting system 340. For instance, the secondary content controller 362 intercepts SAS communications made by the primary content controller 361 that are directed to the casino accounting system 340. For example, the secondary content controller 362 determines, based on the intercepted SAS communications, that funds were added to the gaming session of the wagering game machine 360.
At stage, “B,” the secondary content controller 362 communicates with the wireless communication unit 363 to begin to transmit a pairing beacon signal. In some embodiments, the wireless communication unit 363 is incorporated onto the secondary content controller 362. In other embodiments, the wireless communication unit 363 is separate from the secondary content controller 362. In some embodiments, when the wireless communication unit 363 begins transmitting the pairing beacon, the secondary content controller 162 can cause a visual indicator to appear on the wagering game machine 360 (e.g., a specific colored light effect associated with the secondary content controller 362, such as a blue and green flashing LED light effect).
At stage “D,” the secondary content controller 362 is configured to generate pairing data 414 that will securely link the secondary content controller 362 to the mobile device 330. The wireless communication unit communicates some, or all, of the pairing data 414 to the wireless communication unit 333 of the mobile device 330. The pairing data 414 can include a pairing identifier that uniquely identifies the pairing session between the mobile device 330 and the secondary content controller 362. The pairing identifier can be used at another stage to associate a secondary bet to the pairing. In some embodiments, the wireless communication unit 363 utilizes a wireless technology standard for exchanging data over short distances. In some examples, the wireless technology standard is the Bluetooth wireless technology standard, which uses short-wavelength Ultra-High-Frequency (UHF) radio waves in the ISM band from 2.4 to 2.485 GHz, and which has a range of about 60 meters. In some embodiments, the wagering game machine 360 may be placed on a casino floor, or other location, with various other wagering game machines in close proximity. Therefore, in some embodiments, the wireless communication unit 363 is configured to limit a wireless broadcast range for pairing signals to approximately 0.5 to 1 meter. Because the wireless communication unit 353 broadcasts a limited range, then only mobile devices within that range will detect the signal. Likewise, if other nearby wagering game machines broadcast in limited ranges, the mobile device 330 will detect fewer pairing signals from the other wagering game machines.
In some examples, at stage “D,” the secondary content controller 362 can determine whether primary wagering game content is in a state that would permit pairing. For example, the secondary content controller 362 can determine whether a gaming session has been initiated via the wagering game machine 360. For instance, the secondary content controller 362 can determine whether a credit meter is funded. In another instance, the secondary content controller 362 can determine whether a player has logged into the wagering game machine 360 using an account-based-wagering (ABW) player account. The description for
At stage “C,” the mobile device 330 responds to the pairing beacon by launching a native application (“app”) related to secondary betting. In some embodiments, the pairing beacon is coded in a certain way to be recognized by the app of the mobile device 330. For example, when the mobile device 330 comes within the communication range of the wireless communication unit 363, the app “wakes up” on the mobile device 330. The app on the mobile device 330 can specify a pairing with the particular wagering game machine 330. For example, if the secondary content controller 362 causes the wagering game machine 360 to present a visual indicator regarding the pairing (e.g., the blue and green flashing LED lights), the app can indicate in a message that states, for instance, “Pair with the wagering game machine that has the blue and green flashing lights?” The user of the mobile device 330 could then acknowledge whether or not to pair with the wagering game machine 360 that has the visual indicator. For example, the user could select a button in the app that is marked “Initiate Pairing.” The button can have a blue and green flashing effect surrounding the button, which corresponds to the blue and green flashing effect on the wagering game machine 360. When the button is selected, the pairing procedure between the mobile device 330 and the secondary content controller 362 would be initiated.
In some examples, the secondary content controller 362 can detect whether the player of the wagering game machine 360 should be notified of the pairing. If the player is notified, and authorizes the pairing, then, at a different stage, the secondary content controller 362 will have the option of using funds from the wagering game machine 360 to fund secondary bets made via the mobile device 330. In some examples, the secondary content controller 362 can detect whether the mobile device 330 has identification data that matches corresponding data for the gaming session of the wagering game machine 360. For instance, the mobile device 330 or the app may store in settings identifying information about the player (e.g., a configuration setting that indicates the owner of the mobile device, contact information for the user stored in a profile related to the app, etc.). In other examples, the user of the mobile device 330 may have to sign in to the app using a user identifier (e.g., a user ID and password, a name, a code, etc.). The mobile device 330 can communicate the identifier, or information associated with the identifier (e.g., the user ID and/or password, the name, the code, etc.). The secondary content controller 362 can determine whether matching information is stored for the gaming session on the wagering game machine 360. For instance, if the player of the wagering game machine 360 has provided a matching user identifier (e.g., a matching user ID and/or password, a matching name, a matching code, etc.) then the secondary content controller 362 can compare the identifiers and/or associated information, to detect a match. In some embodiments, the app could present a prompt via the mobile device 330 to ask whether the player of the wagering game machine 360 should be notified about the pairing (e.g., a prompt that states “Request authorization to access gaming funds from the wagering game machine?”). If the secondary content controller 362 detects that the player of the wagering game machine 360 should be notified of the pairing, then the secondary content controller 362 requests a response from the player.
In other embodiments, however, the secondary content controller 362 does not notify the player of the pairing. For instance, if the user of the mobile device 330 wants to use their own player account to fund secondary bets, then the secondary bet may be independent of any funds associated with the gaming session on the wagering game machine 360. Thus, if the secondary content controller 362 determines that the player should not be notified (e.g., the user of the mobile device 330 indicated not to notify the player of the wagering game machine 360, the identifying information from the mobile device 330 does not match identifying information from the wagering game machine 360, etc.), then the secondary content controller 362 does not notify the player and the pairing continues. In some examples, the secondary content controller 362 may require a pairing code and/or an authorization code be entered into a user interface for the wagering game machine 360. For instance, the app on the mobile device 330 may generate an authorization code (e.g., a personal identifier number (PIN)) that the player of the wagering game machine 360 must enter into the wagering game machine 360 to authorize funds sharing. The mobile device 330 submits the authorization code to the secondary content controller 362 so that the secondary content controller 362 can compare the authorization code when it is entered into the wagering game machine 360. The wagering game machine 360 then presents a prompt for the authorization code via the user interface of the wagering game machine 360. If the player of the wagering game machine 360 is the same as the user of the mobile device 330 or if the player of the wagering game machine 360 desires to provide the user of the mobile device 330 access to funds from the gaming session, then the player can enter the authorization code into the user interface. Otherwise, the player can deny the request.
At stage “D” and “E,” the secondary content controller 362 and the secondary content controller 331 perform respective pairing procedures to link the wagering game machine 360 to the mobile device 330. For example, the secondary content controller 362 transmits the pairing identifier to the secondary content controller 331. The secondary content controller 331 can acknowledge the pairing identifier. The pairing establishes a Bluetooth connection 320 between the secondary content controller 362 and the secondary content controller 331.
In some embodiments, for security purposes, only one mobile device might may be permitted to be pair with a wagering game machine at the same time. Yet, in other embodiments, multiple mobile devices can be paired with a single wagering game machine. For example, if all of the mobile devices are part of a shared community game or if multiple users want to bet on activity of the player of the wagering game machine 360. In this case, each of the users of the multiple mobile devices may utilize separate wagering game player accounts (“player accounts”) of an Account Based Wagering System (ABWS) to fund their individual secondary bets via their respective mobile devices. In some embodiments, users of the mobile devices can transfer coins between player accounts using a mobile device app installed on each of the mobile devices. This could be done by Advanced Funds Transfers (AFTs) between the player accounts.
As previously mentioned, the wagering game machine 360 may present a visual indicator regarding the pairing (e.g., blue and green flashing LED lights). The app can also present a matching visual indicator (e.g., a blue and green flashing effect surrounding a button) so that the user of the mobile device 330 can be visually informed that the pairing will be with the wagering game machine 360. When the secondary content controller 362 and the mobile device 330 are paired, the visual indicator presented via the wagering game machine 360 can change to signify the pairing (e.g., the blue and green flashing LED lights displayed on the wagering game machine 360 can change to a non-flashing blue light). Similarly, the matching visual indicator on the app can change to signify the pairing (e.g., the blue and green flashing indicator on the app can change to a non-flashing blue light).
Referring momentarily back to
At stage “G,” the secondary content controller 362 communicates data 365 regarding the primary wagering game content. For example, the secondary content controller 362 can send to the mobile device 330 information that explains what primary wagering game content is being played on the wagering game machine 360. The secondary content controller 362 can also send to the mobile device 330 information about game elements, game functions, game history, player data, etc., that can result in events that may possibly occur during the gaming session. The information can be used to present possible betting parameters via the app of the mobile device 330, which betting parameters are related to events of the gaming session related to the primary wagering game content. For example, referring momentarily back to
In some embodiments, at stage “H,” after the secondary content controller 362 sends the information 365 to the secondary content server 380, the secondary content server 380 uses the information 365 to determine the secondary content to provide to the app, and then provides secondary content data 381 to the mobile device 330. For instance, the secondary content server 380 may provide theme information, icons, or other information/content relevant to the primary wagering game. The app can use the information and content to present the bet possibilities. In some examples, the secondary content server 380 can generate a list of possible game events to present in the app of the mobile device 330. For instance, the secondary content server 380 may (a) generate entries for a dropdown menu or list of events for secondary wagers, (b) specify types of events that may occur in a primary wagering game, (c) specify functions or settings of the primary wagering game, etc. For example, if the secondary content server 380 were used in
Though not shown, in some embodiments, other controls for the secondary content 103 may instead, or in addition, include controls to predict a timing for the event(s), a location for the event(s), a pattern for the event(s), conditions for the event(s), etc. For example, the controls could specify whether the event(s) occur in a primary wagering game versus in a bonus game or a secondary wagering game. In some examples, the controls could specify whether the event(s) occur in the gaming session for the primary content 102 or in another game for another player in a tournament or community game. In some examples, the controls could specify whether the event(s) occur within a given time period. In some examples, the controls could specify whether specific reel symbols will appear in specific sequences. In some examples, the controls could specify whether a certain number of wins or losses will occur within a given number of game play rounds or a time period.
Referring back to
Furthermore, in some embodiments, the secondary content controller 362 and/or the secondary content server 380 can send to the mobile device 330 additional content that adds to the experience of being paired with the wagering game machine 360. For example, the secondary content controller 362 and/or the secondary content server 380 can send to the mobile device 330 side games to play along with the primary wagering game content, bonus rounds that connect to the primary wagering game content, etc.
Still referring to
In
After the secondary bet is initiated, the secondary content controller 331 sends secondary bet data 334 to the secondary content server 380. For instance, the secondary content controller 331 sends a signal to the secondary content server 380 that the bet control 125 (shown in
Referring still to
Returning momentarily to
Referring first to the example of
Still referring to stage “L1,” after the secondary content controller 362 determines that it is authorized to access session funds for the gaming session of the wagering game machine 360, the secondary content controller 362 requests a portion of game session funds equivalent to an amount of the secondary bet.
Returning momentarily to
Referring to stage “L1,” in some examples, the secondary content controller 362 transfers funds to the secondary content server 380 using SAS spoofing. The secondary content controller 362 then makes the casino accounting system 340 aware of the reduction in game credits on the wagering game machine 360, via AFT, as if the credits were bets for the primary wagering game, even though they are secondary bets on the secondary content. The casino accounting system 340 is configured to receive data messages from, and send data messages to, either or both of the primary content controller 361 and the secondary content controller 362. For example, the casino accounting system 340 is configured to send and receive data messages using the SAS protocol. The casino accounting system 340 is configured to perform operations that can separately account for certain financial transactions made for the primary wagering game content. For example, the casino accounting system 340 is configured to communicate with the primary content controller 361 to account for financial data associated when monetary value is added to a credit meter for the primary wagering game content, when bets are made for the primary wagering game content, when winning outcomes occur for the primary wagering game content, when win amounts are added to the credit meter, when a balance of funds (e.g., an amount in the credit meter) is cashed out of the wagering game machine 360, or for any other type of financial activity associated with the primary wagering game content.
In some embodiments, the primary content controller 361 is specifically manufactured and/or configured by the same game provider that manufactures the wagering game machine 360. Thus, in some examples, the programming for the primary content controller 361 is specifically configured for use with the wagering game machine 360. Further, the secondary content controller 362 may originate from a different manufacturer than the manufacturer for the wagering game machine 360 or the primary content controller 361. The secondary content may come from a third-party source separate from a game provider for the primary wagering game content. Therefore, in some embodiments, the primary content controller 361, and various financial related elements of the wagering game machine 360 (e.g., the ticket-in-ticket-out system, the betting controls, the cash-out button, the ticket printer, etc.) may be specifically programmed to respond for only the primary wagering game content and not for the secondary content or the mobile device 330. As such, the primary content controller 361 may be configured to communicate directly with the casino accounting system 340 and not with the secondary content controller 362.
According to some embodiments, the secondary content controller 362 is configured to send commands to the primary content controller 361 that would cause the primary content controller 361 to send a communication to the casino accounting system 340 regarding the amount of funds requested from the gaming session. For example, the secondary content controller 362 spoofs the casino accounting system 340 and sends a SAS command to the primary content controller 361 to transfer a certain amount of funds to the casino accounting system 340.
Referring now to stage “M1,” when the primary content controller 361 transfers the funds (using a SAS communication that indicates credit data 541), the credit meter on the wagering game machine 360 reduces by the amount for the secondary bet specified in the credit data 541. In some examples, the wagering game machine 360 has a credit meter, but the app on the mobile device 330 does not. Individual credits can be transferred from the credit meter on the wagering game machine 360 when needed for a secondary bet of the app on the mobile device 130. In other examples, however, more credits can be transferred from the credit meter than are needed for one secondary bet. For example, the app on the mobile device 330 may have a second credit meter. Some, or all, of the funds can be transferred off the wagering game machine 360 and stored via the secondary content server 380 and/or via the mobile device 330. If the all of the funds are transferred to the mobile device 330, the mobile device 330 (and/or the secondary content server 380) can transfer funds back to the wagering game machine 360 for bets made on the primary wagering game content (which could then cause the first credit meter on the wagering game machine 360 to have credits). In some examples, some funds are on the first credit meter for multiple primary game bets and some funds are on the second credit meter for multiple secondary bets. The wagering game machine 360 can access the funds from the first credit meter for bets made for the primary wagering game content. The mobile device 330 can access the funds from the second credit meter for secondary bets.
Referring still to stage “M1,” the primary content controller transfers the funds using a SAS communication that indicates the credit data 541. The credit data 541 is directed to the casino accounting system 340. However, the secondary content controller 362 intercepts the credit data 541 sent by the primary content controller 361 and spoofs the casino accounting system 340. In other words, the secondary content controller 362 intercepts messages sent by the primary content controller 361 to the casino accounting system 340, uses data from the messages, and then sends modified data to the casino accounting system 340. For instance, at stage “N1,” the secondary content server 362 intercepts the credit data 541 and sends a modified SAS message to the casino accounting system 340. The modified SAS message indicates that the amount of funds from the credit data 541 was actually spent on a wager on the primary wagering game, even though the funds are not spent on a wager of the primary wagering game. In some embodiments, the secondary content controller 362 provides SAS communications to the secondary content server 380 (e.g., money transactions, play activity of the wagering game machine 360, etc.) and/or to any other device or component associated with a wagering game network (e.g., to a primary wagering game server, to an account-based wagering server, etc.), in addition to sending SAS communications to the primary content controller 361 and the casino accounting system 340.
At stage “O1,” the secondary content controller 362 can associate the funds with the pairing identifier and then send funds data 583 to secondary content server 380. The funds data 583 can specify the amount of the funds from the credit data 541 as well as the pairing identifier.
At stage “P1,” the secondary content server 380 transacts the secondary bet. For example, the secondary content server 380 creates a secondary session account (e.g., an anonymous account) into which the funds are deposited for secondary bets. In some embodiments, the secondary session account may be created earlier, such as when the wagering game machine 360 and the mobile device 330 are paired. A “virtual wallet” program of the secondary content sever 380 controls the funds in the secondary session account. As a security measure, the virtual wallet program may require the pairing identifier before it will deposit funds into the secondary session account. In some embodiments, the secondary session account is a floating session account such that when the mobile device 330 is unpaired with the wagering game machine 330, the credits can remain with the mobile device 330 (and/or with the secondary content server 380) until the mobile device 330 pairs with another wagering game machine.
Also at stage “P1,” the secondary content server 380 sends data 535 to the mobile device 330 via the secure wireless network 322. The data 535 indicates that the secondary bet was transacted. The mobile device 330 receives the data 535 and the app indicates that the secondary bet was transacted. For example, the app can show an indicator that the secondary bet was placed. In some embodiments, the secondary content controller 331 can show a secondary credit meter that increments in the app for the amount of the bet, and then decrements when the bet is made. In other embodiments, however, the app does not show a credit meter. Further, in some embodiments, after the mobile device 330 receives the data 535, if there is a time parameter or playing round parameter associated with the secondary bet, the app can begin counting down the time and/or the number of playing rounds of the primary wagering game.
In some embodiments, the secondary content server 380 can communicate directly with the casino accounting system 340 and/or with the account server 370. For example, the secondary content server 380 can send SAS commands or instructions directly to the casino accounting system 340 instead of, or in addition to, sending SAS communications to the secondary content controller 362.
Returning momentarily to
As mentioned previously,
In
Referring to
At stage “M2,” the secondary content server 380 requests funds from the player account to pay for the secondary bet. In one example, the secondary content controller 362 detects login credentials for the player account stored on the account server 370. For example, the login credentials may be provided via the app on the mobile device 330. For instance, when the mobile device 330 pairs with the wagering game machine 360, the app can require login credentials for the player account. In other embodiments, if the mobile device 330 does not pair with the wagering game machine 360, when the user launches the app, the app can require login credentials for the player account. The app communicates those credentials to the secondary content server 380. The app can present a credit meter that shows an amount of credits in the player account.
In some embodiments, the player account can provide funds for any fee associated with wagering game machine 360 and/or the mobile device 330. For example, tournament fees can be paid from the player account prior to pairing. The tournament may be related to games played on the wagering game machine 360 and/or to possible secondary bets made via the app on the mobile device 330.
At stage “N2,” the account server 370 receives the request for the user account and accesses the user account (e.g., using the login credentials provided by the secondary content server 380). The account server 370 then transfers and/or transacts the amount of funds needed for the secondary bet from the player account (e.g., the account server 370 provides transaction data 684 which identifies the funding for the secondary bet). In some embodiments, at stage “O2,” the secondary content controller 362 can detect the communication made by the account server 370 regarding the funds for the secondary bet. The secondary content controller 362 can provide the pairing identifier 683 to identify that the funding is associated with a paired session between the mobile device 330 and the wagering game machine 360.
At stage “P2,” the secondary content server 380 transacts the secondary bet (e.g., provides data 635 which indicates that the funds were attained for the secondary bet and that the secondary bet was transacted). If a credit meter for the player account is shown in the app, then the credit meter decrements by the amount of the secondary bet.
Returning momentarily to
At stage “R,” the secondary content controller 362 detects the events from the primary game event data 765. The secondary content controller 362 can send to the secondary content server 380 data 785 that identifies events from the primary game event data 764. In some embodiments, the secondary content controller 362 filters the primary game events and sends, in the data 785, only information about relevant events to the secondary bet (e.g., the secondary content controller 362 has a filter that detects when an event is relevant to betting parameters set for the secondary bet). In other embodiments, the data 785 includes all primary game event data, which the secondary content server 380 can parse and/or analyze to determine which of the data is relevant to the secondary bet.
In some embodiments, the secondary content controller 362 sends game event data directly to the mobile device 330. In other examples, the mobile device 330 can take information directly from the wagering game machine 360 (e.g., sniff events, such as game outcome data, from the secondary content controller 362 via the Bluetooth connection 320). In some embodiments, the mobile device 330 can take information from the secondary content server 380 via the secure wireless link.
Returning momentarily to
Referring back to
Referring momentarily back to
Referring first to the example of
In
At stage “V2,” the secondary content controller 362 receives the data 966 and sends data 971 to the account server 370. In other embodiments, the secondary content server 380 can instead send the data 966 directly to the account server 370 without intervention by the secondary content controller 362. In such an instance, the secondary content controller 362 may detect that the data 966 was sent to the account server 370 (e.g., the secondary content controller 362 can sniff a SAS communication sent by the secondary content server 380 to the account server 370).
At stage “W2,” the account server 370 receives the data 971 and increases a credit balance for the player account by the win amount for the secondary bet.
While
In
The secondary content controller can include a wireless beacon that detects when the mobile device is within a given distance (i.e., proximity range). The mobile device also includes a wireless beacon which can cause a pairing item to appear on the mobile device as a representation of the wagering game machine even though the wireless beacon is actually associated with the secondary content controller. If the pairing item is selected from the mobile device, the mobile device can send a request to the secondary content controller to pair, such as via the Bluetooth pairing procedure described previously in
The flow 1000 continues at processing block 1004, where the secondary content controller determines whether primary wagering game content on the wagering game machine is available for secondary wagering. For example, the secondary content controller can determine that primary wagering game content of the wagering game machine is in a state that would permit secondary wagering by determining that the wagering game machine has been activated for game play. When the wagering game machine is activated for play, the primary wagering game content is presented and wagers can be made. For example, the secondary content controller can determine that a credit meter of the primary wagering game content is funded. A player may insert or scan a ticket or card using an electronic scanning device of the wagering game machine. The ticket or card is encoded with electronic funds, such as credits. The wagering game machine reads the ticket or card and transfers the electronic funds to an account associated with the wagering game session (“gaming session account”). The gaming session account stores funds temporarily on the wagering game machine to be used for funding wagers on the primary wagering game content. A credit meter associated with the primary wagering game shows the funds.
In some examples, the gaming session account is anonymous. In other examples, the gaming session account is associated with a player account. For instance, instead of scanning a ticket or card that is encoded with funds, a player may instead scan a player card or player device (e.g., RFID device) that is encoded with identifying information for the player and/or an identifier for an account-based-wagering (ABW) player account. The electronic scanning device can read the identifying information and log into the player account via the wagering game machine. In some examples, the system can transfer funds from the player to the gaming session account. In some examples, the player account may not include funds. However, the gaming session may still be activated after the player account logs in. After logging into the player account, the player account can present an option to transfer funds from a financial account (e.g., via electronic funds transfer from a bank account or a credit card) to the player account and/or to the gaming session account. Therefore, in some embodiments, the secondary content controller determines that primary wagering game content of the wagering game machine is in a state that would permit secondary wagering by determining that a player account has logged into the wagering game machine using a player account.
In some examples, the secondary content controller also determines that primary wagering game content of the wagering game machine is in a state that would permit secondary wagering by determining that the primary wagering game content is in non-active, game-play state. A non-active, game play state is a state where a primary wagering game application is not actively presenting a game-play round for the primary wagering game (e.g. is not actively presenting a spin of slot reels, is not actively computing a random-number and/or a random wagering game outcome, is not actively presenting a congratulatory effect for a win event of the primary wagering game, etc.). More specifically, a primary wagering game may experiencing certain events. One type of event is an idle event, where the primary wagering game is not doing anything. A second type of event is a game-start event, which may occur when a “spin” button or “bet” button is activated on a wagering game machine. The game-start event initiates a betting transaction and begins a game play rounds for the primary wagering game. After the game-start event, the primary game may deactivate betting controls for the primary game until after a game-end event occurs. After the game-start event, the primary wagering game may also generate a random game outcome or detect a randomly generated game outcome for the game play round. After the game-start event, the primary wagering game may also present active movement or activity of the primary wagering game elements (e.g., present spinning reels, present a card deal, present movement of a game character, etc.). Further, after the game-start event and after determining the game outcome, the primary wagering game presents a reveal of the game outcome. For example, if the game outcome is a win, the primary wagering game may present a congratulatory game effect. In some examples, after the game-start event, the primary wagering game may also determine whether to present a bonus game and/or bonus content (e.g. present episodic content, launch a community game, present a progressive game event, etc.). At some point after the game-start event, depending on the configuration of the primary wagering game and/or jurisdictional rules, the primary wagering game generates a game-end event, which indicates the end of the game play round. In some examples, the game-end event may occur immediately after the reveal of the game outcome. In other examples, the game-end event may occur after the reveal of the game outcome and after a congratulatory game effect is presented and/or after bonus content is presented. After the game-end event occurs, the primary wagering game activates the betting controls again so that a second bet can be made and a subsequent game play round can begin.
The secondary content controller can detect the game-start events and game-end events. Therefore, in some embodiments, the secondary content controller can determine that the primary wagering game content is in a state that would permit secondary wagering by determining whether the primary wagering game content has generated a game-start event in relation to a game-end event. For instance, if the secondary content controller detects, at a beginning of a gaming session (i.e., after a log-in event, after a gaming session funding event, etc.), that a game-start event has not been generated, then the primary wagering game is in a state that would permit wagering. In another example, if the secondary content controller detects, during a gaming session, that a game-end event has occurred and has not yet been sequentially followed by game-start event, then then the primary wagering game is in a state that would permit wagering. However, if the secondary content controller detects that a game-start event has occurred, but has not yet been followed sequentially by a game-end event, then the primary wagering game is in a state that would not permit wagering
If, at processing block 1004, the secondary content controller determines that the primary wagering game content is not available, the flow 1000 continues at processing block 1006, where the secondary content controller denies pairing of the mobile device with the secondary content controller. For example, the secondary content controller can send a message to the mobile device that the pairing is unavailable. In some example, the secondary content controller may momentarily turn off the pairing functionality.
However, if, at processing block 1004, the secondary content controller determines that the primary wagering game content is available, the flow 1000 continues at processing block 1008, where the secondary content controller pairs with the mobile device.
The flow 1100 starts at processing block 1102, where the secondary content controller detects a request to place a secondary bet via a mobile device. For example, the secondary content controller may detect that a paired mobile device presents an application which presents betting options to place secondary bets on potential primary game events.
The flow 1100 continues at processing block 1104, where the secondary content controller determines whether the primary wagering game content is available for secondary wagering. For example, the secondary content controller can determine whether the primary wagering game is in a non-active, game-play state (e.g., if the primary wagering game is not actively presenting a game-play round for the primary wagering game). Several examples of determining whether a primary wagering game is in a non-active, game-play state were specified previously for processing block 1004 of
Still referring to
Consequently, according to some embodiments, the secondary content controller can ensure that no secondary bets are placed on the mobile device by determining game-play state of the primary wagering game and preventing the mobile device from placing secondary wagers if the primary wagering game is in an active, game-play state. For example, the secondary content controller can send a message to the mobile device to disable betting options as soon as it detects a game-start event. In other examples, the mobile device may disable betting options by default. In that case, the secondary content controller would instead send a message to the mobile device to enable secondary betting only if the secondary content controller detects that a game-end event has occurred and has not yet been followed sequentially by a game-start event.
Referring back to processing block 1104, if the secondary content controller determines that the primary wagering game content is available for secondary wagering, the flow 1100 continues at processing block 1108, where the secondary content controller enables the placement of the secondary bet via the mobile device. For example, the secondary content controller may send a message to the mobile device to enable betting options on the mobile device to place the secondary bet.
In some embodiments, the secondary content controller can determine whether the primary wagering game is a current game-play state that could result in some of the potential game events presented on betting options of the secondary game content, yet still enable secondary betting for other betting options that apply to primary game events that would not occur during the current game-play state. For example, one of the betting control options of the mobile device may be for placing a secondary bet on what might happen in the primary wagering game between certain time periods that will occur subsequent to a current time (e.g., in a minute from now). Therefore, the current, active, game-play state would not be relevant to that betting option. As such, the secondary content controller may permit that betting option to occur, while preventing other betting options on potential primary game events that might occur from the current, active, game-play state.
Further, while the secondary content controller prevents secondary wagering on a primary wagering game, the secondary content controller may enable secondary betting on one or more independent secondary games presented on the wagering game machine, even while the primary wagering game is in an active, game-play state for the primary wagering game.
According to some embodiments, a wagering game system (“system”) can provide various example devices, operations, etc., to providing secondary betting via an associated mobile device. The following non-exhaustive list enumerates some possible embodiments.
Multiple Mobile Devices Paired with the Same Wagering Game Machine.
In some embodiments, the system is configured to pair multiple mobile devices with the same wagering game machine. Thus, different users can bet on different events that occur on the same wagering game machine. In some embodiments, a wagering game machine can provide multiple visual indicators when pairing with multiple mobile devices. For example, the wagering game machine can have multiple overhead visual indicators that flash different colors for different mobile devices that are paired. For instance, a red lighting effect on the wagering game machine's overhead display pertains to a first player's mobile device, whereas a green lighting effect pertains to a second player's mobile device. If more than one wagering game machine in the wireless pairing range, the mobile device's apps could present additional indicia, such as descriptions of game themes for the different wagering game machines, orientation indicators, etc. In some embodiments, if the first player at the wagering game machine is indicated as a social contact of the second player, and if the first player has authorized it, the mobile app for the second player could show information about first player. For example, the mobile app for the second player could show an image of the first player, could indicate which wagering game machine the first player is at, could show win streak data associated with the first player, could show accomplishments by the first player in the gaming session, etc. In some embodiments, the wagering game machine could show credit meter data to the second player if the second player has sufficient authority, such as “spouse” level authority.
Secondary Betting without Pairing.
In some embodiments, the mobile device does not pair with the wagering game machine. Rather, a user can launch an app on a mobile device that will show a listing of wagering game machines on a casino floor. Any one, or more, of the wagering game machines may be selected via the app. One or more secondary bets can be placed for each of the wagering game machines selected via the app. Secondary content controllers for each of the wagering game machines can detect primary content events and provide event data for each of the secondary bets.
Secondary Betting on Progressives.
In some embodiments, the system can pair a mobile device with a wagering game machine and make a secondary game bet related to a progressive game. The secondary bet specifies that if a progressive jackpot were to be won on the wagering game machine within a certain number of game play rounds, then the user that made the secondary bet would get a portion of a reset value of the progressive game. For example, a reset value for a jackpot amount of the progressive game may be five thousand dollars ($5K). The progressive jackpot may increase over time to more than the reset value (e.g., to $1 million) until a player wins the jackpot. The wagering game machine associated with the secondary bet is eligible for the progressive jackpot. An event that occurs on the wagering game machine causes the player to win the progressive jackpot amount (e.g., the player wins the $1 million). Because the user of the mobile device made the secondary bet that the progressive jackpot would be won by the wagering game machine, the user of the mobile device wins some, or all, of the reset value for the progressive jackpot (e.g., $5K). In other examples, the system can provide a secondary bet where a user of a mobile device can place a secondary bet to attempt to win an amount shown a the progressive meter at the time of the secondary game bet.
Secondary Content Controller as Secondary Host.
In some embodiments, the secondary content controller is configured to be a proxy accounting host that intercepts communications between a primary content controller and a casino accounting system. However, in other examples, the secondary content controller can be configured as a secondary host, in additional to the casino accounting system. In this scenario, the primary content controller can work with both the casino accounting system and with the secondary content controller. Further, in some embodiments described previously, the secondary content controller sniffs primary game events that are sent from the primary content controller to a second device different from the secondary content controller. For example, if there is a limit to the number of hosts that can be subscribed to a primary content controller (e.g., as in SAS), and if other hosts are already subscribed to the primary content controller (e.g., a casino accounting system and a progressive game server), the secondary content controller may not be able to connect as a host. In such a scenario, the secondary content controller may instead sniff data communications between the primary content controller and other hosts. However, in other embodiments, the secondary content controller can be configured as a secondary recipient of game event data and does not have to sniff data. For example, if the limit to the number of hosts is not reached for SAS then the secondary content controller can be subscribed as a valid host. In another example, if another protocol is used, such as the Game to System (G2S) protocol, which provides for a vast number of hosts, then the secondary content controller can be subscribed as a valid host. Thus, the secondary content controller can be subscribed to primary game events. Therefore, in such an example, the primary content controller can send the primary game events directly to the secondary content controller as well as to any other hosts that are subscribed to receive the primary game events.
Controlling Secondary Bet Based on Termination Event.
In some embodiments, a termination event may occur before a condition for a secondary bet is satisfied. For example, a mobile device may be linked with a secondary content server. A proposition bet may be made, via the mobile device, that a specific primary wagering game event will occur via a wagering game within a certain number of game plays (e.g., that four specific symbols will occur in a payline within the next 10 spins). In some examples, before the number of game plays have occurred, a termination event may occur that interrupts the conditions associated with the secondary bet. For instance, the mobile device may leave the wireless range of the secondary content controller and may un-pair with the secondary content server before the number of game plays have occurred. In another example, the player that is playing on the wagering game machine may end the wagering game session (e.g., run out of game funds, cash out of the wagering game machine, log off the wagering game machine, etc.) before the number of game plays occur.
In the scenario where the mobile device un-pairs before the conditions of the secondary bet can be satisfied, the system can perform different operations depending on whether the secondary content controller is directly connected to the secondary content server via a back-end communications network, or, instead, whether the mobile device functions as the conduit for communications between the secondary content controller and the secondary content server. In the case where the secondary content controller is directly connected to the secondary content server via a communications network, then, after the mobile device un-pairs, the secondary content server can query the secondary content controller (via the communications network) to determine whether the primary wagering game content is still available (e.g., if there is still money on a credit meter for the primary wagering game and/or if a player account is still logged on to the wagering game machine). If so, then the secondary content controller can communicate game event data directly to the secondary content server via the communications network. The secondary content server can monitor the game events of the primary wagering game until the conditions for the secondary bet have been satisfied (e.g., until the number of game plays have occurred). The secondary content controller can then resolve the secondary bet (e.g., a win or loss based on whether or not there was a win event on the primary wagering game during the number of game plays). The secondary content server can then communicate the results of the secondary bet to the mobile device via a mobile network (e.g., by sending a data communication via a telecommunications network to which the mobile device is connected).
However, after the mobile device un-pairs, if the primary wagering game content is not available (e.g., if funds run out on the credit meter for the primary wagering game before the number of game plays occur and/or if a player account logs off the wagering game machine before the number of game plays occur), the secondary content server can perform a couple of different options.
First, it can cancel the secondary bet, and refund the wagered amounts for the secondary bet. For instance, the secondary content controller can send a coupon for a free game play to an electronic contact identifier (e.g., email, mobile telephone number). In another example, the secondary content controller can transfer the wagered amounts for the secondary bet to a player account associated with the mobile device.
Second, the secondary content server can transfer the secondary bet to a second wagering game machine. For instance, the secondary content server can cause an option to be presented on the mobile device to cancel or transfer bet. If the transfer option is selected, then the secondary content server gives a certain amount of time for the mobile device to pair again with a different wagering game machine that has the same potential event in the condition for the secondary bet. If the mobile device does not pair within the time frame, or if it pairs with a second wagering game machine that does not have the same potential event, then the secondary content server can cancel the secondary bet or extend the time frame. To facilitate the transfer of the secondary bet, the secondary content server can provide, for presentation via the mobile device, a list of other wagering game machines with the same potential event specified by the conditions of the secondary bet (e.g., provide a list of game themes, provide a map to the other wagering game machines, etc.).
The scenarios in the above paragraph indicated some examples of where a mobile device un-pairs before the conditions of the secondary bet can be satisfied and where the secondary content controller is directly connected to the secondary content server via a back-end communications network. In other examples, where a mobile device un-pairs before the conditions of the secondary bet are satisfied and where the secondary content controller is not connected to secondary content server via a back-end communications network (i.e., if the mobile device was functioning as a conduit for communications between the secondary content controller and the secondary content server), then the secondary content server can perform other operations. For instance, the secondary server would not be able to monitor primary game events from the previous wagering game machine from which the mobile device was unpaired. Therefore, the secondary content server can either cancel the bet and refund the bet amount or the secondary content server can offer to transfer the secondary bet (as described in the paragraph above).
In other examples, the secondary content server can cancel a bet and partially refund some of the bet amount. For example, if the conditions of the secondary bet specified that 10 game plays must occur in the primary wagering game, and a termination event occur after only 9 game plays have occurred, the secondary content server can refund 1/10th of the bet amount for the secondary bet. In other examples, such as where the bet amount may not be divisible, the secondary content server can cancel the bet and not refund the game amount, but instead provide another form of compensation, such as a coupon, a discount, a promotional offer, etc., for other gaming or non-gaming activity (e.g., a specific number of free spins for a specific wagering game, a discount on a buffet or other casino merchandise or service, a multiplier for the next time a bonus game occurs, an entry in a raffle drawing, a voucher for a certain number of non-cash points for game play of a non-cash wagering game, a free app, etc.).
In examples where the termination event is that the primary game content becomes no longer available for game play (e.g., the mobile device remains paired, but a player of the wagering game runs out of game funds, cashes out, logs off, or otherwise ends a gaming session for the primary wagering game content), the secondary content server can either cancel the secondary bet or transfer the secondary bet.
This section describes additional example operating environments, systems, networks, etc. and presents structural aspects of some embodiments.
The wagering game machine 1260 also includes one or more input related components and devices (“input components 1262”) configured to control and/or provide input for the wagering games and other content presented via the wagering game machine 1260. For example, the input components 1262 include a touch-screen display by which a user can touch a screen and select certain virtual controls, objects, items, etc. presented on the touch-screen display. In another example, the input components 1262 include a button panel with buttons related to one or more wagering games, application, services, etc. presented via the wagering game machine 1260. The buttons, for example, may indicate betting amounts, payline amounts, spin controls, or other items used to make bets, spin reels, etc. for a wagering game. The buttons may also detect input related to payout mechanisms and/or cashing out a wagering game, such as an activation of a cash-out button used to transfer credits from wagering game credit balances to a cash-out object, card, ticket, account, etc. The buttons may also accept input related to casino services and amenities. In some examples the input components 1262 also includes input devices related to funds, player information, etc. For example, the wagering game machine 1260 includes an information reader that reads information from a card or device and connects to a player account, a customer loyalty account, a financial account, etc. In some examples, the input components 1262 include eye tracking equipment, biometric devices, and so forth.
The wagering game machine 1260 also includes the primary content controller 1263 configured to control content, such as a primary wagering game or other wagering games, provided from a primary source of wagering game content. The primary content controller 1263 can include software and hardware, such as a processor, memory devices, an operating system, game applications, etc. For example, a primary wagering game server 1250 can provide primary game data 1201 to the primary content controller 1263, such as control and application data for one or more client applications controlled by the primary content controller 1263.
The wagering game system architecture 1200 also includes a secondary content controller 1230 configured to communicate with various components of the wagering game machine 1260 to present and control various aspects of independent secondary content using the output components 1261 and the input components 1262 of the wagering game machine 1260. In some examples, the secondary content controller 1230 is similar to the secondary content controller 162 described in
The secondary content controller 1230 includes a detection unit 1234 configured to detect information from the various devices and components of the wagering game machine 1260 including information from the output components 1261 and the input components 1262. For example, the detection module 1234 can detect graphics data 1202 (e.g., graphical and video data) provided from a video card, a graphics engine, or other sources of graphics data of the wagering game machine 1260. The detection module 1234 can send the graphics data 1202 to the controller module 1236. The graphics data 1202 includes a position of primary wagering game content on a display of the wagering game machine 1260 according to default display parameters (e.g., default size of a display area, default display dimensions, etc.). The controller module 1236 can manipulate the graphics data 1202 to move or resize the position of the primary wagering game content relative to the default display parameters. The controller module 1236 can send modified or adapted presentation data 1208 to the output module 1232, such as display coordinates, display boundaries, display sizes, or other display data for the primary wagering game content that has been moved or resized to accommodate the presentation of an independent secondary wagering game. The output module 1232 can receive the adapted presentation data and provide modified output data 1216 to the output components 1261. The output components 1261 can use the modified output data 1216, for example, to move or resize the primary game content on a display device of the wagering game machine 1260. Furthermore, the controller module 1236 can receive secondary game data 1281 from the secondary content server 1280. The controller module 1236 can further include in the adapted presentation data 1208 information about where to position a secondary wagering game relative to the position of the primary game content. The output module 1232 can then incorporate into the modified output data 1216 information about both the secondary game content and the primary game content so that the display device of the wagering game machine 1260 can concurrently present both the primary and secondary game content.
Further, in some embodiments, the detection module 1234 can intercept user input 1203 from the input components 1262 and provide the user input 1203 to the controller module 1236. The controller module 1236 can receive the user input 1203, interpret the user input 1203, and, in some cases, modify the user input 1203 to the adapted presentation data 1208. The controller module 1236 can further provide modified input data 1206 to the primary content controller 1263. For instance, the detection unit 1234 can intercept a touch-screen input from the input components 1262 before the primary content controller 1263 can detect the touch-screen input. The detection unit 1234 can forward the touch-screen input to the controller module 1236. The controller module 1236 can convert or remap the touch-screen input to different coordinates of the touch-screen display that relate to a modified location of primary content on the display as well as to secondary content presented on the display. The controller module 1236 can send the modified input data 1206 to the primary content controller 1263 so that the primary content controller 1263 can control the primary game according to the modified input data 1206. The controller module 1236 can further detect primary game data 1205 generated by the primary content controller 1263 so that the controller module 1236 can generate updates to the adapted presentation data 1208.
The controller module 1236 is further configured to receive information about financial transactions (e.g., from the detection module 1234 via user input 1203 that relates to financial transactions, such as credit transfers, cash outs, etc.). For instance, the controller module 1236 can intercept primary game accounting data 1207, such as SAS messages sent from the primary content controller 1263 directed to the casino accounting system 1290. The controller module 1236 then acts as proxy for the casino accounting system 1290 by generating adapted accounting data 1210, which the controller module 1236 communicates to the primary content controller 1263. Thus, in some embodiments the controller module 1236 interposes itself, or intervenes, between the primary content controller 1263 and the casino accounting system 1290 (e.g., as if the controller module 1236 were an accounting host). For instance, the controller module 1236 initiates a funds transfer between the primary content controller 1263 and the casino accounting system 1290. In some embodiments, the controller module 1236 intercepts the funds transfer from the primary content controller 1263 and provides the funds to the secondary content server 1280 to transact secondary bets. In some embodiments, the secondary content server 1280 can include a SAS module configured to communicate with one or more elements of the wagering game system architecture 1200 regarding one or more types of financial transactions, game events, etc., that use the SAS protocol.
Furthermore, the controller module 1236 can send adapted accounting data 1214 to the casino accounting system 1290. For instance, the controller module 1236 can send accounting data 1214 to the casino accounting system 1290 as if the primary content controller 1263 had initiated a financial transaction. Further, the controller module 1236 can communicate to the casino accounting system 1290 certain SAS communications that satisfy certain accounting rules and requirements associated with the financial transaction.
The wagering game system architecture 1200 can also include an account server 1270 configured to control user related accounts accessible via wagering game networks and social networks. The account server 1270 can store and track player information, such as identifying information (e.g., avatars, screen name, account identification numbers, etc.) or other information like financial account information, social contact information, etc. The account server 1270 can contain accounts for social contacts referenced by the player account. The account server 1270 can also provide auditing capabilities, according to regulatory rules, and track the performance of players, machines, and servers. The account server 1270 can include an account controller configured to control information for a player's account. The account server 1270 can also include an account store configured to store information for a player's account. The account server 1270 can further be configured to provide user information and store information related to a player account and/or a financial account associated with a player (e.g., with a user of the wagering game machine 1260 and/or a user of a mobile device 1223). For example, the controller module 1236 can send accounting data 1220 from the secondary content controller 1230 to the account server 1270. The accounting data 1220 includes information necessary to electronically transfer credits to and/or from the player account and/or financial account associated with the account server 1270.
Referring again to the controller module 1236 of the secondary content controller 1230, in some embodiments, the controller module 1236 sends primary game session data 1225 to the secondary content server 1280. In some embodiments, the primary game session data 1225 includes funding data, such as credits taken from a credit meter of the wagering game machine 1260 and provided to the secondary content server 128 to fund secondary bets. In some embodiments, the primary game session data 1225 includes game event data related to the secondary bet.
The wagering game system architecture 1200 can also include the mobile device 1223. In some examples, the controller module 1236 can communicate with the mobile device 1223, such as via wireless connection. In some embodiments, the secondary content server 1280 can also communicate with the mobile device 1223. For example, the secondary content server 1280 can communicate secondary content data 1224, such as credit data, secondary content, etc.
Each component in the wagering game system architecture 1200 is shown as a separate and distinct element. Some elements may be connected via a communications network 1222 as shown in
The wagering game system architecture 1200 can also include a primary wagering game server 1250 configured to control wagering game content, provide random numbers, and communicate wagering game information, account information, and other information to and from the wagering game machine 1260. The primary wagering game server 1250 can include a content controller configured to manage and control content for presentation on the wagering game machine 1260. For example, the content controller can generate game results (e.g., win/loss values), including win amounts, for games played on the wagering game machine 1260. The content controller can communicate the game results to the wagering game machine 1260. The content controller can also generate random numbers and provide them to the wagering game machine 1260 so that the wagering game machine 1260 can generate game results. The primary wagering game server 1250 can also include a content store configured to contain content to present on the wagering game machine 1260. The primary wagering game server 1250 can also include an account manager configured to control information related to player accounts. For example, the account manager 1253 can communicate wager amounts, game results amounts (e.g., win amounts), bonus game amounts, etc., to the account server 1270. The primary wagering game server 1250 can also include a communication unit configured to communicate information to the wagering game machine 1260 and to communicate with other systems, devices and networks. In some embodiments, the primary wagering game server 1250 can also include a SAS module configured to communicate with one or more elements of the wagering game system architecture 1200 regarding one or more types of financial transactions, game events, etc., that use the SAS protocol.
Each component shown in the wagering game system architecture 1200 is shown as a separate and distinct element connected via a communications network 1222. However, some functions performed by one component could be performed by other components. For example, the primary wagering game server 1250 can also be configured to perform functions of the wagering game machine 1260, and other network elements and/or system devices. In other examples, the secondary content controller 1236 shares or distributes operations with SAS modules of the secondary content server 1280, the casino accounting system 1290, the primary wagering game server 1250, the account server 1270, the wagering game machine 1260, and/or the mobile device 1223. 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 1260) 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 1200 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.
The CPU 1326 is also connected to an input/output (“I/O”) bus 1322, which can include any suitable bus technologies, such as an AGTL+frontside bus and a PCI backside bus. The I/O bus 1322 is connected to a payout mechanism 1308, primary display 1310, secondary display 1312, value input device 1314, player input device 1316, information reader 1318, and storage unit 1330. The player input device 1316 can include the value input device 1314 to the extent the player input device 1316 is used to place wagers. The I/O bus 1322 is also connected to an external system interface 1324, which is connected to external systems 1304 (e.g., wagering game networks). The external system interface 1324 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 1322 is also connected to a location unit 1338. The location unit 1338 can create player information that indicates the wagering game machine's location/movements in a casino. In some embodiments, the location unit 1338 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 1338 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 1306 can include additional peripheral devices and/or more than one of each component shown in
In some embodiments, the wagering game machine 1306 includes a secondary content controller 1337. The secondary content controller 1337 can process communications, commands, or other information, where the processing can provide secondary betting via an associated mobile device.
Furthermore, any component of the wagering game machine 1306 can include hardware, firmware, and/or machine-readable storage media including instructions for performing the operations described herein.
The wagering game machine 1460 illustrated in
Input devices, such as the touch screen 1418, buttons 1420, a mouse, a joystick, a gesture-sensing device, a voice-recognition device, and a virtual input device, accept player input(s) and transform the player input(s) to electronic data signals indicative of the player input(s), which correspond to an enabled feature for such input(s) at a time of activation (e.g., pressing a “Max Bet” button or soft key to indicate a player's desire to place a maximum wager to play the wagering game). The input(s), once transformed into electronic data signals, are output to a CPU for processing. The electronic data signals are selected from a group consisting essentially of an electrical current, an electrical voltage, an electrical charge, an optical signal, an optical element, a magnetic signal, and a magnetic element.
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 that may include a machine-readable storage medium having stored thereon instructions, which may be used to program a computer system 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 (e.g., software, processing application) readable by a machine (e.g., a computer). For example, machine-readable storage media includes magnetic storage medium (e.g., floppy diskette), read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media (e.g., CD-ROM), magneto-optical storage media, flash memory, erasable programmable memory (e.g., EPROM and EEPROM), or other types of media suitable for storing electronic instructions. In addition, embodiments may be embodied in a 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 of U.S. application Ser. No. 14/821,196, filed Aug. 7, 2015, and claims priority benefit of Provisional U.S. Application No. 62/034,646 filed Aug. 7, 2014. The Ser. No. 14/821,196 application and the 62/034,646 application are incorporated herein by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5259613 | Marnell, II | Nov 1993 | A |
| 5265874 | Dickinson et al. | Nov 1993 | A |
| 5326104 | Pease et al. | Jul 1994 | A |
| 5342047 | Heidel et al. | Aug 1994 | A |
| 5412404 | Candy | May 1995 | A |
| 5450938 | Rademacher | Sep 1995 | A |
| 5605506 | Hoorn et al. | Feb 1997 | A |
| 5655961 | Acres et al. | Aug 1997 | A |
| 5919091 | Bell et al. | Jul 1999 | A |
| 5971271 | Wynn et al. | Oct 1999 | A |
| 6146276 | Okuniewics | Nov 2000 | A |
| 6280328 | Holch et al. | Aug 2001 | B1 |
| 6379246 | Dabrowski | Apr 2002 | B1 |
| 6676522 | Rowe et al. | Jan 2004 | B2 |
| 6800029 | Rowe et al. | Oct 2004 | B2 |
| 6846238 | Wells | Jan 2005 | B2 |
| 7025674 | Adams et al. | Apr 2006 | B2 |
| 7335106 | Johnson | Feb 2008 | B2 |
| 7390263 | Acres | Jun 2008 | B1 |
| 7611409 | Muir et al. | Nov 2009 | B2 |
| 7686687 | Cannon et al. | Mar 2010 | B2 |
| 7699703 | Muir et al. | Apr 2010 | B2 |
| 7749081 | Acres | Jul 2010 | B1 |
| 7780517 | Saffari et al. | Aug 2010 | B2 |
| 7850528 | Wells | Dec 2010 | B2 |
| 7867092 | Paulsen | Jan 2011 | B2 |
| 7867095 | Mattice et al. | Jan 2011 | B2 |
| 7892090 | Walker et al. | Feb 2011 | B2 |
| 7905780 | Morrow et al. | Mar 2011 | B2 |
| 7927211 | Rowe et al. | Apr 2011 | B2 |
| 7950996 | Nguyen et al. | May 2011 | B2 |
| 7950999 | Morrow et al. | May 2011 | B2 |
| 7951003 | Russell | May 2011 | B2 |
| 8007361 | Walker et al. | Aug 2011 | B2 |
| 8029364 | Loose et al. | Oct 2011 | B2 |
| 8070590 | Cannon et al. | Dec 2011 | B2 |
| 8083592 | Wells | Dec 2011 | B2 |
| 8088009 | Finnimore et al. | Jan 2012 | B2 |
| 8088014 | Wells | Jan 2012 | B2 |
| 8113956 | Finnimore et al. | Feb 2012 | B2 |
| 8133102 | Dabrowski | Mar 2012 | B2 |
| 8226474 | Nguyen et al. | Jul 2012 | B2 |
| 8241119 | Wells | Aug 2012 | B2 |
| 8241123 | Kelly et al. | Aug 2012 | B2 |
| 8241124 | Kelly et al. | Aug 2012 | B2 |
| 8241127 | Kovacs | Aug 2012 | B2 |
| 8267792 | Buchholz et al. | Sep 2012 | B2 |
| 8282480 | Wells et al. | Oct 2012 | B2 |
| 8282490 | Arezina et al. | Oct 2012 | B2 |
| 8317604 | Wells | Nov 2012 | B2 |
| 8323111 | Finnimore et al. | Dec 2012 | B2 |
| 8328632 | Cannon et al. | Dec 2012 | B2 |
| 8333655 | Gagner et al. | Dec 2012 | B2 |
| 8336697 | Wells | Dec 2012 | B2 |
| 8342935 | Morrow et al. | Jan 2013 | B1 |
| 8348759 | DiMichele et al. | Jan 2013 | B2 |
| 8371937 | Wells | Feb 2013 | B2 |
| 8371942 | Finnimore et al. | Feb 2013 | B2 |
| 8376837 | Gagner et al. | Feb 2013 | B2 |
| 8388424 | Dabrowski | Mar 2013 | B2 |
| 8419526 | Cannon et al. | Apr 2013 | B1 |
| 8430741 | Agarwal et al. | Apr 2013 | B2 |
| 8469800 | Lemay et al. | Jun 2013 | B2 |
| 8475273 | Kelly et al. | Jul 2013 | B2 |
| 8475283 | Guinn et al. | Jul 2013 | B2 |
| 8512144 | Johnson | Aug 2013 | B2 |
| 8529345 | Nguyen | Sep 2013 | B2 |
| 8550900 | Walker et al. | Oct 2013 | B2 |
| 8550903 | Lyons et al. | Oct 2013 | B2 |
| 8597111 | Lemay et al. | Dec 2013 | B2 |
| 8616981 | Guinn et al. | Dec 2013 | B1 |
| 8628418 | Abbot | Jan 2014 | B2 |
| 8678916 | Cannon et al. | Mar 2014 | B2 |
| 8784206 | Gronkowski et al. | Jul 2014 | B1 |
| 8858323 | Nguyen et al. | Oct 2014 | B2 |
| 9335964 | Khatod et al. | May 2016 | B2 |
| 9489794 | Hilbert et al. | Nov 2016 | B2 |
| 9734666 | Gagner et al. | Aug 2017 | B2 |
| 20030054881 | Hedrick et al. | Mar 2003 | A1 |
| 20040142739 | Loose et al. | Jul 2004 | A1 |
| 20050020354 | Nguyen et al. | Jan 2005 | A1 |
| 20050020358 | Cram | Jan 2005 | A1 |
| 20050162337 | Ohashi | Jul 2005 | A1 |
| 20050240873 | Czerwinski et al. | Oct 2005 | A1 |
| 20060143085 | Adams et al. | Jun 2006 | A1 |
| 20060252530 | Oberberger et al. | Nov 2006 | A1 |
| 20070021198 | Muir et al. | Jan 2007 | A1 |
| 20070105613 | Adams et al. | May 2007 | A1 |
| 20070111787 | Adams et al. | May 2007 | A1 |
| 20070243925 | Lemay et al. | Oct 2007 | A1 |
| 20070243934 | Little | Oct 2007 | A1 |
| 20080009344 | Graham et al. | Jan 2008 | A1 |
| 20080076572 | Nguyen et al. | Mar 2008 | A1 |
| 20080113802 | Johnson et al. | May 2008 | A1 |
| 20080113820 | Tedsen et al. | May 2008 | A1 |
| 20080161107 | Johnson | Jul 2008 | A1 |
| 20080234029 | Cannon et al. | Sep 2008 | A1 |
| 20080248865 | Tedesco et al. | Oct 2008 | A1 |
| 20080305862 | Walker et al. | Dec 2008 | A1 |
| 20090042634 | Cannon et al. | Feb 2009 | A1 |
| 20090098943 | Weber et al. | Apr 2009 | A1 |
| 20090104954 | Weber et al. | Apr 2009 | A1 |
| 20090233705 | Lemay et al. | Sep 2009 | A1 |
| 20100087241 | Nguyen et al. | Apr 2010 | A1 |
| 20100210352 | Ansari et al. | Aug 2010 | A1 |
| 20100210353 | Gagner et al. | Aug 2010 | A1 |
| 20110009188 | Adiraju et al. | Jan 2011 | A1 |
| 20110053672 | Gagner et al. | Mar 2011 | A1 |
| 20110195792 | Wells et al. | Aug 2011 | A1 |
| 20110263325 | Atkinson | Oct 2011 | A1 |
| 20120077560 | Cannon et al. | Mar 2012 | A1 |
| 20120108338 | Wells et al. | May 2012 | A1 |
| 20120122558 | Lyons et al. | May 2012 | A1 |
| 20120122560 | Loose et al. | May 2012 | A1 |
| 20130017884 | Price et al. | Jan 2013 | A1 |
| 20130023339 | Davis et al. | Jan 2013 | A1 |
| 20130053136 | Lemay et al. | Feb 2013 | A1 |
| 20130053148 | Nelson et al. | Feb 2013 | A1 |
| 20130059648 | Rowe et al. | Mar 2013 | A1 |
| 20130072310 | Wells | Mar 2013 | A1 |
| 20130084963 | Shorrock et al. | Apr 2013 | A1 |
| 20130084972 | Frady | Apr 2013 | A1 |
| 20130084973 | Frady | Apr 2013 | A1 |
| 20130095904 | Cannon et al. | Apr 2013 | A1 |
| 20130130779 | Gagner et al. | May 2013 | A1 |
| 20130130782 | Hornik et al. | May 2013 | A1 |
| 20130130806 | Gagner et al. | May 2013 | A1 |
| 20130178271 | Aponte et al. | Jul 2013 | A1 |
| 20130196755 | Nelson et al. | Aug 2013 | A1 |
| 20130231192 | Walker et al. | Sep 2013 | A1 |
| 20130252714 | Buchholz et al. | Sep 2013 | A1 |
| 20130260889 | Lemay et al. | Oct 2013 | A1 |
| 20130274016 | Gagner et al. | Oct 2013 | A1 |
| 20130337889 | Gaqner et al. | Dec 2013 | A1 |
| 20130337890 | Earley et al. | Dec 2013 | A1 |
| 20140031107 | Walker et al. | Jan 2014 | A1 |
| 20140045582 | Lyons et al. | Feb 2014 | A1 |
| 20140094272 | Kelly et al. | Apr 2014 | A1 |
| 20140141864 | Ward et al. | May 2014 | A1 |
| 20140248941 | Nelson et al. | Sep 2014 | A1 |
| 20140287822 | Young | Sep 2014 | A1 |
| 20150302695 | Ward | Oct 2015 | A1 |
| 20150348361 | Adiraju | Dec 2015 | A1 |
| 20160042599 | Toohey | Feb 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 199534536 | May 1998 | AU |
| WO9712315 | Apr 1997 | WO |
| WO2007146346 | Dec 2007 | WO |
| Entry |
|---|
| Australian Patent Application No. 2015210435, Examination Report, dated Dec. 16, 2016, 4 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20180336760 A1 | Nov 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62034646 | Aug 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14821196 | Aug 2015 | US |
| Child | 16051061 | US |
