Systems and methods for generating improved non-player characters

Information

  • Patent Grant
  • 11679330
  • Patent Number
    11,679,330
  • Date Filed
    Wednesday, December 18, 2019
    4 years ago
  • Date Issued
    Tuesday, June 20, 2023
    11 months ago
Abstract
The disclosed systems and methods track and continuously monitor data about a player or a multiple players and create a non-playing character (NPC) and/or modify an existing NPC that replicates the player(s) play style. The disclosed systems implement an artificial intelligence engine that monitors how a real player responds to one or more events in a game and correlates game outcomes with real player actions, with the actions or reactions of third players, and/or with an amount or extent of engagement. The engine may be used to generate, host, or otherwise provide data representative of one or more NPCs to multiple different games, being hosted by one or more servers, concurrently.
Description
FIELD

The invention relates generally to video games, and more particularly to systems and methods for styling generic non-player characters in video games based on behavior and actions of real players.


BACKGROUND

Multiplayer video games have exploded in popularity due, in part, to services such as Microsoft's Xbox LIVE® and Sony's PlayStation Network® which enable gamers all over the world to play with or against one another. Generally, a multiplayer video game is a video game in which two or more players play in a gameplay session in a cooperative or adversarial relationship. At least one of the players may comprise a human player, while one or more other players may comprise either non-player characters and/or other human players.


A non-player character (“NPC”), which may also be referred to as a non-person character, a non-playable character, a bot, or other similar descriptor, is a character in a game that is not controlled by a human player. In multiplayer video games, an NPC is typically a character controlled by a computer through artificial intelligence (AI).


Often times, when a player logs in to a game system or platform to play a multiplayer video game, the player may engage in a gameplay session in which he or she is matched with other players to play together (on the same team or as opponents). A given player may engage in multiple gameplay sessions during a login session. In addition, each gameplay session may be played with either the same or a different group of matched players.


In some instances, NPCs are used to fill gaps in a gameplay session. As an example, in a game that requires ten players to play together on a team, four NPCs may be selected to fill out the team if only six human players have joined. Sometimes the NPCs are generic in their characteristics. Sometimes the NPCs are programmed for different skills levels for use with players of matching skill levels. U.S. Pat. No. 10,118,099 entitled ‘System and Method for Transparently Styling Non-Player Characters in a Multiplayer Video Game’ and assigned to the Applicant of the present specification, describes systems and methods for “identifying, by the computer system, one or more human players to be matched for a gameplay session of a multiplayer video game, wherein each human player has a player profile comprising a number of profile attributes, wherein the human players are matched by grouping two or more players to play together in the gameplay session based on at least one of each player's profile attributes, game profile information, or match variables, and wherein the gameplay session requires a predetermined number of required players; determining, by the computer system, whether the predetermined number of players required for the gameplay session is met by the identified human players; obtaining, by the computer system, one or more non-player characters to fill available spots in the gameplay session responsive to a determination that the predetermined number of players required for the gameplay session is not met by the identified human players, wherein each of the one or more non-player characters has a non-player character player profile comprising a number of profile attributes; determining, by the computer system, a subset of profile attributes common to the identified human player profiles and the non-player character player profiles; and permitting, by the computer system, the display of only the determined subset of profile attributes when any identified human player profile or non-player character player profile is accessed.”


U.S. Patent Application Publication Number US 2014/0342808, entitled ‘System and Method of Using PCs as NPCs’, describes virtual gameplay methods for “providing access to a video game in which a player can create a player character for interaction in the video game; allowing the player to play in the video game using the player character via at least one player character script; when the player exits the video game, allowing the player character to at least temporarily become a non-player character in the game by selectively causing the player character to assume at least one non-player character script, such that the player character has automatic, non-player directed interactions in the video game wherein the player character takes on the behaviour of a non-player character; and when the player returns to the video game, allowing the player character to resume play in the video game according to the player character script.”


However, the currently available methods and systems that create and utilize NPCs to play with or on behalf of players are robotic and overly mechanized in nature, not providing the type of fluidity and creative interaction exhibited by human players. There is a need for NPC that may be more personalized not only in their appearance and presentation, but also in their gaming skills and ability to evolve those gaming skills. What is needed is systems and methods of generating NPCs that mimic the behavior of specific human players for enjoyment and business purposes, for example, NPCs mimicking the behavior of friends from online gaming sessions, and NPCs mimicking the behavior of famous and professional players to drive revenue and for practice sessions. What is also needed is a system for generating and implementing NPCs in a manner that allows them to evolve and develop, much like human players do.


SUMMARY

The following embodiments and aspects thereof are described and illustrated in conjunction with systems, tools and methods, which are meant to be exemplary and illustrative, and not limiting in scope. The present application discloses numerous embodiments.


The present specification is directed toward a computer implemented method for generating data representative of one or more non-player characters (NPCs) in one or more multi-player video games, the method being implemented in a host computer having one or more physical processors programmed with programmatic instructions that, when executed by the one or more physical processors, cause the host computer to perform the method, the method comprising: tracking one or more profiles of human players to generate human player data; tracking game data, wherein the game data is representative of one or more game events or game outcomes; generating data representative of a behavior of the NPCs by applying a neural network or machine learning process to the human player data and game data; and transmitting the data representative of the behavior of the NPCs to one or more servers hosting the one or more multi-player video games.


Optionally, the computer implemented method further comprises generating the data representative of the behavior of the NPCs substantially concurrently with at least one of the tracking of human player data or the tracking of game data.


The multi-player video games may be of a different genre, software platform, or type.


The data representative of the behavior of the NPCs may define one or more reactions of the NPCs to game events or a movement of the NPCs.


Optionally, the neural network or machine learning process comprises at least one of a linear regression process, a logistic regression process, a decision tree process, a naïve Bayes process, a k-means process, a random forest process, a dimensionality reduction process, a gradient boosting process, a supervised learning process, an unsupervised learning process, or a reinforcement learning process.


Optionally, the one or more servers comprise at least two and the multi-player video games are of a different genre, software platform, or type.


Optionally, the human player data comprises data representative of at least one of a method of playing, a skill level, reactions to one or more game events, or a visual appearance


Optionally, the tracking of the human player data is triggered by a game score, a time left in a multi-player video game, or a game type.


Optionally, the human player data comprises at least one of an average speed, a weapon usage preference, a weapon in inventory, ammo in inventory, a frequency at which a player engaged an enemy at a first distance, a frequency at which a player fires a first shot in an engagement, a duration that a player spent in specific areas of a map of a game, a time to kill for each weapon type at each distance range, movement attributes, a proximity to teammates, a favorite skin, or emotes.


Optionally, the game data comprises game outcome data, an amount of time a game is played, an amount of virtual resources earned, lost, or exchanged, a score, a time of completion, a number of levels achieved, or metrics indicative of player engagement.


The present specification also discloses a system adapted to generate data representative of one or more non-player characters (NPCs) in one or more multi-player video games, wherein the system has one or more physical processors programmed with programmatic instructions that, when executed by the one or more physical processors, cause the host computer to: track one or more profiles of human players to generate human player data; track game data, wherein the game data is representative of one or more game events or game outcomes; generate data representative of a behavior of the NPCs by applying a neural network or machine learning process to the human player data and game data; and transmit the data representative of the behavior of the NPCs to one or more servers hosting the one or more multi-player video games.


Optionally, when executed by the one or more physical processors, the programmatic instructions are further configured to generate the data representative of the behavior of the NPCs substantially concurrently with at least one of the tracking of human player data or the tracking of game data.


The multi-player video games may be of a different genre, software platform, or type.


The data representative of the behavior of the NPCs may define one or more reactions of the NPCs to game events or a movement of the NPCs.


Optionally, the neural network or machine learning process comprises at least one of a linear regression process, a logistic regression process, a decision tree process, a naïve Bayes process, a k-means process, a random forest process, a dimensionality reduction process, a gradient boosting process, a supervised learning process, an unsupervised learning process, or a reinforcement learning process.


Optionally, the one or more servers comprise at least two and the multi-player video games are of a different genre, software platform, or type.


Optionally, the human player data comprises data representative of at least one of a method of playing, a skill level, reactions to one or more game events, or a visual appearance


Optionally, when executed by the one or more physical processors, the programmatic instructions are further configured to be triggered to track the human player data by a game score, a time left in a multi-player video game, or a game type.


Optionally, the human player data comprises at least one of an average speed, a weapon usage preference, a weapon in inventory, ammo in inventory, a frequency at which a player engaged an enemy at a first distance, a frequency at which a player fires a first shot in an engagement, a duration that a player spent in specific areas of a map of a game, a time to kill for each weapon type at each distance range, movement attributes, a proximity to teammates, a favorite skin, or emotes.


Optionally, the game data comprises game outcome data, an amount of time a game is played, an amount of virtual resources earned, lost, or exchanged, a score, a time of completion, a number of levels achieved, or metrics indicative of player engagement.


The present specification is also directed toward a computer implemented method for modifying an existing non-player character in a multiplayer video game, the method being implemented in a host computer having one or more physical processors programmed with computer program instruction that, when executed by the one or more physical processors, cause the host computer to perform the method, the method comprising: tracking a player's profile, wherein the profile comprises at least one of information about a method of playing by the player, playing skill of the player, playing actions performed by the player, and appearance of the player; monitoring changes in the profile based on at least one factor; and modifying the existing non-player character according to the tracking and the monitoring to create a modified non-player character corresponding to the player.


Optionally, the method further comprises continuously tracking and monitoring and continually modifying the modified non-player character based on the continuous tracking and monitoring.


Optionally, the monitoring changes in the profile based on at least one factor comprises factors comprising at least one of a game score, time left in match, and a game type.


