KR102139241B1 - Spectating system and game systems integrated - Google Patents

Abstract

Spectating system that exposes application programming interfaces (APIs) to game systems. The specting system acquires game metadata from game systems for games broadcast by the specting system according to the API, and generates content for broadcasts based at least in part on the game metadata. The broadcast content is provided to specator devices in broadcasts. The specting system receives indications of broadcast content and spectacle' interactions from spectator devices, and provides indications of interactions to game systems according to the API.

Description

Spectating system and game systems integrated

Internet, web-based, including, but not limited to, the availability and capabilities of high-definition video, the increasingly broad availability of broadband connections and consumer computing devices including but not limited to mobile computing devices such as pad/tablet devices and smartphones. The evolution of computing and mobile computing leads to the continued evolution and growth of online gaming. Online games range from relatively simple, two-dimensional (2D) casual games to more complex 2D or three-dimensional (3D) action, sports or strategy games that can include one or more players in a game session. Multiplayer online battle arena (MOBA) games, world-building multiplayer games, complex 3D large scale multiplayer online games (MMOGs) that can support millions or tens of millions of active players in a permanent online “world” ) For example, it can include everything from massive multiplayer online role-playing games (MMORPGs).

The continued evolution and growth of online gaming eventually led to a rise in the popularity of video game spectating, or virtual specting. In virtual spectating, one or more viewers or speculators are not allowed to participate in game play by themselves or one or more other players actively participating in an online game. You can watch gameplay. For example, in a multiplayer online game, spectors can watch one or more players or teams of players participating in the game play or otherwise included in the battle. Broadband Internet, high-resolution video, and video streaming technologies have resulted in the development of live broadcasting technologies that can be leveraged to provide online virtual specification of online games. For example, a game specting system can allow players to broadcast live or recorded streams of their gameplay to dozens, hundreds, or even thousands of spectors, while at the same time speculators can use specific players for viewing. May allow you to select live or recorded broadcasts of the video.

1A is a block diagram illustrating integrated game systems with a game specting system in a game specting environment in accordance with some embodiments.
1B is a block diagram illustrating an example broadcast content service in a game specting environment according to some embodiments.
1C is a block diagram illustrating a source for game metadata in a game specting environment according to some embodiments.
1D is a block diagram illustrating an example game system architecture in accordance with some embodiments.
2A is a flow chart of a method for providing and determining broadcast content in the game specting environment illustrated in FIG. 1A in accordance with some embodiments.
2B is a flow chart of a method for providing and determining broadcast content in the game specting environment illustrated in FIG. 1B in accordance with some embodiments.
3A illustrates event detection and processing in a game specting system according to some embodiments.
3B illustrates game event processing in a game specting system according to some embodiments.
3C illustrates participant event tag processing in a game specting system according to some embodiments.
3D illustrates participant inputs processing for determining events in a game specting system according to some embodiments.
4 illustrates participant inputs processing to determine broadcast-related information in a game spectating system according to some embodiments.
5 is a flow chart of a method for determining events in a game specting environment according to some embodiments.
Figures 6a and 6b provide non-limiting examples of a specting user interface for a game specting system according to some embodiments.
Figures 7a and 7b provide non-limiting examples of a specting user interface for a game specting system according to some embodiments.
8 provides non-limiting examples of a broadcaster user interface for a game specting system in accordance with some embodiments.
9 provides other non-limiting examples of a specting user interface for a game specting system according to some embodiments.
10 illustrates an example virtual storefront module in a game specting system according to some embodiments.
11 is a flow chart of a method for providing a game-related merchandise through a game speculating system according to some embodiments.
12 provides non-limiting examples of a game sales interface for a game specting system according to some embodiments.
Figures 13A-13E illustrate provisioning game client software and game states to a spectator device in a game specting environment according to some embodiments.
14 provides non-limiting examples of a game participation interface for a game specting system according to some embodiments.
15A is a flow chart of a method for enabling game acquisition and participation through a game speculating system according to some embodiments.
15B is a flow chart of a method for step-in into a game through a game specting system according to some embodiments.
15C is a flow chart of a method for provisioning and cloning game characters in accordance with some embodiments.
15D is a flow chart of a method for provisioning game client software to a spectator device in a game specting environment according to some embodiments.
15E is a flow chart of a method for obtaining game data on a spectator device according to some embodiments.
16 illustrates an example participant rewards module in a game specting environment according to some embodiments.
17A is a high level flow chart of a method for recognizing or rewarding participants in a game specting environment according to some embodiments.
17B is a flow chart of a method for rewarding participants for prominent events in games that are broadcast in accordance with some embodiments.
18 provides non-limiting examples of achievement and reward interfaces for a game spectating system in accordance with some embodiments.
19A is a game specting system that provides inputs for a game that is broadcast through a game specting system based on interactions with broadcasts and specator inputs to broadcasts, in accordance with some embodiments. An example game effects module is illustrated.
19B illustrates example game input modules on a game system that processes speculating data received from a specting system to generate inputs for a game broadcast through a game specting system in accordance with some embodiments. For example.
Figures 20A-20D are flow charts of methods for generating inputs to a game system from specator' interactions from a game specating system to broadcasts in accordance with some embodiments.
FIG. 21 provides a non-limiting example of a game specting system interface that allows spectators according to some embodiments to collectively affect a game broadcast through a game specting system.
22 provides a non-limiting example of specters' inputs for broadcasting to a game specting system that collectively affects a game broadcast through a game specting system according to some embodiments.
23 illustrates an example game interaction module in a game specting system that allows a spectator according to some embodiments to provide inputs affecting a game broadcast through the game specting system.
24A is a flow chart of a method that allows spectors according to some embodiments to provide inputs affecting a game broadcast to a game specting system.
24B is a flow chart of a method for analyzing spectacle audio or text inputs affecting a game broadcast to a game spectating system in accordance with some embodiments.
25 is a non-limiting view of a specting user interface for a game specting system that allows spectors according to some embodiments to provide inputs affecting a game broadcast through the game specting system. Provide an example.
26A is a specting user interface for a game specting system that allows spectors and specting group inputs to affect a game broadcast through the game specting system, according to some embodiments. Other non-limiting examples are provided.
26B is a ratio of a broadcast user interface for a game specting system that allows spectors and specting group inputs to affect a game broadcast through the game specting system, according to some embodiments. Provide limited examples.
27 illustrates collecting and storing game data in a game specting system according to some embodiments.
28 illustrates an example game specification module or service that exposes game specification data to consumers in a game specification system according to some embodiments.
29 is a flow chart of a method for collecting game speculating data and exposing data to consumers in a game specting system according to some embodiments.
FIG. 30 is a non-limiting example of a game specting data consumer interface showing a heat map overlaid on a specting interface showing specator interactions with broadcast content in accordance with some embodiments. Here is an example.
31 is a non-limiting example of a game specting data consumer interface showing game specting metrics correlated with broadcast A/V content in accordance with some embodiments.
32 illustrates example network-based game specting environments according to some embodiments.
33 is a block diagram illustrating an example computer system that can be used in some embodiments.
Although the embodiments are described in this application by way of example for several embodiments and exemplary drawings, those skilled in the art will recognize that the embodiments are not limited to the described embodiments or drawings. . The drawings and detailed description thereof are not intended to limit the embodiments to the particular form disclosed, but on the contrary, the intention is that all modifications, equivalents, and equivalents falling within the spirit and scope as defined by the appended claims It should be understood that the alternatives are covered. The headings used in this application are for structural purposes only and are not intended to be used to limit the scope of the description or claims. As used throughout this application, the word “may” is used in an acceptable sense (ie, meaning to have the potential to do), rather than in a compulsory sense (ie, meaning to do). Similarly, the words “include”, “including”, and “includes” mean including, but not limited to.

Introduction

Various embodiments of apparatus and methods for integrating game specting systems and game systems in a game spectating environment are described. In a game specting environment, the game specting system can receive broadcasts of gameplay of players from broadcaster devices for viewing by individual viewers referred to in the present application as specators and specs It is possible to stream broadcasts to data devices. Broadcasts may include videos showing the gameplay of individual broadcasters participating as players in a game running on a game system. Embodiments may include apparatus and methods for game systems for providing game metadata to a game spectating system in addition to broadcast streams. Embodiments may also include apparatus and methods for providing content to speculators through a specting system interface based at least in part on game metadata obtained or obtained from game system(s). Embodiments also include apparatus and methods that enable Spectator participation to affect games broadcast through the Specting system interface.

Game specting systems can allow game players to broadcast live streams of their gameplay to dozens, hundreds, thousands, or more of the speculators, while at the same time speculators broadcast specific players for viewing. (Also referred to as channels) network-based video streaming systems or services that may allow to select. The game specting system can support live streaming of broadcasts simultaneously from tens, hundreds, or thousands of players. The game specting system can record at least some live broadcasts and allow the recorded broadcasts to be played for viewing by the speculators. The game specting system can support live and recorded broadcasts for one, two or more different online games.

Online games are network-based that can allow one, two, or more players, in some cases even thousands of players, to simultaneously participate in the game from consumer devices connected to the network. It's games. Online games that can be implemented in the game specting environment described in this application can vary from tightly scripted games to games that introduce a random variable amount to gameplay. An online game can be, for example, a game in which players try to achieve some goals or overcome some obstacles, and can include multiple levels that players must overcome. An online game can be, for example, a game in which players collaborate to achieve goals or overcome obstacles, or a game in which one or more players compete as one or more other players as a team or as individuals. Alternatively, the online game can be a game in which players can discover and more passively explore in a complex game universe without any specific goals in mind, or players can have their environment in the game universe. It could be a "world-building" online game that can actively change them. Online games are permanent online “worlds” of millions or tens of millions of players, from relatively simple, two-dimensional (2D) casual games to more complex 2D or three-dimensional (3D) action, sports or strategy games. Multiplayer online battle arena (MOBA) games, from complex 3D large multiplayer online games (MMOGs), such as large multiplayer online role-playing games (MMORPGs) Until, it can include everything.

In this specification, the term “player” is generally used to refer to an actual human being actively participating in an online game, and the term “broadcaster” is generally used to play a player's game through a game specification system. The term “viewer” or “spectator” is used to refer to a player who is broadcasting a stream of, and is generally used to refer to live or recorded gameplay online without directly participating in the game as a player. Used to refer to humans, the term “participant” is generally used to refer to players (active participants) and specators (passive participants) collectively, and the term “client” (“client device”). ”, “Game Client”, “Broadcasting Client”, and “Specting Client”) are typically hardware and/or game systems or streaming systems in which participants interact with the gaming system and/or the specting system. Or is used to refer to a software interface, and the term “character” or “game character” generally refers to different game characters, different game entities, and other objects in the game environment during the game session by the player. It is used to refer to an in-game presence or “avatar” of a player that can be controlled through a game client on a client device to interact with.

Embodiments are mainly described in the present application mainly in the context of specting systems that broadcast gameplay in multiplayer online gaming environments where two or more players remotely participate in online game sessions, but embodiments are also single -Applies to player online games, as well as single-player and multiplayer games that are not necessarily online, such as single-player and multiplayer console games that can be played locally/offline. It should be noted that it can. Moreover, the embodiments are mainly described as examples of streaming live or recorded broadcasts of games, such as action, sports, MOBA, and MMOG games, including players having characters or avatars in a streaming game, but the embodiments are single It can be applied to any type of game with any number of players from player games to MMOGs, for example card games or strategy games such as live and recorded streams of chess. In addition, in some embodiments, the spectating system is live sports games that include live streams from sources other than game systems, for example, but not limited to, electronic spectator sports (esports) matches. , Broadcasts or streams of live and/or recorded digital media content from matches, concerts, talk shows, and other events or activities, embodiments may also support these broadcasts Fields or streams. Moreover, the embodiments are mainly described under the context of live streams or video, but the embodiments can also be applied to pre-recorded streams or video.

In some embodiments of the specting system, specators may be divided into two or more groups, tiers, or levels. As a non-limiting example of groupings for specators, specators can be divided into subscribers and non-subscribers, or viewers, followers, and subscribers. A subscriber is a viewer or specter who signs up (and not necessarily, but generally pays for) at least some of the services of a specting system as a service. The viewer or non-subscriber can watch at least some content from the specting system, but does not necessarily need to register for the service to receive additional or full content or services provided to the subscribers, or the service It is someone who does not need to sign up for or need to pay for the service. A follower can participate as a Spectator in broadcasts, registered as a “follower” of the Specting System content (broadcast, broadcaster, channel, game, etc.) registered in the Specting System. , And as a follower, may receive some advantages (eg, announcements via social media channels for events in broadcasts), but not subscribed to the specting system to receive full subscription benefits It can be a person. In addition, a first (eg, “silver”) membership level providing multiple levels or tiers for groups or subscribers, such as some amount of content and services, and an example For example, a second (eg, “gold”) offering more (or all) content and services as a reward for participating in broadcasts or for a higher membership fee. ) There may be membership. Note that specators can be grouped according to any of a variety of different criteria. As non-limiting examples, spectors can be grouped by geographic area, affiliations, age, length of participation into the specting system, or any of various demographic and profile metrics.

In some embodiments, in addition to broadcasters/players and specators, participants in an online gaming environment may include a commentator. The commentator may be a spectator watching live or recorded gameplay without directly participating in the game. However, commentators are generally someone who knows a lot about the game and is someone who provides audio live broadcasts to the games you are watching, such as game analytics, player analytics, and play-by-play commentary. Can be. One or more commentators can provide an audio and/or text live broadcast to a given game that is broadcast to the specting system, and the live broadcast can be added to broadcasts streamed to the speculators.

In at least some embodiments, the game spectating system can obtain game metadata from game systems in which broadcasts are being streamed, and at least partially content for individual broadcasts from game metadata (broadcast content (Referred to as), and can provide broadcast content along with individual broadcasts to the speculators through the specator interfaces on the speculators' devices. The broadcast content can be targeted to specific specators or groups of specators, for example depending on specators' current selections, profiles, or preferences. In some embodiments, the spectating system acquires broadcast content and spectacle interactions to influence game presentation and gameplay on the game system and/or broadcast presentation to the spectating system in various ways. And process it.

In some embodiments, game metadata may be received according to an application programming interface (API) provided to game systems by a specting system, referred to herein as a game system API. The game system API allows game developers to program games to interact with the specting system functionality described in this application. In some embodiments, a software development kit (SDK) may be provided to assist game developers in programming and developing games to support the game system API of the specting system. In some embodiments, game metadata for a given game system includes game state(s), indications and descriptions of in-game events for the game running on the game system, player inputs to the game, And data describing or representing objects, players/characters, locations, levels, and other content or aspects of the game. In some embodiments, at least some game metadata, eg game states, can be provided in response to requests from the specting system. In some embodiments, the specting system may also obtain or receive game metadata from other sources, including but not limited to data repositories and broadcast devices of game-related data.

The game state may be a point-in-time record of game data and game information representing a particular game at a particular point on the game timeline in the game universe. The game state may include game data that can be used and represented by a game client running on the device to reconstruct the game at a particular point on the in-game game timeline. In at least some embodiments, game states may be received according to a game system API provided to game systems by a speculating system. In some embodiments, one or more game states can be used to regenerate a game session universe to start or restart game play at an individual point in the game session timeline. Note that the format and content of the game state may be different for versions or different types of games, titles.

In at least some embodiments, indications of game events may be received from game systems according to a game system API provided to game systems by a specting system. Game events can include events that are common across two or more games. However, at least some game events may be game-specific events defined by individual game systems. Examples of game events may include, but are not limited to: specific achievements by specific players or teams of players; Level starts and completions; Beginnings, endings, or other important moments of battles, bouts, challenges, or other in-game events; In-game character entries, exits, deaths, etc.; Acquisition or loss of items, objects, powers, etc. by in-game characters or players; Or any event or moment that may have an interest in the game that runs on the game system in general.

In at least some embodiments, indications of player inputs to the game for at least some players in the game may be received from game systems according to the game system API provided to the game systems by the speculating system. The player input may be a single command or action input to the game from an individual player's game client or game controller. The player input or a combination of player inputs can trigger a game event, can be included in a game event, or can be associated with a game event. In some embodiments, player inputs to the game are, for example, but not limited to forming a record of a particular game session (referred to as a game record) that can be bent to clients that include specators. It can be stored as part of a game record along with one or more game states and other game information. The game record containing player inputs can be replayed, and in some embodiments, the viewer of the replay can “step into” the replay as described later in this specification.

In addition to receiving and processing game metadata from the game system(s) to generate broadcast content, in some embodiments, the specating system is running on game systems and/or other for games. Various inputs from participants (players, broadcasters, and/or spectors) can be obtained and analyzed in a game specting environment to determine information or detect events there. Events and other information determined from participant input analysis may be collectively referred to as broadcast metadata. The speculating system can generate broadcast content for individual broadcasts, at least in part, from broadcast metadata, and is not limited through interfaces on individual devices, but individual broadcasts to participants that include specators. You can provide broadcast content with them. Various participant inputs may include, but are not limited to, one or more of the following: audio or voice inputs such as in-game vocal communication or broadcast vocal channels; Video or image inputs (eg, images or video of participants' facial expressions or eyes); Text input, such as in-game or broadcast text chat; Biometric inputs from players; And participant inputs to a broadcast via speculating user interfaces (UI), such as voting or indicating an in-game or broadcast event as highlights for broadcasts and/or games. field.

The generated broadcast content, which can be provided along with individual broadcasts to the speculators via the Spectator Interfaces on Spectators' devices, can be provided on the UI with broadcast video, various user interfaces (UI ) Elements (e.g., buttons, dialogs, lists, tabs, menus, images, video clips, links, including one or more other UI elements, etc., Text, panes) and/or one or more overlays (eg, overlay video, text, etc.) that may be added to the broadcast video. At least some of the UI elements can be or include active UI elements that initiate or perform some action when selected.

In some embodiments, broadcast content and specator interactions can be tracked, processed, and recorded as additional broadcast metadata or as speculating data. Spectator interactions are UI element selection, UI element manipulation (e.g., by scrolling, clicking, sliding, turning, etc.), on or near the UI element. Hovering (e.g., with a cursor), typing into a UI element (e.g., entering text into a text box), and focusing on one or more UI elements (e.g., eye tracking) (Detected through technology).

In some embodiments, broadcast content may be provided to speculators through speculating system client instances on speculators' devices provided by the speculating system. In some embodiments, broadcast content may replace various applications running on Spectators' devices or applications may also be provided, depending on the application programming interface (API) provided to applications by the Spectating system. have.

In some embodiments, a system, module, or service (referred to herein as a broadcast content service) is logically speculating instead of or in addition to a specting system that adds broadcast content to the broadcast. It can be between the system and the spectator devices. The broadcast content service can receive broadcast streams, broadcast metadata, and game metadata from a specting system, and broadcast streams based at least in part on game metadata and/or broadcast metadata. Broadcast content can be added or modified.

In some embodiments, the specting system provides a virtual storefront for game-related content that speculators can view, select, and order, purchase, or otherwise obtain, game-related content. To do this, we can leverage game metadata. Game-related content is virtual game items or objects that can be obtained for use in games (eg, digital representations of physical objects) such as in-game gear, clothing, weapons, characters, avatars Physical items (e.g., physical swords, action figures, toys, etc.), such as physical representations of virtual objects from within games, powers, etc., and/or Or game-related physical products such as t-shirts, posters, videos, or hats. In some embodiments, the specting system can provide or provide access to a “print on demand” service, so that 3D printing technology is game-related objects or items (eg For example, it can be used to print physical objects based on inputs or specifications of in-game characters, weapons, vehicles, monsters, etc.). Designs or instructions for the objects can be obtained from game systems in game metadata, or otherwise, can be obtained. The virtual storefront can provide a user interface (UI) so that spectors can get information about in-game content, for example which characters/players use the item and how they use it , You can watch statistics about item history or success, etc. The specting system can provide text and/or voice chat channels through which speculators and broadcasters can discuss game-related items available through a virtual storefront. In some embodiments, the broadcaster may specify or select specific items or objects advertised or sold through the virtual storefront UI on the broadcaster's channel.

In some embodiments, the specting system may leverage game metadata to allow speculators to join or “step into” games broadcasted through the specting system. In some embodiments, broadcast content provided to speculators on the speculating UI can be obtained by speculators who can order, purchase, or otherwise obtain, demo or full versions of games. User interface elements In some embodiments, the game client software and game data to participate in a demo or full versions of online games is a spectacle device through spectacle system interfaces and broadcast streams. In some embodiments, the broadcast content provided to speculators on the specting UI includes characters, avatars, gears, and speculators specifically for participating in games. Other items can be ordered, purchased, or otherwise, can include user interface elements that can be obtained Characters and game items obtained are through the specting system interfaces and broadcast streams. 'In some embodiments, using the Specting UI to obtain game client software, game data, characters, and gears via broadcast streams, Spectators can play online games. You can join live game sessions, start new game sessions, and/or replay pre-recorded game sessions or portions of game sessions.

In some embodiments, spectors can use the specting UI to obtain game client software, game data, characters, and gears via broadcast streams, and can also use previous game sessions or portions of game sessions. Can be acquired, “Step Into”, and replayed. In some embodiments, game states may be purchased or otherwise obtained through specting system interfaces and broadcast streams. In some embodiments, broadcast content provided to speculators on the specting UI may include user interface elements through which one or more game states, such as game states provided with game metadata , Can be advertised and obtained by Spectators, can be used to regenerate game session universes, start or restart gameplay at individual points in the game session timeline, Spectators become players and have their own in-game Step into a game session universe and timeline by using a character or avatar or taking control of a character that is already in the game session and stepping in. In some embodiments, the broadcast content provided to speculators on the specting UI can be viewed, ordered, purchased, or the characters, avatars, gears of players that speculators specifically participate in games, or Alternatively, it may include user interface elements that can be obtained. Thus, in some embodiments, the spectator can acquire the in-game character and “load out” or equip the character through all spectating system interfaces and streams, and the game is executable. It can acquire a version, acquire and "step in" game states, and can be clones or characters of characters in a step in or game session.

In some embodiments, the “ghosting” mode may be supported when replaying game sessions from acquired game states or game records. In ghosting mode, the player can replay a broadcaster/player's pre-recorded game session or jump into a broadcasted game through the specting system interface. The original player's character/gear (eg, racecar) may still be visible as a “ghost” to the new player. Thus, new players can compare their performance to that of the original player by watching the “ghost” of the original player during replay. In addition, the original player's broadcast live broadcast (video, audio, and/or text) can be played or displayed to the new player. As an example, a new player can use the ghosting mode as a training tool to learn how a skilled or proficient broadcaster/player has played a difficult level or challenge in the game.

In some embodiments, the specting system is intended to reward or otherwise acknowledge the specting system participants (broadcasters/players, specators, and/or commentators). You can leverage game metadata and/or broadcast metadata. In some embodiments, specators may be rewarded for participating in broadcasts or events in games that are specifically broadcast. In some embodiments, the specting system can analyze game metadata and/or broadcast metadata to detect big or important events or highlights in broadcast streams, watch big events, or " You can compensate at least some specators for "being there". In some embodiments, specators may be rewarded for interacting with broadcasters, for example actively participating in broadcast audio or text chat channels. Examples of Spectator Rewards include acknowledgments or "badging" on a game specting system interface, virtual or digital items such as virtual gears in a game, specting system or game content. May include, but is not limited to, discounts or free access, physical items such as t-shirts or hats, and points that can be used and collected to win or purchase items. Does not work. In some embodiments, the specting system allows broadcasters to reward or promote specific speculators, for example, by selecting a spector that shows good knowledge of the game in order to become a narrator for the game. Can be. In some embodiments, broadcasters/players perform certain feats (achievements), such as in-game skills such as performing some feet in front of people of any size, or audience participation or support at any level. (Audience size, enthusiasm, voting, etc.) can be rewarded for achieving. As non-limiting examples, broadcasters/players may obtain in-game health or strength boost or audience size or audience enthusiasm expressed through audio and/or text specator chat input Based on growth, you can be rewarded with in-game powers, gears, weapons, or information. As another example, broadcasters can obtain special broadcast content added to their broadcast channel display based on their achievements. As another example, broadcasters can receive a monetary reward for bringing new followers or subscribers to the specting system through their broadcast channel.

In some embodiments, the specting system may enable participation of the specter in the broadcast to affect games broadcast through the specting system interface in various ways. In some embodiments, the specting system can determine information based on participation in the spectator in broadcasts and information as feedback to the game systems according to the game system API provided to the game systems by the specting system. Can provide. Spectator participation metrics that can be used include broadcasts or games to broadcast “chat”, “crowd noise”, or other audio and text channels, and Spectator audio and And/or including, but not limited to, people or audience size for text entry. In some embodiments, participation of the spectator in broadcasts can be used as a randomizing factor in games. For example, one or more aspects or metrics of a spectator participation in a broadcast or broadcasts (people or audience size, people noise, chat level or volume, etc.) are fed back to the game system for use as a game rendering factor. It can be measured or tracked and provided as. In some embodiments, spectater participation in broadcasts can be used to non-randomly affect games and/or game players broadcast in various ways. As a non-limiting example, the size of a person or audience watching a broadcast or broadcasts of an in-game event can be fed back to the game and served as an audio output along with the broadcast to view the volume and/or event of noise. It may affect the size of the spectacle's imaginary people, the size or appearance of a stadium, arena or other event venue. As another example, the volume, amount, or level of people enthusiasm or support measured from content, for example audio and/or text chat channel inputs to a broadcast, can be fed back to the game and have a broadcaster/player. Can affect the number of “bad guys” or monsters appearing in the current level, or can be used to reward broadcasters at the level by having player access to certain weapons, or various You can have other in-game effects. As another example, Spectators' audio and/or text inputs can be analyzed to detect content or emotion (keywords, cheers, boos, happiness, etc.); Analysis can be fed back to the game and used to affect the player's in-game state, health, power, weapons, etc.

In some embodiments, the specting system may enable speculators to interact and influence players in games in various ways or games broadcast through the specting system interface. In some embodiments, individual spectors can interact with games through a game specting interface to produce in-game effects. In some embodiments, groups of spectors can cause in-game effects through the game specting interface, for example based on voting, or otherwise, affect the game. In some embodiments, the specting system can leverage game metadata to provide specting UI elements that speculators can interact to provide input to individual games. In some embodiments, the specting system may provide specter interactions as feedback to game systems according to the game system API provided to game systems by the specting system. In some embodiments, specators may or may affect in-game players or in-game events, objects in a game universe, games through UI elements on the game specting interface. As non-limiting examples, specators build buildings, hide weapons, set difficult levels, select weather or other environmental factors, or otherwise, through UI elements provided on the game specting interface, or otherwise It can affect game content and events. In some embodiments, the speculators have, for example, objects, boosts, weapons, medicine, health points, intensity levels, etc., through the specting interface. The game content may be provided to certain players or teams of players in the game or may be "gifted" to them. In some embodiments, specators may provide information, such as maps, warnings, or advice, to in-game players or teams of players through a game specting interface. In some embodiments, specators are game specta, for example by causing a storm or other catastrophe, increasing difficulty of game levels or tasks, taking objects from players, reducing player strength, and the like. Challenges and difficulties for players or games in games can be introduced through the chat interface.

In some embodiments, the specting system is not limited, but may store at least a portion of the game metadata and broadcast metadata including spectacle interactions with individual broadcast content as game specting data. The game specting system can provide one or more user interfaces (UIs), query interfaces, and/or application programming interfaces (APIs) through which consumers (eg, game developers, online) Merchants, broadcasters, etc.) may obtain or view game speculating data for use in analyzing performance and online game usage for applications, for example in game development, advertising, and/or marketing. have.

The terms “get”, “provide”, “download”, “stream”, “provision”, and the like (games, game streams, game states, game records or recordings, but not limited to, Purchases for individual items (as used herein in connection with various game-related virtual or physical items, including game content, game characters or gears, game-related products, etc.) are not necessarily Note that it may include purchasing, leasing, subscribing, or otherwise pay for.

Example game Specting Example game spectating environments

1A is a block diagram illustrating integrated game systems with a game specting system in a game specting environment in accordance with some embodiments. The game specting environment may include a specting system 100, one or more game systems 120, and multiple client devices; Client devices may include broadcaster devices 140 and spectacle devices 160.

Client devices (eg, broadcaster devices 140 and specator devices 160) are not limited to desktop computer systems, laptop/laptop computer systems, pad/tablet devices, smartphone devices , Game consoles, handheld game devices, and wearable devices. Thus, client devices can range from powerful desktop computers configured as gaming systems down to “thin” mobile devices such as smartphones, pad/tablet devices, and wearable devices. have. The client device can implement an operating system (OS) platform compatible with the device. The client device can include, but is not limited to, input and output components and client software. The client software on a particular client device can be tailored to support the configuration and capabilities of a particular device type and the OS platform of the device. An example computing device that can be used as a client device is illustrated in FIG. 33.

The broadcaster device 140 may include input and output components (limitedly) for at least one game system 120 where individual players may participate in game sessions currently being executed by the game system(s) 120. But may include, but is not limited to, input devices and technologies such as controllers or joysticks, motion tracking systems, gesture-based input systems, and the like) and game client software and/or hardware. . The broadcaster device 140 includes input and output components (eg, video cameras and microphones) and live A/V streams (broadcasts 142) and individual players of their online game play and Broadcast for Specting System 100 that can generate other broadcaster inputs 144, including but not limited to audio and text live broadcasts for broadcast to Spectators through game Specting System 100. Casting client software and/or hardware may also be included. Spectator device 160 includes input and output components (including but not limited to input devices and technologies such as controllers or joysticks, motion tracking systems, gesture-based input systems, etc.) and individual spectors They can interact with the specting system 100 to select, receive and watch broadcasts 142 from broadcasters or playbacks of pre-recorded broadcasts, and specators limited Spectator interaction with broadcast content 126 that includes, but is not limited to, content generated from game metadata 124 received from game system(s) 120 at least in part by specting system 100 Specting client software and/or capable of providing acts 164 and, but not limited to, audio or text chat or specter inputs 165 including “people noise” for broadcasts 142 It can include hardware, but is not limited to it. In some embodiments, specator inputs 165 may also include inputs from input devices and techniques such as controllers or joysticks, motion tracking systems, gesture-based input systems, etc.

In some embodiments, the specting system 100 may include one or more computing devices that implement game specting functionality, such as one or more server devices. In some embodiments, speculating systems 100 may allow players to broadcast live streams 142 of their online game play to dozens, hundreds, thousands, or more of specators, at the same time It may include network-based video streaming systems or services that may allow spectors to select broadcasts 142 (also referred to as channels) of specific players for viewing. Specting system 100 can support live broadcasts 142 for one, two, or more different gaming systems 120, and can be from tens, hundreds, or thousands of broadcaster devices 140. Spectator devices 160 may support live streaming of broadcasts 142. In some embodiments, the spectating system 100 can record at least some broadcasts 142 and the recorded broadcasts 142 can be viewed by the spectators devices 160 for viewing. ). The game specting system 100 can support live and recorded broadcasts 142 for one, two or more different online games 120.

In some embodiments, the specting system 100 is not limited to, but not limited to, recordings of game specting data and broadcasts 142 including game metadata 124 and participants ( Other devices, services, or systems, including storage devices, systems, or services for storing profiles, preferences, and other information for players, broadcasters, and/or specators) Can also include or access. In some embodiments, the specting system 100 can store recordings of at least some broadcasts 142 in a data store, and speculators can use the speculating client software on the specator devices 160. This allows the recording to be selected and played back.

In some embodiments, the specting system 100 may implement one or more UIs and/or one or more APIs in the game specting system 100 function. For example, the specting system 100 allows broadcasters devices 140 to broadcast 142 their live game play and other inputs 144 such as video inputs and audio or text live broadcasts or chats. ) To implement a broadcasting UI/API 112 that can be accessed. As another example, the spectating system 100 may be used to select, receive and watch live broadcasts 142 from broadcasters or broadcasters of pre-recorded broadcasts 142. Can be accessed through devices 150, and the speculators can provide the specator input 165 (eg, an audio or text live broadcast or chat) to the broadcasts 142, It is possible to implement a specting UI/API 116 that can interact 164 with the broadcast content 126 provided by the specting system 100. As another example, specting system 100 may allow game system(s) 120 to pass game metadata 124 to specting system 100, where specting system 100 may be configured to Game system API 114 that can provide feedback to (s) 120 may be implemented. In some embodiments, at least some game metadata 124, such as game states, may be provided in response to requests 105 from specting system 100.

In some embodiments, the specting system 100 can support broadcasts of live and/or recorded digital media content from broadcast sources via broadcast devices 120 other than game systems 120. . For example, in some embodiments, the specting system 100 is not limited to sports games, matches, concerts, and live streams from electronic Spectator Sports (esports) matches, and It can support live or recorded broadcasts of streams from other events. Esports (also referred to as competitive gaming) generally wears out organized multiplayer video game competitions. For example, video cameras and audio equipment can be installed at an event, such as an arena or other venue where a sports game or esports competition is being held. One or more broadcaster devices 120 capable of compositing and streaming audio/video (A/V) inputs to the specting system 100 from video and/or audio feeds from the device. It may be an input to. For esports events, game A/V 121 can be added to the stream along with feeds from cameras and audio equipment. Commentators and/or broadcasters may also input their audio, text, and/or video content into the stream. The live stream can be broadcast to the spectator devices 160 by the specting system 100, and/or can be recorded for rebroadcast. Spectators can watch broadcasts on spectator devices 160 and can also input A/V and/or text input through specting system clients on their devices 160.

1A shows the gaming systems 120 separated from the specting system 100 and the broadcaster device(s) 140, but in some embodiments, at least one gaming system 120 is a spectacle It can be a component of the tinting system 100 or can be implemented at least partially by a specting system. In some embodiments, the at least one game system 120 can be a component of the broadcaster device 140 or can be implemented at least partially by the broadcaster device. In some embodiments, one or more broadcaster devices 140 may be implemented in the specting system 100. In addition, in some embodiments, specting system 100 may be a component of game system 120 or may be implemented at least partially by a game system.

The following is a broad description of an example method for broadcast streaming in a game spectating system, and is not intended to be limiting. Typically, game system 120 renders a 2D or 3D representation of the game universe based on the current state of the universe, generates video and sound, and is not limited to display, but is not limited to broadcast device(s). ) May include a game engine that sends or streams video and sound (A/V) output 121 to client devices including 140. On the broadcaster device 140, the player/broadcaster can interact with the game system 120 and run on the game system 120 via the player input 122 using game client software on the device 140. You can participate in the game and use the broadcasting UI/API 112 provided by the specting system 100 to construct a live stream of broadcaster's gameplay for broadcast (broadcast 142). Can be. The live stream may include the game A/V 121 received from the game system 120, and the A/V components of the device 140 embedded in the game A/V 121 stream or as a separate stream. It may also include video and audio inputs of players captured by (eg, video cameras and microphones). In some embodiments, the player/broadcaster may also use the broadcasting UI/API 112 to provide a text input to the broadcast 142, for example, a text input to the broadcast chat window. 8 provides non-limiting examples of a broadcaster user interface for a game specting system according to some embodiments.

In some embodiments, live streams of broadcasts 142 are sent from broadcaster device(s) 140 to speculating system 100 according to the broadcasting UI/API 112. The video input can be received by the specting system 100 in any of several video formats. The audio input can be received by the specting system 100, for example, as audio tracks in a video input, as a Voice of IP (VoIP), or according to other network formats or protocols supporting digital audio transmission. have. On the spectating system 100, live streams of broadcasts 142 are processed for rebroadcast to spectator devices 160. In some embodiments, at least some of the broadcasts 142 may be recorded and stored for playback.

On the Spectator device 160, the Spectator is viewed through the Spectating UI provided on the Spectator device 160 according to the Specting UI/API 116 provided by the Spectating system 100. For specific broadcast 142 or channel can be selected. Specting system 100 may then stream the selected broadcast 142 to specter device 140 via specting UI/API 116 for display. In some embodiments, the spectator is an audio input (eg, voice live broadcast, cheers, people noise, etc.) to the current broadcast 142 viewed as input 164 via the specting UI/API 116. Or A/V components of the device 160 (eg, a microphone) to provide a voice chat. The spectator may also provide text input, for example text input to a broadcast chat window provided by the specting UI/API 116. Figures 6a, 6b, 7a, 7b, and 9 provide a non-limiting example of specting user interfaces that can be used to watch broadcasts in a gaming specting environment according to some embodiments.

In at least some embodiments, specting system 100 can obtain game metadata 124 from game system(s) 120 where broadcasts are being streamed, and at least partially game metadata 124 ) Can generate broadcast content 126 for individual broadcast 142 streams received from broadcast device(s) 140, and speculating on specators' devices 160 Through the client interfaces, broadcast content 126 may be provided to the speculators along with individual broadcasts 142. In at least some embodiments, game metadata 124 may be received according to game system API 114 provided to game system(s) 140 by specting system 100. In some embodiments, game metadata 124 for a given game system 120 includes game state(s), indications and descriptions of in-game events and objects, objects for the game running on the game system, player Field/characters, locations, data describing or indicating levels, and one or more of other content or aspects of the game. In some embodiments, at least some game metadata 124, such as game states, may be provided in response to requests 105 from specting system 100.

