# US 2014/0194199 A1 · Collusion detection

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0194199 A1
- Document ID: US20140194199A1
- Status: Published application
- Kind: A1
- Application number: 14/149,192
- Filed: 2014-01-07
- Published: 2014-07-10
- Earliest claimed: 2013-01-07
- Assignees: Cfph, LLC
- Applicants: Cfph, LLC
- Inventors: Joe DiGiovanni
- Web page: https://patentgrep.com/patent/US20140194199A1

## CPC

- G07F 17/3239: {Tracking of individual players}
- G07F 17/3241: {Security aspects of a gaming system, e.g. detecting cheating, device integrity, surveillance (computer security G06F21/00)}
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})

## Abstract

Various embodiments that may generally relate to collusion are described. Collusion detection may be used to prevent players in a wagering environment from violating the integrity of a game. Player actions may be tracked to develop a wagering profile that is specific to various game situations. A player acting in a manner that would be against their interest and against their defined profile may be considered a colluding action. Information about collusion actions may be presented for evaluation and/or anti-collusion actions may be automatically taken in response to such collusion actions being determined.

## Claims

### Claim 1

A method comprising:
monitoring, by a computing device, play of a player in a plurality of games;
generating, by the computing device, profile data for the player based on the monitored play;
determining, by the computing device, that an action by the player in a second game results in a collusive outcome;
in response to determining that the action by the player results in the collusive outcome, determining, by the computing device, that the action deviates from the profile data; and
in response to determining that the action deviates from the profile data, taking, by the computing device, a collusion prevention action.

### Claim 2 (depends on 1)

The method of claim 1, in which determining that the action deviates from the profile data includes determining a probability that the action is not in line with historical play of the player by comparing the action to the profile data.

### Claim 3 (depends on 1)

The method of claim 1, in which the collusive outcome includes a transfer of a large amount of chips from the player to another player in the second game.

### Claim 4 (depends on 1)

The method of claim 1, in which determining that the action results in the collusive outcome includes determining a severity of collusion based on the collusive outcome and in which the determination that that action deviates from the profile data is adjusted to account for the severity so that a higher deviation is required to make the determination for a lower severity and a lower deviation is required to make the determination for a higher severity.

### Claim 5 (depends on 1)

The method of claim 1, comprising determining a likelihood of collusion and presenting the likelihood to a collusion detector.

### Claim 6 (depends on 5)

The method of claim 5, comprising determining a high likelihood of collusion in response to determining that the collusive outcome is a highly severe collusion and deviation from the profile data is great.

### Claim 7 (depends on 5)

The method of claim 5, comprising determining a low likelihood of collusion in response to determining either a) that the collusive outcome is not severe or b) that deviation from the profile data is not great.

### Claim 8 (depends on 1)

The method of claim 1, comprising determining an ongoing collusion rating for the player over the plurality of games based on a percentage of possible collusive actions detected over those games and present that collusion rating to a collusion detector.

### Claim 9 (depends on 1)

The method of claim 1, in which the collusion prevention action includes presenting information to a collusion detector through a user interface that allows the collusion detector to perform at least one of undue a result of the second game, ban the player from gameplay, halt gameplay by the second player, and cause a replay of the second game.

### Claim 10 (depends on 9)

The method of claim 9, comprising recording history of the second game, and in which the user interface allows the collusion detector to access recorded game history of the second game.

### Claim 11 (depends on 10)

The method of claim 10, in which the user interface is configured to allow the collusion detector to access recorded game history in context of the game.

### Claim 12 (depends on 10)

The method of claim 10, in which the game history allows the collusion detector to recreate the second game.

### Claim 13 (depends on 1)

The method of claim 1, comprising storing the profile data in a vector, in which each dimension of the vector represents a determined behavior of the player.

### Claim 14 (depends on 13)

The method of claim 13, in which one dimension of the vector includes a tightness of play dimension determined by a small blind completion percentage in poker games.

### Claim 15 (depends on 13)

The method of claim 13, in which one dimension of the vector includes an aggression dimension determined by a bet and raise percentage post flop compared to a call percentage post flop in Texas hold'em games.

### Claim 16 (depends on 13)

The method of claim 13, in which dimensions of the vector are situationally-generic dimensions.

### Claim 17 (depends on 13)

The method of claim 13, in which dimensions of the vector are specific to a context in which behavior is observed.

### Claim 18 (depends on 17)

The method of claim 17, in which a context for a dimension of the vector is defined by at least one of a hole card strength and a hand strength of the player in the context.

### Claim 19 (depends on 13)

The method of claim 13, comprising estimating a dimension for the vector when there is not sufficient information for the dimension by referencing one or more other dimensions in the vector.

### Claim 20 (depends on 13)

The method of claim 13, comprising determining a dimension of the vector by weighting data so that more recent games are given more weight than less recent games for the dimension.

### Claim 21 (depends on 1)

The method of claim 1, comprising generating the profile data to identify historical actions taken in each of a plurality of gaming situations.

### Claim 22 (depends on 1)

The method of claim 1, comprising generating the profile data to identify historical actions taken against each of a plurality of types of players.

### Claim 23 (depends on 1)

The method of claim 1, in which monitoring play of the player includes operating an electronic platform through which the player may play the plurality of games against a plurality of other players and determining actions in those games taken through the electronic platform.

### Claim 24

An apparatus comprising:
a computing device; and
a non-transitory medium having stored thereon a plurality of instruction that when executed by the computing device cause the apparatus to:
monitor play of a player in a plurality of games;
generate by the computing device, profile data for the player based on the monitored play;
determine that an action by the player in a second game results in a collusive outcome;
in response to determining that the action by the player results in the collusive outcome, determine that the action deviates from the profile data; and
in response to determining that the action deviates from the profile data, take a collusion prevention action.