User matching based on active game time

A method, a computer program product, and a computer system match players in a turn based game based on player activity. The method includes determining first characteristics of a first player activity of a first player. The characteristics are indicative of first active times that the first player historically took turns while playing the turn based game. The method includes identifying a second player having second characteristics of a second player activity. The second characteristics are indicative of second active times that the second player historically took turns while playing the turn based game. The second active times are compatible with the first active times. The method includes generating an indication for a game server hosting the turn based game to match the second player with the first player.

BACKGROUND

The exemplary embodiments relate generally to turn based games, and more particularly to matching a first player with a second player to play in a turn based game with one another based on player activity.

An electronic game may be played by one or more players. For multiplayer games, a game server may host the game via a network where a plurality of players may log into the game server to play the game against one another. There may be a variety of ways for players to match with another player to play the game. For example, a first player may specifically identify a second player for which a game is to be played. The second player may accept the game invitation for the game to be played against manually identified players. In another example, a first player may select to play the game and the game server may select a second player for which the game is to be played. The game server may select from a pool of currently available players (e.g., those who have logged into the game server). There are also a variety of types of games that the players may engage. For example, the game server may host a game where each player playing the game performs actions in a concurrent manner (e.g., a real time strategy game). In another example, the game server may host a turn based game where each player playing the game performs actions in turns where a first player performs actions during the first player's turn and a second player performs actions during the second player's turn. This process may repeat where each player takes a turn in a round robin fashion until the game ends. In this manner, a first player takes a turn, waits for a second player to complete a turn, and the first player may then take a following turn (e.g., a starting player takes odd numbered turns and the other player takes even numbered turns).

When two players are matched by the game server for a turn based game, there may be instances with significant time lags due to one of the players taking a substantial amount of time to complete a turn. For example, a first player may complete a first turn and the second player may complete a second turn at a second, later time. However, the first player may perform turns at a relatively slow rate (e.g., only logging into the game server to complete turns during one stretch of time during a day). For example, after completing the first turn, the first player may have logged out of the game server and not log back into the game server to perform the third turn until a much later time. The second player must therefore wait until the first player has completed the third turn before the second player may take the fourth turn. When the second player is more active and performs turns in a relatively faster rate (e.g., staying logged into the game server to perform a turn throughout the day), the second player is forced to wait for the less active first player in each round of turns. This may result in the second player losing interest in the game and may also result in the second player being less inclined to suggest the game to others which may lead to reduction in available players as new players may decrease or existing players may leave.

SUMMARY

The exemplary embodiments disclose a method, a computer program product, and a computer system for matching players in a turn based game based on player activity. The method comprises determining first characteristics of a first player activity of a first player. The characteristics are indicative of first active times that the first player historically took turns while playing the turn based game. The method comprises identifying a second player having second characteristics of a second player activity. The second characteristics are indicative of second active times that the second player historically took turns while playing the turn based game. The second active times are compatible with the first active times. The method comprises generating an indication for a game server hosting the turn based game to match the second player with the first player.

The drawings are not necessarily to scale. The drawings are merely schematic representations, not intended to portray specific parameters of the exemplary embodiments. The drawings are intended to depict only typical exemplary embodiments. In the drawings, like numbering represents like elements.

DETAILED DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Detailed embodiments of the claimed structures and methods are disclosed herein; however, it can be understood that the disclosed embodiments are merely illustrative of the claimed structures and methods that may be embodied in various forms. The exemplary embodiments are only illustrative and may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope to be covered by the exemplary embodiments to those skilled in the art. In the description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments.

In the interest of not obscuring the presentation of the exemplary embodiments, in the following detailed description, some processing steps or operations that are known in the art may have been combined together for presentation and for illustration purposes and in some instances may have not been described in detail. In other instances, some processing steps or operations that are known in the art may not be described at all. It should be understood that the following description is focused on the distinctive features or elements according to the various exemplary embodiments.

The exemplary embodiments are directed to a method, computer program product, and system for matching players in a turn based game based on player activity where players who are matched exhibit similar playing habits. As will be described in greater detail herein, the exemplary embodiments are configured to monitor a player as the player plays the turn based game. In monitoring the player, the exemplary embodiments may track the player activity of the player including when and how often turns are played over a period of time. The exemplary embodiments provide a mechanism to generate a player profile that dynamically updates the player activity for each player. When the exemplary embodiments are to match a first player and a second player to play the turn based game, the exemplary embodiments may utilize the player profiles to minimize time lags experienced by the players where the player activity and/or playing habits complement one another. Key benefits of the exemplary embodiments may include an alternative matching scheme in matching players for a turn based game for the game to proceed with only anticipated time lags based on the compatible player activities of the players. Detailed implementation of the exemplary embodiments follows.