In some embodiments, in addition to obtaining and processing game metadata 124 from game system(s) to generate broadcast content, spectating system 100 runs on game system(s) 120 From the participants (players, broadcasters, and/or specators) to the game specting environment to determine broadcasts 142 and/or other information about the games or to detect events there. The various inputs 144 and 164 of can be acquired and analyzed. Events and other information determined from participant input analysis may be collectively referred to as broadcast metadata. In some embodiments, the specting system 100 can generate broadcast content 126 for individual broadcasts 142 from at least partially broadcast metadata, and on individual devices 160. Although not limited through interfaces, broadcast content 126 may be provided along with individual broadcasts 142 to participants, including specators. Various participant inputs 144 and 164 may include, but are not limited to, one or more of the following: audio or voice inputs such as in-game vocal communication or broadcast vocal channels; Video or image inputs (eg, images or video of participants' facial expressions or eyes); Text input, such as in-game or broadcast text chat; Biometric inputs from participants; And in-game events or broadcast events as highlights for participant inputs, eg broadcasts and/or games, to broadcasts and/or broadcasts via specting user interfaces (UIs). Voting or inputs that indicate it.

In some embodiments, the generated broadcast content 126, which may be provided with individual broadcasts 142 to speculators via specting UIs on the speculators' devices, is broadcast 142 ) With video, one or more various UI elements that can be provided on the specting UI, and/or one or more overlays that can be added to the broadcast 142 video. At least some of the UI elements can be or include active UI elements that initiate or perform some action when selected.

In some embodiments, broadcast content 126 may be targeted to particular specators or groups of specators, for example depending on specators' current selections, profiles, or preferences.

In some embodiments, the specting system 100 can acquire and process broadcast content 126 and specator interactions 164 so that the specting system ( 100) My game specting, broadcast 142 processing, and broadcast content 126 may be affected. In some embodiments, speculating system 100 may provide game feedback 101 to game system(s) 120. Game feedback 101 may be generated, at least in part, from specator interactions 164 with broadcast content 126. In some embodiments, game feedback 101 may be provided in accordance with game system API 114 provided to game system(s) 140 by spectate system 100. The game system(s) 120 may apply game feedback 101 to affect game execution and game play on the game system 120 in various ways. In some embodiments, speculating system 100 broadcasts feedback 103 to broadcast device(s) 140 based at least in part on specator interactions 164 with broadcast content 126. ) Can also be provided. In some embodiments, broadcast feedback 103 is broadcast UI/API 112 provided to broadcast devices 140 by specting system 100, for example, as illustrated in FIG. 9. It can be provided to broadcasters through.

In some embodiments, the specting system 100 is not limited to other input 167 sources, including but not limited to inputs from social media channels such as “tweets” or instant messaging (IM) or It may include one or more interfaces that can acquire, process, display, and analyze inputs from channels. In some embodiments, inputs from other sources 167, such as text inputs to a social media chat channel, can be acquired, processed, and analyzed to broadcast content 126 in various ways described herein. ), game feedback 101, and/or broadcast feedback 103.

1B is a block diagram illustrating a broadcast content service in a game specting environment according to some embodiments. In some embodiments, by adding broadcast content 126 to broadcasts 142 received from broadcast device(s) 120 instead of or in addition to specting system 100, a module, A system or service (referred to as broadcast content service 113 in this application) may be logically between the specting system 100 and the spectator device(s) 160. Note that the broadcast content service 113 can be implemented as a module or service of the specting system 100, or as a separate service. In some embodiments, broadcast content service 113 can receive broadcasts 142, game metadata 124, and broadcast metadata 117 from specting system 100, Broadcast content 126 may be generated and added based at least in part on game metadata 124 and/or broadcast metadata 117. In some embodiments, at least some game metadata 124, such as game states, may be provided in response to requests 105 from specting system 100.

In some embodiments, the broadcast content service 113 is capable of acquiring and processing broadcast content 126 and specator interactions 164 so that the game specting environment in various ways described herein. In broadcasts 142 and broadcast content 126 may affect presentation and processing. In some embodiments, the broadcast content service 113 provides feedback 119 to the specting system 100 that the specting system 100 can apply to affect the gaming specting environment. Can be created. In some embodiments, specting system 100 can provide game feedback 101 to game system(s) 120 based on feedback 119; Game system(s) 120 may apply game feedback 101 to affect game execution and game play on game system 120. In some embodiments, speculating system 100 broadcasts feedback 103 to broadcast device(s) 140 based at least in part on feedback 119 received from broadcast content service 113. Can also provide In some embodiments, broadcast feedback 103 is broadcast UI/API 112 provided to broadcast devices 140 by specting system 100, for example, as illustrated in FIG. 9. It can be provided to broadcasters through.

In some embodiments, at least some components of the game specting environment illustrated in FIGS. 1A or 1B are services that provide virtualized resources on a provider network to clients of a service provider, for example as illustrated in FIG. 32. It can be implemented in the context of a provider. For example, the specting system 100 may be implemented as a specting service on a provider network, as illustrated in FIG. 32. As another example, broadcast content service 113 may be implemented as a service on a provider network, as illustrated in FIG. 32. In some embodiments, one or more game systems 120 may be implemented by game providers on a provider network.

FIG. 1B logically illustrates the broadcast content service 113 between the specting system 100 and the specator device(s) 160, but in some embodiments, the broadcast content service 113 Instead, it may logically be between the broadcast device 140 and the specting system 100. The broadcast content service 113 may be implemented as a module or service of the specting system 100, or may be implemented as a separate service. In some embodiments, the broadcast content service 113 can receive broadcasts 142, broadcaster input 144, and game metadata 125, and generate content in the broadcast 142 And can be added. Additional content may be based at least in part on game metadata 124. Additional content may include, but is not limited to, overlays on the game video.

As illustrated in Figures 1A or 1B, in some embodiments, game metadata 124 is a game system(s) according to game system API 114 in a separate channel from the game A/V 121 stream. It can be received by speculating system 100 from 120. However, in some embodiments, at least a portion of the game metadata 124 as metadata in the game A/V 121 content sent by the game system(s) 120 to broadcast devices 120. It may be included, and may be included as metadata in broadcast 142 streams sent from broadcaster devices 140 to specting system 100.

As illustrated in Figures 1A or 1B, in some embodiments, game metadata 124 is generated by specting system 100 from game system(s) 120 according to game system API 114. Can be received. However, in some embodiments, the specting system 100 is not limited and may acquire or receive game metadata 124 from other sources including broadcast device(s) 140. . In addition, in some embodiments, specator device 160 is not limited to game metadata from one or more sources including game system(s) 120 and broadcast device(s) 140 ( 124).

1C is a block diagram illustrating a source for game metadata in a game specting environment according to some embodiments. Specting system 100 may stream broadcast(s) 142 from broadcaster device(s) 140 to one or more specter devices 160. Specting system 100 may receive game metadata 124A from game system 120 as illustrated in Figures 1A and 1B. In addition, the specting system 100 can receive game metadata 124B from the broadcaster device 140. Game metadata 124B may include specific data, such as identity information, for a broadcaster/player and/or game client associated with broadcaster device 140. In addition, the specting system 100 can request and receive game metadata 124C from one or more other game metadata sources 190. Other game metadata sources 190 are not limited to game developer systems that include historical, statistical, and/or descriptive information and data for games, game content, players, and/or broadcasters. Or third-party systems, such as, but not limited to, online merchants, game information sites, and data repositories or databases of game information. For example, the specting system 100 may request information about the player and/or broadcaster (game metadata 124C) based on the game metadata 124B received from the broadcaster device 140. have. Specting system 100 may generate broadcast content 126 for broadcast 142 based at least in part on game metadata 124A, 124B, and/or 124C. The spectator can interact with the broadcast content 126 on the spectator device 126. In response to the interaction, the specting system 100 may obtain additional game metadata 124 from one or more of its sources, and the additional or modified broadcast content 126 may be acquired by the spector device. (160). However, in some cases, the broadcast content 126 and spectacle interaction may create a request to one or more other game metadata sources 190, for example additional broadcast content. It can be responded by providing game metadata 124D to the spectator device 160 to be displayed as. For example, the spectator device 160 may source information about the player or game content (game metadata 124D) based on the descriptive or identity information provided to the broadcast content 126 as the source 190 Can be requested at Although not shown in FIG. 1C, in some embodiments, the spectator device 160 may communicate with or on behalf of the game system 140 to obtain game metadata 124.

1D is a block diagram illustrating an example game system architecture in accordance with some embodiments. In some embodiments of the game specting environment illustrated in FIGS. 1A and 1B, the specting system 100 may communicate with the game engine of the game system 120 through the game system API 114. However, in some embodiments, the specting system 100 is not limited to a game system (for exchanging various game system I/Os 123 described herein, including game metadata 124). 120) may communicate with one or more game servers 125 instead. Game server(s) 125 may include game engine I/O 127 to one, two, or more instances of game engine 129 shown by game engines 129A, 129B, ..., 129n in FIG. 1D. Can be delivered one after the other. Game engine 129 instances may be instantiated on one or more servers of game system 120, or alternatively at least some game engine 129 instances may be as illustrated in figures 1a and 1b. Likewise, it can be operated on broadcaster devices 140. In some embodiments, game system I/O 123 received from specting system 100 may include at least some data specific to particular game engines 129 and server(s) ( 125) can handle the distribution of data to target engines 129. In at least some embodiments, the specting system 100 can instantiate one or more processes on one or more server devices for data handling from specific game engines 129 and processing data for them. .

2A is a flow chart of a method for providing and determining broadcast content in a game specting environment according to some embodiments. The method of FIG. 2A can be implemented, for example, by the spectating system 100 illustrated in FIG. 1A or 1B.

As indicated at 200 in FIG. 2A, the game spectating system can receive broadcasts from one or more broadcaster devices. With reference to Figures 1A and 1B, the specting system can receive broadcasts of players' game play from broadcaster devices for viewing by individual spectator viewers and streaming broadcasts to the specator devices can do. Broadcasts may include videos showing the gameplay of individual broadcasters participating as players in a game running on the game system.

As indicated at 202 in FIG. 2A, the game spectating system may receive game metadata from one or more game systems. In at least some embodiments, the game specting system can obtain game metadata from game systems in which broadcasts are being streamed. In at least some embodiments, game metadata may be received according to an application programming interface (API) provided to game systems by a specting system, referred to herein as a game system API. In some embodiments, game metadata for a given game system includes game state(s), indications and descriptions of in-game events for the game running on the game system, and objects, players/ Characters, locations, data describing or indicating levels, and one or more of other content or aspects of the game. Game states, events, objects, and the like that can be described in game metadata may be collectively referred to as game-related content.

As indicated at 204 in FIG. 2A, the game spectating system may determine or generate broadcast content for individual broadcasts, at least in part, from game metadata. Specting systems use information in game metadata to generate broadcast content that corresponds to game-related content represented in game metadata and graphically and/or textually or describes the game-related content. Can. As indicated at 206 in FIG. 2A, the game spectating system can stream broadcasts and related broadcast content to spectacle user interfaces on spectacle devices for presentation to spectacle. Spectators' broadcast content, which can be generated and provided along with individual broadcasts to speculators via specter interfaces on devices, can be provided on the UI along with broadcast video, various user interfaces (UI ) One of the elements (e.g., buttons, dialogs, lists, tabs, menus, images, video clips, links, text, panes, including one or more other UI elements, etc.) And/or one or more overlays (eg, overlay video, text, etc.) that can be added to the broadcast video. The broadcast content is UI elements and/or overlays that correspond to or represent game-related content, such as virtual game items or objects (eg, digital representations of physical objects) such as in-game gear, clothing Physical items (eg, physical swords, action figures, toys, etc.), games, physical representations of virtual objects from within games, weapons, characters, avatars, powers, etc. -UI elements and/or overlays, which may include related physical goods such as t-shirts, posters, videos, or hats and represent or describe game events and/or game states indicated in the game metadata It may also include.

In some embodiments, in addition to receiving and processing game metadata from game system(s) to generate broadcast content, the specting system can be used for broadcasts and/or games running on game systems. Various inputs from participants (players, broadcasters, and/or specators) in a game specting environment to determine other information or detect events therein (eg, audio, video, and And/or text inputs). Events and other information determined from participant input analysis may be collectively referred to as broadcast metadata. The speculating system can generate broadcast content for individual broadcasts, at least in part, from broadcast metadata, and is not limited through interfaces on individual devices, but individual broadcasts to participants that include specators. You can provide broadcast content with them.

As indicated at 208 in FIG. 2A, the game spectating system can receive and process spectacle interactions with broadcast content from spectacle user interfaces. Broadcast content and Spectator interactions include UI element selection, UI element manipulation (e.g., by scrolling, clicking, sliding, turning, etc.), hovering on or near the UI element (e.g., with a cursor), Input to a UI element (e.g., text input into a text box), and focusing on one or more UI elements (e.g., detected via eye tracking technology), but may be limited to It does not work. In some embodiments, the specting system can process broadcast content and specator interactions to influence gameplay on the game system and/or broadcast presentation to the specting system in various ways. . In some embodiments, the specating system can provide feedback to the game system(s) based at least in part on specter interactions with broadcast content. In some embodiments, game feedback may be provided to games according to the game system API of the specting system. The game system(s) can apply game feedback to affect game execution and game play on the game system in various ways. In some embodiments, the specating system may also provide feedback to the broadcast device(s) based at least in part on specator interactions with broadcast content.

As indicated by the arrow returning from element 208 to element 200, in at least some embodiments, the method of FIG. 2A is obtained and used for game metadata for broadcasts to generate and provide broadcast content. , It may be an iterative process in which interactions with broadcast content are received and processed, for example, affecting game play and game play.

2B is a high-level flow chart of a method for providing and determining broadcast content in a game specting environment according to some embodiments. The method of FIG. 2B can be implemented, for example, by the broadcast content service 113 illustrated in FIG. 1B.

2B, the broadcast content service can receive broadcast streams, broadcast metadata, and game metadata from, for example, a streaming service. As indicated at 252 in FIG. 2B, the broadcast content service may determine broadcast content for individual broadcasts, at least in part, from game metadata and broadcast metadata. 2B, the broadcast content service may add broadcast content to broadcast streams delivered to the spectacle device. In some embodiments, instead of or in addition to a specting system that adds broadcast content to broadcasts received from broadcast device(s) as illustrated in FIG. 2A, the broadcast content service is logically It can be between the specting system and the spectator device(s). In some embodiments, the broadcast content service can receive broadcasts and game metadata from the specting system, eg, as described with reference to element 204 of FIG. 1A and at least partially game meta. Broadcast content for broadcast may be generated according to data. In some embodiments, the broadcast content service can add broadcast content as additional content to broadcast content generated by specting systems. In some embodiments, the broadcast content service can change the broadcast content generated by specting systems. In some embodiments, in addition to receiving and processing game metadata to generate broadcast content, the broadcast content service can obtain broadcast metadata generated by the specting system, and at least partially broadcast Broadcast content for individual broadcasts can be generated from the cast metadata.

As indicated by 256 in FIG. 2B, the broadcast content service can receive and process spectacle interactions with the broadcast content. In some embodiments, the broadcast content service can acquire and process broadcast content and spectacle interactions such that the broadcasts and broadcast content presentation in a game specting environment in various ways described herein. And processing. In some embodiments, the broadcast content service may generate feedback on the specting system that the specting system can apply to affect the game specting environment. In some embodiments, the specting system can provide game feedback to the game system(s) based on the feedback; The game system(s) 120 may apply feedback to affect game execution and game play on the game system. In some embodiments, the specting system may also provide broadcast feedback to the broadcast device(s) based at least in part on feedback received from the broadcast content service.

As indicated by the arrow returning from element 256 to element 250, in at least some embodiments, the method of FIG. 2B allows the broadcast content service to generate broadcast content for broadcasts, and broadcast content Interactions with can be received and processed to be an iterative process that affects, for example, game specting, game execution, and game play.

game Specting Determining events in a game spectating environment

In some embodiments, the specting system can obtain event data indicating events or highlights in games and/or broadcasts running on game systems from one or more sources. Event data can be processed to determine events from broadcasts. The determined events can be used to determine broadcast content for broadcasts or otherwise, to affect broadcasts and/or games being broadcast.

In some embodiments, the specting system may receive indications of game events from game systems as game metadata according to a game system API provided to game systems by the specting system. Game events can include events that are common across two or more games and can also include game-specific events defined by individual game systems. Examples of game events may include, but are not limited to: specific achievements by specific players or teams of players; Level starts and completions; Beginnings, endings, or other important moments of battles, bouts, challenges, or other in-game events; In-game character entries, advances, deaths, etc.; Acquisition or loss of items, objects, powers, etc. by in-game characters or players; Or any event or moment that may have an interest in the game that runs on the game system in general.

In some embodiments, instead of or in addition to receiving indications of game events from the game system(s), the specting system detects events in games and/or broadcasts running on the game systems. In order to obtain and analyze various inputs from participants (players, broadcasters, and/or spectors) in a game specting environment. Various participant inputs may include, but are not limited to, one or more of the following: audio or voice inputs such as in-game vocal communication or broadcast vocal channels; Video or image inputs (eg, images or video of participants' facial expressions or eyes); Text input such as in-game or broadcast text chat; Biometric inputs from players; And participant inputs broadcast via speculating user interfaces (UIs), such as voting or indicating inputs in-game or on broadcast events as highlights for broadcasts and/or games.

In some embodiments, participant inputs can be mapped and analyzed to specific events or types of events in an online game being broadcast on a broadcaster's channel. Examples of online in-game events that can be detected by analyzing participant inputs may include, but are not limited to: specific achievements by specific players or teams of players; Level starts and completions; Beginnings, endings, or other important moments of battles, bouts, challenges, or other in-game events; In-game character entries, advances, deaths, etc.; Acquisition or loss of items, objects, powers, etc. by in-game characters or players; Or any event or moment that may have an interest in the game that runs on the game system in general. For example, in a sports game, people (spectator) and/or player audio, text, or other inputs can be played in big plays, such as scoring plays or great defensive plays. ). As another example, in a MOBA game, participant inputs can be mapped to start, ending, or highlight moments in big battles. In some embodiments, participant inputs can be analyzed to detect potential upcoming events in an online gaming session. For example, in a sports game, certain people (spectator) and/or player audio patterns, text chats, or other inputs typically occur before a certain big event, such as the silence of people in front of an important attack play in a people football game. Or it can be mapped to very small people noise in front of big defensive play in chanting, or football games. In some embodiments, information determined from analysis of participant inputs may also indicate locations and times in the game universe for individual events. For example, analysis of spectacle and/or broadcaster audio, text, or other inputs can be used to determine specific times in the game timeline and specific locations or areas of the online game universe for events in game sessions broadcast by broadcasters. Can be represented.

In some embodiments, indications of events received from game systems and/or determined from participant input analysis can be used to generate broadcast content for individual broadcasts, as described herein.

5 is a flow chart of a method for determining events in a game specting environment according to some embodiments. The method of FIG. 5 may be implemented, for example, by a component, module, or service in the game specting environment illustrated in FIGS. 1A and 1B. As indicated at 500 in FIG. 5, the spectating system can stream broadcasts of game play received from broadcaster devices to spectacle devices. Broadcasts may include videos showing the gameplay of individual broadcasters participating as players in a game running on the game system. As indicated by 510 in FIG. 5, the spectating system may acquire event data representing events in broadcasts and/or games that are broadcast. As indicated by 520 of FIG. 5, the spectating system may determine events for broadcasts and/or games according to event data. 3A to 3D illustrate example methods and apparatus for determining events according to event data and obtaining event data. As indicated at 530 of FIG. 5, the spectating system may generate broadcast content for broadcasts according to at least partially determined events.

In some embodiments, event data obtained and processed by the specting system to detect events may include game events received from game systems. Game events for a given game system may indicate game-specific, in-game events defined and detected by individual game systems. In some embodiments, game events may be received as game metadata according to the game system API provided by the specting system. 3A and 3B illustrate receiving and processing game events provided by a gaming system according to some embodiments.

In some embodiments, the event data is input to the Spectators' and/or Broadcasters' for a Specting system that marks or tags interest or striking events or highlights in broadcasts. You can include it by replacing or adding event tags that represent it. 3A and 3C illustrate participants' event tagging inputs and processing for a specting system that can be used to determine events in broadcasts according to some embodiments.

In some embodiments, event data may include it in place of, or in addition to, participant (broadcaster and/or specator) audio and/or text inputs to the specting system. Participant audio or text inputs include broadcaster inputs such as broadcaster live broadcasts, in-game voice or text chats, and broadcast text chats, and spectator inputs such as specter voice comments, people noise, and broadcast text chats. It can contain. In some embodiments, the specting system may receive broadcasters' inputs from broadcaster devices according to the broadcasting UI/API, and the speculators from the specter devices according to the speculating UI/API 'You can receive inputs. 3A and 3D illustrate receiving and processing participant interactions with the specting system 100 to determine events or highlights in broadcasts according to some embodiments.

In addition to analyzing participant audio and/or text inputs to detect events, some embodiments may also collect and analyze other data from participants, and analyze it to detect events in games or broadcasts Can be used alone or in combination with the analysis of participant audio and/or text inputs. As an example, some embodiments obtain biometric data (eg, pulse, heartrate, perspiration, etc.) for participants from wearable devices, for example to collect biometrics, and The analysis can be analyzed and used to determine metrics that can be used alone or in combination with analysis of other inputs such as audio and text inputs to determine events in games and/or broadcasts.

As another example, some embodiments are images of participants' faces (broadcasters, players, commentators and/or specators) captured during game play or broadcast, eg participants' individual client Images captured by cameras attached to or attached to the devices may be acquired. Images can be analyzed using facial recognition techniques and techniques to sense emotions through the analysis of facial expressions, the analysis of other inputs such as audio and text to determine events in games and/or broadcasts It can be used alone or in combination with the analysis of the inputs.

As another example, some embodiments are images of participants' eyes (broadcasters, players, commentators and/or specators) captured during game play or broadcast, eg wearable computing devices such as smart It is possible to obtain images captured by cameras attached to or integrated with glasses, goggles, optical head-mounted displays, virtual reality (VR) headsets, and the like. Images can be analyzed using techniques to detect emotions or other conditions through tracking and analysis of eye movements, blinking, dilation, etc., and the analysis is a game and/or broadcast It can be used alone or in combination with analysis of other inputs such as audio and text inputs to determine in-field events.

3A illustrates event processing in a game spectating system according to some embodiments. In some embodiments, the specting system 400 is one or more computing devices that implement one or more components or modules of the specting system 400 and provide one or more APIs to the specting system 400 functionality. For example, it may include one or more server devices. In some embodiments, the specting system 400 determines an event detection 470 component or module that determines or predicts events in the broadcasts 442, and broadcast content from the determined events or event predictions ( 426) may include broadcast content generation 480 components or modules, but are not limited thereto. Specting system 400 also includes, but is not limited to, various data 478 used to analyze participant inputs and other event data sources to detect events, and event information 479 describing the detected events. It is not limited to storing data and information, including, but not limited to, storage devices, services, or other devices including systems (shown as storage 477 ).

In some embodiments, the event detection 470 component is a game event processing 472 module that processes game events 434 to determine game-specific events in broadcasts 442, broadcasts 442 Participant event tag processing 474 component that processes event tags 466 to determine participant-specific events within the participant's inputs (audio, video, text, speech () during broadcasts 442 speech, social media, etc.) to include a participant input processing 476 component that processes participant inputs 465 to determine events in broadcasts 442. In some embodiments, participant inputs 465 are analyzed and can be used to determine events in individual broadcasts 442 Input devices and techniques such as controllers or joysticks, motion tracking systems, gestures Inputs from based input systems, and the like.

In some embodiments, in addition to determining events in broadcasts 442, event detection 470 component generates information that predicts or predicts potential upcoming events in game sessions or broadcasts. In order to process various inputs. For example, in a sports game, audio, text, or other input can be analyzed to generate predictions of future big plays, or in MOBA or MMOG, audio, text, or other input can lead to battles or battles to take place Can be analyzed to generate predictions. In some embodiments, this information for predicting events in broadcasts can be provided to specators as broadcast content, for example, so that spectors can view predicted events in real time if desired.

In some embodiments, the specting system 400 can include a game system API 414 that game systems or other entities can provide game events 434 to the specting system 400. Or can be provided. Game events 434 can indicate game-specific events defined and detected by individual game systems 420. In some embodiments, the specting system 400 can include or provide a speculating UI/API 416 that provides an interface to speculators on individual specator devices 460. . Spectators interact with the specting system 400 via inputs 456 to the specting UI/API 416, for example, individual spectator devices via the specting UI/API 416. Interact with broadcast content 426 generated by the broadcast content generation 480 module from events or event predictions generated by the event detection 470 component provided to the spectators on 460 can do.

3B-3D further illustrate the components, modules, and operations of the example specting system 400 as shown in FIG. 3A.

3B illustrates game event processing for determining events in a game spectating system in accordance with some embodiments. In some embodiments, event data that can be received and processed by the specting system 400 to determine events in the broadcasts 442 are game events generated by the game systems 420 ( 434). Game events 434 for a given game system 420 may, for example, display game-specific, in-game highlights defined and detected by the individual game system 420. In some embodiments, specting system 400 may include a game event processing 472 module that processes game events 434 to determine game-specific events for broadcasts 442. have.

In some embodiments, the specting system 400 can include a game system API 414 that the game systems 420 can provide game events 434 to the specting system 400. Or may be provided. The game event 434 can display a game-defining interest or a remarkable event or highlight in gameplay on the individual game system 420. 3B illustrates a non-limiting example format for game events 434 according to some embodiments. In this example, game event 434 may be a record that includes, but is not limited to, one or more of the following:

게임 이벤트에 대한 “현실 세계 시간(real world time)”을 나타내는 타임스탬트(timestamp) (날짜/시간).

Timestamp (date/time) representing the “real world time” for the game event.

이벤트 (434)를 생성한 게임 시스템 (420)을 식별하기 위해 사용될 수 있는 게임 ID.

Game ID that can be used to identify the game system 420 that generated the event 434.

게임 시스템 (420)에 의해 실행되는 특정 게임 세션을 식별하기 위해 사용될 수 있는 게임 세션 ID.

Game session ID that can be used to identify a particular game session executed by game system 420.

게임 이벤트에 대한 게임 세션 타임라인 (“게임 시간”)상에 / 게임 유니버스내 시간을 나타내는 게임 세션 타임스탬트 (날짜/시간).

On the game session timeline (“game time”) for a game event / Game session timestamp (date/time) indicating the time in the game universe.

게임 이벤트에 대한 이벤트 유형. 이벤트 유형(event type)은 모든 게임 시스템들 (420)에 걸쳐 또는 일부 게임 시스템들 (420)에 걸쳐 (예를 들어, 장르내 모든 게임들) 공통일 수 있거나, 또는 특정 게임 시스템 (420)에 특정될 수 있고/ 특정 게임 시스템에 의해 정의될 수 있다.

Event type for game events. The event type may be common across all game systems 420 or across some game systems 420 (eg, all games in a genre), or may be specific to a particular game system 420. It can be specified/defined by a particular game system.

이벤트에 지속기간(duration). 지속기간은 실제 시간(real time)으로, 게임 시간(game time)으로, 또는 양쪽으로 표시될 수 있다.

Duration of the event. The duration can be expressed in real time, game time, or both.

이벤트에 대한 게임 유니버스 또는 게임 월드 내 위치.

Game universe or location within the game world for the event.

다른 이벤트 정보. 예를 들어, 이벤트에 포함된 플레이어들 또는 플레이어들의 팀들, 이벤트에 포함된 브로드캐스터들, 이벤트의 요약 설명, 이벤트에 대한 등급(rating) (예를 들어, 1 내지 10 스케일에 기초한 이벤트 중요성(event significance))을 식별하는 정보, 또는 일반적으로 게임내(in-game) 이벤트에 관련될 수 있는 임의의 정보.

Other event information. For example, players or teams of players included in the event, broadcasters included in the event, a summary description of the event, rating of the event (e.g. event importance based on a scale of 1 to 10) significance)), or any information that may generally relate to an in-game event.

In some embodiments, game event processing 472 module can receive and process game events 434 to determine game-specific events or event predictions for broadcasts 442. In some embodiments, the game event processing 472 module can map at least some of the game events 434 for specific broadcasts 442. In some embodiments, for example, broadcast 442 may include metadata representing a broadcaster/player for a particular game system 420, game session, and broadcast 442, and a game event The processing 472 module assigns at least some of the game events 434 to specific broadcasts 442 according to the game ID, game session ID, timestamp, and other event information fields of the game event 434 records. Can be mapped. After the game event 434 is mapped to the broadcast 442, information in the event 434 record can be used to generate broadcast content 426A for the broadcast 442.

In some embodiments, in addition to displaying events in games, game events 434 that predict or predict potential future events in online game sessions may be provided. For example, in a sports game, a game event 434 may be provided prior to an important offensive play, or a game event 434 may be provided indicating an upcoming fight or battle in MOBA or MMOG. In some embodiments, this information for predicting or predicting events in games can be provided to speculators as broadcast content 426A so that spectors can view broadcasts of anticipated events in real time if desired.

3C illustrates participant event tag processing for determining events in a game spectating system in accordance with some embodiments. In some embodiments, event data that can be received and processed by the specting system 400 to determine events from the broadcasts 442 is broadcast through individual devices 440 and 460. Event tags 466 generated by casters and/or spectors. Event tags 466 for a given broadcast 442 may indicate interest or significant events within broadcast 442 as identified by the broadcaster's broadcaster and/or spectors. . In some embodiments, specting system 400 will include a participant event tag processing 474 module that processes event tags 466 to determine participant-specific events from broadcasts 442. Can be.

In some embodiments, the specting system 400 is a broadcasting and specting UI/ in which broadcasters and/or spectors can provide event tags 466 to the specting system 400. APIs can be provided. Event tag 466 can indicate a participant-defined interest or a prominent event or highlight in individual broadcast 442. 3C illustrates a non-limiting example format for event tags 466 according to some embodiments. In this example, event tag 466 may be a record that includes, but is not limited to, one or more of the following:

이벤트 태그에 대한 타임스탬트 (날짜/시간).

Timestamp (date/time) for the event tag.

이 태그 (466) 이벤트가 생성된 브로드캐스트 (442)를 식별하기 위해 사용될 수 있는 브로드캐스트 ID.

The broadcast ID that can be used to identify the broadcast 442 from which this tag 466 event was generated.

이 태그 (466) 이벤트를 생성한 특정 브로드캐스터 및/또는 스펙테이터를 식별하기 위해 사용될 수 있는 참가자 ID.

Participant ID that can be used to identify the specific broadcaster and/or spectator that generated this tag 466 event.

태그 (466)에 대한 이벤트 유형. 일 예로서, 일부 실시예들에서 태그 이벤트 유형들은 관심 또는 현저한 이벤트의 스타트 및 개별 이벤트의 끝을 표시하는 “스타트(statrt)” 태그들 및 “스탑(stop)” 태그들을 포함할 수 있고; 따라서, 두개의 태그들 (스타트 및 스탑 태그)은 개별 참가자에 의해 표시된 개별 브로드캐스트 (442)에 이벤트를 정의할 것이다.

Event type for tag 466. As an example, in some embodiments, tag event types may include “statrt” tags and “stop” tags to indicate the start of an event of interest or salient and the end of an individual event; Thus, two tags (start and stop tags) will define the event in separate broadcasts 442 indicated by the individual participants.

In some embodiments, event tags 466 can include other information about a participant-specific event. For example, in some embodiments, event tags 466 can indicate the duration for an individual event. In some embodiments, event tags 466 can indicate a location in the game universe or game world for the event. In some embodiments, event tags 466 include information identifying players or teams of players included in the event, broadcasters included in the event, a summary description of the event, and a rating for the event (eg, It may include one or more of the information identifying the importance of events based on 1 to 10 scale.

In some embodiments, specators and/or broadcasters broadcast (442) via individual UIs, for example, to determine whether an event is considered an important or significant event or highlight for broadcast 442. ) You can vote on events in streams or game sessions. For example, spectors and/or broadcasters may be prompted to respond to an up or down vote for event(s) in broadcast 442 streams or game sessions. Event tags 466 may include voting information for events (eg, up/down voting information) in broadcast 442 streams or game sessions.

In some embodiments, participant event tag processing 474 module can receive and process event tags 466 to determine broadcast content 426 for broadcasts 442. In some embodiments, the participant event tag processing 474 module can map at least some of the event tags 466 to specific broadcasts 442 according to the broadcast ID. After event tags 466 are mapped to broadcast 442, event tags 466 can be used to generate broadcast content 426B for broadcast 442. For example, in some embodiments, event tags 466 can be used to identify and extract highlight segments in broadcasts 442, which highlight segments can be provided as broadcast content 426B.

In some embodiments, to identify events in broadcast 442 from event tags 466 for broadcast 442, the participant event tag processing 474 module broadcasts how many and/or which participants broadcast The event tags 466 may be analyzed according to the information in the tags 466 to determine if a particular event in the cast 442 or game session has been tagged. For example, in some embodiments, the participant event tag processing 474 module broadcasts (if at least a threshold number or percentage of spectators tagged the event as a prominent event and/or voted the event as a prominent event). It can be determined that the event tagged 442) is an important or remarkable event. As another example, the broadcaster's tag 466 can automatically make an individual event a prominent event, or alternatively, the broadcaster's tagged event is a specter to determine if the event is considered a prominent event. It can be attached to a vote by the field. In some embodiments, the participant's opinions regarding events expressed through tags 466 can be weighted; For example, a given spectator can be a highly-rated spectator or designated commentator, and the spectator tags 466 can automatically make an individual event a prominent event, or Spectator tags 466 are potentially prominent events and can be given a greater weight than other spectator weights when tagged or voted on the events.

In some embodiments, in addition to indicating prominent events in the broadcasts, predictive event tags 466 may be provided that predict or predict potential future events in the broadcasts. For example, in a sports game, spectors and/or broadcasters can generate event tags 466 in the prediction of important attack play, or a potential future fight or battle in a MOBA or MMOG game. Indicating event tags 466 can be generated. In some embodiments, this information for predicting or predicting events in games can be provided to speculators as broadcast content 426B so that spectors can view broadcasts of anticipated events in real time if desired.

3D illustrates participant inputs processing to determine events in a game specting system according to some embodiments. In some embodiments, event data that can be received and processed by the specting system 400 to determine events in the broadcasts 442 is transmitted to the specting system 400 (eg, a broadcaster. Participant (broadcaster and/or specter) audio and/or text inputs for live broadcast, in-game voice or text chat, broadcast text chat, spectacle voice comments, people noise, etc.). In some embodiments, the event data may include it in place of or in addition to the video of participants (broadcasters and/or specators) captured during broadcasts 442. In some embodiments, the specting system 400 is configured to respond to participants' various inputs and interactions (eg, audio, video, text, speech, social media, etc.) during broadcasts 442. And participant input processing 476 component that processes participant inputs 465 to determine events from broadcasts 442 based thereon.

In some embodiments, the participant input processing 476 component is configured to participate in participants' various inputs to detect events 494 in broadcasts 442 based on inputs related to broadcasts 442 ( For example, it may include or have access to one or more analysis modules 492 that analyze and process audio, video, text, speech, etc.). In some embodiments, analysis modules 492 can include, but are not limited to, video analysis 492A module, audio analysis 492B module, text analysis 492C module, and content analysis 492D module. It does not work.

In at least some embodiments, generally, analysis module 492 can perform analysis on its input signal(s) and/or other input data to determine one or more metrics from the inputs, and then The determined metrics can be matched to known patterns. The patterns can then be mapped to certain types of events that can be output as sensed events 494. In some embodiments, in addition to detecting events 494 indicative of events or highlights of interest or striking in broadcasts 442, analysis module 492 can be used to detect potential in game sessions or broadcasts. Can detect events 494 that predict or predict events that will occur in the future. For example, in a sports game, events 494 predicting future big plays can be sensed, or events 494 predicting future fights or battles in MOBA or MMOG. .

In some embodiments, participant input processing 476 component may also include one or more sources of analysis data 499 that may be used to analyze participants' interactions to sense events 494 or You can have access to it. Analysis data 499 may include data specific to games and game systems (eg, mappings of specific audio, text, and/or speech to specific events in games), and may also include specific Data specific to participants or groups of participants (eg, audio or speech patterns, facial metrics, etc.).

In some embodiments, the participant input processing 476 component detects events 494 detected by analysis modules 492, for example to determine broadcast content 426C for broadcasts 442. It may also include a sensed event processing (496) module to process. In some embodiments, analysis modules 492 can provide detected events 494 to sensed event processing 496 module, for example, according to the API for module 496. Detected events 494 may indicate potentially interesting or prominent events in broadcasts 442 as determined from analysis of participants' various inputs 465 (audio, video, chat, social media, etc.) Can be. 3D illustrates a non-limiting example format for sensed events 494 according to some embodiments. In this example, the detected event 494 can be a record that includes, but is not limited to, one or more of the following:

