System for playing multiplayer games

• US 8,956,220 B2
• Filed: 08/07/2012
• Issued: 02/17/2015
• Est. Priority Date: 06/29/2012
• Status: Active Grant

• Current Assignee: Fusion Holdings Limited
• Original Assignee: Pridefield Limited
• Inventors: Melton, Lydia Catherine
• Primary Examiner(s): Shah, Milap
• Assistant Examiner(s): PINHEIRO, JASON PAUL
• Application Number:
  US13/568,474
• Publication Number:
  US 20140004926A1
• Time in Patent Office: 924 Days
• Field of Search: 463/25
• US Class Current: 463/25
• 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 gaming server hosts a turn of a zero-sum game played by a plurality of players via a plurality of websites, each of the websites having a respective clearing account. The application server determines for each player a respective player value contribution based on the wagering activity of the player during the turn and a respective player value indicator associated with the player. The application server determines a total player value contribution based on the player value contributions of all of the players who played during the turn. The application server determines for each player a respective rake allocation based on the player value contribution of the player and the total player contribution. The application server credits each website'"'"'s clearing account based on the respective rake allocation of each player who used the website to play the game during the turn.

Claims

1. A method, comprising:

a gaming server hosting a turn of a zero-sum game played by a plurality of players via a plurality of websites, each of the websites having a respective clearing account;

an application server receiving from the gaming server information regarding the turn of the game, wherein the information indicates for each player (i) the wagering activity of the player during the turn, (ii) any winnings by the player during the turn, and (iii) the website used by the player to play the game during the turn;

the application server determining for each player a respective player value contribution, wherein determining a player value contribution for a player comprises multiplying a called amount that is based on the wagering activity of the player during the turn by a respective player value indicator associated with the player;

the application server determining a total player value contribution based on the player value contributions of all of the players who played during the turn;

the application server determining for each player a respective rake allocation, wherein determining a rake allocation for a player comprises determining the rake allocation based on the player value contribution of the player and the total player contribution; and

the application server crediting each website'"'"'s clearing account based on the respective rake allocation of each player who used the website to play the game during the turn.

2. The method of claim 1, further comprising:

the application server maintaining a playing history log, wherein the playing history log includes data representative of wagers and winnings of players who used any of the plurality of websites to play the zero-sum game during a predetermined time interval.

3. The method of claim 2, wherein the application determines net loss percentile rankings, break-even percentile rankings, and newness indicators for players based on the data in the playing history log.

4. The method of claim 2, further comprising:

the application server determining a secondary rake allocation for a player based on data in the playing history log relating to the player'"'"'s playing history during the predetermined time interval.

5. The method of claim 4, further comprising:

determining a player reward for the player based on the player'"'"'s secondary rake allocation.

6. The method of claim 2, further comprising:

the application server determining a tertiary rake allocation for an entity based on data in the playing history log relating to use of one or more websites affiliated with the entity during the predetermined time period.

7. The method of claim 6, further comprising:

determining a remuneration of the entity based on the entity'"'"'s tertiary rake allocation.

8. The method of claim 1, further comprising:

the application server determining the respective player value indicator of each player, wherein a player value indicator for a player is determined based on a net loss percentile ranking for the player, a break-even percentile ranking for the player, and a newness indicator for the player.

9. The method of claim 8, wherein a player value indicator for a player is calculated as a weighted average of the player'"'"'s net loss percentile ranking, the player'"'"'s break-even percentile ranking, and the player'"'"'s newness indicator.

10. The method of claim 1, wherein determining the called amount comprises determining an amount that was wagered by the player and called by another player during the turn.

11. The method of claim 1, wherein the application server determines the total player value contribution as a sum of the player value contributions of all of the players who played during the turn.

12. The method of claim 1, further comprising:

the application server determining a rake associated with the turn.

13. The method of claim 10, wherein determining a rake allocation for a player further comprises (i) determining a ratio of the player'"'"'s player value contribution to the total player contribution and (ii) obtaining the rake allocation for the player by multiplying the rake by the ratio.

14. A system, comprising:

a gaming server, wherein the gaming server is configured to host a turn of a zero-sum game in which a plurality of players participate via a plurality of websites, each website having a respective clearing account; and

an application server in communication with the gaming server, wherein the application server is configured to determine a respective rake allocation for each player and credit each website'"'"'s clearing account based on the respective rake allocation of each player who used the website to play the game during the turn, wherein determining a rake allocation for a player comprises (i) determining a player value contribution for the player based on a product of a called amount that is based on wagering activity by the player during the turn by a player value indicator associated with the player and (ii) determining the player'"'"'s rake allocation based on the player'"'"'s player value contribution.

15. The system of claim 14, wherein the called amount comprises an amount that was wagered by the player and called by another player during the turn.

16. The system of claim 14, wherein the application server is further configured to determine a total player value contribution based on the player value contributions of all of the players who played during the turn.

17. The system of claim 16, wherein determining the player'"'"'s rake allocation based on the player'"'"'s player value contribution comprises (i) determining a ratio of the player'"'"'s player value contribution to the total player value contribution and (ii) obtaining the player'"'"'s rake allocation by multiplying a rake associated with the turn by the ratio.

18. The system of claim 14, wherein the application server is further configured to determine a player value indicator for a player based on a net loss percentile ranking for the player, a break-even percentile ranking for the player, and a newness indicator for the player.

19. The system of claim 14, wherein the application server is further configured to determine a rake associated with the turn of the game.

20. The system of claim 14, wherein the application server is further configured to maintain a playing history log, wherein the playing history log includes data representative of wagers and winnings of players who used any of the plurality of websites to play the zero-sum game during a predetermined time interval.

21. The system of claim 20, wherein the application server is further configured to determine a secondary rake allocation for a player based on data in the playing history log relating to the player'"'"'s playing history during the predetermined time interval.

22. The system of claim 21, wherein the application server is further configured to determine a tertiary rake allocation for an entity based on data in the playing history log relating to use of one or more websites affiliated with the entity during the predetermined time interval.