Conventional approaches to matching players for a game may involve a variety of factors but may not incorporate whether two players have complementing or compatible schedules to play the game. Initially, conventional approaches are not directed to matching players in a turn based game but for concurrent play. Accordingly, matching schemes directed toward real time strategy games may not utilize proper considerations to match players in a turn based game. Even if these matching schemes were to be used for turn based games, such conventional approaches may not provide the features that the exemplary embodiments offer. For example, a conventional approach may match players based on characteristics of the players including language preference, availability of space in groups, playing style, etc. However, such a conventional approach does not incorporate activity level in the past or present with particular emphasis on turn based games to ensure turns are taken by both players during times when the players are not actively waiting. In another example, a conventional approach may match players based on a range of attributes such as age and gender. The conventional approach may also provide a wait time to users to find a matching player and may refer to historical data to determine the wait time. However, the historical data does not describe a player activity indicative of when players are actively playing a game, particularly for turn based games. In a further example, a conventional approach may match players based on interactions within a scope of the game to form compatible teams. The conventional approach may also optimize based on a user's interest in the game. However, this conventional approach does not describe matching players based on player activity.

In contrast to conventional approaches, the exemplary embodiments may improve a user experience for players engaged in a turned based game by optimization of player matchmaking by creating a gaming experience whereby all players involved have highly compatible and complementary play-sessions. Those skilled in the art will appreciate that matching players in a turn based game may result in significant time lags, even if the players were to have similar active periods. Having similar active periods does not ensure that the players will play the game or take turns in a manner that allows for more optimized game play. In this manner, the exemplary embodiments match players based on historical data of player activity that is indicative of schedules that the players are expected to follow in being active in the game to take turns.

The exemplary embodiments are described with regard to matching players in a turn based game. However, the use of turn based games is only exemplary. The exemplary embodiments may be utilized and/or modified to match a plurality of users to a common endeavour. For example, a project may require a plurality of participants where the project requires input from multiple users in a round robin manner (e.g., building on the project from previous contributions). The exemplary embodiments may refer to activity levels of a pool of participants to identify which participants would be optimal for inclusion in the project. The exemplary embodiments are also described with regard to the turn based game being played between two players. However, the exemplary embodiments may be modified or extended to apply to turn based games involving more than two players.

FIG. 1depicts a gaming system100, in accordance with the exemplary embodiments. According to the exemplary embodiments, the gaming system100may include one or more smart devices110, a game server120, one or more profile repositories130, and a matching server140, which may all be interconnected via a network108. While programming and data of the exemplary embodiments may be stored and accessed remotely across several servers via the network108, programming and data of the exemplary embodiments may alternatively or additionally be stored locally on as few as one physical computing device or amongst other computing devices than those depicted.

In the exemplary embodiments, the network108may be a communication channel capable of transferring data between connected devices. Accordingly, the components of the gaming system100may represent network components or network devices interconnected via the network108. In the exemplary embodiments, the network108may be the Internet, representing a worldwide collection of networks and gateways to support communications between devices connected to the Internet. Moreover, the network108may utilize various types of connections such as wired, wireless, fiber optic, etc. which may be implemented as an intranet network, a local area network (LAN), a wide area network (WAN), or a combination thereof. In further embodiments, the network108may be a Bluetooth network, a WiFi network, or a combination thereof. In yet further embodiments, the network108may be a telecommunications network used to facilitate telephone calls between two or more parties comprising a landline network, a wireless network, a closed network, a satellite network, or a combination thereof. In general, the network108may represent any combination of connections and protocols that will support communications between connected devices. For example, the network108may also represent direct or indirect wired or wireless connections between the components of the gaming system100that do not utilize the network108.

In the exemplary embodiments, the smart device110may include a game client112and may be an enterprise server, a laptop computer, a notebook, a tablet computer, a netbook computer, a personal computer (PC), a desktop computer, a server, a personal digital assistant (PDA), a rotary phone, a touchtone phone, a smart phone, a mobile phone, a virtual device, a thin client, an Internet of Things (IoT) device, a console, or any other electronic device or computing system capable of receiving and sending data to and from other computing devices. While the smart device110is shown as a single device, in other embodiments, the smart device110may be comprised of a cluster or plurality of computing devices, in a modular manner, etc., working together or working independently. The smart device110is described in greater detail as a hardware implementation with reference toFIG. 4, as part of a cloud implementation with reference toFIG. 5, and/or as utilizing functional abstraction layers for processing with reference toFIG. 6.

In the exemplary embodiments, the game client112may act as a client in a client-server relationship and may be a software, hardware, and/or firmware based application capable of allowing a player to match with another player to play a turn based game via the network108. In embodiments, the game client112may operate as a user interface allowing the player to enter inputs associated with actions taken in the turn based game as well as interact with one or more components of the gaming system100, and utilize various wired and/or wireless connection protocols for data transmission and exchange associated with matching players in a turn based game, including Bluetooth, 2.4 gHz and 5 gHz Internet, near-field communication, Z-Wave, Zigbee, etc.

The player may utilize the game client112to log into the game server120and play the turn based game. The player may have an account linked to the game server120that identifies the player. For example, the account may include a user name and/or a password. Once logged into the game server120, the player may perform a plurality of options. For example, the player may create a new game, may continue an ongoing game, may update settings, etc.

