JPWO2019133481A5 - - Google Patents

Description

[Cross reference]
This application claims the benefit of and priority to U.S. Nonprovisional Patent Application No. 15/858,556, filed Dec. 29, 2017, which is hereby incorporated by reference in its entirety.

This application relates generally to virtual reality systems. More specifically, this application describes techniques for organizing registries of virtual reality containers, techniques for interacting with such registries, techniques for simplifying access to virtual reality containers for end users, and techniques for simplifying access to virtual reality containers for end users. Technology for Obtaining Supplemental Content for Use Within.

Various publishers may wish to host or create virtual reality (VR) worlds, different publishers may use different VR formats, or may support only some types of end-user VR systems, and specific can leave end-users with multiple VR systems unable to access VR worlds not supported by their particular VR system.

Systems, methods, and computer products are disclosed herein for facilitating end-user access to virtual reality (VR) containers, including enabling end-user access to supplemental information within the VR container. explained in A universal VR container registry is created to allow end-users to discover VR containers of interest. The registry may also allow end-users to discover VR containers that are compatible with the end-user's own VR system. The registry may also enable end-users to discover useful supplemental content. Any type of VR container or supplemental content has features that describe the requirements necessary to access the container or supplemental content, restrictions on who or when access can be granted, and the mechanics of the container or supplemental content. The registry can be universal in that it can be enumerated within the registry with, etc. The Registry determines how a container is accessed, what other containers can be linked to or accessed from within the container, the type or format of output produced by the container, the inputs the container accepts , what supplemental content can be accessed from within the container, the types and formats of supplemental content that can be accessed from within the container, and the like. To allow more efficient searching or modification of the registry, the registry may be organized in a hierarchical structure.

A hierarchical structure may use or correspond to the Domain Name System and may include one or more top-level items each having one or more second-level items organized beneath it. . Optionally, the top-level registry provider may control or otherwise restrict the top-level registry and allow lower-level registries to be organized under particular top-level entries. Such lower level registries may be aggregated, for example, by agreement between a top level registry provider and a lower level registry provider. At lower levels of the hierarchy, local registries may be further organized under or within higher levels, optionally facilitated by agreement between local registry providers and higher level registry providers or controlling entities. .

Service providers may offer hosted VR containers to facilitate end-user access to other VR containers and supplemental content. Hosting containers may correspond to entry-level or staging containers, allowing end-users to move between remote VR containers while remaining within a VR session, or without having to completely exit the entire VR session. can enable

In one aspect, a method is provided, such as a method relating to effective access of a service provider to a remote VR system. In some embodiments, methods of this aspect establish a first connection, such as a first connection associated with a service provider VR session, between a service provider virtual reality (VR) container and an end-user VR system. determining a first portal for accessing a first remote VR container from within a service provider VR session; populating the first portal into the service provider VR container; detecting input generated by the end-user VR system within the service provider VR container corresponding to determining a first access instruction to access a second remote VR session associated with the first remote VR session; facilitating establishment of a second connection, such as a connection, between a first remote VR container and an end-user VR system; and a second portal, such as a second portal, corresponding to the second remote VR container. detecting input generated by the end-user VR system corresponding to the determination of the second access instruction to access the portal of the third remote VR session, such as a third connection associated with the second remote VR session; connection between the second remote VR container and the end-user VR system.

Optionally, methods of this aspect may identify or determine the requirements and capabilities of the end-user VR system, such as to ensure compatibility with various remote VR containers. Optionally, methods of this aspect may or may further include determining the type of the end-user VR system, such as a type that corresponds at least in part to the requirements and capabilities of the end-user VR system. Optionally, determining the type includes exchanging handshake messages with the end-user VR system. Optionally, determining the type includes receiving input corresponding to determining the type of end-user VR system, such as user input identifying the type of end-user VR system. Optionally, methods of this aspect may or may further include obtaining supplemental content, such as in response to a request for supplemental content, and providing the supplemental content to the end-user VR system.

In embodiments, various remote VR containers and supplemental content may be used with this aspect of the method. For example, different remote VR containers may have different requirements and capabilities, may produce different outputs, and may accept different inputs. For example, aspects of this method include determining a first requirement and first capability of a first remote VR container and determining a second requirement and second capability of a second remote VR container. or may further include Optionally, the first requirement and second capability are different than the second requirement and second capability.

In some embodiments, different VR session types may be used with this aspect of the method. For example, server-side VR session creation techniques may be used. By way of example, establishing the first connection optionally includes generating an output, such as an output compatible with the requirements of the end-user VR system. Optionally, the output corresponds to a VR container output stream sent to an end-user VR system. Optionally, establishing the first connection includes or further includes receiving a VR system output stream from the end-user VR system.

Alternatively, end-user side VR session creation techniques can be used. Illustratively, establishing a first connection involves sending a set of instructions associated with a service provider VR container for execution by an end-user VR system, and transferring data generated during execution of the set of instructions. receiving the output.

It should be appreciated that multiple portals may be populated within the Service Provider VR container. These portals can take different forms depending on the end-user system, the characteristics of the VR container they represent, and so on. Optionally, determining the first portal comprises sending a query to a registry of virtual containers and a query identifying one or more virtual containers including a first remote VR container corresponding to the first portal. and receiving a response. Optionally, the query includes requirements or capabilities of the end-user VR system. Optionally, the query includes features, constraints, or authentication credentials or tokens associated with the user of the end-user VR system. Optionally, the query includes features or identifiers for the target VR container, such as features or identifiers received as input from the end-user. Optionally, the method of this aspect includes or further includes receiving input corresponding to determining the characteristic or identifier. Optionally, the virtual container registry includes multiple entries. For example, each entry optionally corresponds to a virtual container. Optionally, each entry includes an identifier associated with the virtual container, a requirement associated with the virtual container, a constraint associated with the virtual container, and a feature associated with the virtual container. Further details about registries useful in this aspect of the method are described below.

Different representations for various portals may be used. For example, populating a service provider VR container with a first portal involves obtaining one or more portal representations for the first portal and generating the first portal using a particular portal representation. optionally including Optionally, obtaining one or more portal representations for the first portal includes obtaining one or more portal representations for the first portal from a provider associated with the first portal. Optionally, obtaining the one or more portal representations for the first portal includes sending a query to a registry of virtual containers and receiving a query response identifying the one or more portal representations. . Optionally, an entry corresponding to the virtual container each including an identifier associated with the virtual container, a requirement associated with the virtual container, a feature associated with the virtual container, and one or more portal representations associated with the virtual container. The virtual container registry contains a number of entries such as Again, details regarding registries useful in this aspect of the method will be described below. Optionally, a particular portal representation corresponds to one of one or more portal representations compatible with the requirements and features of the end-user VR system. Optionally, a particular portal representation is associated with a time of day, day of the year, day of the week, month of the year, season, holiday, or a particular event. Optionally, a particular portal representation is associated with an authentication credential or token associated with a user of the end-user VR system.

It will be appreciated that end-users may access different portals from within a service provider VR session. It will also be appreciated that an end user may access another remote VR container from within a remote VR session. For example, detecting input generated by the end-user VR system corresponding to determining a second access instruction to access a second portal may be performed by detecting a second access instruction to access the second portal. detecting input generated by the end-user VR system within the first remote VR session corresponding to the determination of . Optionally, facilitating establishment of the third connection occurs while the first remote VR session is active.

In some embodiments, the portal representation can be a representation of the VR world associated with the portal when rendered during a VR session, or can be static, animated, Or it can depict a changing image. As an example, the portal may correspond to images of products or services associated with the VR world, such as advertisements for products or services offered. In this manner, banners, billboards, or other advertisements may be introduced in a VR world, such as a service provider VR session or other VR world. It will be appreciated that portals within a VR session may take any suitable shape or size. In some embodiments, portals may be rendered similar to windows or doors. In other embodiments, the portal may be rendered as a work of art, a small object (eg, tablet or book), or on the surface of another object. Some portals may not allow access for a user to connect to or enter the VR world associated with the portal, thus allowing unidirectional or interactive access to supplemental content within a VR session. It will be appreciated that it can correspond to the display. Optionally, such portals may support technology for advertising within the VR world or VR session and may provide technology for enabling the provision of the VR world or VR session.