감지된 이벤트(494)에 대한 적어도 하나의 타임스탬트 (날짜/시간). 타임스탬트(들)은 실제 시간 (브로드캐스트) 타임스탬트들 및/또는 “게임 시간” 타임스탬트들을 포함할 수 있다.

At least one timestamp (date/time) for the detected event 494. The timestamp(s) may include real time (broadcast) timestamps and/or “game time” timestamps.

이 이벤트 (494) 가 감지된 브로드캐스트 (442)를 식별하기 위해 사용될 수 있는 브로드캐스트 ID.

The broadcast ID that can be used to identify the broadcast 442 this event 494 was detected.

이 감지된 이벤트 (494)에 관련된 특정 브로드캐스터 및/또는 스펙테이터를 식별하기 위해 사용될 수 있는 참가자 ID.

Participant ID that can be used to identify a specific broadcaster and/or specator related to this detected event 494.

감지된 이벤트 (494)에 대한 이벤트 유형. 이벤트 유형은 게임내 이벤트 유형일 수 있고; 게임 이벤트는 모든 게임 시스템들 (420)에 걸쳐 또는 일부 게임 시스템들 (420)에 걸쳐 (예를 들어, 장르내 모든 게임들) 공통이거나 또는 포괄적일 수 있거나, 또는 특정 게임 시스템 (420)에 특정될 수 있고/ 특정 게임 시스템에 의해 정의될 수 있다.

Event type for the event detected (494). The event type may be an in-game event type; The game event can be common or comprehensive across all game systems 420 or across some game systems 420 (eg, all games in a genre), or specific to a particular game system 420 And/or can be defined by a particular game system.

In some embodiments, sensed event 494 records may include other information about the event. For example, in some embodiments, sensed event 494 records can indicate the duration for an individual event. In some embodiments, detected event 494 records may indicate a location in the game universe or game world for the event. In some embodiments, the detected event 494 records include information identifying players or teams of players included in the event, broadcasters and/or specators included in the event, a summary description of the event, and It may include one or more of the information that identifies the rating (eg, event importance based on a scale of 1 to 10). In some embodiments, the detected event 494 record is a confidence level for the event indicating how confident that the individual analysis module 492 correlates the analyzed input data to the displayed event 494. level).

In some embodiments, the participant input processing 476 component can include or have access to a video analysis 492A module. In some embodiments, participant inputs 465 are participant' participants attached to individual devices 440 or 460 or captured during broadcast 442 by integrated video cameras, for example (Broadcasters and/or Spectators). Participant video can be analyzed using facial recognition techniques and techniques for sensing emotions through analysis of facial expressions to determine metrics that can be used to identify events in individual broadcasts 442. For example, the broadcaster's facial expressions can be captured by a live video feed included in broadcast 442, and the video can be analyzed to sense the broadcaster's emotions during game play. . Various emotions that can be related to in-game events (wins, defeats, start-up in-game events, etc.) such as surprise, fear, happiness, and deep immersion (intense concentration), etc. can be detected. As another example, some embodiments include images of participants' eyes (broadcasters, players, commentators and/or spectors) captured during game play or broadcast 442, eg, a wearable computing device. Fields such as smart glasses, goggles, optical head-mount displays, virtual reality (VR) headsets, and similar, or can capture images captured by cameras attached to or integrated with it. Images can be analyzed using techniques to detect emotions or other conditions through tracking and analysis of eye movements, blinking, dilation, etc., and the analysis can be broadcast or in-game events. It can be used alone or in combination with analysis of other inputs, such as audio inputs, to determine the states of participants that can be correlated to casts events.

In some embodiments, the participant input processing 476 component can include or have access to an audio analysis 492B module. Online games and game specting systems can support communication and audio input/output for game players and for game specators. For example, online in-game players can communicate gameplay instructions, suggestions, comments, strategies, chats, or other information to other players in their team in-game via audio input to individual computing devices. As another example, a broadcaster may provide a live speech broadcast to speculators through an audio channel of a game specting system. As another example, specators in a game specting system may provide a cheer, comment, chat, or other audio input for broadcasts through the audio input channels to the game specting system. Synthesized participants' (player and/or spectacle) audio signals can be used to provide background chatter or "people noise" for online gaming or broadcasting. Participants' audio input signals can be captured, digitized, and digitized by audio-visual (A/V) input components on the participants' individual client devices, over a network to an online game or specting system. Can be sent. In an online game or specting system, participants' audio signals can be synthesized, processed, and transmitted to players' and/or specators' individual devices for output as game or broadcast audio.

In some embodiments, the audio analysis 492B module can process and analyze various audio inputs from players, broadcasters, and/or spectors to detect events 494. In some embodiments, the audio analysis 492B module can perform signal analysis, eg, time- and frequency-domain analysis, on audio signals to determine one or more audio signal metrics from the audio signals. have. The metrics can include, for example, one or more of amplitude, pitch, duration, and frequency metrics, and any related metrics that can generally be extracted from an audio or voice signal. Audio signal metrics can be analyzed to determine information about participants and/or game sessions, for example, by comparing metrics to known or learned audio patterns for individual participants or groups of participants.

In some embodiments, audio signals can be analyzed separately to determine metrics for each audio input, and the metrics can then be analyzed for groups of participants (players and/or specators). It can be normalized, synthesized and analyzed to determine. In some embodiments, instead of or in addition to separately analyzing audio signals and then synthesizing metrics for further analysis, the audio signals can be synthesized to generate information about groups of participants and metrics therefor. Or they can be combined and analyzed collectively.

In some embodiments, the participant acquired in or with the audio input signals can be used when the information is to analyze the audio input signals to determine information about specators and/or players. For example, participant information may indicate affiliation or team preferences for specators of a sports game based on the specator's profile information. Spectator audio signals for the game are segmented into two or more groups according to metadata as groups of fans of two opposing teams in a sports game such as football, for example, according to the team belonging to the'Spectators' ), and can be analyzed separately according to groups to determine group-specific information for the current game session or broadcast. For example, the group-specific information may indicate which group of spectors are currently cheering (cheering) or booing, which group is loudest and/or quietest, and so on. In some embodiments, player/broadcaster audio signals may also be segmented into groups (eg, opposing teams) according to player profile information for player group analysis.

In some embodiments, the information determined from the analysis of the participant audio inputs can be determined based on the analysis of the individual participants' vocalizations or other sounds in the individual audio signals, eg, the individual participants (players and/or Or the emotional state or conditions (eg, excitement, stress, fear, shock, surprise, amusement, etc.) of the speculators) Can be displayed. In some embodiments, the audio analysis information is based on an analysis of combined audio signal metrics for two or more participants (players and/or spectors) based on a group or people's state or conditions (eg, Instead of excitement, stress, approval, disapproval, etc.) or a state or conditions can also be indicated. In some embodiments, the information may also indicate a level for a determined state, an indication of how excited the people of the spector are, for example based on analysis of the overall spectacle audio input.

In some embodiments, information determined from analysis of participant audio inputs can be used to detect specific events 494 in an online game session or broadcast. For example, in some embodiments, at least some of the audio patterns with matching audio signal metrics can be mapped to specific types of individual online in-game events. For example, in a sports game, certain people (spectator) and/or player audio patterns can be mapped to big plays, such as scoring plays or massive defensive plays. In some embodiments, the information can predict or predict potential future events in an online game session or broadcast. For example, in a sports game, certain people (spectator) and/or player audio patterns typically occur before a certain big event, such as the silence or chanting of people in front of an important attack play in a people football game, or football. It can be mapped to very small people noise in front of the big defensive play in the game. In some embodiments, the information may also indicate locations and times in the game universe for specific events to which the analyzed audio signals are mapped. For example, analysis of aggregated spectacle or player audio signals and correlated metadata may indicate a specific time in the game timeline and a specific location or area in the online game universe.

In some embodiments, the audio analysis 492B module can identify and extract words, phrases, or other content from input audio associated with broadcast 442. In some embodiments, the audio analysis 492B module can analyze the content to detect events 494 in broadcast 442. For example, the audio analysis 492B module may include keywords or phrases that the keywords or phrases it identifies in the audio stream(s) of the broadcast 442 are related to keywords or phrases related to events in the gameplay, such that the broadcaster You may want to map to keywords or phrases related to specific events in the genre or game participating as a player, and/or to keywords or phrases related to specific participants (eg broadcasters). In some embodiments, the audio analysis 492B module is another analysis module 492 that performs analysis of the extracted content to detect events 494 for broadcast 442, such as content analysis ( 492D) The extracted content can be provided to the module.

In some embodiments, the participant input processing 476 component can include or have access to a text analysis 492C module. Instead of or in addition to audio input, online games and game specting systems can support communication and text input/output for game players and for game specators. For example, players in online games can communicate gameplay commands, suggestions, comments, strategies, or other information to other players in their team in-game through text input in an in-game chat window. As another example, broadcasters and spectors can participate in chat windows associated with specific broadcasts 442 in game specting system 400. In some embodiments, the text analysis 492C module may include one or more sources (eg, in-game) in broadcast 442 to identify and extract words, phrases, or other content from the input text. -game) window and broadcast chat window). In some embodiments, the specting system 100 is not limited to text from other input sources or channels, including but not limited to inputs from social media channels such as “tweets” or instant messaging (IM). It may replace one or more interfaces that can acquire, process, and analyze inputs, or may also include interfaces. In some embodiments, the text analysis 492C module can analyze the extracted text content to detect events 494. For example, the text analysis 492C module may include keywords or phrases that it identifies from the content of the chat windows associated with broadcast 442 to keywords or phrases related to events in the gameplay, such that the broadcaster You may want to map to keywords or phrases related to specific events in the genre or game participating as a player, and/or to keywords or phrases related to specific participants (eg broadcasters). In some embodiments, the text analysis 492C module extracts content to another analysis module 492, eg, content analysis 492D module, that performs analysis of the extracted content to detect events 494. Can provide.

In some embodiments, the participant input processing 476 component can include or have access to a content analysis 492D module. Content analysis module 492D can receive content (eg, words and/or phrases) extracted from audio/speech and/or text chat inputs for broadcasts 442, events The received content may be analyzed to detect 494. For example, the content analysis 492D module allows keywords or phrases from the extracted content to be associated with keywords or phrases related to events in game play, generally the genre or game of the game in which the broadcaster participates as a player. You may want to map to keywords or phrases related to specific events, and/or keywords or phrases related to specific participants (eg, broadcasters). In some embodiments, the content analysis 492D module can access one or more sources of analysis data 499 to retrieve data sets of keywords or phrases related to particular genres, games, broadcasters, etc. There is; Data sets can map keys to specific events or types of events of interest that can be considered important or prominent events or highlights in broadcasts.

4 illustrates participant input processing to determine broadcast-related information in a game spectating system in accordance with some embodiments. In some embodiments, instead of or in addition to or in addition to the events 494 detection and process, the participant input processing 476 component is another broadcast that can be applied to the game specting environment in various ways described herein. In order to generate relevant analysis information 427, for example, inputs to the game system engine are generated through the game system API of the specting system affecting game execution and game play illustrated in FIGS. 19 to 26. One or more participant inputs 465 may be processed to determine rewards for the participants illustrated in FIG. 16, either to play or to generate broadcast content 426 for display in the game spectating interface. . In some embodiments, participant inputs 465 may include, but are not limited to, audio, video, and text inputs to the specting system through specting UI 416. In some embodiments, participant inputs 465 are input devices and techniques, such as controllers, coupled or incorporated into specter devices that can be analyzed and used to generate broadcast-related analysis information 427. Or joysticks, motion tracking systems, gesture-based input systems, and the like. In some embodiments, the specting system 400 is not limited to inputs and similar from social media such as “tweets” or instant messaging (IM) to generate broadcast-related analysis information 427. It may include one or more interfaces capable of obtaining and processing inputs from other input sources or channels, including inputs to other input channels that can be analyzed. The following provides some examples of detecting and applying broadcast-related analytic information 427 in a game specting system. However, note that these examples are not intended to be limiting.

As an example of detecting and applying broadcast-related analysis information 427 in the game specting system, the broadcast-related analysis information 427 may be determined for specators of one or more broadcasts of a particular online game. Is leveraged to identify specific players, locations, areas, or areas in the game world of the online game being broadcast, for example, which activity is “hot” as illustrated in FIG. 9 (leverage). A map of the online game world or a portion of the map may be displayed on at least some specator devices by, for example, the specting UI illustrated in FIG. 9, and in-game according to analysis of specator inputs 495 Players, teams, areas, areas, or locations identified as being active can be marked or highlighted on the map. In some embodiments, instead of or in addition to, or in addition to, a map of active or interested players and/or locations, players and/or players of interest determined specifically by analysis of the spectator inputs 495 Character information to be displayed can be displayed. In some embodiments, audio announcements or sounds can be used to raise attention to specific players and/or locations. In some embodiments, information about locations and/or players of interest in the game world is also fed back to game players and/or broadcasters, eg, broadcast-related analysis information to broadcaster devices. It can be provided through. In some embodiments, information about players and/or locations of interest in the game world can be used to generate feedback or inputs to the game system, as illustrated, for example, in Figures 19-26.

As another example of detecting and applying broadcast-related analytical information 427 in a game specting system, the analytical information 427 is an emotional or emotional state (eg, stress, excitement) for one or more of the broadcasters. , Anger, sadness, happiness, frustration, etc.). The analysis information 427 may be used to generate inputs to the game system engine through the game system API of the specting system. The avatars or online characters of players in the game universe can be affected visually or otherwise, in response to inputs.

As another example of detecting and applying broadcast-related analysis information 427 in the game specting system, the analysis information 427 for speculators is leveraged to influence game characters and gameplay of broadcasters. Can be. For example, analysis of the audio and/or text chat inputs 465 for speculators watching a particular player's broadcast shows that the player/broadcaster backs the specator when compared to other players in the game. You can indicate whether you have or whether your spectator is a favorite. This information can be positively influenced or compensated for, for example, by boosting player health, by providing surfers, by providing points, or in various other ways to positively affect or reward the player's avatar or character in the game. It can be used to generate inputs to the game system engine through the game system API in the Ting system. In some embodiments, teams of players corresponding to the broadcasters can be identified, and the teams are based on analysis of the specter audio and/or text chat inputs 465 for the broadcaster(s) regarding the team. So it can be influenced by the inputs to the game system engine.

As another example of detecting and applying the broadcast-related analysis information 427 in the game specting system, the comprehensive analysis information 427 of the specters of broadcasts of online games is broadcast of specific interests or current. It can be leveraged to identify active channels. In some embodiments, for example, by adding channels to a “recommended” or “hot” list for currently active channels or by highlighting the channel(s) on the specting UI, the spectator Channels of interest may be displayed on at least some of the devices. In some embodiments, information about the channels of interest is analyzed for broadcaster devices indicating the popularity or ranking of the comparison channel according to, for example, analysis of people noise or chat for individual channels. It may also be provided to broadcasters through feedback of information 427. In some embodiments, analysis information 427 indicative of channels or broadcasts of interest may be boosted, geared, or other in-game to, for example, broadcasters' in-game characters or avatars. It can be used to generate inputs to the game system engine through the game system API of the specting system that rewards individual broadcasters by providing advantages.

As another example of detecting and applying broadcast-related analysis information 427 in the game specting system, the comprehensive analysis information 427 for the specators of broadcasts of online games is used to identify broadcasters of particular interest. To be leveraged. In some embodiments, for example, by adding the broadcaster(s) to the “recommended” or “hot” list for the broadcasters or with the broadcasters and/or identified broadcasters on the specting UI Broadcasters of interest may be displayed on at least some of the spectator devices by highlighting the relevant channel(s). In some embodiments, the information about the broadcasters may be analyzed information about broadcasters' individual currently popular broadcasters' devices, for example according to the analysis of people noise or chat on individual channels. It may also be provided to broadcasters via feedback at 427. In some embodiments, the broadcasts' popularity analysis information 427 may be inputs to the game system engine through the specting system's game system API, eg, broadcasters' in-game characters or It can be used to create inputs that reward popular broadcasters by providing boosts, gears, or other in-game advantages to avatars.

As another example of detecting and applying the broadcast-related analysis information 427 in the game specting system, the comprehensive analysis information 427 for the speculators of broadcasts of online games is a specific online game of interest. For example, depending on the “people noise” or chat in the broadcasts of the current game, any activity may be leveraged to identify games currently “hot” or interested. In some embodiments, games of interest can then be displayed on at least a portion of the Spectator devices, for example by highlighting the games on the Specting UI. In some embodiments, analysis information 427 indicative of the game of interest is input to the game system engine through the game system API of the specting system, eg, the game is currently hot in the specting environment. It can be used to generate inputs for a particular game system representing Korean paper. The game system can use this input in a variety of ways, for example by providing boosts, gears, or other in-game advantages to players' in-game characters or avatars to compensate for at least some of the players.

As another example of detecting and applying broadcast-related analysis information 427 in the game specting system, audio and/or text chat inputs 465 for broadcasts or broadcasts are belonging or preferred by the speculators. It can be analyzed to detect matters. The sensed affiliation or preferences can be used to segment specators into two or more groups (eg, fans of specific players or teams). For example, specators are at least partially in response to certain events in a game or broadcast or at their specific audio and/or text chat inputs 465 (cheers, boo, loud, quiet, etc.) at certain times. Based on that, it can be sensed that they are fans of a particular player or team. As another example, specators may be based on a particular player or team based at least in part on specific keywords, phrases, or chants recognized in their audio and/or text chat inputs 465 for broadcast(s). Fans can be detected. In some embodiments, the sensed affiliation or preferences of the spectator can be added to their profile information. In some embodiments, the profiler's profile information can be modified over time based on further analysis of their audio or other inputs. In some embodiments, the analysis information 427 indicating the affiliation belonging to or preferences is input to the game system engine through the game system API of the specting system, for example, how many specators are currently in game It can be used to generate inputs for a particular game system that indicates if you are a fan of two or more teams. The game system provides this input to the players in-game characters or avatars in a variety of ways, for example based on their fan base, to provide boosts, gears, or other in-game advantages among the players. It can be used by compensating for at least a portion or by providing visual and/or audio indications belonging to the'Spectators', for example, as illustrated in FIG. 22.

As another example of detecting and applying broadcast-related analytic information 427 in the game specting system, audio and/or text chat inputs 465 for the broadcast may, for example, detect belonging or preferences Segment into two or more groups (eg, fans of specific players or teams) based on analysis of spectacle' audio and/or text chat inputs 465 or profile information for individual specators. It can be, and can be analyzed separately according to groups to determine group-specific information for games in the specting system. For example, the group-specific information may indicate which group of spectors are currently cheering or booing, which group is the loudest and/or quietest, and so on. The group-specific information is input to the game system engine through the game system API of the specting system, for example, a specific game system indicating the current levels of excitement in groups supporting two or more spectator groups and opposing teams. Can be used to generate inputs for. The game system uses this input in a variety of ways, e.g. visual and/or audio feedback to players and/or specators in the game specting system, e.g., groups that support opposing teams. It can be used to provide visual and/or audio feedback indicating current levels. For example, on one aspect of a stadium or arena in an online sports game, the virtual representations of the speculators are greatly cheered by speculators determined to be fans of a particular team and/or player, for example as illustrated in FIG. 22, or You can make them stand up when they boo, shake their flags, or otherwise, respond visually or audibly.

As another example of detecting and applying broadcast-related analytical information 427 in the game specting system, the spectacle audio output is in response to the analytical information 427, the speculators, specific groups of specators (eg For example, it may be provided to the specific fans) and/or to the broadcaster(s) by the game speculating system via the broadcast's audio channel(s). For example, when specters determined to be fans of a particular team and/or player are determined to cheer or boo loudly based on analysis of specator's audio and/or text chat inputs 465, cheers or Yoo's Spectator audio output can be provided by the game specting system to at least some of the players (eg, to fans of a particular team) and/or via the broadcast's audio channel(s). . As another example, the analysis of the Spectators' audio and/or text chat inputs 465 specifically targets inputs of interest from individual spectors or groups of specators (eg, highly acclaimed or evocative). Spectators or groups, screams, booing players, etc.), and the Spectator audio output of the audio inputs of interest can be provided by the game specting system via the broadcast's audio channel. In some embodiments, the Spectator audio output can be generated from the Spectator audio input(s) or as a mixture thereof. In some embodiments, the Spectator audio output is “canned” and pre-recorded sounds or sound tracks (eg, people cheering or booing) played in response to the analysis information 427. (pre-recorded), can be synthesized (synthesize). In some embodiments, different groups for games' current responses such as cheers, enthusiasm, or disappointment analysis information 427 are inputs to the game system engine through the gaming system API of the specting system, eg For example, it can be used to generate inputs to a particular game system indicating how different groups of specators are currently responding. The game system provides this input to the players in-game characters or avatars in a variety of ways, for example based on their fan base's current enthusiasm level, to provide boosts, gears, or other in-game advantages among the players. It can be used by compensating at least in part or by providing visual and/or audio indications of groups' current responses, for example, as illustrated in FIG. 22.

As another example of detecting and applying broadcast-related analytical information 427 in the game specting system, specters' audio and/or text chat inputs 465 for a game or broadcast are currently specters of interest. For example, it can be analyzed to detect specific spectors that are loudly cheering or shouting or booing the player, or particularly happy, angry, or excited specters. The audio input of the Spectator's interest can be provided to other participants (Spectators and/or Broadcasters) by the game Spectating system via the broadcast's audio channel. In addition, in some embodiments, their video or images identified as presently interested based on the audio input of the speculators are pictured overlaid on the broadcast video, for example, to the speculators and/or broadcasters. It may be provided in a picture-on-picture window. The video is a phantom video or images of avatars representing the spectater(s) and simulating their perceived emotional state, or a video of the spectater(s) of interest captured by video cameras within the spectater's specting environment. Can be

6A provides non-limiting examples of a specting user interface for a game specting system according to some embodiments. Specting UI 602 is, for example, a web page of a game specting system website via a web browser, as an interface to a game specting web application or mobile application, or other network-based game specting It can be provided as an interface to applications. Specting UI 602 is not limited, but controls 610, current broadcast pane 630, games 650, channels 660, and video on demand It may include one or more panes or regions including one or more of 670. Controls 610 may include one or more UI elements that interact with the game specting system, in a navigation or otherwise manner. Games 650 may display UI elements corresponding to one or more online games 652 currently supported by or through a game specting system. This example shows a racing (652A) game, a football (652B) game, and a space explorer (652C) game. Channels 660 correspond to one or more currently active (or upcoming) broadcasts or channels 662, eg, channels 662 corresponding to broadcasters for the currently selected game 652. UI elements can be displayed. In this example, the Space Explorer 652C game is selected, and channels 662 show three broadcasters 662A, 662B, and 662C for the currently selected game 652C. Video on demand 670 displays UI elements corresponding to one or more videos 672, including, but not limited to, pre-recorded broadcasts and/or highlight reels available for viewing. can do. In this example, video on demand 670 shows example pre-recorded videos 672A-672C and highlight reel 672D for the currently selected game 652C. Although not shown, in some embodiments, the specting UI 602 includes recommended games 652, channels 662 (broadcasters), and recorded videos including but not limited to highlight reels. A recommendation pane capable of displaying UI elements corresponding to one or more of 672 may be included.

In some embodiments, the content of recommendations, channels 660 and/or video on demand 670 may be determined, at least in part, according to the currently selected game 652. For example, in some embodiments, the spectator may play a game (to watch currently active channels 662 for the selected game 652C and to watch recordings of broadcasts for the selected game 652) 652C). Although not shown, in some embodiments, UI 602 may allow the spectator to select specific broadcasters, and the content of recommendations, channels 660 and/or video on demand 670 may be It may be determined, at least in part, according to the currently selected broadcaster.

The current broadcast pane 630 is a live broadcast or channel 662 currently selected (channel 662A in this example), or a video stream (broadcast) for the currently selected video 672 being played on an individual spectacle device. Video player 632 with A/V controls 633 displaying (shown as cast 634 ). Broadcast 634 is, for example, a broadcaster/player, in this example a window 635 showing a live view of broadcaster/player A, and a broadcaster/player viewpoint or perspective or buzz eye. It may include a gameplay video viewed from a bird's eye view. Video player 632 typically also can include one or more of in-game audio, broadcaster audio, and audio commentary or “crowd noise” from specators. Also play an audio stream. In some embodiments, the audio may also include play-by-play calls or live broadcasts from the commentator. In some embodiments, the current broadcast pane 630 may also include a chat 636 pane where a broadcaster and/or specator text chat can be displayed. In some embodiments, the current broadcast pane 630 may also include a highlight 635 pane that displays highlights, eg, highlights from the currently active or selected highlight reel or highlights from a broadcast. In some embodiments, the current broadcast pane 630 may also include one or more UI elements through which the spectator can control the highlight 635 display.

In some embodiments, the current broadcast pane 630 may include or provide UI elements capable of displaying broadcast content based at least in part on game metadata for the game being broadcast 634. Can. At least some of the UI elements can be or include active UI elements that initiate or perform some action when selected. In this example, the space explorer 652C in-game gameplay is currently being broadcast, so the broadcast content includes content related to the space explorer 652C game.

As shown in this example, in some embodiments, the current broadcast pane 630 may include a broadcast content 640 pane where spectors can view information about different categories of game content. . For example, the broadcast content 640 pane is a tab that allows spectators to view information about players, items, locations, events, or other categories of game content described in game metadata. ). For a category of content, spectors can select and watch information about specific instances of the content, for example, specific players. For a particular instance of content, spectors can watch additional details.

As shown in this example, information about player A in the Space Explorer 652C game being broadcast is shown. Player information includes, for example, the player's name and affiliation (eg, team), the player's skills or powers, the player's skill or experience levels, the player's ratings, achievements (achievements) Field, and other statistics, the player's gear such as tools, outfit/clothing, and weapons, or any other information that the game can maintain or track against the players. In this example, the viewer interacted with broadcast content 640 to watch the player's gear, and further chose to watch the player's weapons. From the list of displayed weapons currently held by player A, the viewer selected a Disrupter Pistol to view descriptive information about this particular item of the player's in-game gear. The description information may include, for example, the image(s) of the item (“DP9000”) and text description. For example, for a weapon, the descriptive information can indicate the weapon's range, capacity, and effectiveness. In some embodiments, the descriptive information may include usage information for a specific item or type of item. For example, a list of all players using an item such as a particular sword or other weapon may be provided. In some embodiments, the descriptive information may include statistical data for in-game content. For example, popularity or ratings may be provided based on player usage and/or participant voting, for different parts of the game gear or weapons.

In some embodiments, the broadcast content 640 pane may include UI elements from which a viewer can order, purchase or otherwise obtain game-related content. Game-related content is virtual game items or objects that can be obtained for use in games (eg, digital representations of physical objects) such as in-game gear, clothing, weapons, characters, avatars Physical items, such as physical representations of virtual objects from within the games (e.g., powers, etc.) (e.g., physical representations of in-game weapons such as swords, action figures, toys ), etc.), and/or game-related physical goods such as t-shirts or hats. In some embodiments, the specting system can provide or provide access to a “print on demand” service such that 3D printing technology can be used for game-related objects or items (eg, in-game Characters, weapons, vehicles, monsters, etc.) or can be used to print physical objects based on input designs. Designs or instructions for the objects can be obtained from game systems in game metadata, or otherwise, can be obtained. For example, in the broadcast content 640 pane shown in FIG. 6A, the viewer may obtain a virtual DP9000 pistol for use in space explorers games and/or a game system provider, online merchant, manufacturer, or To order or purchase a physical model of the DP9000 Pistol from another entity, “ GET IT ! ”You can select UI elements.

In some embodiments, broadcast content based at least in part on game metadata for the game being broadcast 634 is overlayed, blended, or composited onto the video stream content to be displayed on broadcast 634. ). This broadcast content may be referred to in the present application as overlay content. In some embodiments, the overlay content can be added to the video stream by the speculating service 100 illustrated in figures 1a and 1b. In some embodiments, the overlay content is to be added in place of or in addition to the video stream by the broadcast content service 113 between the specting service 100 and at least some of the specator devices 160. Can be. The overlay content may include text and/or graphic content. As a non-limiting example, text tags or captions can be added to objects or scenes in the video stream. For example, name tags (shown as A, B, C, D, and E in FIG. 6A), shown in FIG. 6A, are added to the characters in the video stream so that spectors can identify players in the game. Can be. As another example, objects or characters of interest may be identified from game metadata and/or broadcast metadata, and the objects or characters may be visually displayed using overlay content in a video stream. For example, game metadata and/or broadcast metadata may indicate the emotional or emotional state of one or more of the players (eg, stress, excitement, anger, sadness, happiness, frustration, etc.) In other words, the avatars or online characters of players displayed in the game universe can be visually modified using colors, for example, to indicate the emotions or emotional states of individual players. For example, as shown in FIG. 6A, character E in broadcast 634 is highlighted using overlay content that changes the visual appearance of the character in the video stream.

As another example of using overlay content, in some embodiments, objects or regions in broadcast 634 can be made to interact using overlays. For example, in some embodiments, at least some objects displayed in broadcast 634 may be interactive so that the spector broadcasts to open an overlay window 638 that provides information about the object. Objects in the cast 634 can be selected. For example, in FIG. 6A, the Spectator used the cursor to select a spacecraft and opened a window 638 showing the ship's name, type, and capabilities. In some embodiments, the overlay content on broadcast 634 can include UI elements that the viewer can order, purchase or otherwise obtain for game-related content. For example, in FIG. 6A, a viewer orders a physical model of a Harpoon XL ship from a merchant or manufacturer to obtain a virtual Harpoon XL ship for use within the “Space Explorers” game, or “ GET IT ! ” in the overlay window (638) for purchase . ”You can select UI elements.

6B provides other non-limiting examples of a specting UI for a game specting system according to some embodiments. In some embodiments, the specting UI 652 is metadata for the game being broadcast 634 (in this example, the Space Explorers game), eg the individual game system or other source illustrated in FIG. 1C. It may include or provide UI elements capable of displaying broadcast content based at least in part on game metadata received from. At least some of the UI elements can be or include active UI elements that initiate or perform some action when selected. 6B provides examples of speculating user interface elements and methods for replaying a pre-recorded broadcast or exploring a broadcasted game based at least in part on game metadata. Specting UI 652 is, for example, a web page of a game specting system website through a web browser, as an interface to a game specting web application or mobile application, or other network-based game specting. It can be provided as an interface to applications. Specting UI 652 is not limited, but video player 632 with controls 610, A/V controls 633, broadcast content 640, world map 696 ), broadcasts 690, and chat windows 636.

Controls 610 may include one or more UI elements that interact with the game specting system, in navigation or otherwise. Video player 632 may display a video stream (shown as broadcast 634) for replay of the previously selected broadcast or for the currently selected broadcast 692 (in this example, broadcast 692A). Can be. Broadcast 634 is, for example, a broadcaster/player, window 635 showing a live view of broadcaster/player A in this example, and a gameplay video viewed from a broadcaster/player's viewpoint or perspective or buzz eye view. It may include. Video player 632 also typically also plays in-game audio from spectors, broadcaster audio, and audio streams that may include one or more of audio live broadcasts or “people noise”. In some embodiments, the audio may also include live play calls or live broadcasts from the commentator. In some embodiments, the specting UI 652 may also include a chat 636 pane where a broadcaster and/or specator text chat can be displayed. The broadcasts 690 pane may display UI elements corresponding to one or more players in the current game that are broadcasting for the game that is broadcasting for the game or being replayed. In this example, player A's broadcast 692A is currently selected. In some embodiments, a viewer or specter can switch to a live or pre-recorded broadcast 692 of a different player by selecting an individual UI element within the broadcasts 690.

As shown in this example, in some embodiments, the specting UI 652 can include a broadcast content 640 pane where spectors can view information about different categories of game content. . For example, the broadcast content 640 pane includes tabs where spectors can view information about players, items, places, events, or other categories of game content described in game metadata. can do. For a category of content, spectors can select and view information about specific instances of the content, for example, specific players or game-related content or items. For a particular instance of content, spectors can acquire or watch additional details.

As shown in this example, a tab is displayed that displays information about selected broadcasted in-game items in broadcast content 640. The tab pane may include control or navigation UI elements, such as a scroll bar. In this example, the displayed list of items includes Disruptor Pistol (“DP9000”) and Laser Rifle (“LR20C”). In some embodiments, for at least some of the displayed items, a list of players who own or use individual items may be provided. In some embodiments, the spectator can select a player in the list to switch to the player's live or pre-recorded broadcast 692. Previously in another player's broadcast 692, viewers watched player-used items, viewed player-statistics, advised on item-use, or asked for player opinions or information about it, and gained player gear , Copy or clone, and so on. This example describes switching from the Items tab in the Broadcast Content 640 pane to the broadcasts of other players, but in some embodiments viewers broadcasts by selecting players from lists on other panes. Can switch. For example, the “places” pane and the “events” pane can provide lists of players at or related to various locations and events, and the viewer can switch to the broadcast of the selected player. You can select a player from the list.

In some embodiments, the player in the list for the item may not be a broadcaster. In this case, selecting a player from the list switches to another player's broadcast that may be associated with the first player, e.g., from the same approximate local location in the game being broadcast or replayed, or to the broadcast of another player to the same team. Can provide options for

As shown in FIG. 6B, UI elements may also be provided in the Broadcast Content 640 Items tab where information about individual items can be viewed or obtained. In some embodiments, the information can include statistical data for the item. For example, popularity or ratings may be provided based on player usage and/or participant voting, for other parts of the game gear or weapons. In some embodiments, the broadcast content 640 pane may include UI elements that a viewer can order, purchase, or otherwise obtain an individual item. For example, in the broadcast content 640 pane shown in FIG. 6B, the viewer may obtain a virtual DP9000 pistol for use in space explorer games and/or a game system provider, online merchant, manufacturer, or Individual “ GET IT ! ” to order or purchase physical models of DP9000 pistols from other entities . ”You can select UI elements.

In some embodiments, the specting system at least partially locates various game content in the game universe, including the location of players that are broadcasters to the game from game metadata received from various sources illustrated in FIG. 1C. Can detect them. In some embodiments, the world map 696 or a portion of the game world map can be displayed on the UI 652. In some embodiments, players, teams, areas, events, locations of regions, or locations can be marked on map 696 or highlighted or otherwise displayed visually. In some embodiments, the locations of players that are broadcasters for the game may be displayed visually, highlighted or otherwise, on the world map 696. For example, as illustrated in FIG. 6B, players A, B, G, and F are shown as broadcasters. In some embodiments, a viewer or spectator can switch to a live or pre-recorded broadcast 692 of a different player by selecting an individual broadcaster/player in map 696. In some embodiments, analysis of game metadata and/or broadcast metadata described in this application (eg, text chat 636 and/or audio chat or analysis of people noise) is active or exciting. (exciting) broadcasts can be identified, and a broadcaster/player's indicatior on map 696 can be highlighted. For example, in FIG. 6B, the broadcast of broadcaster/player A is a broadcast being viewed in video player 632 with the player's indicator circled on map 696. However, the broadcast of broadcaster/player E attracts a lot of attention from spectors, so the player's indicator on map 696 is not very highlighted. Viewers can select broadcaster/player E on map 696 to switch to that broadcast.

Figures 7a and 7b provide non-limiting examples of a specting user interface for a game specting system according to some embodiments. Specting UI 702 is, for example, a web page of a game specting system website through a web browser, as an interface to a game specting web application or mobile application, or other network-based game specting It can be provided as an interface to applications. The specting UI 702 is not limited, but the game metadata for the game in which the control 710, the video player 732 with A/V controls 733, and the spectator broadcast 734 It may include one or more panes or regions, including one or more of the broadcast content pane 740, which can view and interact with the broadcast content based at least in part on the. Controls 710 may include one or more UI elements that interact with the game specting system, in navigation or otherwise. Video player 732 displays a replay of a pre-recorded broadcast or a video stream (shown as broadcast 734) for a live broadcast or channel. In some embodiments, the specting UI 702 is a broadcaster and/or a specter text chat, for example a specter discussing game information and content, such as in-game gear displayed in the broadcast content pane 740. The chat may also include a chat 736 pane on which it can be displayed.

The broadcast content pane 740 includes, for example, a game information 744 pane that displays information about a game being broadcast based at least in part on game metadata received from an individual game system, and a viewer broadcast ( 734) Exploring, viewing and interacting with detailed information about game content (objects, gears, characters, players, locations, events, etc.) based at least in part on game metadata for the game being played. Can include game content details 746 pane.