The smart device110may be equipped with a variety of input devices (e.g., a keyboard, a mouse, a gaming controller, a voice input device, etc.) through which the player may enter inputs for the game to perform corresponding actions. The game client112may be implemented in a variety of ways for the player to play the turn based game with another player. For example, the game client112may run the turn based game locally with the smart device110being a console. Through data exchanged with the game server120, the player may enter inputs that are reflected in the game and shown in a corresponding manner. The inputs entered by player may be transmitted to the game server120to show the same actions on an interface of the game for the other player. The other player may also enter inputs that are reflected in the game of the other player as well as being transmitted to the game server120such that the same actions are shown on the interface of the game for the player. In this manner, the turn based game may be run locally on two smart devices110for the two players in the game. In another example, the turn based game may be run remotely via the game server120such as when the game client112is run via a browser. In this manner, inputs entered by players may be transmitted to the game server120which processes the inputs and updates the game where corresponding changes to the game are transmitted to the game clients112and shown via the interface.

In the exemplary embodiments, the game server120may include a game platform122and act as a server in a client-server relationship with the game client112and may be a software, hardware, and/or firmware based application capable of hosting a turn based game for players to play with one another via the network108. The game server120may be an enterprise server, a laptop computer, a notebook, a tablet computer, a netbook computer, a PC, a desktop computer, a server, a PDA, a rotary phone, a touchtone phone, a smart phone, a mobile phone, a virtual device, a thin client, an IoT device, or any other electronic device or computing system capable of receiving and sending data to and from other computing devices. While the game server120is shown as a single device, in other embodiments, the game server120may be comprised of a cluster or plurality of computing devices, working together or working independently. While the game server120is also shown as a separate component, in other embodiments, the operations and features of the game server120may be incorporated with one or more of the other components of the gaming system100. For example, relative to the perspective of the player and the smart device110, the turn based game may be hosted remotely on the game server120or locally on the smart device110via the game client112. The game server120is described in greater detail as a hardware implementation with reference toFIG. 4, as part of a cloud implementation with reference toFIG. 5, and/or as utilizing functional abstraction layers for processing with reference toFIG. 6.

In the exemplary embodiments, the game platform122may host the turn based game that is played by two players. The turn based game may be any genre of game in which a first one of the players takes a turn by performing one or more actions, then a second one of the players takes a turn by performing one or more actions, and the process repeats until the game ends. For example, the turn based game hosted by the game platform122may be a board game (e.g., chess, checkers, Reversi, Go, etc.), a turn based tactical game (e.g., a battle simulator), etc.

The game platform122may perform operations such that the turn based game is played between the two players. For example, when the turn based game is hosted by the game platform122, the game platform122may receive inputs from the players, process the inputs, and transmit an update to the game to the game clients112. In another example, when the turn based game is hosted locally on the smart device110, the game platform122may receive inputs from one of players and transmit an update to be reflected on the other players interface.

The game server120may utilize an account repository (not shown) which may be remote or local to the game server120. The account repository may indicate current players who are playing the game, players available to play the game (e.g., logged into the game server), seeking to start or continue a game, etc. In creating a game, the game server120may receive a manual indication from one of the players of an identity of a desired player for which the game is to be played. When the desired player is available, the game server120may create the game to be played between the identified players. The game server120may also receive a manual indication of a desire to play the game. In such an option, the game server120may select a currently available player and create the game to be played between matched players. As will be described in further detail below, when the game server120is to select a player to be matched with another player, the game server120may receive an indication of an identity of an available player from the matching server140.

The game server120may also store a most recent update to the game while the game is ongoing (e.g., prior to the game ending). Accordingly, the players may continue a game that has started until a conclusion. The game server120may be configured to store the most recent update to the game for a predetermined amount of time. For example, a first player may take a turn and wait for the second player to perform a turn. When the first player's turn has ended, the game server120may start a timer. If the timer reaches the predetermined amount of time without the second player performing the turn, the game server120may award victory to the first player. The predetermined amount of time may be dynamic, particularly in view of the player activity information that the players may exhibit which forms the basis for the matching.

In the exemplary embodiments, the profile repository130may include one or more player profiles132and may be an enterprise server, a laptop computer, a notebook, a tablet computer, a netbook computer, a PC, a desktop computer, a server, a PDA, a rotary phone, a touchtone phone, a smart phone, a mobile phone, a virtual device, a thin client, an IoT device, or any other electronic device or computing system capable of storing, receiving, and sending data to and from other computing devices. While the profile repository130is shown as a single device, in other embodiments, the profile repository130may be comprised of a cluster or plurality of electronic devices, in a modular manner, etc., working together or working independently. While the profile repository130is also shown as a separate component, in other embodiments, the profile repository130may be incorporated with one or more of the other components of the gaming system100. For example, the profile repository130may be incorporated in the matching server140. Thus, access to the profile repository130by the matching server140may be performed locally. In another example, the player profiles132represented in the profile repository130may be incorporated in respective ones of the smart device110(e.g., each smart device110has a profile repository130including at least the player profile132of the player who is respectively associated). Thus, access to the profile repository130and to a specific one of the player profiles132may be performed through a transmission from the smart device110. The profile repository130is described in greater detail as a hardware implementation with reference toFIG. 4, as part of a cloud implementation with reference toFIG. 5, and/or as utilizing functional abstraction layers for processing with reference toFIG. 6.

