The present disclosure is directed to application multitasking in a shell with a three-dimensional environment.

BACKGROUND

Artificial reality systems have grown in popularity and this trend is expected to accelerate. Immersive artificial reality environments can provide unique experiences and support virtual social interactions among users. However, user interactions with executing applications in a three-dimensional environment often follow rigid conventions. For example, XR systems often omit concurrent execution and display of multiple executing applications. In addition, switching between multiple applications often involves a manual user workflow with several steps, such as terminating execution of a current application before executing a new application.

SUMMARY

According to an aspect, there is provided a method for application multitasking in a shell with a three-dimensional artificial reality, XR, environment, the method comprising: displaying the XR environment comprising a first virtual object that displays content for a first application executing in the shell, and a second virtual object that displays content for a second application executing in the shell; triggering an exclusive mode for the first application, the exclusive mode preventing applications, other than the first application, from displaying world-locked content, wherein, during the exclusive mode, the first and second virtual objects are removed from display, and the second application is transitioned to a background state; redisplaying, in response to termination of the exclusive mode, the first virtual object and the second virtual object in the XR environment by: transitioning the second application from the background state to executing in the shell; and displaying content for the first application executing in the shell at the first virtual object and content for the second application executing in the shell at the second virtual object.

In one embodiment, when displayed or redisplayed, the first virtual object and the second virtual object are displayed side-by-side in a predefined near-field region of the XR environment relative to the user.

In one embodiment, the near-field region of the XR environment comprises a plurality of nodes positioned side-by-side and, when displayed, each of the first virtual object and second virtual object is assigned to one of the nodes.

In one embodiment, in exclusive mode, content for the first application is dynamically moved to a third virtual object displayed in the exclusive region of the XR environment.

In one embodiment, the exclusive region is closer in proximity to the user than the near-field region in the XR environment.

In one embodiment, the triggered exclusive mode for the first application provides the first application use of at least a designated exclusive region of the XR environment, and, in exclusive mode, content for the first application is dynamically moved to a third virtual object displayed in the exclusive region of the XR environment.

In one embodiment, the designated exclusive region of the XR environment is closer in proximity to the user than the near-field region in the XR environment.

In one embodiment, the first virtual object, second virtual object, and third virtual object comprise two-dimensional panels.

In one embodiment: the XR environment displayed to the user comprises a shell XR environment, in exclusive mode, the content for the first application comprises a first application XR environment, in exclusive mode, the shell XR environment is replaced with the first application XR environment, and in response to terminating the exclusive mode, the first application XR environment is replaced with the shell XR environment.

In one embodiment, the method further comprises: storing, in response to triggering the exclusive mode for the first application, state information for the second executing application and the second virtual object, wherein the redisplaying the second virtual object in the XR environment comprises restoring the second virtual object using the stored state information.

In one embodiment, the stored state information comprises a content state for the second virtual object and an execution state for the second executing application.

In one embodiment, redisplaying the second virtual object in the XR environment comprises restoring, using the stored state information, content displayed at the second virtual object and an execution state for the second application.

In one embodiment, said displaying the XR environment comprises displaying the XR environment to a user via an XR device; said triggering the exclusive mode is in response to a request; and the exclusive mode provides the first application use of at least a designated exclusive region of the XR environment. According to another aspect, there is provided a computer-readable storage medium storing instructions that, when executed by a computing system, cause the computing system to perform the method set out above.

According to a further embodiment, there is provided a computing system for application multitasking in a shell with a three-dimensional artificial reality, XR, environment, the computing system comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the computing system to perform the method set out above.

It will be appreciated that any features described herein as being suitable for incorporation into one or more aspects or embodiments of the present disclosure are intended to be generalizable across any and all aspects and embodiments of the present disclosure. Other aspects of the present disclosure can be understood by those skilled in the art in light of the description, the claims, and the drawings of the present disclosure. The foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a block diagram illustrating an overview of devices on which some implementations of the present technology can operate.

Figure 2A is a wire diagram illustrating a virtual reality headset which can be used in some implementations of the present technology.

Figure 2B is a wire diagram illustrating a mixed reality headset which can be used in some implementations of the present technology.

Figure 2C is a wire diagram illustrating controllers which, in some implementations, a user can hold in one or both hands to interact with an artificial reality environment.

Figure 3 is a block diagram illustrating an overview of an environment in which some implementations of the present technology can operate.

Figure 4 is a block diagram illustrating components which, in some implementations, can be used in a system employing the disclosed technology.

Figures 5 is a diagram of a three-dimensional environment for a system shell with concurrently executing applications.

Figures 6A and 6B are diagrams of three-dimensional environments for a system shell with multiple virtual object displays.

Figure 7A is a diagram of a three-dimensional environment with a theater display.

Figure 7B is a diagram of a three-dimensional environment illustrating multiple display locations.

Figure 8 is a diagram of a shared three-dimensional environment with a theater display.

Figure 9 is a flow diagram illustrating a process used in some implementations of the present technology for application multitasking in a shell with a three-dimensional environment.

The techniques introduced here may be better understood by referring to the following Detailed Description in conjunction with the accompanying drawings, in which like reference numerals indicate identical or functionally similar elements. DETAILED DESCRIPTION