Optionally, the tracking the player's profile further comprises tracking from at least one game played by the player: at least one of an average speed, weapon usage preference, given weapons and ammo currently in inventory, frequency at which the player engaged given enemy distance, frequency at which the player fired the first shot in an engagement, duration that the player spent in specific areas of a map of a game, time to kill for each weapon type at each distance range, movement attributes, proximity to teammates, favorite skin, and emotes.


Optionally, the tracking and the monitoring is performed continuously from a start time, wherein the start time is one of a time of inception of a game, and a date defined by at least one of the player and the host computer.


The present specification also discloses a system for modifying an existing non-player character in a multiplayer video game, said system comprising: a host computer having one or more physical processors programmed with computer program instructions that, when executed, cause the host computer to: track a player's profile, wherein the profile comprises at least one of information about a method of playing by the player, playing skill of the player, playing actions performed by the player, and appearance of the player; monitor changes in the profile based on at least one factor; and modify the existing non-player character according to the tracking and the monitoring to create a modified non-player character corresponding to the player.


Optionally, the system is configured to plug into multiple game engines.


The claimed methods and systems improve the quality of generated NPCs by continually monitoring and logging human player attributes to be used to periodically adjust, in real-time, attributes of the generated NPCs, thereby providing an overall better gameplay experience.


The aforementioned and other embodiments of the present specification shall be described in greater depth in the drawings and detailed description provided below.





BRIEF DESCRIPTION OF THE DRAWINGS

These and other features and advantages of the present specification will be further appreciated, as they become better understood by reference to the following detailed description when considered in connection with the accompanying drawings:



FIG. 1 illustrates an exemplary system environment for creating and using a non-player character, in accordance with some embodiments of the present specification;



FIG. 2 is a flowchart illustrating an exemplary process for modifying a non-player character, in accordance with some embodiments of the present specification;



FIG. 3 is a schematic illustrating a process of applying a machine learning process to game data and/or human player data; and



FIG. 4 is a schematic illustrating a process of applying a machine learning process to game data and/or human player data to generate NPC data and transmit it to more than one game server.





DETAILED DESCRIPTION

The present specification is directed towards multiple embodiments. The following disclosure is provided in order to enable a person having ordinary skill in the art to practice the invention. Language used in this specification should not be interpreted as a general disavowal of any one specific embodiment or used to limit the claims beyond the meaning of the terms used therein. The general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. Also, the terminology and phraseology used is for the purpose of describing exemplary embodiments and should not be considered limiting. Thus, the present invention is to be accorded the widest scope encompassing numerous alternatives, modifications and equivalents consistent with the principles and features disclosed. For purpose of clarity, details relating to technical material that is known in the technical fields related to the invention have not been described in detail so as not to unnecessarily obscure the present invention.


In the description and claims of the application, each of the words “comprise” “include” and “have”, and forms thereof, are not necessarily limited to members in a list with which the words may be associated. It should be noted herein that any feature or component described in association with a specific embodiment may be used and implemented with any other embodiment unless clearly indicated otherwise.


As used herein, the indefinite articles “a” and “an” mean “at least one” or “one or more” unless the context clearly dictates otherwise.



FIG. 1 illustrates an exemplary system 100 architecture that includes at least one computer system 110, and may include one or more servers 150 and one or more databases 160, among other components, in accordance with some embodiments of the present specification.


Computer System 110


Computer system 110 may be configured as a gaming console, a handheld gaming device, a personal computer (e.g., a desktop computer, a laptop computer, etc.), a smartphone, a tablet computing device, and/or other device that can be used to interact with an instance of a video game.


Computer system 110 may include one or more processors 112 (also interchangeably referred to herein as processors 112, processor(s) 112, or processor 112 for convenience), one or more storage devices 114, one or more peripherals 140, and/or other components. Processors 112 may be programmed by one or more computer program instructions. For example, processors 112 may be programmed by an NPC application 120 and/or other instructions (such as gaming instructions used to instantiate the game).


NPC Application 120


Depending on the system configuration, NPC application 120 (or portions thereof) may be part of a game application, which creates a game instance to facilitate gameplay. Alternatively or additionally, NPC application 120 may run on a device such as a server 150 or a peripheral 140 to determine one or more NPC configurations for users in an “online” game hosted by server 150.


NPC application 120 may include instructions that program computer system 110. The instructions may include without limitation, an NPC modification engine 122, an NPC management engine 124, an NPC profile engine 126, an Artificial Intelligence (“AI”) engine 128, and/or other instructions 130 that program computer system 110 and/or servers 150 to perform various operations, each of which are described in greater detail herein. As used herein, for convenience, the various instructions will be described as performing an operation, when, in fact, the various instructions program the processors 112 (and therefore computer system 110) and/or the server(s) 150 to perform the operation.


In one embodiment the NPC Application 120 is implemented on a server and comprises one or more application interfaces that are configured to receive, and transmit, data to at least one of a gaming server 150 hosting a multiplayer video game or a computing device 110 executing a video game. The multiple application interfaces in the NPC Application 120 may be configured to enable multiple different servers 150, each hosting a different multi-player video game, and/or multiple different computer systems 110, each executing the same or different video game clients, to directly and concurrently access the NPC Application. Accordingly, the NPC Application, which may be hosted on one or more servers, can provide the functionality described herein to multiple different video games, each of which is being hosted concurrently, thereby enabling the NPC Application to provide improved NPC generation to various multi-player gaming environments at the same time.


Peripherals 140


Peripherals 140 may be used to obtain an input (e.g., direct input, measured input, etc.) from a player. Peripherals 140 may include, without limitation, a game controller, a gamepad, a keyboard, a mouse, an imaging device such as a camera, a motion sensing device, a light sensor, a biometric sensor, and/or other peripheral device that can obtain an input from a player. Peripherals 140 may be coupled to a corresponding computer system 110 via a wired and/or wireless connection.


Server 150


Server 150 may include one or more computing devices and may include one or more physical processors programmed by computer program instructions. For example, server 150 may include all or a portion of a multiplayer video game host.


Although illustrated in FIG. 1 as a single component, computer system 110 and server 150 may each include a plurality of individual components (e.g., computer devices) each programmed with at least some of the functions described herein. In this manner, some components of computer system 110 and/or server 150 may perform some functions while other components may perform other functions, as would be appreciated. The one or more processors 112 may each include one or more physical processors that are programmed by computer program instructions. The various instructions described herein are exemplary only. Other configurations and numbers of instructions may be used, so long as the processor(s) 112 are programmed to perform the functions described herein.


Furthermore, it should be appreciated that although the various instructions are illustrated in FIG. 1 as being co-located within a single processing unit, in implementations in which processor(s) 112 includes multiple processing units, one or more instructions may be executed remotely from the other instructions.


The description of the functionality provided by the different instructions described herein is for illustrative purposes, and is not intended to be limiting, as any of instructions may provide more or less functionality than is described. For example, one or more of the instructions may be eliminated, and some or all of its functionality may be provided by other ones of the instructions. As another example, processor(s) 112 may be programmed by one or more additional instructions that may perform some or all of the functionality attributed herein to one of the instructions.


The various instructions described herein and processed by processor 112 may be stored in a storage device 114, which may comprise random access memory (RAM), read only memory (ROM), and/or other memory. The storage device may store the computer program instructions (e.g., the aforementioned instructions) to be executed by processor 112 as well as data that may be manipulated by processor 112. The storage device may comprise floppy disks, hard disks, optical disks, tapes, or other storage media for storing computer-executable instructions and/or data.


The various components illustrated in FIG. 1 may be coupled to at least one other component via a network 102, which may include any one or more of, for instance, the Internet, an intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network), a SAN (Storage Area Network), a MAN (Metropolitan Area Network), a wireless network, a cellular communications network, a Public Switched Telephone Network, and/or other network. In FIG. 1, as well as in other figures, different numbers of entities than those depicted may be used. Furthermore, according to various implementations, the components described herein may be implemented in hardware and/or software that configure hardware.


In embodiments, various databases 160 are configured to store multiple NPCs created and modified by NPC application 120. The various databases 160 described herein may be, include, or interface to, for example, an Oracle™ relational database sold commercially by Oracle Corporation. Other databases, such as Informix™, DB2 (Database 2) or other data storage, including file-based, or query formats, platforms, or resources such as OLAP (On Line Analytical Processing), SQL (Structured Query Language), a SAN (storage area network), Microsoft Access™ or others may also be used, incorporated, or accessed. The database may comprise one or more such databases that reside in one or more physical devices and in one or more physical locations. The database may store a plurality of types of data and/or files and associated data or file descriptions, administrative information, or any other data.


During operation, NPC application 120 may track a player's play profile and continuously monitor the profile during the playing of a game by the player. Examples of player's play profile tracked and monitored is based on the game being played, and may include average speed, weapon usage, preference given for weapons and ammo currently in inventory, how often the player engaged given enemy distance, how often the player fired the first shot in an engagement, how much time a player spent in specific areas of the map, time to kill for each weapon type at each distance range, movement attributes (strafe, jump, run, walk, and crouch usage), proximity to teammates, cosmetic factors like favorite skin and emotes, among other attributes that distinguish the manner of playing by the player from other players.


An NPC modification engine 122 may modify an existing NPC corresponding to the player, according to the tracked and monitored data. In some embodiments, the data is map specific. In some embodiments, monitoring the data comprises monitoring the inter-relationship between the different attributes of the player's profile during game play. In one embodiment, monitoring the inter-relationship involves observing how the player's play profile changed based on game score, time left in match, and game type, among other factors. In some implementations, specific characteristics being analyzed could be across all levels/maps or specific to a level or map or even a portion of a level/map. In some implementations, the data could relate to how players interact with each other, use weapons/items, navigate through levels, react to attacks, or any other information that relates the player's play profile to various factors in the game.