In the exemplary embodiments, the player profiles132may each be associated with a respective player who plays the turn based game (e.g., has an account with the game server120). The player profiles132may be populated with various types of information that may be used by the matching server140to match one player with another player to play the turn based game. Specifically, the player profiles132may include information directed toward a player activity. For example, the player profiles132may indicate historical playing activity information. The historical playing activity information may include when the player logs into and out of the game server120, periods during which the player is actively playing one or more games, a number of turns taken during a course of a defined time duration (e.g., during the period the player is active, for a given one or more login sessions, during a set timeframe, over a total number of games, over a total number of abandoned games due to the other player not taking a turn in due time, etc.), a number of games started during a course of a defined time duration, etc. The player profiles132may be updated (e.g., by the matching server140) so that the historical playing activity information is kept up to date. For example, the player profiles132may be updated dynamically such that each parameter of the historical playing activity information is updated when a corresponding event has occurred. In another example, the player profiles132may be updated at predetermined time intervals (e.g., every set number of hours) or at predetermined event intervals (e.g., every session from login until logout).

In the exemplary embodiments, the matching server140may include an analysis program142and a matching program144and act as a server in a client-server relationship with the game platform122as well as be in a communicative relationship with the profile repository130. The matching server140may be an enterprise server, a laptop computer, a notebook, a tablet computer, a netbook computer, a PC, a desktop computer, a server, a PDA, a rotary phone, a touchtone phone, a smart phone, a mobile phone, a virtual device, a thin client, an IoT device, or any other electronic device or computing system capable of receiving and sending data to and from other computing devices. While the matching server140is shown as a single device, in other embodiments, the matching server140may be comprised of a cluster or plurality of computing devices, working together or working independently. While the matching server140is also shown as a separate component, in other embodiments, the operations and features of the matching server140may be incorporated with one or more of the other components of the gaming system100. For example, the operations and features of the matching server140may be incorporated in the smart device110, particularly the smart device110of the player requesting another player to play the turn based game. The matching server140is described in greater detail as a hardware implementation with reference toFIG. 4, as part of a cloud implementation with reference toFIG. 5, and/or as utilizing functional abstraction layers for processing with reference toFIG. 6.

In the exemplary embodiments, the analysis program142may be a software, hardware, and/or firmware application configured to monitor activity of players and track player activity to determine characteristics associated with player activity. Accordingly, the analysis program142may update the player profiles132. The analysis program142may track when a player has logged into and out of the game server120. As the time of the log in and log out may be relative (e.g., when the turn based game is available to different regions over multiple time zones), the analysis program142may track the times based on a local clock of the matching server140to maintain a common standard of time. The analysis program142may also maintain an event tracker that tracks each time a corresponding event has occurred. For example, each time that a game is initiated by the player, the analysis program142may update a game event tracker. In another example, each time that a player performs a turn, the analysis program142may update a turn event tracker. In this manner, the analysis program142may update the various types of information that the player profile132includes.

The analysis program142may also compensate for variance. A player may play the turn based game at generally similar timeframes and perform various events in a substantially similar pattern. However, there may also be times when the player has further opportunities to play the turn based game that may inadvertently affect the player activity information of the player profile132. For example, the player may generally not play the turn based game during standard work hours (e.g., 9 am to 5 pm) and instead opt to play the game after a dinner timeframe but before a sleep timeframe (e.g., 8 pm to 10 pm). However, during a holiday or for some other reason, the player may play the game during work hours. These outlier figures may be processed by the analysis program142. For example, the analysis program142may update the player profile132to exclude these outlier figures. In another example, the analysis program142may incorporate various player activity information that also has notes or conditions (e.g., during holidays, during weekends, etc.). The variance may also relate to a larger period of time (e.g., people on shift work change patterns every set period of time such as every two to three weeks, relate to periods of time during the day such as nights, days, afternoons, etc.). Such patterns may be consistent over large periods of time but may appear random over a short period of time. The analysis program142may be configured to incorporate variance in these various periods of time.

The analysis program142may also process the information of events during a session to compensate for other types of variance. For example, because turns may not be performed at regular times as the actions of the other player may affect how a player takes turns, the analysis program142may process the information to reflect turn variance. In this manner, if a player were to normally take 20 turns during a session but a current session only allowed the player to take 15 turns (e.g., the other player(s) did not take turns in a timely manner as anticipated), the analysis program142may incorporate a variance due to these other factors.

Through tracking player activity of the player during a session (e.g., from login time to log out time) and incorporating any variance that may be present, the analysis program142may update the player profile132in a manner that reflects characteristics associated with player activity. Where appropriate, the characteristics may be reflected into metrics or values for comparison purposes (e.g., as used by the matching program144). For example, the number of turns taken during a game session may be converted into a metric (e.g., total number of turns taken during a game session timeframe, a number of turns taken per period of time, etc.). In another example, the login time and log out time may be converted into a metric (e.g., a clock time may be converted into a military or 24 hour time where 8 pm may be converted to 2000, 3 am may be converted to 0300, 7:30 am may be converted to 0730, 12:47 pm may be converted to 1247, etc.).