As shown in FIG. 7A, in some embodiments, game content details 746 pane can be interacted by by a spectator to view various game content and to obtain more information about the game content. UI elements may be included. For example, as shown in FIG. 7A, the game content details pane 746 can be selected by a spectator to view a list of players; Includes a "Select a player" UI element that allows Spectators to select one of the players to view additional information about the player. For example, in FIG. 7A, the viewer views the game content details 746 pane (DP9000 Disruptor Pistol, LR20c Laser Rifle, Harpoon XL Ship, Helmet, Survival Pack, etc. I selected “player E” from the list to watch the current items on my player E's gear set. Note that players in the list may be players that are currently being broadcast or replayed, but this is not necessary.

In some embodiments, the spectator system 100 and/or broadcast content service 113 adds content to the content of the broadcast content pane 740 in response to detected events in the broadcast 734 or Or you can change the content. Events can be detected, for example, by one or more methods illustrated in Figures 3A-3D. For example, information about game content, game events, players, etc. may be added or changed to broadcast content pane 740 based at least in part on game metadata. For example, in FIG. 7A, information about a player or other game content is responsive to an in-broadcast event, for example, an event that includes player E, such as game content in response to the first appearance of player E in the current new game. Details 746 can be added to the pane or changed.

7A, in some embodiments, broadcast content may include overlays 738 on broadcast 734. In some embodiments, the spectator system 100 and/or broadcast content service 113 may add overlays 738 to the broadcast 734 in response to detected events in the broadcast 734. Can be. Events can be detected, for example, by one or more methods illustrated in Figures 3A-3D. The overlay window 738 can provide additional information about game content, game events, players, etc. based at least in part on game metadata obtained from the game system. For example, as shown in FIG. 7A, the overlay window 738A is added to the broadcast 734 in response to an in-game or event that currently includes the new player E, such as player E's first appearance. Became. The example overlay window 738A includes player attributes (name, team, level, skills, etc.), statistics (grade, skill, kills, experience, etc.) and gears (weapons, clothing, tools, Vehicles, etc.). The content of the overlay windows 738 is obtained from the specting system, game system, game developer, game servers, broadcaster devices, third parties such as online merchants, or any source illustrated generally in FIG. 1C. Can be. In addition to overlay windows 738 showing additional information about the information game content, game events, etc., the overlay windows 738 are images, video clips, advertisements, titles or labels, external web Links to sites, or generally any type of content. In some embodiments, the overlay window 738 can include active UI elements that the viewer can interact to display additional information about the selected game content in the broadcast content 740 pane. For example, in FIG. 7A, the viewer selects the “see gear” UI element in the overlay window 738A to watch the current items in player E's gear set in game content details 746 pane. Can be.

As shown in FIG. 7B, in some embodiments, broadcast 734 overlay window 738B provides additional information about the content based, for example, at least in part on game metadata obtained from the game system. It may include overlay content that allows viewers to interact with broadcast 734 to open. For example, as shown in FIG. 7B, the specting UI 702 is displayed on a touch-enabled device, and the spector uses touch gestures to select player E and attributes of the player Overlay window 738B showing field (name, team, level, skills, etc.), statistics (grade, skill, kills, experience, etc.) and gear (weapons, clothing, tools, vehicles, etc.) Open. In some embodiments, the overlay window 738B may include active UI elements that the viewer can interact to display additional information about the selected game content in the broadcast content 740 pane. For example, in FIG. 7B, the viewer is currently playing a game item details 746 in the Payne (DP9000 Disruptor Pistol, LR20c Laser Rifle, Harpoon XL Sheep, Helmet, Survival Pack, etc.) current item on the gear set of Player E The “View Gear” UI element in the overlay window 738B was selected to watch them.

In some embodiments, at least some of the UI elements displayed in the broadcast content 740 pane are added to the game or game content, for example based at least in part on game metadata obtained from the game system by the viewer. It may be interactive elements that allow to obtain information, or to obtain a game or game content in an order, purchase, or other way. For example, in some embodiments, a viewer may obtain a virtual item for in-game use of “space explorers” to obtain additional details about the items, and/or a virtual item from a merchant or manufacturer. It may interact with the displayed UI elements in the game content details 746 pane to order or purchase a physical model. As another example, a viewer may interact with UI elements displayed in the game information 744 pane to obtain more information about the game, or to obtain or purchase a game from a game, game system provider, or some other source. have.

8 provides non-limiting examples of a broadcaster user interface for a game specting system according to some embodiments. The broadcaster's device 800 may implement a game and broadcasting UI 802, and the A/V device 808 (eg, a microphone) may be used to collect broadcaster/player 820 audio and video inputs. Video camera) and speakers 804 (including spectacle audio and/or people noise) to output game audio. The broadcaster's device 800 may also include a keyboard 809 or other input device(s) through which the broadcaster/player 820 can write text input, such as a player chat or broadcast chat, or there Can be coupled to. In some embodiments, the broadcaster's device 800 may also include or combine with input devices and techniques such as controllers or joysticks, motion tracking systems, gesture-based input systems, and the like. Can be.

In some embodiments, the broadcasting UI 802 can include a game play window 810 that displays the current view of the game universe for the broadcaster/player 820. Note that the broadcaster' view of the game universe shown in window 810 can be viewed and included in broadcasts to speculators, for example, as shown in FIG. In some embodiments, the UI 802 can also include game controls 814 through which the broadcaster/player 820 can interact with the game system. In some embodiments, the UI 802 can include an in-game chat 814 through which the broadcaster/player 820 can communicate to other players in the game via text. In some embodiments, the UI 802 can also include broadcast controls 818 that the broadcaster/player 820 can interact with the specting system to control the broadcast. In some embodiments, the UI 802 can include a broadcaster/player 820 and a broadcast chat 818 through which spectors can communicate via text.

In some embodiments, the world map 812 or a portion of the map of the online game world may be displayed on the UI 802, for example, within the game play window 810 or as an overlaid window. The broadcaster/player A's team position is shown marked as "A" (oval). In some embodiments, players, teams, areas, areas, or locations corresponding to current or potential events identified by one or more methods described in this application are marked on map 812 or Or it can be highlighted or otherwise displayed visually. The broadcaster/player and his team can, in some cases, take action based on visual indications of events displayed on map 812.

As shown in Figures 1A and 1B, in some embodiments, the specting system is based, at least in part, on specator interactions with game content and/or broadcast content generated from broadcast metadata. Thus, broadcast feedback may be provided to the broadcast device 800. In some embodiments, at least a portion of the broadcast feedback may be provided to the broadcaster 820 through a window of the broadcast feedback 817 pane or broadcast UI 802.

9 provides other non-limiting examples of a specting user interface for a game specting system according to some embodiments. The Spectator' device 900 can implement the Spectating UI 902 and microphone 906 and game audio (Spectator audio and/or people noise, broadcaster live broadcast, to collect Spectator audio input) Speakers, etc.). Spectator's device 900 may also include or combine keyboard 909 or other input device(s) through which specter 960 can write text input, such as broadcast chat 918. Can be. In some embodiments, Spectator's device 900 may also include or combine with input devices and techniques such as controllers or joysticks, motion tracking systems, gesture-based input systems, and the like. Can be.

In some embodiments, UI 902 may include a game speculating window 910 that displays the current view of the game universe from the perspective of the broadcaster/player. In this example, spectator 960 is currently watching a group of players B, C, and D from the perspective of player A (broadcaster) in specting window 910. In some embodiments, UI 902 also includes specter controls 916 that specter 960 can interact with the specting system to control broadcasts, select other broadcasts, and the like. It can contain. In some embodiments, the UI 902 can include a broadcast chat 918 window through which the spectator 960 can communicate with broadcasters/players and other spectors via text.

In some embodiments, UI 902 may include a broadcaster/player, in this example a window 914 showing a live view of broadcaster/player A. The window 914 can be displayed, for example, within the game speculating window 910 or as an overlaid window. In some embodiments, a portion of the map of the world map 912 or the online game world may be displayed on the UI 902, for example, within the game speculating window 910 or as an overlaid window. The broadcaster/player A's team position is shown with an oval marked “A”.

In some embodiments, the UI 902 broadcasts content that broadcast content may be accessed by, or displayed to, the spectator 960 based at least in part on game metadata received from the individual game system. 940) It may include a pane or region. The broadcast content 940 pane may, for example, show information about games, game players, game objects or items, game events, etc. provided by the game system in game metadata. In some embodiments, UI 902 may replace or also include an overlay window 938 showing broadcast content based at least in part on game metadata received from the individual game system. The overlay window 938 may be displayed as a window therein, or overlay, for example, the game speculating window 910. In this example, the overlay window 938 shows details (gear, health, statistics, etc.) for the currently selected player B.

In some embodiments, players, teams, areas, areas, or locations corresponding to current or potential events identified by one or more methods described in this application are marked on the world map 912 It can be highlighted or otherwise displayed visually. For example, the oval marked “H!” may indicate the location of an event that will occur in the past, present, or future. In some embodiments, the spectator 960 displays the event displayed in the world map 912 to view or replay the event in the game specting window 910 or other window displayed on the UI 902. You can choose.

Game merchandising interface

In some embodiments, the specting system is a game on a specting user interface (UI) that speculators can view, select, and order, purchase, or otherwise obtain, game-related content. The game metadata provided by the game system(s) can be leveraged to provide a virtual storefront for related content. Game-related content is virtual or digital game-related items or objects (eg, digital representations of physical objects) that can be obtained for use in games such as in-game gears, clothing, weapons, Physical items or objects (eg, physical swords, action figures, toys, etc.), such as characters, avatars, powers, etc., physical representations of virtual objects from within games, and/or Or game-related physical goods such as t-shirts, or hats.

In some embodiments, a specating system provider can provide at least a portion of game-related content to requesting spectators. In some embodiments, the spectacle system's virtual storefront is not limited to providing the requested game-related content to speculators, but one or more entities including game systems or game system providers and online merchants. You can interface with people. In some embodiments, the specting system can provide or provide access to a “print on demand” service such that 3D printing technology can be used for game-related objects or items (eg, in-game Characters, weapons, vehicles, monsters, etc.) or can be used to print physical objects based on input designs. Designs or instructions for the objects can be obtained from game systems in game metadata, or otherwise, can be obtained.

In some embodiments, the virtual storefront can provide UI elements so that spectors can learn about in-game content, for example which characters/players use an item or object, and how they use it , You can watch historical information and/or statistical data about the history or success of items, and so on. The specting system can provide text and/or voice chat channels through which speculators and broadcasters can discuss game-related items or objects available through a virtual storefront. In some embodiments, the broadcaster may specify or select specific game-related items or objects provided through the virtual storefront UI on the broadcaster's channel.

FIG. 10 illustrates an example virtual storefront module in a game specting system 100 that provides game-related products to speculators through a specting interface according to some embodiments. The game specting system 100, for example, the game specting system 100 illustrated and described in Figures 1a and 1b, is provided to speculators through the specting UI 116 on the individual speculator devices 160. One or more components or modules 1010 capable of providing broadcast content 126 may be implemented. The broadcast content 126 may be determined at least in part from game metadata 124 received from the game system(s) 120 according to the game system API 114 provided by the specting system 100. In some embodiments, broadcast content 126 may be determined, at least in part, from game-related data obtained from one or more other sources, such as online merchants. Spectators can obtain game-related content through specting UI 116 by viewing, exploring, selecting and ordering, purchasing, or other ways, and according to specting UI 116, specter devices 160 ). Storefront module(s) 1010 can acquire and process Spectator interactions 164 with broadcast content 126 provided on Spectator devices 160 to select virtual and/or physical games- Create requests (1022) to order, purchase, or otherwise obtain a related product to product sources, such as game system 120 providers (requests (1022A)), game-related content 1091 ) To storage 1090 systems or services (requests 1022C), and/or virtual 1023 and/or physical 1076 items or objects (requests 1022B) such as online Virtual items 1023A, 1023B, or 1023C, which may be sent to merchants or other sources of 3D print-on-demand services 1070 and requested as virtual items 1023D to individual spectator devices 160 ), or delivery or provisioning of physical (1076) game-related products to individual specators. In some embodiments, virtual items 1023 are downloaded to game clients on individual spectator devices 160 or otherwise provided in game content (eg, game characters, gears, avatars, Game states, etc.).

In some embodiments, the broadcaster selects or designates specific game-related items or objects to be supplied by the storefront module(s) 1010 via broadcast content 126 on individual broadcast 142 channels. Can (1003). The storefront module(s) 1010 can acquire and process Spectator interactions 164 with broadcaster-specific content 126 provided on Spectator devices 160 to select the selected game-related product. Requests 1022 for ordering, purchasing or otherwise obtained may be generated and sent to individual product sources 120, 1090, and/or 1070. In some embodiments, speculating system 100 broadcasts feedback 103 to broadcast device(s) 140 based at least in part on specator interactions 164 with broadcast content 126. ) Can also be provided. In some embodiments, broadcast feedback 103 is broadcast UI/API 112 provided to broadcast devices 140 by specting system 100, for example, as illustrated in FIG. 9. It can be provided to broadcasters through.

11 is a flow chart of a method for providing a game-related product through a game speculating system according to some embodiments. The method of FIG. 11 can be implemented, for example, by the specting system 100 illustrated in FIGS. 1A, 1B, or 10. As indicated at 1100 in FIG. 11, the spectating system can stream broadcasts of game play to spectacle devices. Broadcasts may include videos showing the gameplay of individual broadcasters participating as players in a game running on the game system.

As indicated at 1110 in FIG. 11, the spectating system is a game on spectacle devices that spectators can view, select, and order, purchase, or otherwise obtain, game-related content. It can provide a game merchandising interface. 12 provides a non-limiting example of a game sales interface or a virtual storefront for a game specting system. In some embodiments, the broadcaster may select or specify specific game-related content to be provided through the game sales interface for the broadcaster's channel.

As shown in (1120) of FIG. 11, the specting system may provide game-related content or broadcast content corresponding to a product through a game sales interface. Game-related content is virtual or digital game-related items or objects that can be obtained for use in games (eg in-game gear, clothing, weapons, characters, avatars, powers, etc., Physical items or objects, such as physical representations of virtual objects from within games (eg, physical representations of in-game weapons such as swords, game-related action figures, toys, etc.), and/or Other game-related physical products, such as posters, books, t-shirts, or hats, etc. Broadcast content is a game received from a game system according to the game system API provided by the specting system. It may be based at least in part on metadata In some embodiments, game metadata may include data that describes or represents at least a portion of game-related content that can be used when generating broadcast content. In some embodiments, the specting system may obtain and use descriptive data for game-related content from one or more other sources, such as online merchants.

Broadcast content provided through the game sales interface may include one or more UI elements (eg, buttons, dialogs, lists, tabs, menus, images, video clips, links) provided on the game sales interface. , Text, panes, etc.). In some embodiments, broadcast content may also include one or more overlays on the broadcast video. In some embodiments, the broadcast content may include UI elements through which the viewer can order, purchase, or otherwise obtain game-related content through the game sales interface. In some embodiments, the broadcast content may or may include descriptive information for game-related content, eg, descriptions, images, and/or video clips of game-related content. Access can be provided. In some embodiments, broadcast content may include historical information or statistics about game-related content, such as which characters/players use an item or object, how they use it, the item's history or success, etc. It may contain statistical data on or provide access to it. In some embodiments, the spectating system can provide text and/or voice chat channels through which the spectators and broadcasters can discuss game-related content provided through the game sales interface.

As shown in 1130 of FIG. 11, the specting system may receive input from a specator device that requests or purchases a selected game-related product through the game sales interface of the specting system. As indicated by 1140 in FIG. 11, the specting system may enable provisioning or delivery of game-related products requested to individual spectors. In some embodiments, the broadcast content may include UI elements through which the viewer can order, purchase, or otherwise obtain game-related content through a game sales interface and interact with viewers/spectators. . The spectating system can acquire and process spectacle interactions with broadcast content provided on spectacle devices through a game sales interface, allowing for various virtual game-related product and/or physical game-related product sources. Requests for selected game-related content can be generated and sent, and delivery or provisioning of requested virtual or physical game-related products to individual specators can be enabled. In some embodiments, a specating system provider can provide at least a portion of game-related content to requesting spectators. In some embodiments, the specating system is not limited to providing speculators with at least a portion of the requested game-related content, but one or more entities including game systems or game system providers and online merchants. And interface. In some embodiments, the specting system can provide or provide access to a “print on demand” service such that 3D printing technology can be used for game-related objects or items (eg, in-game Characters, weapons, vehicles, monsters, etc.) or can be used to print physical objects based on input designs. Designs or instructions for the objects can be obtained from game systems in game metadata, or otherwise, can be obtained.

In some embodiments, the purchase of a game-related product through the game sales interface of the specting system may be reflected in the specting UI so that other spectors know what was purchased and who purchased it. In some embodiments, purchases may be reported back to the broadcaster(s) through the broadcaster client interface as broadcaster feedback. The broadcaster can thus see what is being purchased during the broadcaster. The broadcaster can, for example, give away a virtual and/or physical product as a reward based on how many products have been sold through the broadcaster's channel. Similarly, purchases may be reported back to game systems, game developers, or third parties such as online merchants via individual feedback channels. Element 1237 of FIG. 12 is an example “sales info” pane that can display history or statistics for a broadcaster's sales, for example, during individual broadcasts or through individual channels ( 1237).

12 provides a non-limiting example of a game sales interface or a virtual storefront for a game specting system according to some embodiments. Specting UI 1202 is, for example, a web page of a game specting system website through a web browser, as an interface to a game specting web application or mobile application, or other network-based game specting. It can be provided as an interface to applications. Specting UI 1202 is not limited, but order 1212, video player 1232 with A/V controls 1233, game-related content or product, order, purchase or otherwise obtain A game sales interface capable of viewing and interacting with broadcast content based at least in part on game metadata for the game to which the spectator is broadcast (1234) to play and to obtain information and statistics about the game-related content. (1240), may include one or more panes or regions including one or more of. Controls 1210 may include one or more UI elements that interact with the game specting system, in navigation or otherwise. Video player 1232 displays a replay of a pre-recorded broadcast or a video stream (shown as broadcast 1234) for a live broadcast or channel. In some embodiments, the specting UI 1202 is a broadcaster and/or spectacle text chat, for example game information and games- such as game-related content displayed as broadcast content in the game sales interface 1240. Chats discussing relevant content may also include a chat 1236 pane that can be displayed.

Game sales interface 1240 provides information about the game's content and the game being broadcast based at least in part on game metadata received, for example, from an individual game system and is broadcast (1234) Capable of exploring, viewing and interacting with detailed information about game content (objects, gears, characters, players, locations, events, etc.) based at least in part on game metadata for the game being played It may include broadcast content. At least some of the broadcast content displayed on the game sales interface 1240 allows the viewer to obtain additional information about the game or game content, for example based at least in part on game metadata obtained from the game system, And it may be interactive UI elements that allow you to purchase a game or game content in an order, purchase, or other way. For example, in some embodiments, the viewer orders, purchases, or purchases virtual items (in this example, the DP9000 Disruptor pistol_ or Harpoon XL ship) for in-game use. To obtain or otherwise purchase a physical model of a virtual item (a model of the DP9000 Disruptor Pistol or Harpoon XL Ship in this example) from a merchant or manufacturer, and/or a game-related product such as t- To interact with UI elements displayed on the game sales interface 1240 to obtain information about the game-related content or product and/or statistics about it to obtain shirts or hats in order, purchase or otherwise. As another example, the viewer may obtain the game to obtain more information or statistics about the game (in this example, “space explorers”), or from a game, game system provider, or some other source. Alternatively, the user may interact with UI elements displayed on the game sales interface 1240 to purchase.

In some embodiments, the game sales interface 1240 may include UI elements through which speculators can obtain more information from a broadcaster or other expert. For example, as shown in FIG. 12, an information box about the DP9000 di'm emitter Pistol (Disrupter Pistol) will ask for "professionals who can choose Spectator sends messages to the broadcaster for more info on this item (Ask the Expert)” UI element. Selecting the “Ask the Expert” UI element can trigger a message to be displayed on the broadcaster's device requesting more information about a particular item. The broadcaster can then respond to an audio or text live broadcast to describe the item, or provide information via email or a link to pages including other sources, such as descriptive information.

As shown in this example, the viewer has a specific game were to interact with the display in the broadcast content game sales interface 1240 to select the emitter pistol am DP9000 D to watch the descriptive information for the associated item. The description information can include, for example, image(s) of the item and text description. For example, for a weapon, the descriptive information can indicate the range, dose, and efficacy of the weapon. In some embodiments, the descriptive information may include usage information for a specific item or type of item. For example, a list of all players using an item such as a particular sword or other weapon may be provided. In some embodiments, the descriptive information can be viewed statistical data about an in-game item, such as statistics about which characters/players are using the item, how they use it, the history or success of the item, etc. Can. In some embodiments, popularity or ratings may be provided based on player usage and/or participant votes for other parts or weapons of the in-game gear. In this example, the viewer is to obtain a virtual DP9000 pistol for use in space explorers games and/or to order or purchase a physical model of the DP9000 pistol from a game system provider, online merchant, manufacturer, or other entity. “ GET IT ! ”You can select UI elements.

In some embodiments, broadcast 1234 may include overlay content that allows viewers to interact with broadcast 1234, for example, as illustrated in FIG. 7B. For example, in some embodiments, the viewer broadcasts to open an overlay window that provides additional information about the content based at least in part on game metadata obtained from the game system as illustrated in FIG. 7B ( 1234) My content can be selected. As another example, in some embodiments, a viewer may select game content in broadcast 1234 to display broadcast content related to the selected game content in game sales interface 1240. For example, the spectator can select a particular in-game character to display broadcast content for the gear of the selected character in the game sales interface 1240. FIG. 7B provides an example in which the viewer has selected player E in the overlay window to view the current items in the gear set of player E in the game content details pane.

Game participation interface

Specting system that can interact with game systems to allow viewers or spectors to join or "step into" games broadcast through the specting system in a game specting environment. Embodiments of the following are described: In some embodiments, the specting system also enables provisioning and acquisition of game states or game records for pre-played game sessions that allows spectors to replay the session. The Spectating User Interface (UI) allows Spectators to participate in trial or full versions of the game, as well as game records for game sessions played previously and game states for currently broadcasted games. It can display broadcast content including UI elements that can obtain game client software for playing game client software, game states, and/or game records in response to specator requests through the specting UI. Can be downloaded to the Spectator's devices Spectators can obtain characters, avatars, gear, and/or other game content for use in games through the Specting UI Game client software And using a specting system that enables the acquisition of game states, spectors can join live game sessions of online games, start new game sessions, or replay pre-recorded game sessions. Spectators can acquire in-game characters through all specting system interfaces, "load out" or equip characters, obtain an executable version of the game, and play the game. It can acquire and "step in" the states, and can be clones or characters of characters in step in or game sessions.

In some embodiments, the specting system may leverage game metadata to allow spectors to join or "step in" to games broadcast through the specting system. In, the broadcast content provided to the speculators on the specting UI is a user who can obtain, or otherwise obtain, demos, trials, or full versions of the games. It may include interface elements In some embodiments, game client software and game data are used to participate in demos, trials, or full versions of online games, speculating system interfaces and broadcast streams. It can be downloaded to and obtained from the Spectator's devices In some embodiments, the broadcast content provided to the Spectators on the Spectating UI includes characters, avatars, etc. for Spectators to specifically participate in games. May include UI elements that may be ordered, purchased, or otherwise, or otherwise, obtainable UI elements, in some embodiments, the acquired game content may include speculating system interfaces and broadcasts Specters' devices may be downloaded via streams.In some embodiments, using a Specting UI to obtain game client software, game data, and game content via broadcast streams, the Spectator They can join live game sessions of online games, start new game sessions, and/or replay pre-recorded game sessions.

In some embodiments, spectors may use the specting UI to obtain game client software, game data, and game content (eg, game characters and gear) via broadcast streams, and also transfer Game records of game sessions can be acquired, “step into”, and replayed. In some embodiments, game records and/or game states may be purchased or otherwise obtained through specting system interfaces and broadcast streams. In some embodiments, broadcast content provided to speculators on the specting UI may include user interface elements through which one or more game records and/or game states are advertised and obtained by the speculator. It can be used to regenerate a game session universe and start or restart gameplay at a point in the game session timeline. In some embodiments, the spectator can step in into the game session universe and timeline by using the player and step into their own in-game character or avatar or taking control of a character already in the game session and stepping in. You can be a player. In some embodiments, broadcast content provided to specators on the specting UI is not limited to speculators, but not specifically to other players, including broadcasters participating in games, characters, It may include user interface elements that can view, order, purchase, or otherwise obtain game content including avatars and gears. Thus, in some embodiments, a spectator can acquire an in-game character and “load out” or equip a character through all spectating system interfaces and broadcast streams, and establish an executable version of the game. Can acquire, acquire and "step in" game records or game states, and can be clones or characters of characters in step in or game sessions.

In at least some embodiments, indications of player inputs to the game for at least some players in the game may be received from game systems according to the game system API provided to the game systems by the speculating system. The player input can be a single command or action input to the game from an individual player's game client or game controller. The player input or a combination of player inputs can trigger a game event, can be included in a game event, or can be associated with a game event. In some embodiments, player inputs to the game are, for example, but not limited to forming a record of a particular game session (referred to as a game record) that can be bent to clients that include specators. It can be stored as part of a game record along with one or more game states and other game information. The game record containing player inputs can be replayed, and in some embodiments, the viewer of the replay can “step into” the replay as described later in this specification.

In some embodiments, the “ghosting” mode may be supported when joining game sessions from acquired game states or game records. In ghosting mode, the player can play a broadcaster/player's pre-recorded game session through the specting system interface or jump into a broadcasted game. The original player's character/gear (eg, racecar) may still be visible as a “ghost” to the new player. Thus, new players can compare their performance to that of the original player by watching the “ghost” of the original player during replay. In addition, the original player's broadcast live broadcast (video, audio, and/or text) can be played or displayed to the new player. As an example, a new player can use a ghosting mode as a training tool to learn how an experienced or skillful broadcaster/player has played a difficult level or challenge in the game.

13A-13E illustrate provisioning game client software and game states on a spectator device, for example in the game specting environment illustrated in FIG. 1A or 1B in a game specting environment according to some embodiments. For example. As shown in FIG. 13A, the game specting environment may include a specting system 100, a game system 120, a broadcaster device 140, and specator devices 160.

Typically, the game system 120 renders a 2D or 3D representation of the game universe based on the current state of the universe, generates video and sound, and is not limited to display, but the broadcaster device(s) 140 ) May include a game engine 1322 that sends or streams video and sound (A/V) output 121 to client devices including. The game supported by game engine 1322 is a multiplayer online game, a single-player online game in which two or more players participate in online game sessions remotely, or a single-player that can be played locally or offline. It can be a player or multiplayer game.

Broadcaster device 140 may include input and output components (limited to one) for at least one game system 120 in which individual players may participate in game sessions currently being executed by game system(s) 120. But may include input devices and technologies such as controllers or joysticks, motion tracking systems, gesture-based input systems, etc.) and game client 141A software and/or hardware, but is not limited thereto. Does not work. Broadcaster device 140 includes input and output components (eg, video cameras and microphones) and live A/V streams (broadcasts 142) of individual players and their individual gameplay and is limited. Broadcasting client software for the specting system 100 and, although not exclusively, can generate other broadcaster input, including audio and text live broadcasts for broadcasting to speculators through the specting system 100 and And/or hardware 143.

Specting system 100, such as the gaming specting system 100 illustrated and described in Figures 1a and 1b, broadcasts to speculators via the specting UI on individual specator devices 160 ( 142) and may implement one or more components or modules capable of providing broadcast content 126. 14 provides a non-limiting example of a specting UI according to some embodiments. Broadcast content 126 may be determined at least in part from game metadata 124 received from game system(s) 120 according to the game system API provided by specting system 100. In some embodiments, broadcast content 126 may be determined, at least in part, from game-related data obtained from one or more other sources, such as online merchants or data stores of game-related data. Can be.

Spectator device 160 may include input and output components (including but not limited to input devices and technologies such as controllers or joysticks, motion tracking systems, gesture-based input systems, etc.). Although not limited thereto, the specting system () allows individual spectors to select, receive and watch the playbacks of broadcasts 142 or pre-recorded broadcasts from broadcaster devices 140. 100), and the specters are not limited, but are provided on the specter device 160 through the specting UI, at least in part, and provided by the specting system 100 to the game system(s) 120 ) With broadcast content 126 including content generated from game metadata 124 received from Spectator interactions 164 and audio or text chat for, but not limited to, broadcasts 142 Or it may include speculating client software and/or hardware that can provide spectrometer inputs 165 that include “people noise”. FIG. 14 provides a non-limiting example of a specting UI that can be provided on the specter device 160 by the specting system 100 in accordance with some embodiments. In some embodiments, specator inputs and interactions also include inputs and interactions from input devices and techniques such as controllers or joysticks, motion tracking systems, gesture-based input systems, etc. can do.

In some embodiments, the specting system 100 may request requests 105 for the game system 140, for example requests for specific game metadata 124 or game client software, game states, And specator inputs 165 and/or interactions 164 to process requests to generate game content. As shown in FIG. 14, the Spectating UI provides broadcast content including Spectator UI elements that can interact to generate various requests for game client software, game states, and game content. It may include a game participation interface.

The drawings 13b and 13c illustrate providing access to the game through a streaming system 1300 and a game streaming interface 1341. In some embodiments, full game play may be provided to spector device 160 via streaming service or system 1300 and game streaming interface 1341, as illustrated in FIG. 13B. In some embodiments, demo or trial access to the game may be provided through streaming system 1300 and game streaming interface 1341. In FIG. 13B, the Spectator viewing broadcast 142 through the Spectator device 160 is, for example, FIG. 14 to generate a request 1364 to participate in a trial version of a game running on the game system 120. Interact with the game participation interface of the Spectating UI illustrated in. The trial version of the game may be provided through the streaming system 1300 and the game streaming interface 1341 for a specified period of time, and may be provided for a fee or for free. In response to the request 1344, a trial streaming version of the game can be initiated on the game streaming interface 1341 (eg, a web page) on the specter device 160 via the streaming system 1300. Game stream I/O 1342 from spectator device 160 to game system 120 may include, but is not limited to, player inputs for the game. Game Stream I/O 1342 to Spectator Device 160 may include a streamed video of at least partially rendered game graphics provided on Game Streaming Interface 1341, but there It is not limited. In addition, game software, game data, game records, game states, and/or game content may be included in game stream I/O 1342 to spectator device 160.

13C illustrates downloading a native game client to specter device 160 along with game stream I/O 1342 according to some embodiments. In some embodiments, the “background” download 1350 of the native game client 141B software for the spectator device 160 is initiated to the spectator device 160 in response to the game trial request 1344. Can be, or alternatively, initiated in response to additional or other spectacle interactions with the game streaming interface 1341. In some embodiments, native game client 141B software can be downloaded in stream 1342 from game system 120. In some embodiments, native game client 141B software may instead be downloaded in a broadcast 142 stream from specting system 100. The download 1350 of the game client 141B software may typically take a significant amount of time (eg, 15-20 minutes or longer), such as during a game trial period or in response to a game trial request 1364 Initiating the download 1350 is when the spectator decides to purchase the full version of the game through the game participation interface of the specting UI, for example, as illustrated in FIG. 14 and if so determines the native game client 141B ) To allow seamless switch from the trial version provided by the game streaming interface 1341. Note that the downloaded game client 141B software may not be activated until the spectator purchases the full version of the game.

13D illustrates switching from a game client streaming interface to a native game client 141B on a spectator device 160 in accordance with some embodiments. At some point during or after the trial period, the spectator can generate a request 1366 to purchase a full version of the game running on the game system 120, for example, of the specting UI illustrated in FIG. You can interact with the game participation interface. In response, game client 141B downloaded with stream 1342 during the trial period may be activated. In some embodiments, the current game state for the game 1324 is a game client from the game streaming interface 1341 on the spectator device 160 or some other source including but not limited to the game system 140. It can be obtained by (141B). Accordingly, the spectator can continue to play seamlessly by participating in games that were played through the streaming system 1300 and the game streaming interface 1341. In some embodiments, the game state 1324 can be provided to a broadcast 142 stream from the specting system 100.

The game supported by the game client 141B may be a multiplayer online game, single-player online game, in which two or more players participate in online game sessions remotely, or single-player or multiplayer game played locally/offline. Can be For online games, game I/O 1344A may include at least player inputs to a game running on game system 140, as well as graphics data or rendered graphics, for display on a spectator device. , Game software, game data, game records, game states, and/or acquired by a spectator/player from, but not limited to, through the specting system 100 or from other sources including the game system 140. Or it may also include game content. For offline games, there is no game I/O 1344A to the remote game system 160 or game I/O 1344A is through the specting system 100 or is not limited to the game system 140 ) May also include game software, game data, game records, game states, and/or game content obtained by a spectator/player from another source.

13E illustrates step-in-to-game and game state acquisition from game client 141B on specator device 160 in accordance with some embodiments. Spectator, for example, to generate a request 1368 for purchasing or otherwise obtaining a game record or game state for a game running on game system 120, of the Specting UI illustrated in FIG. 14 In response, the requested game state or game record 1325 (and possibly other game metadata) may be obtained from the game system 140 or from some other source, such as the specting system 100, It can be provisioned from a third-party merchant, or data storage of a third-party storage system, to the spectator device 160. In some embodiments, a game state or record 1325 can be provided to a broadcast 142 stream from a specting system.

In some embodiments, for online games, the Spectator/Player joins the current game running on the Specting System 120 as a new character, or “Step Into” with the control of an earlier character in the game. In order to use the game client 141B and game status or record 1325. In some embodiments, a spectator/player may use game client 141B and game state or record 1325 to replay a portion of a pre-recorded game or game. In at least some embodiments, the game record is not a mere video recording of gameplay, but instead is limited to allowing pre-recorded game sessions to be replayed or replayed by game client 141B or engine 1322. It's not, but it's executable code for gameplay that can contain data and information that originally contains player inputs. In some embodiments, the spectator/player may "step in" with control of the character in the game replay or "jump into" the replay as a new character.

14 provides non-limiting examples of a game participation interface for a game specting system according to some embodiments. Specting UI 1402 is, for example, a web page of a game specting system website via a web browser, as an interface to a game specting web application or mobile application, or other network-based game specting It can be provided as an interface to applications. The speculating UI 1402 is not limited to one or more including one or more of the controls 1410, a video player 1432 with A/V controls 1432, and a game participation interface 1440. It may include panes or regions. The controls 1410 may include one or more UI elements that interact with the game specting system, in navigation or otherwise. Video player 1432 can display a replay of a pre-recorded broadcast or a live broadcast or video stream for a channel (shown as broadcast 1434).

Although not shown, in some embodiments, the specting UI 1402 is broadcaster and/or specator text chat, for example game information and game-related content displayed as broadcast content in the game participation interface 1440. For example, it may also include a chat pane in which chats discussing game software, game states, game records, and/or game content can be displayed. In addition, in some embodiments, the game participation interface 1440 includes UI elements, such as “Ask the expert,” where spectors can obtain more information about a game or game content from a broadcaster or other expert. expert)” UI elements. Selecting the “Ask the Expert” UI element can trigger a message to be displayed on the broadcaster's device requesting more information about the game or specific game content. The broadcaster can then respond to the audio or text live broadcast or provide information through other sources.

Spectating UI 1402 may include game software, game states, games that may allow a spectator to join or "step in" to the current game or participate in a game to replay pre-recorded games, for example. A game in which speculators are broadcast (1434) to order, purchase, or otherwise obtain access to records, and/or game content, and to obtain information and statistics about game and game-related content. It may include a game participation interface 1440 for viewing and interacting with broadcast content based at least in part on game metadata for. At least some of the broadcast content displayed on the game participation interface 1440 allows the viewer to obtain additional information about the game or game content, for example based at least in part on game metadata obtained from the game system, And it may be interactive UI elements that allow you to order, purchase or otherwise obtain a game, game states, game records or game content.

In the non-limiting example shown in FIG. 14, the game participation interface 1440 shows broadcast content for the example “Space Explorers” (SE) game. Note that similar interfaces 1440 can be provided for other games at least partially according to individual game metadata for the games. Viewers can interact with UI elements displayed on the game participation interface 1440 to obtain information about SE games and game-related content, software, and data and/or descriptive information about statistical data. In addition, the viewer can select the “Demo SE game” UI element to obtain or access a demo or trial version of the SE game as described, for example, with reference to drawings 13a-13e.

In some embodiments, the viewer uses the “Purchase SE game” UI element to purchase, download or activate the full version of the SE game client as described, for example, with reference to drawings 13a-13e. You can choose. In some embodiments, the viewer joins the current games and replays pre-recorded games through the demo or trial version or full version of the game client, as described, for example, with reference to figures 13a-13e. Use the “Purchase SE game state” UI element to purchase or otherwise obtain game states and/or game records that may allow you to step in on games or game characters, etc. You can choose. In some embodiments, the viewer is not limited to using the “Get SE game content” UI element to purchase or otherwise obtain game content including gear, avatars, maps, and the like. You can choose. For example, in some embodiments, selecting the “obtain SE game content” UI element may take the viewer to the game sales interface 1240 as illustrated in FIG. 12. In some embodiments, the viewer can select the “Clone SE character” UI element to purchase or otherwise obtain a clone of a particular game character (in this example, the character of player F). have. Acquiring a clone may provision the viewer's game client or game account to, for example, the player F's character/avatar, and also provide the viewer's game client or game account with at least a portion of gear belonging to player F, or You can "load out".