In some embodiments, NPC application 120 tracks a single human player over time and NPC modification engine 122, independently, or in association with AI engine 128, generates an NPC to mimic the tracked human player. In some embodiments, the tracked human player is a high performing human player, or ‘star’ player. In other embodiments, NPC application tracks a plurality of human players in order to generate NPCs which share attributes with a large population of human players to provide for more evenly balanced gaming. In some embodiments, the plurality of human players being tracked comprise all human players in a game or a subset of human players in a game, wherein the subset may be based on attributes such as, but not limited to, level, skill, or playstyle. A larger subset of human players provides a greater data set to allow the system to discern general play patterns in the player groups being tracked. The NPC application 120 tracks the human players over a predetermined time period and game data is logged in the system. In some embodiments, the time period comprises since the beginning of the current game session, since the inception of the game (including all played game sessions), the past X months, wherein X ranges from 0 to 60 months and all increments within, and since the last time an update was performed to modify NPCs based on logged data.


NPC modification engine 122, in association with AI engine 128 or independently, uses these factors or logged data to modify the baseline artificial intelligence (AI) of the existing NPC and generate new NPCs, thus continuously improving the performance of the NPC(s) or changing a performance level to a level comparable with a performance level of one or more human players competing with or against the NPC(s). Accordingly, a reaction time of the NPCs, how the NPC reacts to one or more specific events, the choice the NPC may make in response to one or more game options, and certain other NPC traits may evolve or change based on human player profile data or game data. In embodiments, changing a performance level of an NPC comprises decreasing a performance level of an NPC to match or be in range with the performance level of at least one lower skilled human player or increasing a performance level of an NPC to match or be in range with the performance level of at least one higher skilled human player. In some embodiments, the existing NPC is a generic or a default NPC generated by NPC application 120 and available from database(s) 160, and which may be deployed in any game engine executed on system 110. An original or default NPC may also be referred to as a baseline NPC that is continuously developed based on the player's play profile to improve its performance in tune with the player's performance.


NPC modification engine 122 and AI engine 128 may also correlate player's play profile and game profile information in order to evolve the NPC(s). The game profile information for all the types of games played by the player, such as games provided by different game engines, may be used by NPC modification engine 122 for its purpose. In one implementation, a game profile may be generated for a gameplay session based on gameplay information. Gameplay information may describe various game characteristics of a gameplay session that may influence the quality of gameplay. For example, gameplay information may include, without limitation, a number of players, types of roles (e.g., snipers), types of in-game items used or purchased (e.g., weapons, vehicles, armor, custom suits, custom paint, tires, engine modifications, etc.), composition of teams (e.g., number and/or types of roles in each team), maps or game levels played (e.g., battle zones, racetracks, sporting arenas, etc.), duration of gameplay (e.g., how duration of a given gameplay session), player skill levels, player styles (e.g., aggressive, prefers to be a sniper, etc.), types of matches (e.g., team death match, capture the flag, etc.), and/or other information related to a gameplay session.


Accordingly, game outcomes may be used to modify one or more NPC behavioral or decision traits. In particular, AI engine 128 may be configured to associate, in real-time, specific game outcome data, such as an amount of time a game is played, an amount of virtual resources earned, lost, or exchanged, a score, a time of completion, a number of levels achieved, or other metrics indicative of engagement, with a reaction time of the NPCs, how the NPC reacts to one or more specific events, or the choice the NPC may make in response to one or more game options. To do so, AI engine 128 may comprise one or more nodes, virtually interlinked in a form of one or more layers, that is trained by providing one or more datasets having the game data or human profile data described above, wherein, as a result of the training process, one or more of the aforementioned nodes is associated with a coefficient, weight, or other value indicator used to weight the importance of the node and to associate inputted data, such as a game event, with a preferred behavior, such as how the NPC should react. In one embodiment, a training of the AI engine 128 occurs substantially concurrently with an execution of the AI engine 128 to identify, predict or otherwise select preferred NPC behavior based upon game events occurring within the game. Referring to FIG. 3, the AI engine 322 receives game data 316 and human player data 326 as described above. The AI engine 322 subjects the game data 316 and human player data 326 to one or more artificial engine or machine learning processes 354, including one or more of linear regression, logistic regression, decision trees, naïve Bayes, k-means, random forest, dimensionality reduction algorithms, gradient boosting algorithms, supervised learning, unsupervised learning, or reinforcement learning. In one embodiment the receipt of game data 316 and human player data 326 occurs at a different time or substantially concurrently with the generation of NPC data 346, which is indicative of how the NPC should behave, react, choose, or otherwise act, and/or the supply of the NPC data 346 to more than one server executing different games.


A game profile may be specific for a given gameplay session (e.g., different game profiles may be associated with different gameplay sessions) and/or may be used to generate a broader game profile for a particular game (e.g., different games may be associated with different game profiles). In this manner, a given game or gameplay session may be characterized using a game profile.


According to an aspect of the invention, the play profile may be generated for the player based on player information as well as play information from the game played by the player. Player information may describe various characteristics of the player, which may be used to assess how the player plays in a given gameplay session, a match, and/or a game.


For example, player information may comprise a variety of player attributes including, without limitation, screen name (or gamer tag), style of gameplay (e.g., aggressive), a role preference (e.g., an explicit indication by the player of such preference), a role actually played, a duration of gameplay sessions, a number of gameplay sessions played by in a given login session, in-game items used or purchased by the player, membership in a clan or team, preference to play with clan mates or friends, demographic information of the player (e.g., geographic location, gender, income level, etc.), win/loss records, scores, and/or other attributes or information without limitation that may be used to determine the play profile of the player in a given gameplay session, a match, and/or a game. Further, the play style of the player may be gathered from information about an average speed, use of weapons, preference given to certain weapons and ammo made available to the player, how often the player engaged given enemy distance, how often the player fired the first shot in an engagement, how much time the player spent in specific areas of a map of the game, time taken by the player to kill for each weapon type at each distance range, movement attributes of the player, proximity maintained by the player with the teammates, cosmetic attributes selected by the player for its playing character in the game, among other attributes or information that may be used to determine the play style of the player. While examples provided in the present specification are in context of FPS games, the attributes/information specific to any type of game may be determined by the various embodiments.


Information from a player play profile may be indexed by time. For example, the foregoing player information may include all player information known about a player, a subset of all information (e.g., information related to the last day, week, month, previous “N” number of game sessions, login sessions, etc.). In this manner, a player profile may relate to all-time gameplay of the player, recent gameplay of the player, time of day (e.g., a player may be associated with different player profiles at different times of the day, such as having an aggressive play style during evening hours and a more relaxed play style during morning hours), and/or other subset.


According to an aspect of the invention, a player play profile may include a numerical value or other metric representative of the player's overall player skill. A player skill value may, for example, be determined according to historical player performance data represented (or conveyed) by one or more player play profile attributes. For example, player play profile attributes such as number of games played, winning percentage, highest score, lowest score, and the like may be used to determine a player skill value. It should be appreciated that the number and type of player profile attributes used to determine a player skill value may vary depending on the type of video game. As an example, in a first-person-shooter game, numerical values associated with attributes such as Score Per Minute (“SPM”), Kill/Death Ratio (“KDR”), Win/Loss Ratio (“WLR”), or other attributes may be used to generate a player skill value for the player. The player skill value may be continually updated and stored over time.


In embodiments, the modified and improved NPC(s) are stored in database 160. NPC management engine 124 may select and retrieve one or more NPCs from database 160.


NPC management engine 124 may generate one or more modified NPCs in real-time (“on the fly”) when a demand for the NPCs is identified. Alternatively, NPC management engine may generate the modified or improved NPC corresponding to the player in order to play with/against NPCs of other players. In some embodiments, NPC management engine 124 may license NPCs corresponding to popular players in order to generate value. In some embodiments, NPC management engine 124 uses improved NPCs to create simulated opposing teams/players for professional teams to practice with/against. In some embodiments, NPC management engine 124 replaces human players who left a game with NPCs that mimic the human player's play profile. In some embodiments, NPC management engine 124 uses modified and improved NPCs to develop new baseline NPCs in order to improve a quality of AI bots overall.


In some embodiments, NPCs created in NPC application 120 are styled by NPC profile engine 126 to resemble their corresponding human players in terms of both player profile attributes and gameplay actions such that players may not recognize NPCs as non-human, computer-controlled players. A variety of known computational and/or statistical methods may be used to ensure that an NPC is generated (for current gameplay or later selection) having attributes and attribute values typical of other human players in a gameplay session. Details about such methods are described in U.S. Pat. No. 10,118,099, entitled ‘System and Method for Transparently Styling Non-Player Characters in a Multiplayer Vide Game’, and incorporated herein by reference in its entirety.


During gameplay, AI engine 128 may control an NPC's behavior (including gameplay actions) such that the NPC's gameplay more closely mimics the gameplay of the corresponding player. In one implementation, AI engine 128 may analyze an NPC player play profile (as selected or generated in the manner described above) to determine an appropriate skill level of play of the NPC.


In one implementation, an NPC may be directed (or trained) by AI engine 128 to modify or improve its gameplay behavior corresponding to the changes in the player's gameplay behavior. AI engine 128 may monitor player and NPC gameplay performance in an effort to continually improve NPC performance, logic, strategy, and/or other NPC characteristics. In some implementations, the player's play profile is monitored over and over in multiple gameplay sessions, and AI engine 128 may fine tune the performance of the NPC each time so that it behaves in a manner more and more consistent with that of the player in its gameplay sessions. In this regard, NPC management engine 124 may, over time, have access to a plurality of NPCs (e.g., stored in database 160) that have been fine-tuned according to the play profile of each player. In implementations wherein a NPC is not saved or stored for later gameplay sessions, AI engine 128 may nonetheless fine tune one or more of the NPC's player profile attributes and save them in a template or model for later use by NPC management engine 124 and or NPC profile engine 126.


