Patent Application
20200267197
The present invention generally relates to digital content. More specifically, the present invention relates to providing a contextual layer for digital content.
Presently available digital content streams include those that have long and/or complex histories, mythologies, narratives, storylines, backgrounds, terminologies, lexicons, rules, and other contexts. In some cases, such contexts may (eventually) become discernible to a user given enough effort and time. While rich contexts may prolong and deepen engagement with long-time users, complexity may act as a barrier to entry and engagement, however, for new and casual users.
In addition, certain universes—and their storylines and mythologies—may go back years if not decades, as well as extend over different types of digital media (e.g., print, e-books, audio, video including televised episodes and movies, digital games) and multiple titles thereof. A user who is new to such an extended universe may be intimidated by the sheer amount of content, let alone the complex relationships described therein. Such a user may thus find their introduction to a particular content stream confusing and/or frustrating, especially if they are navigating through the stream alone or without the assistance of knowledgeable or experienced friends.
Meanwhile, even long-time users may wish to be able to access contextual data more easily or more immediately during play of digital content. Many digital content streams may not include such contextual data. As such, obtaining contextual data may therefore require access to various information sources, as well as time and effort to formulate queries or otherwise search for the same.
There is, therefore, a need in the art for improved systems and methods of providing a contextual layer for digital content.
Embodiments of the present invention allow for providing a contextual layer for digital content. Contextual information regarding a digital content stream may be stored in memory. Different sets of the contextual information may be associated with different predefined parts of the digital content stream. A request may be received from a user device over a communication network. Such request may concern context for a scene within the digital content stream, The scene may be identified as associated with at least one of the predefined parts of the digital content stream, One of the stored sets of contextual information may be retrieved based on the at least one predefined part of the digital content stream. A contextual layer may be generated based on the retrieved set of contextual information. Such contextual layer may include a presentation of the retrieved set of contextual information to be overlaid on at least part of the scene within the digital content stream.
Various embodiments of the present invention may include methods for providing a contextual layer for digital content. Such methods may include storing contextual information regarding a digital content stream in memory where different sets of the contextual information is associated with different predefined parts of the digital content stream. Methods may further include receiving a request from a user device over a communication network concerning context for a scene within the digital content stream, identifying that the scene is associated with at least one of the predefined parts of the digital content stream, retrieving one of the stored sets of contextual information based on the at least one predefined part of the digital content stream, and generating a contextual layer that includes a presentation of the retrieved set of contextual information to be overlaid on at least part of the scene within the digital content stream.
Further embodiments of the present invention may include systems for providing a contextual layer for digital content. Such systems may include memory that stores contextual information regarding a digital content stream where different sets of the contextual information is associated with different predefined parts of the digital content stream. Systems may further include a communication interface that receives a request from a user device over a communication network that concerns context for a scene within the digital content stream. In addition, systems may include a processor that identifies that the scene is associated with at least one of the predefined parts of the digital content stream, retrieves one of the stored sets of contextual information based on the at least one predefined part of the digital content stream, and generates a contextual layer that includes a presentation of the retrieved set of contextual information to be overlaid on at least part of the scene within the digital content stream.
Yet further embodiments of the present invention may include non-transitory computer-readable storage media having embodied thereon a program executable by a processor to perform a method for providing a contextual layer for digital content as described above.
Embodiments of the present invention allow for providing a contextual layer for digital content. Contextual information regarding a digital content stream may be stored in memory. Different sets of the contextual information may be associated with different predefined parts of the digital content stream. A request may be received from a user device over a communication network. Such request may concern context for a scene within the digital content stream, The scene may be identified as associated with at least one of the predefined parts of the digital content stream, One of the stored sets of contextual information may be retrieved based on the at least one predefined part of the digital content stream. A contextual layer may be generated based on the retrieved set of contextual information. Such contextual layer may include a presentation of the retrieved set of contextual information to be overlaid on at least part of the scene within the digital content stream.
Content source servers 110 may maintain and provide a variety of digital content available for distribution. The content source servers 110 may be associated with any content provider that makes its content available for access over a communication network. Such content may include not only digital video and games, but also other types of digital applications and services. Such applications and services may include any variety of different digital content and functionalities that may be provided to user devices 150.
The content from content source server 110 may be provided through a content provider server API 120, which allows various types of content sources server 110 to communicate with other servers in the network environment 100 (e.g., user devices 150). The content provider server API 120 may be specific to the particular language, operating system, protocols, etc. of the content source server 110 providing the content, as well as the user devices 150. In a network environment 100 that includes multiple different types of content source servers 110, there may likewise be a corresponding number of content provider server APIs 120 that allow for various formatting, conversion, and other cross-device and cross-platform communication processes for providing content and other services to different user devices 150, which may use different operating systems, protocols, etc., to process such content. As such, applications and services in different formats may be made available so as to be compatible with a variety of different user device 150.
The content provider server API 120 may further facilitate access of each of the user devices 150 to the content hosted or services provided by the content source servers 110, either directly or via content delivery network server 130. Additional information, such as metadata, about the accessed content or service can also be provided by the content provider server API 120 to the user device 150. As described below, the additional information (i.e. metadata) can be usable to provide details about the content or service being provided to the user device 150. In some embodiments, the services provided from the content source servers 110 to the user device 150 via the content provider server API 120 may include supporting services that are associated with other content or services, such as chat services, ratings, and profiles that are associated with a particular game, team, community, etc. In such cases, the content source servers 110 may also communicate with each other via the content provider server API 120.
The content delivery network server 130 may include a server that provides resources, files, etc., related to the content from content source servers 110, including various content and service configurations, to user devices 150. The content delivery network server 130 can also be called upon by the user devices 150 that request to access specific content or services. Content delivery network server 130 may include universe management servers, game servers, streaming media servers, servers hosting downloadable content, and other content delivery servers known in the art.
Context management server 140 may include any data server known in the art that is capable of managing contextual data for a variety of digital content streams. In an exemplary implementation, context management server 140 manages storage of contextual information for different content streams. When a user device 150 requests context for a current scene within a specific content stream, context management server 140 may identify a specific set of contextual information and generate a contextual layer that presents the identified set of contextual information to be overlaid over the current scene.
The user device 150 may include a plurality of different types of computing devices. The user device 150 may be a server that provides an internal service (e.g., to other servers) in network environment 100. In such cases, user device 150 may correspond to one of the content servers 110 described herein. Alternatively, the user device 150 may be a client device that may include any number of different gaming consoles, mobile devices, laptops, and desktops. Such user devices 150 may also be configured to access data from other storage media, such as, but not limited to memory cards or disk drives as may be appropriate in the case of downloaded services. Such user devices 150 may include standard hardware computing components such as, but not limited to network and media interfaces, non-transitory computer-readable storage (memory), and processors for executing instructions that may be stored in memory. These user devices 150 may also run using a variety of different operating systems (e.g., iOS, Android), applications or computing languages (e.g., C++, JavaScript). An exemplary client device 150 is described in detail herein with respect to
In an exemplary implementation, a user device 150 may request a digital content stream hosted by content source server 110. Such request may be made via content delivery network server 130 in conjunction with content provider server APIs 120. Meanwhile, context management server 150 may maintain contextual data regarding the digital content stream. Each digital content stream made available in network environment 100 may be associated with a different body of contextual information, and different sets of that contextual information may be associated with different predefined parts of the digital content stream. For example, a digital game may involve a variety of different players, as well as different in-game objects (inclusive of in-game characters, locations, creatures, weapons, prizes, etc.). Each player and in-game object may be associated with a different set of contextual information. Such contextual information may include information regarding histories, mythologies, narratives, storylines, backgrounds, biographies, terminologies, lexicons, rules, objectives, statistical data, related works, instruction manuals, guides, hyperlinks, commentaries, and other associated media.
A user device 140 that is streaming a particular digital content stream may make a request for context while a specific scene of the digital content stream is currently played. Such stream may or may not be paused in response to the contextual request. Where the requestor is the player, for example, the stream may be paused to allow the player to review the contextual information presented in the contextual layer. Some spectators, however, may prefer to allow the stream to keep playing the background, while the contextual layer is presented (e.g., as a partial or translucent overlay). In some embodiments, the contextual layer may be updated in real-time as the digital content stream continues to play.
Context management server 140 may identify that the request is associated with the specified scene within the digital content stream and further that the specified scene is associated with at least one of the predefined parts of the digital content stream. For example, the scene may include a character holding a weapon and fighting a creature. Within the body of contextual data for the digital content stream, different sets of contextual data may be identified as providing context regarding the character, weapon, and creature, respectively. Parts of the contextual data sets may be related (e.g., applicable rules, scoring systems, and respective abilities in combat). Analyses of the scene in order to identify which contextual data sets to retrieve may further include image analyses, audio/voice analyses (e.g., identified keywords), metadata analyses regarding current status, and other analyses. For interactive and game content, game data (including metadata) may be provided from content source server 110 and/or content delivery server 130 regarding current game status for the current scene within the digital content stream. Where the digital content stream may be associated with audio commentary, for example, the content of the commentary may also be analyzed in accordance with the foregoing techniques. The current scene may further be identified by reference to the point in time at which the current scene appears or a location within a virtual universe where the current scene is set.
Context management server 140 may then retrieve one or more of the stored sets of contextual information based on at least one predefined part (e.g., character, weapon, creature) found in the scene. In some embodiments, the current scene of the digital content stream may include multiple objects, and the behavior of the user device 140 in making the request may specifically indicate a selection among the objects. In such instance, the context management server 140 may prioritize retrieval of the set of contextual information associated with the selected object. As discussed in further detail below, the retrieved set(s) of contextual information may be used to generate a contextual layer. Where there are multiple objects and a selection therefrom, different contextual layers—based on different sets of contextual data retrieved or different layouts—may be generated based on different selections.
Referring to the earlier exemplary scene involving the specific character, weapon, and creature, context management server 140 may retrieve the associated sets of contextual data for use generating a contextual layer that presents the contextual data identified as relevant to the character, weapon, and creature depicted in the specific scene. For digital content streams that are interactive (e.g., game), such contextual data ya further include information regarding how the scene fits into the game title generally, current game session/status, game objectives, and other game-related contexts. Such contextual data may be incorporated into and presented by the contextual layer in a variety of ways.
In some embodiments, the generated contextual layer may be further curated and/or customized in accordance with different parameters and preferences. For example, context management server 140 may further store or access historical or statistical data regarding previous interactions by a plurality of user devices with the digital content stream. Such data may be used as a basis for identifying or prioritizing that the scene is associated with a specific set of contextual data. Such prioritized dataset may be presented more prominently within the contextual layer generated by context management server 140. Further, context management server 140 may make a prediction regarding a future interaction with the digital content stream based on the historical or statistical data. Such prediction may also be presented in the contextual layer, as well as used as a basis for filtering or customizing related sets of data within the presentation of the contextual layer. Different users of user devices 150 may also be associated with user profiles that include preferences and other user data (e.g., skill level, experience level, games played, designated team members and friends, express interests). Such profile data may also be used to customize a contextual layer (e.g., prioritizing or making more prominent the contextual information that is related to the profile data).
In method 400 of
In step 410, information regarding contextual datasets may be stored and managed by context management server 140. In some embodiments, contextual information may also be stored at content source servers 110, content delivery network servers 130, and other data sources (e.g., various websites). Each digital content stream may therefore be associated with a body of contextual data stored in different locations, and different sets of the contextual information with that body may be associated with different predefined parts (e.g., points in time, virtual location, character, weapons, other objects, etc.) of the digital content stream. The information stored by context management server 140 includes information regarding where different sets of the contextual information is stored so as to allow for retrieval of the same as needed.
In step 420, a request may be received from a user device 150 over a communication network. Such user device may be streaming a specific digital content stream and have made the request in association with a specific scene. Various types of data and metadata regarding the specified scene may be included in the request or may be accessed from content source server 110 (or content delivery network server 130). Some analysis—image analysis or audio analysis—may also be performed to identify the scene and its contents.
In step 430, context management server 140 may identify that the scene is associated with at least one of the predefined parts of the digital content stream. Such parts may include specific characters, weapons, creatures, and other objects, etc., depicted with the scene. In certain interactive digital content titles, the parts may further include current game status, game level, and relationships to certain objectives. Once the scene is identified as including certain component parts, such parts may be correlated to specifically identified sets of contextual data.
In step 440, context management server 140 retrieves the specifically identified sets of contextual information from their respective storage locations. As noted above, the sources for the contextual information may be varied, and as such, the context management server 140 may retrieve different datasets from multiple different storage locations based on the identified parts of the scene indicated by the request.
In step 450, context management server 140 generates a contextual layer based on the retrieved set(s) of contextual information. The generated contextual layer may include a presentation of the retrieved set of contextual information to be overlaid on at least part of the scene within the digital content stream. Such overlay may exhibit different degrees of translucency, so that viewer can see the underlying scene in conjunction with the presented contextual information. In some instances, the contextual layer may only overlay part of the scene. Context management server 140 may also configure the presentation of the contextual information around the content of the scene, so as not to obscure the same. Other layouts for the contextual layer may include a designated area of the screen to be used for the retrieved set of contextual information.
In step 460, the contextual layer may be customized to the requesting user via a profile indicative of certain preferences and parameters. Such preferences and parameters may be used to filter the retrieved contextual information, as well as to select different configurations and prioritize different retrieved sets of contextual information.
Entertainment system 500 may be an electronic game console. Alternatively, the entertainment system 500 may be implemented as a general-purpose computer, a set-top box, a hand-held game device, a tablet computing device, or a mobile computing device or phone. Entertainment systems may contain more or less operating components depending on a particular form factor, purpose, or design.
The CPU 510, the vector unit 515, the graphics processing unit 520, and the I/O processor 525 of
The graphics processing unit 520 of
A user of the entertainment system 500 of
The present invention may be implemented in an application that may be operable by a variety of end user devices. For example, an end user device may be a personal computer, a home entertainment system (e.g., Sony PlayStation2® or Sony PlayStation3® or Sony PlayStation4®), a portable gaming device (e.g., Sony PSP® or Sony Vita®), or a home entertainment system of a different albeit inferior manufacturer. The present methodologies described herein are fully intended to be operable on a variety of devices. The present invention may also be implemented with cross-title neutrality wherein an embodiment of the present system may be utilized across a variety of titles from various publishers.
The present invention may be implemented in an application that may be operable using a variety of devices. Non-transitory computer-readable storage media refer to any medium or media that participate in providing instructions to a central processing unit (CPU) for execution. Such media can take many forms, including, but not limited to, non-volatile and volatile media such as optical or magnetic disks and dynamic memory, respectively. Common forms of non-transitory computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM disk, digital video disk (DVD), any other optical medium, RAM, PROM, EPROM, a FLASHEPROM, and any other memory chip or cartridge.
Various forms of transmission media may be involved in carrying one or more sequences of one or more instructions to a CPU for execution. A bus carries the data to system RAM, from which a CPU retrieves and executes the instructions. The instructions received by system RAM can optionally be stored on a fixed disk either before or after execution by a CPU. Various forms of storage may likewise be implemented as well as the necessary network interfaces and network topologies to implement the same.
The foregoing detailed description of the technology has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology, its practical application, and to enable others skilled in the art to utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claim.