In some embodiments, the viewer can select the “Step into SE game” UI element to step in to the broadcast (1434) game session. The game session that is broadcast 1434 can be a live game session running on a game system, or can be, for example, a replay of a session that is being replayed from a game record, or a replay of a preplayed session. Step inito into a game session can launch a local game client on the spectator device to launch the game from an individual game state or game record, or alternatively the game is for example in drawings 13a-13e It may be step-in and played using a streaming client as illustrated in.

15A is a flow chart of a method for enabling game acquisition and participation through a game specting system according to some embodiments. The method of FIG. 15A can be implemented, for example, by the spectating system 100 illustrated in FIGS. 1A, 1B or 13A-13E. As indicated at 1500 in FIG. 15A, the spectating system can stream broadcasts of game play to spectator devices. As indicated at 1502 in FIG. 15A, the specting system may provide a game participation interface on spectater devices. 14 shows an example game participation interface. As indicated by (1504) of FIG. 15A, the specting system may, for example, game software and/or through a game participation interface based at least in part on game metadata received from the game as described with reference to FIG. Provide broadcast content that provides access to game data. As shown in (1506) of FIG. 15A, the specting system is a specter accessing game software and/or game data through a game participation interface, as described, for example, with reference to FIGS. 13A-13E and FIG. It can receive input from the device. As indicated by (1508) of FIG. 15A, the specting system may enable provisioning of game software and/or game data requested to the spectator device, for example as described with reference to FIGS. 13A-13E. have. As indicated by 1510 in FIG. 15A, the spectator may begin to participate as a player in the game, as described, for example, with reference to figures 13A-13E.

15B is a flow chart of a method for step-in into a game through a game specting system according to some embodiments. The method of FIG. 15B can be implemented, for example, by the spectating system 100 illustrated in FIGS. 1A, 1B or 13A-13E. As indicated by (1520) of FIG. 15B, the spectate system wants the spectator to join or "step in" into the currently running game or a pre-recorded game, as described with reference to FIG. 14, for example. It can receive input from a spectator device indicating that it is. As indicated by 1522 in Figure 15B, in response to the input, the specting system enables provisioning of game software and/or game data to the spectator device, for example as described with reference to Figures 13A-13E. You can do it. Note that the spectator device may already include game client software, and in some cases game data (eg, one or more game states) may be downloaded to the game client or otherwise provisioned. As shown in (1524) of FIG. 15B, the specting system may enable provisioning of game content to a spectator device or account, for example in response to input to the game participation interface described with reference to FIGS. have. As indicated by 1526 in FIG. 15B, the spectator may begin to participate as a player in the game, as described, for example, with reference to figures 13A-13E.

15C is a flow chart of a method for provisioning and cloning game characters in accordance with some embodiments. The method of FIG. 15C can be implemented, for example, by the spectating system 100 illustrated in FIGS. 1A, 1B or 13A-13E. As indicated by (1540) of FIG. 15C, the specting system may receive input from a spector device for acquiring or cloning a game character, for example, input to a game participation interface described with reference to FIGS. . As indicated at 1542 in FIG. 15C, the spectating system may enable provisioning of game characters to a spectator device or account, as described, for example, with reference to FIG. 14. As indicated by (1544) of FIG. 15C, the specting system may receive input from a spector device that acquires game gear for a character, as described with reference to FIG. 14 or FIG. 12, for example. As indicated by (1546) of FIG. 15C, the spectating system may enable provisioning of game gear to a character of the spectator, as described with reference to FIG. 14 or FIG. 12, for example.

15D is a flow chart of a method for provisioning game client software to a spectator device in a game specting environment according to some embodiments. The method of FIG. 15C can be implemented, for example, by the spectating system 100 illustrated in FIGS. 1A, 1B or 13A-13E. As shown in (1560) of FIG. 15B, the specting system may receive input from a spector device indicating that the spector wants to try or demo a game, for example, as illustrated in FIG. 13B. have. As indicated at 1562 in FIG. 15D, in response to the request, the specting system may initiate a game client trial stream to the specator's device for the spector, as illustrated, for example, in FIG. 13B. As indicated by 1564 in FIG. 15D, the specting system can download a native game client for the specator device to the stream, as illustrated in FIGS. 13C and 13D, for example. As shown in (1566) of FIG. 15D, the specting system receives input from a spector device indicating that the spector wants to purchase or activate the game, as illustrated in FIG. 13D, for example. can do. As shown in 1568 of FIG. 15D, the native game client may be activated on the specator device in response to the purchase of the specter of the game. As indicated in 1570 of FIG. 15D, the spectator may resume or continue the game to the native game client on the spectator device, as illustrated, for example, in FIGS. 13D and 13E.

15E is a flow chart of a method for obtaining game data on a spectator device according to some embodiments. The method of FIG. 15E can be implemented, for example, by the spectating system 100 illustrated in FIGS. 1A, 1B or 13A-13E. As indicated at 1580 in FIG. 15E, the game client may be provided or provisioned to a spectator device, for example, as illustrated in FIGS. 13A-13E. As indicated at 1582 in FIG. 15E, the spectating system may receive input from a spector device that acquires game data, for example, as illustrated in FIGS. 12 or 14. The game data may include game sessions that allow the spectator to replay various game content, and/or game sessions that can be used in the game, and game state(s) allowing the spectator to join game records. However, there is no limitation. As indicated by 1584 in FIG. 15E, the spectating system may provision selected game data to the spectater device, as illustrated, for example, in FIGS. 13A-13E, 12, or 14. As indicated by (1586) of FIG. 15E, the spectator may initiate or step in a game on a game client according to game data, for example, as illustrated in FIGS. 13D-13E.

Participant achievements and rewards

In some embodiments, the specting system is a game for rewarding or otherwise acknowledging rewarding system participants (broadcasters/players, specators, and/or commentators) It may leverage metadata and/or broadcast metadata. In some embodiments, specators may be rewarded for participating in broadcasts or events in games that are specifically broadcast. In some embodiments, the specting system can analyze game metadata and/or broadcast metadata to detect big or important events or highlights in broadcast streams, watch big events, or " You can compensate at least some specators for "being there". In some embodiments, specators may be rewarded for interacting with broadcasters, for example actively participating in broadcast audio or text chat channels.

Examples of Spectator Rewards include acknowledgments or "badging" on a game specting system interface, virtual or digital items such as virtual gears in a game, specting system or game content. May include, but is not limited to, discounts or free access, physical items such as t-shirts or hats, and points that can be used and collected to win or purchase items. Does not work.

In some embodiments, the specting system allows broadcasters to reward or promote specific speculators, for example, by selecting a spector that shows good knowledge of the game in order to become a narrator for the game. Can be. In some embodiments, broadcasters/players perform certain achievements (achievements), such as in-game achievements such as a certain feat in front of people of any size, or audience participation or support at any level (audience size) , Enthusiasm, voting, etc.) can be rewarded for performance. As non-limiting examples, broadcasters/players may receive in-game health or strength boost or are based on audience size or audience enthusiasm growth expressed through audio and/or text specator chat input. You can be rewarded with in-game powers, gears, weapons, or information. As another example, broadcasters may obtain special or exclusive broadcast content added to their broadcast channel display based on their achievements. As another example, broadcasters may receive a monetary reward or other reward for bringing new followers or subscribers to the specting system through their broadcast channel.

16 illustrates a participant rewards module in a game specting environment according to some embodiments. Game specting system 100, such as game specting system 100 illustrated and described in Figures 1a and 1b, may include one or more components capable of obtaining achievement inputs from one or more sources, or Modules 1610 may be implemented or may have access to it. Module 1610 can process the inputs to determine the participants or groups of participants to be rewarded, and can also process the inputs to determine events and/or achievements as to what rewards will be awarded. Module 1610 can also determine what rewards are to be provided to the determined participants or groups of participants, and can generate reward outputs that are provided to one or more destinations. FIG. 16 shows the participant reward module 1610 as a component of the specting system 100, but in some embodiments the participant reward module 1610 is a game system 120 as illustrated in FIGS. 1A and 1B. It can be implemented as a module or as an external service.

Participant reward module inputs

In some embodiments, performance inputs to participant reward module 1610 may include, but are not limited to, one or more of the following. Various performance inputs, either alone or to determine rewarded participants or groups of participants, which rewards will be awarded, and/or events and/or achievements for rewards provided to participants or groups of participants It can be considered in combination.

Game metadata ( 1624) . In some embodiments, specting system 100 obtains game metadata 1624 from game systems where broadcasts are being streamed, or from one or more other sources, such as illustrated in FIG. 1C, for example. can do. In some embodiments, game metadata for the game 1624 can include, but are not limited to, indications and descriptions of individual in-game events. Figures 1A, 1B, 3A, and 3B show examples of game metadata 1624 reception and processing including game event data according to some embodiments. In some embodiments, game metadata 1624 is a game and other information about the game players, such as the identities of players in the game, player achievements, player statistics and history, players inputs for the game , Etc. can also include. Game metadata 1624 can be obtained by, or provided to, participant reward module 1610 and used to determine events or achievements to be rewarded, rewards, and reward recipients.

Broadcast metadata ( 1630) . In some embodiments, the specting system 100 is a participant in a game specting environment to determine broadcasts and/or other information about games running on game systems or to detect events therein. It can acquire and analyze various inputs from (players, broadcasters, commentators, and/or specators). Events and other information determined from participant input analysis may be collectively referred to as broadcast metadata 1630. 3A, 3C, 3D, and 4 illustrate broadcast metadata 1630 including broadcast events 494 illustrated in FIG. 3D and other broadcast-related analysis information 427 illustrated in FIG. 4. It shows examples of obtaining and analyzing various inputs from participants to generate. The broadcast metadata 1630 can be obtained or provided by the participant reward module 1610 and used to determine the events or achievements to be rewarded, rewards, and reward recipients.

Time and locations ( 1635) . In some embodiments, temporal information about the participants (eg, time of day, day or date, time zone, etc.) and/or geographic location information (eg, city, state ), region, country) can be obtained by the participant reward module 1610 and can be used to determine the events or achievements to be rewarded, rewards, and reward recipients.

Broadcast statistics ( 1640) . In some embodiments, the specting system 100 may collect or determine speculating statistics based on participation in the specter in broadcasts. For example, the specting system 100 can track the size of an audience of a particular broadcaster, or a combined size of audiences for all broadcasters of a particular game. As another example, the specating system is versus subscribing spectors watching certain broadcasts or games. Non-subscribing spectors can be tracked. As another example, statistics on broadcasters' product sales, audience retention, audience subscriptions, and other statistics on broadcasts or individual broadcaster channels may be collected. Various statistics can be provided to or obtained by the participant reward module 1610 and can be used to determine events or achievements to be rewarded, rewards and reward recipients.

Participant history ( 1645) . In some embodiments, the specting system 100 may maintain or obtain historical information about participants, for example, players in broadcasted games. As described above, in some embodiments, player and/or broadcaster history and statistical information may be obtained, for example, from the game system illustrated in FIG. 1C or from other sources. Participant history 1645 may be provided to or obtained by participant reward module 1610 and may be used to determine events or achievements to be rewarded, rewards and reward recipients.

Participant status, profile, and preferences ( 1650 ) . In some embodiments, the status information of the participants in the specting system 100 is provided to the participant reward module 1610 or is determined by the events or achievements, rewards, and reward recipients that can be obtained and to be rewarded. Can be used. The status information for the spectator may indicate, for example, whether the spectator is a viewer, follower, subscriber, non-subscriber, etc. Participant status may be maintained with or there, for example, with a participant account, subscription, or registration information. In some embodiments, the participant status replaces or also ranks broadcasters and/or players' ratings based on a participant'sapproval rating determined from other participants, eg, specators' inputs It can contain. As another example of a state, a broadcaster can be ranked at different levels depending on audience size, number of followers, amount of sales, retention rate, and/or other metrics or broadcast statistics. have.

In some embodiments, the specting system 100 and/or game system(s) can be leveraged by the participant reward module 1610 to determine events or achievements to be rewarded, rewards, and reward recipients. Profile and/or account information for participants may be maintained, which may include information about participants such as various demographic and location information.

In some embodiments, participants' preferences, for example specifications, specified by specators through the specting UI, determined from specter inputs and interactions, or obtained from other sources. Data viewing, game or game genre, broadcaster/channel, or other preferences can be used by participant reward module 1610 to determine events or achievements to be rewarded, rewards and reward recipients.

Participant recommendation inputs ( 1655) . In some embodiments, participants (broadcasters/players, spectors, commentators) are recognized, and/or recognized recipients, or/or groups of participants to be recognized or rewarded. You can make recommendations or nominations for the rewards you will be given. In some embodiments, participants may vote for participants or groups of participants to receive recognitions or rewards, or for rewards to be given. In some embodiments, participants may specify, nominate and/or vote on specific events and/or achievements to be rewarded. In some embodiments, the specting system 100 can speculate and/or broadcaster as illustrated in FIG. 18, for example, where participants can nominate and vote for other participants to be recognized and/or rewarded. It can provide a performance and reward interface for the people. In some embodiments, the participant or group of participants may pay individually or collectively for the selected product to be rewarded to other participant(s). In some embodiments, participants are not limited to the participant reward module for recommendations and rewards via email and other input channels including social media channels such as “tweets” or instant mesaging (IM) ( 1610).

Gift participants entered (Participant gift inputs) (1660) . In some embodiments, participants (spectators, broadcasters/players, commentators) are not limited, but game content such as health boost that players can use in-game or other in-game advantages. ), information (eg, maps), or other participants or groups of participants receiving rewards, recognition, or gifts of a game-related product including live or individually or collectively can be selected or designated. In some embodiments, the specting system 100 is capable of performance against specators and/or broadcasters as illustrated in FIG. 18, for example, where participants can give gifts to players or other participants. And a compensation interface. In some embodiments, the participant or group of participants may pay individually or collectively for the product given as a gift to other participant(s). In some embodiments, participants are not limited to a participant reward module to give gifts to participants through email and other input channels including social media channels such as “tweets” or instant mesaging (IM) ( 1610).

Third-party inputs (1665) . In some embodiments, third parties, including but not limited to game developers, online merchants, game fan sites, etc., can provide inputs 1665 to the participant reward module 1610. Inputs from third parties may include indications of events and/or achievements as to which rewards will be awarded, indications of participants to be rewarded, and/or indications of rewards to be given to selected participants, but this It is not limited to.

Participant reward module output s

In some embodiments, various performance inputs to participant reward module 1610 can be processed to determine the reward outputs illustrated in FIG. 16. The determined reward outputs may indicate events or achievements to be rewarded, participants or groups of participants to be rewarded, and/or rewards to be provided to participants or groups of participants. In some embodiments, the compensation outputs can include one or more of the following, but are not limited thereto.

Game feedback ( 1670) . In some embodiments, the participant reward module 1610 can provide a fiveback 1670 to the game system(s) 120. In some embodiments, feedback 1670 can indicate participants (eg, players) to be rewarded or recognized in the game, and/or specific rewards (eg, to be given to designated participants in the game) In-game gears, health boosts, live, maps, etc.). In some embodiments, the game can provide in-game audible and/or visual effects in response to game feedback 1670; These effects can be reflected in broadcast streams, providing visual and/or audible indications to broadcast viewers and/or receivers of in-game rewards.

Broadcast Content (1626) . In some embodiments, participant reward module 1610 can generate broadcast content 1626 based on one or more performance inputs, eg, as illustrated in figures 8, 9, and 18 It is possible to provide broadcast content 1626 to at least some participants through the tatting system user interface(s). In some embodiments, the spectating system 100 may provide performance and reward interfaces for specators and/or broadcasters as illustrated in FIG. 18, for example, where broadcast content 1626 may be provided. Can provide. The broadcast content 1626 can be specified, for example, according to specters' current choices, profiles, or preferences, or who was rewarded, what they were rewarded for, and what they were rewarded for. It can be a target for specators or groups of specators. For example, broadcast content 1626 may include UI elements provided on the UI that indicate past events for which rewards or recognitions will be given. As another example, broadcast content 1626 may include UI elements that indicate upcoming or current events for which rewards or recognitions may be given or given. As another example, broadcast content 1626 may include UI elements indicating participants (broadcasters, specators, etc.) to which rewards or recognitions may be given or given. As another example, broadcast content 1626 may include UI elements that indicate specific rewards or awards that may or may be given and states or achievements to which awards or awards will be awarded. As another example, broadcast content 1626 displays and/or instructions for a participant(s) to obtain specific rewards or groups of participants that they have been rewarded for, and for example, a participant ( S) may include active UI elements that provide a link to a web page where the reward can be earned.

In some embodiments, at least some compensation may be given or earned for free. In some embodiments, at least some compensation may be given or obtained at a cost or fee. For example, discounts on certain items can be given as rewards. As another example, exclusive virtual and/or physical items or merchandise, game content or information for restricted game events, access to participation or specting privileges, or, but not limited to, game-related advantages and content. Other advantages and content can be provided to the participant(s) who have paid for it.

In some embodiments, broadcast content 1626 may include overlays (eg, overlay video, text, etc.) that can be added to the broadcast video. For example, an overlay text may be provided that announces past, present or future events for which rewards may or may not be given to participants. As another example, rewards have been awarded, and the participants (players, broadcasters, and/or specators), who receive gifts by other participants or who are rewarded by reward third parties, or gift to participants Overlay text may be provided presenting the participants or rewarded participants or third parties.

Broadcaster / Player Reward ( 1680) . Broadcaster/player rewards 1680 can be rewarded provided to participate in special events in games or broadcasts to include, or to reach certain achievements in games or broadcasts, but to this It is not limited. The broadcaster/player reward 1680 may also include rewards awarded or given to other participants, or rewards determined in a variety of other ways. The broadcaster/player reward 1680 is, for example, but not limited to, game content such as health boosts, information (eg, maps), or live that players can use in-game or other in-game advantages. Including game-related physical and/or virtual items or products. As another example, broadcaster/player reward 1680 may include special content or recognitions provided on broadcasters' channels. As another example, broadcaster/player reward 1680 may include special content or acknowledgments such as “badges” provided on broadcasters' channels, either temporarily or permanently. As another example, broadcaster/player reward 1680 may be applied to “broadcasters”, “channels”, “highlights”, or “on-demand video” panes of the specting UI illustrated in FIG. 6A, for example. It may include promoting or highlighting the broadcaster's channel of broadcasts, broadcasts, highlight reels, and/or recordings.

In some embodiments, participant reward module 1610 may provide its broadcaster/player reward 1680 or notifications via broadcast user interface(s). In some embodiments, the speculating system 100 may be provided with a broadcaster/player reward 1680 or notifications of the module, for example, as illustrated in FIG. 18 and/or broadcasters. It can provide an interface for performance and rewards. In some embodiments, participant reward module 1610 is not limited to the module's broadcaster/via email and social media channels such as one or more other channels including “tweets” or instant messaging (IM). Player rewards 1680 or notifications may also be provided.

In some embodiments, at least some broadcaster/player rewards 1680 can be given or earned for free. In some embodiments, at least some broadcaster/player reward 1680 rewards may be given or obtained for free or at a cost. In some embodiments, broadcaster/player reward 1680 may include discounts, old coupons, special offers, or similar to various items, products, or services.

In some embodiments, at least some broadcaster/player rewards 1680 are not limited, but the game system(s) 120, such as the specting system 100, the game system(s) 120, Or it may be recorded by the specting system 100 including the participants' profile and/or history information maintained by a third party or by other systems.

Spectator Reward ( 1685) . Spectator Reward (1685) is a reward provided for participating in special events within games or broadcasts, or “being there” when certain achievements reach games or broadcasts It may include, but is not limited to this. Spectator rewards 1685 may also include rewards awarded or given to other participants, or rewards determined in a variety of other ways. Spectator rewards 1685 may include, for example, but are not limited to, free or discounted game-related physical and/or virtual items or merchandise containing game content that can be used in the game. As another example, spectator reward 1685 may include special content or recognitions provided on the specting UI of specting system 100; Special content or recognitions may be temporary or permanent. For example, the Spectator Reward 1685 is a special content or recognition provided on broadcasters' channels, either temporarily or permanently, whenever the Spectator(s) participate in the broadcast, such as “badges. )”. As another example, the Spectator Reward 1685 is a broadcast provided in the “Broadcasters”, “Channels”, “Highlights”, or “On-Demand Video” panes of the Specting UI illustrated in FIG. 6A, for example. May include specially discounted, or limited access to the broadcaster's channel of broadcasts, broadcasts, highlight reels, and/or recordings.

In some embodiments, participant reward module 1610 may provide the module's spectator reward 1685 or notifications via the broadcast user interface(s). In some embodiments, the specting system 100 may be provided for spectors and/or broadcasters, such as illustrated in FIG. 18, for example, where its spector reward 1685 or notifications may be provided. Can provide performance and reward interfaces. In some embodiments, the participant reward module 1610 is not limited, but the specification of the module through one or more other channels including email and social media channels such as “tweets” or instant messaging (IM). Rewards 1685 or notifications may also be provided.

In some embodiments, at least some spectator reward 1685 may be given or earned free of charge. In some embodiments, at least some Spectator Reward 1685 compensation may be given or earned free of charge or at a cost. In some embodiments, spectator reward 1685 may include discounts, coupons, special offers, or similar to various items, products, or services.

In some embodiments, at least some spectator compensation 1685 is not limited to, but is not limited to, game system(s) 120, such as specting system 100, game system(s) 120, or agents. Participants' profiles maintained by third parties' profiles and/or history information may be recorded by the specting system 100 or by other systems.

Participant feedback ( 1690) . In some embodiments, the participant reward module 1610 can provide feedback to at least some participants about at least some of the broadcaster/player 1680 and spectator 1685 rewards. Feedback 1690 may be provided with a variety of visual and/or audible effects provided to at least some participants, for example, through the specting system user interface(s), as illustrated, for example, in Figures 8, 9, and 18. It may include. Feedback may, for example, announce or display rewards and reward recipients, announce or promote upcoming events for which rewards may be awarded, or participants through auditory and/or visual channels in general. Can provide various information about rewards, recipients, and rewards-related events. In some embodiments, participant reward module 1610 is not limited to feedback to participants through one or more other channels including email and social media channels such as “tweets” or instant messaging (IM) 1690 ) Can also be provided.

Participant reward processing

Embodiments of the participant reward module or service 1610 can obtain the various performance inputs described above from one or more sources, which rewards will be given, and which rewards are determined by the participants or groups of participants You can process inputs to determine participants or groups of participants who will receive rewards, events and/or achievements for what will be provided. The participant reward module 1610 generates the reward outputs described above and provides outputs to one or more destinations.

As a non-limiting example of a participant reward module 1610 that processes performance inputs to generate reward outputs, game developers, specting system providers, or other entities are events specific to the games or broadcasts to be rewarded. Or, specifications for achievements can be provided. When the specifications are achieved (as non-limiting examples, the player achieves a feat, overcomes an obstacle, or acquires a level in the game; the broadcaster's audience reaches a critical size; the player is a specific size audience Specs that perform the pit in front; the broadcaster sells a certain amount of the product in a specified period; certain potential or upcoming events in the game or broadcast that some participants will be rewarded for; a specification that achieves some spectacle system participation threshold Data or Spectator; etc.) Can indicate the event or performance to be rewarded. Specifications can indicate other parameters, such as time, location, and demographic parameters. The specs provide rewards and recognitions (eg, virtual or physical merchandise, specating interface badges, coupons or discounts, special or exclusive offers, etc.) to be provided for specified events or achievements. It can also be displayed. Specifications can also indicate destination(s) for compensation outputs. The participant reward module 1610 may be received specting system, game system(s), or game metadata indicating various performance inputs from other sources, such as events in games and/or broadcasts. And/or broadcast metadata, and can be compared to those for designated events and achievements. When an event or achievement is identified, the participant reward module 1610 can obtain or determine participants (eg, broadcasters, players, and specators) who have achieved the achievement or participated in the event. The designated reward(s) can then be mapped to the recipients of the reward. In some embodiments, different recipients are different for the same event or achievement based on, for example, recipients' profiles, preferences, or specter grouping (eg, viewer, follower, or subscriber). Rewards can be received. Reward outputs can then be provided to appropriate ones of the output destinations to enable provisioning of the rewards to the recipients. Note that other methods can be used to process at least some of the performance inputs to determine and generate reward inputs.

17A is a high level flow chart of a method for acknowledging or rewarding participants in a game specting environment according to some embodiments. Various performance inputs or metrics can be obtained, as indicated at 1700 in FIG. 17A. As indicated at 1702 in FIG. 17A, performance inputs can be analyzed to determine participants to be rewarded, for example, by the participant reward module 1610 illustrated in FIG. 16. In some embodiments, for example, participant reward module 1610 may include performance inputs, but not limited to broadcast metadata and game metadata, past in games or broadcasts to which rewards may or may not be given. , Performance inputs can be analyzed to determine what individual rewards may or may not be, to determine current and/or future events, which rewards may be given, or which participant(s) to be given. As indicated at 1704 in FIG. 17A, rewards may be provided to recognized participants as described, for example, with reference to FIG. 16. As indicated by 1706 of FIG. 17A, content and feedback indicating and/or promulgating rewards may be provided as described, for example, with reference to FIG. 16. Indications and/or feedback may be provided to participants, game system(s), and one or more third parties, including but not limited to one or more of UIs, APIs, and social media channels. It may be provided through one or more channels.

17B is a flow chart of a method for rewarding participants for prominent events in games that are broadcast in accordance with some embodiments. As indicated by (1750) of FIG. 17B, the specting system may broadcast broadcast of game play received from the broadcaster device to one or more of the plurality of spector devices, for example, as illustrated in FIGS. 1A and 18. You can stream. The broadcast may be an online in-game live session or a replay of a pre-recorded game. As indicated by (1752) of FIG. 17B, a prominent event in the game and/or broadcast may be determined, at least in part, from game event data obtained from the game system. Other data, including but not limited to data representing broadcast and/or game events determined from analysis of broadcast audio, text, and/or other inputs, may also be used to determine prominent events. Prominent events can be determined, for example, by participant reward module 1610 illustrated in FIG. 16 that processes various performance inputs to determine reward outputs. As indicated by (1754) of FIG. 17B, reward for participation in a remarkable event may be determined, for example, by the participant reward module 1610 illustrated in FIG. As indicated at 1756 in FIG. 17B, participants in a remarkable event may be determined, for example, by the participant reward module 1610 illustrated in FIG. 16. As indicated by 1758 of FIG. 17B, rewards may be provided to participants by one or more channels or methods, as described, for example, with reference to FIG. 16.

18 provides non-limiting examples of performance and reward interfaces for a game spectating system in accordance with some embodiments. The participant UI 1802 may be used, for example, as an interface to a game-specting web application or mobile application, or as an interface to other network-based game-specting applications through a web browser. As a web page, it can be provided to participants (eg, specators and broadcasters). Participant UI 1802 is not limited, but one or more panes including one or more of controls 1810, video player 1832 with A/V controls 1833, and performance and reward interface 1840. Fields or regions. The controls 1810 can include one or more UI elements that interact with the game specting system, in navigation or otherwise. Video player 1832 can display a replay of a pre-recorded broadcast or a live broadcast or video stream for a channel (shown as broadcast 1834). Although not shown, in some embodiments, participant UI 1802 allows broadcaster and/or specator text chat to discuss in-game games and players, and other game-related information, events, and content, for example. The chat may also include other content or panes that can be displayed, such as chat pane.

The participant UI 1802 can include a performance and reward interface 1840 that allows participants to view and interact with broadcast content related to rewards and achievements for games and/or broadcasts. At least some of the broadcast content displayed on the performance and rewards interface 1840 is broadcast or game event, for example, for participants to vote or nominate other participants for recognition or reward, and what rewards should be given It may be interactive UI elements that allow voting or nominating on a field, or voting or nominating on a reward to be given. As another example, broadcast content is shown in the “give player gifts” pane 1846 that allows participants to provide gifts to selected participants (eg, players or broadcasters). UI elements. For example, as shown in FIG. 18, the “Give Player Gifts” 1846 pane can be selected by a participant to view a list of players or teams of players; Player info, where a participant can select one of the players or teams to view additional information about the player or team (eg, overlaid on a broadcast or provided in the performance and rewards interface 1840) (Via 1836) “Choose a plyaer” UI element. Note that players or teams in the list may be players that are currently broadcast or replayed in-game, but this is not necessary. For example, in FIG. 18, the participant has selected “player E” from the list to view information about player E, including player performance, statistics, and gear. Participants can choose which gear to give to the selected player. In some embodiments, in addition to or in addition to selecting players to receive gifts from the list, as illustrated in FIG. 18, the specting system can support drag and drop functionality. In order for the Spectator to drag the items shown in the Gifts 1846 pane and drop the items onto the player's avatar or character on the Broadcast 1834 pane to provide the selected players.

FIG. 18 shows some non-limiting example gifts for the “Space Explorers” game, including gears such as DP9000 Disruptor Pistol or LR20C laser rifle, boosts such as health boost, and information such as game maps. In some embodiments, the participant(s) may pay for the gift(s) through the “Pay here” UI element, for example, as illustrated in FIG. 18. As another example of active broadcast content, the broadcast content may include UI elements as shown in the “my rewards” (1848) pane, through which the participants receive or receive rewards, eg For example, to other pages or websites of third parties or game developers that provide rewards or links to pages where participants can pay, reimburse, or otherwise earn rewards. Links. In addition to the active broadcast content, the performance and rewards interface 1840 rewards and/or rewards participants as shown in the broadcast content of the participants, e.g. panes 1844, 1836, and 1848. It may include content that publishes or announces performance information.

Specting From community inputs Specting Game into the system Effects

Using embodiments of apparatus and methods for integrating game specting systems and game systems in a game specting environment described in this application, games are played in a game specting environment and interface with the game specting system It can be developed as much as possible. For example, a game specting system can provide an application programming interface (API) for game systems (referred to herein as a game system API). A software development kit (referred to herein as a game system SDK) that can assist developers in developing and programming games to interface and support game system APIs can be provided to game developers.

In some embodiments, the game system API and SDK may allow games running on game systems to obtain various inputs from the game specting system. In some embodiments, the game specting system can generate various game inputs based on the specating community inputs. Spectating community inputs may include, but are not limited to, Spectator participation statistics or metrics, Spectator text chat inputs, Spectator audio inputs, and Specting UI inputs. In some embodiments, game inputs can include random number inputs generated from one or more specting community inputs that can be used as an entropy source for in-game randomizing functions. For example, at a game level where enemies are spawned against the player(s) in battle, random input from the specting system based on the specting community inputs is the number, type, and/or number of enemies being multiplied. Or it can be used to determine the intensity. In some embodiments, game inputs may include parameter inputs that provide values for in-game parameters based on specting community inputs. For example, at a game level where enemies multiply against the player(s) in battle, parameter input from the specting system can specify the number type and/or strength of enemies based on the specting community inputs. have.

Thus, embodiments may be involved in games broadcasted by broadcast specters affecting gameplay through their various inputs, while simultaneously also modifying interest in gameplay affected by their speculating audience. By providing them, it is possible to provide methods for enhancing game play for players. For example, spectacle text and/or audio chat in a broadcast streamed through a specting system may be analyzed by the specting system to determine game inputs that affect certain decisions made by the game engine. Can be. The analysis can, for example, measure metrics for the chat, such as quantity or volume, and provide metrics as randomizing or parametric inputs to the game engine. As another example, analysis can determine content (eg, keywords or phrases) from the chat and collect and quantify the content to generate randomizing or parametric inputs to the game engine. As another example, the analysis can determine metrics for people's emotions or excitement from the chat and provide metrics to the game engine as randomizing or parametric parameter inputs. One or more of the various metrics can be determined and provided to the game engine as randomizing or parametric inputs to be applied in real time or near-real time to make decisions about game play or influence decisions. Gameplay can thus be influenced in very real and visual ways by real-time or near-real-time spectacle' inputs, allowing spectors to allow their influence on the game to detect their involvement in the game. Increase.

19A is a game specting system that provides inputs for a game broadcast through a game specting system based on interactions with the broadcast and spectater inputs to the broadcast, according to some embodiments. An example game effects module is illustrated in (100). The game specting system 100 described and illustrated in the Figures 1a and 1b, such as the game specting system 100, is randomized to the game engine 1922 according to the game system API 114 (1992) And/or one or more components or modules 1910 that can provide parametric (1994) game inputs. Rendering (1992) and/or parametric (1994) game inputs are specter inputs (165), such as text or audio chat inputs, at least partially broadcast content (126) and specifications determined from game metadata (124). Data interactions 164, speculation statistics collected by game specting system 100 (1982), and/or, but not limited to, social media such as “tweets” or instant messaging (IM) ) May be determined from other inputs 167 including inputs from or based on the inputs. In some embodiments, the specting system 100 may be broadcasted from the game system(s) 120 in which broadcasts 124 are being streamed according to the game system API 114, or one or more illustrated in FIG. 1C. Game metadata 1624 can be obtained from other sources.

In some embodiments, specting system 100 may enable spectacle participation in broadcasts 142 to affect the game being executed by game engine 1922 in various ways. . In some embodiments, the specting system 100 can determine information based on the spectator participation in broadcasts 142 and is provided to the game systems 140 by the specting system 100. Information may be provided as feedback for game systems 140 according to game system API 114. Spectator participation metrics that can be used include broadcasts or games to broadcast “chat”, “crowd noise”, or other audio and text channels, and Spectator audio and And/or people or audience size for text inputs 165, but is not limited to this.

In some embodiments, the specting system 100 may collect or determine speculating statistics 1982 based on participation in the specter in broadcasts. For example, in some embodiments, specting system 100 may track the size of an audience of a particular broadcaster, or a combined size of audiences for all broadcasters of a particular game. As another example, a specating system is versus subscribing specators watching specific broadcasts or games. Non-subscribing spectors can be tracked. Statistical data 1982 may be obtained by, or provided to, game effect module(s) 1910 and randomizing (1992) and/or parametric provided to game engine 1922 according to game system API 114 (1994) Can be used to determine game inputs.

In some embodiments, the specting system 100 is not limited to a broadcast chat 142 of broadcasts 142, “people noise”, or specter audio and/or text for other audio and text channels. Spectator inputs can be obtained and analyzed, including inputs 165. In some embodiments, the spectate system 100 is not limited to one, but from other input 167 sources or channels, including inputs from social media such as “tweets” or instant messaging (IM). It may replace one or more interfaces that can acquire, process, and analyze inputs, or may also include interfaces. The analysis can determine, for example, metrics for inputs 165 and/or 167, such as amount or volume in chat channels, and metrics as rendering (1992) and/or parametric (1994) game inputs. It can be provided to the game engine 1922 according to the game system API 114. As another example, analysis can determine content (eg, keywords or phrases) from one or more audio and/or text chat channels or from social media channel 167 and render to game engine 1922. Content can be collected and quantified to generate the Maging (1992) and/or Parametric (1994) game inputs. As another example, the analysis can determine metrics for people emotions or excitement from one or more specter inputs 165 and/or other inputs 167 and render the game engine 1922 to randomization (1992) and/or Or parametric (1994) game inputs. 4 is not limited to determining broadcast-related analytical information, but can acquire and analyze inputs including spectacle audio and/or text inputs 165 or other inputs 167 such as social media inputs. An exemplary participant input processing component of the speculating system 100 is illustrated. The broadcast-related analysis information is sent to the game effect module(s) 1910 upon rendering of the game engine APIs 114 to the game engine 1922 rendering (1992) and/or parametric (1994) game inputs. Can be used by 4 also provides some examples of detecting and applying broadcast-related analysis information in a game specting system to generate various rendering (1992) and/or parametric (1994) game inputs.

In some embodiments, specter participation in broadcasts can be used to determine rendering inputs 1992 to game engine 1922 that can be used as in-game rendering options that are currently being executed and broadcast. For example, one or more aspects or metrics of specter participation in a broadcast or broadcasts (people or audience size, people noise, chat level or volume, emotion or excitement level, etc.) is a game randomizing factor. It can be measured or tracked and provided as feedback to the game system 120 via the game system API 114 for use in the engine 1922. For example, at a game level where enemies multiply against the player(s) in battle, a randomizing input from specting system 100 based on specator participation in one or more broadcasts 142 of the game (1992) ) Can be used to determine the number, type, and/or intensity of multiplying enemies.

In some embodiments, participation of the Spectator in broadcasts is performed in various ways and parametric inputs to the game engine 1922 that non-randomly affect players and/or games being broadcast. (1994). As a non-limiting example, the size of a person or audience watching in-game broadcast 142 or broadcasts 142 of an event can be fed back to game engine 1922, where a stadium, arena, or other event is held. The size or appearance of the, the size of the virtual people of the spectacle shown to watch the event, and/or the noise of people provided as an audio output with the game A/V 121 included in the broadcast(s) 142 It can be used by the game engine 1922 to determine the volume. As another example, the level of people enthusiasm or support as measured by the volume, amount, or content of, for example, audio and/or text chat channel inputs 165 in broadcast 142 is the current presence of the broadcaster/player. Can be fed back to the game engine 1922 to affect the number of “bad guys” or monsters appearing in the level, or by providing broadcaster's in-game character or avatar access to certain weapons It can be used to reward broadcasters at that level, or it can have a variety of other in-game effects. As another example, Spectators' audio and/or text inputs 165 can be analyzed to detect content or emotions (keywords, cheers, boo, happiness), etc.; The analysis can be fed back to the game and used to affect players' in-game state, health, power, weapons, etc.

