System for playing multiplayer games

• US 9,852,586 B2
• Filed: 09/09/2011
• Issued: 12/26/2017
• Est. Priority Date: 05/13/2011
• Status: Active Grant

• Current Assignee: Cork Group Trading Ltd.
• Original Assignee: Cork Group Trading Ltd.
• Inventors: Moshal, Martin Paul
• Primary Examiner(s): Hu, Kang
• Assistant Examiner(s): WONG, JEFFREY KEITH
• Application Number:
  US13/228,964
• Publication Number:
  US 20120289341A1
• Time in Patent Office: 2,300 Days
• Field of Search: 463 42
• CPC Class Codes: G07F 17/3276 wherein the players compete, e.g. tournament
• CPC Class Codes: G07F 17/3293 Card games, e.g. poker, canasta, black jack

Abstract

A computer system for playing multiplayer games comprises a first gaming server which runs multiple instances of a first game and to which is connected a first plurality of players, there being a minimum number of players and a maximum number of players for any instance of the first game; and a second gaming server which runs multiple instances of a second game and to which is connected a second plurality of players, there being a minimum number of players and a maximum number of players for any instance of the second game. The first gaming server is in communication with the second gaming server and through the second gaming server makes available instances of the first game for players from said second plurality of players to join. Thus, separate gaming servers can pool instances of games and players.

Claims

1. A system for playing a multiplayer zero-sum game, comprising:

a plurality of gaming servers, wherein each gaming server is able to host separate instances of the multiplayer zero-sum game that are independent of each other, and for each such instance of the multiplayer zero-sum game the host gaming server is configured to (i) generate random events that are displayable as outcomes on client computers used by players participating in the instance of the game, (ii) enable each participating player to place a wager for each turn of the game, and (iii) determine a winner for each turn of the game, and wherein the plurality of gaming servers comprises a first gaming server and a second gaming server; and

a plurality of databases, wherein each database is configured to store game information data regarding active instances of the multiplayer zero-sum game hosted by a respective gaming server, and at least one of the databases is configured to store game information data regarding active instances of the multiplayer zero-sum game hosted by multiple gaming servers, wherein the plurality of databases comprise a first database configured to store at least game information data for active instances of the multiplayer zero-sum game that are hosted on the first gaming server and a second database configured to store game information data for active instances of the multiplayer zero-sum game that are hosted on the second gaming server, and wherein the first database differs from the second database,

wherein each gaming server is configured to provide the game information data stored in its respective database to client computers of prospective players,

wherein the client computers communicate with the plurality of gaming servers by messages that conform to an application programming interface (API),

wherein the second gaming server is configured to transmit game information data regarding active instances of the multiplayer zero-sum game in the second database to the first gaming server at regular intervals, and

wherein the first gaming server is configured to consolidate the game information data regarding active instances of the multiplayer zero-sum game received from the second gaming server into the first database.

2. The system of claim 1, wherein the game information data in each database comprises one or more of the following for each instance of the multiplayer zero-sum game:

(i) a name of the instance, (ii) the identity of each player, (iii) table stakes, and (iv) available seats.

3. The system of claim 1, wherein each gaming server is configured to provide the game information data stored in its respective database in the form of lobby pages.

4. The system of claim 3, wherein the lobby pages provided by each gaming server comprise a list of active instances of the multiplayer zero-sum game hosted by that gaming server.

5. The system of claim 4, wherein the lobby pages provided by a gaming server are displayable on a client computer of a prospective player, thereby allowing the prospective player to join an instance of the multiplayer zero-sum game hosted by that gaming server.

6. The system of claim 4, wherein the lobby pages provided by at least one gaming server comprise a list of active instances of the multiplayer zero-sum game hosted by multiple gaming servers.

7. The system of claim 6, wherein the lobby pages provided by the at least one gaming server are displayable on a client computer of a prospective player, thereby allowing the prospective player to join an instance of the multiplayer zero-sum game hosted by any of the multiple gaming servers.

8. The system of claim 1, wherein the first gaming server is configured with a login process configured to authenticate a remote player prior to joining an instance of the multiplayer zero-sum game hosted by the first gaming server, wherein the remote player is hosted on a gaming server of the plurality of gaming servers other than the first server.

9. The system of claim 1, wherein the first gaming server is configured to provide the game information data stored in the first database in the form of lobby pages.