Aspects of the present disclosure are directed to application multitasking in a shell with a three-dimensional environment. Implementations immerse a user in a three-dimensional environment via an artificial reality system. The three-dimensional environment can be the display environment for a system shell. Implementations of the system shell execute applications (e.g. , system shell applications and applications remote from the system shell). For example, an executing application can correspond to a two-dimensional virtual object (e.g., panel) displayed in the three-dimensional environment. In some implementations, the system shell can concurrently execute two, three, or more applications and the three-dimensional environment can concurrently display two, three, or more corresponding virtual objects that display contents for the executing applications. The concurrently displayed virtual objects can be side-by-side panel displays in some implementations. Example applications include web browsers, music players, video players, social media applications, messaging or other communication applications, third-party applications, streaming/casting applications, a content library application, or any other suitable application.

Virtual object displays in the three-dimensional environment can comprise display components for executing applications. For example, the content for an executing application is displayed in its corresponding virtual object. Virtual objects can display a webpage for a browser application, an interface for playing music or a video, messages with other users, or any other suitable content. The user can interact with executing applications using their virtual object displays, such as via hand-held controller input (e.g., sensed motion, button presses, etc.), sensed user motion (e.g., virtual hands), or any other suitable user input.

In some implementations, a near-field (e.g., predefined region or volume of the three-dimensional environment) can comprise a set of nodes that can each host a virtual object in cooperative mode. The near-field can comprise the surface of a cylinder that surrounds the user (or a portion of the cylindrical surface) such that that the near-field is a first distance from the user. In some implementations, the nodes can be side-by-side on the near-field so that when the nodes host virtual objects, they are displayed side-by-side. For example, the near-field can display two, three, or more side-by-side two-dimensional virtual objects (e.g., panels) at a first distance from the user, and each virtual object can display contents for a concurrently executing application. In some implementations, when a given application begins executing (e.g., via user input, or any other suitable trigger) or a background application is restored, the given application can be assigned to one of the unassigned nodes of the near-field. A user can also select a virtual object that corresponds to an executing application (e.g., grab a virtual object via user input, such as a pinch) and position the virtual object over an unassigned node at the near-field to assign the virtual object/executing application to the node.

Implementations of the system shell can store the state of executing applications and the shell state of their corresponding two-dimensional virtual objects. For example, when an application is transitioned to background status, such as when an exclusive mode is entered, orthe system shell is transitioned to inactive (e.g., when a user initiates an XR application that triggers display of a new XR environment, ends a user session with the XR system, etc.), the application state of executing application(s) and the shell state (e.g., position, size, etc.) of their corresponding two- dimensional virtual object(s) can be stored. The state storage responsibilities can be divided among the system shell and the individual applications. For example, the shell state stored by the system shell can include: size and position (e.g., within the three- dimensional environment) of the corresponding two-dimensional virtual object(s), application specific display parameters (e.g., tab orientation, relevant websites/webpages, etc.), and any other suitable state parameter(s) that initialize an application. State stored by the individual applications can include: specific state of content displayed at the time the application is closed (e.g., open tab, scroll position, open webpage, open messages in a communication application, etc.), and any other suitable application state parameter.

When the application(s) are restored (e.g., exclusive mode is terminated, the system shell returns to an active state, etc.), implementations of the system shell can restore/initialize display of virtual objects for the application(s) according to the system shell’s stored shell state (e.g., position and size of the virtual object, initialization parameters for the application, etc.) and the application itself can restore the content displayed at the virtual object(s) according to the application’s stored state. In combination, this state save and restoration workflow provides the user a seamless experience. For example, when an executing application is transitioned into the background having a given state (e.g., virtual object position and size, content displayed in the virtual object, etc.), the application can be restored in the same given state (without any additional interaction with or management by the user) upon transitioning into active execution again. Similarly, when a system shell is transitioned to inactive (e.g., its three-dimensional virtual environment is no longer displayed), a given state for each of its executing applications can be stored. Upon reactivation of the system shell (e.g., redisplay of the three-dimensional environment), each application can be restored to its given state to provide a seamless restoration of the state for the entire system shell.

Implementations of a mode manager can manage a mode for the three-dimensional environment/system shell. Example modes include cooperative mode and exclusive mode. Implementations of cooperative mode permit concurrent execution of multiple applications and display of multiple virtual objects, such as multiple panels in a near-field that display the contents of multiple executing applications. In some examples, the mode manager can initiate exclusive mode for an executing application, for example according to user input, based on a request from the application, or in any other suitable manner. Implementations of the exclusive mode permit display of virtual objects only from the executing application entering exclusive mode, for example at a location in the three-dimensional environment closer to the user than the near-field region, orat any other suitable location. When exclusive mode is initiated, executing applications other than the application entering exclusive mode are transitioned to the background and their states are stored. In addition, the virtual object displays for these applications are no longer displayed until exclusive mode is exited. In some implementations, when a given application enters exclusive mode, applications other than the given application are prevented from displayed world-locked content (e.g., content locked to a real-world location while displayed in the XR environment).

Implementations of the three-dimensional environment include a theater screen at a far-field region or volume. For example, the far-field region can be a cylindrical surface (or portion of a cylindrical surface) that is further from the user than the nearfield. The theater screen can display content for any suitable application assigned to the theater screen. In some implementations, the theater screen can be active in cooperative mode or in exclusive mode. For example, the theater screen can display a video while a user interacts with other executing application(s) via their corresponding virtual object(s). In some implementations, a theater screen can be shared among multiple users. For example, a video can be cast to a theater screen that is simultaneously displayed to multiple users via multiple XR systems. In this example, each user can be immersed in a three-dimensional environment (e.g., that corresponds to a system shell), and the theater screen can be displayed in the far- field region for each user. In other examples, the theater screen can simultaneously display video to the multiple users in any other suitable manner.