In some embodiments, specter participations in broadcasts used to determine randomizing (1992) and/or parametric (1994) game inputs to game engine 1922 are on specator devices 160. It may include spectacle interactions 164 with broadcast content 126 provided through the spectating UI 116. For example, broadcast content 126 allows the specting community to see game elements or events such as what type and how many enemies will appear in the level, what type of weapons or other gear players will receive, and difficulty level. Fields, etc., and may include one or more UI elements that allow selecting, voting, or voting.

In some games, as shown in FIG. 22, spectors have different teams, for example different players for different teams, and two or more different game engine instances running to support different teams and/or players. Can be fans of people. Different teams and/or players, and thus different game engines, can be affected by interactions with the same broadcast and inputs to them (or having different broadcasts of the same game). 19A shows the game effect module(s) 1910 of the specting system 100 in communication with the game engine 1922 of the game system 120 via the game system API 114, but in some embodiments In, the game effect module(s) 1910 of the specting system 100 instead of one of the game systems 120 to provide inputs (1992 and 1994) to multiple game engine(s) 1922 It can communicate with the above game servers. The game server(s) may in turn pass inputs (1992 and 1994) to one, two, or more game engine instances as shown in FIG. 1D. Game engine instances can be instantiated on one or more servers of game system 120, or alternatively at least some game engine instances can be run on broadcaster devices 140 as illustrated in FIG. 19A. have. In some embodiments, the inputs 1992 and 1994 received from the game effect module(s) 1910 of the specting system 100 may include at least some data specified for specific game engines and (Eg, designation for different teams and/or players), the game server(s) can handle the distribution of data to target engines.

19B illustrates example game input modules on a game system that processes speculating data received from a specting system to generate inputs for a game broadcast through a game specting system in accordance with some embodiments. For example. In some embodiments, the game effect module(s) of the specting system generating values for the parametric inputs 1994 and/or the rendering inputs 1992 for the game engine(s) 1922 Instead of or in addition to 1910, game effect module(s) 1910 can be used to generate various inputs and interactions (164,165,167, and 1982) as shown in FIG. ), and provide speculating data 1996 to one or more game input module(s) 1930 of game system(s) 120 according to game system API 114. Game input module(s) 1930 may then generate values for parametric inputs 1994 and/or randomizing inputs 1992 for game engine(s) 1922. In some embodiments, instead of processing various inputs and interactions (164,165,167, and 1982), game effect module(s) 1910 may include one or more inputs and/or interactions (eg, audio Or text chat inputs) and inputs and/or interactions with little or no processing to game input module(s) 1930 of game system(s) 120 according to game system API 114 You can forward them.

Figures 20A-20D are flow charts of methods for generating inputs to a game system from inputs to broadcasts and specator' interactions with them in a game specting system according to some embodiments. admit. The methods of FIGS. 20A-20D are, for example, in a specting system environment as illustrated in FIG. 19A to generate randomizing (1992) and/or parametric (1994) game inputs to game engine 1922. Can be implemented.

20A is a high level flow chart of a method for generating inputs to a game system from broadcasts and inputs to it and specator' interactions to a game specting system in accordance with some embodiments. As indicated by (2000) of FIG. 20A, the specting system may collect speculating information and inputs for a game broadcast from one or more speculating information sources. Spectating information and inputs may include, but are not limited to, Spectator participation statistics or metrics, Spectator text chat inputs, Spectator audio inputs, and Specting UI inputs.

As shown in (2002) of FIG. 20A, the specting system may generate game parametric inputs and/or randomizing inputs from the collected specting information and inputs. Figures 20b-20d illustrate example methods for generating parametric inputs and/or randomizing inputs from speculating information and inputs collected according to embodiments.

As indicated in (2004) of FIG. 20A, the spectating system may provide parametric and/or randomizing inputs to the game through the game interface. In some embodiments, the specting system can provide a game system API for game systems that game engines can specify and obtain parametric and/or randomizing inputs. In some embodiments, a game system SDK can be provided to game developers that can assist developers in developing and programming games to interface and support the game system API. The game system API and SDK may allow games running on game systems to specify and obtain parametric and/or randomizing inputs from the game specting system.

As indicated in (2006) of FIG. 20A, inputs may affect game play and/or game play in a variety of ways. For example, at a game level where enemies multiply against the player(s) in battle, random inputs from the specting system based on specting community inputs or specting statistical data are the number of enemies multiplied, It can be used to determine type, and/or intensity. As another example, at the game level, where enemies multiply against player(s) in battle, parametric input from the specting system is based on interactions with the speculating community inputs or broadcast content. The number type, and/or intensity can be specified.

20B is a high-level flow chart of a method for generating inputs from specator inputs to a game system in broadcast to a game spectating system in accordance with some embodiments. As shown in (2010) of FIG. 20B, the spectating system can collect and process spectator inputs to generate spectator input data. Spectator inputs may include, but are not limited to, broadcast chat of broadcasts, “people noise”, or other audio and text channels in the Spectator audio and/or text inputs. As shown in (2012) of FIG. 20B, the specting system may generate game parameter inputs and/or randomizing inputs based at least in part on the spectator input data. For example, analysis of the inputs can determine, for example, a metric for the inputs, such as the amount or volume of a spectator chat in chat channels, and generate randomizing and/or parametric game inputs according to the metrics. Can. As another example, the analysis can determine content (eg, keywords or phrases) from one or more audio and/or text chat channels and collect content to generate randomizing and/or parametric game inputs. And quantify. As another example, the analysis can determine metrics for people's emotions or excitement from one or more spectacle inputs and provide metrics as randomizing and/or parametric game inputs to the game.

In some embodiments, to generate a randomized input to the game system, the specting system is a spectacle audio and/or text to generate an integer value passed to the game engine as a randomized input through the game system API. Chat inputs can be collected and processed. In some embodiments, the spectating system can continuously receive and process spectacle text and/or audio inputs to generate or change values for randomizing inputs. In some embodiments, the specting system may generate a value for randomizing input in response to a request for a random number received from the game engine through the game system API.

In some embodiments, generating random values based on analysis of spectacle inputs can be leveraged to generate some interest actions in games. For example, randomizing the input can be weighted to have more impact on the game when the number of specators watching a particular game's broadcasts crosses or increases the threshold. As another example, when randomizing enemies or challenges in a game based on analysis of spectator chat inputs, the more exciting the game, the more the spectator chat may increase or become more frequent or larger. This change in the Spectator Chat can be used to make the game harder, for example by increasing the impact of the randomizing input, increasing the difficulty level that can be set, or increasing the number of multiplying enemies. Thus, using the Spectators' inputs to randomize the gameplay can provide a feedback loop where changes to the Spectators' inputs result in corresponding changes in gameplay. For example, when players are playing the game, more enemies can multiply. The increased action will make viewers more excited, which will be reflected in text and/or audio chat channels. Viewers' text and/or audio chat inputs are analyzed to provide randomizing inputs to the game engine that may be affected by the viewer's excitement level. So when the viewers' excitement level goes up, more enemies multiply, the game becomes more challenging and more interesting, etc.

20C is a high level flow chart of a method for generating inputs to a game system from spectator statistical data in a game spectating system according to some embodiments. As shown in (2020) of FIG. 20C, the spectating system may collect and process spectator data to generate spectating statistical data. For example, in some embodiments, the specting system can track the size of an audience of a particular broadcaster, or a combined size of audiences for all broadcasters of a particular game. As indicated at 2022 in FIG. 20C, the spectating system may generate game parameter inputs and/or randomizing inputs based at least in part on the spectator statistics. For example, a random value can be generated based on the number of specators currently watching certain broadcasts or the number of specators watching all broadcasts of a particular game. As another example, a parametric input value can be generated based on the current number of specators. In some embodiments, the magnitude of the statistic being monitored can be used to apply weights to render in-game effects.

20D is a high level flow chart of a method for generating inputs to a game system from spectacle interactions with broadcast content to a game spectating system in accordance with some embodiments. In some embodiments, Spectator participation in broadcasts used to determine rendering and/or parametric game inputs to the game engine interacts with Spectator UI elements in the Spectating UI and Spectator devices on the Spectator devices. It may include. As indicated at 2030 in FIG. 20D, the specting system may provide game effect broadcast content to spectacle devices. For example, broadcast content includes one or more UI elements provided through the Specting UI on Spectator devices that allow the Specting community to specify, select, or vote on game elements or events. can do. As indicated at 2032 in FIG. 20D, the spectating system can receive and process spectacle interactions with broadcast content to generate game parameter inputs. As non-limiting examples, UI elements are used to specify, select, or vote on what type and how many enemies the spectators will appear in the level, what types of weapons or other gear players will receive, difficulty levels, etc. Can allow. The specting system is speculators into the UI elements to generate selections for game elements or events as indicated by the broadcast content or parametric inputs to the game engine indicating the specators' specifications. 'Inputs can be collected and analyzed.

FIG. 21 provides a non-limiting example of a game specting system interface that allows spectators according to some embodiments to collectively affect a game broadcast through a game specting system. Specting UI 2102 is, for example, a web page of a game specting system website through a web browser, as an interface to a game specting web application or mobile application, or other network-based game specting It can be provided as an interface to applications. The specting UI 2102 is not limited, but the game metadata for the game in which the control 2110, the video player 2132 with A/V controls 2133, and the spectator broadcast 2134 It may include one or more panes or regions, including one or more of the Spectator Effect pane 2140, which can watch and interact with broadcast content based at least in part on it. The controls 2110 may include one or more UI elements that interact with the game specting system, in navigation or otherwise. Video player 2132 displays a replay of a pre-recorded broadcast or a video stream (shown as broadcast 2134) for a live broadcast or channel.

Spectator effect pane 2140 may include broadcast content based at least in part on game metadata for the game being broadcast. For example, the broadcast content displayed in the Spectator Effect pane 2140 can be used to determine what types and how many enemies the Spectators will appear on the game content, game elements or game events at the level, what types of weapons. Or it can include interactive UI elements that can be specific, selected or voted as to whether players will receive different gear, difficulty levels, when or where enemies or other game content will appear, and the like. Referring to FIG. 19A, the broadcast content and the speculators' interactions 164 displayed in the Spectator Effects pane 2140 of the Spectating UI 2102 are parametric ( 1994) and/or randomizing (1992) inputs can be collected and analyzed by the game specting system 100 to determine values. In the non-limiting example specting UI 2102 of FIG. 21, broadcast content may be any type of adversaries based on community voting as the specting community is shown in the “Votes” column. (“Bugeyes”, “Androids”, or “Cyborgs”) Can contain one or more UI elements that allow you to choose whether to appear in the game's level. Spectating system 100 collects, analyzes spectator votes, and provides results to game engine 1922 as a parametric input. In addition, spectors can specify how many opponents will appear; “How many?” Spectators' inputs to the UI element are collected and analyzed (eg, averaged), and the results are provided to the game engine 1922 as a parametric input. The specting community can thus influence gameplay in a very real and visual way in real time or near-real time through the specting UI 2102 provided by the specting service 100, so that the specting The Ting community watches their impact in-game and thus allows them to detect interventions in-game. In addition, games can be augmented against players by providing variations of interest to gameplay that are affected by their speculating audience.

22 provides a non-limiting example of specters' inputs for broadcasting to a game specting system that collectively affects a game broadcast through a game specting system according to some embodiments. 22 is a Specting User Interface (UI) 2202 for a game specting system on a device 2200 that may result in in-game visual and/or audible effects in which spectacle' inputs are broadcast. ). As shown in FIG. 22, the device 2200 of the Spectator can implement the Specting UI 2202 and the microphone 2206 and game audio (Spectator audio and/or for collecting Spectator 2220 audio) Or speakers 2204 to output people noise, broadcast audio broadcasts, etc.). Spectator's device 2200 may also include a keyboard 2209 or other input device(s) through which broadcaster/player 820 can write text input, such as broadcast chat 2218 or there Can be coupled to. In some embodiments, Spectator's device 2200 may also include or combine with input devices and techniques such as controllers or joysticks, motion tracking systems, gesture-based input systems, and the like. Can be.

In some embodiments, the specting UI 2202 is a broadcast that broadcast content can be accessed by or displayed to the speculator based at least in part on game metadata received from the individual game system. The cast content 2240 may include a pane or area. The broadcast content 2240 pane may, for example, show information about games, game players, game objects or items, game events, etc. provided by the game system in game metadata. In some embodiments, the specting UI 2202 can control the specter controls 2216 that the spectater 2260 can interact with the specting system to control broadcasts, select other broadcasts, and the like. ). In some embodiments, the specting UI 2202 can include a broadcast chat 2218 window through which the spectator 2260 can communicate with broadcasters/players and other spectors via text.

As described with reference to FIG. 4, in some embodiments, the participant input processing component of the specting system is not limited, but is randomized (1992) for the game engine 1922 according to the game system API 114 and And/or acquire and analyze spectater inputs including spectacle audio and/or text inputs to determine broadcast-related analytical information that can be used to generate parametric (1994) game inputs. For example, as shown in FIG. 22, virtual representations 2222 of spectors (eg, specator avatars) can be used to indicate the specters' affiliation or preferences as described with reference to FIG. Two or more groups (eg, in response to parametric (1994) game inputs based on analysis of profile information and/or spectacle' audio and/or text inputs to individual specators 2220 to detect) For example, fans of specific players or teams, fans of teams A and B in this example). As shown in the example of FIG. 22, virtual representations 2222 of spectors on one side of a football stadium or basketball arena in an online sports game (Team B fans, in this example) are described with reference to FIG. As Spectators' Flags when Spectators 2220, fans of a particular team and/or player are cheering or shouting loudly in response to parametric (1994) game inputs determined from analysis of audio and/or text inputs It can be made to raise, shake, or otherwise respond visually. In some embodiments, instead of or in addition to visual indications, a spectater audio output representing sounds or noises generated by speculators or by specific groups of spectors is described with reference to FIG. 4. As specified in response to parametric (1994) game inputs determined from the analysis of the speculators' audio and/or text inputs, the speculators' 2200 may be provided to the speculators 2220.

The content of the speculating UI 2202 may include, for example, profile, preference, and/or UI options and configuration information for individual specators 2220 or group profile information for groups of specators 2220. Note that it may vary for different spectors 2220 based on the. For example, the view of the displayed game in the UI 2202 may change based on the team affiliation of the spectator 2220. In addition, for example, audio output by a gaming specting system through the device 2200 may include profile, preference, and/or UI options and configuration information for individual specators 2220 or specators ( Based on the group profile information for the groups of 2220) may vary for different specators 2220. For example, in the example of FIG. 22, fans of Team A can hear other people's noises than fans of Team B.

Specting With games through the system Spectator Interactions

Using embodiments of apparatus and methods for integrating game specting systems and game systems in a game specting environment described in this application, games are played in a game specting environment and interface with the game specting system It can be developed as much as possible. For example, a game specting system can provide an application programming interface (API) for game systems (referred to herein as a game system API). A software development kit (referred to herein as a game system SDK) that can assist developers in developing and programming games to interface and support game system APIs can be provided to game developers.

In some embodiments, the game system API and SDK is used by games running on game systems to obtain interactions with the specting UI from the specting system according to the game system API and various specator inputs to it. It may allow providing game metadata to a specting system that can be used to generate game-related broadcast content provided in a chat user interface (UI). In some embodiments, the specting system can generate various game inputs based on interactions with the specting UI and specting community inputs to it. In some embodiments, the specting system interacts with speculators interacting with broadcasters and players in games in a variety of ways and/or with games broadcast through the specting UI. It can be possible to influence. In some embodiments, individual spectors can interact with games through the specting UI to produce in-game effects. In some embodiments, groups of spectors can cause in-game effects through the specting UI, for example based on voting, or otherwise, affect the game. In some embodiments, the specting system uses game metadata to provide specting UI elements that speculators can interact to provide inputs that affect individual games and interact with individual games. Leverage. In some embodiments, the specting system may provide specter interactions as feedback or game inputs to game systems according to the game system API provided to game systems by the specting system. have.

In some embodiments, specators may or may affect in-game players or in-game events, objects in a game universe, game through UI elements on the specting UI. As non-limiting examples, specators can build buildings, hide weapons, set difficult levels, choose weather or other environmental factors, or otherwise play through UI elements provided on the speculating UI, or otherwise Content and events can be affected. In some embodiments, spectors are specific players in the game, for example through a specting UI with objects, boosts, weapons, medicines, health points, strength levels, etc. You can provide game content to your teams of players or you can "gift" them. In some embodiments, specators may provide information, such as maps, warnings, or advice, to in-game players or teams of players through the specting UI. In some embodiments, spectors, for example, by causing a storm or other catastrophe, increase the difficulty of game levels, tasks or challenges, by taking objects from players, reducing players' strength, Challenges and difficulties for players or games in games can be introduced through the specting UI and the like by limiting powers. Gameplay can thus interact in real-time or near-real-time with the Specting UI and be influenced by Spectators' inputs on it in very real and visual ways, allowing Spectators to influence their impact on the game. Permit to detect and increase their involvement in the game. In some embodiments, UI elements are provided to the specter to purchase or otherwise pay for other effects on the games or content provided through the UI elements, and/or in-game content to be braked to players. It may include UI elements to provide.

In some embodiments, in addition to providing UI elements on a specting UI that may or may affect a game running on the game system, speculators affect or affect the game. Game inputs are not limited, but may be determined from analysis of spectacle inputs to spectacle devices, including text or audio inputs to spectacle devices. For example, keywords or key phrases indicating spectacle instructions in the game system may be determined from analysis of text, audio, and/or other inputs, such as social media inputs, as illustrated in FIG. 4. In some embodiments, specator inputs from which game inputs can be determined may also include inputs from devices and technologies such as controllers or joysticks, motion tracking systems, gesture-based input systems, etc. .

In some embodiments, in addition to allowing the speculator to affect or influence the game running on the game system through the specting UI and interactions and inputs to it, the specting system is Spectators may individually or collectively provide one or more UI elements that can provide information to the broadcaster. For example, as shown in Figures 25 and 26a, the Community Inputs pane allows the Spectator to provide information to the broadcaster, in this example location information for hidden objects: ”Includes UI elements. Inputs to the UI elements on the Spectator device are for example broadcasts of the community inputs 2666 as text in the pane and/or as graphics in the map overlay window 2662 as shown in FIG. 26B. It is possible to generate input information to be displayed on the device. The information is not necessarily, but may be displayed on other Spectators' devices. Spectator devices and broadcast devices may also include broadcast chat windows through which the spectors and broadcasters can communicate, and the spectating system is audio as illustrated in figures 25, 26a, and 26b. Note that audio chat can be supported through the chat channel.

In some embodiments, the specting system is one or more components or modules mentioned in the present application as game interaction modules capable of providing game inputs to game engines running on game systems according to the game system API. It can contain. In some embodiments, at least some of the game interaction modules can be provided by a specting system. However, in some embodiments, at least some of the game interaction modules may be developed according to the game system SDK and may be provided to the specting system by third parties, including but not limited to game developers. Game interaction modules can, for example, define UI elements for interacting with a game, define game inputs for a game, interactions and values with UI elements in values for game inputs You can map the inputs to In some embodiments, the received game metadata attached to the game system according to the game system API is game content for the game, and U defined by the game interaction module(s) corresponding to or representing the game content. Contains information describing or expressing at least some of the elements.

23 illustrates an example game interaction module in a game specting system that allows spectors according to some embodiments to provide inputs affecting a game broadcast through the game specting system. Game specting system 100 described and illustrated in figures 1a and 1b, such as game specting system 100, provides game inputs 2396 to game engine 2322 according to game system API 114 It can include or implement one or more components or modules 2310 that can. At least some of the game inputs 2396 are determined at least partially from game metadata 124 and provided to the speculators via the game interaction UI(s) 2362 on the specator device(s) 160. May be determined based on or from spectacle interactions 164 with broadcast content 126. In some embodiments, the specting system 100 may be broadcasted from the game system(s) 120 in which broadcasts 124 are being streamed according to the game system API 114, or one or more illustrated in FIG. 1C. Game metadata 1624 can be obtained from other sources. In some embodiments, at least some of the game inputs 2396 can be determined from the specator inputs 165 to the specator device(s) 160, such as text or audio chat inputs. In some embodiments, values for game inputs 2396 are not limited, but specter device(s) 160 that include inputs from social media such as “tweets” or instant messaging (IM). ) Or other inputs to the specting system 100. In some embodiments, the spectating system can obtain video or image inputs of a spectacle eye motion, body motion, or facial expression from spectacle devices 160 and execute on game system 120. Video or image inputs may be processed to determine metrics that specify games and interactions, and values may be generated for one or more game inputs 2396 according to the determined metrics.

In some embodiments, the specting system 100 affects a game that is performed by the broadcast engine 142 and the game engine 2322 to the specator device(s) 160 in various ways. It can make you crazy and able to interact with it. In some embodiments, the game interaction module(s) 2310 of the specting system 100 is based on spectacle interactions 164 and/or inputs 165 and game inputs 2396 Can determine values for and provide game inputs 2396 for game systems 140 according to game system API 114 provided to game systems 140 by specting system 100 can do.

In some embodiments, specator inputs and interactions that determine values for game inputs 2196 to game engine 2322 may include, for example, game interaction UI(s) on specator devices 160. ) On 2362 may include spectacle interactions 164 with broadcast content 126 provided through the specting UI 116. 25 illustrates an example specting UI that includes a game interaction user interface. In some embodiments, the game system API 114 and SDK provide game-related broadcast content 126 in which games running on game systems 120 are provided on game interaction UI(s) 2362. Providing game metadata 124 for the specting system 100 that can be used to generate, and game interaction UI(s) from the specting system 100 according to the game system API 114 It may allow obtaining game inputs 2396 that are determined according to interactions with the broadcast content of 2362 and various specator inputs to them. In some embodiments, the specting system 100 interacts with the game interaction UI(s) 2362 and various game inputs 2396 based on the speculating community inputs and specator for it. You can create In some embodiments, the spectating system 100 interacts with the broadcasters and players in games in various ways and/or through the game interaction UI(s) 2362 in various ways. It may enable interacting with and affecting the games being broadcast 142. In some embodiments, individual spectors can interact with games through game interaction UI(s) 2362 to produce in-game effects. In some embodiments, groups of spectors can cause in-game effects through game interaction UI(s) 2362 based on voting, for example, or otherwise affect the game. have.

In some embodiments, individual spectors and/or groups of spectors are in-game players or in-game events, objects in a game universe, through UI elements on game interaction UI(s) 2362. It may or may affect the game. As non-limiting examples, spectors build buildings, hide weapons, set difficult levels, select weather or other environmental factors through UI elements provided on game interaction UI(s) 2362. Or, otherwise, it may affect game content and events. In some embodiments, specators are specific players in the game, for example through game interaction UI(s) 2362 with objects, boosts, weapons, medicines, health points, strength levels, etc. The game content can be provided to teams of players or players or "gifts" to them. In some embodiments, specators may provide information, such as maps, warnings, or advice, to in-game players or teams of players through game interaction UI(s) 2362. In some embodiments, spectors, for example, by causing a storm or other catastrophe, increase the difficulty of game levels, tasks or challenges, by taking objects from players, reducing players' strength, Challenges and difficulties for players or games in games can be introduced through game interaction UI(s) 2362 and so on by limiting powers. Gameplay can thus interact in real-time or near-real-time with the game interaction UI(s) 2362 and be influenced in very real and visual ways by the Spectators' inputs to it, allowing the Spectators to By allowing their influence on the game, they detect and increase their involvement in the game.

In some embodiments, the specting system 100 is not limited to the spectacle audio and/or text inputs 165 for the broadcast chat or other audio and text channels of the broadcasts 142. Spectator inputs can also be acquired and analyzed, including. In some embodiments, the spectate system 100 is not limited to one, but from other input 167 sources or channels, including inputs from social media such as “tweets” or instant messaging (IM). It may replace one or more interfaces that can acquire, process, and analyze inputs, or may also include interfaces. Analysis can determine content (eg, keywords or phrases) from one or more audio and/or text chat channels or from social media channel 167 and game inputs 2196 to game engine 2322. Content can be collected and quantified to generate. 4 is not limited to determining broadcast-related analytical information, but can acquire and analyze inputs including spectacle audio and/or text inputs 165 or other inputs 167 such as social media inputs. An exemplary participant input processing component of the speculating system 100 is illustrated. In some embodiments, broadcast-related analysis information is to be used by game interaction module(s) 2310 in generating game inputs 2196 to game engine 2322 according to game system API 114. Can.

In some embodiments, the specting system 100 can provide one or more UI elements that the spectors can individually or collectively provide information 2364 to the broadcaster. For example, as shown in Figures 25 and 26a, the community inputs pane includes UI elements through which the spectator can provide information 2364 to the broadcaster. Inputs to UI elements on the spectator device 160 may generate input information 2364 to be displayed on the broadcaster device 140 in the community inputs pane as shown in FIG. 26B, for example. . In some embodiments, information 2364 may, but not necessarily, be displayed on other Spectators' devices 140. Spectator devices 160 and broadcast device 140 may also include broadcast chat windows through which spectors and broadcasters can communicate, and speculating system 100 includes drawings 25 and 26a. Note that audio chat may be supported through the audio chat channel as illustrated in, and 26b.

In some games, as shown in FIG. 22, spectors have different teams, for example different players for different teams, and two or more different game engine instances running to support different teams and/or players. Can be fans of people. Different teams and/or players, and thus different game engines, can be affected by interactions with the same broadcast and inputs to them (or having different broadcasts of the same game). 23A shows the game interaction module(s) 2310 of the specting system 100 in communication with the game engine 2322 of the game system 120 via the game system API 114, but in some embodiments In the field, the game interaction module(s) 2310 of the specting system 100 instead of one of the game systems 120 to provide inputs 2396 to multiple game engine(s) 2322 It can communicate with the above game servers. The game server(s) in turn can pass game inputs 2396 to one, two, or more game engine instances as shown in FIG. 1D. Game engine instances can be instantiated on one or more servers of game system 120, or alternatively at least some game engine instances can be run on broadcaster devices 140 as illustrated in FIG. 23A. have. In some embodiments, game inputs 2396 received from game interaction module(s) 2310 of specting system 100 may include at least some data assigned to specific game engines (eg For example, designation for different teams and/or players), the game server(s) can handle the distribution of data to target engines.

24A is a flow chart of a method that allows a spectator according to some embodiments to provide inputs affecting a game broadcast to a game specting system. The method of FIG. 24A can be implemented, for example, by the spectating system 100 illustrated in FIGS. 1A, 1B, or 23. As indicated at 2400 in FIG. 24A, the specting system can provide game interaction broadcast content to the game interaction UI on the spectator devices, for example, as illustrated in FIGS. 23 and 25. have. The broadcast content may be based at least in part on game metadata received from one or more other sources illustrated in FIG. 1C or from a game system. As indicated at 2402 in FIG. 24A, the spectating system can receive and process specator' interactions with broadcast content to generate game inputs, for example, as illustrated in FIG. . As indicated by (2404) of FIG. 24A, the specting system may provide game inputs to the game through, for example, the game system API illustrated in FIG. 23 and a game interface. As indicated at 2406 in FIG. 24A, game inputs can affect the game in a variety of ways, as described, for example, with reference to figures 23 and 25.

24B is a flow chart of a method for analyzing spectacle audio or text inputs affecting a game broadcast to a game spectating system in accordance with some embodiments. The method of FIG. 24B can be implemented, for example, by the spectating system 100 illustrated in FIGS. 1A, 1B, or 23. As indicated by (2450) of FIG. 24B, the specting system may obtain audio and/or text inputs from the broadcast's specter, as illustrated, for example, with reference to FIGS. 26A and 26B. In some embodiments, other inputs are used to the specting system, such as social media inputs and inputs from devices and technologies, such as controllers or joysticks, motion tracking systems, gesture-based input systems, etc. Can be obtained by As indicated by (2452) of FIG. 24B, the specting system may analyze the inputs to determine specter inputs directed to affect the game. For example, keywords or key phrases indicating spectacle instructions for the game system can be determined from analysis of text, audio, and/or other inputs, such as social media inputs, as illustrated in FIG. Exemplary participant input processing of a specting system that is not limited to determining cast-related analytical information, but can acquire and analyze inputs including spectacle audio and/or text inputs or other inputs such as social media inputs. Illustrate components. As indicated by (2454) of FIG. 24B, the specting system may generate game inputs from the spectator inputs, for example, as illustrated in FIG. As shown in (2456) of FIG. 24B, the specting system may provide game inputs to the game through, for example, the game system API illustrated in FIG. 23, a game interface. As indicated at 2458 in FIG. 24B, game inputs may affect the game in a variety of ways, as described, for example, with reference to figures 23 and 25.

25 is a non-limiting view of a specting user interface for a game specting system that allows spectors according to some embodiments to provide inputs affecting a game broadcast through the game specting system. Provide an example. Specting UI 2502 is, for example, a web page of a game specting system website through a web browser, as an interface to a game specting web application or mobile application, or other network-based game specting It can be provided as an interface to applications. The specting UI 2502 is not limited, but the video player 2532 with controls 2510, A/V controls 2533, the chat 2536 window, and speculators can play the game in various ways. Game interaction pane 2540 and speculators capable of viewing and interacting with broadcast content based at least in part on game metadata for the game being broadcast (2534) to influence the broadcaster to provide information to broadcasters It may include one or more panes or areas, including a community inputs 2516 pane that can. The controls 2510 may include one or more UI elements that interact with the game specting system, in navigation or otherwise. Video player 2532 displays a replay of a pre-recorded broadcast or a video stream (shown as broadcast 2534) for a live broadcast or channel.

The game interaction pane 2540 can include broadcast content based at least in part on game metadata for the game being broadcast. The broadcast content displayed in the game interaction pane 2540 can include interactive UI elements that can affect the game in which the speculators are broadcast 2534. Space Explorers!” As shown in this example for a game, the game interaction pane 2540 allows spectors to play objects in the game (eg, buildings, terrain, weapons, other objects such as scrolls). , UI elements that can add, build, or hide information, such as maps, etc., UI elements where specators can affect the game environment (e.g., weather) in various ways, player with specators selected UI elements that can provide gear, information, or other game content to them, and spectors can include one or more of the UI elements that can set game parameters such as difficulty level, number of enemies, etc. It is not limited to it. As shown in FIG. 25, the game interaction pane 2540 also includes a “Choose a player” UI element that Spectators can use to select players or players to provide gear or other game content. It can contain. In some embodiments, the spectator(s) may pay for gear or other game content through, for example, a “Pay here” UI element, as illustrated in FIG. 25. In some embodiments, game interaction pane 2540 can provide UI elements that speculators can vote for one or more game-changing options provided through game interaction pane 2540.

In some embodiments, in addition to the broadcast content in the game interaction pane 2540 that allows the speculators to interact with and interact with the games in various ways, the specting UI 2502 Silver Spectators can provide one or more UI elements that can individually or collectively provide information to the broadcaster. For example, as shown in Figures 25, the community inputs 2516 pane “Look at” allows the Spectator to provide information to the broadcaster, in this example location information for hidden objects. :” Contains UI elements. Inputs to UI elements on the spectator device may generate input information to be displayed on the broadcaster's device in the community inputs pane as shown in FIG. 26B, for example. The information is not necessarily, but may be displayed on other Spectators' devices. Spectator devices and broadcast devices may also include broadcast chat windows through which the spectors and broadcasters can communicate, and the spectating system is audio as illustrated in figures 25, 26a, and 26b. Note that audio chat can be supported through the chat channel.

Referring to FIG. 23, the broadcast content and the speculators' interactions 164 displayed in the game interaction pane 2540 of the specting UI 2502 are the game inputs to the game engine 2322 ( It can be collected and analyzed by the game interaction module(s) 2310 of the specting system 100 to determine values for 2396. Game interaction module(s) 2310 collects and analyzes spectacle interactions 164 and provides results to game engine 2322 as game inputs 2396. In addition, the chat 2536 window, text inputs via audio chat, and other inputs can be analyzed as illustrated, for example, with reference to FIG. 4 to generate game inputs 2396. The specting community can thus influence gameplay in a very real and visual way in real time or near-real time through the specting UI 2502 provided by the specting service 100, so that the specting community The Ting community watches their impact in-game and thus allows them to detect interventions in-game. In addition, games can be augmented against players by providing variations of interest to gameplay that are affected by their speculating audience.

26A is a specting user interface for a game specting system that allows spectors and specting community inputs to affect a game broadcast through the game specting system, according to some embodiments. Other non-limiting examples are provided. The Spectator' device 2600 can implement the Spectating UI 2602 and microphone 2606 and game audio (Spectator audio and/or people noise, broadcast audio live broadcast, to collect Spectator audio input) Speakers, etc.). The Spectator's device 2600 may also include or combine a keyboard 2609 or other input device(s) through which the Spectator 2660 can write text input, such as a broadcast chat 2618. Can be. In some embodiments, Spectator's device 2600 may also include or combine with input devices and techniques such as controllers or joysticks, motion tracking systems, gesture-based input systems, and the like. Can be.

In some embodiments, UI 2602 can include a game specting window 2610 that displays a current view of the game universe, for example, from a broadcaster/player perspective. In some embodiments, the UI 2602 is a specter control 2619 window or pane where the specter 2660 can interact with the specting system to control broadcasts, select other broadcasts, and the like. It may also include. In some embodiments, the UI 2602 is configured to broadcast content that broadcast content can be accessed by or displayed to the spectator 2660 based at least in part on game metadata received from the individual game system. 2640) may include a pane or area. The broadcast content 2640 pane may, for example, show information about games, game players, game objects or items, game events, etc. provided by the game system in game metadata. In some embodiments, the UI 2602 can include a broadcast chat 2618 window through which the spectator 2660 can communicate with broadcasters/players and other spectors via text.

In some embodiments, UI 2602 can include a window 2614 showing a live view of the broadcaster/player as a window within or over, for example, a game specting window 2610. . In some embodiments, the world map 2612 or a portion of a map of the online game world may be displayed on the UI 2602, for example, within the game speculating window 2610 or as an overlaid window. In some embodiments, window 2615 can show a different perspective of the game selected by the spectator, or alternatively can show on-demand video content such as reels of highlight reels or pre-recorded game sessions.

In some embodiments, UI 2602 is a game interaction interface 2644 that allows a spectator to interact with UI elements affecting the game in a variety of ways, as described with reference to FIG. 25, for example. It may include. In some embodiments, UI 2602 also includes a community inputs 2616 interface through which the spectator can interact with UI elements to communicate with the broadcaster, as described with reference to FIG. 25, for example. can do.

26B is a ratio of a broadcast user interface for a game specting system that allows spectaters and specting community inputs to affect a game broadcast through the game specting system, according to some embodiments. Provide limited examples. The broadcaster's device 2650 may implement a game and broadcasting UI 2562, and may use an A/V device 2656 (e.g., microphone) to collect broadcaster/player 2670 audio and video inputs. Video camera) and speakers 2654 (including spectacle audio and/or people noise) to output game audio. The broadcaster's device 2650 may also include a keyboard 2659 or other input device(s) through which the broadcaster/player 2670 can enter text input, such as a player chat or broadcast chat. Can be coupled to. In some embodiments, the broadcaster's device 2650 may also include or combine with input devices and technologies such as controllers or joysticks, motion tracking systems, gesture-based input systems, and the like. Can be.

In some embodiments, the broadcasting UI 2562 can include a game play window 2660 that displays the current view of the game universe for the broadcaster/player 2670. Note that the broadcaster' view of the game universe shown in window 2660 can be viewed and included in the broadcast, for example, as shown in FIG. 9. In some embodiments, UI 2262 can also include game controls 2696 through which broadcaster/player 2670 can interact with the game system. In some embodiments, the UI 2262 can include an in-game chat 2665 through which the broadcaster/player 2670 can communicate to other players in the game via text. In some embodiments, the UI 2652 can also include broadcast controls 2667 that the broadcaster/player 2670 can interact with the specting system to control the broadcast. In some embodiments, the UI 2652 can include a broadcaster/player 2670 and a broadcast chat 2668 through which specators can communicate via text. In some embodiments, the UI 2262 is configured with community inputs 2666 through which information provided to specific broadcasters by speculators may be displayed via speculating interfaces as illustrated in figures 25 and 26a. ) Can also include a pane. In some embodiments, the information provided may be provided graphically instead of or also as graphics in the world map overlay window 2672, for example, as shown in FIG. 26B.

game Specting Data collection and gaming to consumers Specting Data provided