10. The system of claim 9, wherein the lobby pages provided by the first gaming server are displayable on a client computer of a prospective player to list active instances of the multiplayer zero-sum game that are hosted by the first gaming server and active instances of the multiplayer zero-sum game that are hosted by the second gaming server, thereby allowing the prospective player to join an instance of the multiplayer zero-sum game that is hosted by either of the first and second gaming servers.

11. The system of claim 1, wherein the first gaming server is configured to transmit game information data regarding active instances of the multiplayer zero-sum game in the first database to the second gaming server at regular intervals, and wherein the second gaming server is configured to consolidate the game information data regarding active instances of the multiplayer zero-sum game received from the first gaming server into the second database.

12. The system of claim 11, wherein the second gaming server is configured to provide the game information data stored in the second database in the form of lobby pages.

13. The system of claim 12, wherein the lobby pages provided by the second gaming server are displayable on a client computer of a prospective player to list active instances of the multiplayer zero-sum game that are hosted by the first gaming server and active instances of the multiplayer zero-sum game that are hosted by the second gaming server, thereby allowing the prospective player to join an instance of the multiplayer zero-sum game that is hosted by either of the first and second gaming servers.

14. The system of claim 1, wherein the first and second gaming servers are operated by separate, competing entities.

15. The system of claim 1, further comprising:

an application server in communication with the first and second gaming servers, wherein for each turn of a game hosted by one of the first and second gaming servers that pools together players associated with both the first and second gaming servers the application server is configured to update separate clearing accounts for the first and second gaming servers.

16. The system of claim 15, wherein the hosting gaming server is configured to notify the application server of the outcome of each turn of the game, including winnings and losses of participating players and data representative of the gaming server through which each player was logged in;

and

the application server is configured to responsively (i) debit the clearing account of the gaming server associated with each player who has wagered on the turn of the game by the total amount wagered by that player, (ii) credit the clearing account of the gaming server associated with each winning player by the amount of the pot less any rake amount, and (iii) credit a portion of any rake amount to the clearing accounts of the first and second gaming servers in proportion to the total number of players that participated in the turn of the game while logged in to that particular gaming server.

17. The system of claim 16, wherein each of the first and second gaming servers maintains a credit account for each participating player associated with that gaming server.

18. The system of claim 1, wherein at least the second gaming server is accessible through a plurality of portals.

19. The system of claim 18, wherein the portals are poker room websites.

20. The system of claim 18, wherein the portals are separately operated by competing entities.

21. The system of claim 18, wherein each portal can be logically connected to a plurality of client computers simultaneously.

22. The system of claim 18, further comprising:

an application server in communication with the first and second gaming servers, wherein for each turn of a game hosted by one of the first and second gaming servers that pools together players associated with the first gaming server and the plurality of portals the application server is configured to update separate clearing accounts for the first gaming server and for each of the portals.

23. The system of claim 22, wherein the hosting gaming server is configured to notify the application server of the outcome of each turn of the game, including winnings and losses of participating players and data representative of the gaming server and/or portal through which each player accessed the game;

and

the application server is configured to responsively (i) debit the clearing account of the gaming server or portal associated with each player who has wagered on the turn of the game by the total amount wagered by that player, (ii) credit the clearing account of the gaming server or portal associated with each winning player by the amount of the pot less any rake amount, and (iii) credit a portion of any rake amount to the clearing account of the first gaming server in proportion to the total number of players that participated in the turn of the game through the first gaming server and to the clearing account of each portal in proportion to the total number of players that participated in the turn of the game through that portal.

24. The system of claim 23, wherein the first gaming server includes a credit account for each player participating in the game through the first gaming server and each portal includes a credit account for each player participating in the game through that portal.

25. The system of claim 1, wherein the first gaming server is accessible through a first plurality of portals and the second gaming server is accessible through a second plurality of portals.

26. The system of claim 25, further comprising:

an application server in communication with the first and second gaming servers, wherein for each turn of a game hosted by one of the first and second gaming servers that pools together players associated with the first plurality of portals and the second plurality of portals the application server is configured to update separate clearing accounts for each of the portals.

27. The system of claim 26, wherein the hosting gaming server is configured to notify the application server of the outcome of each turn of the game, including winnings and losses of participating players and data representative of the portal through which each player accessed the game;

and

