Patent Grant
10096209
Social networks in different forms are becoming exponentially popular, with most of them being slight variations on the well-known MySpace™ (http://www.myspace.com) or Facebook™ (http://www.facebook.com) models. For example, active membership in Facebook™, a popular social networking site, has greater than 500 million users, and comprises everyone from school children to grandparents. Such tools are generally used to post information that can be accessed by other registered users of the system. Unfortunately, the trend of social networking tools has solidified the notion of social networks as a web-page only paradigm, a virtual Rolodex that grows so big that the social network lacks context, and hence relevance.
Gaming establishments are constantly looking for different ways to increase gaming revenue and provide a more satisfying gaming experience for the player. Social networks may provide a social aspect for playing games of chance.
A system, apparatus, and method for establishing a social game between a gaming machine and at least one user is provided. A system, apparatus, and method for a real-time temporal grant of a social bonus game feature between a gaming machine user and at least one available remote user is also provided. In one embodiment, a social gaming server and at least one gaming machine may be in communication with a bonus game manager to facilitate a social real-time bonus game feature game play and distribution of bonus game feature award.
In one embodiment, a gaming system may have a gaming machine configured to: (i) present a primary game of chance on a display of the gaming machine; (ii) determine whether a bonus triggering event is triggered on the primary game of chance; (iii) receive a list of at least one available remote user; (iv) display the list of the at least one available remote user on the display of the gaming machine; (v) detect a selection of the at least one remote user from the list of the at least one available remote user displayed on the display; (vi) transmit the selection of the at least one remote user to a social gaming server; (vii) await, up to a predetermined period of time, for receipt of a bonus game input associated with the bonus game, the bonus game input being initiated by the at least one remote user; and (viii) display results of the bonus game following receipt of the bonus game input.
The gaming system may also have a social gaming server configured to: (i) monitor the primary game of chance presented on the gaming machine; (ii) determine whether the bonus triggering event is triggered on the gaming machine; (iii) generate the list of at least one available remote user for participation in the bonus game; (iv) transmit the list of the at least one available remote user to the gaming machine; (v) receive the selection of the at least one remote user from the gaming machine for distribution of the bonus game feature to the at least one remote user; (vi) distribute the bonus game feature to each of the selected at least one remote user; (vii) await, up to a predetermined period of time, for receipt of a bonus game input associated with the bonus game, the bonus game input being initiated by at least one of the selected remote user; (viii) receive a result of the bonus game; and (ix) transfer the result of the bonus game to the gaming machine and the at least one selected remote user.
In another embodiment, a method for granting a real-time bonus game feature may include presenting a primary game of chance on a display of a gaming machine, determining whether a bonus triggering event is triggered on the primary game of chance, receiving a list of the at least one available remote user, displaying the list of at least one available remote user on the display of the gaming machine, detecting a selection of at least one remote user from the list of at least one available remote user displayed on the display, transmitting the selection of the at least one remote user to a social gaming server for distribution of a bonus game feature to the at least one remote user, awaiting, up to a predetermined period of time, for receipt of a bonus game input associated with the bonus game feature, the bonus game input being initiated by the at least one remote user, and displaying results of a bonus game following receipt of the bonus game input, wherein the bonus game feature is used to play the bonus game.
In another embodiment, a method for facilitating real-time bonus game participation on a social gaming server may include monitoring a primary game of chance on a gaming machine, determining whether a bonus triggering event is triggered on the primary game of chance, generating a list of at least one available remote user, transmitting the list of the at least one available remote user to the gaming machine, receiving selection of the at least one remote user from the gaming machine for distribution of a bonus game feature to the at least one remote user, distributing the bonus game feature to each of the selected at least one remote user, awaiting, up to a predetermined period of time, for receipt of a bonus game input associated with a bonus game, the bonus game input being initiated by the at least one remote user, calculating a result of the bonus game, and transferring the result of the bonus game to the gaming machine and the at least one selected remote user.
The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more example embodiments and, together with the description of example embodiments, serve to explain the principles and implementations.
In the drawings:
Embodiments are described herein in the context of social gaming. The following detailed description is illustrative only and is not intended to be in any way limiting. Other embodiments will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following description to refer to the same or like parts.
In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.
In accordance with some embodiments, the components, process steps, and/or data structures may be implemented using various types of operating systems, computing platforms, computer programs, and/or general purpose machines. In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein.
A system, apparatus, and method for providing a social game environment in which players of gaming machines can interact with other users while playing a game on a gaming machine. The game played on the gaming machine can be referred to as a social game (or a social game session) since remote players can assist the player of the gaming machine in playing the game of chance, an associated social game component of the game of chance, or a separate social game (which can be a game of change or a non-game of chance). In general, the player of the gaming machine can gain assistance (e.g., participation or interaction) from other players that are not located at the gaming machine (i.e., remotely located from the gaming machine). The other players may be eligible to gain awards, points, or the like by assisting the primary player (e.g. the player playing the primary game of chance) and participating in a bonus game of chance. The other players may be referred to as at least one social gaming user, social contact, remote user, and/or remote player.
Communication between the game server 104, the at least one gaming machine 106a-106n, the social gaming server 102, the third party server 112, the local users 108a-108n, and the remote users 110a-110n may be conducted through network 115 via any combination of wired networks, wireless communication technology, and cellular networks. A wired network can use Category 5 cable, Category 6 cable, fiber optic cable, coaxial cable or other cable types typically used for computer networks. Examples of wireless communications technology may include, but is not limited to, Wi-Fi and Bluetooth. Cellular networks may use Code division multiple access (CDMA), Global System for Mobile Communications (GSM), or any other common mobile network standards to transmit data at 2nd generation (2G), 3rd generation (3G), 4th generation (4G), or any other data transmission speeds.
The game server 104 may be any computing hardware typically used for network servers. The game server 104 may have a memory configured to store at least one game of chance and a processor configured to manage the game of chance. The game of chance could be reel-based slot games, video poker, video blackjack, electronic table game, lottery games, or any other games of chance. The game server 104 can be configured to communicate with the at least one gaming machine 106a-106n and the social gaming server 102.
The at least one gaming machine 106a-106n can be configured to play the game of chance, received from the game server 104, and produce game information. The at least one gaming machine 106a-106n may be a slot machine, mobile gaming device, electronic gaming table, electronic blackjack table, electronic roulette table, kiosk, interactive TV, tablet computer, or the like. In one embodiment, the at least one gaming machine 106a-106n may have a main display, a secondary display, a graphical user interface (GUI) displayed or presented on the main display or the secondary display, a ticket-in ticket-out (TITO) system, a bill acceptor, and a player tracking device as further illustrated and discussed in
The social gaming server 102 may have a processor. The processor can be any microprocessor, CPU, multi-core processor or chipset commonly used by network servers for computing. The processor can be configured to communicate with and manage a plurality of social gaming managers. The plurality of social gaming managers may include some or all of the following: a social game session manager, an authentication manager, a social contacts manager, a local social game manager, and a social awards manager as further illustrated and discussed with reference to
The third party server 112 may be configured to store and manage non-gaming social games. The third party server 112 may authorize a third party remote user 114a-114n or a user device of the third party remote user 114a-114n and connect the third party remote user 114a-114n to the social gaming server 102 to participate in a social gaming. In one embodiment, the third party server can be any social networking server (e.g. Facebook™, MySpace™, LinkedIn™, Twitter™, and the like) and may receive at least a portion of the game information.
In one embodiment, at least one social gaming user can be a remote user 110a-110n. The remote user 110a-110n may be located in a geographical location that is physically separated from or away from the at least one gaming machine 106a-106n and/or the gaming environment. For example, the remote user 110a-110n may be at home and utilize a laptop computer configured to communicate directly with the social gaming server 102 through network 115.
In another embodiment, the at least one social gaming user can be a local user 108a-108n. The local user 108a-108n may be location within or on the premises of the gaming environment. For example, the local user 108a-108n may be located in a restaurant in the gaming environment and can participate in the social game session using a smart phone configured to communicate with the social gaming sever 102. In another example, the local user 108a-108n may be playing on another gaming machine 106a-106n while participating in a social game.
In yet another embodiment, the at least one social gaming user may be a third party remote user 114a-114n. The third party remote user 114a-114n may participate in a social game session via third party server 112. Third party server 112 may then be configured to communicate with the social gaming server 102 via network 115 and be configured to facilitate communication between the third party remote user 114a-114n and the social gaming server 102.
The at least one social gaming user may participant in a social game session using a user device. In one embodiment, the user device can be a computing device such as, but not limited to, a desktop computer, a laptop computer, a tablet computer, or a netbook computer. In another embodiment, the user device may be a portable electronic device such as a cell phone, a smart phone, a portable media player, a portable gaming device, a personal digital assistant or the like. In yet another embodiment, the user device may be another gaming machine.
The social game session manager 204 may be configured to manage a social game session established between a gaming machine and at least one user device via the social gaming server 200. The social game session can enable the social gaming user of the at least one user device to receive current or real-time and/or past game information about a game of chance. The social game session may also enable the social gaming user of the at least one user device to remotely participate in or interact with the game of chance.
Social gaming server 200 may be configured to acquire gaming information from a gaming machine, such as gaming machines 106a-106n illustrated in
The social game session manager 204 can be configured to determine at least a portion of game information to be distributed to the at least one user device. In one embodiment, the social game session manager 204 can determine the at least a portion of the game information to be distributed based upon a plurality of user preferences. The plurality of user preferences may be any configuration desired by a user that may be stored on the social gaming server 200, the social game session manager 204, or any other memory device or server device. The plurality of user preferences may be any specific preferences desired such as, the type of gaming information the user would like to see and when. For example, Bob may only want to know when Tom has earned a non-gaming award when playing a game on the gaming machine. When Tom earns a non-gaming award while playing the gamine of chance, the social game server 200 may transmit the gaming information about the non-gaming aware to Bob. However, the social game server 200 may not transmit the fact that Tom also won $100.00.
In another example, the social game session manager 204 may be configured to determine which gaming information is considered to be “significant”. The significant event could be, for example, winning a jackpot, the player cashed out of the gaming machine, hitting a royal flush, entering a bonus game, and the like. In another example, the social game session manager 204 may determine to transmit all the gaming information.
In one embodiment, the gaming information may be transmitted from the social gaming server 200 to the users via any known methods, such as streaming the gaming information.
The authentication manager 206 may be configured to authenticate a user. In one embodiment, the authentication manager 206 may authenticate the user by confirming validity of a password, biometric identifier, personal identification number(s), or the like. Following authentication, the authentication manager 206 may signal the social game session manager 204 to establish the social game session between the gaming machine and the user device of the user. In another embodiment, a third party server, such as third party server 112 illustrated in
If the user is authenticated, the authentication manager 206 may transmit an approval notification to the social game session manager 204. The social game session manager 204 may then establish a social game between the gaming machine and a user device of at least one social gaming user.
In one embodiment, the authentication manager 206 may be configured to authenticate the user device based upon an identifier, such as a MAC address, confirming validity of a key file (which may or may not be encrypted) stored on the user device, hashing and comparing contents of the key file to a record maintained by the authentication manager 206, or any other commonly used methods of verifying the validity of a data file. In yet another embodiment, the authentication manager 206 may authenticate the user device using a unique address, such as a short code or a web link.
The social contacts manager 208 may be configured to store and/or manage one or more social contacts for a player playing the game of chance on a gaming machine. In one embodiment, the one or more social contacts may be stored in a contacts database 210. In another embodiment, the one or more social contacts may be stored on a third party server, such as third party server 112 illustrated in
The social game server 200 may optionally have a local social game manager 212. The local social game manager 212 may be configured to manage non-gaming social games. Non-gaming social games may be any type or kind of game that is not a game of chance utilizing a random number generator and/or any type of game where prizes are not monetary. For example, a non-gaming social game may be a “Hotel Management” simulation game, where different players can build and run a hotel.
In another embodiment, an award triggering event may be a loss. For example, an award may be triggered by losing a particular round of the game of chance, losing a certain number of times over a predetermined period of time, losing a certain amount of credits in a particular round of the game of chance, losing a certain total monetary amount, or the like.
In yet another embodiment, an award may be triggered by achieving or obtaining a particular outcome. For example, in a slot game, an award triggering event may be obtaining six cherry symbols on a plurality of reels without winning a payline. In another example, in a video poker game of chance, an award may be triggered by obtaining a pair of queens in five consecutive hands.
The social awards manager 214 can be configured to generate the award if an award triggering event has occurred. The award can be any type of gaming or non-gaming award and may be based on the type and theme of game. A gaming award may be, for example, a monetary award, at least one free spin, a multiplier, earning a plurality of points, triggering a bonus event, and the like. A non-gaming award can be, for example, a digital enhancement for the social gaming user interface on the user device and/or on the gaming machine. The digital enhancement can be a wallpaper, a background, a song, new avatar, a picture, any type of other visual and/or auditory aesthetic prizes, movie tickets, food coupons, and the like. The non-gaming award may also be a virtual good. The virtual good can be used in a non-gaming social game hosted by a third party server or the local social game manager 212 of the social gaming server 250. The social awards manager 214 may store the gaming awards in an awards database 216 and the non-gaming awards in a non-gaming awards database 218.
The social awards manager 214 can be configured to determine if the award is to be transferred to a remote recipient. In one embodiment, the social awards manager 214 can determine if the award is to be transferred if the social awards manager 214 receives a user transfer request to transfer the award to another player. The user transfer request can be made by the user currently in possession of the award. In another embodiment, the social awards manager 214 may receive a remote transfer request for the award by a social gaming user not in possession of the award. The social awards manager 214 may transmit the request to the user currently in possession of the award and await approval of the transfer request from the user currently in possession of the award. If the social awards manager 214 receives an approval for the transfer request, the social awards manager 214 may transfer the award to the social gaming user. The social awards manager 214 can be configured to modify ownership of the award entry in either the awards database 216 or the non-gaming awards database 218. If a denial for the transfer request is received by the social awards manager 214, then the social awards manager 214 determines not to transfer the award.
The method of distributing at least a portion of game information 300 can begin by identifying at least one social gaming user at 302. In one embodiment, the social gaming server may identify the at least one social gaming user based upon player input received from a player playing a game of chance. Input can be performed on a gaming machine such as a portable or mobile gaming device, electronic gaming table, electronic blackjack table, electronic roulette table, kiosk, interactive television, tablet computer, or the like. For example, the player playing a game of chance may select at least one social gaming user from a social contact list as, for example, illustrated in
Once player input is received by the social gaming server, the social gaming server may, in one example, identify the at least one social gaming user from the selection by comparing the input to a list of contacts stored in the contacts database. In another embodiment, the input may be compared with a list of contacts in a third party server. The user input may be transmitted to the third party server which may compare the input with a list of contacts stored at the third party server.
A game of chance may be played on a gaming machine at 303. Game information may be generated for the game of chance at 305 as the player plays the game of chance. In one embodiment, game information may be generated from the gaming machine. In another embodiment, game information may be generated from a game server (as illustrated in
As the game information is generated, the game information can be simultaneously transmitted to and acquired by the social game server (as illustrated in
In another embodiment, the at least a portion of the gaming information may be electronically transmitted to the at least one social gaming user via electronic mail. In yet another embodiment, the at least a portion of the gaming information may be streamed. Streaming results may result in a real time reproduction display of the game of chance. As action occurs in the game of chance, the real time reproduction display will mirror the display of the gaming machine. The streaming can be supplemented by any combination of textual, audio, or visual information.
A determination of whether the game of chance has ended is made at 306. The game of chance may end if the player decides to stop playing the game of chance. The game of chance also may end if no credits for playing the game of chance are left. If the game of chance has not ended, the at least a portion of the gaming information may continue to be distributed to the at least one social gaming user at 304.
If the event is “significant” at 404 the significant event may be posted or transmitted to a social networking server at 406. In one embodiment, the significant event could be, for example, winning a jackpot, the player cashed out of the gaming machine, hitting a royal flush, entering a bonus game, and the like. In another embodiment, the significance of the event can be determined by the player of the game of chance or at least one social gaming user. For example, the player or social gaming user may select specific events from a significant event list as what he or she considers to be significant.
The social networking server may be the social gaming server, a third party server, or any other server. The social networking server can post the information to a webpage, a feed, a notification board, or the like. The at least one social gaming user can then retrieve the information from the webpage, the feed, the notification board, or the like.
If the event is not significant at 404 or the event has been posted to the social networking server at 406, a determination of whether the game of chance has ended is made at 408. In one embodiment, the game of chance may end if the player decides to stop playing the game of chance. The game of chance also may end if there are no more credits to play the game of chance.
The streaming of the gaming information may result in a real time reproduction of the game of chance on a display of a user device. As activity occurs as the player plays the game of chance, gaming information is generated whereby at least a portion of the game information may be streamed to a user device of at least one social gaming user. When the at least a portion of the gaming information is streamed to the at least one social gaming user, everything presented on the gaming machine may be reproduced and instantiated on a display of a user device of the at least one social gaming user.
In one embodiment, the at least a portion of the gaming information may be transmitted via a video feed. A camera positioned on the gaming machine may capture the activity of the game of chance in the video feed. The video feed can be encoded and prepared for streaming using any codec or technology commonly used to stream video over a network such as, but not limited to, Flash video and HTML 5. In another embodiment, the at least a portion of the gaming information may be transmitted via a digitally animated recreation of the game of chance. The streaming of the at least a portion of the gaming information may include any combination of textual, audio, or visual information.
At least one remote user may be authorized to access the stream at 504. The at least one remote user may be a social contact associated with the player playing the game of chance. In one embodiment, the at least one remote user may be stored in a contacts database maintained by a social contacts manager of the social gaming server (as illustrated in
In another example, the at least one remote user may be compared to a list of contact stored in a third party server. For example, the third party server can be any social networking server that manages contacts. The social gaming server can transmit a verification request to the third party server. A confirmation or non-confirmation may be transmitted to the social networking server from the third party server. Upon receipt of a confirmation or verification from the third party server, the social gaming server may authorize the at least one remote server to access the stream at 504.
In another embodiment, the at least one remote user need not be a social contact and may be authorized to access the stream via an identifier. The identifier can be a password, personal identification number (PIN), code, key file, or other similar form of identification or identifier. For example, if remote player A is sitting next to player B paying a game of chance and player A would like to view Player B's game, Player A may transmit a request to view Player B's game of chance to the social gaming server. The social gaming server can transmit a request for identification to the at least one remote user via electronic mail, text message, phone call, or any other identification and/or verification methods. For example, the social gaming server may transmit a request for Player B's player tracking number and PIN. Player B may input and transmit the information to the social gaming server. The social gaming server may then compare and/or verify Player B's information with information stored in the social gaming server, player tracking server, or any other server or database.
In still another embodiment, the identifier can also be a unique shortcode address or a unique URL. The unique shortcode address or the unique URL may be generated by the social gaming server. The social gaming server can transmit the unique shortcode address or the unique URL to a phone number, an email address, or the like, provided by the player. Upon receipt of the identifier, the at least one remote user may access the stream of the game of chance using the identifier. In other words, at least a portion of the gaming information may be streamed to a user device of the at least one remote user when the at least one remote user accesses the identifier.
The input for a selection of a remote user may be made from a social contact list (illustrated in
Once the input for a selection of a remote user is received at 602, input by a user device of the remote user may be enabled at 604. Enabling the input may allow the remote user to participate, interact, and/or observe the game of chance. The input may be based on the type and theme of game. For example, by enabling input from the user device, the remote user may participate by spinning a bonus spin in a social gaming session. In another example, enabling input from the user device may allow the remote user to “hit”, “double down”, or “stay” in a blackjack social gaming session.
A determination is then made as to whether input is received from the remote user within a predetermined period of time at 606. The predetermined period of time may be set by the social gaming server, the player, or any other device or person. If input from the remote user is received within a predetermined period of time at 606, the input may be implemented at the gaming machine at 608. For example, if the remote user participates by spinning a bonus spin, the reels may be presented as spinning on the gaming machine. In another example, if the input received from the remote user is a “hit” for a video blackjack game of chance, the player may receive another card in the video blackjack game. In another example, if the game of chance is video poker, the input received from the remote user may be to draw at least one card. Thus, an additional card may be provided and displayed on the gaming machine.
If no input is received from the remote user at 606, the player may be notified that no input was received at 610, the input may be disabled at 612, and a determination may be made as to whether a new remote user selection was received at 614. In one embodiment, the player can receive a notification, such as an alert, a popup, a message, or any other form of notification, on a GUI of the gaming machine. In another embodiment the notification may occur on a user device of the player such as a text message. The notification may contain any combination of text, graphics, symbols, or indicia to notify the player that no input was received from the remote user. If a new remote user selection was received at 614, input for the user device of the remote user may be enabled at 604.
If it is determined the remote input should be enabled 702, the remote input can be configured at 704. The configuring may customize what remote input is available and tailor the remote input to a type of the game of chance. For example, if the game of chance is video blackjack, the remote input may be configured to limit the remote input to a blackjack action such as hit, stand, double down, split, or other actions associated with a game of blackjack. Configuring the remote input may also initiate a steaming of the gaming information to a user device as discussed above with reference to
The player may play the game of chance on a gaming machine at 706. As the player plays the game a chance, a determination may be made as to whether a request for remote input for the game of chance be made at 710. In other words, as the player plays the game of chance, events may occur whereby the player would like participation or help from at least one social gaming user. In one embodiment, the player may request that a social gaming user assist or participate in playing the game of chance. In another embodiment, the gaming machine may prompt and ask the player whether he or she would like to allow others to assist in playing the game of chance. The gaming machine can offer the player the option to request the remote input for every gaming action, for a random gaming action, or for a predetermined gaming action. The player can accept or deny the remote input request prompt.
If it is determined that the remote input for the game of chance is requested at 710, a remote user may be selected at 712 to participate in the game of chance. In one embodiment, the remote user may be at least one social gaming user stored in a contacts database (as illustrated in
A remote input request may then be transmitted to the remote user at 714. The remote user may receive the remote input request on a user device such as a computing device, a portable electronic device, or another gaming machine. The remote user may then deny or accept the remote input request.
If remote input from the remote user is received within a predetermined period of time at 716, the remote input may be processed and used to play the game of chance at 718. In one embodiment, the remote input may be an acceptance of the remote input request transmitted at 714. In another embodiment, the remote input may be an action to play the game of chance.
For example, if the game of chance is a slot game, the remote input requested may be to initiate a free spin. In another example, if the game of chance is video blackjack, the remote input requested can be to hit, stay, or double down. The remote input may be any input to advance the game of chance.
If no input from the remote user is received within a predetermined period of time at 716, another determination may be made as to whether the player would like to request remote input for the game of chance at 710.
A determination may be made as to whether playing the game of chance is to continue at 720. The game of chance may continue if the player makes another wager, if the player won a bonus game, if additional bonus awards were won, and the like. Another determination of whether the remote input is enabled is made at 724.
Once initiated, a determination is made as to whether a social award is earned at 804. A social award may be earned by any known award triggering events based on the type or theme of game. For example, an award may be triggered for winning a particular game session, winning a certain number of times over a predetermined period of time, winning a certain amount of credits in a particular round of the game, winning a certain monetary amount, achieving a certain game pattern, achieving a free bonus round, winning a certain total monetary amount, obtaining a royal flush, or the like.
In another embodiment, an award triggering event may be a loss. For example, an award may be triggered by losing a particular round of the game of chance, losing a certain number of times over a predetermined period of time, losing a certain amount of credits in a particular round of the game of chance, losing a certain total monetary amount, or the like.
In yet another embodiment, an award may be triggered by achieving or obtaining a particular outcome. For example, in a slot game, an award triggering event may be obtaining six cherry symbols on a plurality of reels without winning a pay line. In another example, in a video poker game of chance, an award may be triggered by obtaining a pair of queens in five consecutive hands.
If a social award is earned at 804, the social award may be generated at 806. In one embodiment, a social awards manager (as illustrated in 2B) may be configured to generate the type of social award won. The award can be any type of gaming or non-gaming award. A gaming award may be, for example, a monetary award, at least one free spin, a multiplier, earning a plurality of points, triggering a bonus event, and the like. A non-gaming award can be, for example, a digital enhancement for the social gaming user interface on the user device and/or on the gaming machine. The digital enhancement can be a wallpaper, a background, a song, new avatar, a picture, any type of other visual and/or auditory aesthetic prizes, movie tickets, food coupons, and the like. The non-gaming award may also be a virtual good. The virtual good can be used in a non-gaming social game hosted by a third party server or the local social game manager of the social gaming server. The social awards manager may store the gaming awards in an awards database \and the non-gaming awards in a non-gaming awards database.
A determination may be made to save the social award at 808, transfer the social award at 812, or redeem the social award at 816. If the player would like to save and keep the social award, the social award may be saved at 810. In one embodiment, the social award may be saved in an awards database or non-gaming awards database (as illustrated in
If the social award is not saved at 808, the social award may be transferred at 812. In one embodiment, the social awards manager can be configured to determine if the award is to be transferred to a remote recipient. In one embodiment, the social awards manager can determine if the award is to be transferred if the social awards manager receives a user transfer request to transfer the award to another player. The user transfer request can be made by the user currently in possession of the award. In another embodiment, the social awards manager may receive a remote transfer request for the award by a social gaming user not in possession of the award. The social awards manager may transmit the request to the user currently in possession of the award and await approval of the transfer request from the user currently in possession of the award. If the social awards manager receives an approval for the transfer request, the social awards manager may transfer the award to the social gaming user at 814. The social awards manager can be configured to modify ownership of the award entry in either the awards database or the non-gaming awards database. If a denial for the transfer request is received by the social awards manager, then the social awards manager determines not to transfer the award at 812.
When the social award is not transferred at 812, a determination is made whether to redeem the social award at 816. In one embodiment, the social awards manager can be configured to determine if the award is to be redeemed. For example, the player or at least one social gaming user may be prompted to redeem the social award or not. The player or at least one social gaming user may then deny or accept the prompt. If an acceptance to redeem the social gaming award is received at 816, the social award may be redeemed at 818. If a denial to redeem the social gaming award is received at 816, the determination as to whether to save the social award at 808 may be repeated.
Once the social award is redeemed at 818, a determination as to whether to end the game may be made at 820. The game may end if the player decides to stop playing the game, no credits remain, the game ends, or the like.
The gaming machine 900 may have a player interface to play the primary game of chance and interact with the social gaming interface. In one embodiment, the player interface may include any type of actuating device such as buttons 912 or a lever 910. In another embodiment, the main display 908 may be the player interface. For example, the player interface may be a touch screen display configured to present a GUI and receive an input from the player. The player interface may be any type of input mechanism capable of allowing a player to select options, play the primary game of chance, play a bonus game, or enter any other player input. For example, pushing a button 912 or pulling a lever 910 may prompt the gaming machine 900 to begin a spin of a reel in a slot game to play a primary game of chance. In another example, a player may use the touch screen display to enter player account information. In yet another example, a player can use the touch screen display to select a social contact to remotely participate in a game of chance. The gaming machine 900 may also have speakers 906, lights, or other output devices.
The gaming machine 900 may also have a TITO (Ticket In, Ticket Out) system. TITO uses tickets encoded with monetary amounts, which can be converted into credits to be played in the gaming machine 900 when inserted into the gaming machine 900. The gaming machine 900 may have a bill acceptor 918 configured to receive the tickets. The gaming machine 900 may also have a ticket printer 914 configured to print out similar tickets encoded with the amount of credits remaining on the gaming machine 900 when the player desires to no longer play the gaming machine 900 and cash out.
The bill acceptor 918 may also be configured to receive currency, for example paper bills. The gaming machine 900 may also have a mechanism to accept currency in other forms such as coins, vouchers, smart cards, electronic funds, and the like. The currency can then be converted into credits to be played on the gaming machine 900. The gaming machine 900 may have a credit dispenser 920 where the credits on the gaming machine 900 can be cashed out when the player desires to no longer play the gaming machine 900.
The gaming machine 900 may have a player tracking device 916 configured to receive a player loyalty card. Casinos may issue players a player loyalty card for player tracking and rewarding purposes. The player loyalty card may be associated with a player account. Player account data may be stored on a network server (e.g. a player tracking server), which may be on a network database server configured to communicate with the gaming machines in the casino. The network may be a client-server network, a peer-to-peer network, a wired or wireless network, a wide area network (WAN), a local area network (LAN), or any other type of network. The player may insert his or her player loyalty card into the player tracking device 916 to log into the player's account. Data about the player's play, such as outcomes, bet amounts, time played, or any other type of information, may be saved over the network to a non-volatile memory at a player tracking server or any other network server. The player's account may be also be used to associate the player with the at least one social gaming user, social awards, and any other data or information.
The gaming machine 900 can have a secondary display 904. The secondary display 904 may also display other text and graphics, including videos, pay tables, advertisements, secondary games, bonus games, player tracking information, announcements, or any other type of text and graphic. The secondary display 904 can potentially display any type of game of chance such as reel-based slot games, video poker, video blackjack, lottery games, secondary games of chance or any other type of known games of chance. The secondary display 904 can be a liquid crystal display screen, cathode ray tube monitor, projection, organic light-emitting diode screen or any other type of display device.
The game of chance window 1006 can display any type of game of chance upon receipt of a wager from the player. For example, the game of chance window 1006 may display reel-based slot games, video poker, video blackjack, lottery games, electronic table games, or any other types or themes of games of chance. The information window 1004 can display information related to the game of chance. The information displayed in the information window 1004 can include a wager amount 1050, total credits 1054, pay lines 1052, or any other gamin information. In one embodiment, the information window 1004 may be a standalone window as illustrated in
The social contact list 1002 can display and provide the player access to a plurality of social contacts. In other words, the social contact list 1002 may provide a list of at least one social gaming user associated with the player. The listing of at least one social gaming user may be obtained from, for example, the social contacts manager (illustrated in
The social contact list 1002 may include a plurality of controls configured to manipulate the social contact list 1002. In one embodiment, the plurality of controls can be a sort button 1016 and a search button 1018. In another embodiment, the actuation of the sort button 1016 may order the plurality of social contacts. For example, pressing the sort button 1016 can sort the plurality of social contacts alphabetically, by type, by groups, by player preferences, availability, or the like. The search button 1018 may allow the player to search for a particular social gaming user using any known searching methods. Although
The plurality of social contacts can be represented by alpha-numeric text such as, but not limited to, name 1010a, email address 1010b, phone number 1010c, or an alias 1010d. Although the plurality of social contacts are illustrated in
The social contact list 1002 may include a plurality of social contact options. The plurality of social contact options may be configured to allow the player to perform a variety of social gaming actions such as viewing a social contact profile, messaging a social contact, inviting a social contact to join a social game, requesting a remote participation input, transferring a social gaming award, and the like. In one embodiment, the plurality of social contact options 1050 may be arranged in a menu listing the various options and include an option indicator 1020 to indicate which social contact option in the menu has been selected by the player. The option indicator 1020 may be, but is not limited to, an arrowhead as illustrated in
In one embodiment, the social contact options 1050 may appear in the social contact list 1002 upon receipt of an input on the gaming machine. For example, the input may be selection of an “option” indicator presented on the GUI. In another example, the input may be a selection of one of the at least one social gaming users. The input may be a tap, double tap, press and hold, swipe, slide, or other input.
The social gaming communications window 1022 can include a session participant area 1026 and a communications area 1024. The session participant area 1026 may contain a list of all contacts participating in the social game session. In one embodiment, the contacts may be listed using alpha-numeric text, as illustrated in
The social gaming log 1028 may display a plurality of events 1030 from a social game session. The plurality of events 1030 can include, but is not limited to, an entrance into the social game session by a contact participating in the social game session, an exit from the social game session by a contact participating in the social game session, a selection of one of the contacts for remote participation, a result of the remote participation, a procurement of an award, and the like. In one embodiment, the social gaming log 1028 may be a standalone window as illustrated in
The remote social gaming interface 1120 may include a remote game of chance window 1110 and a remote information window 1108. The remote game of chance window 1110 can display a representation of the game of chance being played on a gaming machine by a player. The game of chance may be reel-based slot games, video poker, video blackjack, lottery games, electronic table games, or any other primary games of chance. In one embodiment, the remote game of chance window 1110 may display a real-time stream of the game of chance from the gaming machine. If the game of chance is digitally displayed on the gaming machine, the real-time stream may mirror a display of the gaming machine on the remote game chance of window 1110. For example, if the game of chance involves physical reels, cards, dice, or similar gaming objects, a camera may capture activity of the game of chance. The real-time stream can be generated using flash video technology, HTML 5, or other codecs and technology commonly used for streaming video over a network. In another embodiment, the remote game of chance window 1110 may display a real-time animation of the game of chance. For example, if the game of chance is a reel-based slot game with a plurality of physical reels, the remote game of chance window 1110 may show a digitally animated recreation of the plurality of physical reels. In yet another embodiment, the remote game of chance window 1110 may display a plurality of significant events from the game of chance posted by the social gaming server.
The remote information window 1108 can display information related to the game of chance. The information displayed in the remote information window 1108 can include a wager amount 1130, total credits 1132, pay lines 1134, or any other information typically associated with a primary game of chance. In one embodiment, the remote information window 1108 may be a standalone window as illustrated in
The GUI 1120 may include a remote social gaming communications window 1112. The remote social gaming communications window 1112 may contain a list of at least one contact that may be selected to participate in the social game session. The at least one contact may be any one or combination of the local user, remote user, or third party user as illustrated in
The GUI 1120 may include a contact list 1118. The contact list 1118 can display a list of contacts for selection by the player. In one embodiment, the plurality of social contacts can be represented by alpha-numeric text such as, but not only, a name, an email address, a phone number, or an alias. In another embodiment, the plurality of social contacts in the contact list 1118 may be represented by pictures, icons, avatars, or other indicia. Although not illustrated, each contact may be associated with a status indicator, options, and the like as discussed with reference
The GUI 1120 may include a social game session list 1116. The social game session list 1116 can list any active social game sessions the contact is currently participating or observing. The contact may be connected to a first social game session and may be able to join or observe a second social game session. Upon joining the second social game session, content from the remote game of chance window 1110, the remote information window 1108, and the remote social gaming communications window 1112 may switch from that of the first social game session to that of the second social game session. The social game session list 1116 may also updated to reflect the current social game session.
The GUI 1120 may include a remote input indicator 1114.
When inactive, the remote input indicator 1114 can indicate that the player has not selected the contact to make the remote input or that the remote input has not been enabled on the portable electronic device.
Although the inactive remote input indicator 1114 is illustrated with a spin label, this is not intended to be limiting. The remote input indicator may be based upon the type and theme of the social game session. For example, if the social game session is a video blackjack, the remote input indicator may have a “hit”, “stay”, and “double down” label.
Referring now to
Moreover, the remote social gaming communications window 1112 may indicate the contact has been selected to participate in the social gaming session. As illustrated, “JERRY has requested that you spin the reels” may be presented.
A timer 1152 may be presented on the GUI 1120. The user may have a predetermined period of time to participate in the social gaming session. The timer 1152 may inform the user of the time left to participate. For example, the user may have one minute forty-two seconds to participate in the social gaming session by selecting the remote input indicator 1154. The portable electronic device 1102 may refresh the timer 1152 as the amount of time left decreases. The timer 1152 may continue to refresh until the amount of time left decreases to “0”. The timer 1152 may be presented using digital numbers, clock face, or any other time representation. In one embodiment, the timer 1152 can simply display the total amount of seconds. In one embodiment, the timer 1152 may be visible when the remote input indicator is active.
When selected by the contact, the portable electronic device 1102 can transmit the remote input from the portable electronic device 1102 to a social gaming server, a gaming server, or a gaming machine via a network (as illustrated in
The remote social gaming interface 1210 may include a plurality of social game session monitoring windows 1208-1208n. While
A new social game session monitoring window 1208a-1208n may be generated when the user joins a new social game session. In one embodiment, upon the user joining the new social game session, the remote social gaming interface 1210 can resize existing social game session monitoring windows 1208a-1208n to accommodate the new social game session. In one embodiment, the GUI 1210 may automatically be resized to equally allocate space for each social game session monitoring window 1208-1208n. 1208-1208n For example, for two social game session monitoring windows 1208-1208n, each window 1208-1208n may be allocated half of the GUI 1210. If the contact joins a new social game session, the GUI 1210 may divide and present each social gaming session monitoring window 1208-1208n on one third of the GUI 1210. Thus, the social gaming session monitoring windows 1208-1208n are equal in size.
In another embodiment, the plurality of social game session monitoring windows 1208-1208n may be different sizes. The size of each game session monitoring window 1208-1208n may depend upon any number of factors including, but not limited to, user preference, level of activity, wager amount, or request for a remote participation input. For example, for game sessions having a lower credit amount, the game session monitoring window 1208-1208n may be smaller than a game session having a larger credit amount. In another example, the user may manually allocate the size for each social game session monitoring window 1208-1208n.
The remote game of chance window 1310 may display a real-time stream of the game of chance being played by JERRY. The real-time stream may mirror a display of the gaming machine on the remote game chance of window 1310. The streaming of at least a portion of game information from the gaming machine may be transmitted by a game server, a social gaming server, or any other server. In one embodiment, the remote game of chance window 1310 may display a plurality of events from the game of chance posted by the social gaming server. As illustrated, “SPIN BUTTON active for next 2 min.” is an event that is currently occurring.
The remote information window 1308 can also display information related to the game of chance, a remote social gaming communications window 1312, a remote social contact list 1318, a social game session list 1316, a remote input indicator 1314, as discussed above. The GUI 1320 may also have an award notification 1322 to inform the user that an award has been earned. The award notification 1322 may become visible when the player or the user has earned an award as discussed in detail above. Although the award notification 1322 is illustrated in
The GUI 1320 may alternatively display an award icon 1326. The award icon 1326 may indicate that the user received a new award. The award icon 1326 can be any graphic, logo, or picture that can represent the award. For example, if the user earns a 5× win multiplier by remotely participating in the game of chance, the award icon 1326 can be a box printed with a “5×” indicia. In one embodiment, the contact may receive the new award simply by participating in the social game session. The contact may also receive the new award because the player gifted the new award to the contact.
In one embodiment, the contact may select the award icon 1326 to associate and save the award for the contact, transfer the award back to the player, or redeem the award as discussed in detail in
Communication between the social gaming server 1408, the at least one gaming machine 1404a-1404n, and the at least one remote user 1402a-1402n may be conducted through a network 1410 via any combination of wired networks, wireless communication technology, and cellular networks. A wired network can use Category 5 cable, Category 6 cable, fiber optic cable, coaxial cable or other cable types typically used for computer networks. Examples of wireless communications technology may include, but is not limited to, Wi-Fi and Bluetooth. Cellular networks may use CDMA, GSM, or any other common mobile network standards to transmit data at 2G, 3G, 4G or any other data transmission speeds.
The social gaming server 1408 may be configured to distribute or transmit a primary game of chance to the at least one gaming machine 1404a-1404n and/or the at least one remote user 1402a-1402n. The primary game of chance may be reel-based slot games, video poker, video blackjack, electronic table game, lottery games, or any other games of chance. The social gaming server 1408 may be configured to monitor the primary game of chance presented and played on the at least one gaming machine 1404a-1404n. For example, the social gaming server 1408 may monitor whether a bonus game triggering event has occurred in the primary game of chance, whether a jackpot triggering event has occurred in the primary game of chance, and other game of chance events.
The at least one remote users 1402a-1402n may be any device used by a user and configured to and/or capable of communicating with the network 1410. In one embodiment, the remote user 1402a-1402n may be located in a geographical location that is physically separated from or away from the at least one gaming machine 1404a-1404n and/or the gaming environment. In another embodiment, the at least one remote user 1402a-n can be a local user located within or on the premises of the gaming environment. For example, the remote user may be located in a restaurant in the gaming environment and can participate in the social game session using a smart phone configured to communicate with the social gaming sever 1408. In another example, the at least one remote user 1402a-1402n may be playing on another gaming machine 1404a-1404n while participating in a social game session. In still another example, the at least one remote user may be playing on an iPad™ while walking around on a cruise ship.
In one embodiment, the social gaming server 1408 may have a social contact manager 1414. Information or data associated with the at least one remote user 1402a-1402n may be stored in the social contact manager 1414 as one or more social contacts. The social contacts manager 1414 may be configured to store and/or manage one or more social contacts 1402a-1402n for playing a game of chance on a gaming machine. In one embodiment, the one or more social contacts may be stored in a contacts database 1416. In another embodiment, the one or more social contacts may be stored on a third party server 1415. For example, the third party server may be a social networking server configured to store, manage, and associate the one or more social contacts with the player playing the game of chance on the at least one gaming machine 1404a-n. The social contacts manager 1414 may be configured to add contacts, delete contacts, search for contacts, block contacts, and other similar administrative functions as desired by the user
In one embodiment, the social gaming server 1408 may be configured to generate a list of the at least one available remote user. The at least one available remote user may be any remote users 1402a-n that are available to participate, interact, and/or help the user play the game of chance on the gaming machine 1404a-n. In one embodiment, the at least one available remote users 1402a-1402n may be any current remote users connected to the network 1410. For example, the at least one available remote user may be logged onto or in communication with the social contact manager 1414. In another example, the at least one available remote user may be playing a game of chance on the gaming machine configured to communicate with the social gaming server 1408 and/or the social contact manager 1414. In another example, the at least one available remote user may be eating in a restaurant and prompted by the remote user device, such as an iPad™, to connect to the social contact manager 1414.
The list of the at least one available remote user may be a list of remote users 1402a-n that are available to participate, interact, and/or help the user play a game of chance on the at least one gaming machine 1404a-n. The game of chance may be a primary game of chance and/or a bonus game. Once the list of the at least one available remote user is generated, the social gaming server 1408 may be configured to transmit the list of the at least one available remote users to the at least one gaming machine 1404a-n (e.g. as discussed in
The user may select at least one of the at least one available remote users 1402a-1402n presented on the list of the at least one available remote users displayed on a display of the at least one gaming machine 1404a-n. Once selected, the social gaming server 1408 may be configured to receive the selection of the at least one available remote user from the at least one gaming machine 1404a-1404n and distribute or transmit gaming information to the at least one selected available remote user 1402a-n. The gaming information may be gaming information about the primary game of chance or the bonus game. For example, the social gaming server 1408 may be configured to transmit gaming information about the bonus game such as a bonus game feature. The bonus game feature may be any feature used to play or enhance the bonus game. In one example, the bonus game feature may be a roulette wheel. In other words, a roulette wheel may be displayed on the at least gaming machine 1404a-1404n and each of the at least one remote users may be prompted to spin the roulette wheel to participate and/or play a bonus game play. In another example, the bonus game feature may be a dart throwing bonus game whereby players may be prompted to throw a dart at a dart board. In yet another example, the bonus game feature may be a competitive game. The competitive game may be any known competitive game, such as poker, blackjack, car racing, or any other competitive social game. In still another embodiment the bonus game feature may be a collaborative bonus game. For example a plurality of remote users 1402a-n may be used to jointly spin the roulette wheel (e.g. the more remote users that spin the roulette wheel simultaneously, the faster the wheel spins), play a fishing game (e.g. specifically catch a specific fish), and the like.
The social gaming server 1408 may be configured to transmit an invitation to accept or decline the bonus game feature to the at least one selected available remote user 1404a-1404n. In one example, the invitation may include a prompt, button, or voice activated mechanism to initiate the bonus game, such as a “YES” and/or “NO” indicator to accept or decline the invitation. In another embodiment, if the at least one remote user 1402a-n is a local user, acceptance of the invitation may be a click, tap, or any other type of sensory input provided on a sensory device coupled to the at least one gaming machine 1404a-1404n. The sensory input may be transmitted to the social gaming server 1408 for processing.
The social gaming server 1408 may be configured to wait up to a predetermined period of time for acceptance or decline of the invitation and/or a bonus game input associated with the bonus game. In one example, the predetermined period of time may be between about two seconds to five minutes. In another example, the predetermined period of time may be between one minute to three minutes. The predetermined period of time may be presented in a timer window (e.g. timer window 2008 illustrated in
The bonus game input may be initiated by the at least one of the selected remote users 1402a. The bonus game input may be in response to a prompt initiated by the bonus game feature in order to play the bonus game feature. The bonus game input may be a task, a bet, a selection of cards, a click, a tap, or any other known bonus game input. In one embodiment, the bonus game input is a spin of a roulette wheel. In another embodiment, the bonus game input is a card game wager. In still another embodiment, the bonus game input is a throwing of a dart. In yet another embodiment, the bonus game input is racing of a car.
The bonus game information transmitted to the selected remote users and/or 1402a-n and/or the gaming machines 1404a-n can include any game information generated from playing the game of chance such that the social gaming server 1408 can reproduce the game of chance on a display of any user device. For example, the gaming information may include, but is not limited to, number of credits, total amount of time spent playing the gaming of chance at the gaming machine, notification of a win, loss, tie, push, and the like, amount won or lost, wager amount, award earned, notification of a remote input, pay table, and the like. The game information may also be specific to a type of the game of chance being played. For example, if the game of chance is an electronic card game, such as video poker or video blackjack, the game information can include, but is not limited to, cards held by the player, communal cards, and actions taken by the player such as hitting or drawing for new cards and any other game information related to an electronic card game. If the game of chance is a slot game, the game information can include, but is not limited to, contents of the reels, lines being played, notification of lines won, images on the reels, and any game information related to a slot game.
The social gaming server 1408 may be configured to generate a bonus game triggered by a bonus triggering event. The bonus game may be played using the bonus game feature. The social gaming server 1408 may transmit at least a portion of the gaming information to the at least one selected remote user 1402a-1402n and the gaming machine 1404a-1404n to play the bonus game using the bonus game feature. For example, the portion of gaming information transmitted to the at least one selected remote user 1402a-n may include information about the bonus feature input, bonus award, chat logs, and any other gaming information. The portion of gaming information transmitted to the gaming machine 1404a-n may include the bonus feature input, chat logs, and any other gaming information.
The social gaming server 1408 may be configured to transfer a result of the bonus game to the at least one gaming machine 1404a-1404n and the at least one selected remote user 1402a-1402n. In one embodiment, the social gaming server 1408 can calculate the result of the bonus game based on the gaming information. In another embodiment, the social gaming server 1408 may calculate the results of the bonus game based on a predetermined bonus game award distribution.
In one embodiment, the social gaming server 1408 may have a bonus game manager 1412. In another embodiment, the gaming machine 1404a-n may, in addition to or only, have a bonus game manager 1406a-n. The bonus game manager may be configured to communicate with the social gaming server 1408, gaming machines 1404a-n, or any other server to distribute or transmit the bonus game information. In yet another embodiment, the bonus game manager 1412 may be a separate and remote server or device.
The bonus game manager 1412, 1406a-n may also be configured to generate the list of at least one available remote user 1402a-1402n. In one embodiment the bonus game manager 1412 may be configured to communicate with the social contact manager 1414. In another example, the bonus game manager 1412, may be configured to manage the remote users 1402a-n. The bonus game manager 1412 may be configured to perform administrative functions, such as adding, deleting, searching, and blocking remote users 1402a-n. The bonus game manager 1412, 1406a-n may be configured to transmit the list of available remote users 1402a-1402n to the at least one gaming machine 1404a-1404n for display in a list of social contacts (e.g. list of social contacts 1914 as illustrated in
The user may select at least one remote user and the gaming machine 1404a-n may transmit the selection to the bonus game manager 1412. The bonus game manager 1412 may be configured to receive the selection of the at least one remote user 1402a-1402n from the gaming machine 1404a-1404n. The bonus game manager 1412 may then transmit a bonus game feature to each of the at least one selected remote users 1402a-1402n. The bonus game manager 1412 may be configured to wait a predetermined period of time to receive an input from the at least one selected remote user 1402a-1402n. The input may be any type of input, such as the bonus game input, acceptance or rejection of an initiation, and the like. In one embodiment, the predetermined period of time may be between about two seconds to five minutes. In another embodiment, the predetermined period of time may be about between one minute to three minutes. The predetermined period of time may be presented in the timer window (e.g. timer window 2008 illustrated in
If the bonus game is played by the player and remote user, the bonus game manager 1412 may be configured to determine the result of the bonus game and transmit the results to the at least one gaming machine 1404a-1404n and the at least one selected remote user 1402a-1402n. If the bonus game is only played by the player, the bonus game manager 1412 may be configured to determine the result of the bonus game and transmit the results to the gaming machine 1404a-1404n.
If the bonus game is won, the bonus game manager 1412 may distribute a bonus game award, such as a cash award, player tracking points, free buffet coupons, concert tickets, hotel stays, and the like. The bonus game award may be any known type of bonus game award. In one embodiment, the bonus game award may be based on a type or a theme of the bonus game. For example, if the bonus game is a fishing game, the bonus game award may be a free dinner at the seafood buffet.
In one embodiment the user may select at least one bonus award option after the at least one available remote user 1402a-n accepts a bonus game feature invitation, but prior to playing the bonus game. The user may have the option of selecting at least one type of bonus game award from a list of various types of bonus game awards. Once the user receives notice that the at least one selected remote user accepted the bonus game invitation (e.g.
In one embodiment, the bonus award option may be based on a manner of distribution of the bonus award. For example, one distribution option may be to not share the bonus award with any of the remote users participating in the bonus game. In another example, the distribution option may be to receive the at least one remote user non-monetary awards. In still another example, the award distribution option may be based on percentages. For example, the user may elect the percentage amounts and/or the percentages may be predetermined. For example, the player may decide to share only 50% of the bonus award with the remote users that participated in the bonus game.
In yet another example, the bonus award option can be based on a competitive game play. For example, if the bonus game feature is a car race, the player finishing first will receive 50% of the bonus game award, the second place player will receive 30% of the bonus game award, and the third place player will receive 20% of the bonus game award.
If a bonus triggering event is triggered at 1504 then a list of available remote users may be generated at 1506. If no bonus triggering event is triggered at 1504, then the primary game of chance played on the gaming device may continue to be monitored at 1502.
The bonus triggering event may be based on a type and/or theme of the game of chance played. In one embodiment, the bonus triggering event may be triggered by any known bonus triggering events such as achieving a high score on the primary game of chance, achieving a unique combination of numbers or symbols on the primary game of chance, or the like. If the bonus triggering event is triggered, in one embodiment the bonus game manager (e.g. bonus game manager 1412, 1406a-n illustrated in
In one embodiment, the list of available remote users may consist of at least one social contact associated with the player playing the game of chance. For example, the at least one contact may be any remote user within a designated gaming area and available to participate in a bonus game. For example the gaming area may be the casino floor, buffet room, or hotel lobby. The at least one social contact may be stored in a contacts database maintained by a social contacts manager of the social gaming server (e.g. social contacts manager 1414 illustrated in
The list of available remote users may be transmitted to the gaming device at 1508 for selection by the user. The remote user list may be displayed on at least one display of the gaming device. (e.g. social contacts list 1914 illustrated in
In one embodiment, the bonus game feature may be transmitted to a remote user associated with a portable electronic device. In another embodiment the bonus game feature may be transmitted to a remote user associated with or playing on another gaming machine.
Transmission of the bonus game feature may include an invitation to accept or reject the bonus game feature. The invitation to accept or reject may be an invitation to participate, interact with, or help play the primary game of chance. The invitation may include information such a as type of bonus feature, type of primary game of chance, a name of the user or player, predetermined period of time to accept or reject the invitation, and any other desired information and data.
If the selection of at least one remote user is not received at 1510, a determination may be made whether to wait at 1526 for a predetermined period of time. If the predetermined period of time has not elapsed, then the method returns to 1510. During the predetermined period of time, the list of at least one available remote user may be updated to reflect current available remote users until the selection of at least one available remote user is made at 1510. This ensures that only the available remote users are selected to participate in the bonus game session.
If the determination is made that the predetermined period of time has elapsed at 1526, the player may play the bonus game in accordance with a bonus game input at 1518. In other words, the player may play the bonus game alone. In another embodiment, the bonus game feature may be saved to the players account for future game play rather than being played at that moment.
A determination of whether a bonus game input is detected is made at 1514. If a bonus game input is detected at 1514 the bonus game is played in accordance with the bonus game input at 1518. The bonus game input may be any input that signifies that the remote user wants to participate in the bonus game session. In one embodiment, the bonus game input may be an acceptance or rejection of the bonus game invitation. In another embodiment, the bonus game input may be to initiate the bonus game. For example, the user input may be to press a “Spin” button to spin a Wheel of Fortune, press a “Throw” button to throw a dart at a dart board, or any other input to initiate the bonus game.
If the bonus game input is not detected at 1514, a determination is made whether to continue to wait at 1516 for a predetermined period of time. If the predetermined period of time to accept, reject, or initiate bonus game play invitation lapses, then the user may be prompted to select another remote user at 1524. If the selection of another available remote user is received at 1524, then the bonus game feature may be distributed to the selected remote user at 1512. If no selection of another remote available remote user is received at 1524, then the bonus game may be played by the player in accordance with the bonus game input at 1518.
Once play of the bonus game ends, a result of the bonus game may be transmitted to the gaming devices at 1520. The bonus game award, if any, may be distributed at 1522 to the user and the at least one remote user. The bonus game award can be any type of gaming or non-gaming award and may be based on the type and/or theme of the game of chance. The bonus game award may be, for example, a monetary award, a free spin, a multiplier, earning a plurality of loyalty points, and the like. A non-gaming award can be, for example, movie tickets, food coupons, show tickets, and the like.
A determination of whether a bonus triggering event is triggered on the primary game of chance is made at 1604. If the bonus triggering event is triggered at 1604, then a list of at least one available remote user may be received at 1606. The bonus triggering event may be based on a type and/or theme of game played. In one embodiment, a bonus triggering event may be triggered by achieving a high score on the primary game of chance, achieving a unique combination of numbers or symbols in the primary game of chance, or the like.
The list of at least one available remote user may be received from the social gaming server (e.g. social gaming server 1408 illustrated in
The list of at least one available remote user may be displayed on the gaming device at 1608 for selection by the user. If a selection of at least one available remote user is detected at 1610 then the selection of the at the least one available remote user may be transmitted to the social gaming server at 1612. The social gaming server may then transmit a bonus game feature to the selected remote user(s). Detection of the selection by the player may be made via any known detection means such as through physical sensory touch input (i.e use of a touch screen, joystick, and the like), audio input, the user may physically type the name of the remote user, or any other detection means or device.
In one embodiment, the gaming device may transmit the bonus game feature to the social gaming server for substantially real-time transmission of the bonus game feature to the selected remote user(s). The bonus game feature may be any type of feature earned upon triggering of the bonus event, such as at least one free spin, a multiplier earned for a predetermined number of game sessions, a competitive card game played with the at least one remote user, or any other bonus features.
Once the bonus game feature is distributed to the at least one selected remote user(s) at 1612, a determination is made whether a bonus game input is received at 1614. If a bonus game input is received at 1614, the bonus game is played in accordance with the bonus game input at 1618.
In one embodiment, the bonus game feature may first distribute an invitation to each selected remote user to accept or reject the bonus game input. In one example, if the user accepts the bonus game feature, a roulette wheel is distributed to each accepting user and the primary user. Each user is then prompted to place their bets, and the roulette ball is released.
In another embodiment, the bonus game feature is initiated by immediate bonus game feature play. For example, the roulette wheel is distributed to each player. By placing a bet within a predetermined amount of time, the bonus game feature play is initiated for each player that placed the bet.
In one embodiment, if no bonus game input is received at 1614, a determination is made whether to continue to wait for a predetermined amount of time at 1616. If the predetermined period of time to accept, reject, or initiate bonus game play lapses, then selection of other available remote users may be detected at 1624. If a selection of other available remote users is detected at 1624, then the selected remote user may be transmitted to the social gaming server at 1612. If no selection is detected at 1624, then method 1600 ends.
The result of the bonus game may be displayed at 1620. The results of the bonus game may be obtained from the gaming machine or the social gaming server. The results of the bonus game may be based on the determination of the outcome of the bonus game.
The bonus game award, if any, may be distributed to the gaming device and the remote user(s) at 1622. The bonus game award may be distributed by the gaming machine, social gaming server, or any other device. The bonus game award can be any type of gaming or non-gaming award and may be based on the type and/or theme of game. The bonus game award may be, for example, a monetary award, at least one free spin, a multiplier, earning a plurality of points, or the like. A non-gaming award can be, for example, a digital enhancement for the social gaming user interface on the user device and/or on the gaming machine. The digital enhancement can be a wallpaper, a background, a song, new avatar, a picture, any type of other visual and/or auditory aesthetic prizes, movie tickets, food coupons, and the like.
A bonus award distribution menu may be displayed at 1702. The bonus award distribution menu may be displayed on at least one display of the gaming machine, mobile device, or any other device. The bonus award distribution menu may include any known bonus award options, such as type of bonus award (non-gaming vs. gaming, non-cash vs. cash, and the like), amount of bonus award, percentage of distribution (i.e. sharing of the bonus award, if any), and the like. For example, the bonus award option may be monetary or non-monetary awards. In another example, the bonus award options may be based on percentage distribution as discussed below. Another bonus award option may be specific types of bonus awards such as buffet tickets, concert tickets, free hotel stays, social game awards, multipliers, free spin, and the like.
In one embodiment, the bonus award distribution menu may be automatically displayed after a bonus game is earned. In another embodiment, the bonus award distribution menu may be displayed after play of the bonus game completes. In still another embodiment, the bonus award distribution menu may be automatically displayed after a remote user accepts an invitation of a user to participate, interact, and/or play the bonus game. In another embodiment the user may select a bonus award option after the at least one available remote user accepts the bonus game invitation, but prior to playing the bonus game. In yet another embodiment, the user may have the option of selecting at least one type of bonus game award from a variety of bonus game awards. If the user receives notice that the at least one social contact or remote user accepted the bonus game invitation (e.g.
The bonus award distribution menu may list a plurality of award distribution options. For example, one award distribution option may be to not share a monetary award with the remote users participating in the bonus game, but to give the remote user(s) non-monetary awards. Another award distribution option may be to share a specific percentage of the bonus award with the remote users that participated in the bonus game. Still another reward distribution option, can be to distribute the bonus game award based on a competitive bonus game play. For example, if the bonus game feature is a car race, then a player finishing first may receive 50% of the monetary award. A player finishing second may receive 30% of the award, and the player finishing last may receive 20% of the award.
If selection of the bonus game award distribution option is detected at 1704, the bonus award, if any, may be calculated based on the selected award distribution option at 1706. The award earned may be based on the outcome of the bonus game. For example, if money is won by a primary user, other players may receive a gift certificate to a casino buffet or a free hotel stay. In still another example, if there is a monetary award, each player may receive a percentage of the monetary award based upon the user's elected percentage.
The calculated bonus award may be transmitted to the social gaming server at 1708 for transmission to the remote users. The calculated bonus award may also be displayed at 1710 on a display of the gaming device. In one embodiment, an itemized summary or explanation of how the bonus award was distributed may be presented on the display.
The bonus game manager 1802 may be configured to communicate with the social gaming server. In another embodiment, a bonus game manager may be configured to communicate with the gaming machine. However, these are not intended to be limiting as the bonus game manager 1802 may be in communication with any other server or device.
The bonus game feature 1804 may be any known multi-player social bonus game. In one example, the bonus game feature may be a roulette wheel. In another example, the bonus game feature may be throwing darts at a dart board. In another example, the bonus game feature may be a competitive game. The competitive game may be any known competitive game, such as poker, black jack, darts, car racing, or any other group bonus games. In still another embodiment the bonus game feature is a collaborative bonus game such as a game where each user must jointly spin a wheel simultaneously.
The bonus game preferences 1806 may be any known bonus game preferences including award distribution options, settings (e.g. font, volume, display brightness, music, and the like), and the like.
Bonus game award preferences may include a plurality of award distribution options. For example, one award distribution option may be to not share the monetary award with the remote users participating in the bonus game of chance, but to share non-monetary awards with the remote user(s). Another award distribution option may be to share a specific percentage of the bonus award with the remote users that participated in the bonus game of chance. Still another option is to distribute the bonus game award based on a competitive bonus game play. For example, if the bonus game feature is a car race, then the player finishing first will receive 50%, the second place finisher will receive 30%, and the third place finisher will receive 20% of the bonus award.
In one embodiment, the bonus game preference may include the type of bonus game that is to be played. They type of bonus game feature may be a competitive, multi-player, collaborative or any other known type of group bonus games.
In another embodiment, the bonus game preference may be the gaming establishment settings for the bonus game play. Gaming establishment preferences may include how often bonus game features are triggered, the type of prizes, the amount of prizes, how many remote users can participate in the bonus game, the type of remote users that can participate in the bonus game, and any other preference that the gaming establishment may have for social bonus game feature play. In one embodiment, the preferences may be necessary to comply with state, local, city, county, or country laws.
The bonus game information 1808 may be any information needed to facilitate bonus game feature play. In one embodiment, bonus game information may be transmitted between the social gaming server, gaming machine(s), and any other server or device. The bonus game information may be any known type of bonus game information such as speed of game play, music, colors of the bonus game feature, bonus game statistics, and type of awards offered. In one example, the bonus game information is the input from the other remote users playing the bonus game feature. In another example, the bonus game information may be the chat messages between all the players. In still another example, the bonus game information may be any type of information about the bonus game.
The GUI 1902 may further include a social contact list 1914 that can display and provide the user access to a plurality of social contacts. The social contacts may be obtained from, for example, the social contacts manager, a third party server, or any other server or database configured or designed to store a contact list. The user can select one or more contacts from the social contact list 1914 while playing the game of chance to facilitate a social gaming atmosphere. For example, the user might earn a bonus game and decide to invite one or more of the social contacts to participate, interact, or help play the bonus game. In one embodiment, the social contact list 1914 may include a plurality of controls configured to manipulate the social contact list 1914, such as a sort indicator 1916, a search indicator 1918, or any other control elements, e.g. joystick, speaker and/or microphone for audio interactions.
The social contact list 1914 may include availability indicators 1911a-n. The availability indicators may indicate which social users are available to participate in a bonus game session. The available indicators 1911a-n may be any type of indicator and may take any shape, form, and/or color. For example, as illustrated, the availability indicator may be a darkened circle if the social contact is available and not darkened if the social contact is not available. In another example, if the player selects the social contact, the availability indicator may change shape and/or color. As illustrated in
In another embodiment, only available social users may be displayed in the social contact list 1914. Thus, the available indicators 1911a-n may illustrate which social users are chatting with the player, which social users are playing on another gaming machine, which social users are in the gaming area, or any other user-defined criteria to filter the social contact list 1914.
The GUI 1902 may further include a communication window 1920. The communication window 1920 can allow the user to interact and/or communicate with one or more contacts from the social contact list 1914. For example, the user can communicate and/or chat with the one or more social contacts about the game of chance being played, an invitation to participate, view, or help play a bonus game, sports, movies, or any other interests or topics.
The GUI 1902 may further include a session log window 1922. The session log window 1922 can display a plurality of events from a social gaming session in real-time as the events occur. The social gaming session may include play of the primary game of chance and/or the bonus game. As illustrated in
The GUI 1902 may further include a bonus game notification window 1924. The bonus game notification window 1924 may be displayed on the display 1900 when a bonus-triggering event has been triggered. The bonus game notification window 1924 may be configured to inform the user of the bonus game event. As illustrated, the bonus game notification window 1924 may be displayed over the gaming window 1904. However, in another embodiment, the bonus game notification window 1924 may be displayed on another display of the gaming machine or any other area of display 1900.
In one embodiment, the bonus game notification window 1924 may determine whether the user would like to have at least one social contact participate in the bonus game. For example, the bonus game notification window 1924 may display “Do you want to share the bonus game with your contacts?” and present a “YES” indicator 1930 and a “NO” indicator 1932.
If the user wants to share the bonus game, the user may select the “YES” indicator 1930. Referring now to
The user may select at least one social contact from the social contacts list 1914. As illustrated, using a touch screen display, the user selected “Zack” 1928. The user's selection of the at least one social contact may be transmitted to the social game server for processing. In one embodiment, the user can communicate or chat with Zack using the communication window 1920. For example, the user can enter text such as “Please join my bonus game” using a touch screen available on the GUI 1902. The session log window 1922 can also be automatically and periodically updated to reflect the events from the social gaming session. For example, the session log window 1922 can display “Waiting for Zack's responses.”
For example, the bonus gaming notification window 2014 displayed on the GUI 2004 may present “CONGRATULATIONS! Ray would like to share his bonus game with you. Do you want to play?” A “YES” indicator 2016 and a “NO” indicator 2018 may also be displayed in the bonus gaming notification window 2014. A timer window 2008 may be presented on the GUI 2004. The timer window 2008 may be configured to inform the user of the time left to accept or decline the bonus game invitation. In one embodiment, the selected contact may have a predetermined period of time to accept, decline, or ignore the bonus game invitation. In one embodiment, the predetermined period of time may be between about two seconds to five minutes. In another embodiment, the predetermined period of time may be between one minute to three minutes. As illustrated in the timer window 2008, the selected contact may have thirty seconds to accept the bonus game invitation.
The GUI 2004 may also present a communication window 2010. The communication window 2010 may be configured or designed to allow the user and other social contacts to communicate. For example, as illustrated, Ray can communicate to Zack: “Please join my bonus game”. This provides for a social gaming atmosphere where Zack may be invited to participate in the bonus game. This promotes and provides for a social gaming atmosphere where the players feel they have a stake in the game and are more willing to participate and/or watch the game of chance being played.
The GUI 2004 may also present a session log window 2012. The session log window 2012 can be configured or designed to display a plurality of events from a social gaming session and can also be automatically and periodically updated to reflect the events from the social gaming session. The session log window 2012 may include information from the game of chance and/or the bonus game. As illustrated, the session log window 2012 may display “Waiting for Zack to respond.”
The social contact, e.g. Zack, may select the “YES” indicator 2016 if he would like to participate in the bonus game session. Detection of the “YES” indicator 2016 or the “NO” indicator 2018 may be transmitted to the social game server for processing.
In one embodiment, the user can communicate or chat with Zack in real-time using the communication window 2106. The communication window 2106 may be updated frequently to receive communication from other users and/or players. For example, the user can view Zack's response: “Thanks, I'm in!”.
The session log window 2108 can also be automatically and periodically updated to reflect the events from the social gaming session. For example, the session log window 2108 can display “Waiting for Zack's responses”, and “Zack accepted your invitation to play the bonus game.”
The GUI 2102 may also present a communication window 2156. The communication window 2106 may be updated frequently to receive communication from other users and/or players. For example, the communication window 2156 may contain a response from Zack: “Thanks, but I'm busy. Maybe next time.”, indicating that Zack denied the bonus game invitation.
The GUI 2102 may also present a session log window 2158. The session log window 2158 may include information from the game of chance and/or the bonus game. The session log window 2158 can also be automatically and periodically updated to reflect the events from the social gaming session. For example, the session log window 2158 may indicate that the gaming machine is waiting for the user to make another social contact selection.
In one embodiment, the user may be prompted to select another social contact. For example, the GUI 2102 may display “Do you want to select another contact?”, a “YES” indicator 2160, and a “NO” indicator 2162. In one embodiment, the user may then select another social contact from the social contact list 2154. For example, as illustrated, the user may select Shannon 2164 to receive a bonus game invitation.
In yet another embodiment, the user may decide to not select another social contact and play the bonus game himself. The user may select the “NO” indicator 2162. The detected selection may be transmitted to the social game server for processing. In other words, the bonus game session may be played solely by the user and with other social contacts.
The GUI 2202 may also present a session log window 2212. The session log window 2212 may include information from the game of chance and/or the bonus game. The session log window 2212 can also be automatically and periodically updated to reflect the events from the social gaming session. For example, the session log window 2212 may indicate that the gaming machine is waiting for the user to select a bonus game award distribution option.
The session log 2316 may also be automatically updated to reflect the events of the social gaming session. For example, the session log 2316 can indicate “Waiting for bonus game award selection.”
The session log 2508 may also automatically and periodically be updated to reflect the events of the social gaming session. For example, the session log 2508 as illustrated can indicate “Bonus game initiated” and “Bonus game finished.”
Referring now to
The user may communicate with a social contact to determine whether to keep or reject the coupon. In other words, the user may use communication window 2610 to ask if Zack would like the free buffet coupon. As illustrated in the communication window, if the social contact would like the bonus award, the player may press the “No” indicator and grant it to a social contact. The social contact may or may not have participated in the bonus game session.
Referring now to
While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein.
This application is a continuation of U.S. patent application Ser. No. 13/843,087, filed Mar. 15, 2013 and entitled “Temporary Grant of Real-time Bonus Feature,” which is hereby incorporated herein by reference in its entirety for all purposes, and which in turn is continuation-in-part of U.S. patent application Ser. No. 13/296,182, filed Nov. 14, 2011 and entitled “Social Gaming,” which is hereby incorporated herein by reference in its entirety for all purposes, and which in turn claims priority to U.S. Provisional Application No. 61/413,477, filed Nov. 14, 2010, and entitled “Social Gaming,” which is hereby incorporated herein by reference in its entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2033638 | Koppl | Mar 1936 | A |
| 2062923 | Nagy | Dec 1936 | A |
| 4741539 | Sutton et al. | May 1988 | A |
| 4948138 | Pease et al. | Aug 1990 | A |
| 5067712 | Georgilas | Nov 1991 | A |
| 5429361 | Raven et al. | Jul 1995 | A |
| 5489103 | Okamoto | Feb 1996 | A |
| 5630757 | Gagin | May 1997 | A |
| 5655961 | Acres et al. | Aug 1997 | A |
| 5704835 | Dietz, II | Jan 1998 | A |
| 5727786 | Weingardt | Mar 1998 | A |
| 5833537 | Barrie | Nov 1998 | A |
| 5919091 | Bell et al. | Jul 1999 | A |
| 5947820 | Morro et al. | Sep 1999 | A |
| 5997401 | Crawford | Dec 1999 | A |
| 6001016 | Walker et al. | Dec 1999 | A |
| 6039648 | Guinn et al. | Mar 2000 | A |
| 6059289 | Vancura | May 2000 | A |
| 6089977 | Bennett | Jul 2000 | A |
| 6095920 | Sudahiro | Aug 2000 | A |
| 6110041 | Walker et al. | Aug 2000 | A |
| 6142872 | Walker et al. | Nov 2000 | A |
| 6146273 | Olsen | Nov 2000 | A |
| 6165071 | Weiss | Dec 2000 | A |
| 6231445 | Acres | May 2001 | B1 |
| 6270412 | Crawford et al. | Aug 2001 | B1 |
| 6290600 | Glasson | Sep 2001 | B1 |
| 6293866 | Walker et al. | Sep 2001 | B1 |
| 6353390 | Beri et al. | Mar 2002 | B1 |
| 6364768 | Acres et al. | Apr 2002 | B1 |
| 6404884 | Marwell et al. | Jun 2002 | B1 |
| 6416406 | Duhamel | Jul 2002 | B1 |
| 6416409 | Jordan | Jul 2002 | B1 |
| 6443452 | Brune | Sep 2002 | B1 |
| 6491584 | Graham et al. | Dec 2002 | B2 |
| 6505095 | Kolls | Jan 2003 | B1 |
| 6508710 | Paravia et al. | Jan 2003 | B1 |
| 6561900 | Baerlocker et al. | May 2003 | B1 |
| 6592457 | Frohm et al. | Jul 2003 | B1 |
| 6612574 | Cole et al. | Sep 2003 | B1 |
| 6620046 | Rowe | Sep 2003 | B2 |
| 6641477 | Dietz, II | Nov 2003 | B1 |
| 6645078 | Mattice | Nov 2003 | B1 |
| 6719630 | Seelig et al. | Apr 2004 | B1 |
| 6749510 | Giobbi | Jun 2004 | B2 |
| 6758757 | Luciano, Jr. et al. | Jul 2004 | B2 |
| 6773345 | Walker et al. | Aug 2004 | B2 |
| 6778820 | Tendler | Aug 2004 | B2 |
| 6780111 | Cannon et al. | Aug 2004 | B2 |
| 6799032 | McDonnell et al. | Sep 2004 | B2 |
| 6800027 | Giobbi et al. | Oct 2004 | B2 |
| 6804763 | Stockdale et al. | Oct 2004 | B1 |
| 6811486 | Luciano, Jr. | Nov 2004 | B1 |
| 6843725 | Nelson | Jan 2005 | B2 |
| 6846238 | Wells | Jan 2005 | B2 |
| 6848995 | Walker et al. | Feb 2005 | B1 |
| 6852029 | Baltz et al. | Feb 2005 | B2 |
| 6869361 | Sharpless et al. | Mar 2005 | B2 |
| 6875106 | Weiss et al. | Apr 2005 | B2 |
| 6884170 | Rowe | Apr 2005 | B2 |
| 6884172 | Lloyd et al. | Apr 2005 | B1 |
| 6902484 | Idaka | Jun 2005 | B2 |
| 6908390 | Nguyen et al. | Jun 2005 | B2 |
| 6913532 | Bearlocher et al. | Jul 2005 | B2 |
| 6923721 | Luciano et al. | Aug 2005 | B2 |
| 6935958 | Nelson | Aug 2005 | B2 |
| 6949022 | Showers | Sep 2005 | B1 |
| 6955600 | Glavich et al. | Oct 2005 | B2 |
| 6971956 | Rowe et al. | Dec 2005 | B2 |
| 6984174 | Cannon et al. | Jan 2006 | B2 |
| 6997803 | LeMay et al. | Feb 2006 | B2 |
| 7018292 | Tracy et al. | Mar 2006 | B2 |
| 7032115 | Kashani | Apr 2006 | B2 |
| 7033276 | Walker et al. | Apr 2006 | B2 |
| 7035626 | Luciano | Apr 2006 | B1 |
| 7037195 | Schneider et al. | May 2006 | B2 |
| 7048628 | Schneider | May 2006 | B2 |
| 7048630 | Berg et al. | May 2006 | B2 |
| 7063617 | Brosnan et al. | Jun 2006 | B2 |
| 7076329 | Kolls | Jul 2006 | B1 |
| 7089264 | Guido et al. | Aug 2006 | B1 |
| 7094148 | Bearlocher et al. | Aug 2006 | B2 |
| 7105736 | Laakso | Sep 2006 | B2 |
| 7111141 | Nelson | Sep 2006 | B2 |
| 7144321 | Mayeroff | Dec 2006 | B2 |
| 7152783 | Chaffin | Dec 2006 | B2 |
| 7169041 | Tessmer et al. | Jan 2007 | B2 |
| 7169052 | Beaulieu et al. | Jan 2007 | B2 |
| 7175523 | Gilmore et al. | Feb 2007 | B2 |
| 7181228 | Boesch | Feb 2007 | B2 |
| 7182690 | Giobbi et al. | Feb 2007 | B2 |
| RE39644 | Alcorn et al. | May 2007 | E |
| 7243104 | Bill | Jul 2007 | B2 |
| 7247098 | Bradford et al. | Jul 2007 | B1 |
| 7259718 | Patterson et al. | Aug 2007 | B2 |
| 7275989 | Moody | Oct 2007 | B2 |
| 7285047 | Gielb et al. | Oct 2007 | B2 |
| 7311608 | Danieli | Dec 2007 | B1 |
| 7314408 | Cannon et al. | Jan 2008 | B2 |
| 7316615 | Soltys et al. | Jan 2008 | B2 |
| 7316619 | Nelson | Jan 2008 | B2 |
| 7318775 | Brosnan et al. | Jan 2008 | B2 |
| 7326116 | O'Donovan et al. | Feb 2008 | B2 |
| 7330108 | Thomas | Feb 2008 | B2 |
| 7346358 | Wood et al. | Mar 2008 | B2 |
| 7355112 | Laakso | Apr 2008 | B2 |
| 7384338 | Rothschild et al. | Jun 2008 | B2 |
| 7387571 | Walker et al. | Jun 2008 | B2 |
| 7393278 | Gerson et al. | Jul 2008 | B2 |
| 7396990 | Lu et al. | Jul 2008 | B2 |
| 7415426 | Williams et al. | Aug 2008 | B2 |
| 7425177 | Rodgers et al. | Sep 2008 | B2 |
| 7427234 | Soltys et al. | Sep 2008 | B2 |
| 7427236 | Kaminkow et al. | Sep 2008 | B2 |
| 7427708 | Ohmura | Sep 2008 | B2 |
| 7431650 | Kessman | Oct 2008 | B2 |
| 7448949 | Kaminkow et al. | Nov 2008 | B2 |
| 7500913 | Baerlocher | Mar 2009 | B2 |
| 7510474 | Carter | Mar 2009 | B2 |
| 7513828 | Nguyen et al. | Apr 2009 | B2 |
| 7519838 | Suurballe | Apr 2009 | B1 |
| 7559838 | Walker et al. | Jul 2009 | B2 |
| 7563167 | Walker et al. | Jul 2009 | B2 |
| 7572183 | Olivas et al. | Aug 2009 | B2 |
| 7585222 | Muir | Sep 2009 | B2 |
| 7602298 | Thomas | Oct 2009 | B2 |
| 7607174 | Kashchenko et al. | Oct 2009 | B1 |
| 7611409 | Muir et al. | Nov 2009 | B2 |
| 7637810 | Amaitis et al. | Dec 2009 | B2 |
| 7644861 | Alderucci et al. | Jan 2010 | B2 |
| 7653757 | Fernald et al. | Jan 2010 | B1 |
| 7693306 | Huber | Apr 2010 | B2 |
| 7699703 | Muir et al. | Apr 2010 | B2 |
| 7722453 | Lark et al. | May 2010 | B2 |
| 7758423 | Foster et al. | Jul 2010 | B2 |
| 7771271 | Walker et al. | Aug 2010 | B2 |
| 7780529 | Rowe et al. | Aug 2010 | B2 |
| 7780531 | Englman et al. | Aug 2010 | B2 |
| 7785192 | Canterbury et al. | Aug 2010 | B2 |
| 7811172 | Asher et al. | Oct 2010 | B2 |
| 7819749 | Fish | Oct 2010 | B1 |
| 7822688 | Labron | Oct 2010 | B2 |
| 7828652 | Nguyen et al. | Nov 2010 | B2 |
| 7828654 | Carter | Nov 2010 | B2 |
| 7828661 | Fish | Nov 2010 | B1 |
| 7850528 | Wells | Dec 2010 | B2 |
| 7874919 | Paulsen et al. | Jan 2011 | B2 |
| 7877798 | Saunders et al. | Jan 2011 | B2 |
| 7883413 | Paulsen | Feb 2011 | B2 |
| 7892097 | Muir et al. | Feb 2011 | B2 |
| 7909692 | Nguyen et al. | Mar 2011 | B2 |
| 7909699 | Parrott et al. | Mar 2011 | B2 |
| 7918728 | Nguyen et al. | Apr 2011 | B2 |
| 7927211 | Rowe et al. | Apr 2011 | B2 |
| 7927212 | Hedrick et al. | Apr 2011 | B2 |
| 7951008 | Wolf et al. | May 2011 | B2 |
| 8057298 | Nguyen et al. | Nov 2011 | B2 |
| 8057303 | Rasmussen | Nov 2011 | B2 |
| 8087988 | Nguyen et al. | Jan 2012 | B2 |
| 8117608 | Slettehaugh | Feb 2012 | B1 |
| 8133113 | Nguyen | Mar 2012 | B2 |
| 8182326 | Speer et al. | May 2012 | B2 |
| 8210927 | Hedrick | Jul 2012 | B2 |
| 8221245 | Walker | Jul 2012 | B2 |
| 8226459 | Barrett | Jul 2012 | B2 |
| 8226474 | Nguyen et al. | Jul 2012 | B2 |
| 8231456 | Zielinski | Jul 2012 | B2 |
| 8235803 | Loose et al. | Aug 2012 | B2 |
| 8282475 | Nguyen et al. | Oct 2012 | B2 |
| 8323099 | Durham et al. | Dec 2012 | B2 |
| 8337290 | Nguyen et al. | Dec 2012 | B2 |
| 8342946 | Amaitis | Jan 2013 | B2 |
| 8393948 | Allen et al. | Mar 2013 | B2 |
| 8403758 | Homik | Mar 2013 | B2 |
| 8430745 | Agarwal et al. | Apr 2013 | B2 |
| 8461958 | Saenz | Jun 2013 | B2 |
| 8469813 | Joshi | Jun 2013 | B2 |
| 8529345 | Nguyen | Sep 2013 | B2 |
| 8602875 | Nguyen | Dec 2013 | B2 |
| 8613655 | Kisenwether | Dec 2013 | B2 |
| 8613659 | Nelson et al. | Dec 2013 | B2 |
| 8696470 | Nguyen | Apr 2014 | B2 |
| 8745417 | Huang et al. | Jun 2014 | B2 |
| 8858323 | Nguyen et al. | Oct 2014 | B2 |
| 8864586 | Nguyen | Oct 2014 | B2 |
| 8942995 | Kerr | Jan 2015 | B1 |
| 9039507 | Allen et al. | May 2015 | B2 |
| 9235952 | Nguyen | Jan 2016 | B2 |
| 9292996 | Davis et al. | Mar 2016 | B2 |
| 9325203 | Nguyen | Apr 2016 | B2 |
| 9466171 | Hornik | Oct 2016 | B2 |
| 9486697 | Nguyen | Nov 2016 | B2 |
| 9486704 | Nguyen | Nov 2016 | B2 |
| 9576425 | Nguyen | Feb 2017 | B2 |
| 9626826 | Nguyen | Apr 2017 | B2 |
| 9741205 | Nguyen | Aug 2017 | B2 |
| 9811973 | Nguyen | Nov 2017 | B2 |
| 9814970 | Nguyen | Nov 2017 | B2 |
| 9842462 | Nguyen | Dec 2017 | B2 |
| 9875606 | Nguyen | Jan 2018 | B2 |
| 9875609 | Nguyen | Jan 2018 | B2 |
| 20010004607 | Olsen | Jun 2001 | A1 |
| 20010016516 | Takatsuka | Aug 2001 | A1 |
| 20010024971 | Brossard | Sep 2001 | A1 |
| 20010047291 | Garahi | Nov 2001 | A1 |
| 20020006822 | Krintzman | Jan 2002 | A1 |
| 20020042295 | Walker et al. | Apr 2002 | A1 |
| 20020111210 | Luciano, Jr. et al. | Aug 2002 | A1 |
| 20020111213 | McEntee et al. | Aug 2002 | A1 |
| 20020113369 | Weingardt | Aug 2002 | A1 |
| 20020116615 | Nguyen et al. | Aug 2002 | A1 |
| 20020133418 | Hammond et al. | Sep 2002 | A1 |
| 20020137217 | Rowe et al. | Sep 2002 | A1 |
| 20020142825 | Lark et al. | Oct 2002 | A1 |
| 20020147047 | Letovsky et al. | Oct 2002 | A1 |
| 20020147049 | Carter, Sr. | Oct 2002 | A1 |
| 20020151366 | Walker et al. | Oct 2002 | A1 |
| 20020167536 | Valdes et al. | Nov 2002 | A1 |
| 20020183105 | Cannon | Dec 2002 | A1 |
| 20030001338 | Bennett et al. | Jan 2003 | A1 |
| 20030008696 | Abecassis et al. | Jan 2003 | A1 |
| 20030027635 | Walker et al. | Feb 2003 | A1 |
| 20030064805 | Wells | Apr 2003 | A1 |
| 20030064807 | Walker et al. | Apr 2003 | A1 |
| 20030092480 | White et al. | May 2003 | A1 |
| 20030100361 | Sharpless et al. | May 2003 | A1 |
| 20030104860 | Cannon et al. | Jun 2003 | A1 |
| 20030104865 | Itkis et al. | Jun 2003 | A1 |
| 20030148809 | Nelson | Aug 2003 | A1 |
| 20030162588 | Brosnan et al. | Aug 2003 | A1 |
| 20030195024 | Slattery | Oct 2003 | A1 |
| 20030199295 | Vancura | Oct 2003 | A1 |
| 20030224852 | Walker et al. | Dec 2003 | A1 |
| 20030224854 | Joao | Dec 2003 | A1 |
| 20040002386 | Wolfe et al. | Jan 2004 | A1 |
| 20040005919 | Walker et al. | Jan 2004 | A1 |
| 20040023709 | Beaulieu et al. | Feb 2004 | A1 |
| 20040023716 | Gauselmann | Feb 2004 | A1 |
| 20040038736 | Bryant | Feb 2004 | A1 |
| 20040048650 | Mierau et al. | Mar 2004 | A1 |
| 20040068460 | Feeley | Apr 2004 | A1 |
| 20040082385 | Silva et al. | Apr 2004 | A1 |
| 20040106449 | Walker et al. | Jun 2004 | A1 |
| 20040127277 | Walker | Jul 2004 | A1 |
| 20040127290 | Walker et al. | Jul 2004 | A1 |
| 20040137987 | Nguyen et al. | Jul 2004 | A1 |
| 20040147308 | Walker et al. | Jul 2004 | A1 |
| 20040152508 | Lind | Aug 2004 | A1 |
| 20040214622 | Atkinson | Oct 2004 | A1 |
| 20040224753 | Odonovan et al. | Nov 2004 | A1 |
| 20040256803 | Ko | Dec 2004 | A1 |
| 20040259633 | Gentles et al. | Dec 2004 | A1 |
| 20050003890 | Hedrick et al. | Jan 2005 | A1 |
| 20050004980 | Vadjinia | Jan 2005 | A1 |
| 20050026696 | Hashimoto et al. | Feb 2005 | A1 |
| 20050054446 | Kammler | Mar 2005 | A1 |
| 20050101376 | Walker | May 2005 | A1 |
| 20050101383 | Wells | May 2005 | A1 |
| 20050130728 | Nguyen et al. | Jun 2005 | A1 |
| 20050137014 | Vetelaninen | Jun 2005 | A1 |
| 20050181865 | Luciano | Aug 2005 | A1 |
| 20050181870 | Nguyen et al. | Aug 2005 | A1 |
| 20050181875 | Hoehne | Aug 2005 | A1 |
| 20050187020 | Amaitis et al. | Aug 2005 | A1 |
| 20050202875 | Murphy et al. | Sep 2005 | A1 |
| 20050209002 | Blythe et al. | Sep 2005 | A1 |
| 20050221881 | Lannert | Oct 2005 | A1 |
| 20050223219 | Gatto et al. | Oct 2005 | A1 |
| 20050239546 | Hedrick | Oct 2005 | A1 |
| 20050255919 | Nelson | Nov 2005 | A1 |
| 20050273635 | Wilcox et al. | Dec 2005 | A1 |
| 20050277471 | Russell et al. | Dec 2005 | A1 |
| 20050282637 | Gatto et al. | Dec 2005 | A1 |
| 20060009283 | Englman et al. | Jan 2006 | A1 |
| 20060036874 | Cockerille | Feb 2006 | A1 |
| 20060046822 | Kaminkow et al. | Mar 2006 | A1 |
| 20060046830 | Webb | Mar 2006 | A1 |
| 20060046849 | Kovacs | Mar 2006 | A1 |
| 20060068893 | Jaffe et al. | Mar 2006 | A1 |
| 20060073869 | LeMay et al. | Apr 2006 | A1 |
| 20060073897 | Englman et al. | Apr 2006 | A1 |
| 20060079317 | Flemming et al. | Apr 2006 | A1 |
| 20060148551 | Walker et al. | Jul 2006 | A1 |
| 20060189382 | Muir | Aug 2006 | A1 |
| 20060217170 | Roireau | Sep 2006 | A1 |
| 20060217193 | Walker et al. | Sep 2006 | A1 |
| 20060247028 | Brosnan et al. | Nov 2006 | A1 |
| 20060247035 | Rowe et al. | Nov 2006 | A1 |
| 20060252530 | Oberberger et al. | Nov 2006 | A1 |
| 20060253481 | Guido et al. | Nov 2006 | A1 |
| 20060281525 | Borissov | Dec 2006 | A1 |
| 20060281541 | Nguyen et al. | Dec 2006 | A1 |
| 20060287106 | Jensen | Dec 2006 | A1 |
| 20070004510 | Underdahl et al. | Jan 2007 | A1 |
| 20070026935 | Wolf et al. | Feb 2007 | A1 |
| 20070026942 | Kinsley | Feb 2007 | A1 |
| 20070054739 | Amaitis et al. | Mar 2007 | A1 |
| 20070060254 | Muir | Mar 2007 | A1 |
| 20070060306 | Amaitis et al. | Mar 2007 | A1 |
| 20070060319 | Block et al. | Mar 2007 | A1 |
| 20070060358 | Amaitas et al. | Mar 2007 | A1 |
| 20070077981 | Hungate et al. | Apr 2007 | A1 |
| 20070087833 | Feeney et al. | Apr 2007 | A1 |
| 20070087834 | Moser et al. | Apr 2007 | A1 |
| 20070093299 | Bergeron | Apr 2007 | A1 |
| 20070129123 | Eryou et al. | Jun 2007 | A1 |
| 20070149279 | Norden et al. | Jun 2007 | A1 |
| 20070149286 | Bemmel | Jun 2007 | A1 |
| 20070159301 | Hirt et al. | Jul 2007 | A1 |
| 20070161402 | Ng et al. | Jul 2007 | A1 |
| 20070184896 | Dickerson | Aug 2007 | A1 |
| 20070184904 | Lee | Aug 2007 | A1 |
| 20070191109 | Crowder et al. | Aug 2007 | A1 |
| 20070207852 | Nelson et al. | Sep 2007 | A1 |
| 20070207854 | Wolf et al. | Sep 2007 | A1 |
| 20070238505 | Okada | Oct 2007 | A1 |
| 20070241187 | Alderucci et al. | Oct 2007 | A1 |
| 20070248036 | Nevalainen | Oct 2007 | A1 |
| 20070257430 | Hardy et al. | Nov 2007 | A1 |
| 20070259713 | Fiden et al. | Nov 2007 | A1 |
| 20070259717 | Mattice et al. | Nov 2007 | A1 |
| 20070270213 | Nguyen et al. | Nov 2007 | A1 |
| 20070275777 | Walker et al. | Nov 2007 | A1 |
| 20070275779 | Amaitis et al. | Nov 2007 | A1 |
| 20070281782 | Amaitis et al. | Dec 2007 | A1 |
| 20070281785 | Amaitas et al. | Dec 2007 | A1 |
| 20070298873 | Nguyen et al. | Dec 2007 | A1 |
| 20080015032 | Bradford et al. | Jan 2008 | A1 |
| 20080020824 | Cuddy et al. | Jan 2008 | A1 |
| 20080032787 | Low et al. | Feb 2008 | A1 |
| 20080070652 | Nguyen et al. | Mar 2008 | A1 |
| 20080070681 | Marks et al. | Mar 2008 | A1 |
| 20080076505 | Nguyen | Mar 2008 | A1 |
| 20080076506 | Nguyen et al. | Mar 2008 | A1 |
| 20080076548 | Paulsen | Mar 2008 | A1 |
| 20080076572 | Nguyen et al. | Mar 2008 | A1 |
| 20080096650 | Baerlocher | Apr 2008 | A1 |
| 20080102956 | Burman et al. | May 2008 | A1 |
| 20080102957 | Burnman et al. | May 2008 | A1 |
| 20080113772 | Burrill et al. | May 2008 | A1 |
| 20080119267 | Denlay | May 2008 | A1 |
| 20080146321 | Parente | Jun 2008 | A1 |
| 20080150902 | Edpalm et al. | Jun 2008 | A1 |
| 20080153583 | Huntley et al. | Jun 2008 | A1 |
| 20080161110 | Campbell | Jul 2008 | A1 |
| 20080167106 | Lutnick et al. | Jul 2008 | A1 |
| 20080182667 | Davis et al. | Jul 2008 | A1 |
| 20080200251 | Alderucci | Aug 2008 | A1 |
| 20080207307 | Cunningham, II et al. | Aug 2008 | A1 |
| 20080214258 | Brosnan et al. | Sep 2008 | A1 |
| 20080215319 | Lu | Sep 2008 | A1 |
| 20080234047 | Nguyen | Sep 2008 | A1 |
| 20080238610 | Rosenbereg | Oct 2008 | A1 |
| 20080248849 | Lutnick | Oct 2008 | A1 |
| 20080252419 | Batchelor | Oct 2008 | A1 |
| 20080254878 | Sauders et al. | Oct 2008 | A1 |
| 20080254881 | Lutnick et al. | Oct 2008 | A1 |
| 20080254883 | Patel et al. | Oct 2008 | A1 |
| 20080254891 | Sauders et al. | Oct 2008 | A1 |
| 20080254892 | Sauders et al. | Oct 2008 | A1 |
| 20080254897 | Sauders et al. | Oct 2008 | A1 |
| 20080263173 | Weber et al. | Oct 2008 | A1 |
| 20080300058 | Sum et al. | Dec 2008 | A1 |
| 20080305864 | Kelly et al. | Dec 2008 | A1 |
| 20080305865 | Kelly et al. | Dec 2008 | A1 |
| 20080305866 | Kelly et al. | Dec 2008 | A1 |
| 20080311994 | Amaitas et al. | Dec 2008 | A1 |
| 20080318669 | Buchholz | Dec 2008 | A1 |
| 20080318686 | Crowder et al. | Dec 2008 | A1 |
| 20090005165 | Arezina et al. | Jan 2009 | A1 |
| 20090011822 | Englman | Jan 2009 | A1 |
| 20090029766 | Lutnick et al. | Jan 2009 | A1 |
| 20090054149 | Brosnan et al. | Feb 2009 | A1 |
| 20090077396 | Tsai et al. | Mar 2009 | A1 |
| 20090088258 | Saunders et al. | Apr 2009 | A1 |
| 20090098925 | Gagner et al. | Apr 2009 | A1 |
| 20090104977 | Zielinski | Apr 2009 | A1 |
| 20090104983 | Okada | Apr 2009 | A1 |
| 20090118002 | Lyons | May 2009 | A1 |
| 20090118013 | Finnimore et al. | May 2009 | A1 |
| 20090118022 | Lyons et al. | May 2009 | A1 |
| 20090124366 | Aoki et al. | May 2009 | A1 |
| 20090124390 | Seelig et al. | May 2009 | A1 |
| 20090131151 | Harris et al. | May 2009 | A1 |
| 20090132163 | Ashley et al. | May 2009 | A1 |
| 20090137255 | Ashley et al. | May 2009 | A1 |
| 20090138133 | Buchholz et al. | May 2009 | A1 |
| 20090149245 | Fabbri | Jun 2009 | A1 |
| 20090149261 | Chen et al. | Jun 2009 | A1 |
| 20090153342 | Thorn | Jun 2009 | A1 |
| 20090156303 | Kiely et al. | Jun 2009 | A1 |
| 20090176578 | Herrmann et al. | Jul 2009 | A1 |
| 20090191962 | Hardy et al. | Jul 2009 | A1 |
| 20090197684 | Arezina et al. | Aug 2009 | A1 |
| 20090216547 | Canora et al. | Aug 2009 | A1 |
| 20090219901 | Bull et al. | Sep 2009 | A1 |
| 20090221342 | Katz et al. | Sep 2009 | A1 |
| 20090227302 | Abe | Sep 2009 | A1 |
| 20090239666 | Hall et al. | Sep 2009 | A1 |
| 20090264190 | Davis et al. | Oct 2009 | A1 |
| 20090271287 | Halpern | Oct 2009 | A1 |
| 20090275410 | Kisenwether et al. | Nov 2009 | A1 |
| 20090275411 | Kisenwether et al. | Nov 2009 | A1 |
| 20090282469 | Lynch | Nov 2009 | A1 |
| 20090298468 | Hsu | Dec 2009 | A1 |
| 20100002897 | Keady | Jan 2010 | A1 |
| 20100004058 | Acres | Jan 2010 | A1 |
| 20100016069 | Herrmann | Jan 2010 | A1 |
| 20100056248 | Acres | Mar 2010 | A1 |
| 20100062833 | Mattice et al. | Mar 2010 | A1 |
| 20100062840 | Herrmann et al. | Mar 2010 | A1 |
| 20100079237 | Falk | Apr 2010 | A1 |
| 20100081501 | Carpenter et al. | Apr 2010 | A1 |
| 20100081509 | Burke | Apr 2010 | A1 |
| 20100099499 | Amaitis et al. | Apr 2010 | A1 |
| 20100106612 | Gupta | Apr 2010 | A1 |
| 20100120486 | DeWaal | May 2010 | A1 |
| 20100124967 | Lutnick et al. | May 2010 | A1 |
| 20100130276 | Fiden | May 2010 | A1 |
| 20100160035 | Herrmann | Jun 2010 | A1 |
| 20100160043 | Fujimoto et al. | Jun 2010 | A1 |
| 20100178977 | Kim et al. | Jul 2010 | A1 |
| 20100197383 | Rader et al. | Aug 2010 | A1 |
| 20100197385 | Aoki et al. | Aug 2010 | A1 |
| 20100203955 | Sylla | Aug 2010 | A1 |
| 20100203963 | Allen | Aug 2010 | A1 |
| 20100227662 | Speer et al. | Sep 2010 | A1 |
| 20100227670 | Arezine et al. | Sep 2010 | A1 |
| 20100227671 | Laaroussi | Sep 2010 | A1 |
| 20100227687 | Speer et al. | Sep 2010 | A1 |
| 20100234091 | Baerlocher et al. | Sep 2010 | A1 |
| 20100279764 | Allen | Nov 2010 | A1 |
| 20100323780 | Acres | Dec 2010 | A1 |
| 20100325703 | Etchegoyen | Dec 2010 | A1 |
| 20110009181 | Speer et al. | Jan 2011 | A1 |
| 20110039615 | Acres | Feb 2011 | A1 |
| 20110065492 | Acres | Mar 2011 | A1 |
| 20110105216 | Cohen | May 2011 | A1 |
| 20110111827 | Nicely et al. | May 2011 | A1 |
| 20110111843 | Nicely et al. | May 2011 | A1 |
| 20110111860 | Nguyen | May 2011 | A1 |
| 20110118010 | Brune | May 2011 | A1 |
| 20110159966 | Gura et al. | Jun 2011 | A1 |
| 20110183749 | Allen | Jul 2011 | A1 |
| 20110207525 | Allen | Aug 2011 | A1 |
| 20110212711 | Scott | Sep 2011 | A1 |
| 20110223993 | Allen et al. | Sep 2011 | A1 |
| 20110263318 | Agarwal et al. | Oct 2011 | A1 |
| 20110306400 | Nguyen | Dec 2011 | A1 |
| 20110306426 | Novak et al. | Dec 2011 | A1 |
| 20120015709 | Bennett et al. | Jan 2012 | A1 |
| 20120028703 | Anderson et al. | Feb 2012 | A1 |
| 20120028718 | Barclay | Feb 2012 | A1 |
| 20120034968 | Watkins et al. | Feb 2012 | A1 |
| 20120046110 | Amaitis | Feb 2012 | A1 |
| 20120094769 | Nguyen et al. | Apr 2012 | A1 |
| 20120108319 | Caputo et al. | May 2012 | A1 |
| 20120122561 | Hedrick | May 2012 | A1 |
| 20120122567 | Gangadharan et al. | May 2012 | A1 |
| 20120122584 | Nguyen | May 2012 | A1 |
| 20120122590 | Nguyen | May 2012 | A1 |
| 20120172130 | Acres | Jul 2012 | A1 |
| 20120184362 | Barclay et al. | Jul 2012 | A1 |
| 20120184363 | Barclay et al. | Jul 2012 | A1 |
| 20120190426 | Acres | Jul 2012 | A1 |
| 20120194448 | Rothkopf | Aug 2012 | A1 |
| 20120208618 | Frerking | Aug 2012 | A1 |
| 20120231885 | Speer, II | Sep 2012 | A1 |
| 20120239566 | Everett | Sep 2012 | A1 |
| 20120322563 | Nguyen et al. | Dec 2012 | A1 |
| 20120330740 | Pennington et al. | Dec 2012 | A1 |
| 20130005433 | Holch | Jan 2013 | A1 |
| 20130005453 | Nguyen et al. | Jan 2013 | A1 |
| 20130059650 | Sylla et al. | Mar 2013 | A1 |
| 20130065668 | LeMay | Mar 2013 | A1 |
| 20130103965 | Golembeski | Apr 2013 | A1 |
| 20130104193 | Gatto et al. | Apr 2013 | A1 |
| 20130132745 | Schoening et al. | May 2013 | A1 |
| 20130185559 | Morel | Jul 2013 | A1 |
| 20130196756 | Nguyen | Aug 2013 | A1 |
| 20130196776 | Nguyen | Aug 2013 | A1 |
| 20130210513 | Nguyen | Aug 2013 | A1 |
| 20130210514 | Nguyen | Aug 2013 | A1 |
| 20130210530 | Nguyen | Aug 2013 | A1 |
| 20130225279 | Patceg | Aug 2013 | A1 |
| 20130225282 | Williams et al. | Aug 2013 | A1 |
| 20130252730 | Joshi | Sep 2013 | A1 |
| 20130281188 | Guinn | Oct 2013 | A1 |
| 20130316808 | Nelson | Nov 2013 | A1 |
| 20140006129 | Heath | Jan 2014 | A1 |
| 20140057716 | Massing et al. | Feb 2014 | A1 |
| 20140087862 | Burke | Mar 2014 | A1 |
| 20140094295 | Nguyen | Apr 2014 | A1 |
| 20140094316 | Nguyen | Apr 2014 | A1 |
| 20140121005 | Nelson | May 2014 | A1 |
| 20140179431 | Nguyen | Jun 2014 | A1 |
| 20140274309 | Nguyen | Sep 2014 | A1 |
| 20140274319 | Nguyen | Sep 2014 | A1 |
| 20140274320 | Nguyen | Sep 2014 | A1 |
| 20140274342 | Nguyen | Sep 2014 | A1 |
| 20140274357 | Nguyen | Sep 2014 | A1 |
| 20140274360 | Nguyen | Sep 2014 | A1 |
| 20140274367 | Nguyen | Sep 2014 | A1 |
| 20140274388 | Nguyen | Sep 2014 | A1 |
| 20150089595 | Telles | Mar 2015 | A1 |
| 20150133223 | Carter | May 2015 | A1 |
| 20150143543 | Phegade | Aug 2015 | A1 |
| 20170206734 | Nguyen | Jul 2017 | A1 |
| 20170228979 | Nguyen | Aug 2017 | A1 |
| 20170243440 | Nguyen | Aug 2017 | A1 |
| 20170337770 | Nguyen | Nov 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 2033638 | May 1980 | GB |
| 2062923 | May 1981 | GB |
| 2096376 | Oct 1982 | GB |
| 2097570 | Nov 1982 | GB |
| 2335524 | Sep 1999 | GB |
| 12005000454 | May 2007 | PH |
| WO 05073933 | Aug 2005 | WO |
| WO 2008027621 | Mar 2008 | WO |
| WO 2009026309 | Feb 2009 | WO |
| WO 2009062148 | May 2009 | WO |
| WO 2010017252 | Feb 2010 | WO |
| Entry |
|---|
| Benston, Liz, “Harrahs Launches iPhone App; Caesars Bypasses Check-in,” Las Vegas Sun, Las Vegas, NV. Jan. 8, 2010. |
| Finnegan, Amanda, “Casinos Connecting with Customers via iPhone Apps”, May 27, 2010, Las Vegas Sun, Las Vegas, NV. |
| Gaming Today Staff, “Slots showcased at 2009 National Indian Gaming Assoc.”, GamingToday.com, Apr. 14, 2009. |
| Green, Marian, “Testing Texting Casino Journal”, Mar. 2, 2009. |
| Hasan, Ragib, et al., “A Survey of Peer-to-Peer Storage Techniques for Distributed File Systems”, National Center for Supercomputing Applications, Department of Computer Science, University of Illinois at Urbana Champaign, Jun. 27, 2005. |
| Jones, Trahern, “Telecon-equipped drones could revolutionize wireless market”, azcentral.com, http://www.azcentral.com/business/news/articles/20130424telecom-equipped-drones-could-revolutionize-wireless-market.html, downloaded Jul. 2, 2013, 2 pages. |
| Yancey, Kitty Bean, “Navigate Around Vegas with New iPhone Apps”, USA Today, Jun. 3, 2010. |
| iAPS, Daily Systems LLC, 2010. |
| U.S. Appl. No. 12/945,888, filed Nov. 14, 2010. |
| U.S. Appl. No. 12/945,889, filed Nov. 14, 2010. |
| U.S. Appl. No. 13/622,702, filed Sep. 19, 2012. |
| U.S. Appl. No. 13/800,917, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/296,182, filed Nov. 15, 2011. |
| U.S. Appl. No. 13/801,234, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/801,171, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/843,192, filed Mar. 15, 2013. |
| U.S. Appl. No. 13/843,087, filed Mar. 15, 2013. |
| U.S. Appl. No. 13/632,743, filed Oct. 1, 2012. |
| U.S. Appl. No. 13/632,828, filed Oct. 1, 2012. |
| U.S. Appl. No. 13/833,953, filed Mar. 15, 2013. |
| U.S. Appl. No. 12/619,672, filed Nov. 16, 2009. |
| U.S. Appl. No. 13/801,121, filed Mar. 13, 2013. |
| U.S. Appl. No. 12/581,115, filed Oct. 17, 2009. |
| U.S. Appl. No. 13/801,076, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/617,717, filed Nov. 12, 2009. |
| U.S. Appl. No. 13/633,118, filed Oct. 1, 2012. |
| U.S. Appl. No. 12/797,610, filed Jun. 10, 2010. |
| U.S. Appl. No. 13/801,256, filed Mar. 13, 2013. |
| U.S. Appl. No. 12/757,968, filed Apr. 9, 2010. |
| U.S. Appl. No. 12/797,616, filed Jun. 10, 2010. |
| U.S. Appl. No. 13/557,063, filed Jul. 24, 2012. |
| U.S. Appl. No. 13/833,116, filed Mar. 15, 2013. |
| U.S. Appl. No. 13/801,271, filed Mar. 13, 2011. |
| Office Action for U.S. Appl. No. 12/945,888 dated Apr. 10, 2012. |
| Final Office Action for U.S. Appl. No. 12/945,888 dated Sep. 21, 2012. |
| Advisory Action for U.S. Appl. No. 12/945,888 dated Jan. 30, 2013. |
| Office Action for U.S. Appl. No. 12/581,115 dated Dec. 20, 2011. |
| Final Office Action for U.S. Appl. No. 12/581,115 dated Sep. 13, 2012. |
| Notice of Allowance for U.S. Appl. No. 12/581,115 dated May 24, 2013. |
| Office Action for U.S. Appl. No. 12/619,672 dated Dec. 20, 2011. |
| Final Office Action for U.S. Appl. No. 12/619,672 dated Nov. 6, 2012. |
| Office Action for U.S. Appl. No. 12/619,672 dated Mar. 7, 2013. |
| Office Action for U.S. Appl. No. 12/617,717 dated Oct. 4, 2011. |
| Office Action for U.S. Appl. No. 12/617,717 dated Apr. 4, 2012. |
| Advisory Action for U.S. Appl. No. 12/617,717 dated Jun. 12, 2011. |
| Office Action for U.S. Appl. No. 12/617,717, dated Jun. 17, 2013. |
| Office Action for U.S. Appl. No. 12/797,610 dated Dec. 8, 2011. |
| Final Office Action for U.S. Appl. No. 12/797,610 dated Jun. 6, 2012. |
| Office Action for U.S. Appl. No. 12/797,610 dated Feb. 26, 2013. |
| Office Action for U.S. Appl. No. 12/757,968, dated May 9, 2012. |
| Final Office Action for U.S. Appl. No. 12/757,968, dated Nov. 29, 2012. |
| Office Action for U.S. Appl. No. 12/757,968, dated Apr. 25, 2013. |
| Office Action for U.S. Appl. No. 12/797,616 dated Mar. 15, 2012. |
| Final Office Action for U.S. Appl. No. 12/797,616 dated Oct. 13, 2012. |
| Office Action for U.S. Appl. No. 12/797,616 dated Feb. 13, 2013. |
| Final Office Action for U.S. Appl. No. 12/797,616 dated May 8, 2013. |
| Office Action for U.S. Appl. No. 13/296,182 dated Dec. 5, 2012. |
| Brochure, 5000 Ft. Inc., 1 page, Nov. 2010. |
| Frontier Fortune game, email notification, MGM Resorts Intl., Aug. 9, 2013. |
| “Getting Back in the Game: Geolocation Can Ensure Compliance with New iGaming Regulations”, White Paper, Quova, Inc., 2010. |
| Notice of Allowance of U.S. Appl. No. 12/619,672, dated Aug. 23, 2013. |
| Office Action for U.S. Appl. No. 13/633,118, dated Sep. 20, 2013. |
| Office Action for U.S. Appl. No. 13/801,256, dated Jul. 2, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/619,672, dated Oct. 3, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/757,968, dated Oct. 11, 2013. |
| Final Office Action for U.S. Appl. No. 12/797,610, dated Jul. 10, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/757,968, dated Dec. 18, 2013. |
| Office Action for U.S. Appl. No. 12/945,889, dated Dec. 18, 2013. |
| Office Action for U.S. Appl. No. 13/632,828, dated Jul. 30, 2013. |
| Restriction Requirement for U.S. Appl. No. 13/801,256, dated Dec. 30, 2013. |
| Office Action for U.S. Appl. No. 13/801,171, dated Dec. 26, 2013. |
| Office Action for U.S. Appl. No. 13/801,234, dated Jan. 10, 2014. |
| Final Office Action for U.S. Appl. No. 13/296,182, dated Feb. 12, 2014. |
| Office Action for U.S. Appl. No. 12/617,717, dated Feb. 25, 2014. |
| Office Action for U.S. Appl. No. 13/801,076, dated Mar. 28, 2014. |
| Final Office Action for U.S. Appl. No. 13/633,118, dated Apr. 3, 2014. |
| Office Action for U.S. Appl. No. 13/843,192, dated Apr. 3, 2014. |
| Office Action for U.S. Appl. No. 13/632,743, dated Apr. 10, 2014. |
| Office Action for U.S. Appl. No. 13/801,121, dated Apr. 11, 2014. |
| Final Office Action for U.S. Appl. No. 12/945,889, dated Jun. 30, 2014. |
| Notice of Allowance for U.S. Appl. No. 12/617,717, dated Jul. 14, 2014. |
| Office Action for U.S. Appl. No. 13/801,121, dated Sep. 24, 2014. |
| Office Action for U.S. Appl. No. 13/801,171, dated Sep. 22, 2014. |
| Office Action for U.S. Appl. No. 13/801,234, dated Oct. 1, 2014. |
| Office Action for U.S. Appl. No. 13/801,271, dated Oct. 31, 2014. |
| Final Office Action for U.S. Appl. No. 13/843,192, dated Oct. 21, 2014. |
| Office Action for U.S. Appl. No. 13/632,743, dated Oct. 23, 2014. |
| Office Action for U.S. Appl. No. 12/945,889, dated Oct. 23, 2014. |
| Office Action for U.S. Appl. No. 13/632,828, dated Nov. 7, 2014. |
| Office Action for U.S. Appl. No. 12/797,610, dated Dec. 15, 2014. |
| Final Office Action for U.S. Appl. No. 12/945,889, dated Feb. 12, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,171, dated Mar. 16, 2015. |
| Office Action for U.S. Appl. No. 13/833,116, dated Mar. 27, 2015. |
| Office Action for U.S. Appl. No. 13/632,828, dated Apr. 10, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,121, dated Apr. 21, 2015. |
| Final Office Action for U.S. Appl. No. 13/557,063, dated Apr. 28, 2015. |
| Office Action for U.S. Appl. No. 13/296,182, dated Jun. 5, 2015. |
| Office Action for U.S. Appl. No. 13/843,192, dated Jun. 19, 2015. |
| Office Action for U.S. Appl. No. 12/797,610, dated Jul. 14, 2015. |
| Final Office Action for U.S. Appl. No. 13/833,953, dated Jul. 17, 2015. |
| Notice of Allowance for U.S. Appl. No. 12/945,889, dated Jul. 22, 2015. |
| Office Action for U.S. Appl. No. 12/797,616, dated Aug. 10, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,234, dated Aug. 14, 2015. |
| Final Office Action for U.S. Appl. No. 13/833,116, dated Sep. 24, 2015. |
| Office Action for U.S. Appl. No. 13/801,121, dated Oct. 2, 2015. |
| Office Action for U.S. Appl. No. 14/017,150, dated Oct. 7, 2015. |
| Office Action for U.S. Appl. No. 14/017,159, dated Oct. 7, 2015. |
| Office Action for U.S. Appl. No. 13/801,271 dated Oct. 19, 2015. |
| Office Action for U.S. Appl. No. 14/211,536 dated Oct. 19, 2015. |
| Final Office Action for U.S. Appl. No. 13/632,828, dated Oct. 22, 2015. |
| Office Action for U.S. Appl. No. 14/217,066, dated Dec. 17, 2015. |
| Notice of Allowance for U.S. Appl. No. 13/557,063, dated Dec. 23, 2015. |
| Office Action for U.S. Appl. No. 13/296,182, dated Dec. 23, 2015. |
| Final Office Action for U.S. Appl. No. 13/843,192, dated Dec. 30, 2015. |
| Office Action for U.S. Appl. No. 13/801,076, dated Jan. 11, 2016. |
| Office Action for U.S. Appl. No. 12/945,888, dated Jan. 22, 2016. |
| Final Office Action for U.S. Appl. No. 12/797,616, dated Jun. 12, 2016. |
| Office Action for U.S. Appl. No. 13/843,087, dated Feb. 25, 2016. |
| Office Action for U.S. Appl. No. 13/800,917, dated Feb. 25, 2016. |
| Advisory Action for U.S. Appl. No. 13/632,828, dated Feb. 25, 2016. |
| Office Action for U.S. Appl. No. 13/801,234, dated Mar. 8, 2016. |
| Office Action for U.S. Appl. No. 14/216,986, dated Mar. 9, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,271, dated Mar. 11, 2016. |
| Office Action for U.S. Appl. No. 13/622,702, dated Mar. 22, 2016. |
| Final Office Action for U.S. Appl. No. 13/633,118, dated Mar. 24, 2016. |
| Final Office Action for U.S. Appl. No. 14/189,948, dated Apr. 6, 2016. |
| Final Office Action for U.S. Appl. No. 12/797,610, dated Apr. 21, 2016. |
| Final Office Action for U.S. Appl. No. 14/017,150, dated Apr. 26, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,121, dated May 11, 2016. |
| Final Office Action for U.S. Appl. No. 14/017,159, dated Jun. 6, 2016. |
| Office Action for U.S. Appl. No. 13/801,171, dated Jun. 6, 2016. |
| Office Action for U.S. Appl. No. 13/843,192, dated Jun. 9, 2016. |
| Final OA for U.S. Appl. No. 12/945,888, dated Jun. 28, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/833,953, dated Jul. 6, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,171, dated May 21, 2014. |
| Final Office Action for U.S. Appl. No. 13/801,234, dated May 22, 2014. |
| Office Action for U.S. Appl. No. 14/211,536, dated Jul. 13, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/801,076, dated Jul. 11, 2016. |
| Office Action for U.S. Appl. No. 13/296,182, dated Jul. 20, 2016. |
| Restriction Requirement for U.S. Appl. No. 13/296,182, dated Oct. 12, 2012. |
| Advisory Action for U.S. Appl. No. 13/296,182, dated May 8, 2014. |
| Advisory Action for U.S. Appl. No. 13/843,192, dated May 8, 2014. |
| Notice of Allowance for U.S. Appl. No. 13/843,192, dated Aug. 10, 2016. |
| Office Action for U.S. Appl. No. 14/217,066, dated Dec. 22, 2016. |
| Final Office Action for U.S. Appl. No. 14/216,986, dated Sep. 23, 2016. |
| Office Action for U.S. Appl. No. 14/017,159, dated Sep. 23, 2016. |
| Office Action for U.S. Appl. No. 13/632,743, dated Sep. 23, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,234, dated Oct. 14, 2016. |
| Final Office Action for U.S. Appl. No. 13/843,087, dated Oct. 13, 2016. |
| Final Office Action for U.S. Appl. No. 13/622,702, dated Oct. 13, 2016. |
| Office Action for U.S. Appl. No. 14/189,948, dated Nov. 7, 2016. |
| Final Office Action for U.S. Appl. No. 14/211,536, dated Mar. 14, 2014. |
| Notice of Allowance for U.S. Appl. No. 13/833,116, dated Oct. 11, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/801,271, dated Dec. 2, 2016. |
| Notice of Allowance for U.S. Appl. No. 12/797,610, dated Dec. 7, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/632,828, dated Dec. 16, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 19, 2016. |
| Notice of Allowance for U.S. Appl. No. 14/211,536, dated Dec. 28, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/801,256, dated Jan. 20, 2017. |
| Office Action for U.S. Appl. No. 13/800,917, dated Feb. 3, 2017. |
| Final Office Action for U.S. Appl. No. 12/797,616, dated Feb. 10, 2017. |
| Office Action for U.S. Appl. No. 12/945,888, dated Feb. 28, 2017. |
| Final Office Action for U.S. Appl. No. 14/189,948, dated Mar. 17, 2017. |
| Office Action for U.S. Appl. No. 15/400,840, dated Mar. 10, 2017. |
| Notice of Allowance for U.S. Appl. No. 13/801,121, dated Mar. 29, 2017. |
| Office Action for U.S. Appl. No. 15/270,333, dated Mar. 30, 2017. |
| Office Action for U.S. Appl. No. 15/402,945, dated Apr. 5, 2017. |
| Office Action for U.S. Appl. No. 15/271,488, dated Apr. 19, 2017. |
| Final Office Action for U.S. Appl. No. 14/217,066, dated Apr. 21, 2017. |
| Office Action for U.S. Appl. No. 14/216,986 dated Apr. 26, 2017. |
| Office Action for U.S. Appl. No. 13/801,171, dated Jun. 14, 2017. |
| Office Action for U.S. Appl. No. 14/017,159, dated Jun. 29, 2017. |
| Notice of Allowance for U.S. Appl. No. 15/270,333, dated Jul. 5, 2017. |
| Final Office Action for U.S. Appl. No. 13/800,917, dated Jul. 13, 2017. |
| Notice of Allowance for U.S. Appl. No. 13/801,234, dated Jul. 5, 2017. |
| Notice of Allowance for U.S. Appl. No. 14/217,066, dated Jul. 14, 2017. |
| Final Office Action for U.S. Appl. No. 14/518,909, dated Jul. 19, 2017. |
| Final Office Action for U.S. Appl. No. 13/801,121, dated Sep. 15, 2016. |
| Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 17, 2015. |
| Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 19, 2016. |
| Notice of Allowance for U.S. Appl. No. 15/293,751, dated Aug. 4, 2017. |
| Advisory Action for U.S. Appl. No. 14/189,948, dated Jul. 28, 2017. |
| Final OA for U.S. Appl. No. 13/801,256, dated Aug. 15, 2014. |
| Final OA for U.S. Appl. No. 13/801,256, dated Feb. 18, 2015. |
| Advisory Action for U.S. Appl. No. 13/801,256, dated Dec. 5, 2014. |
| Office Action for U.S. Appl. No. 13/801,256, dated Jan. 12, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,256, dated Aug. 16, 2016. |
| Office Action for U.S. Appl. No. 13/801,256, dated Aug. 18, 2017. |
| Office Action for U.S. Appl. No. 13/622,702, dated Aug. 31, 2017. |
| Office Action for U.S. Appl. No. 12/945,888, dated Sep. 1, 2017. |
| Office Action for U.S. Appl. No. 14/017,150, dated Sep. 7, 2017. |
| Notice of Allowance for U.S. Appl. No. 14/189,948, dated Sep. 13, 2017. |
| Office Action for U.S. Appl. No. 15/138,086, dated Oct. 19, 2017. |
| Notice of Allowance for U.S. Appl. No. 15/402,945 dated Nov. 21, 2017. |
| Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 13, 2017. |
| Final Office Action for U.S. Appl. No. 15/271,488, dated Dec. 21, 2017. |
| Office Action for U.S. Appl. No. 15/671,133, dated Dec. 22, 2017. |
| Final Office Action for U.S. Appl. No. 14/216,986, dated Dec. 26, 2017. |
| Restriction Requirement for U.S. Appl. No. 15/427,307, dated Jan. 17, 2018. |
| Office Action for U.S. Appl. No. 15/798,363, dated Jan. 26, 2018. |
| Office Action for U.S. Appl. No. 15/427,291, dated Jan. 29, 2018. |
| Final Office Action for U.S. Appl. No. 14/017,159, dated Feb. 1, 2018. |
| Number | Date | Country | |
|---|---|---|---|
| 20170116823 A1 | Apr 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61413477 | Nov 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13843087 | Mar 2013 | US |
| Child | 15402945 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13296182 | Nov 2011 | US |
| Child | 13843087 | US |