In embodiments of the present specification the NPC application 120 is configured as a standalone system component that may interface with multiple game engines. Referring to FIG. 4, the AI engine 422 receives game data 416 and human player data 426 as described above. The AI engine 422 subjects the game data 416 and human player data 426 to one or more artificial engine or machine learning processes 454, including one or more of linear regression, logistic regression, decision trees, naïve Bayes, k-means, random forest, dimensionality reduction algorithms, gradient boosting algorithms, supervised learning, unsupervised learning, or reinforcement learning. In one embodiment the receipt of game data 416 and human player data 426 occurs at a different time or substantially concurrently with the generation of NPC data 446, which is indicative of how the NPC should behave, react, choose, or otherwise act, and/or the supply of the NPC data 346 to more than one server executing different games. The NPC data 446 is then transmitted to one or more game servers 466a, 446b, 446c, 466d using application programming interfaces specific to game servers 466a, 446b, 446c, 466d. The NPC data 446, thereby enabling different game servers executing different games to share the resources of a common NPC generation system.



FIG. 2 illustrates an exemplary flow chart of processing operations for modifying existing NPCs or generating new NPCs in multiplayer video games, in accordance with some embodiments of the present specification. The various processing operations and/or data flows depicted in FIG. 2 are described in greater detail herein. The described operations may be accomplished using some or all of the system components (enabling all of the features and functionality) described in detail above and, in some implementations, various operations may be performed in different sequences and various operations may be omitted. Additional operations may be performed along with some or all of the operations shown in the depicted flow diagrams.


One or more operations may be performed simultaneously. Accordingly, the operations as illustrated (and described in greater detail below) are exemplary by nature and, as such, should not be viewed as limiting.


At 202, at least one player's play profile is tracked. The play profile may track user's play style, performance, skill levels, appearances, or any other information that determines the manner of play by the player. In some embodiments, multiple player's play profiles are tracked simultaneously. In embodiments, each play profile is tracked for the player across all the games played by the player.


At 204, the play profile is monitored for changes to the tracked play profile. The play profile may be monitored on a continuous basis to determine how various game-related factors such as and not limited to game score, time remaining in a match, type of game, and the like, affect the player's play profile. In embodiments, the play profile is monitored continuously from the time of inception of the first game played by the player. In some embodiments, the monitoring is initiated based on a trigger by the player or by NPC application 120, or any other external factor such as since last balance update, from a specific day or time. In some embodiments, the monitoring is performed for a specified period of time, for example a few months.


At 206, one or more NPCs corresponding to the player's play profile are modified in real time or generated by AI engine 128. Initially, in some embodiments, a baseline NPC assigned to the player is developed to mimic the play profile of the user. In some embodiments, the initial attributes of the NPC are not based on any tracked human player attributes and are rather default attributes provided by the game. In other embodiments, the initial attributes of the NPC are based on tracked attributes of a plurality of human players. In other embodiments, the initial attributes of the NPC are based on the attributes of a single tracked human player. Over the course of time and with the player's experience in gaming, the assigned NPC is further modified and improved based on the continuous monitoring performed at 204. According to some implementations, modifying comprises revising scripts that control NPCs. In an example, if player's play profile data indicates that the player generally reacts a certain way given a certain set of conditions, then the system can script the corresponding NPC to react the same way if those conditions arise.


Among multiple application of the embodiments of the present specification, an NPC customized according to a player is available to play in a video game in place of the player's character when the player exits the game, or is in some way not presently engaged in the video game. Therefore, embodiments of the present specification enable player characters to be used as NPCs, for a part of the game. Sometimes, embodiments enables player characters to be used as NPCs for all of the game. This is implemented in cases where the total number of players required are less than those available in the game.


While embodiments of the present specification are described in context of improving NPC performance based on and corresponding to a player's play profile, they may also be applicable to tracking and monitoring multiple players play profiles in order to improve the performance of at least one or more NPCs. In embodiments, a baseline set of NPCs are modified according to a larger data set of players in a game. So over some time period, the system can collect data about how human players actually play, and adjust NPC behavior to reflect the way humans actually play the game.


The various implementations may track and monitor all human players, a subset of human players based on game level, gaming skill, playstyle, or a particular human player such as a star player, or any other type of player specified within NPC application 120.


The above examples are merely illustrative of the many applications of the methods and systems of present specification. Although only a few embodiments of the present invention have been described herein, it should be understood that the present invention might be embodied in many other specific forms without departing from the spirit or scope of the invention. Therefore, the present examples and embodiments are to be considered as illustrative and not restrictive, and the invention may be modified within the scope of the appended claims.

Claims
  • 1. A computer implemented method for generating data representative of one or more non-player characters (NPCs) in one or more multi-player video games, the method being implemented in a host computer having one or more physical processors programmed with programmatic instructions that, when executed by the one or more physical processors, cause the host computer to perform the method, the method comprising: using the host computer, monitoring gameplay sessions of the one or more multi-player video games, wherein the one or more multi-player video games comprises at least a first human player using a weapon in opposition to at least a second human player;using the host computer and based on said monitoring, generating human player data, wherein the human player data represents actions taken by two or more human players in the gameplay sessions of the one or more multi-player video games, wherein the two or more human players comprises at least the first human player and the second human player and wherein the human player data comprising a combination of a weapon usage preference, a frequency at which a player engaged an enemy at a first distance, a frequency at which a player fires a first shot in an engagement, a duration that a player spent in specific areas of a map of a game, and a proximity to teammates;using the host computer and based on said monitoring, generating game data, wherein the game data is representative of one or more game events or game outcomes in the one or more multi-player video games and wherein the game events or game outcomes represent interactions between the two or more human players;applying a neural network or machine learning process to the human player data and the game data;generating data representative of a behavior of the based on an output from the neural network or machine learning process, wherein the behavior of the NPCs comprises decreasing a performance level of the NPCs to be in range with a performance level of a human player or increasing the performance level of the NPCs to be in range with the performance level of the human player and wherein the data representative of the behavior of the NPCs is generated substantially concurrently with at least one of the generation of human player data or the generation of game data;transmitting the data representative of the behavior of the NPCs; andpresenting the NPCs in the one or more video games based on the data representative of the NPCs.
  • 2. The computer implemented method of claim 1, wherein the one or more multi-player video games are of different genres, software platforms, or types.
  • 3. The computer implemented method of claim 1, wherein the data representative of the behavior of the NPCs defines one or more reactions of the NPCs to game events or a movement of the NPCs.
  • 4. The computer implemented method of claim 1, wherein the neural network or machine learning process comprises at least one of a linear regression process, a logistic regression process, a decision tree process, a naïve Bayes process, a k-means process, a random forest process, a dimensionality reduction process, a gradient boosting process, a supervised learning process, an unsupervised learning process, or a reinforcement learning process.
  • 5. The computer implemented method of claim 1, wherein the data representative of the behavior of the NPCs is transmitted to one or more servers, wherein the one or more servers comprise at least two and wherein the one or more multi-player video games are of different genres, software platforms, or types.
  • 6. The computer implemented method of claim 1, wherein the human player data comprises data representative of at least one of a method of playing, a skill level, reactions to one or more game events, or a visual appearance.
  • 7. The computer implemented method of claim 1, wherein the generation of the human player data is triggered by a game score, a time left in one of the one or more multi-player video games, or a game type.
  • 8. The computer implemented method of claim 1, wherein the game data comprises game outcome data, an amount of time a game is played, an amount of virtual resources earned, lost, or exchanged, a score, a time of completion, a number of levels achieved, or metrics indicative of player engagement.
  • 9. A system adapted to generate data representative of one or more non-player characters (NPCs) in one or more multi-player video games, wherein the system has one or more physical processors programmed with programmatic instructions that, when executed by the one or more physical processors, cause the host computer to: monitor gameplay sessions of the one or more multi-player video games, wherein the one or more multi-player video games comprises at least a first human player using a weapon in opposition to at least a second human player;generate human player data, wherein the human player data represents actions taken by two or more human players in the gameplay sessions of the one or more multi-player video games, based on said monitoring, wherein the two or more human players comprises at least the first human player and the second human players, and wherein the human player data comprises a combination of a weapon usage preference, a frequency at which a player engaged an enemy at a first distance, a frequency at which a player fires a first shot in an engagement, a duration that a player spent in specific areas of a map of a game, and a proximity to teammates;generate game data, wherein the game data is representative of one or more game events or game outcomes in the one or more multi-player video games and wherein the game events or game outcomes represent interactions between the two or more human players;apply a neural network or machine learning process to the human player data and the game data;generate data representative of a behavior of the NPCs based on an output from the neural network or machine learning process, wherein the behavior of the NPCs comprises decreasing a performance level of the NPCs to be in range with a performance level of a human player or increasing the performance level of the NPCs to be in range with the performance level of the human player and wherein the data representative of the behavior of the NPCs is generated substantially concurrently with at least one of the generation of human player data or the generation of game data;transmit the data representative of the behavior of the NPCs; andpresent the NPCs in the one or more video games based on the data representative of the NPCs.
  • 10. The system of claim 9, wherein the one or more multi-player video games are of different genres, software platforms, or types.
  • 11. The system of claim 9, wherein the data representative of the behavior of the NPCs defines one or more reactions of the NPCs to game events or a movement of the NPCs.
  • 12. The system of claim 9, wherein the neural network or machine learning process comprises at least one of a linear regression process, a logistic regression process, a decision tree process, a naïve Bayes process, a k-means process, a random forest process, a dimensionality reduction process, a gradient boosting process, a supervised learning process, an unsupervised learning process, or a reinforcement learning process.
  • 13. The system of claim 9, wherein the data representative of the behavior of the NPCs is transmitted to one or more servers, wherein the one or more servers comprise at least two and wherein the one or more multi-player video games are of different genres, software platforms, or types.
  • 14. The system of claim 9, wherein the human player data comprises data representative of at least one of a method of playing, a skill level, reactions to one or more game events, or a visual appearance.
  • 15. The system of claim 9, wherein the generation of the human player data is triggered by a game score, a time left in one of the one or more multi-player video games, or a game type.
  • 16. The system of claim 9, wherein the game data comprises game outcome data, an amount of time a game is played, an amount of virtual resources earned, lost, or exchanged, a score, a time of completion, a number of levels achieved, or metrics indicative of player engagement.