Broadcasts Collect and store speculating data from broadcasts in a game specting environment, and bend the collected data to, but not limited to, game developers, online merchants, and consumers including broadcasters ( Embodiments of the specting system vend) are described. In some embodiments, the specting system is not limited, and may acquire broadcasts including A/V content from broadcast devices. In some embodiments, the specting system may also obtain game metadata from game systems where broadcasts are being streamed or from one or more other sources as illustrated in FIG. 1C. The specting system stores audiovisual (A/V) content for broadcasts, and collects and stores specting data, including but not limited to game metadata and broadcasts and broadcast content and specator interactions. do. The specting system exposes speculating data and A/V content to consumers through, for example, a user interface (UI), a query interface, and/or an application programming interface (API). The specting system may provide speculating data to consumers in an original or unprocessed form, for example through an API. Instead or in addition, the specting system may perform processing and analysis on at least some specting data, but is not limited to through query interfaces and one or more interfaces including UIs such as web pages. It can provide access to processed data and/or analytical data.

In some embodiments, the specting data stored by the specting system may also include broadcast or speculating statistics. The speculating system can collect or determine statistics based on participation in the specter in broadcasts, and can store statistical data with game metadata, specator interaction data, and other speculating data. For example, in some embodiments, the specting system can track the size of an audience of a particular broadcaster, or a combined size of audiences for all broadcasters of a particular game. As another example, the specting system is a subscription to the particular subscribers watching specific broadcasts or games. Non-subscribing spectors can be tracked.

In some embodiments, the audience or people state or emotion can be tracked by the specting system and stored as additional speculating data. As another example, Spectators' video, audio and/or text inputs can be analyzed as illustrated in FIG. 4 to detect content or emotions (keywords, cheers, boo, happiness, etc.); Analysis information can be used to determine audience status or emotion metrics during broadcasts, and metrics can be stored along with speculating data.

In some embodiments, speech recognition technology can be applied to one or more audio inputs to broadcasts to recognize and convert spoken words into text, and the text can be stored as additional speculating data. For example, the broadcaster's audio channel can be converted to text and stored as speculating data. As another example, the audio channel of the narrator can be converted into text and stored as speculating data. The text can then be exposed to consumers through the API, UI, and/or query interface, and also for example in the game stream or to other speculating data eg Specators' text chat inputs Can be interrelated temporarily.

Specting systems can correlate speculating data and A/V content using, for example, timestamps, so that consumers are able to correlate specific specator behaviors, broadcast statistics (eg audience size), Or you can review portions of text, and/or video, audio from broadcasts that can be related to speculating events indicated by individual speculating data. Specting data can also be spatially mapped to the specting interface so that consumers can determine various broadcast content and interactions and specator interest there. Spectating data may include data for single broadcasts, broadcasters, or games, or for multiple broadcasts, broadcasters, or games.

In some embodiments, the specting system is not limited, but includes at least a portion of broadcast metadata and game metadata for broadcasts that include specator interactions with individual broadcast content as game specting data. Can be saved. The specting system can also record audiovisual (A/V) content for at least some broadcasts. A game specting system is a method in which consumers (eg, game developers) are subordinate to individual broadcasts, game specting data for broadcasters, or broadcasts, broadcasters, or games. It may provide one or more UIs, query interfaces, and/or APIs that can obtain or view speculating data. Spectating data can be analyzed, presented and viewed in a variety of ways, and for various purposes, for example, to analyze online game usage and performance for applications in game development, advertising, and/or marketing. It can be applied by consumers for use or to analyze the bending of game-related content and products through a specting interface. Note that the specting system provider may also leverage specting data, for example, to evaluate specting system UIs and UI content. For example, a specting system provider can use heat maps as illustrated in FIG. 30 to evaluate the content layout of specting interfaces.

In some embodiments, the specting system is capable of performing at least some processing and analysis on specting data, and interface methods (eg, for consumers to obtain and/or view pre-processed data) UIs). In some embodiments, the specting system replaces an interface, such as a query interface that allows consumers to acquire, process, and analyze specting data according to their own general purpose. Or it can be provided in addition to it. The query interface is a query language that allows consumers to make requests or queries for information, for example, to a database or data store that stores speculating data, for example to perform retrieval of specting data. query language).

27 illustrates collecting and storing game data in a game specting system according to some embodiments. As shown in FIG. 27, the game specting system 100, such as the specting system 100 illustrated and described in FIGS. 1A, 1B, and 10, includes video, audio, and text (eg, chat ) Includes broadcast A/V content 2798 from broadcasts 142 including channels, but not limited to, broadcast metadata for broadcasts 142 and at least some of game metadata 124 One or more broadcast processing modules capable of collecting and storing broadcast data 2696, and data 2794 describing broadcasts 142 and broadcast content 126 and specator interactions 164 Field 2700 can be implemented. Specting-related data may be stored in specting data store 2810. Specting data store 2810 may be provided by one or more storage devices, systems, or services, such as provider network services 4192 to provider network 4190 as illustrated in FIG. 32, or It can be implemented by the storage service(s) implemented by it.

The game specting system 100 may include one or more components or modules capable of providing broadcast content 126 to speculators through the specting UI 116 on individual specator devices 160 ( 2700). The broadcast content 126 may be determined at least in part from game metadata 124 received from the game system(s) 120 according to the game system API 114 provided by the specting system 100. In some embodiments, broadcast content 126 may be determined, at least in part, from game-related data obtained from one or more other sources, such as online merchants. Spectators can obtain game-related content through specting UI 116 by viewing, exploring, selecting and ordering, purchasing, or other ways, and according to specting UI 116, specter devices 160 ). Module(s) 2700 may acquire and process spectacle interactions 164 with broadcast content 126 provided on spectacle devices 160 to generate spectacle interaction data 2794. Can.

In some embodiments, the broadcasts 142 and broadcast content 126 and the spectacle interactions are tracked, processed, and as spectacle interaction data 2794 in the specating data store 2810, and It can be recorded. Spectator interactions are UI element selection, UI element manipulation (e.g., by scrolling, clicking, sliding, turning, etc.), on or near the UI element. Hovering (e.g., with a cursor), typing into a UI element (e.g., entering text into a text box), and focusing on one or more UI elements (e.g., eye tracking) (Detected through technology).

In some embodiments, acquiring and recording broadcasts 142 and broadcast content 126 and spectacle interactions may include tracking spectator navigation from specting UI to other pages or sites. Can. For example, in some embodiments, the specting UI can be a web page provided on a web browser, and the specter interactions with the broadcasts 142 and broadcast content 126 are obtained and recorded. And tracking spectator navigation from the dating UI to one or more other web pages.

In some embodiments, acquiring and recording broadcasts 142 and broadcast content 126 and specator interactions is directed to the specting UI, broadcasts 142, and broadcast content 126. Tracking and recording one or both of eye motion or head motion.

28 illustrates an example game specification module or service that exposes game specification data to consumers in a game specification system according to some embodiments. As shown in FIG. 27, the game specting system 100, such as the specting system 100 illustrated and described in FIGS. 1A, 1B, and 10, includes video, audio, and text (eg, chat ) Includes broadcast A/V content 2798 from broadcasts 142 including channels, but not limited to, broadcast metadata for broadcasts 142 and at least some of game metadata 124 One or more broadcast processing modules capable of collecting and storing broadcast data 2696, and data 2794 describing broadcasts 142 and broadcast content 126 and specator interactions 164 Field 2700 can be implemented. Specting-related data may be stored in specting data store 2810. Specting data store 2810 may be provided by one or more storage devices, systems, or services, such as provider network services 4192 to provider network 4190 as illustrated in FIG. 32, or It can be implemented by the storage service(s) implemented by it.

28, game specting module 2800 broadcasts A/V content 2798 to one or more speculating data consumers 2880 via one or more speculating data interfaces 2802. ), broadcast data 2696, and spectator interaction data 2794. The game speculating module 2800 may be a module or service of the specting system 100 as illustrated in figures 1a, 1b, or 27, or alternatively a separate module or service, for example It may be a service implemented as or by provider network services 4192 in provider network 4190 as illustrated in FIG. 32.

Specting data interfaces 2802 can include, but are not limited to, user interfaces (UIs) such as web pages, query interfaces, and/or application programming interfaces (APIs). Through interface(s) 2802, consumers 2890 may specify data 2932 (including data from broadcast data 2696 and/or specator interaction data 2794) and/or broadcast Can generate requests 2822 for cast A/V 2836.

In some embodiments, the game specting module 2800 can temporarily correlate the broadcast A/V 2836 data and the specting data 2832 using, for example, timestamps, such that the consumer The fields 2890 are video, audio, and/or text (correlated) from broadcasts that may be related to specific spectacle actions or speculating events indicated by the individual (correlated) speculating data 2844. Parts of the broadcast A/V (2846). FIG. 31 shows an example of temporarily correlating speculating data with broadcast A/V. In some embodiments, specting data 2844 can also be spatially mapped to specting UIs where broadcasts and broadcast content are provided so that consumers 2890 can be shown, for example, in FIG. 30. As such, it is possible to determine various broadcast content and interactions and specator interest in it. The requested speculating data 2844 and correlated broadcast A/V 2846 are for single broadcasts, broadcasters, or games, or multiple broadcasts, broadcasters, or games And A/V.

29 is a flow chart of a method for collecting game speculating data according to some embodiments and exposing data to consumers in a specting system. The method of FIG. 29 can be implemented, for example, by the specting system 100 illustrated in FIGS. 1A, 1B, and 27. As indicated by (2900) of FIG. 29, the specting system determines broadcast content for individual broadcasts, at least in part, from game metadata, as described with reference to FIGS. 1A, 1B, or 27, for example. Can. As indicated by 2910 of FIG. 29, the spectating system may stream broadcasts and broadcast content to spectater devices, as described, for example, with reference to FIGS. 1A, 1B, or 27. .

As indicated by 2920 in FIG. 29, the spectating system may record broadcast A/V content, for example, as described with reference to FIGS. 27 and 28. As indicated by 2930 in FIG. 29, the spectating system may determine and record broadcast data as spectating data, for example, as described with reference to FIGS. 27 and 28. As indicated by (2940) of FIG. 29, the spectating system captures and records spectacle interactions with broadcasts as spectating data, for example, as described with reference to FIGS. 27 and 28. can do.

As shown in (2950) of FIG. 29, broadcast A/V content may be correlated with speculating data according to timestamps provided as metadata having, for example, A/V content and game metadata. . In some embodiments, the game specting module or service illustrated in FIG. 28 may perform correlation, for example, in response to consumer requests for specting data. As shown in (2960) of FIG. 29, speculating data may be exposed to the consumer(s) through the UI, API, and/or query interface, for example through the interface(s) illustrated in FIG. . As shown in (2970) of FIG. 29, the spectating system may respond to requests for the interface(s) illustrated in FIG. 28 via the UI, API, and/or query interface, for example, consumer(s). It is possible to provide broadcast A/V content correlated with speculating data.

As indicated by the arrow returning from element 2950 to element 2900, in at least some embodiments, the method of FIG. 29 is directed to speculating data and broadcasts to be exposed to consumer(s) through interfaces. The A/V content can be an iterative process that is acquired, stored and correlated.

30 is a game spectacle showing a heat map overlaid on a layout or specting interface 3002 template showing broadcast content and spectacle interactions during at least a portion of a broadcast in accordance with some embodiments. This is a non-limiting example of the Ting data consumer interface. 30 shows an example, for example, including a video player 3032 and broadcast 3034 pane, highlight 3034 pane, and chat 3036 pane with controls 3033 illustrated in FIG. 6A. An example specating UI 3002 template or layout that can be done. Specting UI 3032 is a game 3050 pane showing one or more games 3052, as illustrated in FIG. 6A, channels 3060 pane showing one or more broadcasters 3062, for example. , And an on-demand video 3070 pane showing one or more videos 3072 such as pre-recorded broadcasts and highlight reels. Specting UI 3032 may also include a game sales interface 3040 that includes UI elements for obtaining game-related content and products, for example, as illustrated in FIG. 12. Specting UI 3032 may also include other broadcast content 3037 as described in this application, for example UI elements for acquiring, joining or stepping in games as illustrated in FIG. 14. . The broadcast content for the individual broadcasts for which this heat map was generated can be broadcast over one broadcast 3034 by one or more overlays 3037, for example by the spectating system illustrated in Figures 1A and 27 or Figure 1B. It may also include text or banner advertisements added to the broadcast stream by the broadcast content service illustrated in.

A heat map showing spectater activity on interface 3002 as illustrated by the shaded areas is overlaid on specting interface 3002. The heat map may indicate activity during a brocast or part of a broadcast, or during two or more broadcasts. Although shown in grayscale, darker shading represents areas of more activity, and in practice shading can be done in color, eg "hotter" colors representing more activity. have. For example, one, two, or more broadcasts, as determined by analysis of the specting data 2834 illustrated in FIG. 28, during the broadcast or part of the broadcast or during two or more broadcasts. The shaded areas that tend to interact with or focus on the spectacle interaction data 2794 collected for the fields correspond to the content or areas of the specting interface 3002. Spectating interfaces 3002 and Spectator interactions that are analyzed and tracked to create a heat map can be selected on UI elements, UI element manipulation (e.g., by scrolling, clicking, sliding, turning, etc.) on the UI elements or Hovering nearby (e.g., with a cursor), typing in a UI element (e.g., entering text in a text box), and focusing (e.g., on one or more UI elements) (Detected through eye tracking technology).

Heat maps, for example, tend not to be purchased by specters but tend to focus on them (e.g. items 2 and 3), or more often than other items (e.g. item 1). Items in sales interface 3040 may be displayed. As another example, the heat map may display games 3052, broadcasters 3062, and/or videos 3082 that tend to generate more or less activity. The heat map can also indicate areas within broadcast 3034 that tend to generate more activity. Consumers can use this information to evaluate the layout including, for example, but not limited to, the specting interface 3002 content and products, product placement, advertisements, and the like. As non-limiting examples, broadcasters can use a heat map to evaluate the content they select to place on their channels, and game developers and/or online merchants bending through the specting interface 3002. Heat maps can be used to evaluate the game-related content and products.

30 shows a static heat map, but in some embodiments the heat map can be dynamic; Recorded Spectator interactions can be played again, and the heat map can change to reflect changes in focus. In addition, the spectatation data from which the heat map was generated can be temporarily correlated with the A/V content for the broadcast(s), and the A/V content can be played back to the heat map display , Which, for example, may allow the consumer to see and hear what happened during periods of high and/or low activity during broadcast(s).

31 is a game specting data consumer interface 3102 provided to a consumer 3160's device 3100 showing game specting metrics correlated with broadcast A/V content in accordance with some embodiments ) Is a non-limiting example. Specting data controls 3140 may include, for example, various UI elements that allow consumer 3160 to control the display and content of interface 3102, such as the consumer (as illustrated in FIG. 28). 3160) includes UI elements that allow the querying of the specting data module or service. The metric graph panes 3110A and 3110B individually, plot plots of speculating metrics A and B over time. Specting metrics A and B can be any of a variety of metrics determined from specting data 2834 as illustrated in FIG. 28. As non-limiting examples, metric A may indicate the audience size, and metric B may indicate the audience excitement or activity metric plotted against time. Spike 3111 marks the high point in the metrics plotted at (3110A and 3110B). Specting data metrics 3116 are one or more metrics determined from specting data 2834 obtained from a specting data repository through a specting data module or service as illustrated in FIG. 28 (this example In, values for X, Y, and Z) can be displayed as characters. Pane 3112 may replay video from a broadcast that is plotted at 3110A and 3110B and corresponding to the metrics shown in specting data metrics 3116. The broadcast text chat 3118 can replay the text chat from the broadcast displayed in the pane 3112. In addition, broadcast audio corresponding to the broadcast may be replayed through speaker(s) 3104. Some or all of the data or information provided visually or audibly through the data or information elements 3110A and 3110B, 3112, 3118, 3116, and 3104 is provided by the consumer 3160 during the broadcast 3112 and/or Or it can be temporarily correlated to hear and see what happened at a particular moment in broadcast 3112, such as spike 3111. For example, the consumer 3160 correlates certain events in broadcast A/V content with audience activities, spectacle interactions and inputs, spectating statistics, and other information from spectating data. For example, you can use this example interface.

Example network-based game Specting Environments

32 illustrates an example network-based game and game specting environment according to some embodiments. Embodiments of game systems, game specting systems, and other systems and services in the game specting environments described in this application with reference to drawings 1a-29 are illustrated in, for example, FIG. 32. Providing virtualized resources (eg, virtualized computing resources, virtualized storage resources, virtualized database (DB) resources, etc.) on the provider network 4190 to clients of the service provider as described It can be implemented in the context of a service provider. Virtualized resource instances can be provisioned through one or more provider network services 4192 and game systems 4100 in the service provider's classes, such as through the provider network 4190 and services 4192. ) Or may be leased or leased to developers 4170 clients that provide and develop other systems or services.

In at least some embodiments, one or more developers 4170 program applications to services 4192 to configure game system 4100 and/or game specting service 4130 on provider network 4190. One or more services 4192 of provider network 4190 may be accessed through interfaces (APIs). Game system 4100 or game speculating service 4130 may include multiple virtualized resource instances (eg, computing resources, storage resources, DB resources, etc.).

At least some of the resource instances (eg, computing resources) on the provider network 4190 are attached to hardware virtualization technologies, ie virtual machines (VMs) on the host, that allow multiple operating systems to operate simultaneously on the host computer. It can be implemented accordingly. The provider network 4190 through the services 4192 may enable provisioning of logically isolated sections of the provider network 4190 to specific clients as client private networks on the provider network 4190. have. At least some of the client's resources instances on the provider network 4190 may be provisioned into the client's private network. For example, in FIG. 32, one or more game systems 4100 are on private networks of individual developers 4170 that are provisioned on provider network 4190 or through one or more of services 4192 or network. Field. As another example, game specting service 4130 may be provisioned to private networks on provider network 4190 through one or more of services 4192.

Through the services 4192, the provider network 4190 can be automatically added to or removed from the configuration on the provider network 4190 in response to changes in demand or usage of virtualized resource instances, and thus It can provide clients with flexible provisioning of resource instances that enables automatic scaling of the client's implementation on the provider network 4190 to handle manipulation and/or storage needs. For example, one or more additional computing and/or storage resources may automatically play game, broadcast, and/or game spectacle from player/broadcaster devices 4120 and/or spectacle devices 4180. It may be automatically added to the game system 4100 and/or to the game specting service 4130 in response to an increase in the ting. Conversely, when the usage drops below the threshold and when it falls, resources may be removed from the game system 4100 and/or game speculating service 4130.

Illustrative system

In at least some embodiments, a computing device implementing some or all of the methods and apparatus for integrating a game speculating system and a game system in a game specting environment described herein is a computer illustrated in FIG. 33. It may include one or more computer-accessible media such as system 4300 or a general purpose computer system configured to access media. In the illustrated embodiment, computer system 4300 includes one or more processors 4310 coupled to system memory 4320 via input/output (I/O) interface 4330. Computer system 4300 further includes a network interface 4340 coupled to I/O interface 4330.

In various embodiments, computer system 4300 includes a uniprocessor system including one processor 4310, or several processors 4310 (eg, two, four, eight, or other suitable number). It can be a multiprocessor system including. Processors 4310 may be any suitable processor capable of executing instructions. For example, in various embodiments, processors 4310 implement any of a variety of instruction set architectures (ISAs), such as x86, PowerPC, SPARC, or MIPS ISAs, or any other suitable ISA. It may be one general purpose or embedded processors. In multiprocessor systems, each of the processors 4310 may, in general, but not necessarily, implement the same ISA.

System memory 4320 may be configured to store instructions and data accessible by processor(s) 4310. In various embodiments, system memory 4320 is any suitable memory technology, such as static random access memory (SRAM), synchronous dynamic RAM (SDRAM), non-volatile/flash-type memory, or any other type of memory. Can be implemented using In the illustrated embodiment, program instructions embodying one or more desired functions, such as the methods, techniques and data described herein to integrate the game speculating system and game systems in a game specting environment. And data is shown stored in system memory 4320 as code 4325 and data 4326.

In one embodiment, I/O interface 4330 is a device 4300 that includes a processor 4310, system memory 4320 and network interface 4340, input/output (I/O) devices, or other peripheral interfaces. ) Can be configured to coordinate I/O traffic between any peripheral devices. In some embodiments, the I/O interface 4330 signals data in a format suitable for use by another component (eg, processor 4310) in one component (eg, system memory 4320). Any necessary protocol, timing or other data conversions can be performed to convert them. In some embodiments, I/O interface 4330 is connected via various types of peripheral buses, such as, for example, a variation of peripheral component interconnect (PCI) bus standard or Universal Serial Bus (USB) standard. Support for devices. In some embodiments, I/O interface 4330 is one or more input/output peripheral devices or components 4370 of system 4300, such as cursor control, keyboard, display, video, and/or audio I/ O devices 4370 or components, and/or input devices such as controllers or joysticks, motion tracking systems, and gesture-based input systems. In some embodiments, the functionality of the I/O interface 4330 can be separated into two or more distinct components, such as, for example, the North Bridge and South Bridge. Also, in some embodiments, some or all of the functions of I/O interface 4330, such as an interface to system memory 4320, may be directly integrated into at least one processor 4310.

The network interface 4340 is a computer system 4300 and other devices connected to a network or networks 4350, such as, for example, other computer systems or devices as illustrated in FIGS. 1A-30. 4360). In various embodiments, network interface 4340 can support communication over any suitable wired or wireless general data networks, such as, for example, types of Ethernet networks. Additionally, the network interface 4340 may be through storage area networks, such as Fiber Channel SANs, or through any other suitable type of network and/or protocol, such as analog voice networks or digital fiber communications networks. Communication can be supported through telecommunications/telephone networks.

In some embodiments, system memory 4320 is described above with respect to FIGS. 1A-30 to implement embodiments of methods and apparatus for integrating game specting systems and game systems in a game specting environment. It can be an embodiment of a computer-accessible medium configured to store program instructions and data as described. However, in other embodiments, program instructions and/or data may be received, transmitted, or stored on different types of computer-accessible media. Generally speaking, computer-accessible media is magnetic or optical media, such as disks or memory media or non-transitory storage media such as DVDs/CDs coupled to computer system 4300 via I/O interface 4330. It may include. Non-transitory computer-accessible storage media may also be included in some embodiments of computing device 4300 as system memory 4320 or other type of memory, such as RAM (eg, SDRAM, DDR SDRAM, RDRAM, SRAM) Etc., ROM, and the like, any volatile or non-volatile media. In addition, the computer-accessible medium can be implemented through a network interface 4340, transmission media, such as electrical, electromagnetic or digital signals, transmitted through a communication medium, such as a network and/or wireless link, or Signals.

The preceding can be better understood by considering the following series of items:

1. The system,

A one or more computing devices configured to implement a specting system, the specting system comprising:

Broadcast a video received from a broadcaster device to a plurality of spectator devices, the video including gameplay of individual broadcasters participating as a player in a game running on a game system;

The game metadata for the game is obtained from the game system according to an application programming interface (API) of the specting system, and the game metadata includes game states for the game, game event data for the game, And one or more of player inputs to the game, or data describing or representing game content;

Generate broadcast content at least partially according to the game metadata;

Providing at least a portion of the broadcast content to the plurality of spectator devices according to a specting user interface (UI);

Acquiring spectator interactions with the broadcast content according to the specting UI; And

Configured to provide indications of at least some of the spectacle interactions to the game system according to the API.

2. In the system listed in item 1, the game state is a point-in-time of game data and game information representing a particular game at a particular point on the game timeline in the game universe. ) Is a record.

3. In the system listed in item 1, the game event data includes game event records indicating notable events in the game determined by the game system.

4. In the system listed in item 1, the game content includes one or more of objects, items, or characters in the game.

5. In the system listed in item 1, player input indicates command or action input for the game by an individual player through a game client or game controller.

6. For the systems listed in item 1, the spectate system comprises:

Acquire speculating preferences for a plurality of specators associated with the plurality of specator devices according to the speculating UI; And

It is further configured to determine the broadcast content targeted to a specific spectater among the plurality of spectators according to individual spectating preferences of the spectators.

7. For the systems listed in item 1, the spectate system comprises:

Acquiring spectater inputs from a plurality of spectators associated with the plurality of spectator devices according to the spectating UI, wherein the spectator inputs include one or more of an audio chat or a text chat;

Generate one or more game inputs according to the analysis of the spectator inputs; And

It is further configured to provide the one or more game inputs to the game system according to the API, wherein the game inputs affect the execution of the game on the game system.

8. In the system enumerated in item 1, the broadcast content is displayed on a game video received from the broadcaster device or UI elements provided to the plurality of spector devices for display according to the speculating UI. It includes one or more of the content overlaid (overlaid).

9. In the method,

By a specting system implemented on one or more computing devices:

Streaming one or more broadcasts received from one or more broadcaster devices to a plurality of spectacle devices, each broadcast being a game of an individual broadcaster participating as an in-game player running on a game system. Streaming, showing play;

Generating content for the broadcasts according to game metadata for the game received at least partially according to an application programming interface (API) of the specting system; And

And providing indications of the broadcast content and spectacle interactions to the game system according to the API.

10. The method of item 9, wherein the game metadata includes metadata received from one or more of the game system, the one or more broadcaster devices, a game developer system, or a third party system.

11. The method of item 9, further comprising receiving the one or more broadcasts from the broadcast devices as broadcast streams, wherein at least a portion of the game metadata is included with the broadcast streams. Is received.

12. The method listed in item 9,

Obtaining, by the game system, indications of the broadcast content and spectacle interactions according to the API; And

And influencing the execution of the game on the game system according to the broadcast content and the displayed spectacle interactions.

13. The method according to item 12, among the effects of the broadcast content and the indicated spectacle interactions upon execution of the game to the plurality of spectacle devices via the one or more broadcasts. Further comprising providing one or more indications, wherein the one or more indications include one or both of visual indications or audio indications.

14. The method listed in item 9,

Providing at least a portion of the broadcast content to the plurality of spectator devices according to a specting user interface (UI); And

The method further includes obtaining the broadcast content and specator interactions according to the specting UI.

15. The method according to item 9, wherein the broadcast content includes one or more overlays on the game video received from the one or more broadcaster devices.

16. In the method listed in item 9, the broadcast content includes one or more user interface (UI) elements provided to the plurality of specator devices for display in accordance with the speculating UI.

17. The method as recited in item 9, wherein the game metadata is among game states for the game, game event data for the game, player inputs to the game, or data describing or representing game content. It contains one or more.

18. In the method enumerated in item 17, the game state is a point-in-time of game data and game information representing a particular game at a particular point on the game timeline in the game universe. ) Is a record.

19. The method recited in item 17, wherein the game event data includes game event records that indicate notable events in the game determined by the game system.

20. The method recited in item 17, wherein the game content includes one or more of objects, items, or characters in the game.

21. In the method listed in item 17, player input indicates command or action input for the game by an individual player through a game client or game controller.

22. The method listed in item 9,

Acquiring spectacle inputs from the plurality of spectator devices, wherein the spectacle inputs include one or more of audio inputs or text inputs from specters associated with the spectator devices; To do;

Analyzing the specator inputs to determine one or more game inputs; And

And providing the one or more game inputs to the game system according to the API, wherein the game inputs affect the execution of the game on the game system.

23. The method of item 22, wherein the specator inputs are inputs to one or more of controller devices, joysticks devices, motion tracking input devices, or gesture-based input devices of the specator devices. It includes more.

24. In the method listed in item 9, at least some of the at least some of the game metadata is provided by the gaming system in response to requests from the specting system according to the specting system API.

25. In a non-transitory computer-readable storage medium storing program instructions, one or more computing devices when the program instructions are executed on one or more computers:

Obtain one or more broadcasts from one or more broadcaster devices, each broadcast showing the gameplay of the individual broadcaster participating as a player in a game running on the game system;

The game metadata for the game is obtained from the game system according to an application programming interface (API) of the specting system, and the game metadata includes game states for the game, game event data for the game, And one or more of player inputs to the game, or data describing or representing game content;

Generate broadcast content for the one or more broadcasts based at least in part on the game metadata received from the game system;

Streaming the one or more broadcasts and the broadcast content to a plurality of spectator devices;

Acquire spectater interactions with the broadcast content from the plurality of spectator devices; And

It is to implement a broadcast content module for a specting system configured to provide indications of at least some of the spectacle interactions to the game system according to the specting system API.

26. In the non-transitory computer-accessible storage medium listed in item 25, the broadcast content is user interface (UI) elements provided to the plurality of specator devices for display according to the speculating UI. Or one or more content overlaid on the game video received in the broadcasts from the one or more broadcaster devices.

The preceding can be further understood by considering the following series of items:

1. The system,

A one or more computing devices configured to implement a specting system, the specting system comprising:

Broadcast a video received from a broadcaster device to a plurality of spectator devices, the video including gameplay of individual broadcasters participating as a player in a game running on a game system;

Create broadcast content according to game metadata for the game at least partially obtained from the game system, wherein the game metadata includes data describing or indicating game content, and the broadcast content is individually And user interface (UI) elements for obtaining objects corresponding to the game content;

Providing the broadcast content to the plurality of spectator devices according to the specting UI;

Acquires the broadcast content and spectator interactions according to the specting UI, and the spector interactions include inputs to the UI elements representing requests for individual objects; And

It is configured to generate one or more orders for objects corresponding to the game content in response to the requests.

2. In the system listed in item 1, at least a portion of the game metadata is obtained from the game system according to the application programming interface (API) of the specting system.

3. In the system listed in item 1, the game content includes one or more of in-game items or characters, and the objects are virtual objects or physical objects corresponding to individual game content. It contains one or more of.

4. In the system enumerated in item 1, the objects include virtual objects configured for use in the game, and the spectating system comprises the virtual objects in individual ones of the plurality of specator devices. It is further configured to send at least some of them.

5. In the system listed in item 4, at least one of the plurality of spectator devices includes a game client, and at least one virtual object is downloaded to the game client on a separate spectator device.

6. In the system listed in item 1, the objects include physical objects that model individual game content.

7. In the system listed in item 1, the broadcast content further comprises one or more of descriptions, images, or videos of the game content.

8. In the system enumerated in item 1, the broadcast content further includes one or more of historical information or statistics on in-game use of the game content.

9. In the system listed in item 1, the specting system simultaneously streams a plurality of broadcasts on a plurality of broadcast channels, each broadcast channel corresponding to one of the plurality of broadcasters , The spectate system is:

Obtain broadcast specifications from the broadcaster device, the specifications including indications of specific game content to be provided through the broadcast channel of the individual broadcaster; And

And configured to determine at least a portion of the broadcast content to be provided to the plurality of spectator devices according to the broadcast specifications.

10. In the method,

By a specting system implemented on one or more computing devices:

Streaming one or more broadcasts received from one or more broadcaster devices to a plurality of spectacle devices, each broadcast being a game of an individual broadcaster participating as an in-game player running on a game system. Streaming, showing play;

Generating broadcast content for the broadcasts based at least in part on game metadata describing or representing the game content;

Obtaining indications of the broadcast content and specator interactions, including interactions representing requests for objects corresponding to game content represented by the broadcast content; And

And performing a step of enabling ordering or delivery of the requested objects in response to the requests.

11. The method as recited in item 10, wherein the requests to the objects include purchases of one or more objects, and the step of enabling the ordering or delivery of the requested objects comprises purchasing orders for the requested objects. And generating.

12. The method according to item 10, wherein requests for the objects are made to one or more of the specting devices, the game system, the one or more broadcaster devices, a game developer system, or a third party system. And providing feedback indicating.

13. The method of item 10, further comprising obtaining, by the spectating system, at least a portion of the game metadata from the game system according to an application programming interface (API).

14. In the method enumerated in item 10, the broadcast content includes one or more user interface (UI) elements provided to the plurality of specator devices for display according to the speculating UI.

15. The method of item 14, wherein the UI elements include at least one UI element for requesting additional information about a specific game content from the broadcaster, and selecting the at least one UI element is the Messages to individual broadcaster devices with requests for additional information about specific game content.

16. The method of item 10, wherein the broadcast content includes one or more overlays on the game video received from the one or more broadcaster devices.

17. The method of item 10, wherein the game content includes one or more of in-game items or characters, and the objects are virtual objects or physical objects corresponding to individual game content. It contains one or more of.

18. The method of item 10, wherein the objects include virtual objects configured for use in the game, the method comprising at least one of the virtual objects on individual ones of the plurality of specator devices. The method further includes sending a part.

19. The method according to item 18, wherein at least one of the spectator devices comprises a game client to participate in the game, and the virtual objects are downloaded to the game client on the individual spectator device.

20. In the method listed in item 10, the objects include physical objects that model individual game content.

21. The method of item 10, wherein the broadcast content further includes one or more of descriptions, images, or videos of the game content.

22. In the method listed in item 10, the broadcast content further includes one or more of historical information or statistics on in-game use of the game content.

23. The method according to item 10, wherein the specting system simultaneously streams a plurality of broadcasts on a plurality of broadcast channels, and each broadcast channel corresponds to one of the plurality of broadcasters. And the above method:

Acquiring broadcast specifications for at least one of the broadcaster channels, wherein the broadcast specifications include indications of specific game content to be provided through the broadcast channel; And

And determining at least a portion of the broadcast content to be provided to the plurality of spectator devices according to the broadcast specifications.

24. In a non-transitory computer-readable storage medium storing program instructions, causing one or more computing devices when the program instructions are executed on one or more computers:

Generates broadcast content for a broadcast received from a broadcaster device, the broadcast showing gameplay of an individual broadcaster participating as a player in a game running on a gaming system, the broadcast content being at least partially It is generated according to game metadata received from the game system according to an application programming interface (API), and the game metadata includes data describing or representing game content;

Providing the broadcast content to a plurality of spectator devices according to a speculating user interface (UI), the broadcast content including UI elements for obtaining objects corresponding to individual game content; And

Acquiring the broadcast content and spectacle interactions according to the specting UI, and the spectacle interactions include inputs to the specting UI representing requests for individual objects; And

In response to the requests, it is possible to implement a storefront for a specting system configured to enable the creation of one or more orders for objects corresponding to the game content.

25. The non-transitory computer-accessible storage medium listed in item 24, wherein the broadcast content is:

One or more of the descriptions, images, or videos of the game content; And

The game content further includes one or more of historical information or statistics on the in-game use.

The preceding can be further understood by considering the following series of items:

1. The system,

A one or more computing devices configured to implement a specting system, the specting system comprising:

Broadcast a video received from a broadcaster device to a plurality of spectator devices, the video including gameplay of individual broadcasters participating as a player in a game running on a game system;

Acquire spectater inputs from the plurality of spectator devices;

Analyze the spectater inputs to generate spectating data for the broadcast;

Generate values for one or more game inputs according to the speculating data; And

It is configured to expose the one or more game inputs to the game system according to the application programming interface (API) of the specting system.

2. For the systems listed in item 1, the spectate system comprises:

Repeatedly performing the acquisition, the analysis, the generation and the exposure during the broadcast;

Detect changes to the spectacle inputs during the iterative and performing the analysis repeatedly; And

And change the value of at least one of the one or more game inputs in response to the detection.

3. In the system listed in item 1, the game inputs are among parametric inputs that provide an entropy source for the in-game rendering functions and values for the game or rendering inputs. Includes one or both.

4. In the system listed in item 1, the spectacle inputs include spectatation statistics based on participation in the broadcaster spectacle.

5. In the system listed in item 1, the specator inputs include one or both of audio inputs or text inputs for a plurality of spectors associated with the plurality of specator devices.

6. In the system listed in item 1, the specator inputs include specator interactions with one or more user interface (UI) elements of the specting UI on the plurality of specator devices.

7. In the method,

By a specting system implemented on one or more computing devices:

Streaming one or more broadcasts received from one or more broadcaster devices to a plurality of spectacle devices, each broadcast being a game of an individual broadcaster participating as an in-game player running on a game system. Streaming, showing play;

Obtaining spectacle inputs from the plurality of spectator devices;

Analyzing the spectacle inputs to generate spectaty data for the game;

And exposing the specting data to the game system according to an application programming interface (API) of the specting system.

8. In the method listed in item 7,

Acquiring, by the game system, the specting data according to the API;

Generating values for one or more game inputs according to the acquired spectating data by the game system; And

And further affecting the execution of the game on the game system according to the generated values.

9. In the method listed in item 7, the step of exposing the specting data to the game system according to the API of the specting system is:

Generating values for one or more game inputs according to the specting data; And

And exposing the one or more game inputs to the game system according to the API of the specting system.

10. The method of item 9, wherein exposing the one or more game inputs to the game system according to the API of the specting system comprises: the one or more games to a game server of the game system according to the API. Providing inputs, wherein the game server is configured to distribute the one or more game inputs to one or more game engine instances of the game system.

11. In the method listed in item 9,

Obtaining, by the game system, a value for at least one of the one or more game inputs according to the API; And

And influencing the execution of the game on the game system according to the obtained values.

12. The method as recited in item 11, the method comprising providing to the plurality of spectator devices via the one or more broadcasts one or more indications of the effect of the acquired value upon execution of the game. Further included, the one or more indications include one or both of visual indications or audio indications.