In the exemplary embodiments, the matching program144may be a software, hardware, and/or firmware application configured to match a first player with a second player to play the turn based game based on the player activity of the players. The matching program144may access the player profiles132to identify how the first player is to be matched with a second player. For example, the first player may have requested to play the game and for the game server120to select an opponent. The matching server140may register when this request is received by the game server120to perform the operations in matching the first player with the second player.

Using the player profile132of the first player, the matching program144may identify the characteristics of the player activity of the first player. The matching program144may initially identify currently available players so that the first player may play the game immediately without waiting for the second player to become available. In filtering a pool of players to those who are currently available, the matching program144may process the currently available players for potential second players to be matched with the first player.

According to an exemplary implementation, the matching program144may process the activity level based on information included in the player profiles132to identify potential second players to be matched with the first player. For example, the matching program144may utilize a wait time basis to identify the second player. The wait time basis may be directed to periods during which the first player has completed a turn and waits for the second player to complete a turn to take a following turn. The matching program144may determine the times when the first player generally performs a turn (e.g., 0800, 0930, 1530, 2200, etc.). The matching program144may determine that a potential second player will take turns in between these times that the first player completes turns (e.g., between 0815 to 0925, between 0945 to 1525, between 1545 to 2155, between 2215 to 0755, etc.). Accordingly, in a first characteristic consideration, the matching program144may utilize times when turns are taken to determine a potential second player match for the first player. In this manner, the matching program144may apply a filter for a compatibility of the first player requesting a new game with a second player who falls within the first player's typical wait times.

The matching program144may also incorporate further considerations. For example, each potential second player may not require an exact correspondence to or fall within the first player's wait times. In view of this, the matching program144may consider information related to a particular player's number of turns taken to provide further insight as to whether to match a second player with a first player. Accordingly, the number of turns taken at the various times may be determined for the first player (e.g., at 0800 takes four turns, at 0930 takes two turns, at 1530 takes three turns, at 2200 takes four turns, etc.). In such a scenario, the first player may have a plurality of active games for which turns are taken in each time (e.g., the first player is playing in two games where the first player takes turns at 0800, 0930, 1530, and 2200 as well as a third game where the first player takes turns at 0800, 1530, and 2200). Based on this turns taken information, the matching program144identify a potential second player as one who takes turns before selected turns of the first player (e.g., before the 0800 turn, before the 2200 turn, etc.).

In another example of further considerations, the matching program144may incorporate information directed toward a duration of time and a number of turns taken within an active period. For example, by further incorporating these types of information, the matching program144may match the first player with a second player who have compatible active times and take turns during a common time frame.

In a further example of further considerations, the matching program144may incorporate account patterns of variance in turns taken over a course of a predetermined time period (e.g., a week). For example, the first player may take turns in the evenings on days that the first player works and during the daytime on days off. These time frames may be normalized based on the internal clock of the matching server140. If another player has the same pattern and turn schedule (e.g., whether in the same time zone or not through normalization), the matching program144may identify such a player as a second player to be matched with the first player.

The matching program144may utilize any one or more of the above characteristic comparisons in identifying one or more second players that may be matched with the first player. When comparing the characteristics of player activity between two players, the matching program144may determine a difference threshold for metrics corresponding to the characteristics. For example, for each characteristic and the corresponding metric values, the matching program144may utilize a respective difference threshold. Thus, for the turns taken over a period of time, the matching program144may utilize a turns taken difference threshold to determine whether this characteristic is compatible between the two players (e.g., the metric may indicate a compatibility in active times where a larger difference indicates less overlap in active time while a smaller difference indicates a greater overlap in active time). For the wait time intervals, the matching program144may utilize a wait time difference threshold to determine whether this characteristic is compatible between the two players (e.g., the times that the second player takes turns falls within the wait time range of the first player would have a zero wait time difference while the times that the second player takes turns falls outside the wait time range of the first player would have a positive wait time difference). In the exemplary characteristics described above, the matching program144may determine when the respective difference threshold is met when the difference of the metrics of the two players is less than the difference threshold. However, those skilled in the art will appreciate that based on the characteristic and the manner with which a corresponding metric is determined, the matching program144may determine when the respective difference is met when the difference of the metrics of the two players is at least the difference threshold. Rather than respective determinations, the matching program144may also utilize an aggregate difference threshold based on an aggregation of the metrics identified for the various characteristics.

If each player in the pool of currently available players do not satisfy the threshold to match with the first player, the matching program144may perform a predictive operation to identify the second player. The matching program144may identify players who are currently unavailable but who have player activity as indicated in the respective player profiles132that the player is expected to be available and/or active within an acceptable time frame to be matched with the first player. In this manner, the matching program144may utilize the information indicating the active time periods of the potential second players in identifying currently unavailable players who may still be a compatible match to the first player. When the predictive operation is used, the matching program144may include an indication where the first player who is currently available is defaulted the first turn to minimize any wait time.