Embodiments of the disclosed technology may include or be implemented in conjunction with an artificial reality system. Artificial reality or extra reality (XR) is a form of reality that has been adjusted in some manner before presentation to a user, which may include, e.g., virtual reality (VR), augmented reality (AR), mixed reality (MR), 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, 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 embodiments, 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, a "cave" environment or other projection system, or any other hardware platform capable of providing artificial reality content to one or more viewers. "Virtual reality" or "VR," as used herein, refers to an immersive experience where a user's visual input is controlled by a computing system. "Augmented reality" or "AR" refers to systems where a user views images of the real world after they have passed through a computing system. For example, a tablet with a camera on the back can capture images of the real world and then display the images on the screen on the opposite side of the tablet from the camera. The tablet can process and adjust or "augment" the images as they pass through the system, such as by adding virtual objects. "Mixed reality" or "MR" refers to systems where light entering a user's eye is partially generated by a computing system and partially composes light reflected off objects in the real world. For example, a MR headset could be shaped as a pair of glasses with a pass-through display, which allows light from the real world to pass through a waveguide that simultaneously emits light from a projector in the MR headset, allowing the MR headset to present virtual objects intermixed with the real objects the user can see. "Artificial reality," "extra reality," or "XR," as used herein, refers to any of VR, AR, MR, or any combination or hybrid thereof.

The shell component of conventional XR systems fails to support multiapplication functionality. For example, XR systems often omit concurrent execution and display of multiple executing applications. In addition, switching between multiple applications often involves a manual user workflow with several steps, such as terminating execution of a current application before executing a new application.

Implementations provide a shell XR environment and system shell that executes applications (e.g., system shell applications and applications remote from the system shell). For example, an executing application can correspond to a two-dimensional virtual object displayed in the XR environment. The system shell can concurrently execute two, three, or more applications and the XR environment can concurrently display two, three, or more corresponding virtual objects that display contents for the executing applications. The concurrently displayed virtual objects can be side-by-side panel displays in some implementations.

In addition, implementations of the system shell can store the state of executing applications and the shell state of their corresponding two-dimensional virtual objects. For example, when an executing application is transitioned to background status, the application state of the executing application and the shell state of its corresponding two-dimensional virtual object can be stored. When the application transitions back to active execution, implementations of the system shell can restore/initialize display of virtual object for the application according to the system shell’s stored shell state and the application can restore the content displayed at the virtual object according to the application’s stored state. Accordingly, implementations provide mechanisms for concurrent execution of applications in the shell environment and efficient switching between executing applications.

Several implementations are discussed below in more detail in reference to the figures. Figure 1 is a block diagram illustrating an overview of devices on which some implementations of the disclosed technology can operate. The devices can comprise hardware components of a computing system 100 that provide application multitasking in a shell with a three-dimensional environment. In various implementations, computing system 100 can include a single computing device 103 or multiple computing devices (e.g., computing device 101 , computing device 102, and computing device 103) that communicate over wired or wireless channels to distribute processing and share input data. In some implementations, computing system 100 can include a stand-alone headset capable of providing a computer created or augmented experience for a user without the need for external processing or sensors. In other implementations, computing system 100 can include multiple computing devices such as a headset and a core processing component (such as a console, mobile device, or server system) where some processing operations are performed on the headset and others are offloaded to the core processing component. Example headsets are described below in relation to Figures 2A and 2B. In some implementations, position and environment data can be gathered only by sensors incorporated in the headset device, while in other implementations one or more of the non-headset computing devices can include sensor components that can track environment or position data.

Computing system 100 can include one or more processor(s) 1 10 (e.g., central processing units (CPUs), graphical processing units (GPUs), holographic processing units (HPUs), etc.) Processors 110 can be a single processing unit or multiple processing units in a device or distributed across multiple devices (e.g., distributed across two or more of the computing devices 101-103).

Computing system 100 can include one or more input devices 120 that provide input to the processors 110, notifying them of actions. The actions can be mediated by a hardware controller that interprets the signals received from the input device and communicates the information to the processors 110 using a communication protocol. Each input device 120 can include, for example, a mouse, a keyboard, a touchscreen, a touchpad, a wearable input device (e.g., a haptics glove, a bracelet, a ring, an earring, a necklace, a watch, etc.), a camera (or other light-based input device, e.g., an infrared sensor), a microphone, or other user input devices.

Processors 110 can be coupled to other hardware devices, for example, with the use of an internal or external bus, such as a PCI bus, SCSI bus, or wireless connection. The processors 110 can communicate with a hardware controller for devices, such as for a display 130. Display 130 can be used to display text and graphics. In some implementations, display 130 includes the input device as part of the display, such as when the input device is a touchscreen or is equipped with an eye direction monitoring system. In some implementations, the display is separate from the input device. Examples of display devices are: an LCD display screen, an LED display screen, a projected, holographic, or augmented reality display (such as a heads-up display device or a head-mounted device), and so on. Other I/O devices 140 can also be coupled to the processor, such as a network chip or card, video chip or card, audio chip or card, USB, firewire or other external device, camera, printer, speakers, CD-ROM drive, DVD drive, disk drive, etc.

In some implementations, input from the I/O devices 140, such as cameras, depth sensors, IMU sensor, GPS units, LiDAR or other time-of-flights sensors, etc. can be used by the computing system 100 to identify and map the physical environment of the user while tracking the user's location within that environment. This simultaneous localization and mapping (SLAM) system can generate maps (e.g., topologies, girds, etc.) for an area (which may be a room, building, outdoor space, etc.) and/or obtain maps previously generated by computing system 100 or another computing system that had mapped the area. The SLAM system can track the user within the area based on factors such as GPS data, matching identified objects and structures to mapped objects and structures, monitoring acceleration and other position changes, etc.

Computing system 100 can include a communication device capable of communicating wirelessly or wire-based with other local computing devices or a network node. The communication device can communicate with another device or a server through a network using, for example, TCP/IP protocols. Computing system 100 can utilize the communication device to distribute operations across multiple network devices.

The processors 110 can have access to a memory 150, which can be contained on one of the computing devices of computing system 100 or can be distributed across of the multiple computing devices of computing system 100 or other external devices. A memory includes one or more hardware devices for volatile or non-volatile storage, and can include both read-only and writable memory. For example, a memory can include one or more of random access memory (RAM), various caches, CPU registers, read-only memory (ROM), and writable non-volatile memory, such as flash memory, hard drives, floppy disks, CDs, DVDs, magnetic storage devices, tape drives, and so forth. A memory is not a propagating signal divorced from underlying hardware; a memory is thus non-transitory. Memory 150 can include program memory 160 that stores programs and software, such as an operating system 162, application manager 164, and other application programs 166. Memory 150 can also include data memory 170 that can include, e.g., virtual object data, application data, environment or application state data, configuration data, settings, user options or preferences, etc., which can be provided to the program memory 160 or any element of the computing system 100.

Some implementations can be operational with numerous other computing system environments or configurations. Examples of computing systems, environments, and/or configurations that may be suitable for use with the technology include, but are not limited to, XR headsets, personal computers, server computers, handheld or laptop devices, cellular telephones, wearable electronics, gaming consoles, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, or the like.

Figure 2A is a wire diagram of a virtual reality head-mounted display (HMD) 200, in accordance with some embodiments. The HMD 200 includes a front rigid body 205 and a band 210. The front rigid body 205 includes one or more electronic display elements of an electronic display 245, an inertial motion unit (IMU) 215, one or more position sensors 220, locators 225, and one or more compute units 230. The position sensors 220, the IMU 215, and compute units 230 may be internal to the HMD 200 and may not be visible to the user. In various implementations, the IMU 215, position sensors 220, and locators 225 can track movement and location of the HMD 200 in the real world and in an artificial reality environment in three degrees of freedom (3DoF) or six degrees of freedom (6DoF). For example, the locators 225 can emit infrared light beams which create light points on real objects around the HMD 200. As another example, the I MU 215 can include e.g., one or more accelerometers, gyroscopes, magnetometers, other non-camera-based position, force, or orientation sensors, or combinations thereof. One or more cameras (not shown) integrated with the HMD 200 can detect the light points. Compute units 230 in the HMD 200 can use the detected light points to extrapolate position and movement of the HMD 200 as well as to identify the shape and position of the real objects surrounding the HMD 200.

The electronic display 245 can be integrated with the front rigid body 205 and can provide image light to a user as dictated by the compute units 230. In various embodiments, the electronic display 245 can be a single electronic display or multiple electronic displays (e.g., a display for each user eye). Examples of the electronic display 245 include: a liquid crystal display (LCD), an organic light-emitting diode (OLED) display, an active-matrix organic light-emitting diode display (AMOLED), a display including one or more quantum dot light-emitting diode (QOLED) sub-pixels, a projector unit (e.g., microLED, LASER, etc.), some other display, or some combination thereof.

In some implementations, the HMD 200 can be coupled to a core processing component such as a personal computer (PC) (not shown) and/or one or more external sensors (not shown). The external sensors can monitor the HMD 200 (e.g., via light emitted from the HMD 200) which the PC can use, in combination with output from the IMU 215 and position sensors 220, to determine the location and movement of the HMD 200.

Figure 2B is a wire diagram of a mixed reality HMD system 250 which includes a mixed reality HMD 252 and a core processing component 254. The mixed reality HMD 252 and the core processing component 254 can communicate via a wireless connection (e.g., a 60 GHz link) as indicated by link 256. In other implementations, the mixed reality system 250 includes a headset only, without an external compute device or includes other wired or wireless connections between the mixed reality HMD 252 and the core processing component 254. The mixed reality HMD 252 includes a pass-through display 258 and a frame 260. The frame 260 can house various electronic components (not shown) such as light projectors (e.g., LASERS, LEDs, etc.), cameras, eye-tracking sensors, MEMS components, networking components, etc.

The projectors can be coupled to the pass-through display 258, e.g., via optical elements, to display media to a user. The optical elements can include one or more waveguide assemblies, reflectors, lenses, mirrors, collimators, gratings, etc., for directing light from the projectors to a user's eye. Image data can be transmitted from the core processing component 254 via link 256 to HMD 252. Controllers in the HMD 252 can convert the image data into light pulses from the projectors, which can be transmitted via the optical elements as output light to the user's eye. The output light can mix with light that passes through the display 258, allowing the output light to present virtual objects that appear as if they exist in the real world.

Similarly to the HMD 200, the HMD system 250 can also include motion and position tracking units, cameras, light sources, etc., which allow the HMD system 250 to, e.g., track itself in 3DoF or 6DoF, track portions of the user (e.g., hands, feet, head, or other body parts), map virtual objects to appear as stationary as the HMD 252 moves, and have virtual objects react to gestures and other real-world objects.

Figure 2C illustrates controllers 270 (including controller 276A and 276B), which, in some implementations, a user can hold in one or both hands to interact with an artificial reality environment presented by the HMD 200 and/or HMD 250. The controllers 270 can be in communication with the HMDs, either directly or via an external device (e.g., core processing component 254). The controllers can have their own IMU units, position sensors, and/or can emit further light points. The HMD 200 or 250, external sensors, or sensors in the controllers can track these controller light points to determine the controller positions and/or orientations (e.g., to track the controllers in 3DoF or 6DoF). The compute units 230 in the HMD 200 or the core processing component 254 can use this tracking, in combination with IMU and position output, to monitor hand positions and motions of the user. The controllers can also include various buttons (e.g., buttons 272A-F) and/or joysticks (e.g., joysticks 274A- B), which a user can actuate to provide input and interact with objects.

In various implementations, the HMD 200 or 250 can also include additional subsystems, such as an eye tracking unit, an audio system, various network components, etc., to monitor indications of user interactions and intentions. For example, in some implementations, instead of or in addition to controllers, one or more cameras included in the HMD 200 or 250, or from external cameras, can monitor the positions and poses of the user's hands to determine gestures and other hand and body motions. As another example, one or more light sources can illuminate either or both of the user's eyes and the HMD 200 or 250 can use eye-facing cameras to capture a reflection of this light to determine eye position (e.g., based on set of reflections around the user's cornea), modeling the user's eye and determining a gaze direction.

Figure 3 is a block diagram illustrating an overview of an environment 300 in which some implementations of the disclosed technology can operate. Environment 300 can include one or more client computing devices 305A-D, examples of which can include computing system 100. In some implementations, some of the client computing devices (e.g., client computing device 305B) can be the HMD 200 or the HMD system 250. Client computing devices 305 can operate in a networked environment using logical connections through network 330 to one or more remote computers, such as a server computing device.

In some implementations, server 310 can be an edge server which receives client requests and coordinates fulfillment of those requests through other servers, such as servers 320A-C. Server computing devices 310 and 320 can comprise computing systems, such as computing system 100. Though each server computing device 310 and 320 is displayed logically as a single server, server computing devices can each be a distributed computing environment encompassing multiple computing devices located at the same or at geographically disparate physical locations.

Client computing devices 305 and server computing devices 310 and 320 can each act as a server or client to other server/client device(s). Server 310 can connect to a database 315. Servers 320A-C can each connect to a corresponding database 325A-C. As discussed above, each server 310 or 320 can correspond to a group of servers, and each of these servers can share a database or can have their own database. Though databases 315 and 325 are displayed logically as single units, databases 315 and 325 can each be a distributed computing environment encompassing multiple computing devices, can be located within their corresponding server, or can be located at the same or at geographically disparate physical locations.

Network 330 can be a local area network (LAN), a wide area network (WAN), a mesh network, a hybrid network, or other wired or wireless networks. Network 330 may be the Internet or some other public or private network. Client computing devices 305 can be connected to network 330 through a network interface, such as by wired or wireless communication. While the connections between server 310 and servers 320 are shown as separate connections, these connections can be any kind of local, wide area, wired, or wireless network, including network 330 or a separate public or private network.

Figure 4 is a block diagram illustrating components 400 which, in some implementations, can be used in a system employing the disclosed technology. Components 400 can be included in one device of computing system 100 or can be distributed across multiple of the devices of computing system 100. The components 400 include hardware 410, mediator 420, and specialized components 430. As discussed above, a system implementing the disclosed technology can use various hardware including processing units 412, working memory 414, input and output devices 416 (e.g., cameras, displays, IMU units, network connections, etc.), and storage memory 418. In various implementations, storage memory 418 can be one or more of: local devices, interfaces to remote storage devices, or combinations thereof. For example, storage memory 418 can be one or more hard drives or flash drives accessible through a system bus or can be a cloud storage provider (such as in storage 315 or 325) or other network storage accessible via one or more communications networks. In various implementations, components 400 can be implemented in a client computing device such as client computing devices 305 or on a server computing device, such as server computing device 310 or 320.

Mediator 420 can include components which mediate resources between hardware 410 and specialized components 430. For example, mediator 420 can include an operating system, services, drivers, a basic input output system (BIOS), controller circuits, or other hardware or software systems.

Specialized components 430 can include software or hardware configured to perform operations for controlling an indicator by combining signals from multiple sensors. Specialized components 430 can include system shell 434, application state manager 436, environment mode manager 438, and components and APIs which can be used for providing user interfaces, transferring data, and controlling the specialized components, such as interfaces 432. In some implementations, components 400 can be in a computing system that is distributed across multiple computing devices or can be an interface to a server-based application executing one or more of specialized components 430. Although depicted as separate components, specialized components 430 may be logical or other nonphysical differentiations of functions and/or may be submodules or code-blocks of one or more applications.

System shell 434 can manage the software components of an XR system, such as system display components, software functionality for system display components, and interactions with launched applications. For example, system shell 434 can be a shell environment in which applications are executed, such as shell applications or applications remote from the shell. Example applications include web browsers, music players, video players, social media applications, messaging web browsers, music players, video players, social media applications, messaging or other communication applications, third-party applications, streaming/casting applications, a content library application, or any other suitable application.

Implementations of system shell 434 can interact with the applications executing at the XR system to manage visual displays for the applications, such as two-dimensional virtual object displays (e.g. , panels). System shell 434 can manage positioning and sizing of the virtual object displays and allocate portions of display area/volume to the executing applications. Implementations of system shell 434 can also restore a state for backgrounded/suspended application(s)/virtual object(s) using the saved state(s) managed by state manager 436. In some implementations, system shell 434 can comprise several units of executing software in combination. Additional details on system shell 434 are provided below in relation to Figures 5, 6, 7, 8, and blocks 902, 904, 906, 908, 910, and 912 of Figure 9.

Application state manager 436 can save a shell state for applications, such as positioning and location for the virtual object display component of the applications. For example, when an application is transitioned to background status, such as when an exclusive mode is entered, orthe system shell is transitioned to inactive (e.g., when a user initiates an XR application that triggers display of a new XR environment), the application state of executing application(s) and the shell state (e.g., position, size, etc.) of their corresponding two-dimensional virtual object(s) can be stored. The state storage responsibilities can be divided among application state manager 436 and the individual applications.

For example, application state manager 436 can store the shell state for an application, including: size and position (e.g., within the three-dimensional environment) of the corresponding two-dimensional virtual object(s), application specific display parameters (e.g., tab orientation, relevant websites/webpages, etc.), and any other suitable state parameter(s) that initialize an application. State stored by the individual applications can include: specific state of content displayed at the time the application is closed (e.g., open tab, scroll position, open webpage, open messages in a communication application, etc.), and any other suitable application state parameter. When system shell 434 restores an application with a saved state, the application’s shell state stored by application state manager 436 is used to restore the state of the application’s virtual object (e.g., position and size of the virtual object, initialization parameters for the application, etc.) and the application itself can restore the content displayed by the restored virtual object according to the application’s stored state.

Environment mode manager438 can manage a mode forthe three-dimensional environment/system shell 434. Example modes include cooperative mode and exclusive mode. Implementations of cooperative mode permit concurrent execution of multiple applications and display of multiple virtual objects, such as multiple panels in a near-field relative to the user that display the contents of multiple executing applications. In some examples, mode manager 438 can initiate exclusive mode for an executing application, for example according to user input, based on a request from the application, or in any other suitable manner. Implementations of the exclusive mode permit display of virtual objects only from the executing application entering exclusive mode. When exclusive mode is initiated, executing applications other than the application entering exclusive mode are transitioned to the background and their state(s) are stored. In addition, the virtual object displays for these applications are no longer displayed until exclusive mode is exited. Additional details on environment mode manager 438 are provided below in relation to blocks 906, 908, and 910 of Figure 9.

Implementations of the system shell and the applications that execute at the system shell can manage a lifecycle for applications. Example lifecycle stages for an application running at the system shell can include: inactive, minimized, unfocused, focused, and exclusive. An application at the exclusive stage can be operating in exclusive mode at the system shell/in the three-dimensional environment of the shell. An application in the focused stage can be one of several concurrently executing applications operating in cooperative mode that has user input priority. For example, a concurrently executing application can be focused when the user is interacting with the application’s virtual object display component or the last user interaction was with the application’s virtual object display component. In other examples, an application can gain focus when it is launched, restored, or in any other suitable manner.

Application(s) in the unfocused stage can be one, two, or more concurrently executing application(s) operating in cooperative mode that do not have user input priority. For example, when three applications are concurrently executing in a system shell, two can be unfocused (e.g., without user input priority) and one can be focused. In some implementations, unfocused applications continue to execute at the system shell (e.g., are not backgrounded or suspended) and their content continues to be displayed at their corresponding virtual object displays.

Application(s) in the minimized stage can be backgrounded or suspended applications that comprise a stored state (e.g., shell state and application state) so that the application(s) can be restored (e.g., to a state at the time the application was minimized). In some implementations, minimized applications are not executing at the system shell and do not comprise a corresponding virtual object display. Applications in an inactive state are applications that are not executing and do not comprise a stored state. When launched, inactive applications create a new application session (rather than restoring to a stored state).

In some implementations, during cooperative mode, when an application is launched, restored from a stored state, or selected by a user (e.g., via user input) the application is put into focus. For example, the application will gain focus (e.g., input priority) and a previous application that had focus will lose focus. In some implementations, a first application can launch a second application, and the launched second application gains focus while the first application loses focus. In some implementations, the system shell can automatically minimize one or more defocused applications to conserve system resources. Because shell (e.g., virtual object position and/or size) and application state are saved during minimization, the user does not risk loss of state when the system shell minimizes a defocused application.

Figures 5 is a diagram of a three-dimensional environment for a system shell with concurrently executing applications. Environment 500 includes virtual objects 502, 504, and 506, virtual hand 508, and menu 510. In some implementations, environment 500 can be a three-dimensional environment for a system shell. Environment 500 (and the system shell) can be operating in cooperative mode. For example, virtual objects 502, 504, and 506 can be two-dimensional virtual objects (e.g., panels) assigned to nodes at the near-field that each correspond to a different executing application. Virtual hand 508 can be a user presence in environment 500 controlled by tracked user movement (e.g., hand movement, controller movement, etc.). In environment 500, virtual hand 508 is interacting with virtual object 502. Accordingly virtual object 502 and its corresponding executing application are in focus (e.g., have user input priority) while virtual objects 504 and 506 and their corresponding executing applications are unfocused (e.g., executing with display components, lack of user input priority).

Menu 510 can comprise a listing of the focused application, unfocused applications, minimized applications, applications available for launch, recently used applications, any other suitable listing of applications, or any combination thereof. In some implementations, menu 510 can be used to launch applications, restore a minimized application to executing/unfocused status, enter exclusive mode for an application, or for any other suitable purpose.

Figures 6A and 6B are diagrams of three-dimensional environments for a system shell with multiple virtual object displays. Environment 600 of Figure 6A includes field 602, virtual objects 604, 606, and 608, exclusive field 610, and user 612. When environment 600 and the system shell are in cooperative mode, multiple applications can be concurrently running that each correspond to one or virtual objects 604, 606, and 608. Field 602 can be a cylindrical surface a distance away from user 612 (e.g., 2 meters, 4 meters, etc.) with node points assignable to virtual objects, such as a near-field. For example, virtual objects 604, 606, and 608 are each assigned to a node of field 602.

Environment 620 of Figure 6B includes virtual objects 622, 624, and 626. Environment 620 can be similar to environment 500 of Figure 5, where concurrently executing applications can each correspond to one of virtual objects 622, 624, and 626. For example, virtual objects 622, 624, and 626 can each display the content for an executing application.

Returning to environment 600 of Figures 6A, in some implementations environment 600 can transition to exclusive mode, for example in response to user input that transitions one of the executing applications into exclusive mode, when an application requests exclusive mode, or in any other suitable manner. Exclusive field 610 can be a field within environment 600 closer to user 612 than the field 602 in which a virtual object (e.g., two-dimensional panel) can be displayed, such as a virtual object that corresponds to the application running in exclusive mode. In this example, the display of virtual objects 604, 606, and 608 can be selectively removed from environment 600 such that only the virtual object that corresponds the application executing in exclusive mode remains. This virtual object can be displayed at any other suitable location other than exclusive field 610. In some implementation’s, an application operating in exclusive mode displays a three-dimensional XR environment to user 612. For example, prior to exclusive mode, the three-dimensional XR environment displayed to user 612 can be a shell XR environment. In exclusive mode, the shell XR environment can be replaced by an application XR environment (e.g., XR environment provided by the application operating in exclusive mode). The content displayed throughout the XR environment can include multiple virtual objects, a sky box, background, lighting, filters, augments, and any other suitable content. In some implementations, the application operating in exclusive mode can be an immersive gaming application, and the content can be immersive gaming content (e.g., a user avatar, other user avatars, three-dimensional virtual objects, two-dimensional panels, different skyboxes and backgrounds, etc.).

Implementations of the three-dimensional environment include a theater screen at a far-field region or volume. Figure 7A is a diagram of a three-dimensional environment with a theater display. Environment 700 includes theater object 702, far-field 704, near-field 706, and user 708. Far-field 704 can be a cylindrical surface, portion of a cylindrical surface, or any other suitable field that is further from the user than near-field 706. Theater object 702 can be a virtual object assigned to far-field 704 that displays content for an executing application. In some implementations, environment 700 can operate in cooperative mode. For example, theater object 702 can display a video while a user interacts with other executing applications via their corresponding virtual objects.

Figure 7B is a diagram of a three-dimensional environment illustrating multiple display locations. Diagram 710 illustrates different display locations for near-field displays 712, a far-field display 716, and an exclusive field display 714. Each of near-field displays 712, far-field display 716, and exclusive field display 714 can display content from an executing application, such as in different modes of operation for a system shell. Exclusive field display 714 can be a virtual object that displays content for an application that executes in exclusive mode. Near-field displays 712 can be virtual objects that display content for concurrently executing applications while the system shell operates in cooperative mode. In one or both of exclusive mode or cooperative mode, far-field display 716 can be a theater object that displays application content to a user, such as video content.

In some implementations, a theater screen can be shared among multiple users. Figure 8 is a diagram of a shared three-dimensional environment in theater mode. Environment 800 includes theater object 802 and users 804. Each of users 804 can be displayed a three-dimensional environment by XR systems that comprise theater object 802. For example, a video can be cast to theater object 802 by any participating XR system/system shell, and the video can be simultaneously displayed to users 804 via their XR systems.

Those skilled in the art will appreciate that the components illustrated in Figures 1-5, 6A, 6B, 7A, 7B, and 8 described above, and in each of the flow diagrams discussed below, may be altered in a variety of ways. For example, the order of the logic may be rearranged, substeps may be performed in parallel, illustrated logic may be omitted, other logic may be included, etc. In some implementations, one or more of the components described above can execute one or more of the processes described below.

Figure 9 is a flow diagram illustrating a process used in some implementations of the present technology for application multitasking in a shell with a three-dimensional environment. In some implementations, process 900 can be performed by an XR system. In some implementations, process 900 can be triggered when a three-dimensional environment for a system shell is displayed to a user.

At block 902, process 900 can display a three-dimensional environment for a system shell to a user. For example, an XR system can display an immersive three-dimensional environment to a user that includes content (e.g., virtual objects, application content, etc.) for a system shell. In some implementations, the shell XR environment can be displayed to a user via an XR device. In some implementations, a given executing application and/or executing software process can comprise display priority such that the XR device displays content from the priority application/process. In some instances, a shell application can comprise this priority (e.g., in cooperative mode). In other instances, another executing application can comprise this priority (e.g., when the other application is executing in exclusive mode).

At block 904, process 900 can display first and second virtual objects in the three-dimensional environment. For example, the system shell and three-dimensional environment can operate in a cooperative mode where multiple concurrent applications are executing. The first virtual object can display content for a first executing application and the second virtual object can display content for a second executing application. In some implementations, the first and second virtual objects are displayed at a first distance from the user, such as at a near-field, while the system shell and three-dimensional environment are in cooperative mode.

At block 906, process 900 can detect when an exclusive mode has been initiated for the first application. For example, a user can initiate exclusive mode for the first application, or the first application can request exclusive mode to perform application functionality. In response, the system shell and three-dimensional environment can transition from cooperative mode to exclusive mode. When exclusive mode for an application is initiated, process 900 can progress to block 908. When exclusive mode for an application is not initiated, process 900 can loop back to block 904, where the first and second virtual objects can continue to be displayed in the three-dimensional environment until exclusive mode is initiated.

At block 908, process 900 can provide the first application exclusive mode operation. For example, in exclusive mode, the first application can display any suitable content to the user via the XR device display component (e.g. , head-mounted display). In some implementations, the operation in exclusive mode prevents applications, other than the first application, from displaying world-locked content via the XR device. In some implementations, the operation in exclusive mode provides the first application use of at least a designated exclusive region of the XR environment (e.g., the whole viewable area, a field in front of the user, a specified volume taking most of the viewable area, etc).

In some implementations, process 900 can, in exclusive mode, dynamically display a third virtual object in the XR environment (e.g., shell XR environment). For example, the third virtual object can be displayed at a distance from the user that is closer than the first distance, such as in the exclusive region. The third virtual object can be displayed at any other suitable location. The third virtual object can display content for the first application while the application remains in exclusive mode. In some implementations, while in exclusive mode the first virtual object and second virtual object are removed from display in the three-dimensional environment (e.g., shell XR environment).

In some implementations, while operating in exclusive mode, the first application can display, via the XR device, a first application XR environment to the user. For example, prior to exclusive mode (e.g., in cooperative mode), the three- dimensional environment displayed to the user can be a shell XR environment. In exclusive mode, content for the first application can be a first application XR environment, and the XR device can replace the shell XR environment with the first application XR environment. For example, the first application can comprise priority over the shell application relative to the XR device display component when operating in exclusive mode. In some implementations, the first application can comprise an immersive gaming application, and the first application XR environment can comprise immersive gaming content (e.g., avatar(s), virtual object(s), skybox(es), background(s), etc.).

At block 910, process 900 can store, in response to triggering the exclusive mode for the first application, state information for the second executing application and the second virtual object. In some implementations, the second executing application is transitioned to a background (e.g., suspended, minimized, etc.) while the first application operates in exclusive mode. The system shell and second application can save the second application’s state at the time it is transitioned to the background. For example, the stored state information can include a content state for the second virtual object and an execution state for the second executing application.

At block 912, process 900 can detect when exclusive mode is terminated. For example, a user can exit exclusive mode for the first application (e.g., via input that transitions from exclusive mode) and/or the first application can request a transition from exclusive mode (e.g., back to cooperative mode). When it is detected that exclusive mode is terminated, process 900 can progress to block 912. When it is not detected that exclusive mode has terminated, process 900 can loop back to block 908, where the third virtual object can continue to be displayed in exclusive mode until exclusive mode is terminated.

At block 914, process 900 can restore the first and second virtual objects. For example, the third virtual object can be removed from display when exclusive mode is terminated and the first and second virtual objects can be redisplayed (e.g., at the first distance from the user). In some implementations, the first virtual object resumes display of the content for the first application while executing in cooperative mode. In some implementations, the second application is transitioned back to executing and its state is restored based on its previously stored state. The second virtual object can display content (e.g., the restored state) of the second application while executing in cooperative mode.

In some implementations, in response to terminating the exclusive mode, the XR device replaces the first application XR environment with the shell XR environment. For example, when the content for the first application comprises a first application XR environment, terminating exclusive mode can include returning to the shell XR environment. In this example, the first and second virtual objects can be restored in the shell XR environment.

In some implementations, redisplaying the second virtual object in the XR environment comprises restoring, using the stored state information, content displayed at the second virtual object and an execution state for the second application. For example, the second application can be restored to the execution state that it was in at the time that exclusive mode was triggered for the first application. In addition, the content displayed at the second virtual object can be restored to the content it displayed at the time that exclusive mode was triggered for the first application. Process 900 can then progress to block 904, where the first and second virtual objects are displayed in cooperative mode in the there-dimension environment for the system shell.

Reference in this specification to "implementations" (e.g., "some implementations," "various implementations," “one implementation,” “an implementation,” etc.) means that a particular feature, structure, or characteristic described in connection with the implementation is included in at least one implementation of the disclosure. The appearances of these phrases in various places in the specification are not necessarily all referring to the same implementation, nor are separate or alternative implementations mutually exclusive of other implementations. Moreover, various features are described which may be exhibited by some implementations and not by others. Similarly, various requirements are described which may be requirements for some implementations but not for other implementations.

As used herein, being above a threshold means that a value for an item under comparison is above a specified other value, that an item under comparison is among a certain specified number of items with the largest value, or that an item under comparison has a value within a specified top percentage value. As used herein, being below a threshold means that a value for an item under comparison is below a specified other value, that an item under comparison is among a certain specified number of items with the smallest value, or that an item under comparison has a value within a specified bottom percentage value. As used herein, being within a threshold means that a value for an item under comparison is between two specified other values, that an item under comparison is among a middle-specified number of items, or that an item under comparison has a value within a middle-specified percentage range. Relative terms, such as high or unimportant, when not otherwise defined, can be understood as assigning a value and determining how that value compares to an established threshold. For example, the phrase "selecting a fast connection" can be understood to mean selecting a connection that has a value assigned corresponding to its connection speed that is above a threshold.

As used herein, the word "or" refers to any possible permutation of a set of items. For example, the phrase "A, B, or C" refers to at least one of A, B, C, or any combination thereof, such as any of: A; B; C; A and B; A and C; B and C; A, B, and C; or multiple of any item such as A and A; B, B, and C; A, A, B, C, and C; etc.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Specific embodiments and implementations have been described herein for purposes of illustration, but various modifications can be made without deviating from the scope of the embodiments and implementations. The specific features and acts described above are disclosed as example forms of implementing the claims that follow. Accordingly, the embodiments and implementations are not limited except as by the appended claims.