the application server is configured to responsively (i) debit the clearing account of the portal associated with each player who has wagered on the turn of the game by the total amount wagered by that player, (ii) credit the clearing account of the portal associated with each winning player by the amount of the pot less any rake amount, and (iii) credit a portion of any rake amount to the clearing account of each portal in proportion to the total number of players that participated in the turn of the game through that portal.

28. The system of claim 27, wherein each portal includes a credit account for each player participating in the game through that portal.

29. The system of claim 1, wherein the multiplayer zero-sum game is a multiplayer poker game.

30. A method comprising:

a client computer receiving from a local gaming server a list of active instances of a multiplayer zero-sum game, wherein the list includes active game instances hosted by the local gaming server and active game instances hosted by a remote gaming server, wherein the client computer communicate at least with the remote gaming server by messages that conform to an application programming interface (API), wherein the active game instances hosted by the local gaming server are independent of each other, wherein the active game instances hosted by the remote gaming server are independent of each other, wherein the active game instances hosted by the local gaming server differ from and are independent of the active game instances hosted by the remote gaming server, wherein the remote gaming server is configured to transmit game information data for the active game instances hosted by the remote gaming server to the local gaming server at regular intervals, and wherein the local gaming server is configured to consolidate the game information data for the active game instances received from the remote gaming server into a database configured to store game information data for the active game instances hosted by the local gaming server;

the client computer displaying the list to a player; and

the client computer receiving from the player a selection of an active game instance on the list.

31. The method of claim 30, wherein the selected game instance is hosted by the local gaming server, further comprising:

when the player participates in the selected game instance hosted by the local gaming server, the client computer communicating natively with the local gaming server.

32. The method of claim 30, wherein the selected game instance is hosted by the remote gaming server, further comprising:

when the player participates in the selected game instance hosted by the remote gaming server, the client computer communicating with the remote gaming server by means of an application programming interface (API).

33. The method of claim 30, wherein the local and remote gaming servers are operated by separate, competing entities.

34. The method of claim 30, wherein the multiplayer zero-sum game is a multiplayer poker game.

35. A method for settlement of player wagers, comprising:

a host gaming server hosting a multiplayer zero-sum game involving a plurality of players associated with a plurality of gaming entities, the plurality of players including one or more players using client computers that communicate natively with the host gaming server and one or more players using client computers that communicate with the host gaming server by means of an application programming interface (API), wherein each player is associated with a respective gaming entity with which the player has a credit account, and wherein each gaming entity has a respective clearing account, the host gaming server comprising a database configured to store game information data for active instances of the multiplayer zero-sum game hosted on the host gaming server and for active instances of the multiplayer zero-sum game hosted on a remote gaming server, wherein the active game instances hosted by the local gaming server are independent of each other, wherein the active game instances hosted by the remote gaming server are independent of each other, wherein the active game instances hosted by the local gaming server are independent of the active game instances hosted by the remote gaming server, and wherein the game information data for the active instances of the multiplayer zero-sum game hosted on the host gaming server differs from the game information data for active instances of the multiplayer zero-sum game hosted on the remote gaming server,

the host gaming server receiving, from the remote gaming server, the game information data for the active instances of the multiplayer zero-sum game hosted by the remote gaming server at regular intervals;

the host gaming server consolidating the game information data received from the remote gaming server into the database configured to store the game information data for the active game instances hosted by the host gaming server;

the host gaming server notifying an application server of an outcome of a turn of the game, including losses and winnings of the players participating in the turn, together with data representative of each gaming entity associated with each participating player;

the application server debiting the clearing account of each gaming entity associated with each player that has wagered on the turn of the game by the total amount wagered by that player;

the application server crediting the clearing account of each gaming entity associated with each winning player by the amount of the pot less a rake amount; and

the application server crediting a portion of the rake amount to the clearing account of each gaming entity in proportion to the number of participating players associated with that gaming entity.

36. The method of claim 35, wherein the plurality of gaming entities includes at least one gaming server other than the host gaming server.

37. The method of claim 35, wherein the plurality of gaming entities includes a plurality of portals.

38. The method of claim 35, further comprising:

the host gaming server debiting the credit account of each player that has wagered on the turn of the game by the total amount wagered by that player; and

the host gaming server crediting the credit account of each winning player by the amount of the pot less the rake amount.

39. The method of claim 35, wherein the multiplayer zero-sum game is a multiplayer poker game.