In the process of identifying potential second players, the matching program144may identify more than one potential second player where each of these potential second players satisfies the difference threshold. When multiple second players are identified for the first player, the matching program144may compare the differences of the metrics for the characteristics between the first player and each of the potential second players. The matching program144may order the potential second players according to a degree in satisfying the difference threshold. For example, when the metric of a characteristic satisfies the difference threshold from being less than the difference threshold, the matching program144may determine that a second player having the smallest difference is the most compatible with regard to this characteristic. In another example, when the metric of a characteristic satisfies the difference threshold from being at least the difference threshold, the matching program144may determine that a second player having the greatest difference is the most compatible with regard to this characteristic. Through this comparison within the potential second players who satisfied the initial determination, the matching program144may filter these second players to identify an optimal second player to match with the first player from among the potential second players.

FIG. 2illustrates an exemplary flowchart of a method200illustrating the operations of the analysis program142of the matching server140of the gaming system100in generating player profiles132used to match players in a turn based game based on player activity, in accordance with the exemplary embodiments. The method300will be described from the perspective of the matching server140.

The matching server140may monitor when a player logs into the game server120(step202). In updating the player profiles132, the matching server140may determine when a player logs into the game server120and logs out of the game server120. Thus, the time from the login time to the log out time may indicate a game session in which the user may take turns. The matching server140may utilize each game session as a unit in which to monitor the various events that may occur including turns taken, active periods, etc. as will be described in further detail below.

To further illustrate the operations of the matching server140, reference is now made to an illustrative exemplary embodiment. According to the illustrative exemplary embodiment, the matching server140may determine when players have game sessions over a course of a day. For example, a first player may initiate a first game session by logging in at 7:45 am and conclude the game session by logging out at 10:00 am according to an internal clock of the matching server140. The first player may then have a second game session by logging in at 12:00 pm and logging out at 1:00 pm according to the internal clock of the matching server140. The first player may subsequently have a third game session by logging in at 9:45 pm and logging out at 10:30 pm according to the internal clock of the matching server140. In this manner, the matching server140may monitor each game session from login time to log out time.

The matching server140may determine an active time of the user during each game session (step204). Although the player may be logged into the game server120, the player may have periods of idleness for a variety of reasons. Accordingly, the matching server140may determine periods of activity during each game session. For example, the periods of activity may include times when the player is actively taking a turn.

The matching server140may determine a number of games that are started or played during each game session (step206). As described above, the matching server140may incorporate various factors including a number of games that the player is currently a part. The number of games may clarify how each game session may be spent by the player. For example, the player may take a turn in each game session throughout the day for a first game. In another example, the player may take a turn in only select game sessions throughout the day for a second game. In this manner, the matching server140may determine how the player is active over a course of one or more games that the player may be a part.

The matching server140may determine when and how many turns are taken by the player in each game session (step208). In monitoring each turn that is taken, the matching server140may determine a player activity in a more granular level. Accordingly, the matching server140may identify periods of activity related specifically to taking turns which may translate to a variety of other types of information (e.g., wait times between successive turns, a period in which a second player may respond, etc.).

According to the previously introduced exemplary embodiment, the player may have an active time during each game session. For example, in the first game session, the player may have an active time at 8:00 am and 9:30 am; in the second game session, the player may have an active time at 3:30 pm; in the third game session, the player may have an active time at 10:00 pm. Within each active time, the first player may be a part of three different games in which the first player takes turns in each active time of each game session for a first game and a second game but only takes turns in select active times of each game session for a third game (e.g., does not take a turn at 9:30 am for the third game). In view of the game sessions and active times, the matching server140may also identify wait times. For example, between the first and second game sessions, a wait time may be from 8:15 am to 9:25 am; between the second and third game sessions, a wait time may be from 9:45 am to 3:25 pm; between the third and fourth game sessions, a wait time may be from 3:45 pm to 9:55 pm; and between the fourth game session and the first game session on a following day (where applicable), the wait time may be from 10:15 pm to 7:55 am.

The matching server140may determine whether to update the player profile132for the player (decision210). The matching server140may be configured to update the player profile132at a variety of times. For example, the matching server140may dynamically update the player profile132while the matching server140monitors the player activity in each game session. In another example, the matching server140may update the player profile132at predetermined time intervals. In a further example, the matching server140may update the player profile132when an event is registered (e.g., a turn is taken). In yet another example, the matching server140may update the player profile132when sufficient data has been gathered to warrant an update. Those skilled in the art will appreciate that the matching server140may update the player profile132using these, a combination thereof or other conditions.

As a result of the player profile132not being updated yet (decision210, “NO” branch), the matching server140continues to monitor the player activity of the player. As a result of the player profile132being determined to update (decision210, “YES” branch), the matching server140may perform a further operation in determining variance over time of the player activity (step212). As described above, there may be characteristics that require variance to be incorporated to provide a more accurate representation of the player activity of the player. For example, a player may take turns at night during weekdays but additionally takes turns during the day on weekends. Accordingly, the matching server140may separate the active times during weekends from a player activity information during weekdays. The matching server140may perform such variance incorporations for a variety of factors such as outliers (e.g., events that occur randomly or with relatively low frequency), holidays (e.g., exceptions to generally observed behavior in the player activity), etc. The matching server140may then update the player profile132(step214).