In some embodiments, a user may terminate a particular remote VR session or leave a particular remote VR session, return to the service provider VR container, and/or re-establish the service provider VR session. . Advantageously, this requires the user to set up a new VR session or search for a particular new VR container to access and remove or leave their VR system. It may allow the user to move between unlinked, unconnected, or unrelated VR containers without having to completely terminate the VR session, which means that it is necessary to Optionally, the method of this aspect includes or further includes identifying input generated by the end-user VR system corresponding to an exit instruction for exiting the first remote VR container. Optionally, the method of this aspect includes establishing a fourth connection between the service provider VR container and the end-user VR system, such as establishing a fourth connection that occurs in response to the termination command; or further include: Optionally, a fourth connection is associated with a service provider VR session. Optionally, detecting input generated by the end-user VR system corresponding to determining a second access instruction for accessing the second portal is a second step for accessing the second portal. Detecting input generated by the end-user VR system within the service provider VR session that corresponds to determining the access instruction. Optionally, facilitating establishment of the third connection occurs while the service provider VR session is active. Optionally, the method of this aspect includes or further includes determining a second portal for accessing a second remote VR container from within the service provider VR session.

Various techniques may be used to establish a remote VR session. For example, a direct connection can be established between the end-user system and the remote VR container. Alternatively or additionally, a translation or transformation layer between the end-user system and the remote VR container to enable the end-user system to establish a connection with the remote VR container. can exist. Such conversions or transformations may be useful, for example, in situations where the end-user system is not fully or partially compatible with the remote VR container.

Optionally, facilitating establishing a connection includes an address associated with the remote VR container, requirements and capabilities associated with the remote VR container, and a handshake protocol for establishing the connection with the remote VR container. to the end user VR system, such as information associated with the remote VR container including one or more of: Optionally, receiving information associated with the remote VR container at the end-user VR system causes the end-user VR system to establish a connection with the remote VR container. Optionally, the end-user VR system is compatible with the remote VR container.

Optionally, facilitating establishing a connection associates a VR container output stream, such as a VR container output stream that is at least partially incompatible with the requirements and capabilities of the end-user VR system, with the remote VR container. and transforming the VR container output stream to produce a transformed output stream, the transformed output stream being compatible with the requirements and capabilities of the end-user VR system. and sending the transformed output stream to the end-user VR system. Optionally, the transforming comprises determining a first format of the VR container output stream; determining a second format compatible with the requirements and capabilities of the end-user VR system; identifying a transformation protocol or algorithm for converting from to a second format; and transforming the VR container output stream into the transformed output stream according to the transformation protocol or algorithm.

Optionally, facilitating establishing a connection receives from the end-user VR system a VR input stream, such as a VR input stream that is incompatible with the remote VR container and compatible with the remote VR container. transforming the VR input stream to generate a transformed input stream, such as the transformed input stream; and transmitting the transformed input stream to a content provider associated with the remote VR container. Optionally, the transforming comprises determining a first format of the VR input stream; determining a second format compatible with the remote VR container; converting the first format to the second format; identifying a transformation protocol or algorithm for transformation; and transforming the VR input stream into the transformed input stream according to the transformation protocol or algorithm.

In another aspect, provided herein is a system, such as a system for implementing a method related to effective access of a service provider to a remote VR system. In one embodiment, a system of this aspect is one or more processors and a non-transitory computer-readable storage medium in data communication with the one or more processors, wherein when executed by the one or more processors: and said non-transitory computer-readable storage medium containing instructions that cause one or more processors to perform any of the methods of the previously described aspects.

In another aspect, provided herein is a computer program product, such as a computer program product for implementing a method of facilitating service provider access to remote VR systems. In one embodiment, the computer program product of this aspect comprises instructions that, when executed by one or more processors, cause the one or more processors to perform any of the methods of the previously described aspects. Corresponds to temporary computer-readable storage medium.

In another aspect, a method is provided for establishing and using a registry of virtual containers. In some embodiments, the method of this aspect includes instantiating by the computing device a registry of virtual containers, such as a registry containing multiple entries. Optionally, each entry corresponds to a virtual container and one of an identifier associated with the virtual container, a requirement associated with the virtual container, a constraint associated with the virtual container, and a feature associated with the virtual container. Including above. Optionally, the method of this aspect includes or further includes receiving by the computing device an add query to add a new entry to the registry. Optionally, the additional query includes one or more of additional identifiers for the new entries, additional requirements for the new entries, additional constraints for the new entries, and additional features for the new entries. Optionally, the method of this aspect includes adding a new entry to the registry, such as a new entry including one or more of additional identifiers, additional requirements, additional constraints, and additional features; or further includes Optionally, methods of this aspect include new or changed identifiers for existing entries, new or changed requirements for existing entries, new or changed constraints for existing entries, and or further comprising receiving by the computing device a change query to modify an existing entry in the registry, such as a change query including one or more of the new or changed features. Optionally, methods of this aspect include new or changed identifiers for existing entries, new or changed requirements for existing entries, new or changed constraints for existing entries, and This includes or further includes modifying existing entries in the registry to include one or more of the new or changed features.

The registry of virtual containers may, among other uses, identify VR containers based on queries, obtain information about known VR containers, and provide additional or supplemental information about known VR containers to users. Allowing users to add or modify entries to provide, allowing VR containers to be associated with other VR containers and/or users, and owning VR containers and entries for VR containers can be useful in identifying the author, registrant, creator, or copyright holder. Optionally, the method of this aspect performs a query to identify one or more virtual containers from the registry, such as a query including at least one of an identifier query, a requirement query, a constraint query, and a feature query. Receipt by a computing device and query results corresponding to entries in a registry having identifiers matching an identifier query, requirements matching a requirement query, constraints matching a constraint query, or features matching a feature query, etc. and generating, by the computing device, output corresponding to the one or more query results. Optionally, the query corresponds to an initial filtering request to identify one or more virtual containers accessible to the user. For example, the query can be used to identify VR containers that are compatible with or accessible using a particular end-user system.

Various identifiers may be included in different registry entries. Identifiers include, without limitation, a name associated with a virtual container, an owner associated with a virtual container, a network address associated with a virtual container, a unique identifier associated with a virtual container, a It may correspond to a domain, a version number associated with the virtual container, and a registrant associated with the virtual container.

Various requirements may be contained within different registry entries. It will be appreciated that the term requirement, as used herein, may refer to aspects required to establish access with a VR container or to establish a VR session with a VR container. . It will further be appreciated that different requirements may be met by using transformations or variations to provide compatibility with the requirements. Optionally, the requirements correspond to access restrictions imposed by the virtual container for gaining access to the virtual container. Optionally, the requirements correspond to hardware requirements associated with the virtual container and/or software requirements associated with the virtual container. Optionally, the requirements correspond to indicators of user characteristics required to gain access to the virtual container.

Various constraints may be contained within different registry entries. It will be appreciated that the term constraint, as used herein, can refer to aspects of restricting access to a VR container. For example, the constraints optionally correspond to restrictions on receiving query results corresponding to the virtual container and on obtaining access to the virtual container. Optionally, the constraints correspond to a number of years associated with the virtual container, a language associated with the virtual container, and/or a time limit associated with the virtual container.

Various features may be contained within different registry entries. It will be appreciated that the term feature as used herein may provide a descriptor for a VR container. Another term used in some embodiments to describe features can be the term "tag." Features may be defined by, for example, the creator of the VR container, the organizer of the VR container, the owner of the VR container, or the user of the VR container. Optionally, the features are descriptors associated with the VR container, authorization indicators describing whether the virtual container requires authorization, indicators of allowed use for the virtual container, other and/or the language associated with the virtual container. Optionally, features may contain the same content as identifiers, requirements, and/or constraints. That is, identifiers, requirements, and/or constraints may also be listed as features. Advantageously, a feature can be any item contained within a registry entry that can be different from the entry. For example, some types of features may not be required per entry, but may be available if some containers use them. For example, features describing authentication requirements may be useful features used by at least a portion of the entries. Optionally, the features correspond to one or more portal representations used to represent entry points into the virtual container. Features can also include ratings, such as user ratings, which can be used as crowdsourced authentication of particular entries. Features may also include digital signatures that allow a user to verify the authenticity of a particular entry, such as owned, published, sponsored, created, etc. by a particular entity such as a company, user, publisher, or the like.

In embodiments, multiple entries are organized within the registry in a hierarchical structure. For example, the hierarchical structure optionally includes multiple top-level items each associated with a particular virtual container identifier or characteristic. Exemplary top-level items may correspond to high-level groups of VR containers, such as groups all related to a particular topic, a particular subscriber, a particular owner, a particular publisher, and so on. Optionally, each top-level item has multiple entries organized under the top-level item, such as multiple entries each associated with an identifier or characteristic of a particular virtual container associated with the top-level item. include. Optionally, each top-level item includes one or more second-level items organized under the top-level item, such as one or more second-level items each relating to different characteristics. Optionally, each second level item includes multiple entries organized under the second level item, such as multiple entries each relating to features associated with the second level item.

Such organization may be similar to the organization of domain names in the DNS system. Optionally, the registry uses a domain name server structure. In the DNS system, . It will be appreciated that the top level domain may be controlled by a particular entity, such as how COM top level domains are managed by Verisign. In registries associated with methods of this aspect, a particular top-level item may relate to a particular identifier or characteristic. The example described below is a top-level item corresponding to a library. Each entry organized under the top-level item of the library will be assumed to relate to the library in some way.

In another aspect, systems are provided herein, such as systems for implementing methods relating to establishing and using a registry of virtual containers. In one embodiment, a system of this aspect is one or more processors and a non-transitory computer-readable storage medium in data communication with the one or more processors, wherein when executed by the one or more processors: and said non-transitory computer-readable storage medium containing instructions that cause one or more processors to perform any of the methods of the previously described aspects.

In another aspect, provided herein is a computer program product, such as a computer program product for implementing a method relating to establishing and using a registry of virtual containers. In one embodiment, the computer program product of this aspect comprises instructions that, when executed by one or more processors, cause the one or more processors to perform any of the methods of the previously described aspects. Corresponds to temporary computer-readable storage medium.

In another aspect, a method is provided for facilitating access to supplemental content using a VR container. In one embodiment, a method of this aspect comprises receiving by a computing device a first request to access a virtual reality (VR) container from a first end-user VR system; Establishing a first network connection with the system and using the first network connection to facilitate access by the first end-user VR system to data for rendering output corresponding to the VR container. receiving a second request for access to the VR container from a second end-user VR system; confirming a second network connection with the second end-user VR system; using a second network connection to facilitate access by a second end-user VR system to data for rendering output to the VR container; and accessing supplemental content streams within the VR container. receiving a third request for, using the first network connection to facilitate access by the first end-user VR system to the supplemental content stream; and using a second network connection to facilitate access by the end-user VR system of the. Optionally, the supplemental content stream is a user-sourced content stream generated by the end-user VR system, a data stream associated with the second VR container, an audio stream, a video stream, a text stream, associated with the end-user VR system. Includes one or more of metadata, metadata associated with the VR container, or accessibility data.

Optionally, the third request includes one or more preferences or permissions associated with the first end-user VR system or the second end-user VR system, which are provided to the particular end-user VR system. specific end-user VR system, and may be different from the supplemental content provided to another particular end-user VR system. By way of example, supplemental content may correspond to conversions of content within a VR container, different conversions may be provided for different end-user VR systems, and accessibility mechanisms may be provided in a similar manner.

In embodiments, the supplemental content stream includes supplemental audio information overlaid on an audio stream associated with the VR container, or the supplemental content stream is supplemental video overlaid on a video stream associated with the VR container. Contains information. Optionally, facilitating access to the supplemental content stream includes obtaining the supplemental content stream and transmitting the supplemental content stream or data derived from the supplemental content stream. Optionally, facilitating access to the supplemental content stream includes including at least a portion of the supplemental content stream within data for rendering output corresponding to the VR container. Accordingly, a VR session may have supplemental content from another source added to the VR session. Such additions may occur by the provider of the VR container or at the end-user VR system. Optionally, facilitating access to the supplemental content stream includes transmitting a network address for a remote server providing the supplemental content stream. Such communication of network addresses may allow end-user systems to obtain supplemental content directly from remote servers.

Optionally, the supplemental content stream includes user-sourced content streams generated by the end-user VR system. In this manner, content provided by an end-user VR system, generated in an end-user VR system, or otherwise acquired by an end-user VR system can be shared with VR containers and/or other end-user VR systems. can be For example, methods of this aspect may further include receiving a first user-sourced content stream transmitted by a first end-user VR system. Optionally, the user-sourced content stream is an audio stream obtained by the end-user VR system, a video stream obtained by the end-user VR system, a text stream obtained by the end-user VR system, a Includes one or more of VR container location data, preferences associated with an end-user VR system, permissions associated with an end-user VR system, or metadata associated with an end-user VR system. Optionally, at least a portion of the first user-sourced content stream is transmitted to a second end-user VR system, such as during the VR session or as a second content stream. Optionally, the network address of the first end-user VR system is the second end-user VR system's network address to facilitate acquisition of at least a portion of the first user-sourced content stream by the second end-user VR system. can be sent to Such information may enable a first user-sourced content stream to be obtained directly from a first end-user VR system by a second end-user VR system. Optionally, to facilitate the first end-user VR system providing at least a portion of the first user-sourced content stream to the second end-user VR system, the network of the second end-user VR system It can be sent to the first end-user VR system. In some embodiments, however, the supplemental content is not a user-sourced content stream, but is generated by a remote server rather than the end-user VR system, or is otherwise provided by another source other than the user-sourced content stream. content stream, or is the other content stream.

Optionally, facilitating access to data for rendering output corresponding to the VR container includes transmitting the VR container output stream. For example, facilitating access to data for rendering output corresponding to a VR container may optionally further include generating a VR container output stream. Optionally, facilitating access to data for rendering output corresponding to the VR container includes sending an instruction set for directly generating the VR container output stream by the end-user VR system. Optionally, facilitating access to data for rendering output corresponding to a VR container provides instructions for providing a VR container output stream or directly generating a VR container output stream by an end-user VR system. Including sending the network address to the remote server that provides the set. By facilitating access to data for rendering outputs corresponding to VR containers, end-user VR systems can directly generate VR container output streams, and servers corresponding to VR containers can generate VR container output streams. or a service provider VR session or other intermediary server or session may generate a VR container output stream in a format compatible with the end-user VR system.

In another aspect, systems are provided herein, such as systems for implementing methods related to facilitating access to supplemental content within a VR container. In one embodiment, a system of this aspect is one or more processors and a non-transitory computer-readable storage medium in data communication with the one or more processors, wherein when executed by the one or more processors: and said non-transitory computer-readable storage medium containing instructions that cause one or more processors to perform any of the methods of the previously described aspects.

In another aspect, provided herein is a computer program product, such as a computer program product, for implementing a method related to facilitating access to supplemental content within a VR container. In one embodiment, the computer program product is a non-transitory computer comprising instructions that, when executed by one or more processors, cause the one or more processors to perform any of the methods of the previously described aspects. Corresponds to a readable storage medium.

Without wishing to be bound by any particular theory, discussion herein of basic principles or understandings of the invention is possible. It is understood that regardless of the ultimate correctness of any mechanical explanation or hypothesis, embodiments of the invention may still be effective and useful.

A further understanding of the nature and advantages of various embodiments may be realized by reference to the following drawings. In the accompanying drawings, similar components or features may have the same reference labels. Additionally, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes between similar components. Where only the first reference label is used in the specification, the discussion applies to any one of the similar components having the same first reference label regardless of the second reference label.

Embodiments of networks are described. Provide a general description of communication between devices. 1 provides an overview of a method for providing access to a remote VR system, according to some embodiments; 1 provides a schematic description of a portion of an exemplary registry of virtual containers; 1 provides an overview of methods for creating and using a registry of virtual containers, according to some embodiments; Embodiments of networks are described. Provide a general description of communication between devices. 1 provides a block diagram of an exemplary computing device in accordance with some embodiments; FIG. 9 provides a schematic description of one embodiment of a computing device 900 that may implement various steps of methods provided by various embodiments.

In embodiments, the present invention provides a system, method, and method for facilitating end-user access to a virtual reality world and, optionally, obtaining supplemental content (external content) within the virtual reality world. The Company provides computer program products. As used herein, the terms virtual world, virtual reality world, virtual container, virtual reality container, virtual experience, virtual reality experience, virtual environment, virtual reality environment, and the like refer to locations such as those on Earth or the Moon. Interchangeably refers to a software or computer-generated environment containing images and/or sounds for simulating the presence of a user within a physical environment, which may represent an actual location in space or may represent a fictional world. Typical outputs of virtual reality worlds include, but are not limited to, visual representations of virtual worlds and audio representations of virtual worlds. The visual representation may at least partially overlap the audio representation, or may include text or other information that may represent the audio representation. Similarly, the audio representation may include audio information that may at least partially overlap or represent information contained within the video representation. Other outputs such as tactile or haptic feedback may be generated for perception by the user. In some virtual worlds the physics laws may be set to match those of reality, while in other virtual worlds the physics laws may be modified from reality or otherwise different from reality. Inputs to the virtual container may represent the user's position, orientation, viewpoint, or interaction with the virtual reality. The user may also represent user-generated audio and/or video, such as audio obtained from the end-user virtual reality system or video information obtained by a video capture device associated with the end-user virtual reality system. Source content may be provided as input to the virtual container.

It will be appreciated that the software or computer that generates the virtual environment may be remote from the user and the output representing the virtual environment may be transmitted to the end-user virtual reality system, such as across one or more wired or wireless network links. Will. The software or computer that generates the virtual environment may co-exist with the end-user, may reside within an end-user virtual reality system such as a headset, may reside as part of the end-user virtual reality system, or may It will also be appreciated that there may be partial data communication with the end-user virtual reality system. In some embodiments, the virtual environment may be provided by the end-user system as executable or program instructions, which may be referred to as a kernel. Executable or program instructions may be implemented or otherwise executed by an end-user system to provide output to the user, such as video, audio, haptic, and/or tactile output. In some embodiments, the executable or program instructions are an intermediary between an end-user virtual reality device or system and a remote server, such as a service provider system, to provide output for use by the end-user system. It may be implemented or otherwise performed by the system. It will also be appreciated that in some embodiments executable or program instructions may be provided on a non-transitory computer-readable storage medium such as a flash drive, CD, DVD, or the like. Optionally, executable or program instructions may be included within one or more data transmissions across a network and stored on non-transitory computer-readable storage media local to the end-user virtual reality system.

FIG. 1 provides a schematic illustration of a netting environment 100 . Here, end-user VR system 105 connects to network 110 . In some embodiments, network 110 may allow devices to establish two-way communications for data transfer between devices. Network 110 is intended to represent any number of terrestrial or non-terrestrial network facilities or elements. For example, network 110 may be, for example, a WAN (Wide Area Network) network, a HAN (Home Area Network) network, a LAN (Local Area Network) network, a WLAN (Wireless Local Area Network) network, the Internet, a cellular communications network, and/or a network. Any of various wireless and/or hardwired package-based communication networks, such as any other type of communication network configured to allow data to be transferred between or between individual elements of environment 100 number of features or elements may be incorporated or presented.

Network environment 100 also includes service providers 115 that may host or otherwise provide or include service provider virtual reality containers 120 . Service provider 115, in some embodiments, may act as an intermediary between end-user system 105 and one or more other remote VR providers 125 and 130, which in turn, remote virtual reality container 135 and 140 may otherwise be provided or included.

Network environment 100 also includes virtual container registry server 145 . Virtual container registry server 145 may create, host, or otherwise provide or include a registry of virtual containers. It will be appreciated that virtual container registry server 145 may be part of or included in service provider 115 or another entity, server, or device in communication with network 110 . A virtual container registry server may allow the creation or modification of entries in a registry of virtual containers. The virtual container registry may be replicated in whole or in part on other devices or servers that communicate with network 110 . A registry of virtual containers may exist as a distributed system or database on multiple servers in communication with the network 110, eg, analogous to aspects of the Domain Name System where updates to the registry may propagate from server to server.

FIG. 2 provides a schematic illustration of communications between different devices that may be included within network environment 100 . For example, FIG. 2 shows communication between end-user VR system 200, service provider 204, virtual container registry server 208, and remote VR providers 212 and 216. FIG.

Each end user 200 may send a connection request 220 to service provider 204, such as a request to establish a VR session. Service provider 204 may respond with connection response 224 . Optionally, the service provider 204 sends a registry query 208 to the virtual container registry 208 to query the virtual container registry for one or more remote VR container registries 208 that may be available or accessible to the end user system 200 . can. Registry queries 228 may include information about end-user system 200 and/or users associated with end-user systems, such as credentials, tokens, or characteristics of end-user system 200 or users. The virtual container registry 208 may generate a registry response 232, which may be received by the service provider 204 and includes an identifier, portal information, or other useful information about the remote VR container or its connection with the remote VR session. It may include how the VR session is established.

The connection request 220 and connection response 224 provide a handshake between the end user system 200 and the service provider 204 to establish a service provider VR session 228, which represents the user's entry into the service provider's 204 VR container. can be expressed Service provider VR session 228 may represent a two-way communication between end-user VR system 200 and service provider 204, which may also be referred to herein as a network connection. Service provider VR sessions 236 may allow virtual worlds accessible by end-user VR systems to contain one or more portals that represent entry points to remote VR containers.

End user system 200 may send portal access instruction 240 to service provider 204 representing a request to enter a particular remote VR container, such as the VR container associated with remote VR provider 212 . In response to the portal access instruction 240, the service provider 204 may send a connection request 244 to the remote VR provider 212, eg, a request to establish a VR session. Remote VR provider 212 may respond with connection response 248 . Connection request 244 and connection response 248 may represent a handshake between end user system 200 and remote VR provider 212 via service provider 204 to establish VR session 252 . Optionally, service provider 204 may implement conversion 256 of aspects of remote VR session 252 , such as when end user system 200 is at least partially incompatible with the VR container of remote VR provider 212 .

In some embodiments, the user may wish to move from the remote VR session 252 to another remote VR container, so the end user system 200 may optionally send a quit command 260 and go to another portal. Access instructions 264 may be transmitted. It will be appreciated that the portal access command 264 can be sent while the remote VR session 252 is active or at the time the remote VR session 252 is sent. In some embodiments, termination of remote VR session 252 causes end user system 200 and service provider 204 to re-establish service provider session 236 or establish a new service provider VR session.

In some embodiments, end user system 200 may be compatible with a remote VR container, such as a VR container associated with remote VR provider 216 . In these or other situations, service provider 204 may send remote VR container information 268 to end user system 200 in response to portal access instruction 264 . Remote VR container information 268 may include instructions or information on how to connect or establish a VR session with remote VR container 216 . Optionally, service provider 204 may send registry query 272 and receive registry response 276 to obtain some or all of the information contained within remote VR container information 268 .

To establish a VR session, end user system 200 may send connection request 280 to remote VR provider 216 . Remote VR provider 216 may respond with connection response 284 . Connection request 280 and connection response 284 may represent a handshake between end user system 200 and remote VR provider 216 to establish remote VR session 288 .

It will be appreciated that FIG. 2 provides only one example of how connections are established for a VR session and how communications are exchanged between devices. connection requests and responses for different remote VR sessions occur in different orders, conversions may or may not occur, direct connections between the end-user system 200 and the remote VR provider may occur, etc. Other variations on the communications described in FIG. 2 will be appreciated in view of the drawings and description above.

FIG. 3 provides an overview of an exemplary method 300 that may be implemented by, for example, a service provider or service provider server. At block 305, a service provider VR container connection is established. At block 310, one or more portals are determined. At block 315, one or more portals are populated in the service provider VR session. At block 320, an access instruction for access to the first portal is detected. At block 325, a first remote container connection is established or facilitated . At block 330, an access instruction for access to the second portal is detected. At block 335, a second remote container connection is established or facilitated .

FIG. 4 provides a schematic illustration of a portion of an exemplary registry 400 of virtual containers 400 . The virtual container registry 400 includes multiple entries, each represented as a separate row 405-440 in FIG. Registry 400 may correspond to or include a database, for example. The columns in FIG. 4 represent the different components of each entry, and exemplary components such as identifiers, requirements, constraints, and features are described.

The virtual container registry 400 may be organized hierarchically. For example, row 410 may represent top-level items in the registry. Registries 405 and 425 may be organized to exist as second level items below the top level of row 410 . This organization may not represent the physical organization of data within registry 400, but may represent relationships between different entries within the registry. Row 415 may represent third level items organized under second level items such as row 405 . Similarly, row 430 may represent third level items organized under second level items such as row 425 . It will be appreciated that the organization of items in a hierarchy may allow related items to be grouped together within the hierarchy. In some embodiments, items in registry 400 may be under different hierarchies at the same time.

It will be appreciated that the identifiers shown in registry 400 are merely exemplary names for identifying particular VR containers. Any number of identifiers may be included within an entry. Other identifiers such as domain names, Internet or IP addresses, publishers, etc. may be useful.

It will be appreciated that the requirements shown in registry 400 are exemplary only. Any number of requirements may be included within an entry. Where a requirement of "any" is indicated, this means that the VR container is compatible with any VR system, such as by having the container dynamically rely on a particular VR system to provide output. You can point to getting. At line 420, for example, the historical world container is depicted as requiring a particular operating system, such as Android version 5 or greater, or iOS version 7 or greater. Lines 435 and 440 explain that only certain systems are supported by their virtual containers, namely the Oculus Rift system and the Sony PlayStation VR system.

It will be appreciated that the constraints shown in registry 400 are exemplary only. Any number of constraints may be included within an entry. At line 420, the Historical World is indicated as having English language restrictions, users who do not support English may not be allowed to enter the Historical World, and a password is required to obtain entry. indicates that the Lines 435 and 440 describe the age restrictions, between 3:00 and 9:00 pm entry must be 13 or older, and for all other times entry must be 18 or older. Indicates that age is required.

It will be appreciated that the features shown in registry 400 are exemplary only. Any number of features may be included within an entry, with the flexibility of pointing to any kind of other information related to a particular VR container. For example, a feature may identify a linked VR container. A characteristic may identify a user associated with a VR container. A feature may identify a rating associated with a VR container. A feature may identify that an advertisement is shown within the VR container. A feature may identify that a VR container represents a shopping or trading container. Other features are possible.

FIG. 5 provides an overview of an exemplary method 500 for creating and using a registry of virtual containers. At block 505, a registry of virtual containers is instantiated. An additional query is received at block 510 . At block 515, a new entry corresponding to the add query is added to the virtual container's registry. At block 520, a change query is received. At block 525, the entry is modified based on the change query. At block 530, a query, such as an information query, is received. At block 535, query results are determined. At block 540, an output is generated that includes the query results. Other queries are possible, including delete queries to remove entries from a virtual container's registry.

Content providers or content provider systems may use the aspects of FIG. 5 to publish changes related to their VR containers to the registry. For example, a content provider or content provider system may wish to update, add, lock, or delete one or more registry entries. A registry entry may, for example, have an associated authorization token to identify a controlling entity that modifies or may modify the registry entry. In this manner, an entity may be able to control changes to registry entries.

Watching a sporting event, which may optionally relate to a real-world sporting event (such as a Super Bowl party) or may relate to a virtual event, is one example of a VR container that may demonstrate various aspects of the mechanisms and techniques described herein. End-users may desire to host and/or participate in virtual events such as social gatherings. Various scenarios of virtual containers for such virtual events are possible, including user sponsored containers, service provider sponsored containers, broadcaster or sponsor sponsored containers, and the like. Such virtual containers may be listed in a registry of virtual containers, as described above, to facilitate end-user installation and access to virtual containers. Such virtual containers may be publicly accessible, or may be accessible only to users who meet appropriate restrictions (eg, permissions, authentication, etc.). Since some end-users accessing virtual containers are remote and access virtual containers across a network, mechanisms can be commonly applied for each hosted scenario.

FIG. 6 illustrates an embodiment of network environment 600 . Network 600 may overlap, at least in part, with or share components or aspects with network environment 100 described above with respect to FIG. In FIG. 6, a first end-user VR system 605 and a second end-user VR system 610 each connect to network 615 . In some embodiments, network 615 may allow devices to establish bi-directional communication paths for data transfer between devices. Network 615 is intended to represent any number of terrestrial and/or non-terrestrial network facilities or elements. For example, network 615 may be, for example, a WAN (Wide Area Network) network, a HAN (Home Area Network) network, a LAN (Local Area Network) network, a WLAN (Wireless Local Area Network) network, the Internet, a cellular communication network, and/or a network. Any number of various wireless or hardwired package-based communication networks, such as 600 individual elements or any other type of communication network configured to allow data to be transferred between the elements. Features or elements may be incorporated or presented.

Network environment 600 also includes VR provider 620 that may host or otherwise provide or include virtual reality container 625 . As explained above, a VR provider may be user-sponsored, service-provider-sponsored, broadcaster-sponsored, and so on. VR provider 615 may optionally be associated with, or directly connected to, or part of an end-user VR system, which may be different from end-user VR systems 605 and 610 .

With respect to the example virtual event described above, VR container 625 may correspond to a sporting event viewing party, e.g., end-users associated with end-user VR systems 605 and 610 concurrently attend a sporting event viewing. It can be a virtual reality world built as a living room to allow As an example, a sporting event may be provided within a VR container as a window or portal presenting a broadcaster's display, stream, or video transmission of the sporting event. Such a scenario, for example, could be seen as a representation of commonly available content, such as 2D or 3D video in a virtual reality world as viewed on a television screen, but by the participating end-users. Other embodiments are possible, such as where the commonly shared or viewed event or content corresponds to the virtual reality experience of another virtual reality container.

VR provider 625 may establish network connections 650 and 655 with end-user VR systems 605 and 610 to establish a VR session, and for VR systems 605 and 610 to render output corresponding to VR container 625: Data streams may be provided to end-user VR systems 605 and 610 . Such data streams may be, for example, instruction sets for use in the end-user VR system 605 or 610, audio streams, video streams, text streams for direct output or conversion to the end-user VR system 605 and 610. , metadata, haptic data, and the like. In the sporting event viewing party described above, the VR session established between the VR provider 625 and the end-user VR systems 605 and 610 allows the end user to view a living room with windows or portals displaying the broadcast stations of the sporting event. to watch, listen to, interact with, and/or otherwise experience. Network connections 650 and 655 may be provided via network 615 and may include, for example, Transmission Control Protocol (TCP) connections across packet-switched networks.

End user systems 605 and 610 may be able to apply or provide preferences and permissions to allow customization of the VR container as desired. For example, an end-user system may identify a preference for the colors of a particular sports team included within the visual living room decoration. The end-user system may also identify accessibility mechanisms to be activated within the output provided at the end-user system.

End-user systems 605 and 610 may each provide user-sourced content streams to other devices within network environment 600 . For example, end user systems 605 and 610 may provide audio streams corresponding to audio captured by microphones of end user systems 605 and 610 . These user-sourced content streams are, for example, transferred between the end-user system and the VR provider 620 such that the VR provider 620 may include a portion (eg, audio) from the user-sourced content stream as part of the VR container 625 . can be provided. Optionally, user-sourced content streams can be communicated directly from one end-user VR system to another. VR provider 620 may provide network address information from one or more end-user VR systems 605 or 610 and/or other information that enables end-user VR systems 605 or 610 to exchange data with each other over network 615. may facilitate such exchanges, such as by providing information about

Depending on the configuration, permissions, and preferences associated with end-user systems 605 and 610 and VR container 625, modification of user-sourced content streams can occur. By way of example, audio within a user-sourced content stream may be translated from one language to another, converted to text or video description, filtered, amplified or shortened, and so on. Similarly, if the user source content stream contains video or image information, the video or image information may be converted to another format, may be audio or text descriptions, may be converted to alternative color spaces, may be filtered, get and so on. In this way, users with different preferences or permissions may be allowed to communicate with each other or to accommodate users with accessibility needs (e.g., blind, partially sighted, deaf, or hard of hearing for the user). It can be adapted such as to allow different languages to be spoken. User preferences may or may not apply depending on context and configuration. Transformation of the user-sourced content stream may occur at one or more devices of network environment 600 , such as end-user systems 605 or 610 or VR provider 620 .

Other remote devices, such as supplemental content providers 635 or 645, may also provide variations of user-sourced content streams. For example, supplemental content provider 635 may represent a virtual or network transformation service provider. A data stream, such as a user-sourced content stream, may be received at a supplemental content provider 635 , which subsequently transforms the received data stream into a supplemental content stream 630 , which is one of the VR containers 625 . For example, it may be provided to the VR provider 620, or provided directly to the end-user system 605 or 610, for inclusion as part or the like.

Returning to the example event of a sporting event viewing party as described above, a window or portal is included within the VR container 625 to allow participating end-users to view videos of the sporting event. obtain. Such broadcasts may optionally correspond to supplemental content added to VR container 625 . Optionally, one or more end-users may provide videos as supplemental content. Optionally, VR provider 620 may directly provide or obtain video as supplemental content, such as in response to requests for supplemental content received from one or more end-user VR systems.

In some embodiments, supplemental content provider 635 may provide video as supplemental content stream 630 . Optionally, the VR provider may communicate to supplemental content provider 635 a request for supplemental content stream 630 corresponding to the video displayed in the window or portal within VR container 625 . Optionally, end-user VR system 605 or 610 may communicate a request for the video, which may be received at VR provider 620 and relayed to supplemental content provider 635 or communicated directly to supplemental content provider 635 . Optionally, supplemental content providers 635 may provide supplemental content 630 directly to end-user VR systems 605 or 610 by providing one or more network addresses of devices within network environment 600 to each other. Etc. may be facilitated by the VR provider. It will be appreciated that videos of sporting events displayed within a window or portal within VR container 625 are but one example of supplemental content that may be added to VR container 625 . By way of example, audio content, video or image content, textual content, haptic content, and any other variety of visual data or information may be useful supplemental content added to VR container 625 . Other examples are possible, including variations of the user-sourced content stream, as described above. In content for watching sporting events, users may wish to receive fantasy sports league information and may request such information from fantasy sports league providers corresponding to supplemental content providers 635 . Fantasy sports league information may be provided as a supplemental content stream 630 and rendered as output by the end-user VR system 605 or 610, such as appended by the VR container 625 or overlaid on the output corresponding to the VR container 625. may correspond to rendered text, audio, video, and/or image information.

Still other examples of supplemental content streams are possible, including content from supplemental VR containers, such as supplemental content container 640 provided by supplemental VR provider 645 . In this manner, any variety of visual information or content may be added to VR container 625, such as by VR provider 620 or directly by end user system 605 or 610. FIG. As an example relating to the sporting event viewing party described above, supplemental VR container 640 may correspond to a virtual world representing a stadium where a sporting event is taking place. A representation of the stadium may be added to or included within the living room associated with the VR container 625, e.g., when a user entering a door in the living room explores the stadium in the virtual setting. , and/or otherwise allowed to be experienced. Such representations can be provided as portals to the supplemental VR container 640 or by directly modifying the VR container 625 to include the mechanisms provided by the supplemental VR container.

FIG. 7 provides a schematic illustration of communications between devices that may be included in network environment 600 . For example, FIG. 7 shows communication between end-user VR systems 700 and 704, VR provider 708, and supplemental content providers 712 and 716. As shown in FIG.

End user VR system 700 may send access request 720 , such as a request to establish a VR session, to VR provider 708 . VR provider 708 may establish a network connection 724 with end-user VR system 700, which may at least partially accommodate a VR session. Similarly, end-user VR system 704 may send access request 728 to VR provider 708, such as a request to establish a VR session. A VR provider 708 may establish a network connection 724 with an end-user VR system 700, which may at least partially accommodate a VR session. It will be appreciated that access or communication may optionally be exchanged with the virtual container registry to enable establishment of a VR session. One or more subsequent communications between the end-user VR system 700 and the VR provider 708 are transmitted using the network connection 724 and one or more between the end-user VR system 704 and the VR provider 708 It will also be appreciated that subsequent communications of are transmitted using network connection 732 . With respect to the virtual sporting event viewing party described above, these aspects involve end-user VR systems 700 and 704 establishing a VR session with a virtual living room so that end-users can participate in the sporting event viewing party. can correspond to

End-user VR system 700 may send supplemental content request 736 to VR provider 708 . In response to supplemental content request 736, VR provider 708 may send supplemental content request 740 to supplemental content provider 712, and supplemental content provider 712 may provide supplemental content 744 to the VR provider. VR provider 708 may then relay or facilitate supplemental content 744 being provided to end-user VR system 700 and, optionally, end-user VR system 704 . As described, supplemental content provider 712 transmits supplemental content 744 directly to end-user VR system 704 while VR provider 708 transmits supplemental content 744 to end-user VR system 700 . As an example for a virtual sporting event viewing party, such a request would be heard by all users present in the virtual living room, such as providing background music that is otherwise available to all users. User's desire to access supplemental VR containers within may be accommodated. In this manner, users may be able to obtain supplemental content for presentation to all participating users within the virtual container.

The end-user VR system 704 may send another supplemental content request 748 to the VR provider 708 and may, for example, receive a response 752 that may facilitate the end-user VR system 704 to obtain the desired supplemental content. For example, response 752 may provide a network address or other information (eg, instructions) to obtain the desired supplemental content. As described, the end-user VR system 704 may send the supplemental content request 748 directly to another supplemental content provider 716, which in turn sends the supplemental content 756 back to the end-user VR system. . As an example for a sporting event viewing party, the request may only be provided to the end-user VR system 704, such as overlaid on a video display of the living room environment associated with the virtual container. It can correspond to statistical information. In this way, users may be able to obtain supplemental content for their presentation only, without affecting the experience of other users. Such techniques may also be useful for accessibility mechanisms, for example, as described above.

FIG. 7 also illustrates the transmission of user-sourced content streams 760 from end-user VR system 700 to VR provider 708 . To facilitate the transmission of this information to the end-user VR system 704, in order for the end-user VR system 704 to transmit the user content stream 760 directly to the end-user VR system 704, the VR provider 708 provides the end-user VR system Network address information 764 associated with 704 may be provided to the end-user VR system 700 . As noted above, such a configuration is the only way VR provider 708 can facilitate communication of data between end-user VR systems. In another example, end-user VR system 704 may transmit user-sourced content stream 768 to VR provider 708 , which in turn may relay user-sourced content stream 768 to end-user VR system 700 .

It will be appreciated that FIG. 7 provides an example of how network connections are established and how communications are exchanged between devices. Supplemental content requests are sent to different systems or in different orders, and supplemental content is generated in response to sending requests or data streams to generate transformed data streams as supplemental content streams. etc., other variations on the communications and network connections described in FIG. 7 will be appreciated in light of the above description.

FIG. 8 provides an overview of an exemplary method 800 for accessing a virtual container and obtaining supplemental content from within the virtual container. At block 805, a first request to access a VR container is received, such as from a first end-user VR system. At block 810, a first network connection is established, such as with a first end-user VR system. At block 815, output corresponding to the VR container, such as by sending the VR container output stream, or by sending instructions to directly generate the VR container output stream by the first end-user VR system. Access to data for rendering is provided over the first network connection.

At block 820, a second request to access the VR container is received, such as from a second end-user VR system. At block 825, a second network connection is established, such as with a second end-user VR system. At block 830, output corresponding to the VR container, such as by sending the VR container output stream, or by sending instructions to directly generate the VR container output stream by the second end-user VR system. Access to the data for rendering is provided over the second network connection. At block 835, a third request to access the supplemental content stream is received from the first end-user VR system, the second end-user VR system, or the like.

At block 840, access by the first end-user VR system is facilitated to the supplemental content stream via the first network connection. At block 845, access by a second end-user VR system is facilitated to the supplemental content stream via the second network connection. Facilitating access to the supplemental content stream optionally includes obtaining the supplemental content stream and transmitting the supplemental content stream or data derived from the supplemental content stream, such as over a network connection. . Facilitating access to the supplemental content stream includes including at least a portion of the supplemental content stream within data for rendering output corresponding to the VR container. Facilitating access to the supplemental content stream optionally includes transmitting a network address for a remote server providing the supplemental content stream. In this manner, the first or second end-user VR device may obtain the supplemental content stream directly from the remote server.

transmitting the user-sourced content stream by transmitting a network address of an end-user VR system that provides the user-sourced content stream to another end-user VR system by receiving and transmitting at least a portion of the user-sourced content stream; or by transmitting the network address of the end-user VR system to another end-user VR system that provides the user- sourced content stream. In this manner, the user-sourced content stream may be relayed or allowed to be obtained directly from the source end-user VR system that generates the user-sourced content stream.

Computing devices such as those described in FIG. 9 may be previously described, such as end-user VR systems 105 and 200, service providers 115 and 204, remote VR providers 125, 130, 212, and 216, virtual container registry servers 145 and 208, and so on. can be incorporated as part of a device that FIG. 9 provides a schematic illustration of one embodiment of a computing device 900 that can implement various steps of methods provided by various embodiments. It should be noted that FIG. 9 is intended only to provide a general description of various components, any or all of which may be utilized as appropriate. FIG. 9 thus broadly illustrates how individual system elements can be implemented in a relatively discrete or relatively integrated manner.

Computing device 900 is described as including hardware elements that may be electrically coupled (or otherwise communicated) via bus 905 . Hardware elements include one or more processors 910 including, but not limited to, one or more general purpose processors and/or one or more special purpose processors (such as digital signal processing chips, graphics acceleration processors, and/or video decoders). and one or more input devices 915, which may include, without limitation, a mouse, touch screen, keyboard, remote control, and/or voice input, etc.; and one, which may include, without limitation, a display device, printer, speakers, etc. and an output device 920 as described above.

Computing device 900 may include, without limitation, local and/or network accessible storage, and/or programmable and/or instantaneously updateable disk drives, drive arrays, optical storage devices, solid state drives ( one or more non-transitory storage devices 925, which may include, but are not limited to, solid state storage devices such as "SSD"), random access memory ("RAM"), and/or read only memory ("ROM"); It may further include (and/or communicate with). Such storage devices may be configured to implement any suitable data store including, but not limited to, various file systems and/or data structures.

Computing device 900 may include modems, network cards (wireless or wired), infrared or optical communication devices, wireless communication devices, and/or chipsets (Bluetooth devices, BLE, 802.11 devices, 802.15. 4 devices, WiFi devices, WiMax devices, cellular communication devices, etc.) and/or G.4 devices. A communications subsystem 930 may also be included, which may include, but is not limited to, hn devices and the like. Communications subsystem 930 allows data to be exchanged with networks (such as the networks described below, by way of example), other computing systems, and/or any other devices described herein. can be In many embodiments, computing device 900 will further include working memory 935, which may include RAM or ROM as described above.

Computing device 900 may include an operating system 940, device drivers, executable libraries, and/or computer programs provided by various embodiments as described herein and/or other embodiments. shown as currently residing in working memory 935, including other code such as one or more application programs 945 that may be designed to implement methods and/or configure systems provided by It may also include software elements. Merely by way of example, one or more of the procedures described with respect to the methods discussed above may be implemented as code and/or instructions executable by a computer (and/or a processor within a computer); /or the instructions may be used to configure and/or adapt a general-purpose processor (or other device) to perform one or more operations in accordance with the described methods.

These sets of instructions and/or code may be stored on a non-transitory computer-readable storage medium, such as non-transitory storage device 925 described above. In some cases, the storage media may be incorporated within a computer system, such as computing device 900 . In other embodiments, the storage medium is not a computer system, such that the storage medium can be used to program, configure, and/or adapt a general-purpose computer with instructions/code stored on them. It may be separate (eg, a removable medium such as a compact disc, or a cloud or network-based storage system) and/or provided within an installation package. These instructions may take the form of executable instructions that are executable by the computing device 900 and/or (eg, any of the commonly available compilers, installation programs, compression/answer utilities, etc.). may take the form of source or installable code, which when compiled and/or installed on the computing device 900, takes the form of executable code.

It will be apparent to those skilled in the art that substantial variations may be made according to specific requirements. For example, customized hardware may also be used and/or specific elements may be implemented in hardware, software (including portable applications such as applets), or both. Additionally, connections to other computing devices such as network input/output devices may be used.

As noted above, in one aspect, some embodiments may employ a computing device (such as computing device 900) to perform methods in accordance with various embodiments of the invention. According to one set of embodiments, the procedures of some or all of these methods are contained in working memory 835 (and may be embedded in other code such as operating system 940 and/or application programs 945). Performed by computing device 900 in response to processor 910 executing one or more sequences of the foregoing instructions. Such instructions may be read into working memory 935 from another computer-readable medium, such as one or more of non-transitory storage media 925 . By way of example only, execution of the sequences of instructions contained in working memory 935 may cause processor 910 to perform one or more of the methods described herein.

The terms "machine-readable medium," "computer-readable storage medium," and "computer-readable medium," as used herein, refer to any medium that participates in providing data that causes a machine to operate to specific specifications. point to These media can be non-transitory. In an embodiment implemented using computing device 900, the computer-readable media may involve providing and/or storing and/or carrying such instructions/code to processor 910 for execution. can be used to In many implementations, a computer-readable medium is a physical and/or tangible medium. Such media can take the form of non-volatile media or volatile media. Non-volatile media includes, for example, optical and/or magnetic disks, such as non-volatile storage device 925 . Volatile media includes, without limitation, dynamic memory, such as working memory 935 .

Common forms of physical and/or tangible computer readable media include, for example, floppy disk, floppy disk, hard disk, magnetic tape, or any other magnetic medium, CD-ROM, any other optical medium, mark Any other physical medium having a pattern, RAM, PROM, EPROM, Flash EPROM, any other memory chip or cartridge, or any other form of media from which instructions and/or code can be read by a computer. Network-based and cloud-based storage systems can also be useful forms of computer-readable media.

Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to processor 910 for execution. By way of example only, the instructions may initially be executed on a magnetic and/or optical disk of the remote computer. A remote computer may load instructions into its dynamic memory and may transmit the instructions over the transmission medium as signals to be received and/or executed by computing device 900 .

Communication subsystem 930 (and/or its components) typically receives signals, and bus 905 may subsequently carry the signals (and/or the data, instructions, etc. carried by the signals) to working memory 835 . , processor 910 retrieves from working memory 935 and executes the instructions. The instructions received by working memory 935 may optionally be stored on non-transitory storage medium 925 either before or after execution by processor 910 .

It should further be appreciated that the components of computing device 900 may be distributed across a network. For example, some processing may be performed locally using a first processor, while other processing may be performed by another processor remote from the first processor. Other components of computing device 900 may be similarly distributed. As such, computing device 900 may be construed as a distributed computing system that performs processing at multiple locations. in some instances. Computing device 900 can be interpreted as a single computing device, such as separate laptops or desktop computers, depending on the content.

All references throughout this disclosure, e.g., issued or granted patents or equivalents, patent literature, including patent application publications, and non-patent literature records, or other underlying material, are the following patents and patent application publications: U.S. Pat. and PCT International Application Publication No. WO2009/039080, which when individually incorporated by reference are hereby incorporated by reference in their entireties.

All patents and publications mentioned in this disclosure are indicative of the levels of those skilled in the art to which the invention pertains. The references cited herein, in some cases, are incorporated by reference in their entirety to indicate the state of the art as of their filing date, and to exclude specific embodiments that are prior art. It is intended that this information may be used herein if desired (eg, to disclaim).

Where groups of subroutines are disclosed herein, all individual members of those groups and all subgroups and classes that can be formed using the subroutines are separately disclosed. When a Markush group or other grouping is used herein, all individual components of the group and all possible combinations and subcombinations of the group are intended to be individually included in the disclosure. As used herein, "and/or" includes in the list one, all, or any combination of the items in the list separated by "and/or", e.g. "1, 2 and/or 3" means "1" or "2" or "3" or "1 and 2" or "1 and 3" or "2 and 3" or "1, 2 and 3" intended to be equal to

Any combination of the components described or illustrated can be used to practice the invention unless stated otherwise. Specific names of devices and components are intended to be exemplary, as persons skilled in the art are known to name the same device or component differently. It will be appreciated that methods, device elements, and systems other than those specifically illustrated can be used in practicing the invention without resort to undue experimentation. All known functional equivalents of any such methods, device elements, and systems are intended to be included in this disclosure. Whenever a range is given in the above description, the disclosure is intended to include all intermediate ranges and subranges, as well as all individual values falling within that given range.

As used herein, "comprising" is synonymous with "including," "containing," or "characterized by," and is inclusive. , or without limitation, does not exclude additional, unrecited elements or method steps. As used herein, "consisting of" excludes any element, step, or ingredient not specified in the claim element. As used herein, "consisting essentially of" does not exclude materials or steps that do not materially affect the underlying novel features of the claim. References herein to the term "comprising", particularly in describing methods, components of systems, or elements of devices, refer essentially to and consist of the features for which they are quoted. is understood to include Aptly, the invention illustratively described herein may be practiced in the absence of any one or more elements or limitations not specifically disclosed herein.

The methods, systems, and devices disclosed above are exemplary. Various configurations may omit, substitute, or add various method steps or procedures, or system components as appropriate. By way of illustration, in alternative arrangements, the method may be performed in a different order than described, and/or various stages or steps or modules may be added, omitted, and/or combined. . Also, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of construction may be combined in a similar manner. Also, technology evolves and, therefore, many of the elements are illustrative and do not limit the scope of the disclosure and claims.

Specific details are given in the description to provide a thorough understanding of example configurations (including implementation). However, configurations may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have not been shown in unnecessary detail to avoid obscuring the configurations. This description provides example configurations only and does not limit the scope, applicability, or configurations of the claims. Rather, the preceding description of the configurations will provide those skilled in the art with an effective description for implementing the described techniques. Various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure.

Also, configurations may be described as processes depicted as flow diagrams or block diagrams. Each may describe the operations as a continuous process, and many of the operations may be performed in parallel or concurrently. Also, the order of operations may be rearranged. A process may have additional steps not included in the figure. Further, example methods may be implemented in hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments to perform the necessary tasks may be stored in a non-transitory computer-readable medium such as a storage medium. A processor may perform the described tasks.

Further, the examples described herein can be implemented as logical operations on computing devices within a networked computing system environment. Logical operations may be implemented as (i) a series of computer-implemented instructions, steps, or program modules running on a computing device and (ii) interconnected logical or hardware modules running within a computing device. .

Although the subject matter has been described in language specific to structural features and/or methodological acts, the subject matter defined in the appended claims need not be limited to the specific features or acts described above. should be understood. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

The terms and expressions that have been employed are used as terms of description rather than of limitation, and there is no intention that such terms or expressions exclude any equivalents or portions thereof of the features shown or described. No, but it is understood that various modifications are possible within the scope of the claimed invention. Thus, while the present invention has been specifically disclosed in terms of preferred embodiments and optional features, it is understood that modifications and variations of the concepts disclosed herein can be made by those skilled in the art and such modifications It should be understood that modifications and variations are considered within the scope of this invention as defined by the appended claims.

Claims (23)

receiving by a computing device a first request for access to a virtual reality (VR) container from a first end-user VR system;
establishing a first network connection with the first end-user VR system;
using the first network connection to facilitate access by the first end-user VR system to data for rendering output corresponding to the VR container;
receiving a second request for access to the VR container from a second end-user VR system;
establishing a second network connection with the second end-user VR system;
using the second network connection to facilitate access by the second end-user VR system to data for rendering output corresponding to the VR container;
receiving a third request for access to a supplemental content stream within the VR container;
using the first network connection to facilitate access by the first end-user VR system to the supplemental content stream;
and using the second network connection to facilitate access by the first end-user VR system to the supplemental content stream. The supplemental content stream may be a user-sourced content stream generated by the end-user VR system, a data stream associated with the second VR container, an audio stream, a video stream, a text stream, metadata associated with the end-user VR system. , metadata associated with the VR container, or accessibility data. The supplemental content stream includes supplemental audio information overlaid on an audio stream associated with the VR container, or the supplemental content stream includes video information overlaid on a video stream associated with the VR container. 2. The method of claim 1, comprising: 2. The method of claim 1, wherein facilitating access to the supplemental content stream comprises obtaining the supplemental content stream and transmitting the supplemental content stream or data derived from the supplemental content stream. described method. 2. The method of claim 1, wherein facilitating access to the supplemental content stream comprises including at least a portion of the supplemental content stream within the data for rendering output corresponding to the VR container. . 2. The method of claim 1, wherein facilitating access to the supplemental content stream comprises transmitting a network address for a remote server providing the supplemental content stream. 2. The method of claim 1, wherein the supplemental content stream comprises a user-sourced content stream generated by an end-user VR system. 2. The method of claim 1, wherein the supplemental content stream is other than a user-sourced content stream generated by an end-user VR system. 2. The method of claim 1, further comprising receiving a first user-sourced content stream transmitted by said first end-user VR system. The first user-sourced content stream comprises an audio stream obtained by the first end-user VR system, a video stream obtained by the first end-user VR system, and a video stream obtained by the first end-user VR system. VR container location data associated with said first end-user VR system; preferences associated with said first end-user VR system; permissions associated with said first end-user VR system; , or metadata associated with the first end-user VR system. 10. The method of claim 9, further comprising transmitting at least a portion of said first user-sourced content stream to said second end-user VR system. A network address of the first end-user VR system is provided to the second end-user VR system to facilitate acquisition by the second end-user VR system of at least a portion of the first user-sourced content stream. 10. The method of claim 9, further comprising transmitting to a system. a network of said second end-user VR system for facilitating said first end-user VR system providing at least a portion of said first user-sourced content stream to said second end-user VR system; 10. The method of claim 9, further comprising transmitting an address to said first end-user VR system. 2. The method of claim 1, wherein facilitating access to data for rendering output corresponding to the VR container comprises transmitting a VR container output stream. 15. The method of Claim 14, wherein facilitating access to data for rendering output corresponding to the VR container further comprises generating the VR container output stream. 2. The facilitating access to data for rendering output corresponding to the VR container comprises transmitting a set of instructions for directly generating a VR container output stream by an end-user VR system. The method described in . Facilitating access to data for rendering output corresponding to said VR container provides a VR container output stream, or an instruction set for directly generating a VR container output stream by an end-user VR system. 2. The method of claim 1, comprising sending a network address for a serving remote server. 2. The method of claim 1, wherein the third request includes one or more preferences or permissions associated with the first end-user VR system or the second end-user VR system. The method of claim 1, including one or more of the limitations of any one of claims 2-18. one or more processors;
A non-transitory computer-readable storage medium in data communication with the one or more processors, wherein, when executed by the one or more processors,
receiving a first request for access to a virtual reality (VR) container from a first end-user VR system;
establishing a first network connection with the first end-user VR system;
using the first network connection to facilitate access by the first end-user VR system to data for rendering output corresponding to the VR container;
receiving a second request for access to the VR container from a second end-user VR system;
establishing a second network connection with the second end-user VR system;
using the second network connection to facilitate access by the second end-user VR system to data for rendering output corresponding to the VR container;
receiving a third request for access to a supplemental content stream within the VR container;
using the first network connection to facilitate access by the first end-user VR system to the supplemental content stream;
and using the second network connection to facilitate access by the first end-user VR system to the supplemental content stream. and a computer-readable storage medium. The instructions cause the one or more processors to perform operations corresponding to the method of any one of claims 1-19, or configure the one or more processors to perform the operations. 21. The system of claim 20, wherein: when executed by one or more processors,
receiving a first request for access to a virtual reality (VR) container from a first end-user VR system;
establishing a first network connection with the first end-user VR system;
using the first network connection to facilitate access by the first end-user VR system to data for rendering output corresponding to the VR container;
receiving a second request for access to the VR container from a second end-user VR system;
establishing a second network connection with the second end-user VR system;
using the second network connection to facilitate access by the second end-user VR system to data for rendering output corresponding to the VR container;
receiving a third request for access to a supplemental content stream within the VR container;
using the first network connection to facilitate access by the first end-user VR system to the supplemental content stream;
using the second network connection to facilitate access by the first end-user VR system to the supplemental content stream; A non-transitory computer-readable storage medium. The instructions cause the one or more processors to perform operations corresponding to the method of any one of claims 1 to 19, or configure the one or more processors to perform the operations. 23. The non-transitory computer-readable storage medium of claim 22.

Images