This application claims the priority benefit of U.S. Provisional Application Ser. No. 61/861,546 filed 2 Aug. 2013.
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. Copyright 2014, WMS Gaming, Inc.
Embodiments of the inventive subject matter relate generally to wagering game systems, and more particularly to wagering game systems capable of intelligent game content selection.
Wagering game machines, such as slot machines, video poker machines and the like, have been a cornerstone of the gaming industry for several years. Generally, the popularity of such machines depends on the likelihood (or perceived likelihood) of winning money at the machine and the intrinsic entertainment value of the machine relative to other available gaming options. Where the available gaming options include a number of competing wagering game machines and the expectation of winning at each machine is roughly the same (or believed to be the same), players are likely to be attracted to the most entertaining and exciting machines. Shrewd operators consequently strive to employ the most entertaining and exciting machines, features, and enhancements available because such machines attract frequent play and hence increase profitability to the operator. Therefore, there is a continuing need for wagering game machine manufacturers to continuously develop new games and gaming enhancements that will attract frequent play.
Embodiments of the invention are illustrated in the Figures of the accompanying drawings in which:
This section provides an introduction to some embodiments of the invention.
With such a vast variety of game content available, players may have difficulty selecting games suited to their personal preferences, current surroundings, current tasks, etc. For example, a player may wish to play a game on his/her mobile device while commuting via public transit. The player may prefer poker wagering games and music-themed social games. For the player to satisfy his/her desire, the player may have to search through a seemingly endless game catalogue to find a game meeting his/her preferences, such as a game that is non-disruptive while commuting via public transit, and requires an appropriate concentration level for commuting via public transit. Some embodiments of the inventive subject matter aid the player by analyzing player preferences, device usage, usage environment (location, situation, etc.), device type, etc. to provide the player with a game suited to his/her preferences, environment, attention capability in the environment, etc.
As depicted in
At stage B, the content distribution engine 104 determines the type of device that made the game content request and transmitted the usage information and affinity information. As depicted in
At stage C, the content distribution engine 104 determines game content to transmit to the mobile device 102. In some embodiments, this determination is made by analyzing the usage information, affinity information, and device type. For example, the usage information can indicate that the player is currently at home, has a high speed internet connection, and is in a quiet environment. The affinity information (based on previous games played or information provided by the player) can indicate that the player prefers casino-style card games that are fast-paced. As one example, the content distribution engine 104 can use this information to determine that the player is able to devote sufficient attention to a game, the player would like fast-paced blackjack game, and that the game need not be noisy. Alternatively, the usage information can indicate that the player is running errands, and thus is not able to devote significant attention to the game. Using this information, the content distribution engine 104 can determine that a game requiring lesser attention is appropriate. Additionally, the content distribution engine 104 can select game content based on the type of device from which the request is received. For example, if the content distribution engine 104 receives the request from a desktop computer, the content distribution engine 104 can provide a game that is RAM-intensive (Random Access Memory), requires a large screen, has complex graphics, requires keyboard input, etc. Likewise, if the content distribution engine 104 receives the request from a cellular telephone, the content distribution engine 104 can provide a game that can be presented easily on a less-powerful device with a smaller screen.
At stage D, the content distribution engine 104 transmits that game content to the mobile device 102. For example, when the player opens an application or navigates to a webpage associated with the content distribution engine 104, the content distribution engine 104 can transmit the game content to the mobile device 102. Additionally, in some embodiments, the game content that the content distribution engine 104 transmits can include more than a game. For example, if the usage information indicates that the player is at the airport and has an upcoming flight, the content distribution engine 104 can transmit data needed for the player to play a significant number of hands of a card game, several levels of a social game, etc. to the mobile device 102 so that the player can play the game when the player does not have internet connectivity.
While
At stage A, the content distribution engine 208 receives device identifiers from computing devices 202, 204, and 206, as indicated by arrows 210. As depicted in
At stage B, the content distribution engine 208 registers the computing devices 202, 204, and 206. In some embodiments, once the computing devices 202, 204, and 206 are registered, the content distribution engine 208 can associate the computing devices 202, 204, and 206 with one another. The content distribution engine 208 can also associate the usage information and affinity information corresponding to each computing device 202, 204, and 206 with the other computing devices 202, 204, 206. This can provide a unified game experience across the registered computing devices 202, 204, and 206. In embodiments where the content distribution engine 208 receives a player identifier, the content distribution engine can register the computing devices 202, 204, and 206 and associate the computing devices 202, 204, and 206 with the player identifier. This can further the unified game experience across the registered computing devices 202, 204, and 206.
This section describes operations associated with some embodiments of the invention. In the discussion below, the flow diagrams will be described with reference to the block diagrams presented above. However, in some embodiments, the operations can be performed by logic not described in the block diagrams.
In certain embodiments, the operations can be performed by executing instructions residing on machine-readable storage media, 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 less than all the operations shown in any flow diagram.
At block 402, a content distribution engine registers a plurality of computing devices. In some embodiments, the content distribution engine registers each computing device individually (i.e., each computing device is registered separately as opposed to multiple devices being associated with a player account or other computing devices). In other embodiments, the content distribution engine can register a plurality of computing devices as being associated with a single player. In such embodiments, a plurality computing devices used by a single player can be associated with one another. The registration can also include a player identifier (e.g., used by a player to login). In such embodiments, the content distribution engine registers and associates the computing devices with the player identifier. The flow continues at block 404.
At block 404, the content distribution engine receives a request for game content, usage information, and affinity information from the computing devices. The usage information, for example, can include:
Although the operations at blocks 402 through 410 are depicted in
At block 406, the content distribution engine determines the type of device in-use. For example, the computing device can be a desktop computer, a laptop computer, a tablet computer, a cellular telephone, a PDA, etc. In some embodiments, the computing device can transmit an indication of its type to the content distribution engine (e.g., the indication can be included in the usage information). In some embodiments, the content distribution engine can determine the type of device without receiving an indication of the device type from the computing device. For example, the content distribution engine may receive a device identifier with which it looks-up the device type in a database of registration information associated with the device. The flow continues at block 408.
At block 408, the content distribution engine determines game content for the computing device. In some embodiments, this determination is based on the type of device, usage information, and affinity information. Using this information, the content distribution engine can select content appropriate for the device, environment, and player's liking. For example, if the type of device is a tablet computer, the usage information indicates that the player is in a doctor's office waiting room, and the affinity information indicates that the player prefers sports games, the content distribution engine can determine that the player has time to play an attention-intensive level of a sports game with minimal audio formatted for a tablet computer. Additionally, for example, the content distribution engine can:
At block 410, the content distribution engine transmits the game content to the computing device.
While
At block 502, the content distribution engine transmits game content to a computing device. The content distribution engine can use the operations described in
At block 504, the content distribution engine receives feedback for the game content. For example, a player can indicate that they enjoy the game content transmitted to the computing device. Alternatively, the player can indicate that they do not enjoy the game content transmitted to the computing device. In some embodiments, the player feedback can be more extensive than a simple like or dislike of the game content. For example, the player feedback can indicate specific aspects of the game content which the player likes or dislikes. In some embodiments, the feedback for the game content is received, and the game content updated, in real time. For example, when the player provides negative feedback for the game content, the content distribution engine immediately provides new or modified game content. The flow continues at block 506.
At block 506, the content distribution engine stores the feedback. In some embodiments, the content distribution engine stores the feedback in association with one or more of the computing device, a player identifier, a player account, etc. In such embodiments, the content distribution engine can aggregate the feedback (along with usage information) to establish a rich database of usage information and affinity information for the computing device and/or player. The flow continues at decision diamond 508.
At decision diamond 508, the content distribution engine analyzes the feedback to determine whether it is positive feedback (i.e., the player likes the game content and/or aspects of the game content) or negative feedback (i.e., the player dislikes the game content and/or aspects of the game content). If the feedback is positive feedback, the flow continues at decision diamond 514. If the feedback is negative feedback, the flow continues at block 510.
At block 510 the content distribution engine modifies the game content or determines new game content to transmit, based on the negative feedback. Additionally, the content distribution engine can modify the game content or determine new game content to transmit based on the device type, usage information, and affinity information. The content distribution engine can modify the content, for example, by:
At block 512, the content distribution engine transmits the modified or new game content. If the content distribution engine modified the game content at block 510, the content distribution engine transmits that modified game content. If the content distribution engine selected new game content at block 510, the content distribution engine transmits the new game content. The flow continues at decision diamond 514.
At decision diamond 514, the content distribution engine determines if the player is done using the game content. If the player is not done using the game content, the flow continues at block 504. If the player is done using the game content, the flow ends.
Although examples refer to the content distribution engine transmitting game content, in some embodiments, media other than, or in conjunction with, game content can be transmitted. For example, based on the usage information and affinity information, the content distribution engine can transmit advertisements, coupons, news articles, videos, pictures, or any other media.
Although examples refer to accessing content received from a content distribution engine via an application running on the computing device, in some embodiments, a player can access content received from the content distribution engine via a web browser. For example, the player can navigate the web browser to a webpage or website associated with the content distribution engine. In some embodiments, the player can login, or the computing device can transmit a device identifier (or other means for identification) to the content distribution engine. In response, the content distribution engine can transmit game content to the computing device.
Although examples refer to transmitting game content to a player based on player convenience, in some embodiments, the content distribution engine can transmit game content to players to optimize server load. For example, in some embodiments, the content distribution engine may receive few requests during nighttime hours. In such embodiments, the content distribution engine can transmit game content to a players' device during this off-peak time. The players' device(s) can store the game content until the player accesses the game content. For example, the content distribution engine can transmit several slot reel spins, poker hands, social game levels, etc. to a player's device during off-peak hours. The player can then access the transmitted game content without further interaction with the content distribution engine.
Each casino 612 includes a local area network 616, which includes an access point 604, a wagering game server 606, and wagering game machines 602. The access point 604 provides wireless communication links 610 and wired communication links 608. The wired and wireless communication links can employ any suitable connection technology, such as Bluetooth, 802.11, Ethernet, public switched telephone networks, SONET, etc. In some embodiments, the wagering game server 606 can serve wagering games and distribute content to devices located in other casinos 612 or at other locations on the communications network 614. Additionally, a content distribution engine 618 and computing devices 620 are in communication with the communications network 614. The content distribution engine 618 receives usage information (including device type information) and affinity information from the computing devices 620 and determines game content to transmit to the computing devices 620 based on the usage information and affinity information (as described herein).
The wagering game machines 602 described herein can take any suitable form, such as floor standing models, handheld mobile units, bartop models, workstation-type console models, etc. Further, the wagering game machines 602 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 one embodiment, the wagering game network 600 can include other network devices, such as accounting servers, wide area progressive servers, player tracking servers, and/or other devices suitable for use in connection with embodiments of the invention.
In some embodiments, wagering game machines 602 and wagering game servers 606 work together such that a wagering game machine 602 can be operated as a thin, thick, or intermediate client. For example, one or more elements of game play may be controlled by the wagering game machine 602 (client) or the wagering game server 606 (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 606 can perform functions such as determining game outcome or managing assets, while the wagering game machine 602 can present a graphical representation of such outcome or asset modification to the user (e.g., player). In a thick-client example, the wagering game machines 602 can determine game outcomes and communicate the outcomes to the wagering game server 606 for recording or managing a player's account.
In some embodiments, either the wagering game machines 602 (client) or the wagering game server 606 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 606) or locally (e.g., by the wagering game machine 602). 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.
Any of the wagering game network components (e.g., the wagering game machines 602) can include hardware and machine-readable media including instructions for performing the operations described herein.
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 of the invention, 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.
As will be appreciated by one skilled in the art, aspects of the present inventive subject matter may be embodied as a system, method or computer program product. Accordingly, aspects of the present inventive subject matter may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present inventive subject matter may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Number | Date | Country | |
---|---|---|---|
61861546 | Aug 2013 | US |