With reference again to the previously introduced exemplary embodiment, the above noted active times may refer to select days of the week such as weekdays. The player may have increased active times during the weekends. For example, the player may remain logged into the game server120from a time the player wakes up to a time the player goes to sleep. In this manner, the game session on weekends may be an extended period of time with active times interspersed therein. The matching server140may identify such variances and incorporate the information into an update of the player profile132. For example, the matching server140may set aside such information to be included in a separate indication of active times with a modifier (e.g., day of the week) or remove outlier information having a frequency that falls below a frequency threshold.

FIG. 3depicts an exemplary flowchart of a method300illustrating the operations of a matching program144of the matching server140of the gaming system100in matching players in a turn based game based on player activity, in accordance with the exemplary embodiments. The method300will be described from the perspective of the matching server140.

The matching server140may determine when the game server120receives a request from a first player to start a game in which the game server120selects a second player to match with the first player (step302). The matching server140may be in a communicative relationship with the game server120. The communicative relationship may be used for the game server120to provide an indication to the matching server140that the request has been received from the first player. The indication may include an identity of the first player. As will be described in detail below, the communicative relationship may also be used to transmit a recommendation or instruction from the matching server140to the game server120as to a second player to be matched with the first player who requested the new game.

To further illustrate the operations of the matching server140, reference is now made to an illustrative exemplary embodiment. According to the illustrative exemplary embodiment, the first player may log into the game server120. Upon logging in, the first player may enter an input indicating that the first player is requesting to be matched by the game server120to play the game. Upon receiving the request from the first player (e.g., via the game client112on the smart device110associated with the first player), the game server120may transmit an indication to the matching server140that the request was received. The game server120may include an identity of the first player in the indication. The identity may correspond to an identity associated with one of the player profiles132stored in the profile repository130.

The matching server140may determine characteristics related to player activity of the first player (step304). Based on the identity included in the indication from the gaming server120, the matching server140may retrieve the player profile132associated with the first player. As described above, the player profile132may include various types of information that may be used to determine a plurality of characteristics related to player activity. For example, the player profile132may indicate login and log out times for game sessions, an active time, a number of turns taken at various timeframes, a number of games started/played, variance information, etc. For the different characteristics, the matching server140may determine corresponding metrics or values that represent the characteristic of player activity for the first player.

According to the previously introduced exemplary embodiment, the matching server140may retrieve the player activity information included in the player profile132for the first player. The player profile132for the first player may indicate various active times or times when the first player generally takes turns. For example, the player may take turns at 8:00 am, 9:30 am, 3:30 pm, and 10:00 pm. Based on this information, the matching server140may determine a characteristic of wait times that are available for the first player. From the perspective of the second player who is to be matched to the first player, the wait times may correspond to an active timeframe that falls within the wait times of the first player. Thus, the matching server140may determine the wait times of the first player or the active timeframe of the potential second player to be between 8:15 am and 9:25 am, between 9:45 am and 3:25 pm, between 3:45 pm and 9:55 pm, and between 10:15 pm and 7:55 am.

The matching server140may identify potential second players that match or is compatible with the characteristics of the player activity of the first player within a difference threshold for the characteristics (step306). The matching server140may identify a pool of players (e.g., utilizing any player profile132stored in the player repository130). In a particular implementation, the matching server140may identify a pool of currently available players. Using the pool of players, the matching server140may determine which of the players has player activity characteristics that are compatible with the player activity characteristics of the first player. For example, the matching server140may determine metrics or values for the characteristics for comparison with the metrics or values of the first player. The matching server140may determine a difference in these metrics. The difference may be compared to a difference threshold to determine whether the difference threshold is satisfied. For example, when the characteristic is to be similar, the difference threshold may be set to a near zero value. Thus, the difference threshold may be satisfied when the difference is less than the difference threshold. For players who satisfy the difference threshold, the matching server140may classify these players as potential second players to be matched with the first player in which a selection from the potential second players becomes an actual second player to be matched.

The matching server140may determine whether the results of identifying the potential second players includes one or more players (decision308). As a result of the matching server140identifying only one potential second player (decision308, “NO” branch), the matching server140may continue with matching the single potential second player with the first player, thereby establishing the potential second player as the actual second player (step310). The matching server140may generate a recommendation or an instruction that is provided to the game server120so that the actual second player is matched with the first player. Thereafter, the game between the first and second players may begin (step312).

As a result of the matching server140identifying a plurality of potential second players (decision308, “YES” branch), the matching server140may perform subsequent operations to determine which of the potential second players has a highest compatibility with the first player. In performing these subsequent operations, the matching server140may determine the differences in the metrics or values for the characteristics between the first player and each of the potential second players (step314). As each of the potential second players satisfy the condition of the difference threshold, the degree by which the difference between the first player and each of the potential second players may identify the most compatible candidate among the potential second players to be the actual second player. For example, when the difference is to be a minimum (e.g., near zero), the potential second player having the lowest difference in the metric for the characteristic may be selected as the actual second player. In this manner, the matching server140may select this potential second player as the actual second player from among the plurality of potential second players (step310). The matching server140may generate a recommendation or an instruction that is provided to the game server120so that the actual second player is matched with the first player. Thereafter, the game between the first and second players may begin (step312).