13. The method of item 9, wherein the game inputs include one or more parametric inputs that provide values for the in-game parameters based on the specator inputs, and the generated values are specific games. Contains the values for the parameters.

14. The method of item 9, wherein the game inputs include one or more rendering inputs that provide an entropy source for rendering one or more aspects of the game, and the generated values are the spectrometer inputs. Contains a random value based on.

15. In the method enumerated in item 7, the spectacle inputs include spectatation statistics based on participation in the spectator in the broadcast.

16. In the method listed in item 15, the spectators are segmented into two or more groups, and the spectator statistics include statistical data indicating the percentage of specters who are in each of the two or more groups. do.

17. In the method listed in item 16, the two or more groups include subscribers and non-subscribers for the specting system.

18. The method as recited in item 7, wherein the specator inputs include one or both of audio inputs or text inputs for a plurality of spectors associated with the plurality of specator devices.

19. The method as recited in item 7, wherein the specator inputs include inputs to one or more of controller devices, joysticks devices, motion tracking input devices, or gesture-based input devices.

20. The method listed in item 7, wherein the spectacle inputs include text inputs from one or more social media channels.

21. The method as recited in item 7, wherein the specator inputs include audio inputs for a plurality of spectors associated with the plurality of specator devices, and to generate speculating data for the game. Analyzing the specator inputs includes analyzing the audio inputs to generate audio analysis data for the one or more broadcasts.

22. The method of item 7, wherein the specator inputs include text chat inputs for a plurality of spectors associated with the plurality of specator devices, and generating specting data for the game. Analyzing the spectator inputs in order to include analyzing the text chat to generate chat analysis data for the one or more broadcasts.

23. The method as recited in item 7, wherein the specator inputs include specator interactions with one or more user interface (UI) elements of the specting UI on the plurality of specator devices.

24. The method recited in item 23, wherein the spectacle interactions include the interaction of the one or more UI elements and a plurality of spectators by selecting content or events for the game, and a spec for the game. Analyzing the spectacle inputs to generate tating data includes determining specific content or events for the game according to the selections of the plurality of spectators.

25. In a non-transitory computer-readable storage medium storing program instructions, causing one or more computing devices when the program instructions are executed on one or more computers:

Acquiring specator inputs for a plurality of speculators watching one or more broadcasts from a specter system on individual client devices, each broadcast of an individual broadcaster participating as a player in a game session of an online game. Show gameplay;

Analyze the spectacle inputs to generate spectacle data for the game;

Generate values for one or more game inputs according to the speculating data; And

It is configured to provide the one or more game inputs to the game system according to an application programming interface (API) of the specting system to implement a game effect module for the specting system.

26. For the non-transitory computer-accessible storage medium listed in item 25, the game inputs provide an entropy source for the in-game rendering functions and a value for the game or rendering inputs. This includes one or both of the parametric inputs that provide them.

27. The non-transitory computer-accessible storage medium listed in item 25, wherein the specator inputs are specter participation in the broadcasts, audio chat inputs for the plurality of specators, the plurality of specs. Text chat inputs to data, or one or more of the specting statistics based on specter interactions with one or more user interface (UI) elements of the specting UI on the plurality of client devices. Includes.

The preceding can be further understood by considering the following series of items:

1. The system,

A one or more computing devices configured to implement a specting system, the specting system comprising:

Obtain one or more broadcasts from one or more broadcaster devices, each broadcast showing the gameplay of the individual broadcaster participating as a player in a game running on the game system;

Generate broadcast content for the one or more broadcasts based at least in part on metadata for the game received from the game system;

Streaming the one or more broadcasts and the broadcast content to a plurality of spectator devices;

Recording audiovisual (A/V) content for the broadcasts;

Acquire and store broadcast content and spectroscopic interactions with the broadcasts as speculating data;

Determine and store correlations between the speculating data and the A/V content; And

It is configured to expose the speculating data and the A/V content to one or more speculating data consumer devices according to the speculating data interface.

2. In the system listed in item 1, the specting system is further configured to store at least a portion of the game metadata for the broadcasts as specting data, wherein the game metadata is stored in the game. Game state, game event data for the game, or data describing or representing game content.

3. In the system enumerated in item 1, the broadcast content is UI elements provided to the plurality of spectator devices for display according to the specting UI or game video received from the broadcaster devices. It includes one or more of the content overlaid on, and the Spectator interactions with the broadcast content indicate the individual broadcast content's choices or specator interest.

4. In the system listed in item 1, the broadcast content includes user interface (UI) elements for viewing and purchasing virtual or physical objects including objects related to the game, and the spectacle interactions Includes interactions with the UI elements that represent individual object purchases or specator interest.

5. In the system listed in item 1, the A/V content for the broadcast includes one or more of broadcast video, broadcast audio, or broadcast text chat.

6. For the systems listed in item 1, the spectate system comprises:

Receive an indication of specific speculating data from a consumer device according to the speculating data interface;

Determine a portion of the A/V content correlated to the specific speculating data; And

And configured to provide a correlated portion of the A/V content to the consumer device according to the specting data interface.

7. In the system listed in item 1, the specting data interface includes one or more of an application programming interface (API) user interface (UI), or a query interface.

8. In the method,

By a specting system implemented on one or more computing devices:

Streaming one or more broadcasts received from one or more broadcaster devices to a plurality of spectacle devices, each broadcast being a game of an individual broadcaster participating as an in-game player running on a game system. Streaming, including play;

Providing broadcast content to the spectator devices together with the broadcasts, wherein the broadcast content is determined, at least in part, according to metadata for the game received from the game system; ;

Acquiring and recording individual broadcast content and spectacle interactions with the broadcasts as speculating data; And

And exposing the speculating data to one or more speculating data consumers according to the speculating data interface.

9. In the method listed in item 8,

Recording audiovisual (A/V) content for the broadcasts; And

And determining and storing correlations between the speculating data and the A/V content.

10. The method of item 9, wherein the A/V content for the broadcast includes one or more of broadcast video, broadcast audio, or broadcast text chat.

11. In the method listed in item 8,

Recording audiovisual (A/V) content for the broadcasts;

Receiving an indication of specific speculating data from a consumer device according to the speculating data interface;

Determining a portion of the A/V content correlated to the specific speculating data; And

And providing a correlated portion of the A/V content to the consumer device according to the specting data interface.

12. The method according to item 8, further comprising storing at least a portion of the game metadata for the broadcasts as speculating data, wherein the game metadata includes game states for the game. , Game event data for the game, or data describing or representing game content.

13. The method listed in item 8,

Determining speculating statistical data for the one or more broadcasts based on participation in a spectator in the broadcasts; And

Further comprising the step of storing the speculating statistical data as speculating data.

14. The method according to item 8, wherein the broadcast content is UI elements provided to the plurality of spectator devices for display according to the specting UI or game video received from the broadcaster devices. Include one or more of the content overlaid on, and the Spectator interactions with the broadcast content indicate the individual broadcast content's choices or specator interest.

15. The method of item 8, wherein the broadcast content includes user interface (UI) elements for viewing and purchasing virtual or physical objects including objects related to the game, and the spectacle interactions Includes interactions with the UI elements that represent the purchase or spectator interest of individual objects.

16. The method listed in item 8,

Analyzing the speculating data to determine speculating information for at least one of the broadcasts; And

And providing the speculating information to at least one of the speculating data consumers according to the speculating data interface.

17. The method as recited in item 16, wherein the speculating information is based on individual broadcast content and the broadcast and the specator interactions, and the specator interests in the broadcast and individual broadcast content. It includes a heat map (heat map) for indicating.

18, the method recited in item 8, wherein the specting data consumers include one or more of game developers, broadcasters, or online merchants.

19. The method listed in item 8, wherein the specting data interface comprises one or more of an application programming interface (API), a user interface (UI), or a query interface.

20. In the method listed in item 8, the step of acquiring and recording broadcast content and the broadcasts and specter interactions comprises the specting user interface of the specting system on the individual spector devices ( UI) and interactions.

21. The method as recited in item 20, wherein the specting UI is a web page provided on a web browser, and obtaining and recording the broadcasts and broadcast content and specator interactions is the specting Further comprising tracking the spectator navigation from the UI to one or more other web pages.

22. The method of item 20, wherein tracking and recording the speculating UI and interactions on at least one specator device comprises an eye motion or head motion for the specting UI. and tracking and recording one or both of the head motions.

23. In the method listed in item 8, the specting data includes a broadcast, a plurality of broadcasts, a game, or specific data for a plurality of games.

24. In a non-transitory computer-readable storage medium storing program instructions, causing one or more computing devices when the program instructions are executed on one or more computers:

Gameplaying of individual broadcasters participating as a player in a game running on a game system, storing spectating data, including a plurality of broadcasts and indications of individual broadcaster content and specator interactions, each broadcast And wherein the broadcast content is determined, at least in part, according to game metadata for the game received from the game system;

Store A/V content for the broadcast, and the A/V content for the broadcast includes one or more of broadcast video, broadcast audio, or broadcast text chat;

Expose the speculating data and the A/V content to one or more speculating data consumers according to the speculating data interface;

Receiving a request for specific speculating data from a specting data consumer according to the specting data interface;

Determine a portion of the A/V content correlated to the specific speculating data; And

According to the specting data interface, it is possible to implement a specting data service for a specting system configured to provide the consumer with the requested specting data and a correlated portion of the A/V content.

25. The non-transitory computer-accessible storage medium listed in item 24, wherein the specting data service is:

Analyzing the speculating data to determine specific speculating information for a broadcast, a plurality of broadcasts, a game, or a plurality of games; And

The speculating data interface is further configured to provide the speculating information to at least one of the speculating data consumers.

The preceding can be further understood by considering the following series of items:

1. The system,

A one or more computing devices configured to implement a specting system, the specting system comprising:

Streaming a broadcast received from a broadcaster device to one or more of a plurality of spectator devices, the broadcast showing gameplay of individual broadcasters participating as players in a game running on a game system;

Game event data for the game is obtained from the game system according to an API (application programming interface) of the specting system, and the game event data includes a notable event in the game included in the broadcast. Display;

Determine a reward for participating in the remarkable event;

One or more participants are determined for the remarkable event from the participation data for the broadcast, and the participation data indicates the one or more spectator devices to which the broadcast containing the remarkable event is streamed, and the participants are Include spectors associated with one or more spector devices; And

It is configured to provide access to rewards for participating in the remarkable event through a speculating user interface (UI) on the one or more spectacle devices associated with the one or more participants.

2. In the system listed in item 1, the broadcaster is a participant in the remarkable event, and the specting system is:

Determine broadcaster rewards for the remarkable event; And

And further configured to provide access to the broadcaster rewards via a broadcasting UI on the broadcaster device.

3. In the system listed in item 2, the broadcaster reward includes game content for the game, and the specting system is further configured to enable delivery of the game content to the broadcaster device.

4. In the system enumerated in item 1, the participation data includes spectating statistics based on participation in the broadcast, and the spectating system comprises:

Determining a broadcaster achievement based on the speculating statistical data for the broadcast; And

It is further configured to provide access to rewards for the broadcaster performance via a broadcasting UI on the broadcaster device.

5. In the system listed in item 1, the reward is a virtual object or a physical object corresponding to the in-game content.

6. In the system enumerated in item 1, the reward includes a virtual object configured for use in the game, and the spectating system includes the virtual objects in at least one of the one or more spectator devices. It is further configured to enable delivery.

7. The system as recited in item 1, wherein the spectating system is one of the rewards for participating in the remarkable event to the plurality of spectator devices and to the broadcaster devices via the one or more broadcasts. Further configured to provide the above indications, the one or more indications include one or both of visual indications or audio indications.

8. In the system listed in item 1, the specting UI includes one or more UI elements for specifying rewards for the selected participants and for selecting participants to be rewarded, wherein the specting system is :

Obtain specator inputs for the UI elements;

Determine one or more participants selected to be rewarded according to the spectacle inputs;

Determine one or more rewards for one or more selected participants according to the spectator inputs; And

It is further configured to provide access to the one or more rewards to the one or more selected participants through the specting UI.

9. In the system listed in item 1, the specting UI includes one or more UI elements for specifying rewards for the selected players and selecting players for the game running on the game system to be rewarded. And, the reward includes virtual objects configured for use in the game, and the specting system comprises:

Obtain specator inputs for the UI elements;

Determine one or more players selected to be rewarded according to the spectacle inputs;

Determine one or more virtual objects for one or more selected players according to the spectator inputs; And

And further configured to enable provisioning of the one or more virtual objects to one or more selected players in the game.

10. In the system listed in item 1, the reward is provided by the specting system, the game system, the broadcaster system, the game developer system, or a third party system.

11. In the system listed in item 1, the spectate system is further configured to pay a fee and provide the reward to the one or more participants.

12. In the method,

By a specting system implemented on one or more computing devices:

Streaming one or more broadcasts received from one or more broadcaster devices to a plurality of spectacle devices, each broadcast being a game of an individual broadcaster participating as an in-game player running on a game system. Streaming, showing play;

Determine a remarkable event in at least one of the one or more broadcasts based at least in part on game event data for the game received from the game system, the game event data indicating one or more events in the game;

Determining one or more participants for the remarkable event from participation data for the broadcast, wherein the participants are associated with one or more spectacle devices to which the at least one broadcast containing the remarkable event is streamed Comprising, determining; And

And providing a reward for participating in the remarkable event to the one or more spectator devices associated with the one or more spectators.

13. The method of item 12, further comprising receiving the game event data from the game system according to an application programming interface (API) of the specting system.

14. The method of item 12, wherein the one or more participants include at least one broadcaster in the remarkable event, and the method participates in the remarkable event in the broadcaster device of the at least one broadcaster. And providing a broadcaster reward for doing so.

15. The method of item 14, wherein the broadcaster reward includes game content for the game, and the method further comprises delivering the game content to the broadcaster device.

16. The method of item 12, wherein the participation data includes spectating statistics based on participation in the broadcast, the method comprising:

Determining a specific broadcaster performance based on the speculating statistical data for the broadcast; And

At least providing a reward or reward for the performance to the broadcaster device of the particular broadcaster.

17. In the method listed in item 12, the reward is a virtual object or a physical object corresponding to the in-game content.

18. The method of item 12, wherein the reward comprises a virtual object configured for use in the game, the method comprising delivering the virtual objects to at least one of the one or more spectacle devices. It further includes.

19. The method of item 12, further comprising providing one or more indications of the reward for participating in the remarkable event to the plurality of spectator devices via the one or more broadcasts, the one The above indications include either or both visual indications or audio indications.

20. In the method enumerated in item 19, the one or more indications include one or both of permanent indications or temporary indications.

21. The method of item 12, further comprising providing at least one of the one or more broadcaster devices one or more indications of the reward for participating in the remarkable event, wherein the one or more indications are visual One or both of the indications or audio indications.

22. The method listed in item 12,

Specifying one or more user interface (UI) elements for specifying rewards for the selected participants and selecting participants to be rewarded through a specting UI on the spectacle devices;

Obtaining spectator inputs for the UI elements;

Determining one or more participants selected to be rewarded according to the spectacle inputs;

Determining one or more rewards for one or more selected participants according to the spectator inputs; And

And providing the one or more rewards to the one or more selected participants.

23. The method listed in item 12,

Specifying rewards for the selected players via a specting UI on the spectacle devices and providing one or more user interface (UI) elements for selecting players to a game running on the game system to be rewarded ;

Obtaining spectator inputs for the UI elements;

Determining one or more players selected to be rewarded according to the spectator inputs;

Determining one or more virtual objects for one or more selected players according to the spectacle inputs; And

And enabling provisioning of the one or more virtual objects to one or more selected players in the game.

24. In the method listed in item 12,

Specifying one or more user interface (UI) elements for specifying rewards for the selected participants and selecting participants to be rewarded through a broadcasting UI on the broadcaster devices;

Obtaining broadcaster inputs for the UI elements;

Determining one or more participants selected to be rewarded according to the broadcaster inputs;

Determining one or more rewards for one or more selected participants according to the broadcaster inputs; And

And providing the one or more rewards to the one or more selected participants.

25. In the method listed in item 12, the reward is provided by the specting system, the game system, the broadcaster system, the game developer system, or a third party system.

26. In the method listed in item 12, the spectators are segmented into two or more groups, and the method determines different rewards for the specting system to participate in the remarkable event in the two or more groups. And further comprising the steps of providing.

27. In the method enumerated in item 25, the two or more groups include subscribers and non-subscribers for the specting system.

28. In a non-transitory computer-readable storage medium storing program instructions, causing one or more computing devices when the program instructions are executed on one or more computers:

Acquiring game event data for a game from a game system according to an API (application programming interface) of the specting system, the game event data being streamed to one or more of a plurality of spectator devices and received from a broadcaster device Includes an indication of a prominent event in the game included in the broadcast, the broadcast showing the gameplay of the individual broadcaster participating as a player in the game running on the game system;

Determine rewards to participate in the remarkable event;

One or more participants are determined for the remarkable event from the participation data for the broadcast, and the participation data indicates the one or more spectator devices on which the broadcast containing the remarkable event is streamed, and the participants are Include spectors associated with one or more spector devices; And

Participant reward modules for specting systems configured to provide rewards for participating in the remarkable event are provided to the one or more participants.

29. The non-transitory computer-accessible storage medium listed in item 28, wherein the one or more participants are rewarded for participating in the remarkable event, and the participant reward module is one associated with the one or more participants. It is configured to provide a user interface (UI) element for obtaining rewards to the above devices.

30. The non-transitory computer-accessible storage medium in item 28, wherein the broadcaster is a participant in the prominent event, and the participant reward module is:

Determine a broadcaster reward for the outstanding event, the broadcaster reward comprising a virtual object configured for use in the game; And

And further configured to enable delivery of the virtual object to the broadcaster device.

The preceding can be further understood by considering the following series of items:

1. The system,

A one or more computing devices configured to implement a specting system, the specting system comprising:

Broadcast a video received from a broadcaster device to a plurality of spectator devices, the video including gameplay of individual broadcasters participating as a player in a game running on a game system;

Generate broadcast content according to the game metadata for the game at least partially obtained from the game system;

Providing the broadcast content to the plurality of spectator devices according to a specting user interface (UI), the broadcast content including UI elements for acquiring or joining the game;

Acquire specter interactions with the broadcast content according to the specting UI, and the spectacle interactions receive inputs to the UI elements representing requests to acquire or join the game. Contains; And

It is configured to enable provisioning of one or both of the game client or game state to individual spectacle devices in response to the requests, wherein the provisioning configures the individual spectacle devices for participation in the game.

2. In the system listed in item 1, at least a portion of the game metadata is obtained from the game system according to an application programming interface (API) of the specting system.

3. In the system enumerated in item 1, in response to the requests, provisioning of one or both of the game client or game state to individual spectator devices is possible, and the specting system is the specification. The input system is further configured to generate inputs to the game system according to an application programming interface (API) of the tasting system, and the inputs may download the game client or one or both of the game states to the individual spectacle devices. request.

4. In the system listed in item 1, the game state is a point-in-time of game data and game information representing a particular game at a particular point on the game timeline in the game universe. time) record, and the game client on the spectator device is configured to start or resume game play on the game at the individual point in the game timeline in the game universe according to the game state.

5. In the system listed in item 1, the game metadata includes data describing or indicating in-game virtual content, and the broadcast content further includes UI elements for obtaining the in-game content, The spectating system is further configured to enable provisioning of individual game content to individual spectator devices in response to the UI elements and spectator interactions for obtaining the in-game content.

6. In the system listed in item 5, the in-game virtual content includes one or both of the game gear and game characters for the game characters.

7. The system as recited in item 1, which enables provisioning of one or both of the game client or game state to individual spectator devices, wherein the spectating system comprises, for at least one spectator device: The game stream and the game streaming interface are further configured to initiate a game stream with a game streaming interface on a spectator device, and the game stream and game streaming interface allow trial participation in the game running on the game system from the individual spectator device.

8. In the system enumerated in item 7, the game stream includes the download of one or both of the game client or the game state to the individual spectator device.

9. The system as recited in item 8, wherein the specting system authenticates the game client on the individual specator device in response to receiving input for a UI element on the specator device indicating the purchase of the game. Further configured to enable enabling, the game client enabling allows full participation in the game running on the game system from the individual spectator device.

10. The method recited in item 7, wherein the game stream includes downloading in-game virtual content to the individual spectator device.

11. In the method,

By a specting system implemented on one or more computing devices:

Streaming one or more broadcasts received from one or more broadcaster devices to a plurality of spectacle devices, each broadcast being a game of an individual broadcaster participating as an in-game player running on a game system. Streaming, showing play;

Generating broadcast content for the broadcasts based at least in part on game metadata;

Obtaining indications of the broadcast content and spectacle interactions including interactions representing requests to join the game; And

And enabling provisioning of one or both of the game client or game state to individual spectator devices in response to the requests, wherein the provisioning enables participation in the game from the individual spectator device. , Performing the step of enabling the above.

12. The method of item 11, further comprising obtaining, by the specting system, at least a portion of the game metadata from the game system according to an application programming interface (API) of the specting system. Includes.

13. The method of item 11, wherein the broadcast content includes one or more user interface (UI) elements provided to the plurality of specator devices for display according to the speculating UI.

14. The method as recited in item 11, the step of enabling provisioning of one or both of the game client or game state to individual spectacle devices is the game according to the application programming interface (API) of the specting system. Further comprising generating inputs to the system, the inputs requesting download of one or both of the game client or the game state to the individual spectacle devices.

15. The method according to item 11, wherein the game state is a point-in-time of game data and game information representing the game at a particular point on the game timeline in the game universe. time) records.

16. The method as recited in item 15, wherein provisioning comprises downloading the game state to one or more of the spectator devices, the method being the game time in the game universe according to the downloaded game state Further comprising initiating gameplay on a game client running on the one or more spectator devices at the individual point in line.

17. The method according to item 16, wherein the game state is one of a game state of the game currently being executed on the game system or a game state of a pre-recorded game session.

18. In the method enumerated in item 11, the game metadata includes data describing or indicating in-game virtual content, and the broadcast content further includes UI elements for obtaining the in-game content, The method further includes enabling download of individual game content to individual spectacle devices in response to the UI elements and spectacle interactions for obtaining the in-game content.

19. The method of item 18, wherein the in-game virtual content includes one or both of game gear and game characters for the game characters.

20. The method as recited in item 11, wherein the step of enabling provisioning of one or both of the game client or game state to individual spectacle devices comprises: playing the game on the spectacle device for at least one spectacle device. Further comprising initiating a game stream with a streaming interface, wherein the game stream and game streaming interface enable at least partial participation in the game running on the game system from the individual specator device.

21. The method as recited in item 20, further comprising downloading the game client or one or both of the game states to the individual spectator device in the game stream.

22. The method as recited in item 21, enabling the game client on the individual spectater device in response to receiving input for a UI element on the spectacle device representing the purchase of the game. Further comprising a step, the game client enabling enables full participation in the game running on the game system from the individual specator device.

23. The method recited in item 21, wherein the game stream includes downloading in-game virtual content to the individual spectator device.

24. In a non-transitory computer-readable storage medium storing program instructions, causing one or more computing devices when the program instructions are executed on one or more computers:

Generates broadcast content for a broadcast received from a broadcaster device, the broadcast showing gameplay of an individual broadcaster participating as a player in a game running on a gaming system, the broadcast content being at least partially Generated according to game metadata received from the game system according to an application programming interface (API);

Providing the broadcast content to a plurality of spectator devices according to a specting user interface (UI), the broadcast content including UI elements for joining the game;

Obtain the broadcast content and spectator interactions according to the specting UI, and the spector interactions include inputs to the UI elements representing requests to join the game; And

In response to the requests, it is possible to implement a specting system configured to generate inputs to the game system according to the API requesting provisioning of one or both of the game client or game state to individual spectator devices.

25. The non-transitory computer-accessible storage medium listed in item 24, wherein the game metadata includes data describing or representing in-game virtual content including game characters and game gear for game characters. And, the broadcast content further includes UI elements for acquiring the in-game content, and the specting system responds to individual specifications in response to the UI elements and spectator interactions for acquiring the in-game content. It is further configured to enable provisioning of individual game content to data devices.

The preceding can be further understood by considering the following series of items:

1. The system,

A one or more computing devices configured to implement a specting system, the specting system comprising:

Broadcast a video received from a broadcaster device to a plurality of spectator devices, the video including gameplay of individual broadcasters participating as a player in a game running on a game system;

Generate broadcast content according to the game metadata for the game obtained from the game system at least partially according to an application programming interface (API) of the specting system;

Providing the broadcast content to the plurality of spectator devices according to a specting user interface (UI), the broadcast content including UI elements for interacting with the game running on the game system;

Acquiring the broadcast content and the spectator interactions according to the specting UI, and the spectator interactions are related to the UI elements representing interactions with the game running on the game system. Inputs;

Generate game inputs according to the inputs to the UI elements representing at least partially interactions with the game running on the game system; And

It is configured to provide the game inputs to the game system according to the API.

2. For the systems listed in item 1, the spectate system comprises:

Repeatedly performing the acquisition, the generation, and the provision during the broadcast;

Detect changes in the inputs to the UI elements during the iterative acquisition and the generation; And

And change the value of at least one of the game inputs in response to the detection.

3. For the systems listed in item 1, the spectating system is:

Acquiring spectator chat inputs from the plurality of spectator devices, the spectator chat inputs being one of audio chat inputs or text chat inputs for a plurality of spectators associated with the plurality of spectator devices, or Includes both;

Process the spectator chat inputs to determine chat content specifying interactions with the game running on the game system;

Generate additional game inputs according to the determined chat content representing interactions with the game running on the game system; And

It is further configured to provide the additional game inputs to the game system according to the API.

4. In the system listed in item 1, the broadcast content includes one or more UI elements for delivering game information to broadcasters, and the spectacle interactions specify game information to be provided to the broadcaster. Spectator inputs to the one or more UI elements, wherein the specting system is further configured to provide the broadcaster device with the specified game information for display to the broadcaster.

5. In the system listed in item 1, the broadcast content is:

One or more UI elements for adding content to the game world of the game, the game inputs including inputs specifying content to be added to the game world;

One or more UI elements for affecting the environment of the game world of the game, the game inputs comprising inputs specifying one or more effects in the environment of the game world;

One or more UI elements for influencing events in the game, the game inputs comprising inputs specifying one or more effects on events in the game; or

It includes one or more of one or more UI elements for specifying the parameters of the game, and the game inputs include inputs specifying values of one or more parameters of the game.

6. In the system listed in item 1, the broadcast content includes one or more UI elements for providing in-game content or information to players in the game, and the game inputs are games to be provided to designated players Includes inputs from one or more spectator devices that specify my content or information.

7. In the system listed in item 1, the broadcast content includes one or more UI elements for searching for objects in the game world of the game, and the game inputs specify locations to be searched in the game world Input.

8. The method of item 1, wherein the spectacle interactions are interactions with one or more of the spectator devices' controller devices, joysticks devices, motion tracking input devices, or gesture-based input devices. Further comprising actions, the spectating system is further configured to generate additional game inputs at least partially in accordance with the interactions.

9. The system listed in item 1, wherein the specting system includes a game interaction module for the game running on the game system, the game interaction module:

Define the UI elements for interacting with the game;

Define the game inputs for the game; And

Configured to map inputs to the UI elements to interact with the game to values for the game inputs.

10. In the system listed in item 9, the game metadata includes information describing or indicating game content for the game, and at least some of the UI elements display the game content corresponding to or turning the game content. Shows.

11. In the method,

By a specting system implemented on one or more computing devices:

Streaming one or more broadcasts received from one or more broadcaster devices to a plurality of spectacle devices, each broadcast being a game of an individual broadcaster participating as an in-game player running on a game system. Streaming, showing play;

Generating broadcast content for the broadcasts based at least in part on game metadata describing or representing the game content, the broadcast content being a user interface for interacting with the game running on the game system (UI) comprising the elements, generating;

Obtaining the broadcast content and spectator interactions, wherein the spectator interactions include inputs to the UI elements representing interactions with the game running on the game system, The obtaining step;

Generating game inputs based at least in part on the inputs to the UI elements; And

And exposing the game inputs to the game system according to an application programming interface (API) of the specting system.

12. The method according to item 11, further comprising, by the specting system, obtaining at least a portion of the game metadata from the game system according to the API of the specting system.

13. The method listed in item 11,

Obtaining, by the game system, values for the game inputs according to the API; And

And influencing the execution of the game on the game system according to the obtained values.

14. The method listed in item 11,

Obtaining spectator chat inputs from the plurality of spectator devices;

Processing the spectator chat inputs to determine chat content specifying interactions with the game running on the game system;

Generating additional game inputs according to the determined chat content representing interactions with the game running on the game system; And

And providing the additional game inputs to the game system according to the API.

15. The method as recited in item 14, wherein the specator chat inputs include one or both of audio chat inputs or text chat inputs for a plurality of spectors associated with the plurality of specator devices. .

16. The method listed in item 11,

Obtaining video or image inputs of a spectator eye motion, body motion, or facial expression from the plurality of spectator devices;

Processing the video or image inputs to determine metrics specifying interactions with the game running on the game system;

Generating additional game inputs according to the determined metrics representing interactions with the game running on the game system; And

And providing the additional game inputs to the game system according to the API.

17. The method of item 11, wherein the broadcast content includes one or more UI elements for delivering game information to broadcasters, and the spectacle interactions specify game information to be provided to the broadcaster. The spectrometer inputs to the one or more UI elements, and the method further includes providing the specified game information to the broadcaster device for display on the broadcaster.

18. The method of item 11, wherein the broadcast content includes one or more UI elements for adding content to the game world of the game, and the game inputs are inputs specifying content to be added to the game world Includes

19. The method of item 11, wherein the broadcast content includes one or more UI elements for affecting the environment of the game world of the game, and the game inputs have one or more effects on the environment of the game world. Contains specific inputs.

20. The method according to item 11, wherein the broadcast content includes one or more of one or more UI elements for specifying the parameters of the game, and the game inputs specify values of one or more parameters of the game Input.

21. The method of item 11, wherein the broadcast content includes one or more UI elements for providing in-game content or information to players in the game, and the game inputs are games to be provided to designated players. Includes inputs from one or more spectator devices that specify my content or information.

22. The method of item 21, wherein the broadcast content comprises one or more UI elements for purchasing in-game content or information for players, and the game inputs are in-game content for designated players or It includes inputs from one or more spectator devices purchasing information.

23. The method according to item 11, wherein the broadcast content includes one or more UI elements for searching for objects in the game world of the game, and the game inputs specify locations to be searched in the game world Input.

24. The method recited in item 11, wherein the broadcast content includes one or more UI elements for influencing or causing events in the game, wherein the game inputs are the events in the game. Contains inputs that specify one or more effects for or cause one or more events in the game.

25. The method of item 11, wherein the spectacle interactions are interactions with one or more of the spectator devices' controller devices, joysticks devices, motion tracking input devices, or gesture-based input devices. Further comprising actions, the method further comprising generating additional game inputs at least partially in accordance with the interactions.

26. In a non-transitory computer-readable storage medium storing program instructions, causing one or more computing devices when the program instructions are executed on one or more computers:

Create broadcast content for the broadcast received from the broadcaster device, the broadcast showing the gameplay of the individual broadcaster participating as a player in a game running on the game system, the broadcast content being the game system User interface (UI) elements for interacting with the game running on a computer;

Providing the broadcast content to a plurality of spectator devices according to the specting UI;

Acquiring specter interactions with the broadcast content, the spectacle interactions comprising inputs to the UI elements representing interactions with the game running on the game system; And

Implement a game interaction module for a specting system configured to generate values for game inputs according to the inputs to the UI elements representing interactions with the game running on the game system; And

The game inputs are exposed to the game system according to the application programming interface (API) of the specting system.

27. The non-transitory computer-accessible storage medium listed in item 26, wherein the game interaction module comprises:

Acquiring spectator chat inputs from the plurality of spectator devices, the spectator chat inputs being one of audio chat inputs or text chat inputs for a plurality of spectators associated with the plurality of spectator devices, or Includes both;

Process the spectator chat inputs to determine chat content specifying interactions with the game running on the game system; And

And further configured to generate additional game inputs according to the determined chat content representing interactions with the game running on the game system.

Conclusion

Various embodiments may further include receiving, transmitting, or storing instructions and/or data implemented in accordance with the foregoing description of computer-accessible media. Generally speaking, computer-accessible media are volatile or non-volatile, such as, for example, magnetic or optical media, such as a disc or DVD/CD-ROM, RAM (eg, SDRAM, DDR, RDRAM, SRAM, etc.), ROM, etc. Storage media, such as media, or memory media, as well as transmission media or signals, such as electrical, electromagnetic, or digital signals transmitted over a communication medium such as a network and/or wireless link.

Various methods, illustrated in the drawings and described herein, represent representative embodiments of the methods. The methods can be implemented in software, hardware, or a combination thereof. The order of the methods can be changed, and various elements can be added, reordered, combined, omitted, and modified.

Various modifications and changes can be made as will be apparent to those skilled in the art with the benefit of the present disclosure. It is intended to cover all such modifications and changes to be considered illustrative rather than limiting, and thus the above description.

Claims (15)

In the system,
And one or more computing devices configured to implement a specting system, the specting system comprising
Broadcast a video received from a broadcaster device to a plurality of spector devices, the video including gameplay of individual broadcasters participating as a player in a game running on a game system;
Acquiring game metadata for the game from the game system according to an application programming interface (API) of the specting system, wherein the game metadata includes game states for the game, game event data for the game, And one or more of player inputs to the game, or data describing or representing game content -;
Generate broadcast content according to at least partially the game-related content displayed in the game metadata obtained from the game system;
Providing at least a portion of the broadcast content to the plurality of spectator devices according to a specting user interface (UI);
Acquiring spectater interactions with the broadcast content according to the spectaiting UI and spectata inputs from a plurality of spectators associated with the plurality of spectator devices-the spectata input These include one or more of audio chat or text chat -;
Provide indications of at least some of the spectacle interactions to the game system according to the API;
Analyze the specator interactions and the specator inputs to determine specator emotion metrics;
To generate additional broadcast content, at least in part, according to the broadcast metadata and the game-related content generated based at least in part on the spectator sentiment metrics
Configured, system. The system of claim 1, wherein the game state is a point-in-time record of game data and game information representing a particular game at a particular point on a game timeline in the game universe. The system of claim 1, wherein the game event data includes game event records indicating notable events in the game determined by the game system. The system of claim 1, wherein the game content includes one or more of objects, items, or characters in the game. The system of claim 1, wherein the player input indicates command or action input for the game by an individual player through a game client or game controller. The speculating system of claim 1, further comprising:
Acquire speculating preferences for a plurality of specators associated with the plurality of specator devices according to the speculating UI; And
In order to determine broadcast content targeted to a specific specter among the plurality of speculators according to individual speculating preferences of the speculators
Configured, system. The speculating system of claim 1, further comprising:
Generate one or more game inputs according to the analysis of the spectator inputs; And
To provide the one or more game inputs to the game system according to the API-the game inputs affect the execution of the game on the game system-
System composed. The method according to claim 1, wherein the broadcast content is overlaid (overlaid) on the game video received from the UI elements or the broadcaster device provided to the plurality of spectator devices for display according to the specting UI A system comprising one or more of content. In the way,
By a specting system implemented on one or more computing devices:
Streaming one or more broadcasts received from one or more broadcaster devices to multiple spectacle devices-each broadcast is a gameplay of an individual broadcaster participating as an in-game player running on a game system Show -;
Generating content for the broadcasts according to game metadata for the game received at least partially according to an application programming interface (API) of the specting system;
Obtaining spector inputs from the plurality of spector devices, wherein the spector inputs include one or more of audio inputs or text inputs from spectors associated with the specator devices;
Providing indications of the broadcast content and spectacle interactions to the game system according to the API;
Analyzing the specator interactions and the specator inputs to determine specator emotion metrics; And
Generating additional broadcast content for the broadcasts, at least in part, according to the broadcast metadata and the game metadata generated based at least in part on the spectator sentiment metrics.
A method comprising the following. 10. The method of claim 9, wherein the game metadata comprises metadata received from one or more of the game system, the one or more broadcaster devices, a game developer system, or a third party system. The method according to claim 9,
Obtaining, by the game system, indications of the broadcast content and spectacle interactions according to the API; And
Influencing the execution of the game on the game system according to the broadcast content and the displayed spectacle interactions
The method further comprising. The method according to claim 9,
Providing at least a portion of the broadcast content to the plurality of spectator devices according to a specting user interface (UI); And
Acquiring the broadcast content and the spectator interactions according to the specting UI
The method further comprising. The method of claim 9, wherein the game metadata includes one or more of game states for the game, game event data for the game, player inputs to the game, or data describing or representing game content, Way. The method according to claim 9,
Analyzing the specator inputs to determine one or more game inputs; And
Providing the one or more game inputs to the game system according to the API, wherein the game inputs affect the execution of the game on the game system-
How to include more. 10. The method of claim 9, wherein at least a portion of the game metadata is provided by the game system in response to requests from the specting system according to the specting system API.

Images