Patent Grant
9251645
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. Copyright 2013, WMS Gaming, Inc.
Embodiments of the inventive subject matter relate generally to wagering game systems and networks that, more particularly, integrate chat and wagering games.
Wagering game machines, such as slot machines, video poker machines and the like, have been a cornerstone of the gaming industry for several years. Traditionally, wagering game machines have been confined to physical buildings, like casinos (e.g., resort casinos, road-side casinos, etc.). The casinos are located in specific geographic locations that are authorized to present wagering games to casino patrons. However, with the proliferation of interest and use of the Internet, shrewd wagering game manufacturers have recognized that a global public network, such as the Internet, can reach to various locations of the world that have been authorized to present wagering games. Any individual with a personal computing device (e.g., a personal computer, a laptop, a personal digital assistant, a cell phone, etc.) can connect to the Internet and play wagering games. Consequently, some wagering game manufacturers have created wagering games that can be processed by personal computing devices and offered via online casino websites (“online casinos”). However, online casinos face challenges and struggles. For instance, online casinos have struggled to provide the excitement and entertainment that a real-world casino environment provides. Some online casinos have struggled enforcing cross jurisdictional restrictions and requirements. Further, some online casinos have struggled adapting the online gaming industry to a traditionally non-wagering game business environment. As a result, wagering game manufacturers, casino operators, and online game providers are constantly in need of innovative concepts that can make the online gaming industry appealing and profitable.
Embodiments are illustrated in the Figures of the accompanying drawings in which:
This description of the embodiments is divided into five sections. The first section provides an introduction to embodiments. The second section describes example operating environments while the third section describes example operations performed by some embodiments. The fourth section describes additional example operating environments while the fifth section presents some general comments.
This section provides an introduction to some embodiments.
Social communication is on the rise. Internet users are enjoying a proliferation of social networking mechanisms (e.g., social network websites, online chats, blogging, social network applications, etc.) that are appearing online in vast quantities. Many of those Internet users are also wagering game enthusiasts. Many wagering game enthusiasts are demanding greater access to wagering games and content related to wagering games, especially content that includes social networking. Some wagering game companies have created online wagering game websites that provide a way for wagering game enthusiasts to play wagering games while connected to the Internet (e.g., via a web-browser). Some online wagering game websites provide various features, such as social network functionality. Social networks allow wagering game players (“players”) to create user accounts with one or more unique identifiers that represent an online persona. One example of a unique identifier is an “avatar.” Avatars are graphical, “cartoon-like” depictions of a social network persona. These online personas and associated avatars add to the fun of belonging to a social network. Many online casinos and other gaming venues, however, are constantly looking for new ways to generate innovative online, and other networked, gaming experiences.
Some embodiments of the inventive subject matter, for example, present examples of integrating chat functionality and wagering games in network gaming venues (e.g., online casinos, wagering game websites, wagering networks, etc.). Embodiments can be presented over any type of communications network (e.g., public or private) that provides access to wagering games, such as a website (e.g., via wide-area-networks, or WANs), a private gaming network (e.g., local-area-networks, or LANs), a file sharing network, a social networking network, etc., or any combination of networks. Multiple users can be connected to the networks via computing devices. The multiple users can have accounts that subscribe to specific services, such as account-based wagering systems (e.g., account-based wagering game websites, account-based casino networks, etc.).
In some embodiments herein a user may be referred to as a player (i.e., of wagering games), and a player may be referred to interchangeably as a player account. Account-based wagering systems utilize player accounts when transacting and performing activities, at the computer level, that are initiated by players. Therefore, a “player account” represents the player at a computerized level. The player account can perform actions via computerized instructions. For example, in some embodiments, a player account may be referred to as performing an action, controlling an item, communicating information, etc. Although a player, or person, may be activating a game control or device to perform the action, control the item, communicate the information, etc., the player account, at the computer level, can be associated with the player, and therefore any actions associated with the player can also be associated with the player account. Therefore, for brevity, to avoid having to describe the interconnection between player and player account in every instance, a “player account” may be referred to herein in either context. Further, in some embodiments herein, the word “gaming” is used interchangeably with “gambling.”
The client device 137 presents a graphical user interface (“GUI”) 101 for a network wagering venue. In some embodiments, the network wagering venue is a casino network venue that presents games via wagering game machines. Thus, in some embodiments, the client device 137 can be a wagering game machine, such as the kind used in casinos, which a player can use to login via a private casino network to the player account hosted by the account server 170. In other embodiments, however, the network wagering venue can be an online casino website, or another type of wagering related website. Therefore, in some embodiments, the client device 137 can be a personal computer, a cell phone, or another personal computing device that a player uses to login via the Internet to a player account hosted by the account server 170.
A player can use the client device 137 to log on to a player account stored on the account server 170. The wagering game server 150 can communicate with the account server 170 and determine that the player account has logged in, and present, within the GUI 101, a wagering game interface 103 where the player can play wagering games. The wagering game interface 103, for example, can present playing elements of wagering games (e.g., animated slot reels 107), controls for playing and betting (e.g., a betting meter 132, a spin button 133, etc.), and features for tracking player account information (e.g., a credit meter).
The wagering game server 150 and the chat server 180 can work together to present a chat console 106 within the GUI 101. The chat console 106 integrates with the wagering game server 150 and the chat server 180 to present, in the chat console 106, news items that occur on the network wagering venue, such as wagering game events that occur on the wagering game server 150. For example, the wagering game server 150 can present occurrences of various game events (e.g., wins, jackpot values, etc.).
The chat console 106 can include a chat contact interface 108 (i.e., Chat Buddies). The chat contact interface 108 can include a first bot identifier (“bot identifier”) 147 for a moderator bot 104 that represents the network wagering venue. The moderator bot 104 can communicate, via the chat console 106, as if it were a social contact (e.g., a chat buddy) of the player account logged in to the gambling venue. The moderator bot 104 can present news about events that occur on wagering games, such as wins, and other wagering game events. The moderator bot 104 is an example of one kind of bot. Other embodiments may use other bots that represent specific games or game features available through the gambling venue. For example, the chat contact interface 108 can include a second bot identifier (“bot identifier”) 143 for a game bot 149 that represents a wagering game called “Zeus.” Further, bots can present secondary services information via the chat console 106 in addition to, or in place of, wagering game events. Examples of secondary services may include game notifications, help information, advertisements, game replays, etc. Further, in some embodiments, the player account can communicate with game bots to play wagering games via the chat console 106 using textual commands typed into the chat console 106. In other embodiments, players can modify how the news is presented, both directly and indirectly. For instance, the system 100 can determine player settings that filter, arrange, or modify the presentation of news events via the chat console 106. In other embodiments, however, the system 100 can analyze player factors, such as player history, betting patterns, etc., and automatically modify the presentation of news events via the chat console 106. In some embodiments, the system 100 can also present options to follow users and aggregate chat messages, and other activity performed by the followed users, into the chat console 106. The system 100 can include a community feed control 118 and a following menu control 120. The community feed control 118, when activated, can show the community feed (i.e., the integrated chat and news feed) in the chat console 106 depicted in
Although
This section describes example operating environments and networks and presents structural aspects of some embodiments. More specifically, this section includes discussion about wagering game system architectures.
The wagering game system architecture 200 can also include a wagering game server 250 configured to control wagering game content, provide random numbers, and communicate wagering game information, account information, and other information to and from the client 260. The wagering game server 250 can include a content controller 251 configured to manage and control content for the presentation of content on the client 260. For example, the content controller 251 can generate game results (e.g., win/loss values), including win amounts, for games played on the client 260. The content controller 251 can communicate the game results to the client 260. The content controller 251 can also generate random numbers and provide them to the client 260 so that the client 260 can generate game results. The wagering game server 250 can also include a content store 252 configured to contain content to present on the client 260. The wagering game server 250 can also include an account manager 253 configured to control information related to player accounts. For example, the account manager 253 can communicate wager amounts, game results amounts (e.g., win amounts), bonus game amounts, etc., to the account server 270. The wagering game server 250 can also include a communication unit 254 configured to communicate information to the client 260 and to communicate with other systems, devices and networks. The wagering game server 250 can also include a chat controller 255 configured to present and control chat bots that emulate social contacts via chat. The chat controller 255 can also be configured to receive chat text commands and control wagering games using the chat text commands. The chat controller 255 can also present and control following functionality for selected chat social-contacts associated with a player account. The wagering game server 250 can also include a news provider 256 configured to control presentation of wagering game news events via gaming chat consoles. The news provider 256 can also be configured to automatically adjust presentation requirements for news events based on quantifiable player factors.
The wagering game system architecture 200 can also include the client 260 configured to present wagering games and receive and transmit information to integrate chat and wagering games. The client 260 can be a computer system, a personal digital assistant (PDA), a cell phone, a laptop, a wagering game machine, or any other device or machine that is capable of processing information, instructions, or other data provided via a communications network 222. The client 260 can include a content controller 261 configured to manage and control content and presentation of content on the client 260. The client 260 can also include a content store 262 configured to contain content to present on the client 260. The client 260 can also include a gaming chat module 263 configured to control wagering games and chat on the client 260.
Each component shown in the wagering game system architecture 200 is shown as a separate and distinct element connected via the communications network 222. However, some functions performed by one component could be performed by other components. For example, the wagering game server 250 can also be configured to perform functions of the gaming chat module 263, and other network elements and/or system devices. Furthermore, the components shown may all be contained in one device, but some, or all, may be included in, or performed by multiple devices, as in the configurations shown in
As mentioned previously, in some embodiments, the client 260 can take the form of a wagering game machine. Examples of wagering game machines can include floor standing models, handheld mobile units, bar-top models, workstation-type console models, surface computing machines, etc. Further, wagering game machines can be primarily dedicated for use in conducting wagering games, or can include non-dedicated devices, such as mobile phones, personal digital assistants, personal computers, etc.
In some embodiments, clients and wagering game servers work together such that clients can be operated as thin, thick, or intermediate clients. For example, one or more elements of game play may be controlled by the client or the wagering game servers (server). Game play elements can include executable game code, lookup tables, configuration files, game outcome, audio or visual representations of the game, game assets, or the like. In a thin-client example, the wagering game server can perform functions such as determining game outcome or managing assets, while the clients can present a graphical representation of such outcome or asset modification to the user (e.g., player). In a thick-client example, the clients can determine game outcomes and communicate the outcomes to the wagering game server for recording or managing a player's account.
In some embodiments, either the client or the wagering game server(s) can provide functionality that is not directly related to game play. For example, account transactions and account rules may be managed centrally (e.g., by the wagering game server(s)) or locally (e.g., by the client). Other functionality not directly related to game play may include power management, presentation of advertising, software or firmware updates, system quality or security checks, etc.
Furthermore, the wagering game system architecture 200 can be implemented as software, hardware, any combination thereof, or other forms of embodiments not listed. For example, any of the network components (e.g., the wagering game machines, servers, etc.) can include hardware and machine-readable media including instructions for performing the operations described herein. Machine-readable media includes any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine (e.g., a wagering game machine, computer, etc.). For example, tangible machine-readable media includes read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory machines, etc. Machine-readable media also includes any media suitable for transmitting software over a network.
This section describes operations associated with some embodiments. In the discussion below, some flow diagrams are described with reference to block diagrams presented herein. However, in some embodiments, the operations can be performed by logic not described in the block diagrams.
In certain embodiments, the operations can be performed by executing instructions residing on machine-readable media (e.g., software), while in other embodiments, the operations can be performed by hardware and/or other logic (e.g., firmware). In some embodiments, the operations can be performed in series, while in other embodiments, one or more of the operations can be performed in parallel. Moreover, some embodiments can perform more or less than all the operations shown in any flow diagram.
The flow 300 continues at processing block 304, where the system determines wagering game news events to present via a gaming chat console for the chat session. In some embodiments, the news events are related to wagering games or, in other words, wagering game news events.
The chat contact interface 108 (i.e., the “Chat Buddies” panel) also presents social contact identifiers 141, such as avatar images, animations, photographs, etc., that represent chat social contacts 145 (e.g., Anne S. or “YumYum” and John B. or “JumpNBump”) that the player has invited, or accepted invitations, to include in the chat contact interface 108. The system 100 may include options for the player to invite the moderator bot 104 to be in the chat contact interface 108. In some embodiments, however, the system 100 can invite the moderator bot 104 by default to be a chat contact. The system 100 can present the moderator bot 104 in the chat contact interface 108 using the bot identifier 147 (i.e., a name, such as “Jackpot Party Moderator,” and an avatar that resembles a money graphic). In some embodiments, the player can invite other bots to be social contacts, such as the game bot 149. The system 100 can present the game bot 149 in the chat contact interface 108 using the bot identifier 143 (i.e., a name “Zeus Game” and an avatar that resembles a lightning bolt graphic, which represents a Zeus character for the Zeus game assigned to the game bot 149). The game bot 149 can also present news events and communicate with the player account via the chat console 106.
The system 100 can insert chat comments from the moderator bot 104 and the game bot 149 in stream with other chat comments by the chat social contacts 145 and/or other chat participants that are participating in chat activity via the chat console 106. The system 100 can present news related to casino-sponsored game events in a mixed delivery mode of both push and pull communications. For example, the system 100 can push game news events (e.g., the news event 125) into the chat console 106 while at the same time the chat console 106 can pull news events from other sources (e.g., other game bots, other news sources, etc.). The system 100 can present news via internal Really Simple Syndication (RSS) news feeders, XML MIME Transformation Protocol (XMTP), or other methods. In some embodiments, the system 100 can embed content in news messages. For example, the system 100 can embed a menu link into the news event 125. When a player activates the menu link, the link can bring up a menu that allows the player to replay the gaming event. The system 100 can also embed content into links for other news events that can perform other activities, such as launch a wagering game in the wagering game interface, present a profile, present past big wins, etc. Further, in some embodiments, the system 100 can present news from automated sources, such as chat bots, or from user accounts, such as from a hired moderator's user account.
The flow 300 continues at processing block 306, where the system automatically adjusts presentation requirements for the news events based on quantifiable player factors. The quantifiable player factors can be based on a group of players or on an individual player. The system can automatically adjust the presentation requirements for a group or collection of player accounts, for individual player accounts, or for both group player accounts and individual player accounts. The system can intelligently determine which news to send out based on any one or more of (though are not limited to), the following factors: player interests, player game play history, player playing schedules (e.g., times of day that players play), player locations, player personal schedules, numbers of players playing, etc. The system can refer to pre-set news-delivery threshold requirements (“news thresholds”) for what constitutes an automated chat item (e.g., a win must be above a certain dollar amount threshold). The system compares the quantifiable player factors to the news thresholds to determine whether the quantifiable player factors meet, or comply with, the news thresholds.
For instance, in some embodiments, the system monitors site user activity for a wagering game website. When the wagering website slows in user activity (e.g., not as many players playing), the system can dynamically modify a “win event” dollar amount threshold, for one or more games, to have a lower value so that more win amounts are delivered as news items. On the other hand, if the wagering website is busy, the system can modify the “win event” dollar amount threshold to have a higher value, so fewer, but higher, win amounts are delivered as news items. In another example, in some embodiments, the system monitors player betting activity on the wagering game website and modifies presentation requirements based on the betting activity. For example, a news threshold can be based on an average bet for a group of players for some portion of the wagering venue (e.g., all players on the casino website, all players in a room, etc.). If the betting activity for the portion of the wagering venue is slow, for instance, the system can modify a news threshold dollar amount, for that portion of the wagering venue, to a low news threshold value (e.g., 15× the average bet). In busy times, however, the system can set the news threshold dollar amount to a high news threshold value (e.g., 25× the average bet). Instead of, or in addition to, an average bet for a portion of the wagering venue, the system can determine an average bet, coin in, or other betting activity for an individual player. For instance, if a player bets at higher bets (e.g., 30× average bet on site), then the system can automatically increase the threshold dollar amount to only show higher win news items (e.g., so that higher betting individuals only see activity of other higher betting individuals).
The quantifiable player factors, therefore, in some embodiments, are player-related statistical values (e.g., betting statistics, logon statistics, etc.) for one or more player accounts logged on to a wagering game network. The system monitors and determines the pre-set news threshold values, determines the player-related statistical values for the one or more player accounts and dynamically adjusts the pre-set news threshold values to a modified news threshold value based on the player-related statistical values.
In another embodiment, the system can compare an event value associated with a gaming event to the modified news threshold value, determine that the event value complies with the modified news threshold value and present the news message via a chat console because the event value complies with the modified news threshold value. The event, for example, can be any gaming related event that occurs, such as a win occurring on a wagering game, a progressive jackpot hitting a given level, a slot reel combination occurrence, a card combination occurrence, a chip lead change, etc. The event value is the value (numerical, relational, combination, etc.) associated with the event. Thus, examples of event values can be a win amount associated with the win, a progressive jackpot value that hits the given level, a pay-table identifier associated with the slot reel combination, a quantified description of the card combination, an indicator of the chip lead change, etc.
The system can present the news message to all user accounts logged on to a wagering game website, or only to user accounts that meet pre-determined presentation requirements. For example, the system can determine that a first player account is assigned the pre-set news threshold value. For instance, the system can determine that a player logs on during a given time period (e.g., during a busy time period on a network wagering venue). For that given time period, the system assigns the player account a pre-set news threshold value of $500 for any win, meaning that any win, from any player on the network wagering venue, that is $500 or more, during that given time period, will invoke a news event in the player's chat console. The first player account's playing activity generates a first player-related statistical value, for example, a bet average of over $1 per bet, which complies with a default betting average of $1 or more set by the system. A second player account, which also logs on during the given time period, can also be assigned the pre-set news threshold value of $500. However, the second player account's playing activity generates a second player-related statistical value, for example, a bet average of over $5 per bet. The system, however, can have a pre-set threshold modification value (“threshold modifier”) that is related to average bet activity that indicates that if any player's average bet exceeds $5 per bet, then the system will automatically modify the pre-set news threshold value. In this particular example, therefore, the second player's average bet is over $5 per bet and the system can modify the pre-set news threshold value, for the second player account, to be a modified news threshold value. For instance, the system can modify the default $500 news threshold value for the second player account to be higher, such as $1000. As a result, the system would only notify the second player account, via the chat console, if a player on the network wagering venue had a win of $1000 or more. At the same time, however, the system can still present news events, for the first player account, at the original news threshold value of $500 or more. Therefore, an event win value of $640 would comply with the default pre-set news threshold value for the first player account but not with the modified news threshold value for the second player account. The system can thus present the news message of the $640 win to the first player account, via an instance of the gaming chat console associated with the first player account, but at the same time suppress, or refrain from presenting, the news message of the $640 win to the second player account.
In another embodiment, the system can determine that the first player's activity merits the assignment of a second modified threshold value for the first player account. The second modified threshold value, for the first player account, may have an opposite impact of the first modified threshold value for the second player account. In other words, the first player account may have a betting average of only $0.50, which does not meet the default betting average of $1 or more set by the system. The system can have a second pre-determined news modification value that lowers the pre-set news threshold value for players whose bet averages are less than $1. As a result, the system can assign the additional modified threshold value to the first player, which lowers the news threshold value to be less than $500, perhaps $100. As a result, the first player account will receive news messages for wins over $100 where the second player account receives news messages for wins over $1000.
In some embodiments, a casino operator can configure the system to automatically adjust presentation requirements for news events. For example, in
The news threshold modifier settings 430, on the other hand, include controls that specify conditions that, when met, modify the requirements specified in the news threshold requirement settings 404. The news threshold modifier settings 430 can include, for example, a site activity factor control 432 that indicates that site activity is a factor for which news threshold values can be modified. The news threshold modifier settings 430 can include a site activity metric control 434 for setting a statistical measurement value, or metric, to which a player's statistics can be measured, or compared. For example, as described further above, a player's activity, as measured by player statistical values, can affect the news thresholds so that the system 400 can customize required news events thresholds for individual players and/or groups of players. One of the factors can be site activity. Thus, for example, if a site login activity increases or decreases by a first amount (e.g., 5% variance indicated in the site activity metric control 434), then the system 400 can modify one or more of the news threshold requirement settings 404 by a second amount (e.g., increase or decrease by 10% indicated in a first news threshold modifier control 444). Some of the news threshold modifier settings 430 can be related to groups of player accounts whereas others can be related to individual player accounts. For example, a group bet-average factor control 433 can specify that the system 400 will monitor group bet averages for a gaming venue website as a factor that can modify news threshold requirements. If the group bet average increases or decreases by a first amount (e.g., 20% variance indicated in the group bet-average metric control 436), then the system 400 can modify one or more of the news threshold requirement settings 404 by a second amount (e.g., increase or decrease by 4% indicated in a second news threshold modifier control 442). In another example, however, an individual bet-average factor control 438 can specify that the system 400 will monitor individual player account bet averages for a gaming venue website as a factor that can modify news threshold requirements. If an individual player account's bet average increases or decreases by a first amount (e.g., 1% variance indicated in the individual bet-average metric control 439), then the system 400 can modify one or more of the news threshold requirement settings 404, for the individual player account, by a second amount (e.g., increase or decrease by 1% indicated in a third news threshold modifier control 449). As an example, for every $1 that a player account's average bet value increases, the system 400 can increase news presentation requirements by $50, which suppresses more messages in the player's chat console. In another example, however, the player account may desire to receive more messages. In such an example, the system 400 can decrease news presentation requirements by $50. The system 400 can look at player preferences stored in the player account to determine whether the player desires to have the news presentation requirements increased or decreased.
Returning to
Some examples of player account presentation criteria may include filters and toggles. The filters can filter the delivery of content based on content type. The news items can have tags describing the content types. The player preferences indicate the types and the system filters based on the types. In some embodiments, the filters can push news messages out to different mediums (e.g., to chat, to email, to social network sites), etc. Toggles, for example, can hide new messages (e.g., hide and show, hide based on type, etc.). In
Other examples of player account presentation criteria may include settings that relate to a rate of delivery for news messages. For instance, a player account can specify a rate of deliver (e.g., fast, slow, periodically, etc.) or alters requirements for content delivery, based on player preference (e.g., player thresholds that set a delivery speed for the news events). The system can also include controls for presentation display configurations, such as split screens, indentations, columns, text, highlighting, and other visual configurations that alter the way the news messages look.
In some embodiments, the player account presentation criteria can be statistical values representing a player account's wagering activity. The statistical values can be related to a betting amount for a player, a betting average for a player, an amount of player status points, a degree of player activity, a degree of player chat participation, or any other activity that a player can perform on a network wagering venue. In some embodiments, the system can generate marketing messages within a chat console. For example, the system can present advertisements or offers that offer discounts on games based on player history or preference. The system can determine overall coin-in for a player account and can determine an amount of coin-in that the player account is below average. The system can offer sponsored games to the player account to encourage additional coin-in. The system can push out news items that are sponsored by a company. In some embodiments, the system can produce news messages with effects that distinguish them as sponsored news messages (e.g., highlighting, different colors, specific animations, fonts that match a sponsors branding, etc.).
The flow 300 continues at processing block 308, where the system receives textual chat game commands communicated to an interactive game bot and controls a wagering game via the textual chat game commands. For example, in
In some embodiments, the system 100 can present functionality for players to play head-to-head against each other. For example, a player can challenge other players to compete in a crossword game. Certain words or phrases in the crossword game can yield different monetary amounts or multipliers. In some embodiments, an opponent can start filling out a word or phrase out and the player can steal it.
The flow 300 continues at processing block 310, where the system follows chat activity for the selected chat social-contacts associated with the player account. For example in
The followers menu 540 can be divided into two major sections including a following section 521 and a followers section 523. The following section 521 can be a list, or group, of social contact accounts that the player account is following, or in other words, for which the player account desires to view chat messages and other electronic social communications. In some embodiments, the social contact accounts being followed may be spread across different chat rooms on the network wagering venue. However, the player account that is following the social contact accounts can see the social contacts' chat messages (e.g., the contacts' sides of chat conversations) no matter what chat room the social contact accounts are logged into at the time. The chat messages from the followed social contact accounts can feed into a chat console (e.g., a chat client window) that the player account is using at the time that the followed social contact accounts transmit their chat messages.
The followers section 523 can be a list of social contacts that are following the player account. The social contact can also have wagering game player accounts that are linked to the player account (e.g., are linked to the Marcus Miller/“Ace” player account). The system 500, thus, can also present an instance of the chat console 506 to the social contact. The instances of the chat console 506 presented to the social contacts, however, would list names that the social contacts selected to follow or that were following the social contacts.
In one embodiment, the system 500 assigned the social contact links 525 and 527 to the following section 521 when the player account (e.g., the Marcus Miller/“Ace” player account) selected social contact representations (e.g., buddy names) from a chat contact interface 508 (e.g., a buddy list). The social contact links 529, 532, and 534 can appear in the followers section 523 when the player account (e.g., the Marcus Miller/“Ace” account) is selected by other player accounts. One social contact link 527 (i.e., for the social contact account “WhoDidWhatWhere”), in the following section 521, can include an interactive dropdown menu 536 that appears when a player selects (e.g., mouse over+clicks) the social contact link 527. The interactive dropdown menu 536 can include various options that the player can apply to the social contact account that the player account is following. Another social contact link 534 (i.e., for the social contact account “SillyRabbit”), in the followers section 523, can include an interactive dropdown menu 539 that appears when a player selects the social contact link 534. The interactive dropdown menu 539 can include various options that the player can apply to the social contact account that is following the player account. Some examples of options that can appear specifically in the interactive dropdown menu 536 in the following section 521 can include options to: (1) stop following, (2) see all chat for the social contact, (3) see all chat in context (i.e., show the chat messages from other users in a room that the social contact is chatting in), and (4) challenge to compete in a head-to-head game (e.g., could include a feature to pay in a certain amount to compete with the social contact), etc. Some examples of options that can appear specifically in the interactive dropdown menu 539 in the followers section 523 can include options to: (1) follow the follower as well, (2) block the follower from following the user, (3) accept invitations to compete in a head-to-head game, etc. Some examples of options can appear in either the interactive dropdown menu 536 and/or the interactive dropdown menu 539 can include options to: (1) send a whisper (i.e., a private message), (2) see the social contact's profile, (3) present video replay feeds of the social contact's wagering game activity (e.g., could be a graphical link to the video content), (4) embed video content (e.g., could use a thumbnail image of video and, when activated, display video in a chat feed window or pop-up in a main window), (5) be alerted of a certain game being played by the social contact, (6) challenge to a head-to-head competition, (7) self-invite to the social contact's game, (8) etc.
In some embodiments, the system 500 can combine player accounts and chat social contacts, and their chat messages, into a single chat room. In other embodiments, the system 500 can separate, or segregate, player accounts and chat contacts into different chat rooms. In some embodiments, the system 500 can duplicate instances of a chat object that represent the player account and place chat object into different chat rooms. The system 500 can also aggregate chat comments, and/or news messages, from the different chat rooms into a single chat console for the player account. For example, the system 500 can determine that the player account is chatting in a first chat room via a chat room console. The system 500 can also determine that a followed social contact is in a second chat room separate from the first chat room. The system 500 can determine that the followed social contact makes chat messages while chatting in the second chat room. The system 500, however, can present the chat messages for the followed social contact to the player account via the chat room console for the first chat room.
The flow 300 continues at processing block 312, where the system integrates chat activity with client applications, and social network functions. For example, in
In some embodiments, the third party chat client 606 can launch a chat console 612. The chat console 612 can include a list of social contacts (e.g., buddy list 616). Some of the social contacts, such as social contacts 621, can be for social network accounts that are linked to, or acquainted with, a user account 614. The user account 614 can be a chat account, or other social network account, that communicates with the chat server 640 via the chat console 612.
Some of the social contacts, such as social contact 623, can represent game bots (e.g., the social contact 623 is associated with a game bot for the Zeus game). The user account 614 can use the chat console 612 to play wagering games using textual commands. For example, the social contact 623, or more particularly, the game bot associated with the social contact 623, can send a first message 646 to the user account 614 to play the Zeus game via the chat console 612. The user account 614 can generate a second message 647 that includes a textual command, with special characters or phrases that control the Zeus game via the chat console 612. When the game bot receives a textual command, the game bot can connect the user account 614, if not already connected, to an associated player account for the user account 614. For instance, the game bot can logon the player account to an account server associated with the wagering game server 650. The player account links the user account 614 to the wagering game server 650 so that the user account 614 can provide game commands, which the wagering game server 650 can process. The wagering game server 650 can receive the textual command in the second message 647, decipher the textual command's meaning, and process the textual command. For example, the second message 647 includes special characters that the wagering game server 650 deciphers as a command to spin the Zeus game once with a $1 bet. The wagering game server 650 generates a game result for the Zeus game, for the one spin, and sends a third message 648 that indicates a game result for the one spin. The wagering game server 650 can send and receive the messages via the chat server 640. The wagering game server 650 can transact the bet and/or any winnings from, or to, the user account 614. In some embodiments, textual commands can launch a wagering game application (e.g., bring up a flash application of a wagering game), control the wagering game application, close the wagering game application, etc.
In some embodiments, the third party chat client 606 can include a gaming toolbar 641 that can be used instead of, or in conjunction with, textual commands. The gaming toolbar 641, for instance, can include a first button 642 configured to present player account information and a second button 644 configured to present gaming content. For example, activation of the second button 644 can integrate with and control a game client 610 stored on the computer 637 and/or served as a server-based application by the wagering game server 650. The gaming toolbar 641 can be a plug-in to the third party chat client 606, which presents the gaming toolbar 641 below chat functionality of the third party chat client 606. The chat console 612 can also include a chat room console 618 which the player account can use to access game related chat rooms (e.g., Zeus' Throne Room) and non-game-related chat rooms (e.g., Chuckle Hut). In some embodiments, the system 600 can integrate the chat features with gaming text commands into another casino website's chat or social network's applications. The system 600 can also integrate the chat features with other local applications.
In some embodiments, the system 600 can include a keystroke watcher application 608. The keystroke watcher application 608 can be a plug-in embedded in the third party chat client 606, or any other local software application, that watches for specific key-stroke combinations by the player, or other similar player configured inputs that initiate gaming functionality. The keystroke watcher application 608 can watch for pre-configured gaming keystrokes that are activated by the user of the computer 637. Once the keystroke watcher application 608 detects a gaming keystroke, the keystroke watcher application 608 coordinates with the wagering game server 650 to enable the wagering functionality. The keystroke watcher application 608 can also plug into, and track keystrokes from, any application that runs on the computer 637.
In some embodiments, the system 600 can integrate chat features, contact lists, etc., from different chat clients, social network platforms, etc. For example, the system 600 can integrate contacts from different chat clients (e.g., Yahoo Messenger) and/or social networks websites (e.g., Facebook™) into a single chat console.
In some embodiments, the system 600 can send wins, bonuses, and referrals through the third party chat client 606. The system 600 can solicit referrals through the chat console 612 (e.g., via a chat message 649). The system 600 can use the game bot associated with the social contact 623 to send the chat message 649.
This section describes example operating environments, systems and networks, and presents structural aspects of some embodiments.
The memory unit 730 may also include an I/O scheduling policy unit 7 and I/O schedulers 7. The memory unit 730 can store data and/or instructions, and may comprise any suitable memory, such as a dynamic random access memory (DRAM), for example. The computer system 700 may also include one or more suitable integrated drive electronics (IDE) drive(s) 708 and/or other suitable storage devices. A graphics controller 704 controls the display of information on a display device 706, according to some embodiments.
The input/output controller hub (ICH) 724 provides an interface to I/O devices or peripheral components for the computer system 700. The ICH 724 may comprise any suitable interface controller to provide for any suitable communication link to the processor unit 702, memory unit 730 and/or to any suitable device or component in communication with the ICH 724. The ICH 724 can provide suitable arbitration and buffering for each interface.
For one embodiment, the ICH 724 provides an interface to the one or more IDE drives 708, such as a hard disk drive (HDD) or compact disc read only memory (CD ROM) drive, or to suitable universal serial bus (USB) devices through one or more USB ports 710. For one embodiment, the ICH 724 also provides an interface to a keyboard 712, selection device 714 (e.g., a mouse, trackball, touchpad, etc.), CD-ROM drive 718, and one or more suitable devices through one or more firewire ports 716. For one embodiment, the ICH 724 also provides a network interface 720 though which the computer system 700 can communicate with other computers and/or devices.
The computer system 700 may also include a machine-readable medium that stores a set of instructions (e.g., software) embodying any one, or all, of the methodologies for integrate chat and wagering games. Furthermore, software can reside, completely or at least partially, within the memory unit 730 and/or within the processor unit 702. The computer system 700 can also include a gaming chat module 737. The gaming chat module 737 can process communications, commands, or other information, to integrate chat and wagering games. Any component of the computer system 700 can be implemented as hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein.
The CPU 926 is also connected to an input/output (“I/O”) bus 922, which can include any suitable bus technologies, such as an AGTL+ frontside bus and a PCI backside bus. The I/O bus 922 is connected to a payout mechanism 908, primary display 910, secondary display 912, value input device 914, player input device 916, information reader 918, and storage unit 930. The player input device 916 can include the value input device 914 to the extent the player input device 916 is used to place wagers. The I/O bus 922 is also connected to an external system interface 924, which is connected to external systems (e.g., wagering game networks). The external system interface 924 can include logic for exchanging information over wired and wireless networks (e.g., 802.11g transceiver, Bluetooth transceiver, Ethernet transceiver, etc.)
The I/O bus 922 is also connected to a location unit 938. The location unit 938 can create player information that indicates the wagering game machine's location/movements in a casino. In some embodiments, the location unit 938 includes a global positioning system (GPS) receiver that can determine the wagering game machine's location using GPS satellites. In other embodiments, the location unit 938 can include a radio frequency identification (RFID) tag that can determine the wagering game machine's location using RFID readers positioned throughout a casino. Some embodiments can use GPS receiver and RFID tags in combination, while other embodiments can use other suitable methods for determining the wagering game machine's location. Although not shown in
In some embodiments, the wagering game machine 906 can include additional peripheral devices and/or more than one of each component shown in
In some embodiments, the wagering game machine 906 includes a gaming chat module 937. The gaming chat module 937 can process communications, commands, or other information, where the processing can integrate chat and wagering games.
Furthermore, any component of the wagering game machine 906 can include hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein.
The mobile wagering game machine 1000 includes several input/output devices. In particular, the mobile wagering game machine 1000 includes buttons 1020, audio jack 1008, speaker 1014, display 1016, biometric device 1006, wireless transmission devices (e.g., wireless communication units 1012 and 1024), microphone 1018, and card reader 1022. Additionally, the mobile wagering game machine can include tilt, orientation, ambient light, or other environmental sensors.
In some embodiments, the mobile wagering game machine 1000 uses the biometric device 1006 for authenticating players, whereas it uses the display 1016 and the speaker 1014 for presenting wagering game results and other information (e.g., credits, progressive jackpots, etc.). The mobile wagering game machine 1000 can also present audio through the audio jack 1008 or through a wireless link such as Bluetooth.
In some embodiments, the wireless communication unit 1012 can include infrared wireless communications technology for receiving wagering game content while docked in a wager gaming station. The wireless communication unit 1024 can include an 802.11G transceiver for connecting to and exchanging information with wireless access points. The wireless communication unit 1024 can include a Bluetooth transceiver for exchanging information with other Bluetooth enabled devices.
In some embodiments, the mobile wagering game machine 1000 is constructed from damage resistant materials, such as polymer plastics. Portions of the mobile wagering game machine 1000 can be constructed from non-porous plastics, which exhibit antimicrobial qualities. Also, the mobile wagering game machine 1000 can be liquid resistant for easy cleaning and sanitization.
In some embodiments, the mobile wagering game machine 1000 can also include an input/output (“I/O”) port 1030 for connecting directly to another device, such as to a peripheral device, a secondary mobile machine, etc. Furthermore, any component of the mobile wagering game machine 1000 can include hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein.
The described embodiments may be provided as a computer program product, or software, that may include a machine-readable medium having stored thereon instructions, which may be used to program a computer system (or other electronic device(s)) to perform a process according to embodiments(s), whether presently described or not, because every conceivable variation is not enumerated herein. A machine readable medium includes any mechanism for storing or transmitting information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). The machine-readable medium may include, but is not limited to, magnetic storage medium (e.g., floppy diskette); optical storage medium (e.g., CD-ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; or other types of medium suitable for storing electronic instructions. In addition, embodiments may be embodied in an electrical, optical, acoustical or other form of propagated signal (e.g., carrier waves, infrared signals, digital signals, etc.), or wireline, wireless, or other communications medium.
This detailed description refers to specific examples in the drawings and illustrations. These examples are described in sufficient detail to enable those skilled in the art to practice the inventive subject matter. These examples also serve to illustrate how the inventive subject matter can be applied to various purposes or embodiments. Other embodiments are included within the inventive subject matter, as logical, mechanical, electrical, and other changes can be made to the example embodiments described herein. Features of various embodiments described herein, however essential to the example embodiments in which they are incorporated, do not limit the inventive subject matter as a whole, and any reference to the invention, its elements, operation, and application are not limiting as a whole, but serve only to define these example embodiments. This detailed description does not, therefore, limit embodiments, which are defined only by the appended claims. Each of the embodiments described herein are contemplated as falling within the inventive subject matter, which is set forth in the following claims.
This application is a divisional of, and claims priority benefit to, U.S. patent application Ser. No. 13/499,064 which is the National Stage of International Application No. PCT/US10/51018 filed 30 Sep. 2010, which claims priority benefit of U.S. Application No. 61/247,631 filed 1 Oct. 2009. The U.S. patent application Ser. No. 13/499,064, the International Application No. PCT/US10/51018, and the U.S. Patent Application No. 61/247,631 are incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5830067 | Graves et al. | Nov 1998 | A |
| 20050043088 | Nguyen et al. | Feb 2005 | A1 |
| 20060211479 | Walker et al. | Sep 2006 | A1 |
| 20060287046 | Walker et al. | Dec 2006 | A1 |
| 20070015574 | Vale et al. | Jan 2007 | A1 |
| 20070060355 | Amaitis et al. | Mar 2007 | A1 |
| 20070197247 | Inselberg | Aug 2007 | A1 |
| 20070298886 | Aguilar et al. | Dec 2007 | A1 |
| 20080287180 | Hutchinson-Kay | Nov 2008 | A1 |
| 20100062840 | Herrmann | Mar 2010 | A1 |
| 20120214564 | Barclay et al. | Aug 2012 | A1 |
| 20130244778 | Barclay et al. | Sep 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| WO-2011041619 | Apr 2011 | WO |
| Entry |
|---|
| “PCT Application No. PCT/US10/51018 International Preliminary Report on Patentability”, Oct. 24, 2011 , 5 pages. |
| “PCT Application No. PCT/US10/51018 International Search Report”, Dec. 2, 2010 , 8 pages. |
| “U.S. Appl. No. 13/874,797 Office Action”, Apr. 28, 2015. |
| Co-pending U.S. Appl. No. 13/874,797, filed May 1, 2013, 54 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20130244743 A1 | Sep 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61247631 | Oct 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13499064 | US | |
| Child | 13874705 | US |