CROSS-REFERENCE

The present application relies on U.S. Patent Provisional Application No. 62/781,568, entitled “Systems and Methods for Generating Improved Non-Player Characters” and filed on Dec. 18, 2018, for priority.

US Referenced Citations (644)
Number Name Date Kind
4461301 Ochs Jul 1984 A
4908761 Tai Mar 1990 A
5031089 Liu Jul 1991 A
5058180 Khan Oct 1991 A
5365360 Torres Nov 1994 A
5371673 Fan Dec 1994 A
5432934 Levin Jul 1995 A
5442569 Osano Aug 1995 A
5493692 Theimer Feb 1996 A
5497186 Kawasaki Mar 1996 A
5530796 Wang Jun 1996 A
5539883 Allon Jul 1996 A
5561736 Moore Oct 1996 A
5563946 Cooper Oct 1996 A
5606702 Diel Feb 1997 A
5630129 Wheat May 1997 A
5685775 Bakoglu Nov 1997 A
5694616 Johnson Dec 1997 A
5706507 Schloss Jan 1998 A
5708764 Borrel Jan 1998 A
5726883 Levine Mar 1998 A
5736985 Lection Apr 1998 A
5736990 Barrus Apr 1998 A
5737416 Cooper Apr 1998 A
5745113 Jordan Apr 1998 A
5745678 Herzberg Apr 1998 A
5758079 Ludwig May 1998 A
5761083 Brown Jun 1998 A
5762552 Vuong Jun 1998 A
5768511 Galvin Jun 1998 A
5774668 Choquier Jun 1998 A
5793365 Tang Aug 1998 A
5825877 Dan Oct 1998 A
5828839 Moncreiff Oct 1998 A
5835692 Cragun Nov 1998 A
5860137 Raz Jan 1999 A
5877763 Berry Mar 1999 A
5878233 Schloss Mar 1999 A
5880731 Liles Mar 1999 A
5883628 Mullaly Mar 1999 A
5900879 Berry May 1999 A
5903266 Berstis May 1999 A
5903271 Bardon May 1999 A
5911045 Leyba Jun 1999 A
5920325 Morgan Jul 1999 A
5920692 Nguyen Jul 1999 A
5920848 Schutzer Jul 1999 A
5923324 Berry Jul 1999 A
5926100 Escolar Jul 1999 A
5933818 Kasravi Aug 1999 A
5938722 Johnson Aug 1999 A
5958014 Cave Sep 1999 A
5969724 Berry Oct 1999 A
5977979 Clough Nov 1999 A
5983003 Lection Nov 1999 A
5990887 Redpath Nov 1999 A
5990888 Blades Nov 1999 A
6006223 Agrawal Dec 1999 A
6008848 Tiwari Dec 1999 A
6009455 Doyle Dec 1999 A
6012096 Link Jan 2000 A
6014145 Bardon Jan 2000 A
6018734 Zhang Jan 2000 A
6021268 Johnson Feb 2000 A
6021496 Dutcher Feb 2000 A
6023729 Samuel Feb 2000 A
6025839 Schell Feb 2000 A
6032129 Greef Feb 2000 A
6049819 Buckle Apr 2000 A
6058266 Megiddo May 2000 A
6059842 Dumarot May 2000 A
6061722 Lipa May 2000 A
6067355 Lim May 2000 A
6069632 Mullaly May 2000 A
6070143 Barney May 2000 A
6076093 Pickering Jun 2000 A
6081270 Berry Jun 2000 A
6081271 Bardon Jun 2000 A
6088727 Hosokawa Jul 2000 A
6088732 Smith Jul 2000 A
6091410 Lection Jul 2000 A
6094196 Berry Jul 2000 A
6098056 Rusnak Aug 2000 A
6101538 Brown Aug 2000 A
6104406 Berry Aug 2000 A
6108420 Larose Aug 2000 A
6111581 Berry Aug 2000 A
6115718 Huberman Sep 2000 A
6134588 Guenthner Oct 2000 A
6138128 Perkowitz Oct 2000 A
6141699 Luzzi Oct 2000 A
6144381 Lection Nov 2000 A
6148294 Beyda Nov 2000 A
6148328 Cuomo Nov 2000 A
6157953 Chang Dec 2000 A
6177932 Galdes Jan 2001 B1
6179713 James Jan 2001 B1
6182067 Presnell Jan 2001 B1
6185614 Cuomo Feb 2001 B1
6195657 Rucker Feb 2001 B1
6199067 Geller Mar 2001 B1
6201881 Masuda Mar 2001 B1
6212494 Boguraev Apr 2001 B1
6212548 Desimone Apr 2001 B1
6216098 Clancey Apr 2001 B1
6222551 Schneider Apr 2001 B1
6226686 Rothschild May 2001 B1
6233583 Hoth May 2001 B1
6249779 Hitt Jun 2001 B1
6266649 Linden Jul 2001 B1
6271842 Bardon Aug 2001 B1
6271843 Lection Aug 2001 B1
6275820 Navin-Chandra Aug 2001 B1
6282547 Hirsch Aug 2001 B1
6293865 Kelly Sep 2001 B1
6301609 Aravamudan et al. Oct 2001 B1
6308208 Jung Oct 2001 B1
6311206 Malkin Oct 2001 B1
6314465 Paul Nov 2001 B1
6330281 Mann Dec 2001 B1
6334127 Bieganski Dec 2001 B1
6334141 Varma Dec 2001 B1
6336134 Varma Jan 2002 B1
6337700 Kinoe Jan 2002 B1
6345264 Breese Feb 2002 B1
6345287 Fong Feb 2002 B1
6349091 Li Feb 2002 B1
6351775 Yu Feb 2002 B1
6353449 Gregg Mar 2002 B1
6356297 Cheng Mar 2002 B1
6360254 Linden Mar 2002 B1
6363174 Lu Mar 2002 B1
6370560 Robertazzi Apr 2002 B1
6396513 Helfman May 2002 B1
6411312 Sheppard Jun 2002 B1
6418424 Hoffberg Jul 2002 B1
6418462 Xu Jul 2002 B1
6426757 Smith Jul 2002 B1
6445389 Bossen Sep 2002 B1
6452593 Challener Sep 2002 B1
6462760 Cox, Jr. Oct 2002 B1
6463078 Engstrom Oct 2002 B1
6466550 Foster Oct 2002 B1
6469712 Hilpert, Jr. Oct 2002 B1
6473085 Brock Oct 2002 B1
6473103 Bailey Oct 2002 B1
6473597 Johnson Oct 2002 B1
6476830 Farmer Nov 2002 B1
6499053 Marquette Dec 2002 B1
6501834 Milewski Dec 2002 B1
6505208 Kanevsky Jan 2003 B1
6509925 Dermler Jan 2003 B1
6525731 Suits Feb 2003 B1
6539415 Mercs Mar 2003 B1
6549933 Barrett Apr 2003 B1
6559863 Megiddo May 2003 B1
6567109 Todd May 2003 B1
6567813 Zhu May 2003 B1
6574477 Rathunde Jun 2003 B1
6580981 Masood Jun 2003 B1
6594673 Smith Jul 2003 B1
6601084 Bhaskaran Jul 2003 B1
6618751 Challenger Sep 2003 B1
6640230 Alexander Oct 2003 B1
6641481 Mai Nov 2003 B1
6645153 Kroll Nov 2003 B2
RE38375 Herzberg Dec 2003 E
6657617 Paolini Dec 2003 B2
6657642 Bardon Dec 2003 B1
6684255 Martin Jan 2004 B1
6717600 Dutta Apr 2004 B2
6734884 Berry May 2004 B1
6742032 Castellani May 2004 B1
6765596 Lection Jul 2004 B2
6781607 Benham Aug 2004 B1
6801930 Dionne Oct 2004 B1
6807562 Pennock Oct 2004 B1
6819669 Rooney Nov 2004 B2
6832239 Kraft Dec 2004 B1
6836480 Basso Dec 2004 B2
6845389 Sen Jan 2005 B1
6854007 Hammond Feb 2005 B1
6886026 Hanson Apr 2005 B1
6901379 Balter May 2005 B1
6941236 Huelsbergen Sep 2005 B2
6948168 Kuprionas Sep 2005 B1
RE38865 Dumarot Nov 2005 E
6970929 Bae Nov 2005 B2
6993596 Hinton Jan 2006 B2
7006616 Christofferson Feb 2006 B1
7028296 Irfan Apr 2006 B2
7031473 Morais Apr 2006 B2
7050868 Graepel May 2006 B1
7062533 Brown Jun 2006 B2
7089266 Stolte Aug 2006 B2
7124071 Rich Oct 2006 B2
7124164 Chemtob Oct 2006 B1
7139792 Mishra Nov 2006 B1
7143409 Herrero Nov 2006 B2
7159217 Pulsipher Jan 2007 B2
7185067 Viswanath Feb 2007 B1
7192352 Walker Mar 2007 B2
7209137 Brokenshire Apr 2007 B2
7230616 Taubin Jun 2007 B2
7240093 Danieli Jul 2007 B1
7249123 Elder Jul 2007 B2
7263511 Bodin Aug 2007 B2
7278108 Duarte Oct 2007 B2
7287053 Bodin Oct 2007 B2
7292870 Heredia Nov 2007 B2
7305438 Christensen Dec 2007 B2
7308476 Mannaru Dec 2007 B2
7314411 Lannert Jan 2008 B2
7328242 McCarthy Feb 2008 B1
7353295 Crow Apr 2008 B1
7376474 Graepel May 2008 B2
7383307 Kirkland Jun 2008 B2
7404149 Fox Jul 2008 B2
7426538 Bodin Sep 2008 B2
7427980 Partridge Sep 2008 B1
7428588 Berstis Sep 2008 B2
7429987 Leah Sep 2008 B2
7436407 Doi Oct 2008 B2
7439975 Hsu Oct 2008 B2
7443393 Shen Oct 2008 B2
7447996 Cox Nov 2008 B1
7467180 Kaufman Dec 2008 B2
7467181 McGowan Dec 2008 B2
7475354 Guido Jan 2009 B2
7478127 Creamer Jan 2009 B2
7484012 Hinton Jan 2009 B2
7503007 Goodman Mar 2009 B2
7506264 Polan Mar 2009 B2
7509388 Allen Mar 2009 B2
7515136 Kanevsky Apr 2009 B1
7525964 Astley Apr 2009 B2
7527191 Takayama May 2009 B2
7552177 Kessen Jun 2009 B2
7565650 Bhogal Jul 2009 B2
7571224 Childress Aug 2009 B2
7571389 Broussard Aug 2009 B2
7580888 Ur Aug 2009 B2
7590984 Kaufman Sep 2009 B2
7596596 Chen Sep 2009 B2
7614955 Farnham Nov 2009 B2
7617283 Aaron Nov 2009 B2
7640587 Fox Dec 2009 B2
7667701 Leah Feb 2010 B2
7677970 O'Kelley, II Mar 2010 B2
7698656 Srivastava Apr 2010 B2
7702730 Spataro Apr 2010 B2
7702784 Berstis Apr 2010 B2
7714867 Doi May 2010 B2
7719532 Schardt May 2010 B2
7719535 Tadokoro May 2010 B2
7734691 Creamer Jun 2010 B2
7737969 Shen Jun 2010 B2
7743095 Goldberg Jun 2010 B2
7747679 Galvin Jun 2010 B2
7765478 Reed Jul 2010 B2
7768514 Pagan Aug 2010 B2
7770114 Sriprakash Aug 2010 B2
7773087 Fowler Aug 2010 B2
7774407 Daly Aug 2010 B2
7780525 Walker Aug 2010 B2
7782318 Shearer Aug 2010 B2
7792263 D Amora Sep 2010 B2
7792801 Hamilton, II Sep 2010 B2
7796128 Radzikowski Sep 2010 B2
7808500 Shearer Oct 2010 B2
7814152 McGowan Oct 2010 B2
7827318 Hinton Nov 2010 B2
7843471 Doan Nov 2010 B2
7844663 Boutboul Nov 2010 B2
7844673 Bostick Nov 2010 B2
7846024 Graepel Dec 2010 B2
7847799 Taubin Dec 2010 B2
7853594 Elder Dec 2010 B2
7856469 Chen Dec 2010 B2
7865393 Leason Jan 2011 B2
7873485 Castelli Jan 2011 B2
7882222 Dolbier Feb 2011 B2
7882243 Ivory Feb 2011 B2
7884819 Kuesel Feb 2011 B2
7886045 Bates Feb 2011 B2
7890623 Bates Feb 2011 B2
7893936 Shearer Feb 2011 B2
7904829 Fox Mar 2011 B2
7921128 Hamilton, II Apr 2011 B2
7940265 Brown May 2011 B2
7945620 Bou-Ghannam May 2011 B2
7945802 Hamilton, II May 2011 B2
7955171 Jorasch Jun 2011 B2
7970837 Lyle Jun 2011 B2
7970840 Cannon Jun 2011 B2
7985132 Walker Jul 2011 B2
7985138 Acharya Jul 2011 B2
7990387 Hamilton, II Aug 2011 B2
7996164 Hamilton, II Aug 2011 B2
7997987 Johnson Aug 2011 B2
8001161 George Aug 2011 B2
8004518 Fowler Aug 2011 B2
8005025 Bodin Aug 2011 B2
8006182 Bates Aug 2011 B2
8013861 Hamilton, II Sep 2011 B2
8018453 Fowler Sep 2011 B2
8018462 Bhogal Sep 2011 B2
8019797 Hamilton, II Sep 2011 B2
8019858 Bauchot Sep 2011 B2
8022948 Garbow Sep 2011 B2
8022950 Brown Sep 2011 B2
8026913 Garbow Sep 2011 B2
8028021 Reisinger Sep 2011 B2
8028022 Brownholtz Sep 2011 B2
8037416 Bates Oct 2011 B2
8041614 Bhogal Oct 2011 B2
8046700 Bates Oct 2011 B2
8051462 Hamilton, II Nov 2011 B2
8055656 Cradick Nov 2011 B2
8056121 Hamilton, II Nov 2011 B2
8057307 Berstis Nov 2011 B2
8062130 Smith Nov 2011 B2
8063905 Brown Nov 2011 B2
8070601 Acharya Dec 2011 B2
8082245 Bates Dec 2011 B2
8085267 Brown Dec 2011 B2
8089481 Shearer Jan 2012 B2
8092288 Theis Jan 2012 B2
8095881 Reisinger Jan 2012 B2
8099338 Betzler Jan 2012 B2
8099668 Garbow Jan 2012 B2
8102334 Brown Jan 2012 B2
8103640 Lo Jan 2012 B2
8103959 Cannon Jan 2012 B2
8105165 Karstens Jan 2012 B2
8108774 Finn Jan 2012 B2
8113959 De Judicibus Feb 2012 B2
8117551 Cheng Feb 2012 B2
8125485 Brown Feb 2012 B2
8127235 Haggar Feb 2012 B2
8127236 Hamilton, II Feb 2012 B2
8128487 Hamilton, II Mar 2012 B2
8131740 Cradick Mar 2012 B2
8132235 Bussani Mar 2012 B2
8134560 Bates Mar 2012 B2
8139060 Brown Mar 2012 B2
8139780 Shearer Mar 2012 B2
8140340 Bhogal Mar 2012 B2
8140620 Creamer Mar 2012 B2
8140978 Betzler Mar 2012 B2
8140982 Hamilton, II Mar 2012 B2
8145676 Bhogal Mar 2012 B2
8145725 Dawson Mar 2012 B2
8149241 Do Apr 2012 B2
8151191 Nicol, II Apr 2012 B2
8156184 Kurata Apr 2012 B2
8165350 Fuhrmann Apr 2012 B2
8171407 Huang May 2012 B2
8171408 Dawson May 2012 B2
8171559 Hamilton, II May 2012 B2
8174541 Greene May 2012 B2
8176421 Dawson May 2012 B2
8176422 Bergman May 2012 B2
8184092 Cox May 2012 B2
8184116 Finn May 2012 B2
8185450 McVey May 2012 B2
8185829 Cannon May 2012 B2
8187067 Hamilton, II May 2012 B2
8199145 Hamilton, II Jun 2012 B2
8203561 Carter Jun 2012 B2
8214335 Hamilton, II Jul 2012 B2
8214433 Dawson Jul 2012 B2
8214750 Hamilton, II Jul 2012 B2
8214751 Dawson Jul 2012 B2
8217953 Comparan Jul 2012 B2
8219616 Dawson Jul 2012 B2
8230045 Kawachiya Jul 2012 B2
8230338 Dugan Jul 2012 B2
8233005 Finn Jul 2012 B2
8234234 Shearer Jul 2012 B2
8234579 Do Jul 2012 B2
8239775 Beverland Aug 2012 B2
8241131 Bhogal Aug 2012 B2
8245241 Hamilton, II Aug 2012 B2
8245283 Dawson Aug 2012 B2
8265253 D Amora Sep 2012 B2
8310497 Comparan Nov 2012 B2
8313364 Reynolds Nov 2012 B2
8334871 Hamilton, II Dec 2012 B2
8360886 Karstens Jan 2013 B2
8364804 Childress Jan 2013 B2
8425326 Chudley Apr 2013 B2
8442946 Hamilton, II May 2013 B2
8489925 Antukh Jul 2013 B1
8496531 Youm Jul 2013 B2
8506372 Chudley Aug 2013 B2
8514249 Hamilton, II Aug 2013 B2
8554841 Kurata Oct 2013 B2
8607142 Bergman Dec 2013 B2
8607356 Hamilton, II Dec 2013 B2
8624903 Hamilton, II Jan 2014 B2
8626836 Dawson Jan 2014 B2
8692835 Hamilton, II Apr 2014 B2
8696465 Gatto Apr 2014 B2
8721412 Chudley May 2014 B2
8827816 Bhogal Sep 2014 B2
8838640 Bates Sep 2014 B2
8849917 Dawson Sep 2014 B2
8911296 Chudley Dec 2014 B2
8992316 Smith Mar 2015 B2
9083654 Dawson Jul 2015 B2
9152914 Haggar Oct 2015 B2
9205328 Bansi Dec 2015 B2
9286731 Hamilton, II Mar 2016 B2
9299080 Dawson Mar 2016 B2
9364746 Chudley Jun 2016 B2
9525746 Bates Dec 2016 B2
9583109 Kurata Feb 2017 B2
9682324 Bansi Jun 2017 B2
9764244 Bansi Sep 2017 B2
9789406 Marr Oct 2017 B2
9795887 Lin Oct 2017 B2
9808722 Kawachiya Nov 2017 B2
9827488 Pearce Nov 2017 B2
9942013 Malladi Apr 2018 B2
10118099 Condrey Nov 2018 B2
10402731 Cosic Sep 2019 B1
20010025253 Heintz Sep 2001 A1
20010032240 Malone Oct 2001 A1
20010049301 Masuda Dec 2001 A1
20020002514 Kamachi Jan 2002 A1
20020007319 Yu Jan 2002 A1
20020026388 Roebuck Feb 2002 A1
20020035480 Gordon Mar 2002 A1
20020035593 Salim Mar 2002 A1
20020043568 Hess Apr 2002 A1
20020065870 Baehr-Jones May 2002 A1
20020090995 Haga Jul 2002 A1
20020095586 Doyle Jul 2002 A1
20020096831 Nakayama Jul 2002 A1
20020097856 Wullert Jul 2002 A1
20020116466 Trevithick Aug 2002 A1
20020124137 Ulrich Sep 2002 A1
20020130904 Becker Sep 2002 A1
20020135618 Maes Sep 2002 A1
20020169665 Hughes Nov 2002 A1
20020184373 Maes Dec 2002 A1
20020184391 Phillips Dec 2002 A1
20020188688 Bice Dec 2002 A1
20030008712 Poulin Jan 2003 A1
20030014297 Kaufman Jan 2003 A1
20030032476 Walker Feb 2003 A1
20030050977 Puthenkulam Mar 2003 A1
20030055892 Huitema Mar 2003 A1
20030056002 Trethewey Mar 2003 A1
20030076353 Blackstock Apr 2003 A1
20030101343 Eaton May 2003 A1
20030112952 Brown Jun 2003 A1
20030135621 Romagnoli Jul 2003 A1
20030141977 Brown Jul 2003 A1
20030145128 Baird Jul 2003 A1
20030149675 Ansari Aug 2003 A1
20030158827 Ansari Aug 2003 A1
20030177187 Levine Sep 2003 A1
20030195957 Banginwar Oct 2003 A1
20030210265 Haimberg Nov 2003 A1
20040014514 Yacenda Jan 2004 A1
20040054667 Kake Mar 2004 A1
20040059781 Yoakum Mar 2004 A1
20040078432 Manber Apr 2004 A1
20040078596 Kent Apr 2004 A1
20040088303 Elder May 2004 A1
20040097287 Postrel May 2004 A1
20040103079 Tokusho May 2004 A1
20040113756 Mollenkopf Jun 2004 A1
20040127277 Walker Jul 2004 A1
20040128181 Zurko Jul 2004 A1
20040172339 Snelgrove Sep 2004 A1
20040174392 Bjoernsen Sep 2004 A1
20040186886 Galli et al. Sep 2004 A1
20040205134 Digate Oct 2004 A1
20040210627 Kroening Oct 2004 A1
20040228291 Huslak Nov 2004 A1
20040244006 Kaufman Dec 2004 A1
20040260771 Gusler et al. Dec 2004 A1
20050015571 Kaufman Jan 2005 A1
20050021484 Bodin Jan 2005 A1
20050027696 Swaminathan Feb 2005 A1
20050043097 March Feb 2005 A1
20050050137 Bodin Mar 2005 A1
20050060368 Wang Mar 2005 A1
20050071428 Khakoo Mar 2005 A1
20050071462 Bodin Mar 2005 A1
20050080859 Lake Apr 2005 A1
20050085296 Gelb Apr 2005 A1
20050091380 Gonen Apr 2005 A1
20050097440 Lusk May 2005 A1
20050113164 Buecheler May 2005 A1
20050132009 Solie Jun 2005 A1
20050138108 Galvin Jun 2005 A1
20050149620 Kirkland Jul 2005 A1
20050161878 Nally Jul 2005 A1
20050165893 Feinberg Jul 2005 A1
20050216346 Kusumoto Sep 2005 A1
20050223075 Swearingen et al. Oct 2005 A1
20050246711 Berstis Nov 2005 A1
20050277472 Gillan Dec 2005 A1
20060003305 Kelmar Jan 2006 A1
20060004659 Hutchison Jan 2006 A1
20060026253 Kessen Feb 2006 A1
20060031322 Kessen Feb 2006 A1
20060031326 Ovenden Feb 2006 A1
20060036688 McMahan Feb 2006 A1
20060080702 Diez Apr 2006 A1
20060121990 O'Kelley Jun 2006 A1
20060128460 Muir Jun 2006 A1
20060129643 Nielson Jun 2006 A1
20060155813 Dietz et al. Jul 2006 A1
20060160589 Okada Jul 2006 A1
20060161852 Chen Jul 2006 A1
20060178968 Jung Aug 2006 A1
20060184260 Graepel Aug 2006 A1
20060190591 Bobde Aug 2006 A1
20060252526 Walker Nov 2006 A1
20060258463 Cugno Nov 2006 A1
20070026934 Herbrich Feb 2007 A1
20070066403 Conkwright Mar 2007 A1
20070073582 Jung Mar 2007 A1
20070087799 Van Luchene Apr 2007 A1
20070106526 Jung May 2007 A1
20070111789 Van Deursen May 2007 A1
20070112624 Jung May 2007 A1
20070112706 Herbrich May 2007 A1
20070117623 Nelson May 2007 A1
20070117636 Takahashi May 2007 A1
20070130001 Jung Jun 2007 A1
20070168444 Chen Jul 2007 A1
20070168447 Chen Jul 2007 A1
20070173323 Johnson Jul 2007 A1
20070180040 Etgen Aug 2007 A1
20070218997 Cho Sep 2007 A1
20070260567 Funge Nov 2007 A1
20070265718 Graepel Nov 2007 A1
20070281285 Jayaweera Dec 2007 A1
20070298867 Huang Dec 2007 A1
20080019353 Foote Jan 2008 A1
20080059304 Kimsey Mar 2008 A1
20080064467 Reiner Mar 2008 A1
20080113815 Weingardt May 2008 A1
20080120558 Nathan May 2008 A1
20080126350 Shoemaker May 2008 A1
20080155019 Wallace Jun 2008 A1
20080176655 James Jul 2008 A1
20080207329 Wallace Aug 2008 A1
20080214287 Lutnick Sep 2008 A1
20080242420 Graepel Oct 2008 A1
20080254893 Patel Oct 2008 A1
20080268943 Jacob Oct 2008 A1
20080270605 Berstis Oct 2008 A1
20080270916 Chen Oct 2008 A1
20080274805 Ganz Nov 2008 A1
20080301405 Kaufman Dec 2008 A1
20090005172 Shibahara Jan 2009 A1
20090075738 Pearce Mar 2009 A1
20090088233 O'Rourke Apr 2009 A1
20090113448 Smith Apr 2009 A1
20090118006 Kelly May 2009 A1
20090137320 Kimura May 2009 A1
20090209335 Pearce Aug 2009 A1
20090253494 Fitch Oct 2009 A1
20090280909 McEniry Nov 2009 A1
20090318223 Langridge Dec 2009 A1
20090325711 Bronstein Dec 2009 A1
20100131864 Bokor May 2010 A1
20100169800 Lance Jul 2010 A1
20100173701 Van Luchene Jul 2010 A1
20100173713 Van Luchene Jul 2010 A1
20100203963 Allen Aug 2010 A1
20100267450 McMain Oct 2010 A1
20100304839 Johnson Dec 2010 A1
20100306672 McEniry Dec 2010 A1
20100312995 Sung Dec 2010 A1
20110092279 Pilip Apr 2011 A1
20110131085 Wey Jun 2011 A1
20110190063 Kajii Aug 2011 A1
20110212762 Ocko Sep 2011 A1
20120009997 Youm Jan 2012 A1
20120010734 Youm Jan 2012 A1
20120015736 Vanbragt Jan 2012 A1
20120021823 Youm Jan 2012 A1
20120021825 Harp Jan 2012 A1
20120064968 Youm Mar 2012 A1
20120094751 Reynolds Apr 2012 A1
20120122552 Youm May 2012 A1
20120190456 Rogers Jul 2012 A1
20120315993 Dumont Dec 2012 A1
20130225260 Cudak Aug 2013 A1
20130252737 Mescon Sep 2013 A1
20130260876 Margalith Oct 2013 A1
20130266927 Mann Oct 2013 A1
20130296046 Mianji Nov 2013 A1
20140004955 Nahari Jan 2014 A1
20140004960 Soti Jan 2014 A1
20140011595 Muller Jan 2014 A1
20140024445 Aller Jan 2014 A1
20140162763 Kim Jun 2014 A1
20140162781 Butler Jun 2014 A1
20140274402 Michel Sep 2014 A1
20140342808 Chowdhary Nov 2014 A1
20140344725 Bates Nov 2014 A1
20140349753 Lmai Nov 2014 A1
20150031426 Alloway Jan 2015 A1
20150038233 Rom Feb 2015 A1
20150051000 Henn Feb 2015 A1
20150310698 Polis Oct 2015 A1
20160001181 Marr Jan 2016 A1
20160001182 Marr Jan 2016 A1
20160001186 Marr Jan 2016 A1
20160005270 Marr Jan 2016 A1
20160067611 Ware Mar 2016 A1
20160067612 Ntoulas Mar 2016 A1
20160166935 Condrey Jun 2016 A1
20160191671 Dawson Jun 2016 A1
20160296840 Kaewell Oct 2016 A1
20170206797 Solomon Jul 2017 A1
20170279719 Faith Sep 2017 A1
20180169515 Rice Jun 2018 A1
20180280806 Otomo Oct 2018 A1
20180308473 Scholar Oct 2018 A1
20190043239 Goel Feb 2019 A1
20190081848 Zou Mar 2019 A1
20190118078 Li Apr 2019 A1
20190126150 Tartaj May 2019 A1
20190164007 Liu May 2019 A1
20190184286 Du Jun 2019 A1
20190197402 Kovács Jun 2019 A1
20190205727 Lin Jul 2019 A1
20190295306 Weston Sep 2019 A1
20190340419 Milman Nov 2019 A1
20200122038 Ebrahimi Apr 2020 A1
20200122040 Juliani, Jr. Apr 2020 A1
20200145615 Seko May 2020 A1
20200372400 Carreira-Perpiñán Nov 2020 A1
20200401576 Yerli Dec 2020 A1
Foreign Referenced Citations (93)
Number Date Country
768367 Mar 2004 AU
2005215048 Oct 2011 AU
2143874 Jun 2000 CA
2292678 Jul 2005 CA
2552135 Jul 2013 CA
1334650 Feb 2002 CN
1202652 Oct 2002 CN
1141641 Mar 2004 CN
1494679 May 2004 CN
1219384 Sep 2005 CN
1307544 Mar 2007 CN
100407675 Jul 2008 CN
100423016 Oct 2008 CN
100557637 Nov 2009 CN
101001678 May 2010 CN
101436242 Dec 2010 CN
101801482 Dec 2014 CN
668583 Aug 1995 EP
0627728 Sep 2000 EP
0717337 Aug 2001 EP
1207694 May 2002 EP
1209849 May 2002 EP
0679977 Oct 2002 EP
0679978 Mar 2003 EP
0890924 Sep 2003 EP
1377902 Aug 2004 EP
0813132 Jan 2005 EP
1380133 Mar 2005 EP
1021021 Sep 2005 EP
0930584 Oct 2005 EP
0883087 Aug 2007 EP
1176828 Oct 2007 EP
2076888 Jul 2015 EP
2339938 Oct 2002 GB
2352154 Jul 2003 GB
H11191097 Apr 1999 JP
11191097 Jul 1999 JP
3033956 Apr 2000 JP
3124916 Jan 2001 JP
2001119403 Apr 2001 JP
3177221 Jun 2001 JP
2001204973 Jul 2001 JP
3199231 Aug 2001 JP
2001230883 Aug 2001 JP
3210558 Sep 2001 JP
3275935 Feb 2002 JP
3361745 Jan 2003 JP
3368188 Jan 2003 JP
3470955 Sep 2003 JP
3503774 Dec 2003 JP
2004062539 Feb 2004 JP
3575598 Jul 2004 JP
3579823 Jul 2004 JP
3579154 Oct 2004 JP
3701773 Oct 2005 JP
3777161 Mar 2006 JP
3914430 Feb 2007 JP
3942090 Apr 2007 JP
3962361 May 2007 JP
4009235 Sep 2007 JP
4225376 Dec 2008 JP
4653075 Dec 2010 JP
5063698 Aug 2012 JP
5159375 Mar 2013 JP
5352200 Nov 2013 JP
5550720 Jul 2014 JP
2015002839 Jan 2015 JP
5734566 Jun 2015 JP
20020038229 May 2002 KR
20030039019 May 2003 KR
117864 Aug 2004 MY
55396 Dec 1998 SG
424213 Mar 2001 TW
527825 Apr 2003 TW
0060444 Oct 2000 WO
0062231 Oct 2000 WO
0137162 May 2001 WO
0201455 Jan 2002 WO
0203645 Jan 2002 WO
2002073457 Sep 2002 WO
20020087156 Oct 2002 WO
03044755 May 2003 WO
03049459 Jun 2003 WO
03058518 Jul 2003 WO
2004086212 Oct 2004 WO
2005079538 Sep 2005 WO
2007101785 Sep 2007 WO
2008037599 Apr 2008 WO
2008074627 Jun 2008 WO
2008095767 Aug 2008 WO
2009037257 Mar 2009 WO
2009104564 Aug 2009 WO
2010096738 Aug 2010 WO
Non-Patent Literature Citations (27)
Entry
Ma et al., “A Scalable Parallel Cell-Projection Volume Rendering Algorithm for Three-Dimensional Unstructured Data”, IEEE 1997, pp. 1-10.
Hassen et al., “A Task-and Data-Parallel Programming Language Based on Shared Objects,” ACM Transactions on Programming Languages and Systems, vol. 20, No. 6, Nov. 1998, pp. 1131-1170.
Y. Zhao et al., “A 3D virtual shopping mall that has the intelligent virtual purchasing guider and cooperative purchasing functionalities”, CSCWD 2004—8th International Conference on Computer Supported Cooperative Work in Design—Proceedings, 2004, p. 381-385.
V. Stojanovic, “Virtual boutique—try clothes on-line”, 5th International Conference on Telecommunications in Modern Satellite, Cable and Broadcasting Service. TELSIKS 2001. Proceedings of Papers (Cat. No. 01EX517), 2001, pt. 2, p. 802-3 vol.2.
Kautz, H., B. Selman, M. Shah.. “Referral Web: Combining Social Networks and Collaborative Filtering”. Communications of the ACM, vol. 40, No. 3, Mar. 1997.
Schwartz, M. F., D. C. M. Wood. “Discovering shared interests among people using graph analysis of global electronic mail traffic”. Department of Computer Science, University of Colorado, Boulder CO, Oct. 1992.
Wellman, B. “For a social network analysis of computer networks: a sociological perspective on collaborative work and virtual community”. Proceedings of the 1996 conference on ACM SIGCPR/SIGMIS. 1-11.
Qureshi, S. “Supporting electronic group processes: a social perspective”. Proceedings of the 1995 ACM SIGCPR Conference on Supporting teams, groups, and learning inside the IS function. ACM Press. 24-34.
Ackerman, M.S., B. Starr. “Social activity indicators: interface components for CSCWsystems”. Proceedings of the Sth ACM Symposium on User Interface and Software Technology. ACM Press. 159-168, Nov. 14-17, 1995.
Garton, L., C. Haythornthwaite, B. Wellman. “Studying on-line social networks in Doing Internet Research”, Jun. 1997.
Srivastava, Jaidepp, Robert Cooley, Mukund Deshpande, Pang-Ning Tan. “Web Usage Mining: Discovery and Applications of Usage Patterns from Web Data”. SIGKDD Explorations, vol. 1, Issue 2. Jan. 2000. 12-23.
Wang, Y. “Web Mining and Knowledge Discovery of Usage Patterns”. CS748T Project (Part I) Feb. 2000.
Sack, W. “Conversation Map: a content-based Usenet newsgroup browser”. Proceedings of the 2000 International Conference on Intelligent User Interfaces. ACM Press. 233-240.
Feldman, R. “Mining unstructured data”. Tutorial notes for ACK SIGKDD 1999. ACM Press. 182-236.
International Search Report as Published as WO2005/079538 in corresponding international application No. PCT/US2005/005550, dated Jul. 5, 2006.
IBM developer Works, OptimalGrid—autonomic computing on the Grid, James H. Kaufman; Tobin J. Lehman; Glenn Deen; and John Thomas, Jun. 2003.
IBM, Transcoding: Extending e-business to new environments, Britton et al., Sep. 22, 2000.
Duong et al.; “A dynamic load sharing algorithm for massivly multiplayer online games” published Sep. 28, 2003-Oct. 1, 2003.http://ieeexplore.ieee.org/iel5/8945/28322/01266179.pdf?tp=&arnumber-=1266179&isnumber=28322http://ieeexplore.ieee.org/xpl/absprintf.jsp7arnumb- er=1266179.
“A multi-server architecture for distributed virtual walkthrough” http://delivery.acm.org/10.1145/590000/585768/p163-ng.pdf?key1=585768&key-2=0554824911&coll=GUIDE&dl=GUIDE&CFID=41712537&CFTOKEN=50783297. Nov. 11, 2002.
Mauve, M., Fischer, S., and Widmer, J. 2002. A generic proxy system for networked computer games. In Proceedings of the 1st Workshop on Network and System Support for Games (Braunschweig, Germany, Apr. 16-17, 2002). NetGames '02. ACM, New York, NY, 25-28. DOI= http://doi.acm.org/10.1145/566500.566504.
Lee et al., “A Self-Adjusting Data Distribution Mechanism for Multidimensional Load Balancing in Multiprocessor-Based Database Systems,” Information Systems vol. 19, No. 7, pp. 549-567, 1994.
Feng et al., “A Parallel Hierarchical Radiosity Algorithm for Complex Scenes,” Proceedings IEEE Symposium on Parallel Rendering (PRS) '97), IEEE Computer Society Technical Committee on Computer Graphics in cooperation with ACM SIGGRAPH pp. 71-79, 1997.
Andert, “A Simulation of Dynamic Task Allocation in a Distributed Computer System,” Proceedings of the 1987 Winter Simulation Conference, 1987, pp. 1-9.
Roaming Virtual World Is a Real Trip; [Final Edition] Leslie Walker. The Washington Post. Washington, D.C.: Mar. 30, 2006.
E-Entrepreneurship: Learning in a Simulated Environment Salim Jiwa, Dawn Lavelle, Arjun Rose. Journal of Electronic Commerce in Organizations. Hershey: Jul.-Sep. 2005. vol. 3, Iss. 3.
“Universally Unique Identifier”, 2006 (http://en.wikipedia.org/wiki/UUID).
K. Loesing et al., “Privacy-aware presence management in instant messaging systems”, Distributed & Mobile Syst. Group, Otto-Friedrich-Univ. Germany, Proceedings. 20th International Parallel and Distributed Processing Symposium Rhodes Island, Greece; (IEEE Cat. No. 06TH8860), 2006, 8 pp.
Related Publications (1)
Number Date Country
20200197811 A1 Jun 2020 US
Provisional Applications (1)
Number Date Country
62781568 Dec 2018 US