Patent Application
20190262712
Aspects of the subject technology relate to an online gaming platform, and in particular, to a platform for facilitating user creation of customizable gaming channels for viewing competitive game-play.
Like any popular competitive activity, such as football, card games and board games, online games have a large following of fans that appreciate competitive games and highly skilled players. As with other games, such fans also enjoy structured competition amongst peers of comparable skill level. For example, by encouraging a competitive atmosphere amongst peers, fantasy sports leagues and competitions have become a widespread activity. While fantasy leagues for a variety of sports are now widely available, comparable leagues for online games are not readily available for non-professional players.
Embodiments of the claimed invention include methods and systems for managing an online gaming league and in particular, for enabling customizable channels for viewing competitive game-play. Such systems can include a network interface configured to receive event attributes that define information about gaming titles and game environment pre-conditions that are required to initiate video streaming of an associated game-play, for example, into a user-curated gaming channel. In some aspects, one or more processors of such systems can be configured to execute operations to perform steps for receiving a first set of event attributes from a first user, the first set of event attributes comprising information identifying a first game title and a first game-play event associated with the first game title, monitoring play of the first game title by a second user to detect occurrence of the game-play event, and automatically providing a video stream of the first game title to the first user in response to a detected occurrence of the first game-play event.
Certain features of the subject technology are set forth in the appended claims. However, the accompanying drawings, which are included to provide further understanding, illustrate disclosed aspects and together with the description serve to explain the principles of the subject technology. In the drawings:
The detailed description set forth below is intended as a description of various configurations of the subject technology and is not intended to represent the only configurations in which the technology can be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a more thorough understanding of the technology. However, it will be clear and apparent that the technology is not limited to the specific details set forth herein and may be practiced without these details. In some instances, structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject technology.
Competitive gaming, commonly referred to as electronic sports or “eSports,” involve the play of video games in a competitive environment. Videogame competitions have existed for nearly as long as video games themselves. Early competitions were set up as tournament style matches between players focused on one particular game, often tied to a new product release. Eventually, competitive leagues and a constant stream of tournaments evolved to provide structure for the eSports community. Players now have the option of competing in a vast array of professional and amateur competitions held at physical locations or in virtual competitions conducted online. Leagues and content providers such as Major League Gaming (MLG), and Global StarCraft® League, provide opportunities for competition and to find information about competitive gaming. Until recently, participation in competitive gaming has demonstrated a gradual and steady pace in growth. However, competitive gaming is presently undergoing a rapid expansion in participation and interest.
Unlike fantasy gaming leagues, such as fantasy football, non-professional players of online games have limited ability to create and manage their own leagues in which players a similar skill level can compete. Online gamers often lack access to a centralized platform that can be readily configured to perform player rankings, or than can enable users to make easy comparisons between different players or different game titles on the basis of user-defined statistical criteria. Additionally, gamers (e.g., users/players) are often spectators of games played by both professional and non-professionals, but lack the ability to filter available gaming video feeds based on their own criteria.
The subject technology addresses the foregoing limitations by providing a gaming league platform that facilitates the creation and management of customized gaming leagues, as well as dashboards to enable players to define statistical criteria for selecting video feeds for games that wish to watch.
In some aspects, the gaming platform can enable player-spectators to define event attributes that can be used to filter available gaming feeds. In some aspects, filtered gaming feeds can be curated to form gaming channels that are available to subscribing users/players. As used herein, event attributes can include any type of game identifying information (e.g., title names or versions), as well as player identifying information (e.g., player names or online handles), associated with competitive gameplay. Event attributes can also include statistical parameters or pre-conditions that can be used to filter what gaming feeds (video feeds) are captured and provided.
By way of example, event attribute information can be provided to the gaming platform using a dashboard. Event attribute information can identify one or more game titles, one or more game players, and/or one or more statistical parameters that are pre-conditions for video capture and streaming. As such, players can conveniently “flag” potentially interesting game events, player bouts, or other phenomena in an online gaming environment for capture and viewing. Such features can enable players to tune into potentially interesting gaming events while they are happening (in real time), or to capture interesting events for later viewing. In some aspects, players may combine feeds from multiple different games that are played either concurrently or asynchronously to create content channels based on their own pre-defined criteria. By way of example, user defined event attribute information can be used to create gaming mashups, such as to enable a user to watch a speed run versus a pitcher's duel versus a pugilistic battle, e.g., to create customized game streaming channels that would not otherwise have been available.
In some aspects, user selected gaming feeds can be re-run or re-rendered, e.g., to provide the consuming user with a preferred viewing angle or other perspectives with which to select and view interesting game events.
Public network 102, and gaming network 104 provide player and developer access to league management system 112. As illustrated, players 108, 109, and 110 are permitted access to league management system 112 using respective client devices (e.g., 108A, 109A, and 110A). Although client devices 108A, 109A, and 110A, are depicted as personal computing devices, it is understood that the client devices can include various types of processor-based systems, including but not limited to: game consoles, smart phones, tablet computer systems, and the like. Example of hardware systems that can be used to implement the client device are discussed in further detail below with respect to
It is understood that a greater (or fewer) number of players and/or developers can be engaged with environment 100, without departing from the scope of the technology.
In practice, management system 112 is configured to create and support tournament style competitions between various players and for multiple different game titles, and to provide the interfaces (dashboard) necessary to enable users/players to define parameters for game capture and playback. As such, management system 112 is configured to facilitate player competition across game genres, as well as to facilitate the selection, capture and distribution of competitive gameplay events.
Because the metrics that are used to evaluate player performance for a particular game can vary widely between game title and type, in some aspects, game developers are encouraged to provide an indication of the specific game-performance attributes that should be used to evaluate player performance for the developer's game.
By way of example, developers 105, 106, and/or 107 can be developers of different game titles, each of which is associated with a different genre. To facilitate league competition for their games, each of the developers can submit game-performance attributes to the league, e.g., using respective computing systems 105A, 106A, and 107A. In a similar manner, the creation of gaming leagues and corresponding league parameters can be managed at the player level, for example, by one or more of players 108, 109, and/or 110. That is, individual players or player collectives can provide specific game-performance attributes that they would like implemented to structure their own individualized league play.
Although game-performance attributes can include virtually any type of information that can be used in conjunction with the creation, execution, management, and/or promotion of a gaming league, in some aspects, game-performance attribute information can include game characteristics, including but not limited to one or more of: a “match type,” “event information,” and/or a player access list, etc. Game attributes information can also include game statistics, including but not limited to “high-level” player statistics such as: win/loss records, play time duration, levels achieved, points scored, and/or an ELO rating, etc. In some aspects, game statistics include “low-level” player statistics, including but not limited to: map-position information, map-path information, shots fired, time with rifle, time in kneel, time running, time to first fix, time to acquire a target, (e.g., “quick-draw” metrics), and/or measures of player/avatar health, etc.
The game-performance attributes, including game characteristics and game-play statistics can be received and recorded by league management system 112, for example, using an application programming interface (API), such as API 114. Subsequently, the game-performance attributes can be passed from API 114 to statistics module 116 for use in player analysis. In a similar manner, game-play statistics can be collected by API 114 and passed to statistics module 116.
Depending on implementation, game-play statistics can be collected via active monitoring of an online game environment, or received from one or more external systems, for example, as part of a game performance data set that includes information describing individual player performance for one or more game titles and/or genre categories.
As discussed above, monitoring of a game environment (e.g., for a single game title or for multiple game titles), can be performed based on user defined event attributes that indicate when game capture is to be performed, and what aspects behaviors/events are to be recorded. In practice, capture/streaming module 120 is configured to record and/or stream those portions of gameplay that have been preselected by user defined event attributes provided to a dashboard provided by management system 112.
In the illustrated example, each of users 206 are subscribed to a different “channel,” for example, that is defined based on different predetermined events, e.g., as defined by respectively provided even attribute information. That is, user 206A is subscribed to Channel 1, which contains gaming feeds based on events (event attributes) A, B, and C; user 206B is subscribed to Channel 2, which contains various gaming feeds based on events A, C, and D; and user 206N is subscribed to Channel N comprised of gaming feeds based on events X, Y, and Z.
As discussed above, the event attributes may define any characteristics relating to the gameplay environment, including but not limited to: player parameters, title parameters, and/or event parameters on which the respective gaming feeds are to be based, etc. For example, Event A may specify the selection of all gaming events played in a first person shooter game, for which each participating opponent has accumulated a point total (or “kill count”) exceeding a predetermined threshold. Event B may specify a racing game title in which competing player lap times are within a 8 seconds of one another; Event C may specify all events associated with 4 specific players in the online gaming environment, and Even E may specify all gaming events associated with soccer related games. As such, player 206A, subscribed to Channel 1, would receive streaming coverage for Events A, B, and C, whereas player 206B would receive streaming coverage of feeds from various game titles/players/environments matching the criteria of Events A, C, and D, etc. It is understood that the scope of the technology is not limited by player/subscriber count, and that each channel may be defined based on virtually any number and any type of user-defined characteristic or statistical attribute. As such, each user/player may optionally create one or more channels that are filtered by highly specific gaming events, and player actions or achievements, etc.
In step 304, gameplay of the first game title is monitored according to the first set of event attributes provided by the first user. Gameplay monitoring can be performed either for the user defining the event attributes (e.g. the first user), or for one or more other users that engage with the event title, e.g. a second user. As such, a first user can “flag” gameplay events for a specific gaming title for which later notifications or video streaming are to be provided.
In step 306, a video stream of the first game title is automatically provided to the first user in response to detected occurrence of the first gameplay event. It is understood that the provided video stream may include clips, highlights, or notifications drawn from one or more game titles that are either played concurrently or asynchronously. That is, aspects of the technology are not limited to the monitoring of a single game environment, or a single game title, etc.
The user device 400 may include various elements as illustrated in
The tracking device 424 may be a camera, which includes eye-tracking capabilities. The camera may be integrated into or attached as a peripheral device to user device 400. In typical eye-tracking devices, infrared non-collimated light is reflected from the eye and sensed by a camera or optical sensor. The information is then analyzed to extract eye rotation from changes in reflections. Camera-based trackers focus on one or both eyes and record their movement as the viewer looks at some type of stimulus. Camera-based eye trackers use the center of the pupil and light to create corneal reflections (CRs). The vector between the pupil center and the CR can be used to compute the point of regard on surface or the gaze direction. A simple calibration procedure of the viewer is usually needed before using the eye tracker.
Alternatively, more sensitive trackers use reflections from the front of the cornea and that back of the lens of the eye as features to track over time. Even more sensitive trackers image features from inside the eye, including retinal blood vessels, and follow these features as the eye rotates.
Most eye tracking devices use a sampling rate of at least 30 Hz, although 50/60 Hz is most common. Some tracking devises run as high as 1250 Hz, which is needed to capture detail of very rapid eye movement.
A range camera may instead be used with the present invention to capture gestures made by the user and is capable of facial recognition. A range camera is typically used to capture and interpret specific gestures, which allows a hands-free control of an entertainment system. This technology may use an infrared projector, a camera, a depth sensor, and a microchip to track the movement of objects and individuals in three dimensions. This user device may also employ a variant of image-based three-dimensional reconstruction.
The tracking device 424 may include a microphone integrated into or attached as a peripheral device to user device 400 that captures voice data. The microphone may conduct acoustic source localization and/or ambient noise suppression.
Alternatively, tracking device 424 may be the controller of the user device 400. The controller may use a combination of built-in accelerometers and infrared detection to sense its position in 3D space when pointed at the LEDs in a sensor nearby, attached to, or integrated into the console of the entertainment system. This design allows users to control functionalities of the user device 400 with physical gestures as well as button-presses. The controller connects to the user device 400 using wireless technology that allows data exchange over short distances (e.g., 30 feet). The controller may additionally include a “rumble” feature (i.e., a shaking of the controller during certain points in the game) and/or an internal speaker.
The controller may additionally or alternatively be designed to capture biometric readings using sensors in the remote to record data including, for example, skin moisture, heart rhythm, and muscle movement.
As noted above, the user device 400 may be an electronic gaming console. Alternatively, the user device 400 may be implemented as a general-purpose computer, a set-top box, or a hand-held gaming device. Further, similar user devices may contain more or less operating components.
CPU 404, vector unit 406, graphics processing unit 408, and I/O processor 410 communicate via system bus 436. Further, the CPU 404 communicates with the main memory 402 via a dedicated bus 438, while the vector unit 406 and the graphics processing unit 408 may communicate through a dedicated bus 440. The CPU 404 executes programs stored in the OS ROM 426 and the main memory 402. The main memory 402 may contain pre-stored programs and programs transferred through the I/O Processor 410 from a CD-ROM, DVD-ROM, or other optical disc (not shown) using the optical disc control unit 432. The I/O processor 410 primarily controls data exchanges between the various devices of the user device 400 including the CPU 404, the vector unit 406, the graphics processing unit 408, and the controller interface 414.
The graphics processing unit 408 executes graphics instructions received from the CPU 404 and the vector unit 406 to produce images for display on a display device (not shown). For example, the vector unit 406 may transform objects from three-dimensional coordinates to two-dimensional coordinates, and send the two-dimensional coordinates to the graphics processing unit 408. Furthermore, the sound processing unit 430 executes instructions to produce sound signals that are outputted to an audio device such as speakers (not shown).
A user of the user device 400 provides instructions via the controller interface 414 to the CPU 404. For example, the user may instruct the CPU 404 to store certain information on the memory card 416 or instruct the user device 400 to perform some specified action.
Other devices may be connected to the user device 400 via the USB interface 418, the IEEE 1394 interface 420, and the AUX interface 422. Specifically, a tracking device 424, including a camera or a sensor may be connected to the user device 400 via the AUX interface 422, while a controller may be connected via the USB interface 418.
It is understood that any specific order or hierarchy of steps in the processes disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged, or that only a portion of the illustrated steps be performed. Some of the steps may be performed simultaneously. For example, in certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.”
A phrase such as an “aspect” does not imply that such aspect is essential to the subject technology or that such aspect applies to all configurations of the subject technology. A disclosure relating to an aspect may apply to all configurations, or one or more configurations. A phrase such as an aspect may refer to one or more aspects and vice versa. A phrase such as a “configuration” does not imply that such configuration is essential to the subject technology or that such configuration applies to all configurations of the subject technology. A disclosure relating to a configuration may apply to all configurations, or one or more configurations. A phrase such as a configuration may refer to one or more configurations and vice versa.
The word “exemplary” is used herein to mean “serving as an example or illustration.” Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs.
