The subject matter described herein relates to a peer-to-peer software platform that enables dynamic advertising based on gameplay and wagering on online skill based games.
An online game is a video game played over a network on some form of computer, mobile device, or on a video game console such as the Xbox 360 and PlayStation 3. This usually means the Internet or equivalent technology, but games can use a wide range of technologies. A recent expansion of online gaming has reflected the overall expansion of computer networks from small local networks to the Internet and the growth of Internet access itself.
Online games can range from simple text based games to mobile games to games incorporating complex graphics and virtual worlds populated by many players simultaneously. Many online games require skill and strategy and have a social aspect beyond single player games. For example, players compete head-to-head, in a tournament, or for the highest score on a leader board. Example categories of online skill-based games include first person shooters, real time strategy games, social games, role-playing games, board games, card games, etc. Due to their social nature, many online games are inherently competitive.
In one aspect, data characterizing historical skills-based gaming metrics for a first user and historical skills-based gaming metrics for at least one second user is accessed. Using the accessed data and a set of rules, a targeted advertisement to present to the first user is determined. The targeted advertisement specifies at least one skills-based game and a characterization of the at least one second user's historical skills-based gaming metrics. The targeted advertisement is generated. Data characterizing the targeted advertisement is provided.
In another aspect, a digital skills based game is provided to a first user. The skills based game includes display space for displaying at least one advertisement to the user. Using historical skills-based gaming metrics and a set of rules, a targeted advertisement to present to the first user is determined. The targeted advertisement specifies at least one skills-based game and a characterization of at least one second user's historical skills-based gaming metrics. The advertisement display space is modified to include the targeted advertisement. The advertisement prompts the user to, using a peer-to-peer wagering platform, enroll in and place a wager on an online skills based gaming competition. The online skills-based gaming competition is provided to the user.
In yet another aspect, a system includes a third party gaming server, a plurality of third party game instances, and a transactional server. The third party gaming server provides data related to the third party game. The plurality of third party game instances are in communication with and receiving game data from the third party gaming server. Each third party game instance includes a peer-wagering module. The transactional server determines, using historical skills-based gaming metrics and a set of rules, a targeted advertisement to present to a first user. The targeted advertisement specifies at least one skills-based game, and a characterization of at least one second user's historical skills-based gaming metrics. The transactional server generates the targeted advertisement.
One or more of the following features can be included. For example, the advertisement can further specify a proposed wager for the first user in connection with the at least one skills-based game. When to prompt the targeted advertisement to the first user can be determined using the accessed data and the set of rules. Historical skills-based gaming metrics can include game-related attributes from a user's past game plays. Historical skills-based gaming metrics can include game-related attributes from a user's in-progress game or most recent game played. Historical skills-based gaming metrics can include one or more of: game outcome, game score, game level completed, game difficulty, player ratings, average game scores, statistical measure of game outcome, game achievements, top scores across a set of other user's results, completion of in-game objectives, user ranking, in-game character level, in-game character possession of game item, in-game character attribute.
Historical skills-based gaming metrics can be aggregated by tracking a user's game data over a period of time. The first user can provide a peer-to-peer wagering platform that enables the first user to place a wager on an online skills-based gaming competition. Providing can include transmitting, persisting, displaying, and prompting to the user. The set of rules can be customizable by a skills-based game tournament creator. The targeted advertisement can further specify at least one skills-based game tournament. The historical skills-based gaming metrics for the at least one second user can be taken from skills-based game tournaments. The advertisement can further specify a proposed wager for the first user in connection with the at least one skills-based game. When to modify the advertisement display space can be determined using the accessed data and the set of rules.
The transactional server can be configured to generate a pseudo-random number stream for use by at least some of the plurality of third party game instances.
In yet another aspect, a system includes a third party game server, a plurality of third party game instances and a transactional server. The third party game server provides data related to a third party game. Each of the third party game instances is in communication with and receiving game data from the third party gaming server. Additionally, each third party game instances includes a peer-wagering module to receive a wager amount from a player associated with the corresponding third party game instance. Each third party game instance is associated with an online gaming competition and each player is participating in the online gaming competition. The transactional server receives the wager amount from each peer-wagering module. The transactional server secures previously deposited funds associated with each of the associated corresponding players. The fund amount is equal to the respective wager amount. Each server includes at least one computing system having at least one data processor.
In yet another aspect, data characterizing a plurality of players and a wager amount for each player can be received. Each player is enrolled in a third party skills based digital gaming competition. An amount of funds previously deposited by the respective player is secured for each player, using an online skills based digital game wagering platform. The secured funds are equal to the wager amount. The funds can be secured such that they cannot be transferred, withdrawn, or secured for a different wager. Data characterizing a confirmation that each of the plurality of players funds were successfully secured is transmitted.
In yet another aspect, a digital skills based game is provided to a player using a mobile processing device. The skills based game is single player and displays at least one advertisement to the player. The advertisement is modified using historical gaming results of the player. Content of the advertisement includes text, graphics, and linked-destination. The advertisement prompts the player to enroll in and place a wager on an online skills based gaming competition. The online skills based gaming competition is provided to the player.
One or more of the following features can be included. The transactional server can receive game statistics describing the results of the online gaming competition from the third party gaming server and automatically transfer, based on the received game statistics, at least a portion of the secured funds to at least one account associated with at least one of the players. The third party game can be an asynchronous competitive skill based game played between each player. The third party game can be a synchronous competitive skill based game played between each player. The transactional server can send a notification of each player's winnings, losses, score, time, and other game play information to the peer-wagering module in each of the plurality of game instances. The transactional server can determine if the previously deposited funds associated with a player are less than the wager amount. The online gaming competition can be a tournament. The online game competition can be selected from a group consisting of: Massively Multiplayer Online Role Playing Games (“MMORPG”), First Person Shooters (“FPS”), and Real Time Strategy (“RTS”) games.
Data characterizing the outcome of the third party skills based gaming competition can be received. At least a portion of the secured funds can be transferred, using the online skills based digital game wagering platform, to an account associated with one of the plurality of players. Data characterizing the transfer can be transmitted. Data characterizing the winnings and losses of one or more of the plurality of players can be transmitted. At least one of the plurality of player's can be rewarded with non-monetary compensation based on the outcome of the third party skills based gaming competition. The non-monetary compensation can be used as a substitute to funds to enter a future online skills based gaming competition. The data characterizing the transfer can be transmitted to a plurality of peer-wagering modules, each module included in an instance of a third party game. The data characterizing the confirmation is transmitted to a plurality of peer-wagering modules, each module included in an instance of a third party game. The data characterizing the outcome of the third party skills gaming competition can be received from a third party game server, the game server providing game data to a plurality of game instances in communication with the game server, each game instance including a peer-wagering module.
The data characterizing the outcome of the third party skills gaming competition can be received from a plurality of peer-wagering modules. Each module can be included in an instance of a third party game in communication with a game server providing game data to the plurality of game instances. The third party skills based gaming competition can be associated with an asynchronous game. The third party skills based gaming competition can be associated with a synchronous game. The wager amount can include a plurality of values. Each value can be associated with one of the plurality of players.
Data characterizing the player's game play can be received. One or more characteristics of the received data can be monitored. The monitored characteristics can be compared to historical characteristics associated with the player to detect fraudulent behavior by the player. Deviations between the monitored characteristics and historical characteristics can indicate fraud. The monitoring can be performed in real time. The monitoring can be performed after the online skills based game competition is complete.
Articles of manufacture are also described that comprise computer executable instructions permanently stored (e.g., non-transitorily stored, etc.) on computer readable media, which, when executed by a computer, causes the computer to perform operations herein. Similarly, computer systems are also described that may include a processor and a memory coupled to the processor. The memory may temporarily or permanently store one or more programs that cause the processor to perform one or more of the operations described herein. In addition, methods can be implemented by one or more data processors either within a single computing system or distributed among two or more computing systems.
The subject matter described herein provides many advantages. The current subject matter provides a fully integrated set of technologies to facilitate wagering within electronic multiplayer or single-player games of skill. Users can complete a wager conveniently and receive any winnings. Users can track individual winnings and losses and, when placing bets, can be comfortable knowing that the current subject matter places wagered funds in escrow to guarantee payment to the winner(s). Additionally, users can easily create competitions using their favorite online game for friends to join and wager real money on the outcome. Users can also compete against strangers. Furthermore, a software development kit provides game developers with a toolset that is easy to integrate into games. The current subject matter can convert any game of skill into a tournament enabled wagering platform. The current subject matter also enables user-created tournaments.
The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Other features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims.
Like reference symbols in the various drawings indicate like elements.
Each game instance 130i includes a peer-wagering module 140i. The peer-wagering module 140i integrates into the game instance 130i and enables the players 110i to wager on the outcome of a given game competition. The peer-wagering module 140i communicates with and works in tandem with a transactional server 160. The transactional server 160 maintains account information for each player 110i, including financial information, and acts as a trusted party to hold funds in escrow and/or secure funds to enforce the terms of a wager (i.e., ensures winning players receive the winnings).
The transactional server 160 can also pass data characterizing advertisements (e.g., advertising logic, invitations, and/or messages) to the third party game server 150. This advertising data can be algorithmically customized based on player 110i historical gaming data or metrics of the gaming data. For example, an advertisement could include or be modified to prompt the player with “you've won four out of five of your last games, click here to play in $5 tournament and take your game play to the next level.”
The historical skills-based gaming metrics can be supplied by the player client 120i, or tracked and/or recorded (e.g., over time) by the transactional server 160, or the third party gaming server 150. Historical skills-based gaming metrics can include game attributes that can be traced (e.g., recorded or monitored) and are associated with the player's in-progress, most recent, and/or past game plays. For example, historical skills-based gaming data can include: an in-game score, game outcome, time to complete a stage, game level achieved, difficulty, number of enemies, power-ups acquired, player ratings, number of wins or losses, statistical measures of attributes (e.g., average scores, ratio of wins to losses, etc.), top scores across some or all players, completion of any game related task, objective, and/or achievement, in-game acquisition of items, and/or other character attributes. Historical skills-based gaming metrics can include other traceable game attributes.
When the advertisement is presented to the player and/or the content of the targeted advertisement can be based on configurable messaging rules (i.e., a set of rules). The rules can be used to target players with specific attributes, levels of skill, or relationships. For example, an advertisement or invitation could prompt to a player to join and wager on a tournament based on a player exceeding a certain predetermined value or score for a particular in-game challenge. The rules could include whether the player has completed a particular level, game, number of games played, time played, or other game element. An advertisement could be presented when a player is among a certain percentile of players (e.g., prompting players to enroll in a tournament with like-skilled players).
Additional rule examples can include when a player has wagered, lost, and/or won at least a certain amount (e.g., prompting players to enroll in a tournament that requires “high stakes” or large minimum wagers), when one or more other players associated with the first player (e.g., links on a social networking website) are enrolled in a tournament (e.g., prompting a player to enroll in a tournament with their friends), when a player has played a certain number of games, and/or when a player has completed a level or challenge in a tournament. The messaging rules can also be based on a geographic location of the player (e.g., online wagering regulations may vary based on locality), or whether the player is eligible to wager cash or rewards on a tournament. Administrators, and/or tournament creators can configure or customize the messaging rules.
The targeted advertisement can include graphical, textual, and hyperlink information necessary to populate pre-existing advertising space with a customized invitation for players to wager on a skill based gaming tournament. Targeted advertisements can include customized messages derived or based on the messaging rules and/or other data triggered by a rule, gameplay, or historical skills-based gameplay metrics. The targeted advertisement can be targeted to the player and include a characterization of the player's historical skills-based gaming metrics and a characterization of one or more other player's historical skills-based gaming metrics. For example, the targeted advertisement can include information regarding how many active games are being played for a given game or a different game. The advertisement can include a message regarding how many of the player's friends, contacts, or in-network users are active in the system. The advertisement content can show how a player would fare if they joined a tournament or played a different game by including a comparison between or characterization of the historical gaming data and other players in the system (e.g., showing how much money the player would have won in a real tournament, a comparison of the player's average score to other player's average scores, a mock leader board where the game player is compared to all players of the game, etc.). The targeted advertisement could include a proposed wager amount for the first player.
By utilizing specific player's historical gaming data and messaging rules, the advertisements/messages can be customized to the player and each advertisement has a higher likelihood of enticing the player than a non-customized (e.g., a general) advertisement.
Referring again to
Players 110i can create tournaments. Prior to game play, the peer-wagering module 140i can receive credential information from the player 110i, send the credentials to the transactional server 160, which can authenticate the credentials. Authentication can include age and location controls to ensure local law compliance. Age can be entered by the player 110i and location can be verified by any of a billing address used to fund an account, the GPS location of a mobile device (if available), and an IP address of the player client 120i. When each player 110i enrolls in a tournament, including placing a wager on the tournament (e.g., paying a tournament entry fee), the transactional server 160 can secure the player 110i funds. Secured funds cannot be withdrawn or used for another wager. Securing the funds can include transferring the funds from the player account to an escrow account as well as placing a “hold” on the funds in the player's account.
Once the transactional server 160 secures funds from all participating players 110i, the tournament can proceed. The tournament proceeds under normal game mechanics (such as each game instance 130i communicating game data with the game server 150) until game play completes. The transactional server 160 receives completed game statistics from the game server 150 or, alternatively, from each peer-wagering module 140i. The game statistics can indicate winners and losers based on one or more in-game metrics. A player 110i can also determine one or more custom in-game metrics to be used in determining winners and losers during tournament initialization. The transactional server 160 transfers the previously secured funds to one or more player 110i accounts based on the game statistics. For example, a winning player can have the player's winnings transferred from the other players' accounts or the secure escrow account into the winning player's account. The transactional server 160 sends financial data related to winnings and losses to each peer-wagering module 140i, which provides the financial data to the players 110i. Additionally, the transactional server 160 can send the game statistics to each peer-wagering module 140i, which provides the game statistics to the player 110i.
Game statistics sent to the transactional server 160 from either the game server 150 or from each peer-wagering module 140i can include summary level statistics such as winners and losers and/or specific in game actions such as player orientation within the gaming environment, player actions (e.g. buttons pressed or character movement), or user display details. The user display details can include, but are not limited to, graphics card-information, in-game screen shots and live action game-play. These statistics can be used to determine system level player-rewards that are independent from tournament outcomes as well as in the detection of fraudulent behavior through any of the following: real-time tournament monitoring, delayed tournament review, or statistical player review for idiosyncratic behavior or behavior characteristic of fraudulent play.
The peer-wagering module 140i provides necessary user interface components and player 110i to transactional server 160 interaction functionality for the game instance 130i. This provides a low barrier for third party game providers to enable the peer-wagering functionality into the game. The peer-wagering module can be implemented with platform specific software development kits (SDKs).
Communication can occur over any suitable communications network, such as, for example, the internet.
Optionally, at 240, the transactional server 160 receives data characterizing the outcome of the competition. The data can include in-game statistics and indicate that some of the enrolled players are winners and some are losers. Alternatively, the transactional server 160 can differentiate, based on the in-game statistics, players that are winners and players that are losers. The transactional server 160 can determine based on the in-game statistics the amount of secured funds (if any) to which enrolled players are entitled. Optionally, at 250, the transactional server 160 can transfer at least a portion of the secured funds to one or more accounts associated with their respective enrolled players. Optionally, at 260, the transactional server 160 can transmit data characterizing the transfer and/or the in-game statistics. The transactional server 160 can receive the respective data from and transmit the respective data to one or more of the peer-wagering module 140i and the third party game server 150.
The game can be asynchronous. Asynchronous games cover any turn-based game where players 110i take turns and real-time game play is not an issue. A player 110i may leave the game to perform other tasks on the same device on which the game is running, without forfeiting a tournament. Asynchronous games can include games such as Chess, Checkers, Go, and most board games where timing of player turns is not a consideration.
The game can be synchronous. Synchronous games cover any game where real time interaction between the game and player or between players is required. For example, first person simulations wherein each player has one or more characters (i.e. avatars) and multiple players' characters are interacting in real time with each other's characters or game environment in a synchronized way. First person shooters, driving and racing simulators as well as real time sports simulations are synchronous. Some turn-based game designs can also include synchronous aspects if all players must be present at some times while a game is in progress.
Whether synchronous or asynchronous, an entire level of a can game constitute a turn, and the players can take turns independently. For example, games such as Angry Birds, where two or more players can complete a level, independently but potentially at the same time, and the winner can be determined based on some metric when all players complete the level. In this manner, an entire level constitutes a player turn.
The transactional server 160 can provide an application-programming interface (API) for the third party game instances 130i or the third party game server 150 to communicate with the transactional server 160.
Establishing tournaments can allow players 110i to compete with one another within skill-based games in a single or series of contests. Tournaments can work with synchronous and asynchronous play modes, and tournaments can be user or system generated. Tournaments can be either public or private. Public tournaments can be open to any registered player while private tournaments can be open only to invited players. Any tournament must necessarily have at least two participants. Player-created tournaments can require a specific number of entrants in order to begin the competition, whereas system-created tournaments can have a fixed or variable number of permitted and/or required entrants. Tournaments with a variable number of participants can have a fixed starting time and can have a maximum number of allowed entrants.
Tournaments can comprise a single match or a series of matches (i.e., multi-round tournaments). The structure can be determined at the time of tournament creation. Each match can have a specified number of participants and winners. A specific win-metric can determine the winners of each match. Individual tournament rounds (e.g., matches) can begin at a pre-determined time set up by the creator of the tournament or they can proceed in immediate sequence. Matches not completed by the next designated match time slot can be terminated, and the top contenders from each non-concluded match can be rewarded the win for that match.
Each tournament or tournament round can have defined criteria by which the winner(s) are determined. Possible win-metrics can be dependent on the type of game, but can include (for example): highest score, first to complete a level, least moves to complete a level, etc. Additionally, each tournament can have an entry fee which is a dollar amount required to enter the tournament (i.e., a wager amount). However, some system-created tournaments can waive this fee for some or all players 110i. The tournament creator can determine the amount of the entry fee.
Prizes offered to tournament winner(s) can be determined at the time of tournament creation. Prize information can be visible to all prospective tournament entrants. In the case of user-created tournaments, the player creating the tournament can set the total prize pool automatically. For example, the creating player can set the prize pool based on the number of entrants and the entry fee that the creating player has specified. The creating player can allocate prizes in a variety of ways such as awarding prizes to more than one participant in a given tournament. A tournament creator can specify the number of winners and the percentage allocation of prizes to each of those winners. A public tournament creator can base prize distribution on individual performance relative to the defined win-metric; however, a private tournament creator can incorporate team scoring relative to the win-metric in determining prize allocation.
An example player 110i interaction with an asynchronous multiplayer game including the current subject matter includes creating a tournament, joining a tournament, and concluding a tournament. To create a tournament, the player 110i, using the player client 120i, launches a third party game instance 130i. The player can choose within the game to compete using the peer-wagering module 140i. The user can log into their transactional server 160 account, optionally electing to remain logged in to the account within this session and future session of this game.
Once signed into their account, the player 110i can create a public or private tournament and set parameters for the tournament. The transactional server 160 can prompt the player to add funds to their account if the player 110i has inadequate funding. The player 110i can invite several known players using their account names (e.g., email addresses, user names, etc.). If the tournament is a public tournament, uninvited participants can join. Public tournaments can start on a rolling basis with players taking their first turn as soon as they join the tournament or as soon as the player before them has played (depending on game mechanics). Private tournaments start when the prescribed number of participants has entered the tournament. The game proceeds according to the game developer's prescribed game mechanics.
If the player 110i does not yet have an account, the player 110i can register for an account by entering information such as email address and password in data fields 330 and pressing the next button 340.
To join a tournament, a player 110i can receive a notification inviting them to a tournament. Notifications can arrive via any one of several means. For example, push notifications, SMS, email and in-game notifications are all options for notification. Alternatively, the user browses public tournaments that are seeking players and selects one. The player 110i launches the game via the notification they have received or proceeds into the game after selecting a public tournament. The player 110i accepts the terms of the tournament, including the funding requirements of the tournament in response to a prompt. If the player 110i has inadequate funding in their account, they can add funds. The player 110i can accept the terms of the tournament and enter the game. The game proceeds according to the game developer's prescribed game mechanics.
In the case when the multiplayer game is synchronous, all players 110i must start the game simultaneously. To provide this functionality, the transactional server 160 presents the players 110i with a tournament lobby while they wait for the synchronous game tournament to begin. The transactional server 160 provides the lobby for both the player 110i who created the tournament as well as the players 110i who join the tournament. The players can see the other players as they join the tournament and can have the opportunity to withdraw from the tournament before the tournament begins. The game can begin a predetermine length of time (e.g., 60 seconds) after all players have joined the tournament. Any withdrawal by the players 110i after this point constitutes forfeiture of the tournament entry fee (i.e. the wager).
The tournament can also start at a predetermined time independent of the number of players 110i in the lobby. Players 110i can sign-up for the tournament in advance of the tournament start time. Once players 110i have signed-up for a tournament, the transactional server 160 can alert the players 110i that the tournament is starting soon through a variety of methods such as email, SMS, in-game alert, etc.
Detailed information 530 provides tournament information for a selected tournament and shows the name, type, number of players and maximum players, entry fee, and prize breakdown. In this example tournament, the top three players 110i will receive winnings. Player list 540 provides each player name and overall score currently entered in the tournament. Push buttons 550 enables the player 1101 to enter or not enter the tournament.
At the conclusion of a tournament, the normal game mechanics are complete and the third party game server 150 posts data to the transactional server 160 indicating game results. Each player 110i who completes the game should see game results immediately, including data from the transactional server 160 detailing their winnings or losses for the tournament. Other players 110i in the tournament can also receive a notification detailing their winnings or losses from the transactional server 160 and indicating that their tournament is complete. For games where a continuous connection to the service is important to game-play or game integrity, any player 110i who drops off the service and does not re-connect within a certain predetermined period forfeits the game. Third party game developers can determine the period or can optionally include reconnection logic to re-establish a lost connection between players when such a loss of connection cannot be used to gain an advantage in either game-play or waging. Additionally, players may be required to take their turn or take another specified in-game action within a predetermined amount of time. Players who do not act within this set amount of time, as determined by third party game developers, will forfeit the game. The peer-wagering module 140i can report to the transactional server 160 when the player 110i disconnects from the competition or when the player 110i has not taken his turn within the allotted time.
At 702 through 708 the player 110i logs into the transactional server 160 using the interface provided by the peer-wagering module 140i embedded in the game instance 130i. The peer-wagering module 140i authenticates 706 with the transaction server 160 allowing for further messaging between the peer-wagering module 140i and the transaction server 160, via authentication tokens, security certificates, or other user/password exchanges 708. All future requests are set with the valid authentication method. Peer-wagering module 140i requests 710 a list of potential gaming opponents for the logged in player for the currently running game. The transactional server 160 and peer-wagering module 1401 returns (712 and 714) a list of the players available for play as well as a list of current tournaments requiring additional players. The creating player 110i creates a tournament 716 and invites other players 110i. The peer-wagering module 140i sends 718 the transactional server 160 data regarding invited players 110i and the tournament name. When a player 110i joins the tournament, the player's information is communicated to the peer-wagering module 140i as well. Funds are transferred 720 from the joining/creating player's transactional server 160 account. The transactional server 160 places these funds in escrow or places a “hold” on wagered funds in player accounts. The transactional server 160 returns 722 a unique tournament ID and all entered players 110i wait 724 for the tournament to start. Each peer-wagering module 140i communicates with 726 the transactional server 160 with the tournament ID until the server indicates 728 the tournament has started. The peer-wagering module 140i can signal the transactional server 160 to force the tournament to start for those players who have joined.
During normal game play, all communication (732 and 734) occurs between the third party game instance 130i and its own third party game server 150. All active gaming statistics including rank of each player is communicated and coordinated between the game instance 130i and the gaming server 150. The third party game instance 130i communicates 736 data regarding any players 110i who have left the game or any data relevant to the detection of fraudulent behavior.
On completion of the game, each connected peer-wagering modules 140i send (740 and 742) tournament statistics to the transactional server 160. The transactional server 160 calculates winnings and losses based on the tournament statistics. The transactional server 160 sends (744 and 746) notifications to all players in the completed tournament indicating their tournament has completed, and they have winnings or losses, as well as a leader board for the tournament. The players 110i receiving the completion notification can launch a new game via the notification.
Alternatively, on completion of the game 750, the third party game server 150 sends 752 games statistics to the third party game 130i and sends 754 tournament statistics to the transactional server 160. Each peer-wagering module 140i polls 756 the transactional server 160. The transactional server 160 sends (758 and 760) a leader board for the tournament, as well as notifications to all players in the completed tournament indicating their tournament has completed, and indicating whether they have winnings or losses. The players 110i receiving the completion notification can launch a new game via the notification.
The data flow diagram of
The transactional server 160 can further be configured to generate a stream of pseudo-random numbers for use by the third party game instances. Since random numbers are typically used in gameplay engines to decide game elements and properties (e.g., what obstacles are present can be decided based on the value that a random number generator returns), the use of common random numbers can provide a common gameplay experience to a subset of users (e.g., the players involved in a third party game tournament). The common gameplay experience can be used to standardize (or level the playing field) for a game of skill that still has random elements.
For example, while Tetris is typically considered a game of skill, the order in which the Tetris pieces present to a player is normally random. By providing a common stream of pseudo-random numbers to each game instance participating in an online tournament, the order that Tetris pieces appear to each player can be common across all participating game instances. Thus, the results of a competitive tournament would be based entirely on skill, and not on a random chance of getting an easier order of Tetris pieces presented.
In one example, the transactional server 160 can use a tournament identification number as a seed to generate pseudo-random numbers, thus causing gameplay to be different between tournaments, but not between game instances involved in a given tournament.
Various implementations of the subject matter described herein may be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations may include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software, software applications or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the term “machine-readable medium” refers to any computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the subject matter described herein may be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user may provide input to the computer. Other kinds of devices may be used to provide for interaction with a user as well; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The subject matter described herein may be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a client computer having a graphical user interface or a Web browser through which a user may interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (“LAN”), a wide area network (“WAN”), and the Internet.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
Although a few variations have been described in detail above, other modifications are possible. For example, the logic flow depicted in the accompanying figures and described herein do not require the particular order shown, or sequential order, to achieve desirable results. Other embodiments may be within the scope of the following claims.
This application is a continuation of U.S. application Ser. No. 16/992,618, filed Aug. 13, 2020, which is a continuation of U.S. application Ser. No. 16/382,890 filed Apr. 12, 2019, and granted as U.S. Pat. No. 10,748,373, which is a continuation of U.S. application Ser. No. 15/595,794 filed May 15, 2017, and granted as U.S. Pat. No. 10,290,179, which is a continuation of U.S. application Ser. No. 14/976,569 filed Dec. 21, 2015, and granted as U.S. Pat. No. 9,649,564, which is a continuation of U.S. application Ser. No. 14/212,651 filed Mar. 14, 2014, and granted as U.S. Pat. No. 9,240,101, which is a continuation of U.S. application Ser. No. 13/858,581, filed Apr. 8, 2013, and granted as U.S. Pat. No. 8,715,077, which is a continuation-in-part of U.S. application Ser. No. 13/569,424, filed on Aug. 8, 2012, and granted as U.S. Pat. No. 8,414,387, the contents of each is hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
462448 | Paine et al. | Nov 1891 | A |
5169155 | Soules et al. | Dec 1992 | A |
5779545 | Berg et al. | Jul 1998 | A |
5823879 | Goldberg et al. | Oct 1998 | A |
5882260 | Marks et al. | Mar 1999 | A |
6533664 | Crumby | Mar 2003 | B1 |
6557120 | Nicholson et al. | Apr 2003 | B1 |
6676517 | Beavers | Jan 2004 | B2 |
6790143 | Crumby | Sep 2004 | B2 |
7048629 | Sines et al. | May 2006 | B2 |
7160189 | Walker et al. | Jan 2007 | B2 |
7329183 | Michaelson et al. | Feb 2008 | B2 |
7479062 | Michaelson | Jan 2009 | B2 |
7486273 | Aviles et al. | Feb 2009 | B1 |
7517282 | Pryor | Apr 2009 | B1 |
7589742 | Street et al. | Sep 2009 | B2 |
7658672 | Wolf et al. | Feb 2010 | B1 |
7692573 | Funk | Apr 2010 | B1 |
7758411 | Crawford et al. | Jul 2010 | B2 |
8147334 | Gatto et al. | Apr 2012 | B2 |
8152643 | Halliburton et al. | Apr 2012 | B2 |
8235800 | Gingher | Aug 2012 | B2 |
8287354 | Gail et al. | Oct 2012 | B2 |
8371921 | Perrone et al. | Feb 2013 | B1 |
8414387 | Paradise et al. | Apr 2013 | B1 |
8475255 | Wolf et al. | Jul 2013 | B2 |
8512125 | Weber et al. | Aug 2013 | B2 |
8523684 | Lutnick et al. | Sep 2013 | B2 |
8589488 | Huston et al. | Nov 2013 | B2 |
8678902 | Kelly et al. | Mar 2014 | B2 |
8715077 | Paradise et al. | May 2014 | B2 |
8732780 | Kahn et al. | May 2014 | B2 |
8758106 | Wolf et al. | Jun 2014 | B2 |
8840462 | Patel et al. | Sep 2014 | B2 |
8851980 | Versaci | Oct 2014 | B2 |
8864588 | Karsten | Oct 2014 | B2 |
9155968 | Hedrick et al. | Oct 2015 | B2 |
9214058 | Kelly et al. | Dec 2015 | B2 |
9240101 | Paradise et al. | Jan 2016 | B2 |
9266017 | Parker et al. | Feb 2016 | B1 |
9300704 | Petersen et al. | Mar 2016 | B2 |
9311776 | Crowder et al. | Apr 2016 | B2 |
9317996 | Pierce et al. | Apr 2016 | B2 |
9430909 | Shore et al. | Aug 2016 | B2 |
9489793 | Williams et al. | Nov 2016 | B2 |
9524619 | Colvin et al. | Dec 2016 | B2 |
9552191 | Oram | Jan 2017 | B2 |
9569932 | Nicely et al. | Feb 2017 | B2 |
9589417 | Frenkel et al. | Mar 2017 | B2 |
9607474 | Nguyen et al. | Mar 2017 | B2 |
9649564 | Paradise et al. | May 2017 | B2 |
9711003 | Carter, Sr. | Jul 2017 | B2 |
9833699 | Rouse et al. | Dec 2017 | B2 |
10068422 | Gadher et al. | Sep 2018 | B2 |
10068425 | Colvin et al. | Sep 2018 | B2 |
10089608 | Cage et al. | Oct 2018 | B2 |
10135943 | Palandurkar | Nov 2018 | B2 |
10210705 | Frenkel et al. | Feb 2019 | B2 |
10255753 | Merati | Apr 2019 | B2 |
10290179 | Paradise et al. | May 2019 | B2 |
10510214 | Amaitis et al. | Dec 2019 | B2 |
10532283 | Parker et al. | Jan 2020 | B2 |
10614657 | Koustas et al. | Apr 2020 | B2 |
10657768 | Northrup et al. | May 2020 | B2 |
10748373 | Paradise et al. | Aug 2020 | B2 |
11017630 | Williams et al. | May 2021 | B2 |
11024131 | Simons et al. | Jun 2021 | B2 |
11551515 | Paradise et al. | Jan 2023 | B2 |
20010004509 | Hayashi | Jun 2001 | A1 |
20030087701 | Paravia et al. | May 2003 | A1 |
20030130029 | Crumby | Jul 2003 | A1 |
20040053675 | Nguyen et al. | Mar 2004 | A1 |
20040166942 | Muir | Aug 2004 | A1 |
20040167792 | Diehl et al. | Aug 2004 | A1 |
20050085290 | Schugar | Apr 2005 | A1 |
20050090307 | Walker et al. | Apr 2005 | A1 |
20050179206 | Cogert | Aug 2005 | A1 |
20050197190 | Amaitis et al. | Sep 2005 | A1 |
20050288101 | Lockton et al. | Dec 2005 | A1 |
20060030405 | Robertson | Feb 2006 | A1 |
20060040735 | Baerlocher | Feb 2006 | A1 |
20060058084 | Crawford et al. | Mar 2006 | A1 |
20060058103 | Danieli et al. | Mar 2006 | A1 |
20060068895 | Nguyen et al. | Mar 2006 | A1 |
20060082056 | Kane et al. | Apr 2006 | A1 |
20060247053 | Mattila | Nov 2006 | A1 |
20070004509 | Banton | Jan 2007 | A1 |
20070054739 | Amaitis et al. | Mar 2007 | A1 |
20070072676 | Baluja | Mar 2007 | A1 |
20070129147 | Gagner | Jun 2007 | A1 |
20070167210 | Kelly et al. | Jul 2007 | A1 |
20070191101 | Coliz et al. | Aug 2007 | A1 |
20070235939 | Ko | Oct 2007 | A1 |
20070265092 | Betteridge | Nov 2007 | A1 |
20080015013 | Gelman et al. | Jan 2008 | A1 |
20080207296 | Lutnick et al. | Aug 2008 | A1 |
20080214301 | Sandige et al. | Sep 2008 | A1 |
20090011834 | Chhabra | Jan 2009 | A1 |
20090036188 | Gelman | Feb 2009 | A1 |
20090131175 | Kelly et al. | May 2009 | A1 |
20090170608 | Herrmann et al. | Jul 2009 | A1 |
20090209350 | Kelly et al. | Aug 2009 | A1 |
20090275371 | Takahashi et al. | Nov 2009 | A1 |
20090318219 | Koustas et al. | Dec 2009 | A1 |
20100022307 | Steuer et al. | Jan 2010 | A1 |
20100121896 | Oram | May 2010 | A1 |
20100144426 | Winner et al. | Jun 2010 | A1 |
20100151938 | Boesen | Jun 2010 | A1 |
20100311496 | Taylor et al. | Dec 2010 | A1 |
20120028718 | Barclay et al. | Feb 2012 | A1 |
20120084364 | Sivavakeesar | Apr 2012 | A1 |
20120122558 | Lyons et al. | May 2012 | A1 |
20120178514 | Schulzke et al. | Jul 2012 | A1 |
20130029745 | Kelly et al. | Jan 2013 | A1 |
20130110895 | Valentino et al. | May 2013 | A1 |
20130130807 | Youm et al. | May 2013 | A1 |
20130159076 | Heisler et al. | Jun 2013 | A1 |
20140045589 | Paradise et al. | Feb 2014 | A1 |
20140074918 | Wang et al. | Mar 2014 | A1 |
20140087807 | Kearns | Mar 2014 | A1 |
20140200062 | Paradise et al. | Jul 2014 | A1 |
20140243059 | Arnone et al. | Aug 2014 | A1 |
20140342835 | Bell et al. | Nov 2014 | A1 |
20150094135 | Hedrick et al. | Apr 2015 | A1 |
20150133223 | Carter, Sr. | May 2015 | A1 |
20150375102 | George | Dec 2015 | A1 |
20160110960 | Paradise et al. | Apr 2016 | A1 |
20160168860 | Stucky et al. | Jun 2016 | A1 |
20160321864 | Burman et al. | Nov 2016 | A1 |
20170249802 | Paradise et al. | Aug 2017 | A1 |
20170263077 | Lyons et al. | Sep 2017 | A1 |
20190228612 | Pierce et al. | Jul 2019 | A1 |
20190236894 | Paradise et al. | Aug 2019 | A1 |
20200051376 | Lutnick et al. | Feb 2020 | A1 |
20210225121 | Paradise et al. | Jul 2021 | A1 |
Number | Date | Country |
---|---|---|
2464498 | Oct 2005 | CA |
1853205 | Oct 2006 | CN |
1894694 | Jan 2007 | CN |
101044520 | Sep 2007 | CN |
101090759 | Dec 2007 | CN |
101128852 | Feb 2008 | CN |
101356533 | Jan 2009 | CN |
102209105 | Oct 2011 | CN |
102497358 | Jun 2012 | CN |
103945912 | Jul 2014 | CN |
1088575 | Apr 2001 | EP |
1738810 | Jan 2007 | EP |
2001175761 | Jun 2001 | JP |
2003144745 | May 2003 | JP |
2003225460 | Aug 2003 | JP |
2006305307 | Nov 2006 | JP |
2009526603 | Jul 2009 | JP |
2010017258 | Jan 2010 | JP |
20070110544 | Nov 2007 | KR |
20110068218 | Jun 2011 | KR |
1020120005072 | Jan 2012 | KR |
20120053497 | May 2012 | KR |
1020120053497 | May 2012 | KR |
9739811 | Oct 1997 | WO |
9823340 | Jun 1998 | WO |
2004114188 | Dec 2004 | WO |
2007072019 | Jun 2007 | WO |
2010004864 | Jan 2010 | WO |
2014025971 | Feb 2014 | WO |
Entry |
---|
Age of Empires 3 System. |
Age of Empires 3 User's Manual, Microsoft Corporation, 2005, 80 pages. |
AviaGames Inc.'s Amended Invalidity Contentions, United States District Court, Northern District of California, San Jose Division,, 23 pages. |
AviaGames Inc.'s Invalidity Contentions, United States District Court, Northern District of California, San Jose Division, 29 pages. |
Civilization 5 System. |
Claim Chart, Exhibit A-1 to AviaGames Inc.'s Invalidity Contentions, 11 pages. |
Claim Chart, Exhibit A-10 to AviaGames Inc.'s Invalidity Contentions, 19 pages. |
Claim Chart, Exhibit A-11 to AviaGames Inc.'s Invalidity Contentions, 37 pages. |
Claim Chart, Exhibit A-12 to AviaGames Inc.'s Invalidity Contentions, 40 pages. |
Claim Chart, Exhibit A-13 to AviaGames Inc.'s Invalidity Contentions, 35 pages. |
Claim Chart, Exhibit A-14 to AviaGames Inc.'s Invalidity Contentions, 38 pages. |
Claim Chart, Exhibit A-15 to AviaGames Inc.'s Invalidity Contentions, 35 pages. |
Claim Chart, Exhibit A-16 to AviaGames Inc.'s Invalidity Contentions, 44 pages. |
Claim Chart, Exhibit A-2 to AviaGames Inc.'s Invalidity Contentions, 34 pages. |
Claim Chart, Exhibit A-3 lo AviaGames Inc.'s Invalidity Contentions, 38 pages. |
Claim Chart, Exhibit A-4 lo AviaGames Inc.'s Invalidity Contentions., 42 pages. |
Claim Chart, Exhibit A-5 to AviaGames Inc.'s Invalidity Contentions, 37 pages. |
Claim Chart, Exhibit A-6 lo AviaGames Inc.'s Invalidity Contentions, 33 pages. |
Claim Chart, Exhibit A-7 lo AviaGames Inc.'s Invalidity Contentions, 42 pages. |
Claim Chart, Exhibit A-8 lo AviaGames Inc.'s Invalidity Contentions, 38 pages. |
Claim Chart, Exhibit A-9 lo AviaGames Inc.'s Invalidity Contentions, 36 pages. |
Dice (Ex. 1010), The British Museum, 1 page. |
Empire Earth 2 Manual 1, 2 pages. |
Empire Earth 2 Manual 2, www.empireearth2.com, Sierra Entertainment, Inc, 2005, 2 pages. |
Empire Earth 2 System. |
Fandom Games Community, “Random Map”, Age of Empires Wiki,, 24 pages. |
Games of Chance: Gambling Devices of the Mechanical Age, 3 pages. (Ex. 1012). |
Japanese Office Action issued in Japanese Application No. 2015-526695, dated Jun. 6, 2017, 07 pages of English Translation and 07 pages of Japanese Office Action. |
King System. |
Maim Chart, Exhibit A-14B to AviaGames Inc.'s Amended Invalidity Contentions, U.S. Patent No. 2010/0022307 Steuer, 40 pages. |
Minecraft Mobile Manual, www.mobileminecraft.com, 3 pages. |
Minecraft System. |
Nevada Gaming Control Board Notice to Licensees, accessed at https://gaming.nv.gov/modules/showdocument.aspx?documentid=3450, May 24, 2012, 12 pages. |
Print; Playing-Card, the British Museum, 1 page.(Ex. 1011). |
Regular Session New Jersey Assembly Bill 2578, NJ A2578, 2013. |
Report on the Possible Regulation of Intrastate Internet Poker in the State of Iowa, Iowa Racing and Gaming Commission, Dec. 1, 2011, 168 pages. |
Technical Policies of the Nevada Gaming Control Board and Gaming Commission as They Relate to Gaming Devices and Gaming Associated Equipment, Gaming Control Board, May 24, 2012, 12 pages. |
The WBF Code of Laws for Electronic Bridge 2001 Promulgated by the World Bridge Federation, Aviagames Ex. 1032, 75 pages. |
U.S. Before the Patent Trial and Appeal Board U.S. Pat. Nos. 9,479,602 and 9,649,564, dated Feb. 15, 2022, 250 pages. (Ex. 1003, Part 3). |
U.S. Before the Patent Trial and Appeal Board U.S. Pat. Nos. 9,479,602 and 9,649,564, dated Feb. 15, 2022, 185 pages. (Ex. 1003 Part 1). |
U.S. Before the Patent Trial and Appeal Board U.S. Pat. Nos. 9,479,602 and 9,649,564, dated Feb. 15, 2022, Feb. 7, 2022, 216 pages. (Ex. 1003, Part 2). |
U.S. Before the Patent Trial and Appeal Board U.S. Pat. Nos. 9,649,564 B2, Aviagames, Inc. Petitioner v. Skillz Platform Inc., Patent Owner., Aug. 4, 2022, 42 pages. |
U.S. District Court Northern District of California San Francisco Division, case No. 5:21-cv-02436-BLF, Filed on Jan. 10, 2022, 9pages (Ex. 1017). |
U.S. District Court Northern District of California, case No. 21-cv-02436-BLF, 77 pages (Ex. 1018). |
U.S. Pat. No. 9,649,564 Claim Listing, 3 pages. (Ex 1025). |
U.S. Petition for Inter Partes Review of U.S. Pat. Nos. 9,649,564, dated Feb. 15, 2022, 91 pages. |
U.S. Utility Patent Application Transmittal (Ex. 1002), dated Feb. 15, 2022, 203 pages. |
U.S. Utility Patent Application Transmittal, dated Feb. 15, 2022, 155 pages. (EX 1021). |
U.S. Utility Patent Application Transmittal, dated Feb. 15, 2022, 176 pages. (EX 1023). |
U.S. Utility Patent Application Transmittal, dated Feb. 15, 2022, 124 pages. (EX 1019). |
Douceur et al. (2007) “Enhancing Game-Server AI with Distributed Client Computation”, 6 pages. |
Dutang et al. (Sep. 2009) “A Note on Random No. Generation”, 25 pages. |
Gainsbury et al. (2015) “The Use of Social Media in Gambling”, A report commissioned by Gambling Research Australia, 337 pages. |
Galton Francis (May 1, 1890) “Dice for Statistical Experiments”, Nature, 42:13-14 (5 pages). (Ex 1027). |
Gillett et al. (1991) “An Introduction to Engineered Software”, Software Engineering, 7 pages. |
Ke et al. (2008) “Random and pseudo-random numbers”, Network Security Protocol, 4 pages. |
king.com (Jan. 16, 2013) “Community”, retrieved from https://web.archive.org/web/20130116121352/http:/www.king.com/community/, 2 pages. |
king.com (Jan. 16, 2013) “Games”, Retrieved from https://web.archive.org/web/20130116113545/http:/about.king.com/games, 9 pages. |
king.com (Jan. 31, 2013) “Games Online”, retrieved on https://web.archive.org/web/20130131004232/http:/www.king.com/, 3 pages. |
king.com (Oct. 29, 2012) “Gin Rummy”, retrieved from https://web.archive.org/web/20121029022933/http://www.king.com/games/card-games/gin-rummy/, 1 page. |
king.com (Jan. 16, 2013) “How it Works”, retrieve from https://web.archive.org/web/20130116115853/http:/www.king.com/how_it_works.jsp, 2 pages. |
king.com (Jan. 7, 2013) “Privacy Policy”, retrieved form https://web.archive.org/web/20130107225634/http:/about.king.com/privacy, 2 pages. |
king.com (May 21, 2013) “Signup”, retrieved from https://web.archive.org/web/20130521202607/https:/www.king.com/signup.jsp, 1 page. |
Komenda Ed. (Sep. 24, 2013) “How Online Poker Companies Track Players and Verify Their Location”, Vegas Inc coverage, 4 pages. |
Korf et al. (Jul. 1996) “Best-first Minimax Search”, Artificial Intelligence, 84(1-2):299-337. |
Kruse et al. (2005) “Data Structure and Programming—C Language”, Beijing: Tsinghua University Press, 1 page. |
Marins et al. (2011) “SmartRabbit: A Mobile Exergame Using Geolocation”, SBC—Proceedings of SBGames, 10 pages. |
Neumann John V. (1951) “Various Techniques Used in Connection With Random Digits”, 36-38. (EX. 1028). |
Press et al. “Numerical Recipes in C”, The Art of Scientific Computing Second Edition, 9 pages. (EX. 1028). |
Qin et al. (2008) “Network Security Protocol [M]”, Yishuleia Database, Section 2.4, 2 pages. |
Rutter et al. (Mar. 2004) “Mobile Entertainment Users: Headline Results from an Online Survey”, 287 pages. |
Schulte, Andy (Jun. 2005) “Scenario Editor Guide for Age of Empires 3”, Age of Empires 3, cheatcodes.com, 13 pages. |
Song, Brian, “Civilization V Manual”, SID Meier's Civilization, 233 pages. |
Srinivasan et al. (Jan. 2003) “Testing Parallel Random Number Generators”, Parallel Computing, 29(1):69-94. |
Stankiewicz Matthew J. (May 1, 2013) “All In: New Jersey Bets on Online Gambling”, Law School Student Scholarship, 32 pages. |
Winands et al. (Sep. 2012) “Computer Games Workshop at ECAI 2012”, ICGA Journal, 2 pages. |
Wong et al., “Casino Tournament Strategy”, 3 pages. (EX. 1030). |
Number | Date | Country | |
---|---|---|---|
20230222867 A1 | Jul 2023 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16992618 | Aug 2020 | US |
Child | 18058424 | US | |
Parent | 16382890 | Apr 2019 | US |
Child | 16992618 | US | |
Parent | 15595794 | May 2017 | US |
Child | 16382890 | US | |
Parent | 14976569 | Dec 2015 | US |
Child | 15595794 | US | |
Parent | 14212651 | Mar 2014 | US |
Child | 14976569 | US | |
Parent | 13858581 | Apr 2013 | US |
Child | 14212651 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13569424 | Aug 2012 | US |
Child | 13858581 | US |