With reference again to the previously introduced exemplary embodiment, the matching server140may have identified three potential second players. Specifically, the three potential second players may have active times that are within a difference threshold of the wait times of the first player. For example, the matching server140may set a difference threshold for the active time of the potential second player to be within 15 minutes of the wait time range of the first player. Thus, by incorporating the difference threshold to a maximum amount, the matching server140may select players having active times that are between 8:00 am and 9:40 am, between 9:30 am and 3:40 pm, between 3:30 pm and 10:10 pm, and between 10:00 pm and 8:10 am. The matching server140may convert the wait times including the difference threshold as metrics such as 0800 to 0940, 0930 to 1540, 1530 to 2210, and 2200 to 0810. In determining a difference, the matching server140may use a center time in each wait time. For example, the center time between 8:15 am and 9:25 am may be 8:40 am (e.g., with a converted metric of 0840), between 9:45 am and 3:25 pm may be 12:35 pm (e.g., with a converted metric of 1235), between 3:45 pm and 9:55 pm may be 6:50 pm (e.g., with a converted metric of 1850), and between 10:15 pm and 7:55 am may be 3:05 am (e.g., with a converted metric of 0305). The matching server140may determine a difference between active times of each potential second player with the center times of the wait times of the first player. In determining these differences, the matching server140may rank the difference in an individual capacity or as an aggregate (e.g., a sum of all the differences for each wait time). In the example, the matching server140may determine that a first potential second player has the smallest difference, a second potential second player has a middle difference, and a third potential second player has a highest difference. For the characteristic of wait times of the first player and active times of the second player, the matching server140may utilize a smallest difference standard such that a smallest difference indicates a highest compatibility while a greater difference indicates a lowest compatibility. The matching server140may rank the potential second players with the first potential second player having the highest rank and the third potential second player having the lowest rank. By selecting the potential second player with the highest rank, the matching server140may select the first potential second player to be matched with the first player. The matching server140may generate an instruction for the game server120for this match.

The method300may incorporate further features of the exemplary embodiments. For example, the method300may perform an operation to determine whether the currently available players satisfy the difference threshold. For scenarios where the currently available players are not compatible with the first player, the method300may include operations to predictively select a second player for the first player based on player activity and an expectation that the second player is compatible once available.

The exemplary embodiments are configured to match players in a turn based game based on player activity. The exemplary embodiments may monitor player activity while a player is playing the turn based game, particularly during game sessions while the player is logged into a game server that hosts the turn based game. The exemplary embodiments may maintain player profiles of each player that represents the historical player activity. Using the player profiles, when a request is received for a new game to be started including a first player, the exemplary embodiments may determine the characteristics of the player activity of the first player and compare the characteristics with corresponding characteristics of other players. The results of the comparison may be used to identify a second player to be matched with the first player for the game to be played therebetween.

FIG. 4depicts a block diagram of devices within the gaming system100ofFIG. 1, in accordance with the exemplary embodiments. It should be appreciated thatFIG. 4provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environment may be made.

Devices used herein may include one or more processors02, one or more computer-readable RAMs04, one or more computer-readable ROMs06, one or more computer readable storage media08, device drivers12, read/write drive or interface14, network adapter or interface16, all interconnected over a communications fabric18. Communications fabric18may be implemented with any architecture designed for passing data and/or control information between processors (such as microprocessors, communications and network processors, etc.), system memory, peripheral devices, and any other hardware components within a system.

One or more operating systems10, and one or more application programs11are stored on one or more of the computer readable storage media08for execution by one or more of the processors02via one or more of the respective RAMs04(which typically include cache memory). In the illustrated embodiment, each of the computer readable storage media08may be a magnetic disk storage device of an internal hard drive, CD-ROM, DVD, memory stick, magnetic tape, magnetic disk, optical disk, a semiconductor storage device such as RAM, ROM, EPROM, flash memory or any other computer-readable tangible storage device that can store a computer program and digital information.

Devices used herein may also include a R/W drive or interface14to read from and write to one or more portable computer readable storage media26. Application programs11on said devices may be stored on one or more of the portable computer readable storage media26, read via the respective R/W drive or interface14and loaded into the respective computer readable storage media08.

Devices used herein may also include a display screen20, a keyboard or keypad22, and a computer mouse or touchpad24. Device drivers12interface to display screen20for imaging, to keyboard or keypad22, to computer mouse or touchpad24, and/or to display screen20for pressure sensing of alphanumeric character entry and user selections. The device drivers12, R/W drive or interface14and network adapter or interface16may comprise hardware and software (stored on computer readable storage media08and/or ROM06).

The programs described herein are identified based upon the application for which they are implemented in a specific one of the exemplary embodiments. However, it should be appreciated that any particular program nomenclature herein is used merely for convenience, and thus the exemplary embodiments should not be limited to use solely in any specific application identified and/or implied by such nomenclature.

Based on the foregoing, a computer system, method, and computer program product have been disclosed. However, numerous modifications and substitutions can be made without deviating from the scope of the exemplary embodiments. Therefore, the exemplary embodiments have been disclosed by way of example and not limitation.

It is to be understood that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, the exemplary embodiments are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

Characteristics are as follows:

Service Models are as follows:

Deployment Models are as follows: