Patent ID: 12197634

DETAILED DESCRIPTION

FIG.1A,FIG.1B,FIG.1C, andFIG.1Dare a sequence of conceptual diagrams illustrating operations performed by an example artificial reality system, in accordance with one or more aspects of the present disclosure. In each ofFIG.1A,FIG.1B, andFIG.1C, artificial reality system100is depicted within or operating on physical environment120. Physical environment120is shown as a room that includes user101and a number of real world or physical objects, including HMD112, window108, seat110, and wall clock114. Other physical objects, such as lamp107and picture109, are included within physical environment120but are not specifically illustrated with physical environment120inFIG.1A. Images of lamp107and picture109are, however, illustrated within artificial reality content122A ofFIG.1A, for example.

Artificial reality system100includes head-mounted display (HMD)112, console106, one or more sensors190, and cameras192A and192B (collectively “cameras192,” representing any number of cameras). Although in some examples, external sensors190and cameras192may be stationary devices (e.g., affixed to the wall), in other examples one or more of external sensors190and/or cameras192may be included within HMD112, within a user device (not shown), or within any other device or system. As shown in each ofFIG.1A,FIG.1B,FIG.1C, andFIG.1D, HMD112is typically worn by user101and includes an electronic display and optical assembly for presenting artificial reality content122A to the user. In addition, HMD112may, in some examples, include one or more sensors (e.g., accelerometers) for tracking motion of the HMD and may include one or more image capture devices, e.g., cameras, line scanners and the like, for capturing image data of the surrounding environment.

Artificial reality system100may use information obtained from a real-world or physical three-dimensional (3D) environment to render artificial reality content for display by HMD112, thereby presenting the content to user101. In each of the examples illustrated inFIG.1A,FIG.1B,FIG.1C, andFIG.1D, user101views and/or is presented with artificial reality content constructed and rendered by an artificial reality application executing on console106and/or HMD112. In the example ofFIG.1A, user101is presented with and/or view the artificial reality content122A. Similarly, inFIG.1B, user101views artificial reality content122B, inFIG.1C, user101views artificial reality content122C, and inFIG.1D, user101views artificial reality content122D. In each case, the artificial reality content may include images of physical objects within physical environment120, including lamp107, window108, and picture109(see artificial reality content122A and122D) or in other situations, the artificial reality content might include few or no images of physical objects (e.g., artificial reality content122B and122C).

Some physical objects, as further described herein, may be special objects or “trigger objects.” A trigger object may be an object that, when certain interactions are performed with respect to such an object, artificial reality system100performs one or more specific or special operations. For instance, in some examples, seat110might serve as a trigger object. In such an example, when artificial reality system100determines that user101has performed a movement that results in user101sitting on seat110, artificial reality system100may determine that the movement qualifies as a trigger action. As another example, when artificial reality system110determines that user101is seated on seat110, artificial reality system100may determine that the user has performed a movement that qualifies as a trigger action. Artificial reality system100may, in response to the trigger action, perform one or more specific operations, which may include presentation of specific artificial realty content within HMD112worn by user101.

In each of the illustrations ofFIG.1A,FIG.1B,FIG.1C, andFIG.1D, console106is shown as a single computing device, such as a gaming console, workstation, a desktop computer, or a laptop. In other examples, console106may be distributed across a plurality of computing devices, such as a distributed computing network, a data center, or a cloud computing system. HMD112, console106, external sensors190, and cameras192, may, as illustrated, be communicatively coupled via network104, which may be a wired or wireless network, such as Wi-Fi, a mesh network or a short-range wireless communication medium. In some examples, user101may use one or more controllers (not shown) to perform gestures or other actions. In such an example, such controllers may be in communication with HMD112using near-field communication or short-range wireless communication such as Bluetooth, using wired communication links, or using another type of communication links. Although HMD112is shown in each ofFIG.1A,FIG.1B,FIG.1C, andFIG.1Das being in communication with (e.g., tethered to) or in wireless communication with, console106, in some implementations HMD112operates as a stand-alone, mobile artificial reality system. As such, some or all functionality attributed to console106in this disclosure may be distributed among one or more user devices, such as one or more instances of HMD112.

In some examples, an artificial reality application executing on console106and/or HMD112presents artificial reality content to user101based on a current viewing perspective for user101. That is, inFIG.1Afor example, the artificial reality application constructs artificial content by tracking and computing pose information for a frame of reference for HMD112, and uses data received from HMD112, external sensors190, and/or cameras192to capture 3D information within the real-word, physical 3D environment120, such as motion by user101and/or tracking information with respect to user101and one or more physical objects, for use in computing updated pose information for a corresponding frame of reference of HMDs112(or another user device). As one example, the artificial reality application may render, based on a current viewing perspective determined for HMD112, an artificial reality environment, including artificial reality content122A having, in some cases, artificial reality content overlaid upon images of physical or real-world objects (e.g., window108). Further, from the perspective of HMD112, artificial reality system100renders artificial reality content based upon the estimated positions and poses for user101and other physical objects.

In the example ofFIG.1A, an in accordance with one or more aspects of the present disclosure, artificial reality system100may present an artificial reality environment including content122A within HMD112. For instance, in an example that can be described with reference toFIG.1A, HMD112, external sensors190, and/or cameras192capture images within physical environment120. HMD112detects information about a current pose of user101. Console106receives such images and information about the current pose of user101and determines the position of physical objects within physical environment120, including user101and seat110. Console106determines, based on the position of physical objects within physical environment120and the pose information, that user101is standing within physical environment120near seat110. Based on the position information and pose information, console106generates artificial reality content122A. Console106causes HMD112to present artificial reality content122A to user101within HMD112in the manner shown inFIG.1A.

Artificial reality system100may detect that user101has performed a trigger action, and in response, present artificial reality content122B. For instance, continuing with the example and referring now toFIG.1B, HMD112, external sensors190, and/or cameras192capture images within physical environment120, and HMD112captures information about a current pose of user101. Console106receives the images and pose information and determines that user101has moved so that user101is sitting on seat110as illustrated inFIG.1B. Console106determines that the movement by user101corresponds to a trigger action. Responsive to the trigger action, console106generates artificial reality content122B. Console106causes HMD112to present artificial reality content122B to user101within HMD112in the manner shown inFIG.1B.

InFIG.1B, artificial reality content122B includes content corresponding to a driving scene, such might be presented for an artificial reality driving game or artificial reality driving experience. Artificial reality content122B includes virtual dashboard141and virtual steering wheel142, which may correspond to objects included within an artificial reality car. A view from such an artificial reality car that is driving along virtual road143is illustrated within artificial reality content122B. In some examples, virtual steering wheel142(or other aspects of artificial reality content122B) might correspond to a physical object possessed by or near user101, but in other examples, virtual steering wheel142might be simply a virtual steering wheel142.

Artificial reality content122B may be chosen by artificial reality system100based on a prior configuration indicating that each time user101sits on artificial reality system100, a game or other artificial reality application corresponding to artificial reality content122B may be presented. In such an example, sitting on seat110may have a consistent and known result, and user101may initiate the artificial reality experience associated with artificial reality content122B by simply sitting on seat110. In other examples, seat110may initiate another type of experience, such as a virtual movie theatre, a virtual safari, or a virtual world, or may initiate an application, such as a communication or video conferencing session. In some examples, sitting on seat110may cause or enable user101to answer a call or video call and enter or initiate teleconference or video conference. In some examples, the experience presented by artificial reality content122may be based on contextual information about user101, such as information from a calendar maintained by user101(a teleconferencing session based on an appointment on the user's calendar, or during on a holiday celebrated by user101, appropriate decorations might be included in artificial reality content122B). In other examples, artificial reality content122B may be based on prior activity by user101(each morning, user101initiates a call to a relative, or spends time reading in a specific artificial reality environment, or on weekends, user101often likes to visit his or her parents' home, or revisit an old memory). To identify the user, HMD112may use biometric information and/or input from user101(e.g., a username or password).

The artificial reality experience presented may also differ based on how the trigger action is performed. For instance, in some examples, sitting on seat110might initiate one type of artificial reality experience, while standing on seat110, might initiate another. In another example, the artificial reality experience may be presented based on the condition of user101, such as might be determined based on biometrics information. For instance, in one such example, a calming artificial reality experience (e.g., a visit to a childhood home) might be presented to user101when HMD112determines that user101exhibits signs of stress. Still further, artificial reality content122B may be chosen based on one or more objects possessed or held in the hand of user101(e.g., a joystick or a steering wheel), as is further described in connection withFIG.6.

Artificial reality system100may perform operations in response to interactions with a user interface. For instance, still continuing with the same example and with reference toFIG.1C, HMD112detects movement and/or gestures performed by user101. Console106receives information about the movements and/or gestures and determines that they correspond to a request to present a user interface. Console106generates artificial reality content122C including user interface menu124. Console106causes HMD112to present artificial reality content122C to user101within HMD112in the manner shown inFIG.1C. Console106may receive indications that user101has performed movements interacting with one or more user interface elements126of user interface menu124. Console106may interpret such movements as commands to perform operations. In response, console106may perform operations to carry out such commands, which may include modifications to artificial reality content122C, such as altering content presented within HMD112or altering configuration options for a game corresponding to the content presented within artificial reality content122B and artificial reality content122C.

Artificial reality system100may determine that user101has performed a de-trigger action, and in response, cease presentation of artificial reality content122C. For instance, still continuing with the example being described, and now with reference toFIG.1CandFIG.1D, HMD112, external sensors190, and/or cameras192capture images and pose information. Console106receives the images and pose information and determines that user101is standing near seat110and is no longer sitting on seat110, as illustrated inFIG.1D. Console106determines that movement by user101corresponds to a de-trigger action. Responsive to detecting the de-trigger action, console106generates artificial reality content122D. In the example being described, the de-trigger action may be, in some respects, the opposite of the trigger action (i.e., standing after sitting in a chair may be considered the opposite of sitting in the chair). Console106causes HMD112to present artificial reality content122D to user101within HMD112in the manner shown inFIG.1D.

InFIG.1D, artificial reality content122D includes content similar to that presented in artificial reality content122A ofFIG.1A. Specifically, artificial reality content122D includes lamp107, window108, and picture109, each of which are presented as images of physical objects from physical environment120. Upon standing up, therefore, user101is presented with artificial reality content122D, which is very similar to artificial reality content122A ofFIG.1A. Accordingly, in the example illustrated inFIG.1AthroughFIG.1D, the effect of user101sitting on seat110(i.e., performing a trigger action) and then standing up after sitting on seat110(i.e., performing a de-trigger action) is that sitting on seat110activates a mode change, causing artificial reality content to be presented. Standing up after sitting on seat110, however, also causes a mode change, such as causing presentation of that artificial reality content to cease (or pause, suspend, hold, or terminate).

In the example described, therefore, user101may use seat110to automatically trigger presentation of a known artificial reality experience simply by sitting on seat110. Sitting on seat110may be an effective, intuitive, frictionless, and natural way to initiate an artificial reality experience, and user101may associate various physical objects (i.e., trigger objects) with various artificial reality experiences that are triggered by performing actions on such trigger objects.

Also, in the example described, after being presented with artificial reality content122C (inFIG.1C), user101may also escape, cease, pause, or otherwise exit that artificial reality experience simply by standing up after sitting on seat110. This may also be an effective, intuitive, frictionless, and natural way to exit an artificial reality experience, providing user101with a known way to transition to a more reality-based or a different experience where, in some examples, little or no artificial realty content is presented.

In such examples, standing (or otherwise performing a “de-trigger” action) may transition user101to a “safe” state that does not involve an immersive or intensive artificial reality experience. Such a safe state might be considered an “idle” state where idle artificial reality content is presented, which might involve primarily images of the physical world with little or no artificial reality content. In other examples, however, such an “idle” state may involve substantial artificial reality content overlaid on physical elements or even an immersive artificial reality experience.

FIG.2is an illustration depicting an example HMD112configured to operate in accordance with the techniques of the disclosure. HMD112ofFIG.2may be an example of any HMD112ofFIG.1A,FIG.1B,FIG.1C, and/orFIG.1D. HMD112may be part of an artificial reality system, such as artificial reality system100, or may operate as a stand-alone, mobile artificial realty system configured to implement the techniques described herein. HMD112may include a mobile device (e.g., a smart phone) that is removable from the body of the HMD112.

In the example ofFIG.2, HMD112includes a front rigid body and a band to secure HMD112to a user. In addition, HMD112includes an interior-facing electronic display203configured to present artificial reality content to the user. Electronic display203may be any suitable display technology, such as liquid crystal displays (LCD), quantum dot display, dot matrix displays, light emitting diode (LED) displays, organic light-emitting diode (OLED) displays, cathode ray tube (CRT) displays, e-ink, or monochrome, color, or any other type of display capable of generating visual output. In some examples, the electronic display is a stereoscopic display for providing separate images to each eye of the user. In some examples, the known orientation and position of display203relative to the front rigid body of HMD112is used as a frame of reference, also referred to as a local origin, when tracking the position and orientation of HMD112for rendering artificial reality content according to a current viewing perspective of HMD112and the user.

In the example ofFIG.2, HMD112further includes one or more sensors206, such as one or more accelerometers (also referred to as inertial measurement units or “Mils”) that output data indicative of current acceleration of HMD112, GPS sensors that output data indicative of a location of HMD112, radar or sonar sensors that output data indicative of distances of the HMD112from various objects, or other sensors that provide indications of a location or orientation of HMD112or other objects within a physical 3D environment. Moreover, HMD112may include one or more integrated sensor devices208, such as a microphone, audio sensor, a video camera, laser scanner, Doppler radar scanner, depth scanner, or the like, configured to output audio or image data representative of a surrounding real-world environment. HMD112includes an internal control unit210, which may include an internal power source and one or more printed-circuit boards having one or more processors, memory, and hardware to provide an operating environment for executing programmable operations to process sensed data and present artificial-reality content on display203. Internal control unit210may be part of a removable computing device, such as a smart phone.

Although illustrated inFIG.2having a specific configuration and structure, HMD112may take any of a number of forms. For example, in some implementations, HMD112might resemble glasses or may have a different form. Also, although HMD112may be configured with a display203for presenting representations or images of physical content, in other examples, HMD112may include a transparent or partially transparent viewing lens, enabling see-through artificial reality (i.e., “STAR”). Further, HMD may implement features based on wave guides or other STAR technologies.

In accordance with the techniques described herein, control unit210is configured to present content within the context of a physical environment that may include one or more trigger objects. For example, HMD112may compute, based on sensed data generated by motion sensors206and/or audio and image data captured by sensor devices208, a current pose for a frame of reference of HMD112. Control unit210may include a pose tracking unit, which can execute software for processing the sensed data and/or images to compute the current pose. Control unit210may store a master 3D map for a physical environment and compare processed images to the master 3D map to compute the current pose. Alternatively, or additionally, control unit210may compute the current pose based on sensor data generated by sensors206. Based on the computed current pose, control unit210may render artificial reality content corresponding to the master 3D map for an artificial reality application, and control unit210may display the artificial reality content via the electronic display203.

As another example, control unit210may generate mapping information for the physical 3D environment in which the HMD112is operating and send, to a console or one or more other computing devices (such as one or more other HMDs), via a wired or wireless communication session(s), the mapping information. In this way, HMD112may contribute mapping information for collaborate generation of the master 3D map for the physical 3D environment. Mapping information may include images captured by sensor devices208, tracking information in the form of indications of the computed local poses, or tracking information that provide indications of a location or orientation of HMD112within a physical 3D environment (such as sensor data generated by sensors206), for example.

In some examples, in accordance with the techniques described herein, control unit210may peer with one or more controllers for HMD112(controllers not shown inFIG.2). Control unit210may receive sensor data from the controllers that provides indications of user inputs or controller orientations or locations within the physical 3D environment or relative to HMD112. Control unit210may send representations of the sensor data to a console for processing by the artificial reality application, where the indications may be event data for an artificial reality application. Control unit210may execute the artificial reality application to process the sensor data.

FIG.3is a block diagram showing example implementations of an example console and an example HMD, in accordance with one or more aspects of the present disclosure. Although the block diagram illustrated inFIG.3is described with reference to HMD112, in other examples, functions and/or operations attributed to HMD112may be performed by a different device or system, such as a user device as referenced in connection withFIG.1A.

In the example ofFIG.3, HMD112includes one or more processors302and memory304that, in some examples, provide a computer platform for executing an operation system305, which may be an embedded and near (or seemingly-near) real-time multitasking operating system. In turn, operating system305provides a multitasking operating environment for executing one or more software components307. Processors302are coupled to electronic display203(seeFIG.2). HMD112is shown including motion sensors206and sensor devices208coupled to processor302, but in other examples, HMD112may include neither or merely either of motion sensors206and/or sensor devices208. In some examples, processors302and memory304may be separate, discrete components. In other examples, memory304may be on-chip memory collocated with processors302within a single integrated circuit. The memory304, processors302, operating system305, and application engine340components may collectively represent an example of internal control unit210ofFIG.2.

HMD112may include user input devices, such as a touchscreen or other presence-sensitive screen example of electronic display203, microphone, controllers, buttons, keyboard, and so forth. Application engine340may generate and present a login interface via electronic display203. A user of HMD112may use the user interface devices to input, using the login interface, login information for the user. HMD112may send the login information to console106to log the user into the artificial reality system.

Operating system305provides an operating environment for executing one or more software components, which include application engine306, which may be implemented as any type of appropriate module. Application engine306may be an artificial reality application having one or more processes. Application engine306may send, to console106as mapping information using an I/O interface (not shown inFIG.3) via a network or other communication link, representations of sensor data generated by motion sensors206or images generated by sensor devices208. The artificial reality application may be, e.g., a teleconference application, a gaming application, a navigation application, an educational application, or training or simulation application, for example.

Console106may be implemented by any suitable computing system capable of interfacing with user devices (e.g., HMDs112) of an artificial reality system. In some examples, console106interfaces with HMDs112to augment content that may be within physical environment120, or to present artificial reality content triggered by an action or gesture performed in a particular location relative to a trigger object. In some examples, console106generates, based at least on mapping information received from one or more HMDs112, external sensors190, and/or cameras192, a master 3D map of a physical 3D environment in which users, physical devices, and other physical objects are located. In some examples, console106is a single computing device, such as a workstation, a desktop computer, a laptop. In some examples, at least a portion of console106, such as processors352and/or memory354, may be distributed across one or more computing devices, a cloud computing system, a data center, or across a network, such as the Internet, another public or private communications network, for instance, broadband, cellular, Wi-Fi, and/or other types of communication networks, for transmitting data between computing systems, servers, and computing devices.

In the example ofFIG.3, console106includes one or more processors312and memory314that provide a computer platform for executing an operating system316. In turn, operating system316provides an operating environment for executing one or more software components317. Processors312are coupled to I/O interface315, which provides one or more I/O interfaces for communicating with external devices, such as a keyboard, game controllers, display devices, image capture devices, and the like. Moreover, I/O interface315may include one or more wired or wireless network interface cards (NICs) for communicating with a network, such as network104(see, e.g.,FIG.1A). Each of processors302,312may comprise any one or more of a multi-core processor, a controller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or equivalent discrete or integrated logic circuitry. Memory304,314may comprise any form of memory for storing data and executable software instructions, such as random-access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electronically erasable programmable read-only memory (EEPROM), and/or Flash memory. Software components317of console106operate to provide an overall artificial reality application. In the example ofFIG.3, software components317be represented by modules as described herein, including application engine320, rendering engine322, pose tracker326, mapping engine328, and user interface engine329.

Application engine320includes functionality to provide and present an artificial reality application, e.g., a teleconference application, a gaming application, a navigation application, an educational application, training or simulation applications, and the like. Application engine320and application engine340may cooperatively provide and present the artificial reality application in some examples. Application engine320may include, for example, one or more software packages, software libraries, hardware drivers, and/or Application Program Interfaces (APIs) for implementing an artificial reality application on console106. Responsive to control by application engine320, rendering engine322generates 3D artificial reality content for display to the user by application engine340of HMD112.

Rendering engine322renders the artificial content constructed by application engine320for display to user101in accordance with current pose information for a frame of reference, typically a viewing perspective of HMD112, as determined by pose tracker326. Based on the current viewing perspective, rendering engine322constructs the 3D, artificial reality content which may be overlaid, at least in part, upon the physical 3D environment in which HMD112is located. During this process, pose tracker326may operate on sensed data received from HMD112, such as movement information and user commands, and, in some examples, data from external sensors190and/or cameras192(as shown inFIG.1A,FIG.1B, andFIG.1C) to capture 3D information within the physical 3D environment, such as motion by HMD112, a user thereof, a controller, and/or feature tracking information with respect to the user thereof.

Pose tracker326determines information relating to a pose of a user within a physical environment. For example, console106may receive mapping information from HMD112, and mapping engine328may progressively generate a map for an area in which HMD112is operating over time, HMD112moves about the area. Pose tracker326may localize HMD112, using any of the aforementioned methods, to the map for the area. Pose tracker326may also attempt to localize HMD112to other maps generated using mapping information from other user devices. At some point, pose tracker326may compute the local pose for HMD112to be in an area of the physical 3D environment that is described by a map generated using mapping information received from a different user device. Using mapping information received from HMD112located and oriented at the computed local pose, mapping engine328may join the map for the area generated using mapping information for HMD112to the map for the area generated using mapping information for the different user device to close the loop and generate a combined map for the master 3D map. Mapping engine328stores such information as map data330. Based sensed data collected by external sensors190, cameras192, HMD112, or other sources, pose tracker326determines a current pose for the frame of reference of HMD112and, in accordance with the current pose, provides such information to application engine320for generation of artificial reality content. That artificial reality content may then be communicated to HMD112for display to the user via electronic display203.

Mapping engine328may be configured to generate maps of a physical 3D environment using mapping information received from user devices. Mapping engine328may receive the mapping information in the form of images captured by sensor devices208at local poses of HMD112and/or tracking information for HMD112, for example. Mapping engine328processes the images to identify map points for determining topographies of the scenes in the images and use the map points to generate map data that is descriptive of an area of the physical 3D environment in which HMD112is operating. Map data330may include at least one master 3D map of the physical 3D environment that represents a current best map, as determined by mapping engine328using the mapping information.

Mapping engine328may receive images from multiple different user devices operating in different areas of a physical 3D environment and generate different maps for the different areas. The different maps may be disjoint in that the maps do not, in some cases, overlap to describe any of the same areas of the physical 3D environment. However, the different maps may nevertheless be different areas of the master 3D map for the overall physical 3D environment.

Pose tracker326determines information relating to a pose of a user within a physical environment. For example, console106may receive mapping information from HMD112, and mapping engine328may progressively generate a map for an area in which HMD112is operating over time, HMD112moves about the area. Pose tracker326may localize HMD112, using any of the aforementioned methods, to the map for the area. Pose tracker326may also attempt to localize HMD112to other maps generated using mapping information from other user devices. At some point, pose tracker326may compute the local pose for HMD112to be in an area of the physical 3D environment that is described by a map generated using mapping information received from a different user device. Using mapping information received from HMD112located and oriented at the computed local pose, mapping engine328may join the map for the area generated using mapping information for HMD112to the map for the area generated using mapping information for the different user device to close the loop and generate a combined map for the master 3D map. Mapping engine328stores that maps as map data330. Based sensed data collected by external sensors190, cameras192, HMD112, or other sources, pose tracker326determines a current pose for the frame of reference of HMD112and, in accordance with the current pose, provides such information to application engine320for generation of artificial reality content. That artificial reality content may then be communicated to HMD112for display to the user via electronic display203.

Mapping engine328may use mapping information received from HMD112to update the master 3D map, which may be included in map data330. Mapping engine328may, in some examples, determine whether the mapping information is preferable to previous mapping information used to generate the master 3D map. For example, mapping engine328may determine the mapping information is more recent in time, of higher resolution or otherwise better quality, indicates more or different types of objects, has been generated by a user device having higher resolution localization abilities (e.g., better inertial measurement unit or navigation system) or better optics or greater processing power, or is otherwise preferable. If preferable, mapping engine328generates an updated master 3D map from the mapping information received from HMD112. Mapping engine328in this way progressively improves the master 3D map.

In some examples, mapping engine328may generate and store health data in association with different map data of the master 3D map. For example, some map data may be stale in that the mapping information used to generate the map data was received over an amount of time ago, or the map data may be of poor quality in that the images used to the generate the map data were poor quality (e.g., poor resolution, poor lighting, etc.). These characteristics of the map data may be associated with relatively poor health. Contrariwise, high quality mapping information would be associated with relatively good health. Health values for map data may be indicated using a score, a descriptor (e.g., “good”, “ok”, “poor”), a date generated, or other indicator. In some cases, mapping engine328may update map data of the master 3D map for an area if the health for the map data satisfies a threshold health value (e.g., is below a certain score). If the threshold health value is satisfied, mapping engine328generates an updated area for the area of the master 3D map using the mapping information received from HMD112operating in the area. Otherwise, mapping engine328discards the mapping information.

In some examples, map data330includes different master 3D maps for different areas of a physical 3D environment. Pose tracker326may localize HMD112to a location in one of the areas using images received from HMD112. In response, application engine320may select the master 3D map for the area within which pose tracker326localized HMD112and send the master 3D map to HMD112for use in the artificial reality application. Consequently, HMD112may generate and render artificial reality content using the appropriate master 3D map for the area in which HMD112is located.

In some examples, map data includes different master 3D maps for the same area of a physical 3D environment, the different master 3D maps representing different states of the physical environment. For example, a first master 3D map may describe an area at a first time e.g., August 2015, while a second master 3D map may describe the area at a second time, e.g., October 2016. Application engine320may determine to use the first master 3D map responsive to a request from the user or responsive to a trigger within an artificial reality application, for instance. The mapping engine328may indicate in map data330that the first master 3D map is the master 3D map that is to be used for rendering artificial reality content for an artificial reality application. In this way, an artificial reality system including console106can render artificial reality content using historical map data describing a physical 3D environment as it appeared in earlier times. This technique may be advantageous for education-related artificial reality applications, for instance.

User interface engine329may perform functions relating to generating a user interface when a user is interacting or has interacted with a trigger object (e.g., seat110) and/or when a user performs a gesture or action (e.g., sitting on seat110). User interface engine329may receive information from application engine320, pose tracker326, and/or mapping engine328and based on that information, generate a user interface (e.g., user interface menu124having user interface elements126). User interface engine329may output, to rendering engine322, information about the user interface so that rendering engine322may present the user interface, overlaid on other physical and/or artificial reality content, at display203of HMD112. Accordingly, user interface engine329may receive information from and output information to one or more other modules, and may otherwise interact with and/or operate in conjunction with one or more other engines or modules of console106.

In some examples, such as in the manner described in connection withFIG.4, some or all of the functionality attributed to pose tracker326, rendering engine322, configuration interface332, classifier324, and application engine320may be performed by HMD112.

Modules or engines illustrated inFIG.3(e.g., operating system316, application engine320, rendering engine322, pose tracker326, mapping engine328, user interface engine329, operating system305, and application engine306),FIG.4, and/or illustrated or described elsewhere in this disclosure may perform operations described using software, hardware, firmware, or a mixture of hardware, software, and firmware residing in and/or executing at one or more computing devices. For example, a computing device may execute one or more of such modules with multiple processors or multiple devices. A computing device may execute one or more of such modules as a virtual machine executing on underlying hardware. One or more of such modules may execute as one or more services of an operating system or computing platform. One or more of such modules may execute as one or more executable programs at an application layer of a computing platform. In other examples, functionality provided by a module could be implemented by a dedicated hardware device.

Although certain modules, data stores, components, programs, executables, data items, functional units, and/or other items included within one or more storage devices may be illustrated separately, one or more of such items could be combined and operate as a single module, component, program, executable, data item, or functional unit. For example, one or more modules or data stores may be combined or partially combined so that they operate or provide functionality as a single module. Further, one or more modules may interact with and/or operate in conjunction with one another so that, for example, one module acts as a service or an extension of another module. Also, each module, data store, component, program, executable, data item, functional unit, or other item illustrated within a storage device may include multiple components, sub-components, modules, sub-modules, data stores, and/or other components or modules or data stores not illustrated.

Further, each module, data store, component, program, executable, data item, functional unit, or other item illustrated within a storage device may be implemented in various ways. For example, each module, data store, component, program, executable, data item, functional unit, or other item illustrated within a storage device may be implemented as a downloadable or pre-installed application or “app.” In other examples, each module, data store, component, program, executable, data item, functional unit, or other item illustrated within a storage device may be implemented as part of an operating system executed on a computing device.

FIG.4is a block diagram depicting an example of a user device for an artificial reality system, in accordance with one or more aspects of the present disclosure. InFIG.4, HMD112may operate as a stand-alone device, i.e., not tethered to a console, and may represent an instance of any of the user devices, including HMDs112described in connection withFIG.1A,FIG.1B,FIG.1C, andFIG.1D. Although device112illustrated inFIG.4is primarily described as a head-mounted device, the device illustrated inFIG.4may, in other examples, be implemented as a different device, such as tablet computer, for instance. In the specific example ofFIG.4, however, and in a manner similar toFIG.3, HMD112includes one or more processors302and memory304that, in some examples, provide a computer platform for executing an operation system305, which may be an embedded multitasking operating system. In turn, operating system305provides an operating environment for executing one or more software components417. Moreover, processor(s)302are coupled to electronic display203, motion sensors206, and sensor devices208.

In the example ofFIG.4, software components417operate to provide an overall artificial reality application. In this example, software components417include application engine420, rendering engine422, pose tracker426, mapping engine428, and user interface (UI) engine429. In various examples, software components417operate similar to the counterpart components of console106ofFIG.3(e.g., application engine320, rendering engine322, pose tracker326, mapping engine328, and user interface engine329).

One or more aspects ofFIG.4may be described herein within the context of other Figures, includingFIG.1A,FIG.1B,FIG.1C, andFIG.1D. In various examples, HMD112may generate map information, determine a pose, detect input, identify one or more trigger objects, determine a user has performed a trigger action and de-trigger action with respect to an object, and present artificial reality content.

In accordance with one or more aspects of the present disclosure, HMD112ofFIG.1AandFIG.4may generate map information. For instance, in an example that can be described with reference toFIG.1AandFIG.4, each of external sensors190, cameras192, sensor devices208collect information about physical environment120. External sensors190and cameras192communicate the information each collects to HMD112, and such information may be communicated to HMD112over network104or through other means. HMD112receives information from external sensors190and/or cameras192and outputs to mapping engine428information about physical environment120. Sensor devices208of HMD112also collect information about physical environment120, and output to mapping engine428information about physical environment120. Mapping engine428determines, based on the information received from external sensors190, cameras192, and/or sensor devices208, a map of physical environment120. Mapping engine428stores information about the map as map data430.

HMD112may determine pose information. For instance, referring again toFIG.1AandFIG.4, motion sensor206and/or sensor devices208detect information about the position, orientation, and/or location of HMD112. Pose tracker426receives from mapping engine428information about the position, orientation, and/or location of HMD112. Pose tracker426determines, based on this information, a current pose for a frame of reference of HMD112.

HMD112may identify one or more objects within physical environment120as trigger objects. For instance, continuing with the example and with reference toFIG.1AandFIG.4, mapping engine428identifies, based on the information received from external sensors190, cameras192, and/or sensor devices208, one or more physical objects having the form of a chair, bench, desk, table, floor surface (e.g., a rug), or other object. Mapping engine428outputs information to application engine420. Application engine420determines that one or more of the identified objects is to be considered a trigger object. For instance, in some examples, application engine420may be previously configured (e.g., by an administrator or through default settings) to treat any type of object capable of supporting user101in a seated position as a trigger object. In such an example, application engine420may store information in map data430identifying seat110ofFIG.1Aas a trigger object. In some examples, application engine420might only recognize certain types of seats110as trigger objects, such as an object having the form of a bench as illustrated inFIG.1A. In other examples, however, application engine420may alternatively or in addition recognize as a trigger object other types of objects that support users in a sitting position, such as couches, or chairs with a backrest, chairs with arm rests, and/or chairs that recline. Application engine420updates map data430to reflect the objects identified as trigger objects.

In some examples, HMD112and/or an artificial reality system in general may identify (whether automatically or in response to user input or otherwise) trigger objects that might be considered, in some senses, to be arbitrary and/or ordinary physical objects. Examples of such arbitrary or ordinary physical objects may include a chair or a table or a decorative item hanging on a wall, and might not, in some examples, encompass certain objects are part of an artificial reality system, such as a joystick or a controller or a device that might regularly communicate with other components (e.g., console106) of an artificial reality system.

HMD112may identify one or more trigger objects within physical environment120in response to user input. In some examples, HMD112may identify trigger objects automatically, such as based on appearance, images of objects, and/or prior configurations, as described above. In other examples, however, HMD112may identify trigger objects identified by user101(or another user, such as an administrator). For instance, in such an example, and still referring toFIG.1AandFIG.4, external sensors190, cameras192, and/or sensor devices208detect movements by user101and output information about the movements to pose tracker426. Pose tracker426determines that the movements correspond to a gesture performed by user101. Pose tracker426outputs information about the gesture to application engine420. Application engine420determines that the gesture corresponds to user101identifying seat110as a trigger object. In some examples, user101may point to seat110and perform a gesture that application engine420recognizes as user101identifying seat110as a trigger object. In other examples, user interface engine429may, in response to the gesture, cause a user interface to be presented within HMD112A prompting user101for identification of one or more trigger objects. In some examples, HMD112A may detect an object, and prompt user101to configure the detected object as a trigger object or to confirm or deny its use as a trigger object.

Further, in some examples, one or more user interfaces may present a set of configuration options when a trigger object is configured. Such configuration options may include defining a trigger action to be associated with an object (sitting on the object, standing on the object, touching the object, moving the object, picking up the object, throwing the object) or configuring responses to such actions (starting or resuming a game, a driving, flight, or other simulator, initiating communications with other users or systems).

HMD112may determine that user101is within physical environment120but is not sitting on seat110. For instance, again in an example that can be described with reference toFIG.1AandFIG.4, mapping engine428outputs, to application engine420, information about mapping information for physical environment120. Pose tracker426outputs, to application engine420, information about the current pose determined for a frame of reference of HMD112. Application engine420determines, based on the mapping and pose information, that user101is standing near seat110, but is not sitting on seat110.

HMD112may present artificial reality content within HMD112while user101is standing. For instance, inFIG.1Aand with reference toFIG.4, application engine420generates artificial reality content122A. Application engine420outputs information about artificial reality content122A to rendering engine422. Rendering engine422causes artificial reality content122A to be presented at display203within HMD112in the manner shown inFIG.1A.

InFIG.1A, artificial reality content122A may correspond to simply an image of physical environment120, with little or no artificial reality content overlaid on physical environment120. In the example shown, artificial reality content122A includes window108, which is an image of window108illustrated in physical environment120. Artificial reality content122A also includes lamp107and picture109, both of which are three-dimensional objects within physical environment120(inFIG.1A, lamp107and picture109are positioned along the same wall as window108, but are not included in the illustration of physical environment120). Artificial reality content122A ofFIG.1Ais illustrated as an example of content that might be presented within HMD112, generally only showing images or three-dimensional representations of objects in physical environment120. In other examples, however, artificial reality content122A may include artificial reality content, including artificial reality content overlaid on images of physical objects within physical environment120. In at least some examples, physical objects are rendered from any angle to look three-dimensional.

HMD112may determine that user101has performed a trigger action with respect to seat110. For instance, continuing with the example being described and with reference toFIG.1BandFIG.4, motion sensors206detect motion and sensor devices208capture images. Motion sensors206and sensor devices208output information about the detected motion and captured images to pose tracker426. Pose tracker426determines a current pose of user101. Pose tracker426outputs, to application engine420, information about the current pose determined for a frame of reference of HMD112. Mapping engine428outputs, to application engine420, information about current mapping information for physical environment120. Application engine420determines, based on the mapping and pose information, that user101has moved so that user101is sitting on seat110, as illustrated inFIG.1B. Application engine420determines that the movement performed by user101(i.e., sitting on seat110) qualifies as a trigger action.

HMD112may present artificial reality content within HMD112in response to the trigger action. For instance, with reference toFIG.1BandFIG.4, application engine420determines, based on information about the trigger action and mapping information about seat110, that artificial reality content relating to a driving scene should be presented. Application engine420generates artificial reality content122B. Application engine420outputs information about artificial reality content122B to rendering engine422. Rendering engine422causes artificial reality content122B to presented at display203within112in the manner shown inFIG.1B.

In the example ofFIG.1B, content corresponding to a driving scene is presented, such as for a game or other artificial reality application. In other examples, artificial reality content122B may correspond to content rendered pursuant to other types of applications, including, but not limited to, a social interaction application, a video conferencing application, a movement instruction application, an alternative world application, a navigation application, an educational application, gaming application, training or simulation applications, augmented reality application, virtual reality application, or other type of applications that implement artificial reality.

Often, content presented in response to a trigger action will have some parity with the trigger action performed by user101. For example, if a trigger action involves moving from a standing to a sitting position, user101may be presented with triggered content where user101is in a sitting position, as inFIG.1B. Similarly, if a trigger action involves interactions with a table, artificial reality content or triggered content might be expected to include content where user101is using a table. If user101is running to perform a trigger action, the artificial reality content presented in response to such a trigger action might involve content consistent with the running action.

HMD112may continue to present artificial reality content122B while user101is seated on seat110. For instance, still referring toFIG.1BandFIG.4, motion sensors206detect motion and sensor devices208capture images while user101is seated on seat110. Motion sensors206and sensor devices208output information about detected motion and images to pose tracker426. Pose tracker426determines a current pose, and outputs information about the current pose to application engine420. Mapping engine428may output, to application engine420, information about current mapping information for physical environment120. Application engine420generates updated artificial reality content122B in response to movements by user101, and in response to progression of the game or driving experience being presented in HMD112(e.g., the scenery changes as user101drives along virtual road143).

HMD112may present a user interface menu in response to user input. For instance, now referring toFIG.1CandFIG.4, application engine420may determine that motion by user101or gestures performed by user101indicate that the user seeks to modify one or more options corresponding to the driving experience that user101is being presented with through HMD112. In response to such a determination, application engine420outputs information to user interface engine429. User interface engine429generates a user interface and outputs information about the user interface to application engine420. Application engine420generates artificial reality content122C. Application engine420outputs information about artificial reality content122C to rendering engine422. Rendering engine422causes artificial reality content122C to be presented at display203within HMD112in the manner shown inFIG.1C.

InFIG.1C, artificial reality content122C includes user interface menu124, and artificial reality content122C is similar to artificial reality content122B with the addition of menu124overlaid on the artificial reality content122B. Included within user interface menu124is one or more user interface elements126.

HMD112may perform operations in response to interactions with user interface menu124. For instance, referring again toFIG.1CandFIG.4, HMD112may detect movements by user101that application engine420determines corresponds to selection of one or more user interface elements126within user interface menu124. Application engine420may, in response to such movements, perform one or more operations. In some examples, such operations may cause user interface engine429to generate further user interfaces or modify aspects of artificial reality content122C. In such examples, application engine420updates artificial reality content, and causes rendering engine422to present the updated content to the user at display203.

HMD112may determine that user101has performed a de-trigger action. For instance, in an example that can be described with reference toFIG.1DandFIG.4, motion sensors206detect motion and sensor devices208capture images. Motion sensors206and sensor devices208output information about the detected motion and captured images to pose tracker426. Pose tracker426determines a current pose of user101. Pose tracker426outputs, to application engine420, information about the current pose determined for a frame of reference of HMD112. Mapping engine428outputs, to application engine420, information about current mapping information for physical environment120. Application engine420determines, based on the mapping and pose information, that user101is standing near seat110and is no longer sitting on seat110, as illustrated inFIG.1D. Application engine420determines that the action performed by user101(i.e., standing up after sitting on seat110) qualifies as a de-trigger action.

HMD112may cease presentation of triggered content in response to determining that user101has performed a de-trigger action. For instance, now referring toFIG.1DandFIG.4, application engine420determines, based on information about the de-trigger action, that artificial reality content relating to the driving scene (shown inFIG.1BandFIG.1C) should be no longer be presented. Application engine420generates artificial reality content122D. Application engine420outputs information about artificial reality content122D to rendering engine422. Rendering engine422causes artificial reality content122D to presented at display203within HMD112in the manner shown inFIG.1D, thereby ceasing presentation of artificial reality content122C.

In some examples, when ceasing presentation of artificial reality content122C, artificial reality content122D may be presented as simply an image of physical environment120without any content from artificial reality content122C ofFIG.1C. In other examples, however, some indication of content or parts of content from artificial reality content122C may continue to be presented in122D, even after the de-trigger action is detected. As illustrated inFIG.1D, for example, game score indicator145is included in artificial reality content122D, which may indicate a score achieved by user101when the de-trigger action was detected. Even after the de-trigger action, game score indicator145may be presented within artificial reality content122D indefinitely, or for a limited period of time, or until removed in response to user input. In some examples, the appearance of game score indicator145may be modified (e.g., drawn with a dotted line, as shown inFIG.1D) when presented in artificial reality content122D, thereby indicating that game score indicator145corresponds to content previously presented in artificial reality content122C.

FIG.5A,FIG.5B, andFIG.5Care conceptual diagrams illustrating an example artificial reality system that generates artificial reality content in response to interactions with a desk, in accordance with one or more aspects of the present disclosure. In each ofFIG.5A,FIG.5B, andFIG.5C, artificial reality system500is depicted within physical environment520. Physical environment520is shown as a room that includes user101and a number of real world or physical objects, including HMD112, window108, desk510, and wall clock114.

In the examples ofFIG.5A,FIG.5B, andFIG.5C, artificial reality system500includes many of the same elements described in artificial reality system100ofFIG.1A(and other illustrations), and elements illustrated in each ofFIG.5A,FIG.5B, andFIG.5Cmay correspond to elements illustrated inFIG.1Athat are identified by like-numbered reference numerals inFIG.1A. In general, such like-numbered elements may be implemented in a manner consistent with the description of the corresponding element provided in connection withFIG.1Aor elsewhere herein, although in some examples, such elements may involve alternative implementation with more, fewer, and/or different capabilities and attributes. Accordingly, artificial reality system500ofFIG.5A,FIG.5B, andFIG.5Cmay be described as an alternative example or implementation of artificial reality system100ofFIG.1A.

In accordance with one or more aspects of the present disclosure, HMD112may identify desk510as a trigger object. For instance, in an example that can be described with refence toFIG.4andFIG.5A, mapping engine428identifies, based on information stored in map data430, desk510as a trigger object, where an action is triggered when a user sits at desk510and, in some examples, places at least one arm on the surface of desk510. In some examples, mapping engine428may be previously configured (e.g., by administrator) to identify desk510as such a trigger object. In other examples, however, mapping engine428may determine, in response to input from user101, that desk510is to serve as a trigger object.

HMD112may present artificial reality content522A while user101is standing near desk510. For instance, referring again toFIG.4andFIG.5A, application engine420determines, based on mapping and pose information, that user101is standing near seat110. Application engine420generates artificial reality content522A. Application engine420outputs information about artificial reality content522A to rendering engine422. Rendering engine422causes artificial reality content522A to be presented at display203within HMD112in the manner shown inFIG.5A. InFIG.5A, artificial reality content522A may present an image of physical environment520, including virtual desk540, derived from an image of desk510from the perspective of HMD112.

HMD112may determine that user101has performed a trigger action on desk510. For instance, referring now toFIG.5B, motion sensors206and sensor devices208detect movements that application engine420determines corresponds to user101sitting at desk510and placing at least one arm on desk510. Application engine420generates artificial reality content522B. Application engine420outputs artificial reality content522B to rendering engine422, which causes artificial reality content522B to be presented at display203within HMD112, in the manner shown inFIG.5B.

InFIG.5B, artificial reality content522B includes user interface menu124and virtual desk540. User interface menu124includes one or more user interface elements126, which provide options for which type of artificial reality experience is to be presented to the user. In some examples, virtual desk540presented in artificial reality content522B might simply be an image of desk510from physical environment520, without any artificial reality content overlaid on the image.

HMD112may present artificial reality content522C based on interactions with artificial reality content522B. For instance, referring now toFIG.5BandFIG.5C, motion sensors206and sensor devices208detect movements that application engine420determines correspond interactions with user interface menu124ofFIG.5B. Application engine420determines that the interactions correspond to a user's selection of an artificial reality experience to be presented in response to the trigger action (i.e., sitting at desk510). Application engine420generates, based on the selection, artificial reality content522C. Application engine420outputs artificial reality content522C to rendering engine422, which causes artificial reality content522C to be presented at display203within HMD112in the manner illustrated inFIG.5C.

InFIG.5C, artificial reality content522C includes virtual desk540, virtual desk lamp546, and virtual window547. Artificial reality content522C may alter the lighting presented within physical environment520, such as through virtual desk lamp546providing additional light for virtual desk540. Virtual window547may provide a specific view chosen by user101and/or otherwise selected for user101. In some examples, artificial reality content522C may be presented along with music chosen by user101or otherwise selected based on determined musical interests of user101.

In at least some examples previously described in connection withFIG.1AthroughFIG.1D, artificial reality content is presented (e.g., automatically, without further user input) upon detecting a trigger action with respect to seat110. That artificial reality content may be selected based on the identity of user101, a user profile associated with user101, time of day, day of week, a calendar maintained or used by user101, or other time-based information. However, in the example just described with reference toFIG.5A,FIG.5B, andFIG.5C, HMD112presents options for selecting artificial reality content upon detecting a trigger action with respect to desk510. Artificial reality content is then presented based on interactions with a user interface (e.g., user interface menu124) by user101. Accordingly, in some examples, artificial reality content may be presented automatically upon detection of a trigger action. In other examples, options for artificial reality content may be presented to user101upon detection of a trigger action, and artificial reality content may then be presented in response to selected options.

FIG.6AandFIG.6Bare conceptual diagrams illustrating an example artificial reality system that generates artificial reality content in response to interactions with a portion of a floor space, in accordance with one or more aspects of the present disclosure. In each ofFIG.6AandFIG.6B, artificial reality system600is depicted within physical environment620. Physical environment620is shown as a room that includes user101and a number of real world or physical objects, including HMD112, window108, rug610and wall clock114. In addition, artificial reality system600includes context object611, which is held by user101. Context object611may be an object that is used to select or help select a particular artificial reality experience presented upon detection of a trigger action, as described herein.

In the examples ofFIG.6AandFIG.6B, artificial reality system600includes many of the same elements described in artificial reality system100ofFIG.1A, and elements illustrated inFIG.6AandFIG.6Bmay correspond to elements illustrated inFIG.1Athat are identified by like-numbered reference numerals inFIG.1A. In general, such like-numbered elements may be implemented in a manner consistent with the description of the corresponding element provided in connection withFIG.1Aor elsewhere herein, although in some examples, such elements may involve alternative implementation with more, fewer, and/or different capabilities and attributes. Accordingly, artificial reality system600ofFIG.6AandFIG.6Bmay again be described as an alternative example or implementation of artificial reality system100ofFIG.1A.

In accordance with one or more aspects of the present disclosure, HMD112may identify rug610and context object611. For instance, in an example that can be described with reference toFIG.4andFIG.6A, mapping engine428identifies, based on information stored in map data430, rug610as a trigger object. Mapping engine428further identifies, based on information stored in map data430, context object611as an object that is used to select what type of artificial reality content is presented upon interaction with rug610.

HMD112may present artificial reality content622A while user101is not standing on rug610. For instance, still referring toFIG.6A, application engine420determines, based on mapping and pose information, that user101is standing within physical environment620, but at a location not on rug610. Application engine420generates artificial reality content622A. Application engine420outputs622A to rendering engine422. Rendering engine422causes artificial reality content622to be presented at display203within HMD112in the manner shown inFIG.6A.

InFIG.6A, artificial reality content622A presents an image of a wall within physical environment620. Physical environment620includes a wall having lamp107, window108, and picture109. In the illustration ofFIG.6A, window108is visible in physical environment620. In artificial reality content622A, an image of objects along that wall in physical environment620are illustrated, including lamp107, window108, and picture109. In some examples, artificial reality content may be overlaid on the image of physical environment620presented within artificial reality content622A, but in the example shown, only an image of physical environment620is presented.

HMD112may determine that user101has performed a trigger action on rug610. For instance, referring now toFIG.6B, motion sensors206and sensor device208detect movements that application engine420determines corresponds to user101walking over to rug610and standing on rug610. Application engine420determines, based on information from motion sensors206, sensor devices208, and/or current mapping information from map data430, that user101is holding context object611in a hand. Application engine420recognizes that user101standing on rug610corresponds to a trigger action being performed on rug610. Application engine420generates artificial reality content622B, and uses information about user101holding context object611to select content to include within artificial reality content622B. Application engine420outputs artificial reality content622B to rendering engine422. Rendering engine422causes artificial reality content622B to be presented at display203within HMD112in the manner illustrated inFIG.6B.

InFIG.6B, virtual vista623in artificial reality content622B replaces the image of physical environment620presented in artificial reality content622A. In some examples, virtual vista623may be a replica of a real place, perhaps a place user101has previously visited. In some examples, the place depicted in virtual vista623might have some correlation with context object611, meaning, for example, that context object611is used to select virtual vista623. For instance, in one example, context object611may be a souvenir user101purchased when visiting the place depicted in virtual vista623. Application engine420may determine, based on prior input from user101, an administrator, or through image recognition of context object611, that context object611is associated in some way with the place depicted in virtual vista623. Accordingly, in such an example, application engine420uses context object611to select virtual vista623to present to user101within HMD112.

FIG.7is a flow diagram illustrating operations performed by an example artificial reality console106in accordance with one or more aspects of the present disclosure.FIG.7is described below within the context of artificial reality system100ofFIG.1AthroughFIG.1D. In other examples, operations described inFIG.7may be performed by one or more other components, modules, systems, or devices. Further, in other examples, operations described in connection withFIG.7may be merged, performed in a difference sequence, omitted, or may encompass additional operations not specifically illustrated or described.

In the process illustrated inFIG.7, and in accordance with one or more aspects of the present disclosure, console106may cause idle artificial reality content to be presented within HMD112(701). For example, with reference toFIG.1A, each of HMD112, external sensors190, and/or cameras192capture images within physical environment120. Console106receives such images and determines the position of physical objects within physical environment120, including user101, HMD112, and seat110. Console106generates map data (e.g., map data330inFIG.3) describing the physical environment. Console106identifies seat110as a trigger object, based on user input, image recognition, prior configuration, or in another way. Console106generates artificial reality content122A and causes artificial reality content122A to be presented within HMD112. In some examples, artificial reality content122A may be considered “idle” artificial reality content, since it might not be artificial reality content presented in response to a trigger action. Idle artificial reality content may be simply an image of physical environment120, or may include artificial reality content overlaid on an image of physical environment120.

Console106may determine whether user101has performed a trigger action (702). For example, with reference toFIG.1B, console106and/or HMD112detect motion and capture images. Console106uses the detected motion and images to determine a pose of user101. Console106uses the pose and/or mapping information to determine that user101is sitting on seat110, as illustrated inFIG.1B. Console106determines that the action performed by user101(e.g., sitting on seat110) qualifies as a trigger action (YES path from702). In examples where console106determines that user101is not sitting on seat110, console106continues to present idle content (NO path from702).

Console106may cause triggered artificial reality content to be presented within HMD112(703). For example, with reference toFIG.1B, console106generates an artificial reality environment, including artificial reality content122B reflecting a driving experience. Console106causes artificial reality content122B to be presented within HMD112. In the example ofFIG.1B, artificial reality content122B may present an immersive driving experience that includes no physical elements from physical environment120. In other examples, however, artificial reality content122B may augment aspects of physical environment120with artificial reality content, rather than providing an immersive experience.

Console106may determine whether user101has performed a de-trigger action (704). For example, with reference toFIG.1D, console106and/or112detect motion and capture images. Console106uses the detected motion and captured images to determine a pose of user101. Console106determines that user101is standing after sitting on seat110, and console106further determines that the motion of user101in standing qualifies as a de-trigger action.

Console106may cease presentation of the triggered artificial reality content (705). For example, again referring toFIG.1D, console106generates artificial reality content122D, which like artificial reality content122A, includes an image of physical environment120. Console106causes artificial reality content122D to be presented within HMD112. In some examples, artificial reality content122D may be substantially similar to artificial reality content122A, and may correspond to presenting the same type of “idle” content presented prior to detecting the trigger action. Accordingly, console106ceases presentation of artificial reality content122C and replaces artificial reality content122C with idle artificial reality content (e.g.,122D) upon detecting that user101is standing after sitting on seat110.

For processes, apparatuses, and other examples or illustrations described herein, including in any flowcharts or flow diagrams, certain operations, acts, steps, or events included in any of the techniques described herein can be performed in a different sequence, may be added, merged, or left out altogether (e.g., not all described acts or events are necessary for the practice of the techniques). Moreover, in certain examples, operations, acts, steps, or events may be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors, rather than sequentially. Further certain operations, acts, steps, or events may be performed automatically even if not specifically identified as being performed automatically. Also, certain operations, acts, steps, or events described as being performed automatically may be alternatively not performed automatically, but rather, such operations, acts, steps, or events may be, in some examples, performed in response to input or another event.

For ease of illustration, only a limited number of devices (e.g., HMD112, console106, external sensors190, cameras192, networks104, as well as others) are shown within the Figures and/or in other illustrations referenced herein. However, techniques in accordance with one or more aspects of the present disclosure may be performed with many more of such systems, components, devices, modules, and/or other items, and collective references to such systems, components, devices, modules, and/or other items may represent any number of such systems, components, devices, modules, and/or other items.

The Figures included herein each illustrate at least one example implementation of an aspect of this disclosure. The scope of this disclosure is not, however, limited to such implementations. Accordingly, other example or alternative implementations of systems, methods or techniques described herein, beyond those illustrated in the Figures, may be appropriate in other instances. Such implementations may include a subset of the devices and/or components included in the Figures and/or may include additional devices and/or components not shown in the Figures.

The detailed description set forth above is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a sufficient understanding of the various concepts. However, these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in the referenced figures in order to avoid obscuring such concepts.

Accordingly, although one or more implementations of various systems, devices, and/or components may be described with reference to specific Figures, such systems, devices, and/or components may be implemented in a number of different ways. For instance, one or more devices illustrated in the Figures herein (e.g.,FIG.1A,FIG.1B,FIG.1C,FIG.1D,FIG.2, and/orFIG.3) as separate devices may alternatively be implemented as a single device; one or more components illustrated as separate components may alternatively be implemented as a single component. Also, in some examples, one or more devices illustrated in the Figures herein as a single device may alternatively be implemented as multiple devices; one or more components illustrated as a single component may alternatively be implemented as multiple components. Each of such multiple devices and/or components may be directly coupled via wired or wireless communication and/or remotely coupled via one or more networks. Also, one or more devices or components that may be illustrated in various Figures herein may alternatively be implemented as part of another device or component not shown in such Figures. In this and other ways, some of the functions described herein may be performed via distributed processing by two or more devices or components.

Further, certain operations, techniques, features, and/or functions may be described herein as being performed by specific components, devices, and/or modules. In other examples, such operations, techniques, features, and/or functions may be performed by different components, devices, or modules. Accordingly, some operations, techniques, features, and/or functions that may be described herein as being attributed to one or more components, devices, or modules may, in other examples, be attributed to other components, devices, and/or modules, even if not specifically described herein in such a manner.

Although specific advantages have been identified in connection with descriptions of some examples, various other examples may include some, none, or all of the enumerated advantages. Other advantages, technical or otherwise, may become apparent to one of ordinary skill in the art from the present disclosure. Further, although specific examples have been disclosed herein, aspects of this disclosure may be implemented using any number of techniques, whether currently known or not, and accordingly, the present disclosure is not limited to the examples specifically described and/or illustrated in this disclosure.

The techniques described in this disclosure may be implemented, at least in part, in hardware, software, firmware or any combination thereof. For example, various aspects of the described techniques may be implemented within one or more processors, including one or more microprocessors, DSPs, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or any other equivalent integrated or discrete logic circuitry, as well as any combinations of such components. The term “processor” or “processing circuitry” may generally refer to any of the foregoing logic circuitry, alone or in combination with other logic circuitry, or any other equivalent circuitry. A control unit comprising hardware may also perform one or more of the techniques of this disclosure.

Such hardware, software, and firmware may be implemented within the same device or within separate devices to support the various operations and functions described in this disclosure. In addition, any of the described units, modules or components may be implemented together or separately as discrete but interoperable logic devices. Depiction of different features as modules or units is intended to highlight different functional aspects and does not necessarily imply that such modules or units must be realized by separate hardware or software components. Rather, functionality associated with one or more modules or units may be performed by separate hardware or software components or integrated within common or separate hardware or software components.

The techniques described in this disclosure may also be embodied or encoded in a computer-readable medium, such as a computer-readable storage medium, containing instructions. Instructions embedded or encoded in a computer-readable storage medium may cause a programmable processor, or other processor, to perform the method, e.g., when the instructions are executed. Computer readable storage media may include random access memory (RAM), read only memory (ROM), programmable read only memory (PROM), erasable programmable read only memory (EPROM), electronically erasable programmable read only memory (EEPROM), flash memory, a hard disk, a CD-ROM, a floppy disk, a cassette, magnetic media, optical media, or other computer readable media.

As described by way of various examples herein, the techniques of the disclosure may include or be implemented in conjunction with an artificial reality system. As described, artificial reality is a form of reality that has been adjusted in some manner before presentation to a user, which may include, e.g., a virtual reality (VR), an augmented reality (AR), a mixed reality (MR), a hybrid reality, or some combination and/or derivatives thereof. Artificial reality content may include completely generated content or generated content combined with captured content (e.g., real-world photographs). The artificial reality content may include video, audio, haptic feedback, or some combination thereof, and any of which may be presented in a single channel or in multiple channels (such as stereo video that produces a three-dimensional effect to the viewer). Additionally, in some examples, artificial reality may be associated with applications, products, accessories, services, or some combination thereof, that are, e.g., used to create content in an artificial reality and/or used in (e.g., perform activities in) an artificial reality. The artificial reality system that provides the artificial reality content may be implemented on various platforms, including a head-mounted display (HMD) connected to a host computer system, a standalone HMD, a mobile device or computing system, or any other hardware platform capable of providing artificial reality content to one or more viewers.